How to reset the sequence number to 1 at SO? Use the option ‘DBAnalyzer >> DBUtilities >> SO - HO Data Transfer’ before doing da...
How to reset the sequence number to 1 at SO?
Use the option ‘DBAnalyzer >> DBUtilities >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced.
Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme.
This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post.
2.How to reset the sequence number to 1 at HO for a SO?
Use the option ‘DBAnalyzer >> DBUtilities >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced.
Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO.
3.What are the preparatory steps for commencement of SO to HO data transfer?
The following points are to be ensured:a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code.b. Include HO name in SOs (Using PO Name & Address Form) in a separate row.c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed.d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which data transfer is to be commenced.e. Rectify the discrepancies listed in DBAnalyzer.
4.
Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated.
Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check ‘Initialisation >> PO Name & Address’ form and ensure that the scheme is selected in ‘Set Scheme Computerisation Status’ option.
5.
Files generated at SO are without extension and hence cannot be imported at HO
HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row.
6.
'Data does not belong to [soname]’ message displayed while importing data.
Select the file again and retry
Logout and login to SOSB module and retry
Ask SO to re-generate the file & resend.
If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO.
7.
RD bulk posting data not transferred.
RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).
Use the option ‘DBAnalyzer >> DBUtilities >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced.
Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme.
This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post.
2.How to reset the sequence number to 1 at HO for a SO?
Use the option ‘DBAnalyzer >> DBUtilities >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced.
Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO.
3.What are the preparatory steps for commencement of SO to HO data transfer?
The following points are to be ensured:a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code.b. Include HO name in SOs (Using PO Name & Address Form) in a separate row.c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed.d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which data transfer is to be commenced.e. Rectify the discrepancies listed in DBAnalyzer.
4.
Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated.
Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check ‘Initialisation >> PO Name & Address’ form and ensure that the scheme is selected in ‘Set Scheme Computerisation Status’ option.
5.
Files generated at SO are without extension and hence cannot be imported at HO
HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row.
6.
'Data does not belong to [soname]’ message displayed while importing data.
Select the file again and retry
Logout and login to SOSB module and retry
Ask SO to re-generate the file & resend.
If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO.
7.
RD bulk posting data not transferred.
RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).
COMMENTS