Ansicht
Dokumentation

IDocs in the Confirmation Process (Message Category: FTRCON) ( RELNTRTM_46A_C_IDOC )

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Short text

IDocs in the Confirmation Process (Message Category: FTRCON)

Scope of Functions

As of Release 4.6A, you have the option of generating IDoc confirmations as well as using the existing correspondence media functions - print, fax and SWIFT files (MT300/MT320). This enables you to use the standardized R/3 IDoc interface as a basis for managing the send activity and checking the status (see also the documentation for the IDoc Interface). In the medium term, this will replace the report programs RFTXM300 and RFTXM320.

A middleware can be installed for the user which converts the IDoc data format to a SWIFT format or another format. At the moment, the SWIFT messages MT300 and MT320 can be substituted by an IDoc. There are plans to develop this function further in later releases.

The following considerations led to the generation of IDocs in the confirmation process:

• IDocs enable you to make changes to SWIFT formats or other formatting conventions independently of the R/3 System. You can change guidelines in each middleware, without having to enter notes in the R/3 System.

• You can reproduce the status of the send function at any time.

• The IDoc confirmation process can be embedded in the existing system consistently. As a result, IDocs can be sent automatically in the background after you have created a transaction, unlike SWIFT files.

• You can add data to the IDoc interface according to your requirements.

You manage IDocs in the same way as you manage the correspondence media mentioned above: on the one hand, independently of the business transaction (Customizing: 'Define Correspondence Activities') and, on the other hand, independently of the business partner (correspondence standing instructions). The IDoc correspondence medium has been added to the standing instructions.
When you define the correspondence type, you can also define the partner type and the partner number for the IDoc interface. There are two possible scenarios:

Scenario 1:You send all outgoing IDocs, using the port, to which you assigned the partner type and partner number of the relevant correspondence type.

Scenario 2:If only the partner type is entered in Customizing and not the partner number (character field), the partner number entered in the IDoc interface configuration is replaced by the business partner name. In this scenario use a separate port for each IDoc.

A user exit is available (RFTBCOEX), which you can use to represent enhancements, modifications or other send scenarios prior to sending the IDoc.

Provided that the interface is configured correctly, you can generate an IDoc as follows:

1. Choose IMG activity 'Define Correspondence Activities'and define a correspondence type (must be an external correspondence type) for a product type/transaction type from the money market or foreign exchange areas.
2. Create standing instructions for the relevant correspondence type and business partner. When doing this, specify 'IDoc' as the medium. If you define more than one medium, also indicate which status has priority.
3. Create a transaction with the business partner you have selected. The system creates a correspondence planned record in the background. This either generates correspondence as soon as you save, provided you have set the 'automatic correspondence' indicator in Customizing, or remains available for further processing.
4. Start the Output correspondencefunction from the application menu (transaction TBZ1, report program RFTBCO00) and set the 'IDoc' indicator.

CPI1466 during Backup   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 4060 Date: 20240523 Time: 061938     sap01-206 ( 90 ms )