## 13.2.8.2.4  Communication Destinations
## Use
The following table shows an overview of the communication destinations (RFC) that you need for SAP Dispute Management if you use it in a multiple-system scenario. You can use these communication destinations to establish communication between the Financial Accounting system and the Dispute Case Processing system.
You can assign names for your RFC destinations as required. The names of the RFC destinations that are specified in the table are merely examples. The destinations are not delivered in the standard system; you need to create them yourself.
| Destination          | Description                                                                                                                                                                 | User, Authorizations                                                                                                                                                                                                                                                                                                                                                                                                                                      |
|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Example: DM2FIN_DIAG | This destination is used for dialog calls that take place from the Dispute Case Processing system to the Accounts Re- ceivable system by means of RFC.                      | RFC user (dialog) in Accounts Receiv- able Role: SAP_FIN_FSCM_DM_AR_RFC_DIALOG Contains the authorizations required by a user to call SAP Dispute Management dialog methods using RFC from the Dis- pute Case Processing system in the Ac- counts Receivable system. Examples of such methods are includ- ing open items in a dispute case and navigating from a dispute case to a linked line item.                                                      |
| Example: DM2FIN_COMM | This destination is used for synchro- nous and asynchronous (IDocs) BAPI calls that take place from the Dispute Case Processing system to the Ac- counts Receivable system. | RFC user (communication) in Ac- counts Receivable Role: SAP_FIN_FSCM_DM_AR_RFC_COMM Contains the authorizations required by a user to call synchronous and asyn- chronous SAP Dispute Management BAPI methods from the Dispute Case Processing system in the Accounts Re- ceivable system. Examples of such methods are the au- tomatic write off of dispute cases and automatic notification of Accounts Re- ceivable when confirming and voiding cases. |
| Example: FIN2DM_DIAG | This destination is used for dialog calls that take place from the Accounts Re- ceivable system to the Dispute Case Processing system by means of RFC.                      | RFC user (dialog) in Dispute Case Processing Role: SAP_FIN_FSCM_DM_RFC_DIALOG Contains the authorizations for a user with which the DISPLAY method is called in the Dispute Case Processing system from the Accounts Receivable system by RFC. The role contains the authorizations necessary for displaying the dispute case.                                                                                                                            |
| Destination           | Description                                                                                                                                                               | User, Authorizations                                                                                                                                                                                                                                                                                                                                                                                                                               |
|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Example: FIN2COL_COMM | This destination is used for synchro- nous and asynchronous (IDocs) BAPI calls that take place from the Accounts Receivable system to the Dispute Case Processing system. | RFC user (communication) in Dispute Case Processing Role: SAP_FIN_FSCM_DM_RFC_COMM Contains the authorizations required by a user to call synchronous and asyn- chronous BAPI methods from the Ac- counts Receivable system in the Dis- pute Case Processing system. Examples of such methods are creating dispute cases from Accounts Receiva- ble and automatically changing dispute cases using clearing transactions in Ac- counts Receivable. |
## Set up RFC destinations for the ALE scenario
When you set up the RFC destinations for the ALE scenario, check whether the option of trusted/trusting system relationship is relevant for you. Using an RFC trusted/trusting system relationship between two SAP systems means that in the case of an RFC (Remote Function Call) from the trusted to the trusting system, no password is sent for the logon to the trusting system. You can configure the RFC destinations in such a way that the call in the target system occurs with the current user from the calling system without a password being specified or entered on the logon screen. This has the following advantages, for example:
- When changes to objects or data are logged in the called system, this logging takes place with the current user from the calling system. This makes it easier to track changes that occurred through RFC.
- You can assign individual authorizations to the users in the called system. As such you can differentiate which actions or functions are accessible to the user in the called system irrespective of the user.
With this procedure, you must create the users that are to be allowed to execute using RFC functions in the called system as well. Note that in the ALE scenario of SAP Dispute Management , RFC calls take place from the Accounts Receivable system to the Dispute Case Processing system and vice versa. A trust relationship between SAP systems is not mutual. This means that you can choose whether one system is to be designated as trusted for the other system and vice versa, or whether you want to define the trust relationship only in one direction.
In Customizing of ALE ( Application Link Enabling ), you can also define different RFC destinations for dialog calls, for BAPI calls, and for sending IDocs. As such you can also define an RFC destination for the dialog calls that use the trusted/trusting system relationship and use the current user from the calling system for the RFC calls in the target system, whilst you define an RFC destination for BAPI calls and for the sending of IDocs that does not use the trusted/trusting system relationship and in which you enter a communication user.
##  Note
Note the following if your Accounts Receivable system is known as a trusted system by the Dispute Case Processing system and you want to configure the RFC destination used for sending IDocs so that it uses the
trusted/trusting system relationship and the RFC calls in the target system with the current user from the calling system:
IDocs are sent to the Dispute Case Processing system from the Accounts Receivable system when items are cleared in the Accounts Receivable system, the clearing of items is reset, or partial payments are executed on items for which a promise to pay exists for the corresponding invoice. If the corresponding RFC destination uses the trusted/trusting system relationship, and carries out the call in the target system with the current user from the calling system, this means that the user triggering the clearing, reset of clearing, or partial payment must also be defined in the Dispute Case Processing system. You must therefore create all users who carry out clearing, resets of clearing, or partial payments in the Accounts Receivable system, and therefore affect dispute cases, in the Dispute Case Processing system.