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. For child objects, the prefix is prepended to the actual structure or table name. The tool does not permit you to change this prefix.
Naming convention for simple BAPI business objects
The following table describes the naming convention that the enterprise service discovery wizard uses for the business object of a simple BAPI.
Element | Naming convention |
---|---|
Name of the BusinessGraph | Sap + Name of the wrapper object as specified by the user in the enterprise service discovery wizard + Wrapper + BG For example: SapSalesOrderWrapperBG |
Name of the top-level business object | Sap +Name of the wrapper object as specified by the user in the enterprise service discovery wizard + Wrapper For example: SapSalesOrderWrapper |
Name of the BAPI interface object | Sap + Name of the BAPI interface For example: SapBapiSalesOrderCreateFromDat1 Note: The top-level object can contain more than one individual BAPI
interface objects
|
Name of the child object | Sap + Name of the Structure/Table For example: SapReturn Note that in the case of structures having the same name in different BAPIs or the same structures within a BAPI (for example, one at the export level and one at the table level), the enterprise service discovery wizard generates a unique numeric code and increments to the structure that is existing more than once. For example: SapReturn619647890, where 619647890 is the unique identifier suffix appended to the name SapReturn. |
Naming convention for BAPI transaction objects
The following table describes the naming convention that the enterprise service discovery wizard uses for BAPI transaction objects.
Element | Naming convention |
---|---|
Name of the BusinessGraph | Sap + Name of the wrapper object as specified by the user in the enterprise service discovery wizard + Txn + BG For example: SapSalesOrderTxnBG |
Name of the top-level business object | Sap +Name of the wrapper object as specified by the user in the enterprise service discovery wizard + Txn For example: SapSalesOrderTxn |
Name of the BAPI interface object | Sap + Name of the BAPI interface For example: SapBapiSalesOrderCreateFromDat1 Note: The top-level object can contain more than one individual BAPI
interface objects
|
Name of the child object | Sap + Name of the Structure/Table For example: SapReturn Note that in n the case of structures having the same name in different BAPIs or the same structures within a BAPI (for example, one at the export level and one at the table level), the enterprise service discovery wizard generates a unique numeric code and increments to the structure that is existing more than once. For example: SapReturn619647890, where 619647890 is the unique identifier suffix appended to the name SapReturn. |
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)