WebSphere Message Brokers
File: rbp_sap_namebo_ale
Writer: Karen Cameron

Reference topic

This build: July 31, 2007 21:40:42

Naming conventions for ALE business objects

The Adapter Connection wizard provides names for the ALE business graph, top-level business object, and the business object itself. The business object name reflects the structure of the business object.

The following table describes the naming conventions that the Adapter Connection wizard uses for the business object. Note that [Name of Extension type IDoc] in the Naming convention column represents an optional entry. It is included in the name only if the selected IDoc is an Extension Type IDoc.

Table 1. ALE business object naming convention
Element Naming convention
Name of the business graph Sap + Name of IDoc + [Name of Extension type IDoc] + BG

For example: SapAlereq01BG

Name of the top-level wrapper object

Sap + Name of IDoc + [Name of Extension type IDoc]

For example: SapAlereq01

Name of the IDoc business object for basic IDocs

Sap + Name of IDoc

For example, the business object for the IDoc MATMAS03 is: SapMatmas03

Name of the IDoc business object for extension type IDocs

Sap + Name of IDoc + Name of Extension type IDoc

For example, the business object for the IDoc DELVRY03 and extension SD_DESADV_PDC is: SapDelvry03SdDesadvPdc

In the case of an IDoc duplicate name, the Adapter Connection wizard adds a unique suffix to differentiate the business object. If an IDoc packet has two segments with the same name (for example segOrder), the first business object is assigned the name SapSegOrder and the second business object is assigned a name such as SapSegOrder619647890, where 619647890 is the unique identifier appended to the name by the Adapter Connection wizard.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:40:42

rbp_sap_namebo_ale This topic's URL is: