Kontakt

Ansicht
Dokumentation

IDOC_INPUT_FTR_TRES_CHANGE - IDoc -> BAPI: IDOC_INPUT_FTR_TRES_CHANGE

IDOC_INPUT_FTR_TRES_CHANGE - IDoc -> BAPI: IDOC_INPUT_FTR_TRES_CHANGE

CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This function module was generated from
the object BUS5640 and the method CHANGE
for the BAPI call through ALE.

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

The function module is started in the inbound system by the ALE system. It converts the data from the IDoc into BAPI parameters and calls the BAPI in the incoming system. For more information on this BAPI, refer to BAPI_FTR_TRES_CHANGE

When this module is executed, a new IDoc status is written. It states whether the BAPI cal in this system has been executed successfully (status '53') or has errors (status '51').

The ALE layer writes the IDoc status in connection with the BAPI return parameter, and, in the case of an error, in connection with the ALE layer. Effects of the BAPI return parameters:

  • If the BAPI return parameter is an exporting parameter, 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 message types 'W', 'I' , or 'S'.
  • If the return parameter is a tables parameter, several IDoc status records are written. The message types determine the IDoc status. If a message in the table has type 'A' or 'E', then the status '51' (application document not posted) is written for the IDoc for all entries, except for those with type 'S' (that is, with types 'A', 'E', 'W' , or 'I'). For messages with type 'S' , no IDoc status appears. If no message in the table has type 'A' or 'E', status '53' is written for 'W', 'I' , or 'S' . The status records are written in the sequence of the messages in the return parameter.
  • If the return parameter was not filled, this means that the BAPI was called successfully. In this case, an IDoc status record with the status '53' (application document posted) is written from the ALE layer.

If there is an error, the application must ensue that the data is in a consistent state - that is, it resets undesired changes through a rollback.

For all errors, the ALE error handling function is at your disposal (creation of a work item).





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

FTR_BAPI_TRES

CPI1466 during Backup   General Material Data  
This documentation is copyright by SAP AG.

Length: 2982 Date: 20240523 Time: 082451     sap01-206 ( 61 ms )