SAP ABAP Data Element /MRSS/T_RCCF_DEST_ID (Destination ID of External Engine in RCCF)
Hierarchy
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net
   PM-WOC-MO (Application Component) Maintenance Orders
     /MRSS/RCCF_COMMON (Package) RCCF Common
Basic Data
Data Element /MRSS/T_RCCF_DEST_ID
Short Description Destination ID of External Engine in RCCF  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type /MRSS/RCCF_DO_CID    
Data Type CHAR   Character String 
Length 10    
Decimal Places 0    
Output Length 10    
Value Table      
Further Characteristics
Search Help: Name /MRSS/SH_RCCFSD_DESTID    
Search Help: Parameters DEST_ID   
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Dest. ID 
Medium 20 Destination ID 
Long 30 Destination ID 
Heading 50 Destination ID of External Engine in RCCF 
Documentation

Definition

Specifies the unique identifier of a destination in the Remote Control and Communication Framework (RCCF).

Use

You define this identifier in the Process Destinations of RCCF Engines. Customizing activity. It is used in other transactions, for example, in the /MRSS/OPT_LOG bzw. /MRSS/RCCF_LOG log display, to uniquely identify the destination in which an MRS optimizer ran or is to run.

Dependencies

Example

The destination ID identifies a single RFC connecton that provides a certain level of processor capacity. If you were to define two destination IDs - DEST1 and DEST2 - where both are showing different RFC connections:

  • If you do not specify a particular destination ID, for example, in the optimizer profile, the in-built load balancing helps do decide which RFC connection still has available slots and these are then occupied.

  • If you explicitly specify a destination ID, an attempt is only made on this RFC connection to reserve a slot for the pending optimization run.

This enables you to use different servers, or in the case of RFC groups, several servers depending on, for example, the time or the scenario to be optimized. Examples of such usage include separate servers for longer running optimizations or special scenarios such as night-time optimization on an alternative server to enable maintenance work to be carried out.

History
Last changed by/on SAP  20141109 
SAP Release Created in 610