Not possible to run Data Manager packages as Manager - Work Status Submitted

[Former Member]

Dear all,

We got a issue, where it wasn't possible to run Data Manager packages as Manager on Work Status Submitted?

it is oK in BPC10, but with problem in BPC10.1(we just finished upgrade).

please see attachments "work status" for the work status setting, and "bpc env" for the environment.

Any comments will be appreciate,

BR,

Jacob

[former_member186338]

"We got a issue, where it wasn't possible to run Data Manager packages as Manager on Work Status Submitted" - full details of the issue including error screenshot

[Former Member]

Hi Vadim,

thank you for your reply.

the package failed since the work status of relative dimension are in submitted. but according to the user's role is manager, who should be run the package successfully according to work status's setting.

the error message please see the enclosure.

BR,

Jacob

[former_member186338]

I can see that some data is written! Are you sure that the scope of DM is OK?

[former_member186338]

P.S. Try to test with minimum (1) records in scope to be sure...

[Former Member]

Hi Vadim,

yes, you are right. we did some calculation and write back to model by running data package.

the scope of dimensions was submitted, the data package can be run successfully only the work status need to be changed as open. but this is violated against work status setting, it should be run data package to write data as manager? right?

BR,

Jacob

[Former Member]

Hi Jacob,

You may select "No,do not check work status settings" option to by pass the work status settings.

You may aware that,"manager" means owner of the parent member.

Please check if you are the "owner" for the parent member which your are trying to load in DMP.

Regards,

Manohar

[former_member186338]

Yes, please check your manager assignments...

[Former Member]

Hi Manohar,

You may select "No,do not check work status settings" option to by pass the work status settings.

Re: yes, you are right. I think this should not be lead to the error.

and I confirm that I am the "owner" of the parent member.

it works fine in BPC10, but issue happend on 10.1

BR,

Jacob