Parcel Tracking functionality in standard SAP

1. Parcel Tracking, SAP Shantanu Dey

2. Main Concepts Provide name of a carrier in XSI Cockpit Express Delivery Cockpit (VTRC)carrier configuration and activation

3. Prerequisites

4. Functionality Scope

5. Configuration Steps XSI XML server can be used to load the data required for the Express Delivery Company Cockpit (Customizing data, master data, and documentation relevant for creating the necessary labels) into the SAP system RFC Destinationfield will use SAP business connector URL for connecting to XML server and downloading master data EDI can be used to load the same master data after maintaining the relevant mapping Master data can be entered manually Activate, assign service agent, activate for shipping point There should be at least one value in the Qualifier field to make direct database reference when entering metadata there must be at least one placeholder with qualifier TRACKN, SHIPACCT, XSISRVC, ROUTECODE, or PRDCD Once XSI cockpit is activated the parcel tracking tab along with parcel tracking data will appear in delivery and shipment transactions

6. Master data explanations Service Code - express delivery company-specific code that is printed on the label so that the express delivery company can deliver the parcel by the requested time. An example of a service code is: tomorrow before 8:00or overnight delivery We can derive service codes through special processing, shipping conditions, route, delivery priority Tracking Number - Unique no. for tracking shipments Can be set up via internal number range Shipper Account Number - The shipper account number is the sender's account number with the small parcel carrier We can define an external number in the control data Product code – similar to service code, depends on the carrier’s definition URLs – URL for business connector, URL for tracking status web page Different URL codes are used serving different purpose Tracking Status – Map the different status codes used by XSI to the status descriptions and information need of the customer Standard Carrier Alpha Code – Unique number assigned to each carrier for unique identification Assigned to vendor master

7. Business Process

9. The value determination can happen in a specified sequence.

10. A default value can be set for fields which are constant for a carrier (eg. Shipper’s account no.)

12. XSI Integration

14. The HTML view can be clicked from VTRK or the parcel tracking tab to get the status information

15. VTRKH is the main table containing information at individual tracking number and parcel level and VTRKP contains all the detail history

17. EDI 214/240 - Familiarity Partner must link to the XSI carrier through vendor assignment XSI incorporates four new segments in DELVRY0X IDoc E1EDL47 or header segment for XSI containing tracking number, account number, route code and other standard qualifiers XSITD or carrier code (identifying carrier), SHIPACCT or shipper’s account no, TRACKN or tracking no. PRDCD or product code etc. E1EDL48 or VLBL segment under E1EDL47 containing all meta data tags that have an external communication qualifier attached XSIQUALF or external communication qualifier and VLABDATA for qualifier value E1EDL49 under segment E1EDL37 for handling units, similar to E1EDL47 E1EDL50 under E1EDL49 and contains all segments of E1EDL48 IDocs can be transferred to an external system via “file” or “XML” ports. Typically, this type of transfer is to a local non-SAP system, such as an external EDI sub-system IDocs can also be sent to the SAP Business Connector, which provides services for routing, transporting and processing returned (inbound) IDocs to and from external non-SAP (or SAP) systems

19. Lacks the ability to print label format based on service label or destination of shipment