SAP ABAP Data Element RSDDSCR_MAXWAIT (Wait Time for Change Run Lock (in Minutes))

Hierarchy

☛ SAP_BW (Software Component) SAP Business Warehouse
   ⤷ BW-WHM (Application Component) Warehouse Management
     ⤷ BW_CORE_WHM_MISC (Package) BW WHM parts that are needed in the CORE

Basic Data

Data Element	RSDDSCR_MAXWAIT
Short Description	Wait Time for Change Run Lock (in Minutes)

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	INT4
Data Type	INT4	4-byte integer, integer number with sign
Length	10
Decimal Places	0
Output Length	10
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	Wait Time
Medium	15	Wait Time
Long	25	Wait Time (Change Run)
Heading	10	Wait Time

Documentation

Definition

Here you can set a waiting period (in minutes) that specifies how long a process is to wait when it encounters a lock created by other parallel processes, such as for loading hierarchies or master data, another change run, or rolling up of aggregates.

If the system does not find a relevant lock, the change run waits the length of time specified here without creating its own lock.

Use

Dependencies

Note also that all processes that can be locked by a change run wait for up to five minutes for the CHANGERUN START lock and then terminate with an appropriate error message if necessary.

Example

• Two change runs start in parallel. In this case, one change run would start immediately. Since the other change run is a process that could be affected by the lock created by the first change run, it waits up to five minutes. The system checks which InfoCubes contain the InfoObjects affected by the change run and locks these along with all corresponding aggregates.
• If the change runs affect different objects, they can run in parallel once the five minute waiting period has ended.
• If there is an overlap between the objects affected by the change runs, the second change run waits the length of time specified here without creating its own lock.
If there are change runs in your system that are executed frequently but that are completed relatively quickly, it makes sense to specify a waiting period that reflects the short runtime of these change runs.
• The system is loading master data when another change run is to start. The change run waits the period of time specified in parameter CR_MAXWAIT without creating its own lock.

History

Last changed by/on	SAP	20130604
SAP Release Created in	700