Naming conventions for ALE business objects

The Adapter Connection wizard provides names for the ALE business object. The business object name reflects the structure of the business function on the SAP server.

If you are using the ALE pass-through IDoc interface, the following naming conventions apply:
  • When you select Generic IDoc from the Object Discovery and Selection window, the Adapter Connection wizard creates a business object named SapGenericIDocObject. The naming convention described in the following sections does not apply to generic IDocs.
  • When you discover an IDoc from the system or from a file, the object is named according to the naming convention for top-level wrapper objects, as described in Table 1. No other objects are generated.

When it names business objects for ALE, the Adapter Connection wizard adds a prefix of Sap. The wizard also converts the name of the IDoc and extension to mixed case, removing any separators such as spaces or underscores, capitalizes the first letter of each word, and it can add an element-specific suffix.

The following table describes the conventions that are applied by the Adapter Connection wizard when it names ALE business objects. The [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. Naming conventions for ALE business objects
Element Naming convention
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 + BO

For example, the business object for the IDoc MATMAS03 is: SapMatmas03BO
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

For 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 that the Adapter Connection wizard appends to the name.