Hierarchy

⤷

⤷

IMG Activity
ID | DM_ALE_RFC_FI | Prepare Accounting System |
Transaction Code | S_SE3_50000121 | (empty) |
Created on | 20030322 | |
Customizing Attributes | DM_255MKA | Attribute: Critical Interface Realization |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | DM_ALE_RFC_FI_DC |
Use
You make these settings if you use a multi-system scenario for SAP Dispute Management. This means that you are using one or more systems for accounting that are separate to the system for dispute case processing.
Requirements
You have created a logical system for each of the following systems:
- For each accounting system involved
- For the system for dispute case processing
You have created the appropriate RFC destinations.
Standard settings
Activities
- Define a standard destination for BAPI calls
If you create a hyperlink Dispute Case in accounting, before creating the IDocs, the system synchronizes with the system for dispute case processing in order to carry out a simulation run. For this simulation, the system needs a standard destination for BAPI calls. - Define a standard destination for dialog calls
When you display a dispute case in accounting, the accounting system calls up the display of the dispute case in the system for dispute 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.
You make both settings in Customizing for your accounting system in the area Application Link Enabling (ALE) under Define RFC Destinations for Method Calls.
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 | 20040322 |
SAP Release Created in | 200 |