For overview
on this topic and BW classic related specific information see following post: Checking
status of cube behavior – BW classic.
In
BW4/HANA based
system there is no information about real-time behavior persistently stored in
database like is in BW
classic. Instead, the behavior (whether it is loading/staging or planning
mode) is evaluated on the fly while user request the change of the behavior. For
example if user triggers the behavior change system checks what real-time behavior
is set currently and subsequently is changes it to opposite one.
Behavior
change in t-code RSMNG:
As
the current mode is not stored persistently in database, it is hard to read it without
access either to t-code RSMNG or to BW cockpit. However there is a way how to
do it. To find out of aDSO is in planning or loading mode, query table RSPMPROCESS with selection:
PROCESS_TYPE = PLAN
PROCESS_ID = */CPMB/ARI* //your planning enabled aDSO
object
Then
sort a result set via field PROCESS_TSN
and check value of PROCESS_STATUS
field. If it is Y means PLANNIG request is active in the aDSO thus whole aDSO is in
PLANNIG mode. If the PROCESS_STATUS field has value G (Finished) means there
is no open yellow planning request in the aDSO thus it is in LOADING mode.
Logic that handles flipping of aDSO mealtime behavior is coded in ABAP class: IF_RSPLS_ADSO_API~SET_PLANNING_MODE
(CL_RSPLS_ADSO_API).
