Kontakt

Ansicht
Dokumentation

Derivation of the Default Risk Rule and the Limit Product Group ( RELNBANK_462_CL_DERIARR )

Derivation of the Default Risk Rule and the Limit Product Group ( RELNBANK_462_CL_DERIARR )

General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Derivation of the Default Risk Rule and the Limit Product Group

Use

  • Data fields DKLBEG (transaction start date for CL) and DKLEND (transaction end date for CL) have been changed to DARBEG (transaction start date for CL counterparty/issuer risk) and DAREND (transaction end date for CL counterparty/issuer risk)
  • The limit product group can also be derived in this way.
  • As from this Release, the system is able to derive the default risk rule for all transactions. The corresponding assignment table in Customizing is no longer taken into account during determination of the default risk rule and limit product group. For this reason one derivation strategy is to be stored for all transactions.
  • In particular for BCA accounts, risk objects and variable transactions, you need to store not only a derivation for the default risk rule, but also for the limit product group.
  • If the previous assignment tables are still to be used, then you need to link these by table access to the derivation strategy. In addition, the limit parts of the financial objects for the corresponding transactions need to be updated. The system contains a service report in the application menu for this purpose.
  • The user exit interface has changed in such a way that the importing parameter I_OBJECT is categorized dynamically. You can find more details in both the function module documentation and user exit documentation.
  • In addition, the user exit interface is enhanced by data from the financial object. This structure is only filled where integration is used. If financial object integration is not used, then financial object data in structure I_OBJECT is available.

,,

Effects on Existing Data

The changes made to the data fields require that you also change the existing settings.

For BCA accounts, risk objects and variable transactions, you also need to store a derivation strategy, provided that you have already stored a derivation rule for all other transactions.

The same applies for single transaction-related collateral.

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

In the case of single transaction-related collateral, see also the information on Conversion of Master Data.






Addresses (Business Address Services)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2793 Date: 20240420 Time: 045219     sap01-206 ( 50 ms )