Ansicht
Dokumentation

XI_BADI - BAdI: Receive XI Message Type "TreasuryDealNotification"

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

You can use the XI interfaces to automatically transfer transactions that were concluded on a marketplace, for example. You can transfer data for the following financial products in the area of foreign exchange transactions:

• FX Spot and Forward

• FX Swap

• FX Options (plain vanilla)

Note (1):
Unlike the BAPI interfaces, XI interfaces are not influenced by your Customizing settings, Customizing terms, or organizational structure. It is sufficient for your business partner (a counterparty or a marketplace) to simply send you the structure characteristics of the transaction.

You can use tools from the SAP Exchange Infrastructure (XI) to technically map external formats (for example, XML) to the SAP XI interface TreasuryDealNotification.

In the case of business mapping, you use the Business Add-Ins (BAdIs):

• BAdI: Receive XI Message Type TreasuryDealNotification (FTR_XI_INTERFACE_MAPPING)
  This gives you complete access to the interface TreasuryDealNotification or the enhancements.

• BAdI: Receive Financial Transactions (General View) (FTR_XI_GENERAL_MAPPING)
  This gives you access to flat structures that have already been processed. They should facilitate mapping and how you proceed.

You can use these two enhancements when:
- translating the external partner ID to the key in your business partner master data.
- defining terms based on your Customizing settings (for example, product types and transactions types.)

Note (2):
You can also use other transactions to map with the derivation tool. The derivation tool enables you to define assignments and derivation rules without any programming knowledge.

• Mapping for general transaction information.

• Mapping for spot exchange and forward transactions

• Mapping for foreign exchange swaps

• Mapping for currency options

When the data is being processed, the system configures the various data structures of the transactions received and executes the following steps in sequential order:

1. Internal SAP step:
   The system converts the XI message and preassigns the EXT structures.
2. Call BAdI:
   (FTR_XI_INTERFACE_MAPPING, Method MAPPING )
   You can implement this BAdI if, for example, you prefer the actual view of the TreasuryDealNotification message type or you have enhanced the interface with your own fields or elements.
3. Internal SAP step:
   Preassignment of INT structures
4. Call BAdI:
   (FTR_XI_INTERFACE_MAPPING, Method GET_ID_TYPES)
   You provide SAP with the ID types to identify the business partner from the view of the provider (counterparty) or from the exchange.
5. Internal SAP step:
   If you have informed SAP of your ID types, SAP attempts to select an existing business partner using this data and the "external" business partner ID included in the message. Note: See the SAP business partner master data, tab page "Identification". You can define alternative ID numbers on this tab page and assign them to ID types.
6. Call BAdI:
   (FTR_XI_GENERAL_MAPPING, Method PRE_MAPPING)
   You can implement this BAdI to carry out checks and further steps that are only relevant after the business partner IDs have been converted.
7. Call Derivation Tool:
   This always involves two sequences:
   - Sequence for general transaction information
   - Sequence to specifically map each financial product

Note:
If you have not implemented any of these BAdIs up to now, you must convert the external partner IDs to the internal business partner IDs along with their company code (requestor), and assign a product type and transaction type. Other fields are optional.

1. Call BAdI:
   (FTR_XI_GENERAL_MAPPING, Method POST_MAPPING)
   You can implement this BAdI to make checks and further steps, for example, that are only relevant after processing in the derivation tool.
2. Internal SAP step:
   You need to have specified all the data in the required fields to create the transactions. BAPI interfaces are used to check and create the transactions.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5127 Date: 20240523 Time: 184027     sap01-206 ( 75 ms )