Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI (Application Component) Financial Accounting⤷
FB_ICRC (Package) Cross-System Intercompany Reconciliation
Basic Data
| Data Element | FBICRC_RFCDEST |
| Short Description | Logical Destination (Specified in Function Call) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCDEST | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | RFCDES |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | RFC | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 5 | Dest. |
| Medium | 11 | Destination |
| Long | 15 | RFC Destination |
| Heading | 15 | RFC Destination |
Documentation
Definition
Standard name of an RFC destination.
Use
Dependencies
Example
Supplementary Documentation - FBICRC_RFCDEST0010
Use
Specify the RFC destination to be used when the user calls an interactive function from the reconciliation display. In the standard, only the function Display Document uses this RFC destination. You may want to use this RFC destination for your own functions (BAdI implementation) for calling the sender system of the data.
This RFC destination is usually defined without storing a user and password. This ensures that the user using the function also has a user with proper authorizations in the sender system.
Dependencies
Example
Supplementary Documentation - FBICRC_RFCDEST0020
Use
Specify the RFC destination to be used when the data selection program is executed.
Dependencies
This RFC destination is usually defined with a fixed user name and password to ensure that the data selection program can run without interruption (for example, a logon screen).
Example
Supplementary Documentation - FBICRC_RFCDEST0030
Use
Specify the RFC destination which is supposed to be used when the data is pushed back into the reconciliation system after data selection was triggered in the sender system.
Dependencies
There are no value help and no verification of the RFC destination available in the local system since the RFC destination will usually not be available in the sender system.
Example
You have a complex system structure with the following systems involved:
- Reconciliation System: ICS
- Sender System: SND
- XI System: XIS
You would like to use the option of asynchronously triggering data selection in the sender system from the reconciliation system for your company C1000. The details of the communication are set up in the XI system.
This means that you have an RFC destination specified for XIS in ICS. In XIS you specified that RFC calls from ICS involving company C1000 are supposed to be routed to SND. In SND you have to specify an RFC connection which will send the data back to ICS (either directly or via XI). This is the RFC connection you need to specify in this field of the customizing.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
