Naming conventions for Advanced event processing business objects

The Adapter Connection wizard provides names for the Advanced event processing top-level business object, and the business object. The name of the business object reflects the structure of the business function on the SAP server.

When it names business objects for the Advanced event processing interface, 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 might add an element-specific suffix.

The following table describes the convention that is applied by the Adapter Connection wizard when it names Advanced event processing 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 convention for advanced event processing business objects
Element	Naming convention
Name of the top-level wrapper object	`Sap + Name of IDoc + [Name of Extension type IDoc]` For example: `SapAepreq01`
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 is appended to the name by the Adapter Connection wizard.