Hierarchy

⤷

⤷

IMG Activity
ID | ACCLOGICSYS_D | Assign RFC Destination |
Transaction Code | S_SE3_50000012 | (empty) |
Created on | 20020618 | |
Customizing Attributes | ACCLOGICSYS_D | Assign RFC Destination |
Customizing Activity | ACCLOGICSYS_D | Assign RFC Destination |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ACC_LOGICSYS_D_DC |
Use
In this IMG activity, you assign an RFC destination to a logical system ID (locally).
Components that work together with the logical system ID then use this RFC destination to communicate and work with remote components. If no RFC destination is entered, the system assumes that the component in question is available locally.
Requirements
It is not necessary for a logical system ID to have been entered before an RFC destination can be assigned.
This has the advantage that this setting can be made in test systems and productive systems before Customizing has been transported.
Standard settings
Activities
Make a new entry by choosing an existing logical system ID or creating a new name.
Assign a valid RFC destination. A check is made to ensure that the destination is functioning.
If the RFC destination field is left empty, the component in question is available locally.
Example
Business Accounting:
Assign an RFC destination to the logical system ID ACC_BW.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_ACCLSYS01 | V - View | SM30 |
History
Last changed by/on | SAP | 20021001 |
SAP Release Created in | 1.0B |