08 August 2014
09 May 2014
Update Delivered / Returned COD Articles
In Most of the Post Offices COD Article Status Not updated in Parcel Net MIS, and Postman Status so that those COD articles Status shows Still in Deposit.
Reason for Non Updation of COD Article Status
- COD Window Delivered articles not updated due to Previous version of Parcel Net issues.
- Delivered / Returned Message has been broken while transmit from Local server.
- Not Taken BO COD Article returns.
Window Delivery Issues
In many Sub Offices / Head Offices were taken the returns as window delivered but in Postman Module show the Status as "Still In Deposit" but in Remarks "Window Delivery".
- Download attached script from PoTools.
- Execute Once Using MM Script Tool.
- Execute R Net Communication and wait at least 24 hours to update in Parcel Net MIS.
Update Article Status in MIS
In Some of the Offices, article status was not update even taking the correct returns. This issues not only for the COD Articles and also the Register, Parcel articles.
- After Day End / Before Day Begin - Login as Postman Supervisor
- Goto Tools > Click On delivery / Undelivery Article Message.
- Execute R Net communication.
- Wait at Least 24 hours to update MIS Status.
BO COD Returns Not Taken
In some case few SOs not Taken the BO COD Article Returns, just enter the COD Value in Sub Account Module and just make it in Treasury Account. Those articles was not updated and payment also has not done at booking office to Bulk COD Customer.
Contact CEPT with COD article Number and Paid date to Update the delivery Status.
06 May 2014
COD Messages Received:
No Articles were found while fetch in Postman Module
Solution Shared by
RABINARAYAN CHOUDHURY Mobile : +91-9778236897
- Download attached Script from PoTools.
- Execute Once Using MM Script Tools.
- Now you can Fetch the Article in Postman Module.
94 Department of Post employees have been identified as the top performers for their outstanding contribution in the Change Network of IT Modernisation Project 2012. Our Change Leaders and Change Agents have gone that extra mile in ensuring their fellow DoP employees are aware of the upcoming solutions and have relayed employee concerns to us. We thank each one of you for taking up your role in the Change Network with such zeal and look forward to your continued efforts in the times ahead.
Click here to get the detailed list of the Top Performers
The search option which newly included in postman module is not checking all the tables. Here is an Tool that will check all details including despatch module.
Execute on PC having windows authentication
1. Provide Correct Server Name
2. Check on windows authentication
3. Type Exact COD article number then click on find status.
Note : Article Number Should be 13 Digit Only
Nedumkandam 685 553. Mobile: 9497278337
Developed and shared byRajesh CR - System Administrator.
Nedumkandam 685 553. Mobile: 9497278337
05 May 2014
The non receipt of electronic data of a particular Parcel COD article at a delivery post office is largely either due to operational errors or error in R Net Communication. Precisely there are 06 parameters which need to be checked specifically before arriving at probable reason for non receipt of electronic data of any Parcel COD article at a delivery PO and further diagnosis of the issue. All these 06 parameters along with relevant details are listed below.
It is requested to check each of these 06 Parameters to ensure that it satisfies the desired status, before raising the issue with the CEPT Support Desk. Do mention the actual status against each of the 06 parameters while raising any issue of non receipt of electronic data with CEPT to enable us to ensure speedy disposal of the case.
Note: After receiving the Request Resend option by the Postman Supervisor, the Central Server may take some time to honor the request depending upon the load on the Central Server and hence please wait for at least 02 Hrs, run the R Net Communication and check.
Solution Number 01: Office properly upgraded to Meghdoot version 7.9.1 but reflecting as Not Upgraded in Parcel Net MIS Report Office Not
Upgraded to version 7.9.1
After upgradation of office, version update files are generated automatically and are communicated to Central Server through R Net Communication which in turn updates the MIS Report. However in the instant cases it seems there might have been some issues in the transmission of version update files to the central server through R Net communication after upgradation of office with update 7.9.1. Therefore in order to re-generate the version update files internally, please run the scripts kept at the location mentioned below using Meghdoot Script Tool after taking backup of counter database. Thereafter run the R Net Communication. After some time please check the MIS Report for confirmation.
There are 02 Script Files kept at the location mentioned above:
1. Counter23042014.exl: For upgradation of Despatch to 7.9.1 & Point of sale to 7.91.
2. Postman&Rnetcommunication_versionupdate7.9.1.exl: For upgradation of Postman to 7.9.1 & R Net Communication to 7.9.1