Ansicht
Dokumentation

BAPIs in the Foreign Exchange Area (New) ( RELNFIN_ERP2005_TR_BAPI )

TXBHW - Original Tax Base Amount in Local Currency   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Short text

BAPIs in the Foreign Exchange Area (New)

Use

As of release SAP ECC Enterprise Extension Financial Services 6.0 (EA-FS 600) there are new BAPIs in the foreign exchange area.

The following methods already exist for the business object ForeignExchange:

Method	Function module
Change	BAPI_FTR_FXT_CHANGE
Create	BAPI_FTR_FXT_CREATE
CreateSwap	BAPI_FTR_FXT_CREATESWAP
GetDetail	BAPI_FTR_FXT_GETDETAIL
PrepareChangeStructure	BAPI_FTR_FXT_PREP_STRUC
Reverse	BAPI_FTR_FXT_REVERSE
Settle	BAPI_FTR_FXT_SETTLE

The interfaces for the existing BAPIs have not been changed and their functions have only changed slightly:

• The BAPIs return a success message in the RETURN parameter due to a success. Warning messages are returned for the consistency check.

• If errors occur, an error message is included in the RETURN parameter as well as error and warning messages that have occurred in the consistency check.

After the coding has been restructured and grouped together for services, the architecture of the BAPIs in the foreign exchange area is as follows:

In the function group FTR_API, services are provided using function modules. These services correspond to processing a tab page for the online transaction. In the BAPIs, the services are simply called up in the appropriate sequence and supplied with data. This means you can easily create additional BAPIs. If BAPIs do not fulfill the required functions, customers can create a remote-enabled function module in the customer namespace which calls up the required services.

The business object ForeignExchange has been enhanced using the following new methods:

Method	Function module
DealCreate	BAPI_FTR_FXT_DEALCREATE
DealChange	BAPI_FTR_FXT_DEALCHANGE
DealGet	BAPI_FTR_FXT_DEALGET

• With the DealCreate method you can now create a foreign exchange transaction completely with only one call. You must enter the general data, data for a specific product category, payment details, and other flows for the method.

• With the DealChange method you can change all the data for a foreign exchange transaction with only one call-up. You must enter the general data, data for a specific product category, payment details, and other flows for the method.

• The DealGet method gets the complete data for a foreign exchange transaction (general data, data for a specific product category, payment details, and other flows).

For the new BAPIs, the concept of selected field changes has been changed. Now a change parameter exists, also when creating, for a structure or table parameter. This change parameter indicates the fields of the parameter that are to be transferred. This means it is also possible to create fields without a value, that would usually have default values in the application.

Since payment details and other flows possibly occur several times and are therefore to be transferred as tables, the TABLEINDEX column exists. This column creates a unique assignment between a parameter entry and a change parameter entry.

The parameters PAYDET_COMPLETE_INDICATOR and ADDFLOW_COMPLETE_INDICATOR also exist for the payment details and other flows. These parameters specify whether the entries that are transferred to the table are complete or not. If they are set, the transferred entries are complete and exist in the transaction. However, entries that are not transferred in the BAPI are deleted. If they are not set, the transferred entries are changed and created.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

See also

BAL_S_LOG - Application Log: Log header data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 5806 Date: 20240520 Time: 194938     sap01-206 ( 80 ms )