Work Status in BPC 10.1

[Former Member]

Hi All,

I have a work status state as below:

• unlocked
• submitted
• approved

the owner dimension is entity as shown below:

Entity AA (owner properties is : Manager2)

---> Entity AA1 (owner properties is : Manager1)

           ---> Entity AA1-1  (owner properties is : staff1)

           ---> Entity AA1-2 (owner properties is : staff2)

           ---> Entity AA1-3 (owner properties is : staff3)

My question is:

After I set the work status Entity AA1-1 to "submitted" using ID=Staff1, the ID=Manager1 can change the work status set to "Approved" for all entity AA1-1, AA1-2, AA1-3 even before Entity AA1-2 and AA1-3 change their work status set to "submitted".

Is this the way it works???? because my understanding, if entity Entity AA1-2 and AA1-3 have not have work status state="submitted", manager1 should not be able to change their status to "approve"

thanks.

[dinesh_veluru · Accepted solution]

Dear U-one,

Since Entity AA1 is the manager they will be able to approve prior to submission of other entities.

Entity AA1 (owner properties is : Manager1)

           ---> Entity AA1-1  (owner properties is : staff1)

           ---> Entity AA1-2 (owner properties is : staff2)

           ---> Entity AA1-3 (owner properties is : staff3)

below steps to be followed.

1) Badi logic to be implemented  where it has to fetch all the base members of  Entity AA1 and check the individual status code for (SUBMITTED) in the table UJ*_STEP_RGEN for all the base level entities  and it should display error message if any base entities are not submitted prior to submission of parent(AA1)

2) Please check if the  below workaround helps.

create step1 by passing all the base members of the entities.

create step2 passing all the parent members of the entities(step2 will be in pending state till step1 is completed)

Thanks,

Dinesh.V

[dinesh_veluru · Accepted solution]

upadating the correct table name  UJB_STEP_RGN

Thanks,

Dinesh.V

[Former Member · Accepted solution]

Hi Dinesh,

I am trying following workaround:

.

create step1 by passing all the base members of the entities.

create step2 passing all the parent members of the entities(step2 will be in pending state till step1 is completed)

In step 1, I create process instances and pass all the base members of the entities. Opening Criteria=Matched, Performer= Owner, and the workspace is "Set work status State".

In step 2, I create another activity inside the process instances and pass all the parent members of the entities.  Opening criteria= matched, Performers (Reviewer property in entity dimension) and the workspace is "set work status state"".

After I complete all the steps1 in my activity screen, my second activity (which is defined is step 2) still have status "pending". Why could it be? I tried to pass all the base member and parent member of the entities in step 2 and complete activities in step 1, but still the second activities have "pending" status.

Thanks

[dinesh_veluru · Accepted solution]

Dear U-One,

lets assume below is the master of Entity dimension.

ID	Owner	reviewer	Hirearchy
AA1		Manager1	H1
AA1-1	staff1		AA1
AA1-2	staff2		AA1
AA1-3	staff3		AA1
H1

1) create step1 by selecting only the base members AA1-1,AA1-2,AA1-3 AND performer as owner property AND opening criteria ticked as  "ALL" and "Allow reopen"

2) Create step 2 by passing only the parent AA1 and performer property as reviewer AND opening criteria ticked as  "ALL" and "Allow reopen"

Step 2 will be in pending state till step 1 is completed

Please attach the process template screenshot to check on this further.

Thanks,

Dinesh.V

[Former Member · Accepted solution]

Hi Dinesh

If the hierarchy is complex (contain multi- level structure) as below:

ID	Owner	reviewer	Hirearchy
AA1		Manager1	AA
AA1-1	staff1		AA1
AA1-2	staff2		AA1
AA1-3	staff3		AA1
H1
AA		Manager2	H1
BB		Manager3	H1
BB1		Manager4	BB
BB1-1	staff4		BB1

I guest I have to define many steps..rite??

Thanks

[dinesh_veluru · Accepted solution]

Hi U-One,

Yes, multiple steps to be created

1) all AA1-1... BB1-1...

2) AA1,BB1

3)AA, BB

Please explain the worklfow of the each users.

As per my understanding AA1-1.. BB1-1 are the performers once they complete the step . then should avaliable AA1, BB1 once they complete the step then it should to final level approval to AA, BB.

Thanks,

Dinesh.V

[former_member182766]

In work status setting for Submitted step do you have it controlled by Owner and Manager?

Set it to be controlled only by "Owner".

Disregard that. Was thinking about something else.

Manager will have the right of Approval. Fiddle with "Order" of tasks in Works status settings.

Maybe you can create another placeholder task between Approved and Submit and maybe that helps, because Order in Works Status makes sense.

[Former Member]

Hi Vadim,

Sorry ..I don't get you. What do you mean with create another placeholder task between approved and submit?