SAP ABAP IMG Activity TR_LO_KOPIER (Copy Settings for Loans)
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 TR_LO_KOPIER Copy Settings for Loans  
Transaction Code S_ALR_87007879   IMG Activity: TR_LO_KOPIER 
Created on 19981222    
Customizing Attributes TR_LO_KOPIER   Copy Settings for Loans 
Customizing Activity TR_LO_KOPIER   Copy settings for Loans 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name TR_LO_KOPIER    

Important: Read the general information beforehand in the unit entitled Copying of Standard Customizing in Treasury.

Proceed as follows:

  1. Copy non-critical settings for Loans.
  2. Copy critical settings for Loans.

    Prerequisites for copying:

  • Company code 0001 exists in target client.
  • Currencies: DEM is defined as currency.

    Have all Prerequisites been met and has FI not been modified? If yes: you can copy the TR-critical settings.

  1. Make the following settings in FI in the target client manually:
    • Setting of Financial Assets Management Indicator to Active.
      • If customer payments from FI are to be confirmed for Loans, you must have set the 'Financial Assets Management Active' indicator in the global company code data.
    • Modification of Posting Keys
      • For Loans Accounting, it is necessary to change the field status of certain standard FI posting keys. To do this, you must set the Financial Assets Management field status group to optional entry. This entry ensures that when you create a document with the posting keys mentioned, the contract number, contract type and flow type are shown. This adjustment is necessary for the following customer posting keys: 01, 12, 15, 05, 17, 07. These posting keys are used for account determination in Loans.
      The change must be made in table TBSL in Customizing for the above-mentioned posting keys.
      Note: Document creation is influenced by this change.
    • Interest Calculation for Program on Interest in Arrears
      • The interest calculation program for interest on arrears requires some enhancements in Customizing so that it works properly with the Loans component.
      Set up an interest calculation indicator (e.g. VD) as the item interest calculation via Change interest calculation type - Overview.

      Under: Prepare calculation of interest in arrears, you make an entry for the interest calculation indicator (VD). In item selection, open and cleared items are marked. You must also make an entry for calendar type and tolerance days. Only debit interest is marked; this entry is also necessary for function module: OVERDUE_INTEREST_FOR_COND_ITEM. This function module provides the link to Loans management.
    • Activation of RW interface component VV
      • If you are posting on the customer-side (FI posting: 3), the VV component must be set as active in table TRWCA.
    • Enhancements to the Payment Program
      • To use the payment program, you must make certain Customizing entries for Loans for
      a.) Payment methods
      b.) Customer grouping keys
      c.) Payment blocking reasons.
      The necessary settings are described with examples.
      a.) Payment methods
      i.) Special payment methods for loan disbursement.
      As loan disbursement can never be cleared with other customer items, special payment methods must be defined with the Payment method for individual payment indicator.
      This definition is made in FI in the company code data of payment method definition. When creating the disbursement in the loan, you have to enter a payment method with individual payment in the transaction.
      Examples of payment methods:
      1. Check with individual payment (copy of payment method, check + Payment method for individual payment indicator in company code data).
      2 Transfer with individual payment (Copy of payment method, Transfer + indicator for individual payment in the company code data).
      ii.) Payment method for debit memo for alternative payers .
      The FI payment program checks the payment data of the customer in the case of debit memos and alternative payers (field 'Alternative payee' set in document and bank data maintained). To avoid parallel maintenance of bank data for customers and alternative payers, you can define an additional payment method that is a 'mixture' of a bank debit and debit memo.
      For this payment method, the Collection authorization indicator cannot be set but the 'Key in coding line' field must contain the ID for the debit memo. In Germany, this key is 05 as standard. This payment method is to be used for debit memos of alternative payments instead of payment methods for bank collections. (c.f. payment method for conditions).
      b.) Posting key
      Payments from the Loans area within a financial project, contract/ customer should be grouped together into one payment according to settings. the financial project, contract/customer are, therefore, specified in the assignment number of the FI document. The customer (c.f. Default customer) must have a grouping key of the following type so that the payments can be grouped together:

        Posting key.    01

        Text        Grouping according to finance project,

                Contract,

        Name        Description    Offset        Length

        Field 1        ZUONR        Assignment    18

These defined posting keys are included in the 'Customer' details.
c.) Payment block reasons
i.) Blocking of a customer item against further processing.
To do this, you must create a payment block with the 'Block against manual payment' attribute. Such a payment block is necessary when withholding outstanding receivables upon disbursement. You can set this payment block as a default in company code-dependent product types. ( c.f. Release Notes for product types).
ii.) Payment block for receivables from returned debit memos.
This payment block must not have the 'Block against manual payment' indicator. You can set a default once again in the company-code dependent product types. This payment block is automatically transferred from the product type to the new open item. This prevents a new collection of the receivable by the payment program before the cause of the returned debit memo has been determined. Otherwise, unnecessary charges are generated. A manual payment can, however, be made on these items. Maintain the following settings manually in LO in the target client:

    • Number ranges
      • Setting up a client via a client copy from client 000: The number range intervals are copied here. As maintenance of the
      intervals is necessary for the components to function, you must then check via the list whether the relevant intervals have been set up.
      - Loan number
      - Internal loan number
      - Collateral object number
      - Collateral value number
      - Land register number
      - Collaterals
      - Special arrangements
      - Rollover number
      - Conditon number (Activity management)
      - Document number for document header
      - Daybook number
      - General daybook number
      - Interested party
      - Activity number
      - Business operation
    • Setting of posting keys for residual items carried forward
      • In Loans, you can clear items via the Accounting interface. You must define posting keys in the SAP R/3 System for these residual
      items carried forward. Without this definition the loans posting forward interface cannot be run.

The necessary Customizing settings are described below.

To keep the necessary posting keys for residual items carried forward, new activities have been produced in the automatic posting of FI. The other necessary Customizing settings are described below:
Maintenance of T030B via SM31. Make the following entries:
i.) Double-click on 'Posting from the loans area'
ii.) The following entries appear:

    Group        ZAU Postings from the loans area

    Name                Activity        Account determination

    Residual item carried forward - Payment activity    ZA1

    Residual item activity - Sales relevant    ZA2

    Residual item carried forward - Neutral            ZA3

iii.) Double-click on each individual entry from ii.) and make the following entries:

    Activity        ZA1 Residual item carried forward - Payment activity

    Debit        05

    Credit        15

    Activity        ZA2 Residual item activity - Sales-relevant

    Debit        01

    Credit        11

    Activity        ZA3 Residual item carried forward - Neutral

    Debit        07

    Credit        17

  • Maintain Customer Defaults
    • For product types that should be posted on the customer side (FI posting : 3), you must set defaults for automatic creation of customers which are then specified to the customer master record when you create a customer. Alongside the reconciliation account and the payment
Business Attributes
ASAP Roadmap ID 251   Transport Customizing for Processes 
Mandatory / Optional 1   Mandatory 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 TR_LO_KOPIER 0 HLA0100074 O  
SIMG TR_LO_KOPIER 1 KFM0000007 Transaction Manager 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object TRCB 0000000001 Copy uncritical settings for Loans 
IMGDUMMY D - Dummy object TRCC 0000000001 Copy critical settings for Loans 
History
Last changed by/on SAP  20000718 
SAP Release Created in