Posted on 1 Comment

Draft SOP in c/w Handling PLI / RPLI Maturity Claim Cases

Draft SOP in c/w Handling PLI / RPLI Maturity Claim Cases for inputs of Circles

Click Here to view Annexure – I
 Click Here to view Annexure -II
 Click Here to view Annexure – III
 Click Here to view Annexure – IV
 Click Here to view Annexure – V
 Click Here to view Annexure – VI
 Click Here to view Annexure – VII
Posted on 1 Comment

USER GUIDE ON CONFIGURATION OF WEIGHING SCALE IN POS || CSI SOP

Standard Operating Procedure for connecting weighing Scale with POS Application in CSI environment

Step 1: Connect the Weighing Scale to Client / Server machine used for Counter activities
Step 2: Go to Postal Back Office and select the option “Counter Configuration” menu “Configuration”

Step 9: Go to C drive – POS – Application – Counter – build – conf_comm – properties folder and open
the properties file ” weighingScale.properties” using Note Pad application

Step 10: The file content will be as shown below:

 COM_PORT_USED=COM1
BAUD_RATE=9600
DATA_BITS=8
PARITY=0
STOP_BIT=1
FLOW_CONTROL=0
MUL_FACTOR=1000
WEIGHING_MC_TYPE=E

Step 11: The configured values need to be changed according to the Weighing Machine viz.,
BAUD_RATE=2400 etc. and Save the file.
Posted on Leave a comment

Procedure for renewing the despatch schedule – SOP

Here is the procedure for renewing the despatch schedule
The procedure for renewing the Dispatch schedule is as below:-
1.       Divisional SPOC has to login to the PTM module in SAP using Super-user credential shared during creation of dispatch schedule.
2.       Go to  “Edit Schedule” option under Schedule tab to get the schedule editing screen. 
3.       Enter the Schedule ID for which validity has to be extended.
4.       Change the “Valid to” date as required and save the same.
5.       Login to ECP module of SAP using Divisional head login and download the edited schedule using “ZMOSCHDWNLD”
6.       Maintain the edited schedule under “ZMOIPVS” option.
7.       After completion of all the above task, Share the schedule ID to  tcsdop.sapipvs@tcs.com and tcsdop.pos@tcs.com with a copy of DMCC Chennai, RIT and CIT for pushing the edited schedule data to IPVS Back office.
In this connection, it is requested to direct all the Divisional SPOC to renew the dispatch schedules well in advance  before the expiry date to avoid the issues in dispatching the articles in IPVS Back Office.
Posted on Leave a comment

CSI COD Front Ending Standard Operating Procedure Ver. 2.0 || By CEPT-DPMS

What’s New in Ver 2.0 >>> 
image search result for CSI COD Front Ending SOP

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.