Ansicht
Dokumentation

Counterconfirmation BAPI for Transactions (BUS2042) ( RELNTRTM_46A_C_BAPI_CONF )

Counterconfirmation BAPI for Transactions (BUS2042) ( RELNTRTM_46A_C_BAPI_CONF )

RFUMSV00 - Advance Return for Tax on Sales/Purchases   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Counterconfirmation BAPI for Transactions (BUS2042)

Scope of Functions

As of Release 4.6A, you have the option of using BAPI methods to counterconfirm transactions in the money market and foreign exchange areas. The BAPI method provided for the business object 'transaction' (BUS2042) is called 'CounterConfirm'.

The transfer parameters for the BAPI are defined and documented in the Business Object Repository (BOR). Here, you also find a more detailed description of how to call up BAPIs from external systems.

BAPIs form the basis of the SAP R/3 software change management, and are therefore protected against any future changes which may be incompatible.

Procedure for using the counterconfirmation BAPI:

You can use the BAPI interface to counterconfirm a business transaction externally. This changes the status in the correspondence data table VTBKORES and in the corresponding business transaction from '1' (= required) to '3' (= counterconfirmed).

The transaction data is not matched, in other words, you must match the transactions either manually or automatically before you call up the method. The method call works in the same way as the counterconfirmation function from the correspondence monitor.

A prerequisite for counterconfirmation using the method is that the relevant correspondence data record in table VTBKORES has the value 'X' in the SSTATUS field. This is only possible if business transactions were created or changed after Release 4.0B.

You must also make sure that the method call for internal R/3 processing can be assigned uniquely to one business transaction or correspondence data record. If this is not the case, the counterconfirmation is rejected. We recommend, therefore, that you enter the following optional call parameters, provided the calling program is familiar with them:

  • TRANSACTIONACTIVITY
  • SEQUENCENUMBER
  • IDOCNUMBER
  • SWIFTREFERENCE





BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 2246 Date: 20240523 Time: 081228     sap01-206 ( 45 ms )