EPM 10.1 NW Work Status not working

[PankajVPatil]

Hi Experts,

I have configured the work status as Default, Submitted, and Approved; depicted as below:

Also have set the OWNER property of ENTITY dimension to reflect the owner/manager user id against respective entity nodes. But when trying to save the data on respective data point through owner login via input schedule, the data gets saved without the default work state. Also on clicking of the "Change Work Status" at BPC excel; the pop-up comes disabled saying that the owner does not have authorization to edit the work status for the respective data point. I checked the security configuration and have "Use Work Status" as a task profile included in the owner's and manager's security configuration. In fact both the owner and manager are admins and have all available/applicable access from security perspective.

I have tried multiple options but the work status pop-up do not get enabled.

Can anyone help me understand what I need to do to make work status function correctly ?

Regards,

Pankaj

[former_member193143 · Accepted solution]

Hello Pankaj,

As per note 2123404,

SAP Business Planning and Consolidation 10.1, version for SAP Netweaver, upgrade to(Component CPMBPC 810) support package 06 and upgrade BW740(Component SAP_BW) to support package 11.

regards,

Saida Reddy G

[PankajVPatil · Accepted solution]

Hello Saida,

Thanks for the response. I am trying to setup the work status in Production environment. I referred the note and it seems that my system requires patch updates. But what I don't understand is that the same work status configuration functions correctly in Q but does not in P; and Q is on the same patch levels.

Regards,

Pankaj

[dinesh_veluru · Accepted solution]

Hi Pankaj,

1) Please check whether the workstates in QA and production are in sync and access rights are same in both the landscapes.

goto se16-- UJW_STATCODE check the table entries.

2)  if state "0" is missing then run the program

SE38  -   UJW_UP_INSERT_0_STATE  -- which will create default 0 state.

3)  if there are more inconsistency in the workstates then please follow below steps

a) Please delete the work states that are defined in the production system by running the following SE37>> UJW_API_DELETE_ALL_WORKSTATES

b) Transport the table entries in UJW_STATCODE from quality to production or create the workstates again in production from bpc web (front end)

please note if any changes were made in the workstates , then it is advised to first disable the workstatus and then enable again and test.

Thanks,

Dinesh.V

[PankajVPatil · Accepted solution]

Hi Dinesh,

Thanks for the response.

I followed the points mentioned in your post and the issue got resolved.

Just curious, does the 0 state record in table UJW_STATCODE get deleted when the existing "unlock" state is deleted ? or is there any other reason for this record's disappearance which may involve any dependency on environment transport etc. ?

Thanks a lot !

- Pankaj

[former_member193143 · Accepted solution]

Hello Pankaj,

yeah if the default work state deleted the order will change in the work status table , in order to add the default work state we will run the program. when we run the program it will add that default work state.As far as I know its a normal error while doing the transport..

Regards,

Saida Reddy G

[former_member182709]

Pankaj,

Does the user have the write access to the entity in DAP as from 10.0 sp17 or 10.1 sp06 DAP will be checked as well when set work status. Note 2127269

Charlie