SAP ABAP IMG Activity _FICAINK_ALE (Settings for ALE Business Process)
Hierarchy
☛ FI-CA (Software Component) FI-CA
   ⤷ FI-CA (Application Component) Contract Accounts Receivable and Payable
     ⤷ FKKB_DM (Package) Contract Accts Receivable and Payable - Dispute Management
IMG Activity
ID _FICAINK_ALE Settings for ALE Business Process  
Transaction Code S_KK4_74002777   (empty) 
Created on 20040206    
Customizing Attributes _FICAINK_ALE   Settings for ALE Business Process 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _FICAINK_ALE    

Use

You make these settings if you use a multiple system scenario for Debt Recovery Management. In these scenarios you use one system (this system) for Contract Accounts Receivable and Payable (Financial Accounting) and this is separate to the system for collection case processing.

Requirements

Standard settings

Activities

All of the settings described below are in Customizing for Application Link Enabling (ALE) (transaction SALE).

  1. Create a logical system in each system and assign it to a client.
  2. Create a relevant RFC destination in each system.
  3. In each system, define an RFC destination for method calls:
    Note the following in the system for Contract Accounts Receivable and Payable (Financial Accounting):
    1. Define a standard destination for BAPI calls
      When you create a collection case in financial accounting, before the system creates the IDoc it synchronizes with the system for collection case processing to perform a simulation run. For this simulation the system needs a standard destination for BAPI calls.
    2. Define a standard destination for dialog calls
      When you display a collection case in financial accounting, the financial accounting system calls up the collection case display in the system for collection case processing. To do this the financial accounting system needs a standard destination for dialog calls. Make sure that this RFC destination uses a dialog user. Otherwise dialog calls are not possible.
  4. Generate the partner agreement.

Example

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
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 _FICAINK_ALE 0 I500000220 Public Sector Contract Accounting 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20040206 
SAP Release Created in 472