Business object naming conventions

A BAPI interface consists of simple, structure, return 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 structure and table parameters to child business objects, and BAPI simple parameters to the corresponding simple attribures on WebSphere business objects for SAP as described in Table 8..

Table 8. Naming conventions: WebSphere business objects for SAP
Business object BAPI interface
Top-level business object BOprefix_BAPIname
Child business object BOprefix_BAPIParameterName
Attribute FieldDescription

Note:
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.

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.

When naming an attribute from a BAPI parameter, SAPODA prepends a string to the attribute name when the changed attribute name:

Important:
You can modify the attribute names at any time after you generate the business object definition. However, when you modify an attribute name, 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 Attribute-level ASI.

Copyright IBM Corporation 1997, 2004. All Rights Reserved.