Hierarchy
FINBASIS (Software Component) Fin. Basis⤷
FIN-FSCM-COL-COL (Application Component) Basic Functions⤷
UDM_P2P (Package) Promise to Pay
IMG Activity
| ID | COL_ALE_RFC_FI | RFC Destinations for Method Calls in the Accounting System |
| Transaction Code | S_SE3_50000193 | (empty) |
| Created on | 20040301 | |
| Customizing Attributes | COL_255MKA | Attribute: Critical Interface Realization |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | COL_ALE_RFC_FI_DC |
Use
If you run Collections Management and Accounts Receivable Accounting (FI-AR) in separate systems, you have to define RFC destinations for calls to the Collections Management system in the Accounts Receivable Accounting (FI-AR) system.
If you use SAP Dispute Management in a multiple system scenario, you also have to run SAP Collections Management in a multiple system scenario.
Requirements
You have created a logical system for the following systems:
- For the accounting system
- For the Collections Management system
You have created the appropriate RFC destinations.
Standard settings
Activities
- Define a standard destination for BAPI calls
When you create a promise to pay or dispute case, the Accounting system synchronizes with the Financial Basis system for an internal test run. To do this, the system needs a standard destination for BAPI calls. - Define a standard destination for dialog calls
To display the case from the Accounting system, the system requires a standard destination for dialog calls. Make sure that this RFC destination uses a dialog user.
When you create the RFC destinations, check whether the option of trusted/trusting system relationship is relevant for you. For more information about trusted/trusting system relationship, see the SAP library under Key Areas of SAP NetWeaver -> Application Platform -> Connectivity -> Components of SAP Communication Technology -> Classic SAP Technologies (ABAP): RFC -> RFC Programming in ABAP -> Trusted System: Maintain Trust Relationships between R/3 Systems.
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 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20040327 |
| SAP Release Created in | 300 |
