Ansicht
Dokumentation

MEREP_IDOC_INPUT_MEREP_DELTABO - IDoc -> FM : IDOC Inbound Process

MEREP_IDOC_INPUT_MEREP_DELTABO - IDoc -> FM : IDOC Inbound Process

Vendor Master (General Section)   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This function module has been generated from the object TESTAK and the method BAPIAKBD for the BAPI call with ALE.

The interface of this module was defined as a standard API in ALE. The data is provided by the ALE layer.

The function module is started from the ALE layer in the inbound system. It converts the data from the IDoc into BAPI parameters and calls the BAPI in the inbound system. For more information on this BAPI, see BAPIAKBD.

When this module is executed, a new IDoc status is set. This status indicates whether the BAPI call was successful in this system (status 53) or not (status 51).

The ALE layer sets the IDoc status according to the BAPI return parameters, or, if errors occur, in the ALE layer.

Consequences of the BAPI Return Parameters

  • If the BAPI return parameter is an exporting parameter, then an IDoc status record is written. The IDoc gets the status 51 (application document not posted) if the message has the type A or E. Otherwise, the IDoc gets the status 53 (application document posted) for the message types W, I, or S.
  • If the return parameter is a table parameter, then multiple IDoc status records can be written. Message types determine the IDoc status. If a message in the table has the type A or E, then the status 51 (application document not posted) is set for all entries, except for those with the type S (this means this status is set for types types A, E, W, or I). No IDoc status is set for messages with the type S. If not message in the table has the type A or E, then the status 53 (application document posted) is set for W, I, or S. The status records are written in the same order as the messages in the return parameter.
  • If the return parameter was not filled, then the BAPI was called successfully. In this case, an IDoc status record with the status 53 (application document posted) is written by the ALE layer.

If errors occur, the application must make sure that the data is consistent, for example, by rolling back any invalid changes.

You can use the ALE error handler (Create Work Item) to process any errors.





Parameters

APPLICATION_VARIABLE
CALL_TRANSACTION_DONE
IDOC_CONTRL
IDOC_DATA
IDOC_STATUS
INPUT_METHOD
IN_UPDATE_TASK
MASS_PROCESSING
RETURN_VARIABLES
SERIALIZATION_INFO
WORKFLOW_RESULT

Exceptions

WRONG_FUNCTION_CALLED

Function Group

MEREP_RUNTIME

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2919 Date: 20240603 Time: 220212     sap01-206 ( 38 ms )