Work status Data Manager

Question

Hello!
We can run a package from Data Manager on periods that have the status of "Locked"
We have a package with the following script:
'DEBUG(ON)
PROMPT(SELECTINPUT,,,"Please select category, entity and time for restatement","%CATEGORY_DIM%%TIME_DIM%%CURRENCY_DIM%")
TASK(Execute formulas,USER,%USER%)
TASK(Execute formulas,APPSET,%APPSET%)
TASK(Execute formulas,APP,%APP%)
TASK(Execute formulas,SELECTION,%SELECTIONFILE%)
TASK(Execute formulas,LOGICFILE,%APPPATH%\..\AdminApp\%APP%\FXCONSOL_Restatement.lgx)
TASK(Execute formulas,RUNMODE,1)
TASK(Execute formulas,LOGICMODE,1)
TASK(Execute formulas,CHECKLCK,1)
The logic used are as follows:
*INCLUDE SYSTEM_CONSTANTS.LGL
//Kr omflyttning av obeskattade reserver
*INCLUDE ObeskRes.lgf
// Kr berkningar av elimineringar och konsolidering
*RUN_STORED_PROCEDURE = SPRUNCONSO('%APP%', [%KATEGORI_SET%], [%GRUPP_SET%],'%SCOPETABLE%','%LOGTABLE%')
*COMMIT
*INCLUDE Calculations_H2.LGF
If we use this package in Data Manager for a period which has the status of "Locked" the package will run. Should not this be stopped because we have the status of "Locked" on the period and the script says that it will check Work Status

Answer 1

Hi Daniel,
'Normal' logic should listen to the 'locked' settings. Please double check the workstatus settings to see if DM=locked is correct for the 'locked' workstatus.
BUT:
The businessrules stored procedures do not listen to these settings. Most SP calls have there own locking methods.
For example the SPRUNCONVERSION call is as follow:
*RUN_STORED_PROCEDURE=SPRUNCONVERSION(u2018APPLICATIONu2019,u2019CATEGORY_SET%u2019,
u2019%CURRENCY_SET%u2019,u2019GLOBALu2019,u2019%SCOPETABLE%u2019,u2019%LOGTABLE%u2019,impact,destination,
ratedimension,maxstatus)
The maxstatus setting here is the maximum status which allows change of data.
The one exception here is SPRUNCONSO which can not be prevented from running and storing data.
Normally this is good behaviour;
SPRUNCONSO doesn't change LC data and shouldn't therefore not calculate other numbers than the previous run.
The behaviour of other sp's could/must sometimes be different then normal datamanager packages; for example when the status is submitted, users should not be able to upload/clear data, but should be able to run conversion and consolidations, that is why the sp's have there own locking section in the call itself.
Alwin