P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

SAP PI - Naming Conventions for OA-EDI

Document Information

Title SAP PI - Naming Conventions for OA-EDI

Version updated on 07-AUG-2009
Owner Jan Hoffmann - [email protected] - contact phone +49-172-6856792

Overview

1. Enterprise Services Repository....................................................................................3

1.1. Enterprise Objects 3
1.1.1. Products ................................................................................................................................................... 3
1.1.2. Software Components.............................................................................................................................. 3
1.1.3. Software Component Versions ................................................................................................................ 3
1.1.4. Namespaces ............................................................................................................................................ 3

1.2. Integration Scenario Objects 4

1.2.1. Integration Scenarios ............................................................................................................................... 4
1.2.2. Actions ..................................................................................................................................................... 4
1.2.3. Integration Processes .............................................................................................................................. 4

1.3. Interface Objects 5

1.3.1. Service Interfaces .................................................................................................................................... 5
1.3.2. Message Types........................................................................................................................................ 5
1.3.3. Fault Message Types............................................................................................................................... 5
1.3.4. Data Types ............................................................................................................................................... 6
1.3.5. Data Type Enhancements........................................................................................................................ 6
1.3.6. External Definitions .................................................................................................................................. 6
1.3.7. Context Objects........................................................................................................................................ 6

1.4. Mapping Objects 7

1.4.1. Operation Mappings................................................................................................................................. 7
1.4.2. Message Mappings .................................................................................................................................. 7
1.4.3. Mapping Templates.................................................................................................................................. 7
1.4.4. Imported Archives .................................................................................................................................... 7

1.5. Adapter Objects 8

1.5.1. Adapter Metadata..................................................................................................................................... 8
1.5.2. Communication Channel Templates........................................................................................................ 8

(continued on next page)

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 1 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

2. Integration Directory......................................................................................................9
2.1. Configuration Objects 9
2.1.1. Configuration Scenario............................................................................................................................. 9
2.1.2. Receiver Determination............................................................................................................................ 9
2.1.3. Interface Determination............................................................................................................................ 9
2.1.4. Value Mappings ....................................................................................................................................... 9
2.1.5. Value Mapping Groups ............................................................................................................................ 9

2.2. Collaboration Profiles 10

2.2.1. Party....................................................................................................................................................... 10
2.2.2. Business Services.................................................................................................................................. 10
2.2.3. Business Systems.................................................................................................................................. 10
2.2.4. Communication Channels ...................................................................................................................... 11

2.3. Collaboration Agreements 11

2.3.1. Sender Agreements ............................................................................................................................... 11
2.3.2. Receiver Agreements............................................................................................................................. 11

3. Third Party Products....................................................................................................12

3.1. Seeburger 12
3.1.1. System Mappings................................................................................................................................... 12

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 2 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

1. Enterprise Services Repository

1.1. Enterprise Objects

1.1.1. Products

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

1.1.2. Software Components

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

1.1.3. Software Component Versions

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

1.1.4. Namespaces

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 3 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

1.2. Integration Scenario Objects

1.2.1. Integration Scenarios

Convention IS_<ScenarioDescription>

Parameters ScenarioDescription: Interface functionality (max. 35 characters)

Examples IS_UploadCreditRating

1.2.2. Actions

Convention <Action|Event><BusinessObject>

Parameters Action|Event: Actions mostly refer to synchronous interfaces

Events mostly refer to asynchronous interfaces
BusinessObject: Object which represents Action/Event

Examples SendCreditRating
GetEmployeeDetails
CreateMaterial

1.2.3. Integration Processes

Convention BPM_<ProcessDescription>

Parameters ProcessDescription: Process functionality (max. 35 characters)

Examples BPM_OutboundInvoiceConsolidationEDIFACT

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 4 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

1.3. Interface Objects

1.3.1. Service Interfaces

Convention SI_<Category><Mode>_<BusinessService>

Parameters Category: O-Outbound; I-Inbound; A-Abstract

Mode: S-Synchronous; A-Asynchronous
BusinessService: Business Service rendered by interface
ANSI.X12 Standard: X-ANSI.X12; V-VICS; U-UCS

Pattern-EDI ANSI.X12: SI_[O|I|A][S|A]_[812|850|850|...]_[X|V|U][4010|5030|...]

EDIFACT: SI_[O|I|A][S|A]_[ORDERS|INVOIC|...]_[D96A|D01A|...]_[UN|EAN]
SAP-IDoc: SI_[O|I|A][S|A]_<MessageType>_<IDocBasicType>_<IDocExtension>

