Parcel Tracking, SAP

Shantanu Dey

Main Concepts

Real Time Tracking

Track the path of individual deliveries or parcels that

were sent via express delivery

company like UPS or DHL or

Blue dart

Data Interchange

Exchange the necessary data with the express delivery company and ship-to parties e.g. EDI 214, XI

Print Labels if needed

Display Tracking Data Convenience

Show the data on Delivery or

Shipment->parcel

tracking tab

To activate parcel tracking tab,

configure XSI cockpit with the express

delivery company and activate the

same

Provide name of a carrier in XSI Cockpit

Express Delivery Cockpit (VTRC)carrier configuration and activation

Prerequisites

Important fields needed to be configured as metadata and master data for updating tracking information

• Tracking number, Tracking Status, Recipient Signature, Location, Date and Time

Set up partner profile with vendor no. and partner type LI if EDI is used for data interchange

Set up the basic IDOC type and message type and process code for inbound IDOC

Set up the outbound IDOC type for sending delivery information to carrier (SHOR output type with DELVRY03 IDOC type )

Functionality Scope

Metadata Update

• Any number of fields can be defined for each express delivery company in the metadata field definition. These fields are updated in SAP from express delivery company interface

• Metadata can be updated using standard and custom function modules

Metadata Definition

• Fields are defined with specific properties like number ranges• E.g. of standard fields TRACKN, SHIPACCT (senders’ account

no.) service code, product code, tracking status

Information Exchange

• We can use XML enabled RFC calls to talk to express delivery company’s server or we may use XI, Business Connector or EDI for data interchange

• Information flow can be two way, i.e. using same functionality and interface XSI can receive data

Status and Information Update

• We can use several express delivery companies by assigning them each to a different vendor

• Necessary information can be printed on the package label by XSI

• Parcel tracking status is set automatically and it is possible to view the web tracking status directly from SAP delivery or shipment document.

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 Destination field 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

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:00 or 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

Business Process

Delivery is packed into parcel, output type entered into header for IDOC output to XSI

Message comes back to SAP to populate tracking no, status etc.=

Labels often contain additional (bar-coded) information like routing codes or tracking

numbers etc. for fully automated sorting and dispatching in express carriers distribution

centers

Meta-Data

A set of tags which symbols the value determination attributes or properties

Tags are used as placeholders for creating data determination formulas

Can be assigned default values, no. range, qualifiers or fields or local FM

External meta data tag retrieval handled through BAPI at the moment of saving delivery or shipment

Tables used for storing data are VTRKH and VLBL

•Metadata can be re determined after initial value determination during saving of delivery or shipment based on configuration. •The value determination can happen in a specified sequence. •A default value can be set for fields which are constant for a carrier (eg. Shipper’s account no.)•Manual entry of value in Delivery or Shipment Document tab is possible

Master Data Configuration• Service Codes identify various levels of service provided by an express

carrier e.g. code for next day air service– Each service code can be assigned a service code group, e.g. air based services– We can map one of the following business document elements to service code

• Delivery priority, Shipping Condition, Route, Special Processing Indicator

– XSI includes certain functions to perform service code translation like – XSI_GET_SERVICE_CD_LPRIO, using delivery priority– Service code mappings can also be maintained manually in XSI

• XSI “Number Ranges” are used in the generation of tracking numbers and are based on standard SAP number range objects– Intervals must be created in VTRC under no. range tab

• Use of no. range can be restricted to a specific shipping point using meta data

• URL can be configured to identify the web server for accessing data for HTML based tracking or getting master data for RF-XML integration, also the logo can be displayed– URL type determines the utility of URL e.g. 04 for HTML based tracking

• Tracking status codes can be mapped to XSI provided tracking status e.g. A-picked up, C – Delivered

• Routing codes are carrier specific hub and distribution centre codes used for sorting, routing and label printing– May be determined by postal codes from and to or city and country– Is also determined by function XSI_GET_CARRIER_ROUTING

• Product Codes can be used to determine availability of additional services like Proof of Delivery. This is a custom implementation

XSI Integration

Automatic set up allows downloading a predefined

XSI configuration

Works in two modes – Remote System Test (Automatic) and Load all Master Data (Manual)

Automatic Config uses the RFC destination when invoking BAPIs.

For XML integration a URL should be provided

When non SAP button is selected XSI invokes each BAPI in test mode. Based on response tab

strips are filled or disabled.

Parcel Tracking (Delivery and Shipment Tab)

General Tracking information from carrier

Returned as a series of tracking items or events for each parcelEvent date and time, status, location, recipient and additional details

Additional Details

Detail information about statusException detailsRecipient signature can be viewed as a proof of deliveryIn all cases VTRKH is updated with status details and VTRKP with event details

Mechanism

Can be done using BAPI BAPI_CAR_PRVD_TRACK_STATUS Can be done through EDI, by calling web browser, by having HTML viewTracking information viewed in order, delivery, shipment and VTRK

•Double click on tracking number to get the status directly from carrier website along with tracking history•The HTML view can be clicked from VTRK or the parcel tracking tab to get the status information•VTRKH is the main table containing information at individual tracking number and parcel level and VTRKP contains all the detail history•VLBL is the database table for updating metadata qualifier and its value

Delivery Parcel Tracking Tab

Getting the HTML view of carrier’s website

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

Label Printing

Printing Label - Mechanism •Delivery or handling unit outputs, standard type KEP6, processing program R_XSI_LABEL_PRINT •From 4.6C from packing stations we can print labels

Label Text •The standard program contains generic SAP script form and carrier provided custom text element•The text element contains the label definition and SAP shipping document data fields in SAP Script format

Printer •Best suited for printer having command language protocol like EPL2 for generating bar code, position and format label content and generate graphics•OSS notes are available for configuring other types of printers

Several Limitations exist • Cannot support more than one label

format for one XSI carrier• Lacks the ability to print label format

based on service label or destination of shipment

• Cannot produce labels for different language

Thank You