The Adapter Connection wizard provides names for the business objects for BAPIs, BAPI transactions, and BAPI result sets. The business object name reflects the structure of the business object.
The following table describes the naming convention that the Adapter Connection wizard uses for the business object of BAPIs.
Element | Naming convention |
---|---|
Name of the business graph | Sap + Name of the wrapper object you specify in the Adapter Connection wizard + BG For example: SapSalesOrderBG |
Name of the top-level business object | Sap + Name of the wrapper object you specify in the Adapter Connection wizard + Wrapper For example: SapSalesOrderWrapper |
Name of the BAPI business object | Sap + Name of the BAPI interface For example: SapBapiSalesOrderCreateFromDat1 Note: The
top-level object can contain more than one BAPI object.
|
Name of the child object | Sap + Name of the Structure/Table For example: SapReturn |
If structures with the same name exist in different BAPIs or exist within a BAPI (for example, one at the export level and one at the table level), the Adapter Connection wizard adds a unique suffix to differentiate the structures. The first structure is assigned a name (for example, SapReturn) and the second structure is assigned a name such as SapReturn619647890, where 619647890 is the unique identifier appended to the name by the Adapter Connection wizard.
The following table describes the naming convention that the Adapter Connection wizard uses for the business object of BAPI transactions.
Element | Naming convention |
---|---|
Name of the business graph | Sap + Name of the wrapper object you specify in the Adapter Connection wizard + Txn + BG For example: SapCustomerTxnBG |
Name of the BAPI business object | Sap + Name of the BAPI interface + Txn For example: SapCustomerTxn |
Name of the child object | Sap + Name of the Structure/Table For example: SapReturn |
If structures with the same name exist in different BAPIs or exist within a BAPI (for example, one at the export level and one at the table level), the Adapter Connection wizard adds a unique suffix to differentiate the structures. The first structure is assigned a name (for example, SapReturn) and the second structure is assigned a name such as SapReturn619647890, where 619647890 is the unique identifier appended to the name by the Adapter Connection wizard.
The following table describes the naming convention that the Adapter Connection wizard uses for the business object of a BAPI result set.
Element | Naming convention |
---|---|
Name of the top-level business object | Sap + Name of the object you specify in the Adapter Connection wizard + Resultset For example: SapCustomerGetDetailResultset |
Name of the result set BAPI business object | Sap + Name of the BAPI interface For example: SapBapiCustomerGetDetail |
Name of the child object | Sap + Name of the Structure/Table For example: SapReturn |
Name of the query business object | Sap + Formatted name of the query BAPI interface For example: SapBapiCustomerGetList |
If structures with the same name exist in different BAPIs or exist within a BAPI (for example, one at the export level and one at the table level), the Adapter Connection wizard adds a unique suffix to differentiate the structures. The first structure is assigned a name (for example, SapReturn) and the second structure is assigned a name such as SapReturn619647890, where 619647890 is the unique identifier appended to the name by the Adapter Connection wizard.