A BAPI interface consists of importing, exporting, and table parameters, where:
Some BAPIs may not have all of the types of parameters. For example, a BAPI may have importing and table parameters only.
SAPODA automatically maps the BAPI importing, exporting, and table parameters to attributes in WebSphere business objects for SAP as described in Table 30.
Table 30. Naming Conventions: WebSphere business objects for SAP
Business Object | BAPI Interface |
---|---|
Top-level business object | BOprefix_BAPInameNote: The illustrations in this chapter use SAP_ or sap_ as the business object prefix. You can specify your own meaningful prefix when you create your business object definitions. |
Attribute | FieldDescription |
Child business object | BOprefix_BAPIParameterName |
SAPODA guarantees that all attribute names in the business object definition are unique. If a BAPI has multiple parameters with the same field description, SAPODA adds a counter as the suffix to the generated attribute name.
You can modify the attribute names at any time after you generate the business object definition. However, when you modify an attribute name, ensure that you do not modify the application-specific information. The connector uses this information to identify the BAPI parameter to which the attribute corresponds. For more information on the application-specific information, see "AppSpecificInfo for attributes".