Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-DP (Application Component) Transaction Data Pool⤷
JBDC (Package) Customizing IS-B Data Pool
IMG Activity
| ID | SIMG_CGJB01JBLC4 | Transfer Category 009: Loans |
| Transaction Code | S_ABA_72000080 | IMG Activity: SIMG_CGJB01JBLC4 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC4 | Transfer Category 009: Loans |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC4 |
General Information on the Transfer Category 'Loans'
In contrast to transactions or account turnovers, a single loan is transferred in several records rather than just in one record.
Receiver Structure
The receiver structure (JBIUDAR) for loans transfer is comprised of four tables: VDARL (Master), VZZKOKO (Condition header), VZZKOPO (Condition item), and VZZKOPA. Only one of the three parts in the receiver structure may be filled at a time. Each transferred data record must be given a mode. The mode indicates whether the data record is to be stored in the database for the first time (Insert mode = I) or changed (Update mode = U).
Required/Optional Fields
Required/optional fields are found in Customizing. You can influence their behavior using the field control found there (in Customizing). Fields that could be derived (an item from a header, for example) still have to be specified so that the header or item can also be delivered independently (that is why the fields GSART and SANLF always have to be delivered, for example).
Header and Item Structure
All data records for a loan must be delivered consecutively. Data records for different loans cannot be transferred in mixed order.
Within a single loan, there is also a fixed sequence to follow. First, transfer the master data of the loan (table VDARL). Next, transfer the condition header (table VZZKOKO). Finally, deliver one or more condition items (table VZZKOKO). Note: You do not always have to deliver all data records (master data, header and items) for a loan. This depends on what the transfer is for (settlement, type one cash flow disturbance, or rollover).
It is only possible to transfer the master of a loan in the case when no other parts have already been transferred.
A loan can only be accessed once per transfer.
Note that cash flows can be generated when transferring loans. However, this is only the case if a financial object has already been created for the loan. The following table shows which cash flow is generated.
Transfer of Mode Action
Master data I No cash flow
Condition header I Rollover
Condition item I Settlement or type I cash flow disturbance (*)
Master data U No cash flow
Master data and U Rollover
Condition header I
Master data and U Settlement or type I cash flow disturbance (*)
Condition header U
Master data and U Settlement or type I cash flow disturbance (*)
Condition item I/U
Condition header U Settlement or type I cash flow disturbance (*)
Condition item U Settlement or type I cash flow disturbance (*)
|
(*): A settlement cash flow is generated until final settlement has taken place. Once the loan has been finally settled, a type one cash flow disturbance/activity is determined.
Provided the information delivered for a loan is correct, the individual data records are transferred to the database according to their mode (Insert/Update). If appropriate, a cash flow is generated during the transfer.
Pay special attention to the following aspects:
- The system must have all relevant parts (master data, condition header and items) for a loan. If some parts are not delivered in the transfer, the system must already have access to those parts.
- The delivered condition headers and items are not completed any further. Make sure all relevant entries are transferred.
- If a cash flow disturbance is calculated, you must transfer the date of this disturbance with the first data record for the loan. You can prevent the system generating a cash flow disturbance by setting the SNOLEIS indicator in the first data record for the loan.
- If you want to roll over a loan, the condition header that is to be transferred contains information about the capital which is to be rolled over (commitment capital - repayments).
- A loan may only be rolled over after it has been finally settled.
- Once the loan has been rolled over, you must not change the old information (condition header and items).
- When partial waivers are transferred, the amounts are not checked. This means that you have to check for consistency yourself.
Identification of Master, Header or Item Data Records:
Filled fields Unfilled fields
Master DGUEL_KK
Master DGUEL_KP
Header DGUEL_KK DGUEL_KP
Item DGUEL_KK
Item DGUEL_KP
Note that the external loan number is a required field for each record, and is used for identification purposes. You therefore need to make sure that there is a 1:1 relationship between the loan and the external loan number.
Conventions
A master part can have several header parts. Each header part can in turn have several item parts. This means that there is a 1 to N to N relationship between master, header and item. Both the insert and the update functions are possible, although a combination of insert and update is not permitted for loans.
Each loan must have an external number. This number uniquely identifies the loan in the legacy system and in the SAP datapool.
A loan may only be transferred once per transfer.
Special Features
Number assignment takes place for the following fields within external data transfer:
Data record Field Meaning
Master RANL Contract no. (internal)
Master SOJEKT Object no. (internal)
Header RANL Contract no. (internal)
Item RANL Contract no. (internal)
Both internal and external number assignments are possible for the internal contract number. If the RANL field in the insert mode is initial then an internal number assignment takes place. If, however, the RANL field and the RANLALT1 field contain the same number, an external number assignment occurs.
In a test run there is no cash flow generation.
Transfer of Formulas for Items of Interest Rate Terms
Formulas for items of interest rate terms are to be transferred with term items.
To ensure that the formula arrives correctly in the system the following rules must be adhered to:
- The formula is transferred with the term item in one record.
- The formula can have up to 4 variables (V1 through V4). The exact number of variables depends on the definition of the formula. The 'fixed' values (interest rates) are assigned to the fields PKOND_V1 through PKOND_V4.
- The reference interest rates arrive on the other hand in the fields SZSREF_V1 through SZSREF_V4. The name of the formula (standardly 0001, 0002, and 0003) is to be entered in the field SFORMREF. The fluctuation margin for a reference interest rate is entered in the fields PFLUCHT_V1 through PFLUCHT_V4.
- It is important to note the following: The thresholds are transferred in the fields SZSREFMIN, SZSREFMAX, PKONDMAX, PKONDMIN. In the online transaction, it is also possible to control the rounding category. The rounding category unit is transferred in the field PRUNIT. The information about the rounding category is transferred in the ROUND field. If it is empty, it is rounded commercially. If it contains '+' it is rounded up. If it contains '-' then it is rounded down.
Interaction with Other Transfer Categories
- Cash flow: Disbursements as part of the transfer of cash flows may only be made once the loan has been transferred.
- Financial objects: The corresponding objects may only be transferred after the loan has been transferred.
Loan Partner
A business partner must exist in the system for each loan. If partner administration is used, either the internal partner number (field RDARNEHM) or the external partner number (field RDAREXT) must be delivered.
If no partner is delivered, the system inserts a standard business partner. This standard business partner must be created by the user. You can identify the standard business partner by the 'ISB-FIX' string in the Surname field (NAME1). The standard business partner is to have the role "borrower", and a 'default' address indicator. Make sure that only partners already entered in the system are specified.
Check Concept
Only check level 3 is used for the transfer category 'Loans'. Even if you set another check level, it will always be interpreted as 3.
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CGJB01JBLC4 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20000118 |
| SAP Release Created in |
