Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-TM (Application Component) Transaction Manager⤷
FTAC (Package) R/3 customizing for Treasury money, forex, forward
IMG Activity
| ID | TRFDUE_JBIUDAB | Loans Flow Data |
| Transaction Code | S_ALR_87007958 | IMG Activity: TRFDUE_JBIUDAB |
| Created on | 19981222 | |
| Customizing Attributes | TRFDUE_JBIUDAB | Loans Flow Data |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | TRFDUE_JBIUDAB |
You can transfer the following loan flow data via external data transfer:
- Subledger
- G/L for balance sheet postings, open items (overpayment and underpayment), advance payments and periodic revenue postings to amortize loan discounts
G/L account balance
When you transfer external data, the loan balance you transfer must be updated in the loans G/L account. There are two alternative procedures:
- The loan balance (flow with cateogry MIGR) on the key date for migration is posted to the G/L account. All other past flows can be delivered, but are only written to the subledger.
- If you transfer the history, only a restricted number of flows are transferred. (For example, reversed flows are not transferred.) The ALT_BUCHEN field must be set for all past flows that are transferred. This means that all past flows are posted to G/L accounts. The sum of the disbursements minus the sum of the repayments then gives you the transfer balance. No flow with the category MIGR is required.
When you transfer data from R/2, the first procedure is used.
Control of transfer data
You control which records are transferred via Record categories.
Other important control fields in the receiver structure are:
- ALT_BUCHEN (also post flow in the G/L)
- SZEGEN (generate incoming payments automatically)
- DBUDAT (posting date in document)
- DBLDAT (document date in document)
Requirements
The transfer category for loan flows is 50. There is a fixed link between transfer category 50 and transfer structure JBIUDAB.
You are only allowed to transfer loans flow data in Insert mode.
You must always transfer at least one flow record with the category disbursement. This is necessary to set the contract status to loan disbursed. In turn, this status has far-reaching effects when you go on to process the loan.
Standard settings
Updating the subledger
All the loans flow data you transfer is put into the subledger and is visible in the cash flow (except for flows with the category MIGR). Where the flows have already been cleared, it is advisable to let the system generate incoming payments automatically (see below for further details).
Updating the general ledger
The cleared flows can be transferred to the general ledger as well as to the subledger. To do this, however, you will need to set the indicator for the field ALT_BUCHEN in the record you want to transfer (see below for further details).
In most cases, besides updating the subledger, you will need to post the position transferred to the corresponding G/L account. To do this, you need to deliver a separate transfer record. The flow type of this record must belong to the flow category MIGR. The record contains the total transfer balance for the loan in question.
When you define the posting rule, you should make sure that flows can be debited to the relevant G/L account (loans given). The offsetting entry is posted to a clearing account.
Condition types or flow types
You can include condition types and flow types in the transfer rules.
Condition types must always be delivered with condition-based flows (e.g. interest, annuity repayments etc.). The transfer program then determines the corresponding flow type automatically.
If flows are not condition-based (e.g. full or partial disbursement), the flow type (field SBEWART) must be delivered to the transfer program.
Loan discounts
Discounts which have been amortized in the legacy system can be transferred. For this, you need to set up a transfer rule for the flow type (field SBEWART). This transfer rule must contains the flow category EAAR (normal discount amortization). The field SREFBEW in the transfer record indicates the flow type (TA) of the discount. You also need to specify the period over which the discount was amortized.
Open items (overpayment and underpayment)
You differentiate open items from other flows in the subledger via the record type. Various fields are available, all of which have the prefix 'OP_'. Fields for controlling the number of decimal places have the prefix 'N_OP_'. These special fields for handling open items contain the amounts actually paid.
When you transfer the flow data, the system updates the flow data in the subledger and also posts the open items to customer accounts.
Advance payments
You differentiate advance payments from other flows in the subledger via the record category. As for disbursements, you need to specify the flow type in the transfer structure. The 'OP_' fields are not used here. Advance payments are treated like cleared items (or flows), in other words, they appear in the subledger. In addition, the advance payment is credited to the customer.
Further notes
- Determine which fields are compulsory using the transaction for checking required/optional field control.
- Always fill the BUKRS and RANL fields
- Use transfer program TR_DBEW with send structure J11SDAB if you do not want to generate your own send structure and are able to deliver the transfer data in the format of send structure J11SDAB. The corresponding transfer rules are available.
- To write past flows relevant to G/L accounts to G/L accounts, fill the ALT_BUCHEN field
- To generate an incoming payment automatically for the transferred flow, set the SZEGEN field. It may be best to define a constant in the transfer rules
- To only transfer the capital balance on the migration key date to the general ledger, create flow types with the flow category MIGR
- Note the difference between condition types and flow types when you define the transfer rules
Business Attributes
| ASAP Roadmap ID | 152 | Design data acquisition |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | TRFDUE_JBIUDAB | 0 | HLA0100062 O HLA0100104 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20000801 |
| SAP Release Created in |
