Tuesday, October 27, 2009
Thursday, October 8, 2009
Work flow of new DET
1.While doing day end in Treasury Module data relating to Treasury i.e. the time at which the cash given to the last postman, sale of publication, Stamp Sales, etc. will be inserted in the Local Server.
2.While doing day end in Postman Module the data relating to the delivery performance of SP, EPP, RLs, Parcels, Etc. will be inserted in the Local Server.
3.While doing day end in Point of Sale data relating to POS i.e.IPO Sold, MPCM no of transactions, eMOs booked, VPMOs booked, Ordinary MOs booked, Stamps prefixed, Postage revenue realised, articles booked and despatched etc. will be inserted in the Local Server.
4.While doing day end in Sanchay Post 6.5 data relating to signature scanning i.e. Signature Scanning Details account type wise will be inserted in the Local Server.
5.While executing the Sanchay Post - Project Arrow Reports the data relating to Sanchay Post i.e total no. of live accounts account type wise, transaction time, no of transactions account type wise, etc will be inserted in the Local Server.
6.While executing Meghdoot Accounts Mis Client all the data which was inserted as said above in local server will be extracted and encrypted file(.psq) with this data will be created and transmitted to central server.
2.While doing day end in Postman Module the data relating to the delivery performance of SP, EPP, RLs, Parcels, Etc. will be inserted in the Local Server.
3.While doing day end in Point of Sale data relating to POS i.e.IPO Sold, MPCM no of transactions, eMOs booked, VPMOs booked, Ordinary MOs booked, Stamps prefixed, Postage revenue realised, articles booked and despatched etc. will be inserted in the Local Server.
4.While doing day end in Sanchay Post 6.5 data relating to signature scanning i.e. Signature Scanning Details account type wise will be inserted in the Local Server.
5.While executing the Sanchay Post - Project Arrow Reports the data relating to Sanchay Post i.e total no. of live accounts account type wise, transaction time, no of transactions account type wise, etc will be inserted in the Local Server.
6.While executing Meghdoot Accounts Mis Client all the data which was inserted as said above in local server will be extracted and encrypted file(.psq) with this data will be created and transmitted to central server.
Precautions for proper updation of data relating to all columns in DET
For proper updation of data relating to all columns in DET the following procedure to be followed scrupulously.
1.Day end/Shift end in all the modules of Meghdoot including eMO must be completed. Regarding the following modules the day end sequence must be followed as below.
a.Speed Net
b.Postman
c.Point of Sale.
Remaining modules can be day ended in any sequence. But day end must be done in all the meghdoot modules.
2.Day end in Sanchay Post 6.5 to be performed.
3.Sanchay Post - Project Arrow Reports( Installed with the setup available in Meghdoot 6.6 CD) must be executed.
4.Meghdoot Accounts MIS Client to be executed.
If the above sequence is followed, the data relating to all the columns will be transmitted to the central server.
1.Day end/Shift end in all the modules of Meghdoot including eMO must be completed. Regarding the following modules the day end sequence must be followed as below.
a.Speed Net
b.Postman
c.Point of Sale.
Remaining modules can be day ended in any sequence. But day end must be done in all the meghdoot modules.
2.Day end in Sanchay Post 6.5 to be performed.
3.Sanchay Post - Project Arrow Reports( Installed with the setup available in Meghdoot 6.6 CD) must be executed.
4.Meghdoot Accounts MIS Client to be executed.
If the above sequence is followed, the data relating to all the columns will be transmitted to the central server.
SOLUTION FOR ERRORS ARISED WHEN ACCOUNTS MIS APPLICATION IS INSTALLED AFRESH:
If Accounts MIS application is installed afresh and any error relating to project database occurs, following are the possible actions:
1. If Sanchay Post Version 6.0 or earlier version is used, upgrade to Version 6.5 immediately.
2. If Post Office is already using Sanchay Post Version 6.5, use DB Analyzer to check whether Post Office has upgraded to Version 6.5 successfully. While checking, if DB Analyzer displays error code 1: Z, run 'ARROW.EXE' which is available at www.tamilnadupost.nic.in/sdc/sblan.htm to create the Project database & login.
3. If the Post Office has shifted operations to a new server after up gradation to Sanchay Post Version 6.5, run 'ARROW.EXE' to create the Project database & login and then restore the Project database's backup, if available. Not restoring backup of Project database or removal of the existing Project database and recreating it using 'ARROW.EXE' will result in loss of previous transaction data.
4. ARROW.EXE file in zip format is available at the SBLAN webpage i.e., www.tamilnadupost.nic.in/sdc/sblan.htm along with the instructions for use.
1. If Sanchay Post Version 6.0 or earlier version is used, upgrade to Version 6.5 immediately.
2. If Post Office is already using Sanchay Post Version 6.5, use DB Analyzer to check whether Post Office has upgraded to Version 6.5 successfully. While checking, if DB Analyzer displays error code 1: Z, run 'ARROW.EXE' which is available at www.tamilnadupost.nic.in/sdc/sblan.htm to create the Project database & login.
3. If the Post Office has shifted operations to a new server after up gradation to Sanchay Post Version 6.5, run 'ARROW.EXE' to create the Project database & login and then restore the Project database's backup, if available. Not restoring backup of Project database or removal of the existing Project database and recreating it using 'ARROW.EXE' will result in loss of previous transaction data.
4. ARROW.EXE file in zip format is available at the SBLAN webpage i.e., www.tamilnadupost.nic.in/sdc/sblan.htm along with the instructions for use.
Solution for not transmitting signature scanned data
The reason for this discrepancy was improper installation of Accounts MIS part of Meghdoot 6.6.
All the Project Arrow offices are required to follow the following steps, so that signature scanned data is captured regularly by New DET:
1. Sanchay Post Project Arrow Interface module which is available in Meghdoot 6.6 cd has to be uninstalled in all Project Arrow Phase I, II and III Offices and also Phase III-A, if installed earlier.
2. At any time, the option Sanchay Post >> Project Arrow >> Transaction Time Report should be used for viewing KPIs, instead of Project Arrow Interface Module.
3. The KPIs are updated during day end process automatically.
4. It should be ensured that all the patches for Version 6.5 available on SDC Chennai website i.e., www.tamilnadupost.nic.in/sdc/sblan.htm are copied to the respective folders (after unzipping) in all the clients running Sanchay Post.
Out of four points, point no. 01 and 04 must be performed with due care then only signature scanned data will be transmitted.
All the Project Arrow offices are required to follow the following steps, so that signature scanned data is captured regularly by New DET:
1. Sanchay Post Project Arrow Interface module which is available in Meghdoot 6.6 cd has to be uninstalled in all Project Arrow Phase I, II and III Offices and also Phase III-A, if installed earlier.
2. At any time, the option Sanchay Post >> Project Arrow >> Transaction Time Report should be used for viewing KPIs, instead of Project Arrow Interface Module.
3. The KPIs are updated during day end process automatically.
4. It should be ensured that all the patches for Version 6.5 available on SDC Chennai website i.e., www.tamilnadupost.nic.in/sdc/sblan.htm are copied to the respective folders (after unzipping) in all the clients running Sanchay Post.
Out of four points, point no. 01 and 04 must be performed with due care then only signature scanned data will be transmitted.
Wednesday, October 7, 2009
Subscribe to:
Posts (Atom)