SAP ABAP IMG Activity OALE_DSTSCN_CREDIT (Distributed Credit Management)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ FBD (Package) Customers
IMG Activity
ID OALE_DSTSCN_CREDIT Distributed Credit Management  
Transaction Code S_ALR_87008563   IMG Activity: OALE_DSTSCN_CREDIT 
Created on 19981222    
Customizing Attributes OALE_DSTSCN_CREDIT   Distributed Credit Management 
Customizing Activity OALE_DSTSCN_CREDIT   Distributed Credit Management 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OALE_DSTSCN_CREDIT    

Distributed Credit Management

The system supports an ALE business process in which several local SD systems carry out active credit management against a central FI system.

An A/R summary is created in the FI system for this purpose. This contains a summary of all the credit information on a credit account (in a control area) necessary for the credit check in SD.

A program which you start periodically creates this A/R summary and sends it to the local SD systems based on the ALE customer distribution model. (Methods from the Business Object Repository are used for this). The data is received there and stored in the database. The checks called locally then do not run against the database (which is merely a mirror image of the local activities) but instead against the A/R summary and thus against all the open items. If the A/R summary is outdated, you can determine the current data in the FI system using a Remote Function Call.

For system performance reasons, it may make sense to run the SD credit check against this A/R summary even in a non-distributed system, as this way repeated reading of the open items is exchanged for repeated reading of the result of such an inquiry.

Data determined from the A/R summary in this way can be integrated in line layout variants in the credit overview. This makes it possible for the system to identify those credit accounts for which the credit check will report an error with the next incoming orders.

Example

Requirements

You have a central system on which FI runs and one or more systems on which SD runs locally. One of the following conditions must also be met:

1. The local SD systems must have separate credit control areas; there must not be any multiple assignments.

2. Different customers must be assigned to each of the local SD systems; there must not be any multiple assignments.

3. The credit checks in the local SD systems may only be run for FI data (such as statistical crdit limit checks without open credit values from SD, dunning levels, etc.).

ALE Customizing should be complete. You will find the specifications for maintaining the distribution model in the following section.

Maintaining the distribution model

  • Object name: DebtorCreditAccount (customer credit account)
  • Methods:
    • ReplicateStatus (replicate credit status)
    • GetOldestOpenItem (determine oldest open item)
    • GetHighestDunningLevel (determine highest dunning level)
    • GetOpenItemsStructure (determine open item structure)
    • GetDetail (determine master data)

Maintaining partner profiles

  • Message type: cresta
  • IDoc type (base type): cresta01

Standard settings

Recommendation

Activities

  1. Maintain table T000CM in the system in which central FI runs as follows.
    In the Financial Accounting Implementation Guide, go to Accounts Receivable and Accounts Payable and choose Credit Management -> Credit Control Account -> Define Preliminary Settings for Credit Management.
    Select the Create A/R summary field.
    You can find more information in the F1 help for the respective fields.
  2. Maintain tables T000CM and T691F in all systems in which local SD runs as follows:
    In the Financial Accounting Implementation Guide, go to Accounts Receivable and Accounts Payable and choose Credit Management -> Credit Control Account -> Define Preliminary Settings for Credit Management.
    Leave the Create A/R summary field blank.
    Select the Read A/R summary field.
    You can find more information in the F1 help for the respective fields.
  3. In the Sales and Distribution Implementation Guide, choose Basic Functions -> Credit Management/Risk Management -> Credit Management -> Define Automatic Credit Control.
    There maintain the Financial Accounting/old A/R summary checks. You can find more information in the F1 help.

Further notes

You distribute the A/R summary using program RFCMCRCV. You can find more information in the program documentation.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
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 OALE_DSTSCN_CREDIT 0 HLB0009110 Cross-Application Components 
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
T000CM S - Table (with text table) SM30 FI_ALE1 Distributed Credit Management 
History
Last changed by/on SAP  19990115 
SAP Release Created in