Supported data operations on ALE business objects
The operations that are supported by ALE business objects vary, depending on whether the business object is an outbound or inbound object. The adapter uses the application-specific information (ASI) inside the business object definition to implement the operation.
Business objects that are generated with the ALE pass-through IDoc interface are not associated with an operation.
Outbound business objects
The operation of an ALE
outbound business object is called by the application component that makes
calls to SAP through the adapter. The adapter supports the following outbound
operation:
| Operation | Definition |
|---|---|
| Execute | This operation posts the IDoc business object
to the SAP application. This operation is one-way and asynchronous. For the CWYAP_SAPAdapter_TX.rar version of the adapter, the transaction ID is returned. |
Inbound business objects
For ALE inbound business
objects, the application-specific information of an operation contains the
message type, message code, and message function for an IDoc type. The adapter
supports the following inbound operations:
| Operation | Definition |
|---|---|
| Create | The top-level business object and all contained children are created. |
| Update | The top-level business object is modified. This operation can include adding and deleting child objects. |
| Delete | The top-level business object and any contained children are deleted. |
The adapter uses the IDoc control record field data
to determine the operation that is set on the business object before sending
it to the endpoint. The following fields in the control record are used to
determine the operation:
- Logical_message_type (MESTYP)
- Logical_message_code (MESCOD)
- Logical_message_function(MESFCT)