Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel...
-
date post
19-Dec-2015 -
Category
Documents
-
view
214 -
download
0
Transcript of Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel...
![Page 1: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/1.jpg)
Intel’s Utilization of SAP*s Carrier Cockpit (XSI)
Session Code: 4304
Karri L. PaiceIntel Corporation
![Page 2: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/2.jpg)
Presentation Objectives• Awareness of how Intel is utilizing SAP* XSI
including:– express delivery company set up– carrier and tracking number assignment– carrier label printing– manifesting– communication with carrier systems (UPS and
FedEx) • Advantages of replacing a stand-alone
shipment manifesting system with native SAP* transportation execution functionality
• Challenges and key learnings of integrating SAP* XSI with decentralized WM
![Page 3: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/3.jpg)
Agenda
• Key Terms• History/Background• Drivers for Change• The Solution• Intel’s FGDSS Overview• Key XSI functionality and enablers• Benefits• Challenges• Lessons Learned
![Page 4: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/4.jpg)
Key Terms1. Express Ship Interface or XSI = SAP* capability
that allows for: – Carrier Cockpit set up– Label generation, manifesting, and PLD (package
level detail) upload from SAP*– Data transfer to and from an Idoc (SHPMNT04,
DELVRY03)– opportunity to track shipments from start to
finish (parcel tracking function)2. Express Carrier = small parcel carrier, e.g. UPS
and FedEx3. Freight Forwarder = LTL or generic carrier
![Page 5: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/5.jpg)
Key Terms (cont)4. FGDSS = Intel’s Finished Goods Domestic
Shipping Solution project; intro to XSI at Intel5. Shipment = a shipment document including
one or multi DNs; all DNs must have the same tracking #
6. Tracking # = AWB #, BOL #, Pro #; can be single DN or multi DNs per tracking #
7. Transportation Execution = SAP* functionality that includes reporting capabilities, Emailing auto-ship notifications, outputs, and AWB consolidation(More information on this topic can be found in the Intel presentation ‘Intel’s Utilization of SAP’s* Transportation Functionality’ – Session 4311, Wed. 5/21)
![Page 6: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/6.jpg)
History/Background Information
– Upgraded WMS to SAP 4.6b in 2000– Decentralized environment on 4.6c in
2002– Started looking at SAP* Transportation
Functionality in 2002 to replace…• Customized Interfaces between WM and
carrier systems• Several stand-alone or interfaced 3rd-party
transportation applications
![Page 7: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/7.jpg)
Drivers for Change
• Transition from legacy 3rd-party WMS to WM Decentralized
• Fragmented transportation solution (many interfacing and stand-alone systems)
• EOL of existing shipment manifesting application
• Intel moving towards SAP* as common core solution
![Page 8: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/8.jpg)
The Solution
• Replace our stand-alone shipment manifesting application with native SAP* functionality
• Integrate SAP* XSI with SAP* Transportation Functionality and Decentralized WM 4.6c
![Page 9: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/9.jpg)
Intel’s FGDSS Overview
• In Scope – US origin shipments– Finished Goods Shipments– Express carrier shipments
• UPS domestic• Fed Ex domestic and international
– Freight forwarder domestic and international shipments
![Page 10: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/10.jpg)
Intel’s FGDSS Overview (cont)
• Out of Scope – Non-US origin shipments– Non-finished goods– Shipper’s Export Declaration (SED) data to
carrier interfaces and Automated Export System (AES)
– Low volume shipment carriers
![Page 11: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/11.jpg)
Key XSI Functionality & Enablers• Carrier Cockpit set up• Begin Shipping Period• Carrier Assignment• Freight Payment Term Assignment• Service Level Assignment• Tracking # Assignment• Carrier Documentation
– Labels– BOL, AWB– Manifests/Shipment summaries
• End Shipping Period• Communication with Carrier Systems
![Page 12: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/12.jpg)
Carrier Cockpit set up (VTRC)• Some prerequisites to enabling the cockpit
functionality– Determine to what level packages will be
tracked by express delivery company (carrier)
Note: 8 = shipment levelJ = DN levelX = box level
![Page 13: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/13.jpg)
Carrier Cockpit set up (cont)
– Configure express delivery companies– Define tracking # format and ranges (i.e. by
plant) per express delivery company– Define service levels per express delivery
company– Assign freight payment terms per express
delivery company– Assign shipper account # (i.e.by plant) per
express delivery company
![Page 14: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/14.jpg)
Carrier Cockpit set up (cont)
• Carrier Cockpit: tracking #’s by carrier
![Page 15: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/15.jpg)
Carrier Cockpit set up (cont)
• Carrier Cockpit: tracking #’s by carrier
![Page 16: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/16.jpg)
Carrier Cockpit set up (cont)
• Carrier Cockpit: Service levels by carrier
![Page 17: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/17.jpg)
Begin Shipping Period (VT01n/VT04)
• Begin a shipping period by creating a Shipment Document (VT01n for single shipment docs; VT04 for multiple shipment docs)
![Page 18: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/18.jpg)
Carrier Assignment (VL02n)
• Carrier and tracking number assignment using the carrier cockpit and systematic triggers
– Express carrier tracking # assignment by box/package
– Freight forwarder tracking # assignment by shipment
Note: VL02n is being used for express carriersVT02n is being used for freight forwarders
![Page 19: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/19.jpg)
Carrier Assignment (cont)
1) Assign forwarding agent (carrier) > Save
![Page 20: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/20.jpg)
Freight Pay Terms (VL02n)
2) Assign freight pay terms >
![Page 21: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/21.jpg)
Service Level Assignment (VL02n)
3) Assign service level > Save >
![Page 22: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/22.jpg)
Tracking# Assignment (VL02n)
4) Save triggers tracking # assignment
![Page 23: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/23.jpg)
Carrier Documentation
• Carrier label printing via HUPAST which uses SAP Forms* and systematic triggers/user exits– Labels print by highest level handling unit– Native and built-in error messages– Reprinting functionality, as an exception
![Page 24: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/24.jpg)
Label Printing (HUPAST)
![Page 25: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/25.jpg)
Carrier Labels
![Page 26: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/26.jpg)
End of Shipping Period docs
• UPS Summary label in place of manifest• FedEx using manifest generated automatically
from FedEx server• Freight forwarders using BOL copies; no manifests
![Page 27: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/27.jpg)
End of Shipping Period (VT02n)
• Generation of end-of-shipping-period carrier documentation using systematic triggers
Shpment completion triggers UPS summary label and FedEx upload
Shipment start triggers Goods Issue for all shipments and UPS PLD upload
Check-in triggers BOL for freight forwarders
![Page 28: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/28.jpg)
End of Shipping Period (cont)• All DN’s for same shipping period, transportation
planning date, carrier, Ship-To party, etc. are consolidated onto one shipment document
![Page 29: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/29.jpg)
Communication with carrier systems• UPS
– Intel built standard interface to communicate outbound• using UPS’ SPF7 guidelines• UPS has standard process for creating PLD
upload interface
– Direct connection to UPS production server• PLD upload directly to UPS at end of
shipping period• HTTPS used for data transmission
![Page 30: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/30.jpg)
Communication with carrier systems (cont)• FedEx
– Created a middleware program to communicate with on-site FedEx Ship Manager Server
– Connection to local FedEx server • Generates carrier labels to dedicated local
printer• Initiates end-of-period upload to FedEx server• Data transmission to FedEx mainframe via
modem
• All other carriers– No special requirements– No interfaces in or out
![Page 31: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/31.jpg)
Some Benefits
• One system vs. many allows for integrated supply chain visibility
• Standardized cross-warehouse business processes
• Transportation tasks occur earlier in the order fulfillment process providing more effective transportation execution
• Able to utilize our existing capabilities vs. investing in another system/solution
![Page 32: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/32.jpg)
Some Challenges
• Limited industry use and limited experienced resources
• Integrating Decentralized WM with XSI • Inconsistent express carrier requirements
and standards
![Page 33: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/33.jpg)
Some Lessons Learned
• Project was more complex than initially anticipated– limit scope to ensure the foundation is built– add incremental capabilities (i.e. new carriers,
new service levels, etc) later
• Strong relationships with carriers are essential– Drive for standard interface solutions
• Enable SED capabilities up front• Intel as 3rd party to freight forwarders
![Page 34: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/34.jpg)
Questions
![Page 35: Intel’s Utilization of SAP*s Carrier Cockpit (XSI) Session Code: 4304 Karri L. Paice Intel Corporation.](https://reader031.fdocuments.us/reader031/viewer/2022032309/56649d265503460f949fcf15/html5/thumbnails/35.jpg)
Thank you for attending!Please remember to complete and return your evaluation form following this session.
Session Code: 4304
For further questions contact:
Karri Paice
*SAP and other names and brands may be claimed as the property of others.