IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > SAP Software > Reference > Business object information > Naming conventions for business objects
Naming conventions for Advanced event processing business objects
The external service wizard provides names for Advanced event processing business graph, top-level business object, and the business object itself. At its core, the business object name reflects the structure of the business function on the SAP server.
When naming business objects for the Advanced event processing interface, the external service wizard adds a prefix of Sap then 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 may add an element-specific suffix (for example, BG for business graph).
The following table describes the convention applied by the external service wizard when naming 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.
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
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
If that business graph generation is optional and is supported for IBM BPM or WebSphere Enterprise Service Bus only.
In the case of an IDoc duplicate name, the external service 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 external service wizard.