cancel
Showing results for 
Search instead for 
Did you mean: 

Work status check in LOAD_INVOPROV_UI

Former Member
0 Kudos

Hi All,

We're using the standard LOAD_INFOPROV_UI process chain to load data from a BW multiprovider to BPC cube. The package script is standard as well. When I set the CHECKLCK parameter to 1 from the package, which should check the work status and not allow the system to write to the BPC cube, data is still getting written. We currently have entity as an OWNER and all the entities that are being loaded from the BW cube are in the following workstate:

LOCKED

-DM - LOCKED

-JRN - LOCKED

-MAN - LOCKED

I checked the process chain and the CHECKLCK parameter for CLEAR_DATA and APPEND_LOAD were hardcoded to 0. I changed it to 1 and it still does not check work state.

Please help me understand if it's something I'm missing.

We;re on 7.50.12 NW

Thanks,

Zoheb

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member200327
Active Contributor
0 Kudos

Hi Zoheb,

Can you see if Package log shows CHECKLCK = 0 or 1?

Regards,

Gersh

Former Member
0 Kudos

Thanks Gersh, the package log does say CHECKLCK=Yes. I've ensured the app parameters are setup correctly and that we're using the same hierarchy that is specified in the APPROVALORG parameter.

Former Member
0 Kudos

Also, if it helps, we checked the cube and data isn't actually getting written when in LOCKED status. We compared the source BW cube and the destination BPC cube and do not see any records that were written in. However, it seems there might be something with the package log because it still shows number of records accepted even though nothing is actually written to the cube.

One additional test we did was to run the package with filters on 1 entity and 1 account. In this case we get the expected warning message of No accept records and all rejected records because of Error checking work status.

Could use any suggestions of things we might be missing or why we are experiencing this behavior.

former_member200327
Active Contributor
0 Kudos

Hi Zoheb,

Do you run DEFAULT logic after load in that Package? There was a bug in BPC 7.5 that was loosing messages from Write-Back if another Write-Back is issued.

Since you are on SP12 it should have been already fixed, but it makes sense to check if something similar is still happening.

Regards,

Gersh