Solution Postman 7.9 RL Invoicing
Issues:
In Some Office, While invoicing RL in latest Postman 7.9 , the below error Occurring
Solution:
- Download two exl from PoTools Given by CEPT, Mysore.
- Execute it Once through script tool.
Saturday, 1 March 2014
Postman 7.9 Registered article Invoicing Issues and Solution
Solution for Treasury HO Summary Timeout Expired
Treasury Timed out Expired
Solution
The error message will appear if there is huge data in the database.
Therefore, it is suggested in Meghdoot Treasury user manual that the
treasury supervisor has to delete the old data periodically. This may
not be followed in your office causing the error.
To solve the problem, delete the old data through the option
Treasury > Supervisor > Tools > Delete
-up to the required date.
The data may be deleted in piece meal ie; month wise only from the
oldest date of data available in the database after following the
prescribed procedure ie; taking backup in any other device, approval of
the Divisional Office etc., With this Option, data pertaining to
Treasury, subtreasury, SubAccounts, BOSubaccounts databases will be
deleted up to the required date.
Don't try to delete the data in one step ie; in bulk - it will give
"Timeout Expired" error message. This will solve the problem.
Patch for Despatch 7.9 String or Binary data would be truncated
String / Binary data would be truncated in Despatch 7.9
In some office, while fetch postman returned article in Despatch Module,
it shows an error message as String or binary data would be truncated.
so that we could not fetch even a single article from Postman to
despatch Module.
above error message shown while fetch RTS - COD article because of more than 30 characters available in Addressee Name.
Solution
Actually this is not an solution. A small patch was developed by admin,
PoTools to find out the COD article having more than 30 characters in
Addressee Name.
- Download attached Patches from PoTools
- Check whether length of COD Article addressee name more than 30 characters.
- If More than 30 Character exist, kindly take up this issue to CEPT, Mysore for solution.
Download
Download
DELIVERY PROCESS OF COD ARTICLES
DELIVERY PROCESS OF COD ARTICLES
BAG RECEIVING
BAG RECEIVING
OPEN POSTMAN MODULE -> LOGIN WITH USER -> INVOICING-> PARCEL-> BAG RECEIVING-> OK -> BAG NUMBER (RBJ00000000IN) -> OFFICE OF DESPATCH (PH GOMOH)-> OK-> CLOSE.
BAG OPENING
OPEN POSTMAN MODULE -> LOGIN WITH USER -> INVOICING-> PARCEL-> BAG OPENING -> ENTER BAG NUMBER ->
PRESS ENTER KEY -> SELECT ARTICLE TYPE—BPCOD -> ENTER ARTICLE NUMBER -> OK -> YES -> CLOSE.
CASES
CASE 1: - FOR ARTICLE INVOICING TO BEAT
OPEN POSTMAN MODULE -> LOGIN WITH USER -> INVOICING-> COD
ARTICLES -> ARTICLE FOR DELIVERY -> POST SORTING -> SELECT THE
BEAT NUMBER -> FETCH -> ARTICLES SELECT -> OK
CASE 2: - FOR PRINT DELIVERY SLIP OF POSTMAN
OPEN POSTMAN MODULE -> LOGIN WITH USER -> DELIVERY SLIP ->
SELECT BEAT -> SELECT ARTICLE -> OK -> FILE ->
PRINT.
CASE 3: - TAKE RETURN OF POSTMAN IF COD ARTICLES DELIVERD
OPEN POSTMAN MODULE -> LOGIN WITH USER -> RETURN -> COD
ARTICLES -> BEAT NUMBER SELECT -> FETCH -> ARTICLE NUMBER
SELECT -> FINISH.
THEN
OPEN TREASURY MODULE -> LOGIN WITH USER -> RECEIPTS -> POSTMAN
RETURN -> SELECT POSTMAN & BEAT ->OK ->ENTER AMOUNT ->
FINISH -> CLOSE.
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TREASURY -> SUBMIT ACCOUNT -> POSTMAN -> SELECT BEAT -> OK.
CASE 4: - TAKE RETURN OF POSTMAN IF COD ARTICLES RETURN TO SENDER SAME DAY
OPEN POSTMAN MODULE -> LOGIN WITH USER -> COD ARTICLE ->BEAT
NUMBER -> FETCH -> ARTICLE NUMBER SELECT -> GIVE REMERK ONLY
& ONLY ABSENT NOT FOUND -> UNDELIVERED -> FINISH ->
CLOSES.
THEN
OPEN POSTMAN MODULE -> LOGIN WITH USER -> WINDOW DELIVEY -> COD
ARTICLE -> SELECT THE ARTICLE -> UNCLAIMED -> OK -> CLOSE.
(THEN WE HAVE ABLE TO CLOSE COD ARTICLE BAG IN DESPATCH MODULE WITH OPTION FETCH FROM POSTMAN)
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TREASURY -> SUBMIT ACCOUNT -> WINDOW-> OK.
CASE 5: -FOR TAKE RETURN IF COD ARTICLE NOT DELIVERED SAME DAY & DEPOSIT FOR 1 TO 7 DAY
OPEN POSTMAN MODULE -> LOGIN WITH USER -> COD ARTICLE ->BEAT
NUMBER -> FETCH -> ARTICLE NUMBER SELECT -> GIVE REMERK ONLY
& ONLY ABSENT NOT FOUND -> UNDELIVERED -> FINISH ->
CLOSES.
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TREASURY ->
SUBMIT ACCOUNT-> SELECT BEAT ->OK-> CLOSE. (NOTE: - AFTER THIS
PROCESS RELATED COD ARTILCES ADDED TO WINDOW DEPOSIT & TRAETED AS
WINDOW DEPOSIT ARTICLE)
CASE 6 : - IF COD ARTICLES DELIVERED AFTER 1 TO 7 DAYS IN WINDOW DELIVERY OPTION
OPEN POSTMAN MODULE -> LOGIN WITH USER -> WINDOW DELIVEY -> COD
ARTICLE -> SELECT THE ARTICLE -> DELIVERED -> OK -> CLOSE
THEN
OPEN TREASURY MODULE -> LOGIN WITH USER -> RECEIPTS -> POSTMAN
RETURN -> WINDOWS ->OK ->ENTER AMOUNT -> FINISH ->
CLOSE.
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TREASURY -> SUBMIT ACCOUNT -> WINDOWS -> OK-> CLOSE.
CASE 7 : - IF COD ARTICLES RETURN TO SENDER AFTER 1 TO 7 DAYS IN WINDOW DELIVERY OPTION
OPEN POSTMAN MODULE -> LOGIN WITH USER -> WINDOW DELIVEY -> COD
ARTICLE -> SELECT THE ARTICLE -> UNCLAIMED -> OK -> CLOSE.
(THEN WE HAVE ABLE TO CLOSE COD ARTICLE BAG IN DESPATCH MODULE WITH OPTION FETCH FROM POSTMAN)
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TREASURY -> SUBMIT ACCOUNT -> WINDOW-> OK.
CASE 8: - FOR ARTICLE INVOICING TO BEAT IF MASSEGE GIVE NO ARTICLE FOUND
OPEN POSTMAN MODULE -> LOGIN WITH USER -> INVOICING-> COD
ARTICLES -> ARTICLE FOR DELIVERY -> POST SORTING -> SELECT THE
BEAT NUMBER -> FETCH -> MASSEGE GIVE NO ARTICLE FOUND -> OK
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TOOLS ->
REQUEST RESEND PARCEL COD Booking DATA -> ARTICLE SELECT -> SEND
REQUEST ->THEN RUN R NET COMMUNICATION -> OK -> CLOSE
(NOTE: - NEXT REQUEST SEND AFTER 50 MINUTE) AFTER RECEIVED FILE THROUGH R
NET COMMUNICATION FROM CENTRAL SERVER POSTMAN USER ABLE TO INVOICING
THE COD ARTILCE TO BEAT OR B.Os.
CASE 9: - FOR ARTICLE INVOICING TO BOs
OPEN POSTMAN MODULE -> LOGIN WITH USER -> INVOICING-> COD
ARTICLES -> TO BOs -> SELECT B.O -> FETCH -> SELECT ARTICLES
-> OK.
CASE 10: - FOR PRINT DELIVERY SLIP OF B.Os
OPEN POSTMAN MODULE -> LOGIN WITH USER -> REPORTÃ COD ARTICLES -> TO BOs -> SELECT B.Os -> OK -> PRINT.
CASE 11: - TAKE RETURN OF B.Os IF COD ARTICLES DELIVERD
OPEN POSTMAN MODULE -> LOGIN WITH USER -> BO REMARKS -> COD
ARTICLES -> SELECT B.O -> FETCH -> SELECT ARTICLE ->REMARK
DELIVERED ->OK ->FINISH.
(NOTE: - TAKE RETURN OF COD ARTICLE AFTER DATA ENTRY IN SUB ACCOUNTS TO CONCERNED BO UNDER HEAD BPCOD Collection.)
THEN
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TREASURY -> BO
CODs VERIFICATION -> SELECTS B.O-> FETCH->SELECT ALL ->OK.
CASE 12: - TAKE RETURN OF B.Os IF COD ARTICLES RETURN TO SENDER
OPEN POSTMAN MODULE -> LOGIN WITH USER -> BO REMARKS -> COD
ARTICLES -> SELECT B.O -> FETCH -> SELECT ARTICLE ->REMARK
RETURN TO SENDER ->OK ->FINISH.
(THEN WE HAVE ABLE TO CLOSE COD ARTICLE BAG IN DESPATCH MODULE WITH OPTION FETCH FROM POSTMAN)
CASE 13: - COD ARTICLE DESPATCH PROCESS IF COD ARTICLES ARE MISSENT
OPEN POSTMAN MODULE -> LOGIN WITH USER -> INVOICING-> COD
ARTICLES -> MISSENT REDIRECTION FOR COD ARTICLES->ARTICLE
SELECT->MISSENT REDIRECT->OK->CLOSE
(IF FILE OF MISSENT COD ARTICLE NOT FOUND IN THIS OPTION THEN APPLY THIS PROCESS=
OPEN POSTMAN MODULE -> LOGIN WITH SUPERVISOR -> TOOLS ->
REQUEST RESEND PARCEL COD Booking DATA -> ARTICLE SELECT -> SEND
REQUEST ->THEN RUN R NET COMMUNICATION -> OK -> CLOSE)
-------------------------------------------------------------------
NOTE:
1.CLOSE THE BAG IN DESPATCH MODULE UNDER BAG TYPE PARCEL
1.CLOSE THE BAG IN DESPATCH MODULE UNDER BAG TYPE PARCEL
2. RECEIVE THE COD ARTICLE IN DESPATCH MODULE UNDER OPTION: - RECEIPTS-> FETCH FROM POSTMAN
3. RUN E PAYMENT CLIENT COMMUNICATION TO SENT CASH COLLECT DATA
4. RUN RNET COMMUNICATION FOR SENT & RECEIVED COD BOOKING DATA
Prepared by:-
Avinash Kumar
System administrator
Bermo S.O, 829104
+919471512546
Subscribe to:
Posts (Atom)
