Ansicht
Dokumentation

IDOC_INPUT_FTR_FXT_DEALCHANGE - IDoc -> BAPI: IDOC_INPUT_FTR_FXT_DEALCHANGE

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Functionality

This function module was generated from
object BUS5600 and method DEALCHANGE
, for BAPI calls using ALE.

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

The function module is executed in the inbound system by the ALE layer. It converts the data from the IDoc into BAPI parameters and calls the BAPI in the inbound system. For more information about this BAPI, see BAPI_FTR_FXT_DEALCHANGE.

When this module is executed, a new IDoc status is written. This status indicates either that the BAPI was called successfully in this system (status 53) or that errors occurred (status 51).

BAPI return parameters specify how the ALE layer writes the IDoc status. If errors occur, the ALE layer is responsible. How the BAPI return parameters work:

• If the BAPI return parameter is an EXPORTING parameter, one single IDoc status record is written. If the message has type A or E, the IDoc is given status 51 (application document not posted). Otherwise (for message types W, I, or S), the IDoc is given status 53 (application document posted).

• If the return parameter is a tables parameter, multiple IDoc status records can be written. Message types determine the IDoc status. If a message has type A or E in the table, status 51 is written for the IDoc (application document not posted) for all entries except those with the type S (entries with types A, E, W, or I). For messages with type 'S', no IDoc status appears. If a message in the table has type 'A' or 'E', status '53' (application document posted) is written for 'W', 'I' or 'S'. The status records are written to the database in the same sequence as the messages in the return parameter.

• If the return parameter is empty, the BAPI call was successful. In this case, an IDoc status record with status 53 (application document posted) is written by the ALE layer.

If errors occur, the application must ensure that the data is consistent, for example by rolling back unwanted changes.

You can use the ALE error handling functions (create a work item) to process any errors. (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_FXT

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 2901 Date: 20240523 Time: 045501     sap01-206 ( 73 ms )