An RFC-enabled function interface consists of importing, exporting, and table parameters, where:
Some RFC-enabled functions may not have all of the types of parameters. For example, an RFC-enabled function may have importing and table parameters only.
SAPODA automatically maps the RFC-enabled function importing, exporting, and table parameters to IBM WebSphere attributes as described in Table 37.
Table 37. Naming Conventions: WebSphere Business Objects for SAP
Business object | Rfc-Enabled Function Interface |
---|---|
Top-level business object | BOprefix_FunctionNameNote: 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 | Field Description |
Child business object | BOprefix_FunctionParameterName |
SAPODA guarantees that all attribute names in the business object definition are unique. If an RFC-enabled function 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 RFC-enabled function parameter to which the attribute corresponds. For more information on the application-specific information, see "AppSpecificInfo for attributes".