Ansicht
Dokumentation

_FICAINK_ALE - Settings for ALE Business Process

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

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.

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.

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 1791 Date: 20240523 Time: 153031     sap01-206 ( 40 ms )