Ansicht
Dokumentation

SIMG_CGJB01JBLC44 - Transfer Category 044: Collateral Provisions

ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

You use this transfer category to transfer global collateral, single-transaction-related collateral and collateral agreements as collateral provisions into the SAP system.

A collateral provision is described by at least two data records: a header record and an item record.When you are transferring more than one collateral provision, you need to transfer the data in a particular sequence. You have to transfer the header, and then at least one corresponding item.

Example:

Header for 1st collateral provision -> item for 1st collateral provision -> header for 2nd collateral provision -> 1st item for 2nd collateral provision -> 2nd item for 2nd collateral provision -> header for 3rd collateral provision -> item for 3rd collateral provision -> and so on.

An exception to this rule are collateral agreements. You can transfer these without any items.

Each data record transferred to SAP Banking is interpreted as either a header or an item, depending on which fields are filled. The receiver structure, and hence also the required/optional field control, differs depending on the level of the collateral provision (global collateral, single-transaction-related collateral, or collateral agreements as collateral provision). You can display the required/optional field control for the individual levels for the header structure and item structure respectively.

In the case of single-transaction-related collateral, in addition to the required and optional fields there are also dependent fields:

SIGEBER: This field is used to contain data about the provider of the collateral. It is either a required or optional field depending on the type of collateral (tangible/personal). If the collateral is personal collateral then this field is a required field. If the collateral is tangible, then it is an optional field.

RANL: This field contains the security ID number or contract number. It is only a required field if the collateral provided is in the form of securities. Otherwise this field must not be filled. The same applies for the fields NORDEXT (external order number) and NORDER (number of the order).

RFHA: This field contains the number of the financial transaction to which the collateral is to be assigned. It is a required field if you enter additional information about this transaction. Otherwise this field must not be filled.

RIDEXT: This field contains the external number of the risk object. It is a required field if the collateral is to be assigned to an external risk object.Otherwise this field must not be filled. The fields RIDXRT (internal number of the enhanced risk object), RIDBSTDEXT (external ID of the position of risk objects) and RIDBSTD (internal number for the position of risk objects) in turn become required fields depending on RIDEXT.

VTNUM: This field contains the number of the variable transaction. It is a required field if the collateral is to be assigned to a variable transaction. Otherwise this field must not be filled.

FAZNR and FAZID: If you want to assign the collateral to a facility, you have to specify either the external or the internal identifier for the facility. Note, however, that you to fill one of the fields only.If the collateral is not to be assigned to a facility, then you must leave both these fields empty.

MODE: In the mode field you specify whether the collateral is new (enter I for Insert) or whether the data refers to a change to an existing collateral item (enter U for Update). If you enter D for Delete in the mode field, the system deletes the item record only. It is not permitted to enter D in the header, as you cannot delete collateral provisions.

BESANT and BESANTP: These fields are for the proportion of collatera in percentage (economic) and the proportion of collateral in percentage (political). These are required fields if the collateral is percentage collateral. You can fill either one field or both fields. If the collateral is not percentage collateral, these fields must be empty.

SSIWHR: This field contains the currency of the collateral and is only required if the collateral is an amount.If the collateral is percentage collateral or securities, then this field must be empty.

BSIWHR and BSIWHRP: You always have to enter the amount of collateral.You can, however, enter either the economic amount of the collateral only, or the political amount of the collateral only, or both amounts.

RANL: This field contains details from RM: the security ID number or contract number. It is only a required field if the collateral provided is in the form of securities. Otherwise this field must not be filled.

ASTUECK: This field contains the number of units in the case of unit-quoted securities. It is only a required field if the collateral provided is in the form of securities. Otherwise this field must not be filled.

You have the option of first carrying out a test run for the EDT of collateral provisions. During this test run there is only a rudimentary check (for example, whether a sender file exists, whether the output file can be written). The data is checked on a business level (for example, whether the business partner or the transaction, to which the collateral is assigned, actually exists in the system) only during the update run. It is only then that, if relevant, the corresponding error messages appear in the EDT log.

The following note applies for the prototype functions that are developed as part of a project solution and that are not yet available on the market:

Collateral provisions at facility level have to have different priorities if they are assigned to the same facility.

The transactions, to which the collateral is assigned, must already exist in the system.

This transfer category is only relevant for the Default Risk and Limit System component as collateral provisions can only be taken into account here.

So that collateral can be taken into account, after you have transferred the collateral, you then have to create the corresponding financial objects. You can also do this using the EDT of financial objects.

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 6632 Date: 20240523 Time: 223406     sap01-206 ( 154 ms )