Ansicht
Dokumentation

Correspondence enhancements - MM/FX/DE ( RELNTRTM40C_CORR_MMFXDE )

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Short text

Correspondence enhancements - MM/FX/DE

Description

From Release 4.5A, correspondence for further derivative transactions is available. For FRAs, CAPs/FLOORs and SWAPs, confirmations and other correspondence can now be generated. Correspondence can be customized for both the transactions themselves and for the interest rate adjustment activities. The standard form is F_TR_CONFIRM_ALL in which diverse text modules of the text ID, 'TBCO', are included. You will find further information on this in the form documentation for F_TR_CONFIRM_ALL.
Via transaction SO10 and entry of the text ID, standard texts can be edited.

Control of correspondence via planned records/work lists:

Upto and including Release 4.0B, correspondence was created on the basis of Customizing settings and standing instructions correspondence (SI) was created on the basis of the last activity. Access to control was only possible via changes to the standing instructions/Customizing settings.
With Release 4.5A, correspondence is created as a worklist and/or planned records when creating/changing/reversing/settling. Planned records can be deleted from the transaction via Extras --> Delete correspondence or created. Correspondence is either carried out automatically or by starting the report RFTBCO02 (Transaction TBZ1).

This enhanced control results in additional authorization problems as correspondence can be suppressed. You can use authorization object T_DEAL_PD to stop the creation and/or deletion of planned records via function '04' (correspondence), activities '01' (add or generate) and/or '06' (delete).

When changing a transaction and correspondence already carried out, a dialog box appears from Release 4.5A, asking whether the change is correspondence-relevant or not. If this decision is not to be left to the user, he must not be given access to function '04' (correspondence) and activity '02' (change) via authorization T_DEAL_PD. In this case, the dialog box is suppressed and a planned record is created.

There has been a small enhancement relating to status allocation in Standing instructions correspondence: Up to Release 4.0B, the confirmation status for the outgoing confirmation is always set in the case of outgoing EXTERNAL correspondence types. The settings are limited to the definition of a principal correspondence medium if several media are selected. This can lead to problems, especially if more than one correspondence type per activity exists. From Release 4.5A, you can, therefore, select the 'No status allocation' option in the 'Principal correspondence medium' field. When creating planned records in the transaction, you also have the 'Status-relevant' option.

Multi-level payment methods:
For incoming or outgoing payment methods, multi-level payment methods can be defined. These payment methods are also available for correspondence forms. The output occurs using text element /E 1200. You will find further details in the SAPscript form documentation for F_TR_CONFIRM_ALL.

Check function for Customizing:
Im Customizing under 'Assign forms', there is a check function in the MM, FX and DE areas that can be called up at the push of a button.

Installation information

From Release 4.5A, correspondence generation is based on planned records created when creating, changing, reversing, etc. due to Customizing settings and standing instructions correspondence. For transactions created prior to the upgrade and for whom no correspondence was generated, it is necessary to create planned records.

Report RFTBCO04 can be used for this purpose. You can carry out a test run to display the planned records determined. SAP, however, recommends that all correspondence is carried out prior to the upgrade if possible, thus not using RFTBCO04.

TXBHW - Original Tax Base Amount in Local Currency   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4081 Date: 20240523 Time: 071042     sap01-206 ( 101 ms )