Hierarchy
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net⤷
PM-WOC-MO (Application Component) Maintenance Orders⤷
/MRSS/SGE (Package) Multiresource Planning: Scheduling Engine
IMG Activity
| ID | /MRSS/C_ENG_DEST | Process Destinations of RCCF Engines |
| Transaction Code | /MRSS/92000166 | (empty) |
| Created on | 20090811 | |
| Customizing Attributes | /MRSS/C_ENG_DEST | Process Destinations of RCCF Engines |
| Customizing Activity | /MRSS/C_ENG_DEST | Process Destinations of RCCF Engines |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /MRSS/C_ENG_DEST |
Use
In this IMG activity, enter the destinations of the external engines in the Remote Control and Communication Framework (RCCF).
A destination in this case is not necessarily one alternative engine server. Multiple destinations can indicate the same engine server via their communication links.
Destinations are normally used to limit the number of runs per engine server and distribute them among several servers. The RCCF does not actually balance the load in this case. It simply distributes the runs equally among the existing destinations using the same priority and the same number of free remaining slots. The runs are distributed only among the destinations of the respective application.
If multiple destinations refer to the same server (and different applications), the RCCF still only includes the destinations that are assigned to the requested application when balancing the load. It does not include the destinations of the other applications or the respective, underlying engine server.
If you have not set the status of destinations to active, the RCCF does not include them for engine runs.
When destinations are selected for an engine run, the RCCF also examines priorities. The lower the value, the higher the priority. The priority with the value 1 is the highest priority. Load balancing is supported only for destinations with the same priority.
You must also select the communication type and its communication link. We recommend that you always use RFC in the standard system.
If you choose the communication type GRID, this requires a corresponding GRID to be installed on the engine servers. This kind of installation can be carried out only via SCM Expert Services and is delivered only on the basis of a customer project. For more information about SCM Expert Services, see SAP Note 689101.
Requirements
To copy existing data from SAP APO to the new framework, execute the upgrade report /SAPAPO/OPT_UPGRADE in SAP APO. For comparison, see the obsolete data in transactions /SAPAPO/COPT01_OLD, /SAPAPO/COPT00_OLD, and /SAPAPO/COPT10_OLD before you start the upgrade report.
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory 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 | /MRSS/C_ENG_DEST | 0 | HLB0009110 | Cross-Application Components |
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 |
| /MRSS/V_ENG_DEST | V - View | SM30 |
History
| Last changed by/on | SAP | 20090908 |
| SAP Release Created in | 700 |
