## 13.2.8.3.4  Communication Destinations
## Use
The following table shows an overview of the communication destinations that you need for SAP Collections 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 system that contains SAP Collections Management.
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: COL2FIN_DIAG | This destination is used for dialog calls that take place from the Collections Management system to the Accounts Receivable system by means of RFC.                          | RFC user (dialog) in Receivables Proc- essing Role: SAP_FIN_FSCM_COL_AR_RFC_DIALOG Contains the authorizations for a user with which the navigate to receivables processing from the worklist by means of RFC. The authorizations permit the following activities: Display of invoice data Display of payment data Display of invoice history Creation, change, or display of a con-                      |
| Example: COL2FIN_COMM | This destination is used for synchro- nous and asynchronous (IDocs) BAPI calls that take place from the Collec- tions Management system to the Ac- counts Receivable system. | RFC user (communication) in Ac- counts Receivable Role: SAP_FIN_FSCM_COL_AR_RFC_COMM Contains authorizations for a user with which synchronous and asynchronous BAPI methods are called from the SAP Collections Management system in the Accounts Receivable system. An example of such a method is the automatic notification to Accounts Re- ceivable when promises to pay are con- firmed and voided. |
| Destination           | Description                                                                                                                                                              | User, Authorizations                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Example: FIN2COL_DIAG | This destination is used for dialog calls that take place from the Accounts Re- ceivable system to the Collections Man- agement system by means of RFC.                  | RFC user (dialog) for collections man- agement functions Role: SAP_FIN_FSCM_COL_RFC_DIALOG Contains authorizations for a user with which dialog methods are called in the SAP Collections Management system from the Financial Accounting system by means of RFC. For example, navigation from receiva- bles processing to the detail display of the promise to pay or dispute case.                                                                                                                                                                                |
| 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 Collections Management system. | RFC user (communication) for collec- tions management Role: SAP_FIN_FSCM_COL_RFC_COMM Contains authorizations for a user with which synchronous and asynchronous methods are called in the SAP Collec- tions Management system from the Fi- nancial Accounting system. For example: Posting of IDocs with data from Finan- cial Accounting Creation of dispute cases, promises to pay, customer contacts, and resubmis- sions Reading of attributes of dispute cases, promises to pay, customer contacts, and resubmissions for display in receiv- ables processing |
## Possible additional necessary destinations
If you connect several FI systems in a multiple-system scenario and use the connection of Unified Key Mapping Service to SAP Process Integration (UKMS connection to SAP Process Integration ) to resolve conflicts when assigning numbers, you also need to set up the following destinations:
- Calls from the of accounts receivable system to the system of SAP Process Integration (PI system)
- Calls from the Collections Management system to the PI system
For additional information, see Customizing of SAP Collections Management under Basic Settings for Collections Management Business Partners Master Data Distribution for Several FI Systems , if you have activated business function FSCM Functions 2 ( FIN\_FSCM\_CCD\_2 ).
For additional information about the security aspects of the CRM Middleware that you can use as a tool for master data replication, see the Security Guide for SAP Customer Relationship Management .
## 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 Collections Management , RFC calls take place from the Accounts Receivable system to the Collections Management 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 the 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 Collections Management system and you want to configure the RFC destination used for sending IDocs so that it uses the trusted/trusting system relationship and carries out the RFC calls in the target system with the current user from the calling system:
IDocs are sent to the Collections Management 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 Collections Management 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 promises to pay, in the Collections Management system.