Examples-EDI ANSI.X12: SI_OA_850_X4010

EDIFACT: SI_OA_ORDERS_D96A_UN
SAP-IDoc: SI_OA_ZPICRQ_DELVRY03_ZDELVRY3

Examples-A2A SI_IS_CreditRatingManagement
SI_IA_CreditRatingManagement

1.3.2. Message Types

Convention MT_<BusinessObject>_<Suffix>

Parameters BusinessObject: Object for representation of data type in message type

Suffix: for sync: REQ-for requests; RES-for response
for async: no suffix
for JBDC: SELECT-select; INSERT-insert; UPDATE-update

Remark this object is not needed for IDocs or EDI messages (handling via external definitions)

Examples-A2A MT_CreditRatingQuery_REQ

1.3.3. Fault Message Types

Convention FT_<BusinessObject>_<Operation>

Parameters BusinessObject: Object for representation of data type in message type

Operation: Operation for which Fault was generated

Examples FT_CreditRating_Upload

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 5 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

1.3.4. Data Types

Convention DT_<BusinessObject>

Parameters BusinessObject: data type representation in XI

Remark for ABAP Proxies: usage to SAP tables and SAP field names recommended

Examples DT_CreditRating

1.3.5. Data Type Enhancements

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

1.3.6. External Definitions

Convention ED_<BusinessObject>

Parameters BusinessObject: Object for representation of external definition

ANSI.X12 Standard: X-ANSI.X12; V-VICS; U-UCS

Remark IDocs are handled via imported objects

Pattern-EDI ANSI.X12: ED_[812|850|850|...]_[X|V|U][4010|5030|...]

EDIFACT: ED_[ORDERS|INVOIC|...]_[D96A|D01A|...]_[UN|EAN]

Examples-EDI ANSI.X12: ED_850_X4010

EDIFACT: ED_ORDERS_D96A_UN

Examples-A2A ED_CreditRating

1.3.7. Context Objects

Convention CO_<ContextObjDescription>

Parameters ContextObjDescription: meaningful element description

Examples CO_CustomerNumber

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 6 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

1.4. Mapping Objects

1.4.1. Operation Mappings

Convention OM_<SourceOperation>_To_<TargetOperation>_<AddInfo>

Parameters SourceOperation: Source operation (analog to service interface)

TargetOperation: Target operation (analog to service interface)
AddInfo: Additional information to distinguish similar mappings

Examples-EDI OM_DESADV_D96A_UN_To_ZPICRQ_DELVRY03_ZDELVRY3
OM_856_X4010_To_ZPICRQ_DELVRY03_ZDELVRY3

Examples-A2A OM_UploadCreditRating_To_CreateCreditRating

1.4.2. Message Mappings

Convention MM_<SourceBusinessObject>_To_<TargetBusinessObject>_<AddInfo>

Parameters SourceBusinessObject: Object for representation of message type

TargetBusinessObject: Object for representation of message type
AddInfo: Additional information to distinguish similar mappings

Examples-EDI MM_DESADV_D96A_UN_To_ZPICRQ_DELVRY03_ZDELVRY3
MM_856_X4010_To_ZPICRQ_DELVRY03_ZDELVRY3

Examples-A2A MM_CreditRating_to_CreditRating

1.4.3. Mapping Templates

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

1.4.4. Imported Archives

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 7 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

1.5. Adapter Objects

1.5.1. Adapter Metadata

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

1.5.2. Communication Channel Templates

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 8 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

2. Integration Directory

2.1. Configuration Objects

2.1.1. Configuration Scenario

Convention EDI: PG_TOM_EDI_<Region>_<Standard>_<Direction>_<Transaction>

A2A: PG_TOM_A2A_<Region>_<Application>

Parameters Region: GLOBAL, EMEA, NA, LA, ASIA (uppercase)

Standard: EDIFACT, X12, UCS, VICS,
Direction: IN, OUT (uppercase)
Transaction: INSDES, INVOIC, 850, 810
Application: WOM, OrderPad (camel case)

Pattern-EDI ANSI.X12: PG_TOM_EDI_[NA|...]_[X12|UCS|VICS]_[IN|OUT]_[850|856|...]

EDIFACT: PG_TOM_EDI_[EMEA|...]_EDIFACT_[IN|OUT]_[ORDERS|INVOIC]

