Notes
Notes
Please also note the following:
Namespace extension is also supported for customers and partners starting in Release 4.5A.
The filtering of data can be linked to conditions that are defined as filters in the distribution model.
If you want to perform data filtering, you will have to choose option Data filtering allowed in the dialog box for creating or changing the interface.
For more information, see the ALE Programmer Guide under
Data Filtering.
The function module on the outbound side has an optional parameter: SERIAL_ID (reference to the channel number). This input parameter controls the allocation of messages to message channels. All the messages in the target system are processed in an object channel in the same order they were created in the source system. An object channel is identified by a key from the BAPI object type and the channel number.
For more information on this subject, refer to the document "ALE Introduction and Administration" under
Serialization of Messages.
The relationship in ALE answers the following questions:
Which application object was used to create the IDoc?
Prerequisite: The application has correctly filled parameter APPLICATION_OBJECTS in the function module on the outbound side.
Which outbound IDoc was used to create the inbound IDoc, and which application object was created from this inbound IDoc?
Prerequisite: A key has been defined in the BOR for the BAPI method, and this key is contained in the exporting or importing parameters in the BAPI function module. This key can consist of several key fields. If no key fields exist in the BOR, then a relationship to a different object can be specified in the corresponding prompt.
Documentation has also been written for generated function modules (outbound/inbound). You can call this documentation within the interface. It describes the meanings of the parameters and the values they can assume.
If the Return parameter has been filled by the application, the IDoc status and the corresponding information from the parameter is included in the IDoc. Message types determine the IDoc status.
If the Return parameter is an EXPORTING parameter, than a single IDoc status record is written:
Message type A: |
Status 51 (application document not posted, with DB rollback) | |
Message type E: |
Status 51 (application document not posted, no DB rollback) | |
Message type W, I, S: |
Status 53 (application document posted) |
If the Return parameter is a TABLES parameter, then several IDoc status records can be written, depending on the message types in the table:
Message type A: |
Status 51 (application document not posted, with DB rollback) | |
Message type E: |
Status 51 (application document not posted, no DB rollback) | |
Exception: |
No IDoc status for type S | |
No message type A or E: |
Status 53 (application document posted) |
The IDoc status records are written in the same sequence as the messages in the Return parameter.
If the Return parameter was not filled, this means the BAPI has been successfully called by the IDoc. In this case, the ALE layer writes an IDoc status record with status 53 (application document posted).
If an error occurs, only the first message from the Return parameter is included in the text of the corresponding error task (work item).