SAP ABAP Data Element /MRSS/T_ORD_LOCK (Lock Active at Order Level)
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
Basic Data
Data Element /MRSS/T_ORD_LOCK
Short Description Lock Active at Order Level  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type /MRSS/_BOOLEAN    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
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 Order Lock 
Medium 15 Order Lock 
Long 20 Order Lock 
Heading 20 Order Lock 
Documentation

Definition

Specifies whether orders are locked in the planning board.

Use

If you set this indicator, only one user can currently create assignments for an order.

If you change the service order during transaction processing, assignments cannot be created in the planning board.

The lock at order level prevents two users from creating assignments for the same demand at the same time. It also ensures that the alerts that occur when relationships are violated are displayed immediately (see the example below).

If you do not set the lock at order level, the system checks when saving the planning board whether any potential conflicts exist (due to two users processing the same order at the same time, for example), and then updates the alerts.

Dependencies

Example

An order has two operations, item 10 and item 20, which are linked by an end-start relationship. Two assignments already exist:

Assignment    Item    Date    Time

A10    10    01/01    8:00 a.m. - 9:00 a.m.

A20    20    01/01    10:00 a.m. - 11:00 a.m.

Lock is set at order level:

  1. User U1 and user U2 are both working with the planning board at the same time.
  2. U1 postpones assignment A10 one hour to 9:00 a.m. - 10:00 a.m. This user does not receive an alert because the relationship has not been violated.
  3. U2 attempts to put forward assignment A20 one hour to 9:00 a.m. - 10:00 a.m. If the lock at order level has been set, U2 receives a message that the order is already being processed by U1, which means that U2 cannot put forward assignment A20.

Lock is not set at order level:

  1. U2 puts forward assignment A20, even though U1 has already postponed assignment A10, and does not receive an alert because the relationship in U2's planning board has not been violated.
  2. U1 saves changes.
  3. U2 then also saves. The system detects that the order in question was processed by U1 at the same time. Once the changes have been saved, the planning board is updated and the alert checks are performed for the order. U2 receives the alert stating that the relationship for assignments A10 and A20 has been violated.

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