Business object request handling features

Table 62 lists business object request handling features supported by the connector.

Table 62. Business object request handling features

Category Feature Support Notes
Create Create verb Full
Delete Delete verb Partial Typically, the adapter uses SAP's Call Transaction API, which simulates a user's interaction through a GUI to use a transaction. SAP, therefore, is in control of all database interaction. Each SAP transaction determines whether or not a physical or logical delete is executed. Further, any custom tables and transactions that you may write may be available for direct database interaction rather than using the Call Transaction API. In this case, clearly, physical deletes may be an option.

Logical delete Partial Typically, the adapter uses SAP's Call Transaction API, which simulates a user's interaction through a GUI to use a transaction. SAP, therefore, is in control of all database interaction. Each SAP transaction determines whether or not a physical or logical delete is executed. Further, any custom tables and transactions that you may write may be available for direct database interaction rather than using the Call Transaction API. In this case, clearly, physical deletes may be an option.
Exist Exist verb Partial The connector operates by passing business object data into the SAP application via an ABAP function module. When this function executes successfully, the connector returns SUCCESS; when it fails, it returns FAIL. Because SAP is an open system, the connector supports an extremely open architecture, which allows an ABAP developer to do anything the SAP IDE permits. This includes support for the development of any verb.
Misc Attribute names Full

Business object names Full
Retrieve Ignore missing child object No
RetrieveByContent Ignore missing child object No

Multiple results No

RetrieveByContent verb Partial The connector operates by passing business object data into the SAP application via an ABAP function module. When this function executes successfully, the connector returns SUCCESS; when it fails, it returns FAIL. Because SAP is an open system, the connector supports an extremely open architecture, which allows an ABAP developer to do anything the SAP IDE permits.This includes support for the development of any verb as well as any database manipulation or code execution.
Update After-image support Partial The connector operates by passing business object data into the SAP application via an ABAP function module. When this function executes successfully, the connector returns SUCCESS; when it fails, it returns FAIL. Because SAP is an open system, the connector supports an extremely open architecture, which allows an ABAP developer to do anything the SAP IDE permits. This includes support for the development of any verb as well as any database manipulation or code execution.

Delta support Partial The connector operates by passing business object data into the SAP application via an ABAP function module. When this function executes successfully, the connector returns SUCCESS; when it fails, it returns FAIL. Because SAP is an open system, the connector supports an extremely open architecture, which allows an ABAP developer to do anything the SAP IDE permits. This includes support for the development of any verb as well as any database manipulation or code execution.

KeepRelations No
Verbs Retrieve verb Full

Subverb support Partial The connector operates by passing business object data into the SAP application via an ABAP function module. When this function executes successfully, the connector returns SUCCESS; when it fails, it returns FAIL. Because SAP is an open system, the connector supports an extremely open architecture, which allows an ABAP developer to do anything the SAP IDE permits. This includes support for the development of any verb as well as any database manipulation or code execution.

Verb stability Full

Copyright IBM Corp. 1997, 2003