Pattern-A2A PG_TOM_A2A_[GLOBAL|NA|EMEA|...]_[WOM|OrderPad|...]

Examples-EDI ANSI.X12: PG_TOM_EDI_NA_X12_IN_850

EDIFACT: PG_TOM_EDI_EMEA_EDIFACT_IN_ORDERS

Examples-A2A PG_TOM_A2A_GLOBAL_WOM
PG_TOM_A2A_GLOBAL_OrderPad

2.1.2. Receiver Determination

(no further information required; automated determination by SAP PI)

2.1.3. Interface Determination

(no further information required; automated determination by SAP PI)

2.1.4. Value Mappings

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

2.1.5. Value Mapping Groups

(contact Global OA/EDI Solution Owner for further information; do not create without prior approval)

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 9 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

2.2. Collaboration Profiles

2.2.1. Party

Convention EDI: <PartnerType>_<PartnerFunction>_<CustomerNumber>

A2A: P_TOM_A2A_<Region>_<Application>

Parameters PartnerType: Partner type in SAP partner profile (WE20)

PartnerFunction: Partner function in SAP partner profile (WE20)
CustomerNumber: SAP customer number (10 digits; for KU/LI with leading zeros)
Region: GLOBAL, EMEA, NA, LA, ASIA (uppercase)
Application: WOM, OrderPad (camel case)

Pattern-EDI [KU|LI|LS|...]_[AG|WE|...]_<CustomerNumber>

Pattern-A2A P_TOM_A2A_[GLOBAL|EMEA|NA|...]_[WOM|OrderPad|...]

Examples-EDI KU_AG_0001234567

Examples-A2A P_TOM_A2A_GLOBAL_WOM
P_TOM_A2A_GLOBAL_OrderPad

2.2.2. Business Services

Convention EDI: contact Global OA/EDI Solution Owner for further information
A2A: CC_TOM_A2A_<Region>_<Application>

Parameters Region: GLOBAL, EMEA, NA, LA, ASIA (uppercase)

Application: WOM, OrderPad (camel case)

Examples-A2A CC_TOM_A2A_GLOBAL_WOM
CC_TOM_A2A_GLOBAL_OrderPad

2.2.3. Business Systems

Convention SAP: <SapSystem><SapClient>

Parameters SapSystem: Name of SAP system (like KLD, A6P, F6P, L60, N6P)
SapClient: Number of SAP client (like 400, 430)

Remark Objects are owned and created by EAI

Examples-SAP F6P430

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 10 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

2.2.4. Communication Channels

Convention EDI: contact Global OA/EDI Solution Owner for further information
A2A: CC_TOM_A2A_<Region>_<Application>_<AdapterType>_<Direction>

Parameters Region: GLOBAL, EMEA, NA, LA, ASIA (uppercase)

Application: WOM, OrderPad (camel case)
AdapterType: Adapter type (like File, RFC, JBDC, HTTP)
Direction: in, out (lowercase)

Remark SAP For SAP these communication channels are owned by EAI (no separate creations!):
GeneratedReceiverChannel_HTTP
GeneratedReceiverChannel_IDoc
GeneratedReceiverChannel_RFC
GeneratedReceiverChannel_XI

Examples-A2A CC_TOM_A2A_GLOBAL_WOM_File_in
CC_TOM_A2A_GLOBAL_WOM_File_out

2.3. Collaboration Agreements

2.3.1. Sender Agreements

(no further information required; automated determination by SAP PI)

2.3.2. Receiver Agreements

(no further information required; automated determination by SAP PI)

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 11 of 12
file: c:\sap pi - naming conventions for oa-edi.doc
 P&G Shelf-to-Cash > SAP PI > Naming Conventions for OA-EDI

3. Third Party Products

3.1. Seeburger

3.1.1. System Mappings

Convention See_<SeeDirection>_<Standard+MessageType+Version>

Parameters SeeDirection: Seeburger direction: E2X = EDI to XML; X2E = XML to EDI
Standard: UN = EDIFACT; EAN = EANCOM; ANSIX12 = ANSI X.12
MessageType: Message type (like INSDES, DESADV, 810, 850)
Version: EDI version (like D96A, D01A, 4010, 5030)

Examples See_E2X_PRICAT_UN_D96A
See_E2X_ANSIX12_810_V4010

document version: 07-AUG-2009 - saved on 07-AUG-2009 13:56 - document creator: Jan Hoffmann Page 12 of 12
file: c:\sap pi - naming conventions for oa-edi.doc