1011 End to End Tracking SAP PI

]Orange County Convention CenterOrlando, Florida | May 15-18, 2011

P&G's global B2B Integration with SAP-PI Tracking B2B messages End-to-End with SAP-PI and SAP-ECC

Jan HoffmannGlobal Application Manager

Shelf-to-Cash OA/EDIProcter & Gamble

Real Experience. Real Advantage. Jan Hoffmann - P&G - Session 1011

[

Objective | Learning Points

Learn more about the importance of EDI End-to-End tracking

Discover ways how to provide B2B status information to business

Understand the complexity of EDI End-To-End Tracking


[

Condensed Profile - Jan Hoffmann

1991 - Continental Tires AG - Hannover (Germany) Consultant for B2B Integration (VDA, EDIFACT, ...) and BPO SAP-R/3 SD Integration for Continental AG allied companies

2000 - Gillette - Boston; Kronberg / Frankfurt (Germany) B2B / SAP-SD Rollout in Nordic Region (DK, NO, SE, FI) and Great Britain Integration of external customer via EDI (X12, EDIFACT, TRADACOM)

2005 - Procter & Gamble - Cincinnati; Schwalbach / Frankfurt B2B / SAP-SD consolidation in Russian Federation (Moscow) Integration of external Warehouse Management Systems via EDI current: Global Application Manager Team Lead for Order Acquisition / EDI


[

Agenda

Introduction / Background

Overview of End-to-End Tracking

Deep Dive into P&G End-to-End Tracking Solution

Summary / Conclusion


[

About Procter & Gamble

P&G at a Glance Founded 1837 Headquarters in Cincinnati $78.9 Billion annual sales 127,000 employees More than 300 brands sold in 180 countries Operations in more than 80 countries

William Procter

James Gamble


[

B2B Communication in Procter & Gamble

Technical Structure Redundant / high available and global EDI infrastructure Regional SAP-ECC 6.0 - SAP-PI 7.1 with Seeburger BIC

B2B Communication, EDI Standards B2B data communication via AS2 and VAN provider EDI standards: X.12, EDIFACT, TRADACOM, GS1-XML

Document Volumes Worldwide over 5 million annual customer EDI messages Typical Messages: 850 / ORDERS; 856 / DESADV; 810 / INVOIC ...


[

EDI Processing in P&G with SAP-PI

CIB Cyclone

EDI

EDI

IDoc

SAP-PI 7.1:Production System with Seeburger BIC [and AS2 Adapter]

SAP-ECC:APAC

SAP-ECC:LA

SAP-ECC:NA

SAP-ECC:EMEA

IDoc IDoc IDoc

CustomerEDI

AS2

ECC

PI


[

Agenda






[

Business benefits and needs for B2B Tracking

Data Retrieval and Data Access Search for business documents with processing status Display of EDI content (payload)

Support / Reporting Extended status overview for EDI and IDoc processing Effort reduction to monitor in SAP-PI and across platforms Determine EDI volumes (interchanges, messages, size) - with peaks

Legal / Archiving Documentation End-to-End status (eg. EDI confirmation from customer) Provide interface for long-term archiving with meta information


[

User of EDI Tracking

Business Solving customer requests User friendly display of SAP IDocs and EDI data

Support / Application Management Automated alert management for SAP-PI (mappings with error) Automated alert management for SAP-ECC (IDocs with error) Statistical evaluations for system improvements

Management Provide KPI figures (Key Performance Indicator) about processes


[

Tracking Options: Overview

SAP-PI: Existing monitoring components in SAP-PI Track via Adapter / Integration or Business Process Engine Individual Alert Management (eg. CCMS)

SAP-ECC: IDoc Status Management in SAP-ECC Usage of SAP-PI Acknowledgement Status back to ECC

Seeburger Message Tracker Seeburger Add On for Status Tracking in SAP-PI

Applications of external suppliers External Application to monitor EDI data


[

Tracking Options: SAP-PI Integration Engine


[

Tracking Options: SAP-PI Adapter Engine


[

Tracking Options: EvaluationSAP-PI: Monitoring components in SAP-PI No systematic search / log files are not long-term available E2E status can't easily determined for complex errors (ccBPM)

SAP-ECC: IDoc Status Management in SAP-ECC Not available for non-IDocs management (eg. proxy or flat files) No End-to-End status tracking till Adapter Engine

Seeburger Message Tracker No End-to-End status tracking till SAP-ECC Low performance for high data volumes

Applications of external suppliers High implementation effort No End-to-End status tracking from Adapter Engine till SAP-ECC


[

Complexity of Inbound EDI Tracking

EDI interchanges may contain multiple EDI messages 1 interchange may contain multiple messages (eg. in-850) EDI messages may be rejected in case of incorrect structure

EDI messages may be sent to non-SAP systems Consideration of messages which don't create SAP-ECC IDocs

Processing of inbound Acknowledgements MDN, in-997, in-CONTRL,... updates outbound document status


[

Complexity of Outbound EDI Tracking

EDI interchanges may contain multiple EDI messages 1 interchange may contain multiple messages (out-810) Consideration of ccBPM processes for message consolidation

Processing of outbound Functional Acknowledgements Creation of out-997 and out-CONTRL acknowledgements


[

Agenda






[

P&G End-to-End Tracking: Inbound EDI

EDICIB Cyclone

Customer

EDI

EDI

SAP-PI: transfer from UNIX store EDI raw data split EDI data / mapping create 997 / CONTRL process MDN confirmation

status updatesIDoc

SAP-ECC: IDoc processingECC

PI


[

P&G End-to-End Tracking: Outbound EDI

SAP-ECC: IDoc processing

EDI

MDN

CIB Cyclone

EDIMDN

EDI

MDN

status updates

SAP-PI: ccBPM (optional) message mapping store EDI raw data file transfer to UNIX

IDoc

Customer

ECC

PI


[

P&G End-to-End Tracking: Components

SAP-ECC: Collect and consolidate status information IDoc table for generated and received IDocs

SAP-PI: Generate status information for SAP-ECC Integration Engine (Message Mapping) Adapter Engine (Communication Channel)

External: Provide status information for End-to-End-Tracking AS2 Software with AS2-MDN (Message Delivery Notification) Customer acknowledgements (in-997, in-CONTRL, ...)


[

P&G End-to-End Tracking: Components

ECC

PI

Stored EDI DataUNIX NFS

IDoc Payload

End-to-End Tracking Status Information

Temporary Storage of PI Processing Status

Cyclone

Customer

ZEDITRACK

EDI Payload Status Information

IDoc Information

Tracking-DB

IDoc-Database

AS2-MDN

SAP PI Status DB

in-997, in-CONTRL, -in-APERAK

MessageMapping

Comm-Channel


[

P&G End-to-End Tracking: Architecture

Status IDocPayload IDoc

SMT-DBINSERT /

UPDATE

UPDATE /

DELETE

INSERT

/sapmnt//global/Seeburger/...Folder for CIB data transfer

SAP-ECC:IDoc status

processing

INSERT /

UPDATE

UNIX NFS

INSERT /

UPDATE

ETR-DB

EDIDC

ECC

PI

ZEDITRACK

SAP-PI:Message Mapping(EDI vs. IDoc)

Seeburger/FileStore

SAP-PI:Status processing(IDoc ZSYSTAT1)

SAP-ECC:IDoc PayloadProcessing


[

Process scenarios for EDI

Inbound EDI (Customer to P&G) 1 Interchange Multiple Messages 1 Interchange ccBPM Consolidation 1 Interchange 1 Output File

Outbound EDI (P&G to Customer) 1 IDoc 1 Message 1 Interchange n IDocs n Messages 1 Interchange 1 IDoc n Messages 1 Interchange


[

Inbound EDI: 1 Interchange Multiple Messages

SAP-PI

SAP-ECC

Cyclone

...

...

IDoc created

Seeburger Splitter

IDoc created

EDI mapping (in)map1 run

map1 end

file adapter

CustomerCIB

file adapter


map1 end

Ext. System


map1 end

...

FncAcknowlegement

map1 end

map1 run

file adapter

AS2-MDN

61

63

51

66

64

72

91

71

81

62

65


[

Inbound EDI: 1 Interchange ccBPM Consolidation

SAP-PI

SAP-ECC

Seeburger Splitter

IDoc created

file adapter

CIB


map1 endExt. System

FncAcknowlegement

map1 end

map1 run

file adapter

61

63

51

91

71

62

ccBPM...

Cyclone CustomerAS2-MDN81


[

Inbound EDI: 1 Interchange 1 Output File

SAP-PI

SAP-ECC

file adapter


map0 end

Ext. System

CIB

file adapter

51

73

66

64

65

Cyclone Customer


[

Outbound: 1 IDoc 1 Message 1 Interchange

SAP-PI

SAP-ECCIDoc created

IDoc sent

file adapter

EDI mapping (out)map1 end

map1 run

Ext. System

CIB

11

12

31

24

26

25

Cyclone CustomerAS2 MDN41


[

Outbound: n IDocs n Messages 1 Interchange

SAP-PI

SAP-ECC...

...

...

IDoc created

ccBPM Queue

IDoc created

IDoc sent

multi mapping

map1 end

map1 run

file adapter

IDoc sent

multi mapping

map1 end

map1 run


map9 run

Ext. System

CIB

11

12

21

23

24

26

31

22

25

Cyclone CustomerEDI file41


[

Outbound: 1 IDoc n Messages 1 Interchange

SAP-PI

SAP-ECC

Ext. System

CIB

IDoc created

IDoc sent

file adapter


map1 run

11

12

31

24

26

25

Cyclone CustomerAS2-MDN41


[

P&G Tracking Solution - Selection Screen I


[

P&G Tracking Solution - Selection Screen II


[

P&G Tracking Solution - Main Overview Screen


[

P&G Tracking Solution - Payload Display


[

Agenda






[

Key features and advantages of P&G Tracking Solution

Very user friendly SAP-ECC solution for end- and key-user Extended reporting of SAP-IDoc errors (eg. IDoc ORDERS) Customized display of SAP-IDocs (can be defined by user)

Generation of consolidated reports overviews with drill down Automated distribution of user customized reports by mail Customized alert management to any iPhone or cell phone

Conversion of technical sender/receiver ids to name / group / country Supported search of multinational customer cooperation Extended master data maintenance (eg. EDPAR, EDSDC)

Central reporting of all errors during conversion and communication Central storage and display of all exchanged EDI data Export to archiving solution "TRIM" for long-term archiving


[

Best Practice (Technical Implementation)

Select reliable status sources EDI Tracking should not rely only on system log-files Consider non-time-sequential processing events Use well-defined correlations for processes chains (GUID)

Be flexible and open for enhancements Build an open framework for process enhancements (eg. new ccBPM) Use enhancement opportunities eg. for IDoc processing


[

Key Learnings (Executive Summary)

Importance of EDI End-to-End Tracking for P&G Ensure all EDI documents are processed (orders, invoices) Avoid loss of NOS due to lost or delayed EDI documents

B2B status information for business in P&G Different functional teams use EDI Tracking Solution for daily work A user friendly GUI ensures high user satisfaction and reduces effort

Need for P&G to develop a custom EDI Tracking Application No standard EDI Tracking application exists for SAP-ECC / SAP-PI Status information are consolidated from ECC, PI and other provider


[

Q&A - Thank you for your Attention!

Session Code1011


Jan HoffmannGlobal Application Manager Team Lead for Order Acquisition / EDIProcter & [email protected]://linkedin.com/in/hoffmann7


[

]Thank you for participating.SESSION CODE: 1011


Please remember to complete and return your evaluation form following this session.

For ongoing education in this area of focus, visit www.asug.com.


[

P&G Supported EDI Standards for B2B

X12 - ANSI / VICS / UCS (United States, Canada): Regional EDI format for US/CA; very high standardization

ISA*00* *00* *12*2562379521 *01*067429365 *990225*0930*U*00401*000000005*0*P*>'

EDIFACT / EANCOM (United Nations): Worldwide established EDI Standard for B2B communication

UNB+UNOA:3+9313938000631:ZZ+9331849499994:ZZ+060829:1141+2++++1++1'

TRADACOM (Great Britain): Regional EDI format UK, similar to EDIFACT standard

STX=ANA:1+5015715444440:ASDA+5050085097067:ABER+090825:190940+1569+YFBA+ORDHDR'

GS1-XML (Global Standard 1; former EAN / CCG): Successor for EDIFACT / EANCOM (currently not broadly used)


[

Sample for X12 order: 850ISA*00* *00* *12*2562379521 *01*067429365 *990225*0930*U*00401*000000005*0*P*>'GS*PO*2562379521*067429365*19990225*0930*000000051*X*004010VICS'ST*850*000000001'BEG*00*SA*105073**19990223'REF*IA*43520'REF*DP*51'CSH*P4'ITD*01*3*0**30*00000000*0'DTM*037*19990224'DTM*002*19990224'DTM*063*19990311'TD5**92***SHIPPING GUIDE'N1*ST**92*970'N1*BT**92*000'PO1**3*EA*2.98*WE*UP*012036200774'CTP**RES*5.95'SDQ*EA*92*001*3'PO1**3*EA*2.98*WE*UP*012036126722'CTP**RES*5.95'SDQ*EA*92*001*3'CTT*36*309'SE*122*000000001'GE*1*000000051'IEA*1*000000005'

Source: Internet(no P&G data)


[

EDI Structure for X12 (ANSI, UCS, VICS)ISA Interchange Control Header

GS Functional Group Header

ST Transaction Set Header Transaction Segments

SE Transaction Set Trailer

GE Functional Group Trailer

IEA Interchange Control Trailer


[

Sample for EDIFACT order: ORDERSUNB+UNOA:3+9313938000631:ZZ+9331849499994:ZZ+060829:1141+2++++1++1'UNH+2+ORDERS:D:01B:UN:EAN010'BGM+220+R-06228A+9'DTM+137:20060829:102'DTM+2:20060906:102'NAD+BY+9313938000631::9'NAD+ST+9315GR::92'NAD+SU+156001::92'LIN+1++9314250041845:EN'QTY+21:15'DTM+15:20060912:102'PRI+1E:9.9'LIN+2++9356452341123:EN'QTY+21:30'PRI+1E:11.9'LIN+3++9123456741329:EN'QTY+21:20'PRI+1E:6.9'LIN+4++9314250987654:EN'QTY+21:10'PRI+1E:9.5'UNS+S'MOA+86:961'CNT+2:5'UNT+24+2'UNZ+1+2'



[

EDI Structure for EDIFACT (EANCOM)UNA Service String Advice UNB Interchange Header

UNG Functional Group Header

UNH Message HeaderMessage Segments

UNT Message Trailer

UNE Functional Group Trailer

UNZ Interchange Trailer


[

Sample for TRADACOM order: ORDERSSTX=ANA:1+5015715444440:ASDALTD+5050085097067:ABERGAVENNY+090825:190940+1569+YFBA+ORDHDR'

MHD=1+ORDHDR:9'

TYP=0350+PROP-ORDERS'

SDT=:813266740+ABERGAVENNY FINE FOODS LTD.'

CDT=5015715444440+ASDA STORES LTD'

FIL=0235+1+090825'

MTR=6'

MHD=3+ORDERS:9'

CLO=5055023772408+ASDA 7424+STAITHES ROAD:PATTINSON INDUSTRIAL:WASHINGTON::NE38 8NW'

ORD=PLAN223926::090827++P'

DIN=090828+++0'

OLD=1+5050854479878++:007415144+8+3'

OLD=2+5050854619809++:007415571+6+6'

OLD=3+5050854980961++:007417902+12+1'

OTR=3'

MTR=9'

MHD=65+ORDTLR:9'

OFT=63'

MTR=3'

END=5'



[

EDI Structure for TRADACOMSTX Interchange Header

MHD Message HeaderMessage (like ORDHDR)

MTR Message Trailer

MHD Message HeaderMessage (like ORDERS)

MTR Message Trailer

MHD Message Header Message (like ORDLTR)

MTR Message Trailer

END Interchange Trailer

Message Loop Begin

Message Loop End

Documents

1011 End to End Tracking SAP PI