Hierarchy

⤷

⤷

IMG Activity
ID | POC_INSTR_NAV_BOR | Set Up Navigation to Remote BOR Objects in Process Monitor |
Transaction Code | S_BT6_28000087 | (empty) |
Created on | 20110713 | |
Customizing Attributes | POC_INSTR_NAV_BOR | Set Up Navigation to Remote BOR Objects in Process Monitor |
Customizing Activity | POC_INSTR_NAV_BOR | Set Up Navigation to Remote BOR Objects in Process Monitor |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | POC_INSTR_NAV_BOR |
Use
In this Customizing activity, you define the technical parameters for Remote Function Call (RFC) destinations, and assign the RFC destinations used for synchronous BAPI calls and for calling dialog methods in other systems. You do this so you can navigate from the Process Monitor to remote Business Object Repository (BOR) objects.
You must maintain RFC destinations for each remote logical system that supports navigation from the Process Monitor.
Requirements
You have determined which logical systems support navigation from the Process Monitor. This will be all or some of the systems that allow federation with the local system.
Standard settings
No default settings are delivered.
Activities
- Define all logical system that you want to navigate to using the BOR navigation.
To define a logical system, see Customizing activity Define Logical System.
- Maintain an RFC destination for each logical system to which the Process Monitor navigates.
To maintain RFC destinations, see the Customizing activity Create RFC Destinations.
- For each logical system, assign the RFC destination to the logical system as a Standard BAPI destination.
To assign RFC destinations used for synchronous BAPI calls and for calling dialog methods in other systems, see the Customizing activity Determine RFC Destinations for Method Calls.
Example
For the process chain "lead to cash", a local system monitors the order to cash process, while lead processing is monitored in a remote system. You have set up federation between the two systems.
To be able to navigate to the remote leads that are visible in the remote system, you must do the following:
1. Create an RFC destination of the remote lead processing system.
2. Assign that RFC destination to the logical system of the lead processing system.
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | POC_INSTR_NAV_BOR | 0 | BT60000013 | Process Orchestration for Built-In Processes |
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_TBDLS | V - View | SM30 | ALE | Maintain Logical Systems | ||
SYSDUMMY | D - Dummy object | SM59 | Configuration of RFC Connections | |||
ALEDUMMY | D - Dummy object | BD97 | Assign RFC Destinations for Synchronous Method Calls |
History
Last changed by/on | SAP | 20121126 |
SAP Release Created in | 731 |