Short Notes for PAs/SPMs for Postal Operations
Short Notes for PAs/SPMs for Postal Operations
Thanks to Prabhat Kumar Sahu, Balangir Dn., Odisha Circle
Download PDF
Download PDF
Articles by "DPMS"
Showing posts with label DPMS. Show all posts
EOD Role Assignment in CSI SAP || Beat EOD Error in DPMS Module & Solution
Anyone facing Beat EOD error in delivery POs please follow below procedure.
Assign Update EOD flag role to Divisional Head.
Then in his login use TCODE ZMO_EOD_INSERT
Fill up necessary details and execute.
Check the Role after 10Mins by doing EOD in the allotted user.
CSI COD Front Ending Standard Operating Procedure Ver. 2.0 || By CEPT-DPMS
What’s New in Ver 2.0 >>>
ZCOD_DUPLICATE T-Code
Has been enhanced to identify duplicate articles from Paid and unpaid article list Biller ID wise.
Introduction :
The Purpose of this document is to enable user to make Payment against Cash on Delivery collections of Mail articles within CSI.
Objectives of CSI COD Front Ending :
1. Accounting document posted against Delivery office after DPMS EOD& COD cash collected from postman/Window Delivery/RICT delivery/BO returns will be processed directly (Pan India) for Payment.
Hence Article can be paid soon after Delivery confirmation & COD cash collected from postman.
2. COD reports introduced for Delivery & RTS articles list based on Booking Date & Delivery Date.
3. ZART_UPLOAD restricted for the front ended biller & hence Booking Data cannot be created.
• Article can be delivered or returned only if the booking data is available in CSI.
4. No changes in Delivery operations & few modifications in Payment process:
a. Payment due report (FBL5N).
b. Posting Payment (F-58).
c. Payment Details (ZFI_EPAY).
5. Payment of COD Collections made at Non-CSI Office (Including TNF) continues with existing process.
6. CEPT E-payment site/Parcelnet reports will not include the collections/payments of CSI Offices.
7. Any files related to delivery/payments for COD Customer to be generated at nodal Payment/Booking Office only.
Hence no download currently possible at CEPT Epayment site for COD Customers.
Legacy CODE mapping is also not required.
OFFLINE DELIVERY AND DESPATCH TOOL Version 1.0.0
OFFLINE DELIVERY AND DESPATCH TOOL Version 1.0.0
Help
This tool is provided as an aid and an alternative to spreadsheet to perform offline delivery and despatch work in case of inaccessibility of SAP by any means, otherwise use of this tool should strictly be avoided and is not recommended. The developer is not responsible for any misuse and unauthorized use of this tool. See disclaimer under about menu. The disclaimer is clearly stated in accordance with widely accepted licensing model and accepted principles of law.
Access to this tool is protected by means of username and password. Multiple users are supported. Minimum password length should be 8 eight chars with any combinations. Anybody can create a user and start to work. All users will have same access rights. Users can change his password at their convenience. User id can not be deleted. Every user is responsible for authenticity of data and safety of database. Logged in user id will be shown when you are logged in. Log info is not stored in Database. Password is stored in DB in encrypted form.
Configuration is needed when it is used for the first time. Office name has to be entered. Beat and BO details can be entered up to 30 each. In destination, all destinations to which bags are closed and despatched are entered.
Article barcode number validation is incorporated which will prevent invalid barcode usage.
Bag barcode number validation is incorporated which will prevent invalid inclusion of any article in the unsupported bag.
To make the task easier, it is designed that opening of bag, delivery and despatch is not interlinked and will work separately without depend on each other. Which means that straight away delivery can be made even without opening of bag and straight away despatch can be made even without opening of bag and without making delivery.
Opening of bag is to be done under Bag Open menu. Bag can be opened and reopened any number of times. Reopening can be done in case of alteration. Recd. Bag manifest can be printed under Recd. Bag Manifest under Report menu. In which enter bag id and print manifest for any date. The manifest can be printed in two different form ie) with or without barcode in it. Barcode will make the task of later bag opening in SAP-DPMS easier in case of articles were sent out for delivery.
Beat issue and BO issue can be made under Issue under Delivery menu. If name and address is needed uncheck auto save checkbox. It is auto saved after every article is invoiced. Delivery slip can be printed there itself. Delivery slip will be saved in Documents folder by default. Wrong entry can be deleted by selection. Same article can not be issued more than once in a working day but different day possible. Issue of articles can not be made after returns taken. The same is applicable to BOs also.
Beat returns can be made under beat returns under delivery menu. Returns can be taken for any pending date and beat. When you click on submit, returns will be completed. Summary will be shown. Only three remarks can be give namely “Delivered”, “On Hold” and “Despatch”. Excel file containing delivered articles and on hold articles can be generated for any date for every beat and BO under Export under Report menu. The files will be saved in a newly created folder under Desktop. The folder name will be date of working. If any file is created with the same name available in that folder, will be overwritten. The exported files can be uploaded in SAP using t-code provided by CEPT.
BO returns can be made under BO returns under delivery menu. List of all pending articles will be shown for every BO. Select article number, date of remark and remark and then click on mark button for every article and finally give submit to finish returns. BO returns can be recurred until all pending is over. Rest is same as Beat returns.
Return remark can be modified for any article under Modify Returns under Delivery menu.
Despatch of articles can be made under despatch menu. Before invoicing of articles, bag should be created under Create Bag menu. Created bag can be deleted by selection if it is in open status. Any invoiced articles will also be deleted. Closed and despatched bags can not be deleted. When you create, bag status will be open. Bag closing can be made under Close bag menu. When you click on Re(Scan) button, bag status will be changed to open. When you click on Re(Close) button status will be changed to Closed. Bags can be reopened and closed for any number of times before despatch. Despatched bags can not be reopened. Despatch manifest can be printed with barcode or without barcode. Barcode printed on the manifest will make the task of later closing of bag in SAP easier in case of bags were despatched offline.
Despatch of bags can be done under despatch bags menu. List of all pending closed bags will be shown. You can despatch one by one or all at once.
Recd. bag manifest can be printed later under report menu.
Despatched bag manifest can be printed later under report menu.
List delivered and on hold articles for any date of remark can be generated under export menu for any date. All generated files will be stored in a newly created folder in desktop. The folder name will be date of working day.
Details of any article can be searched in find article menu.
Under print barcode menu, barcodes can be printed for article numbers. Copy form spreadsheet and paste it. Minimum columns should be one. Maximum three columns are supported. Any excess pasted columns will clipped off while printing of barcodes. First row should contain headers. First column will be barcoded.
All components are bundled with this tool and hence will not need any prerequisites and will run on most windows platform.
Data is permanent unless deleted by user.
This tool is not designed to support to work with multiple users at the same time. It is not designed to work as server and client. If this tool is required to be shifted to another computer without loss of data, first of all take backup of the database to external drive. Install this tool in another computer. Create one temp user. Login with that user. After that restore the database in the new machine from the backup. This tool will now be entered into the state like in the old computer. Newly created temp user will be lost.
Database option is used to backup database, restore database and delete old data. It is recommended to take periodic backup of database for safety. When database is corrupted or lost by any means, restore the database from backup. Database includes user credentials and all data. When the database is restored, the state of the tool goes back to the time when the backup took place. It means that any newly created users along with newly worked out data will be lost. It is recommended to periodically delete old data of unwanted period to improve database performance.
To completely remove this tool, go to programs and features under control panel and uninstall it. First of all it is recommended to take backup of database.
That's it.
eMO paid list Generation- An ultimate solution [CSI - DPMS]
eMOPaidKavasuDynamicSolution :
(An Ultimate Solution)
Introduction:
Now a day, Post offices are working with CSI and DPMS is not generating eMO Paid Report properly. Our Postal Staff facing lot of difficulties while generation eMO paid List. Hence this tool designed.
Designer:
Umesha HN Sub Post Master Palya-573218 Karnataka Circle
contact and Whatsapp: 9449759640 9036683744 eMail : skpumesha@gmail.com
How to Use:
After dolwnload the Tool, do the office configuration by using the folder eMOPaidList>FacilityIDs.txt
Do the MSAccess2007 settings by using the link provided by the developer Watch the video for ”How To Work” and get the report
Links Tool
Video
Instructions on taking postman returns for previous day [Procedure for SAP Down]
For completing yesterday''s DPMS work like beat returns and EOD. Follow below steps to perform previous day returns
- In DPMS, under supervisor approval
- Give delayed confirmation approval for that date
- Enter reason:sap not accessible (examples)
- Then approve
- Take returns if not taken with the previous date for that beat
- And give eod that beat.
- Receive cash for that beat on yesterday date
If u have given eod for one beat,don't wait for all beats to give eod. Now you can start today's work for the beat (for H.Os..It may be useful)
Unpaid EMO'S Report Generation in DPMS - CSI
Sir/madam,
This is regarding introduction of a new report in CSI DPMS exclusively to view and monitor the unpaid eMOs on daily basis. The salient features are mentioned below:
a) A word document containing the t-code (zemo_unpaid) and steps to enter the key values is attached
b) The output of this t-code displays all the eMOs pending disposal at the particular post office for the day given as input
c) The list displays pending eMOs after receipt at the post office with the following fields
eMO Number
Date of Booking
Amount of eMO
Status ( like printed, received, taken out etc)
Date of receipt of the eMO at the post office
d) The list also arranged in the order of oldest eMO pending based on the date of receipt at the office
The SPMs / Supervisors of all offices are instructed to run this t-code at the close of everyday and they should review the actual status of the eMOs pending to ensure disposal of them within the timeline prescribed. A mail is sent in this regard.
This is regarding introduction of a new report in CSI DPMS exclusively to view and monitor the unpaid eMOs on daily basis. The salient features are mentioned below:
a) A word document containing the t-code (zemo_unpaid) and steps to enter the key values is attached
b) The output of this t-code displays all the eMOs pending disposal at the particular post office for the day given as input
c) The list displays pending eMOs after receipt at the post office with the following fields
eMO Number
Date of Booking
Amount of eMO
Status ( like printed, received, taken out etc)
Date of receipt of the eMO at the post office
d) The list also arranged in the order of oldest eMO pending based on the date of receipt at the office
The SPMs / Supervisors of all offices are instructed to run this t-code at the close of everyday and they should review the actual status of the eMOs pending to ensure disposal of them within the timeline prescribed. A mail is sent in this regard.
BCP for DPMS operations in CSI - Procedure for uploading the delivery data excel file in SAP - ZMOEXCELUPLOAD
Respected Sir (s) / Madam(s),
This is regarding instructions to upload articles delivery information and articles deposit information in to DPMS.
Instructions may kindly be issued to follow the guidelines below:
1. Prepare the list in excel containing the articles delivered beat-wise (Article numbers only)
2. Prepare the list in excel containing the articles on hold beat-wise (returned by postmen to be kept in deposit for today – Article numbers only)
3. Those articles which are returned to sender may be handled manually today
4. Items as in (1) and (2) may be kept ready for upload CSI-SAP
Procedure for uploading the delivery data excel file in SAP:
Step-1:
a) Use t-code zmoexcelupload
b) Enter the mandatory selections like facility ID and Date of delivery (Actual date of delivery)
c) Upload the entire excel which was prepared on that date both delivered beat-wise and onhold – beatwise first
d) Those records for which data was available in dpms on that date will get updated and a summary will be displayed
Total number of articles in excel,
Total number dated and
Total number not updated
e) Total number not updated is due to non-availability of the article data in the DPMS
f) Through the hyperlink from the summary, copy of the list of articles not updated and then follow step-2
Step-2:
g) In DPMS, received a bag with the bag ID
h) Open the same bag ID ( legacy option)
i) Enter those articles copied as in (f) and treat those articles as received through this bag-ID
j) Then those articles would be available in DPMS
Step-3:
k) Again repeat the exercise as in step-1 for both delivered and on-hold articles
l) This would update both the delivery information and on-hold information in DPMS
For any further queries and support, instructions may be issued to call DMCC Chennai.
Yours Sincerely,
(V M Sakthivelu)
Deputy Director CEPT
Solution for "Bag is locked by other user" during bag open in DPMS
Error :
Bag is locked by other user
Solution:
After Bag receipt is completed user has to refresh or close Bag Receive screen. untill then Bag Id ll be locked for further access.
Techinical team is working to improve performance, kindly follow said process.
Mandatorily user has to refresh or close Bag Receive screen after any count of bags Received succesfully.
Regards
CSI CCT
CEPT Mysuru
Changes in DPMS - eMO Screen [CSI Update]
Request all DPMS users to use View update individual emo screen with date filter range for two weeks only. Do not run the transaction without date filter.
Request all spocs of different circle and division to pass this message to all Delivery offices
Subscribe to:
Posts (Atom)