Naming conventions for ALE business objects

When you use the enterprise service discovery wizard to generate a business object, a prefix of Sap is automatically assigned to the business object name. The tool does not permit you to change this prefix.

Naming convention of a single ALE IDoc business object

The naming convention of a single ALE IDoc business object is as follows:

prefix + NameofIDoc + [Name of Extension type IDoc]

Where [Name of Extension type IDoc] represents an optional entry. It is included in the name only if the selected IDoc is an Extension Type IDoc.

Naming convention of an ALE IDoc wrapper business object

An IDoc wrapper business object is used for business objects that represent IDoc packets.

The naming convention of an ALE IDoc wrapper business object graph is as follows:

prefix + NameofIDoc + [Name of Extension type IDoc] + Wrapper + BG

The naming convention of the top level wrapper object of an ALE IDoc packet is as follows:

prefix + NameofIDoc + [Name of Extension type IDoc] + Wrapper

The naming convention of each participant single IDoc business object is the same as all single IDoc business objects:

prefix + NameofIDoc + [Name of Extension type IDoc]

Where [Name of Extension type IDoc] represents an optional entry. It is included in the name only if the selected IDoc is an Extension Type IDoc.

Note that in case of an IDoc duplicate name, the enterprise service discovery wizard adds a unique suffix to distinguish the business object. If an IDoc packet has two segments with the same name, for example segOrder, then 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 suffix appended to the name by the enterprise service discovery wizard.

Related concepts
ALE business object structure

Terms of use |

Last updated: Sun Mar 12 11:15:17 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)