SAP ABAP Data Element TB_RKLAMMER_DEBTTR (Classification Number for Finance Projects)

Hierarchy

☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FS-CML (Application Component) Loans Management
     ⤷ FVVD_DEBTTR (Package) Borrower Change Without Capital Transfer

Basic Data

Data Element	TB_RKLAMMER_DEBTTR
Short Description	Classification Number for Finance Projects

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	RANL
Data Type	CHAR	Character String
Length	13
Decimal Places	0
Output Length	13
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☑
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Fin.Proj.
Medium	15	Finance Project
Long	20	Finance Project
Heading	13	Finance Proj.

Documentation

Definition

The finance project number groups together several loans for one main borrower for the purpose of controlling the incoming payment distribution and the dunning procedure. For reasons of data consistency, the system does not permit the grouping together of more than one main borrower under one finance project number.

The borrower change must guarantee this determining factor at every processing stage.

Therefore, the following rules need to be observed:

• If you enter a borrower change for one loan in a finance project, the system forces a borrower change to be entered for all of the loans in the finance project.
• This rule continues in the same way for the other statuses of a borrower change, meaning that the execution of a borrower change for one loan leads to the execution of all the other loans and so on.
• The release procedure is an exception, this is operated without referring to the finance project.

For the online processing of the borrower change this means that:

• You can start processing a borrower chnage for a loan in a finance project from any point in the finance project. The other loans in the finance project are worked through in ascending order and after reaching the highest loan number, the system begins at the smallest number.
• You cannot process just one borrower change for a loan in a finance project. The function selection for the borrower change forces the processing sequence mentioned above. The buttons "Not Finance Project Case" have been replaced with others that clearly indicate, by means of an arrow, how you are to required to continue processing. For example, Execute Next Loan.
• The data consistency factors that apply to the main borrower of a finance project lead to other consistency factors for the borrower change. The new main borrower, the reason for the borrower change and the transfer date can only be entered or changed in the business operation in which the processing was started.
• The remaining data, in particular charges, can be entered in a different order.
• The release workflow is unaffected by the data consistency factors and can be operated at the level of individual business operations, meaning that each business operation can be released individually. However, the release of all business operations for all loans in a finance project is a prerequisite for the execution of a borrower change.
• If you include a loan in a finance project retrospectively, by altering the finance project number in the loan master data, the corresponding validations in the loan master data ensure that these consistency factors are observed.

These limitations do not apply to loans without a finance project number or finance projects that only contain one loan.

History

Last changed by/on	SAP	20020219
SAP Release Created in	463_20