Decentralization of Beat EOD in SAP at Divisional Level - Operating Procedure

Respected All,

This is regarding handling of Beat EOD issues at DPMS (postman) module at Divisional level.


While observing the tickets raised at DPMS module, it is noticed that majority of the tickets were raised for non completion of beat eod at delivery post office dpms module and closing the day which is impacting data availability for accounting and tracking systems in CSI.


To overcome, detailed SOP for Beat EOD Insert has been prepared to handle the same at divisional level to provide immediate solution. No need to raise ticket for this in service desk by delivery post office.


Key summary of Beat EOD Summary is as follows:


(1) In DPMS module, this issue will arise when delivery PA takes returns without giving EOD to particular Beat and perform day end.(due to various reasons).

(2) Delivery Post office to inform the same to Divisional office with screenshot of the activity (mentioned in SOP) along with Facility ID/Beat ID/Date of error.

(3) Divisional office on receipt of the error screen shot from PO, they can verify the genuine and execute the Tcode ZMO_EOD_INSERT @ SAP for particular office to complete the EOD process and inform PO .

(4) By executing the tcode and fixing the issue, it may be noted that Financial posting of EMO/ Value article such as COD,VPP, CD articles will not be accounted. Liability document in respect to COD article will not generate and payment cannot be made to the biller by payment office.(This can be solved through raising ticket to TCS DPMS Team).

Hence, All delivery post offices may please be instructed to complete the EOD process for all the beats without fail so that they can avoid above process.

Necessary instructions may please be circulated to all. SOP can also be downloaded from https://utilities.cept.gov.in//csi/ .

 

DOWNLOAD STANDARD OPERATING PROCEDURE FOR BEAT EOD AT DIVISIONAL LEVEL