Workstatus transport

[Former Member]

Hi experts,

Does the workstatus customizing need to be transported or you just replicate it on the target system?

If so, is there any table to modify the transport behaviour of the workstatus settings?

Maybe is the same as team, by secury no team is transported to the target system.

Could you confirm that? Do you have any information about this?

We made a transport test and no workstatus setting were transported.

Thanks.

[SEdelstein · Accepted solution]

Hi Dave -

Work Status configuration is controlled by table UJT_TRANS_CHG via transaction SM30 and object type u201CWSTA . This setting allows you to control whether work status configurations are imported into your target system when importing a BPC transport. If this object is flagged to u201CDevelopmentu201D in the source system, all work status configuration within the AppSet will be collected in the transport.

Transports can collect the work states that are defined as well as any work status settings that are defined. Transports do not include any work status locks that may have been set in the source system.

Regards,

Sheldon

[Former Member · Accepted solution]

Hi Sheldom,

Thank you very much for the quick response.

Do you know if there is some sap note regarding all the tables you have maintain in the bpc nw transports?

UJT_TRANS_CHG: Transport objects maintenance

UJT_TRANS_FIL: paths of the file system you want to transport

UJT_TRANS_VAL: appset and app parameters

What about these?

UJT_TRANS_FLD?

UJT_TRANS_HDR?

UJT_TRANS_MBR?

UJT_TRANS_OBJ?

UJT_TRANS_STP?

UJT_TRANS_TAB?

Regards.

[SEdelstein]

Hi Dave-

Two documents that might provide a good perspective on what transports do (and don't do):

A Blog:

[/people/pravin.datar/blog/2010/02/17/what-you-should-know-about-transports-in-bpc7xnwSAPWeblogs_CorporatePerformanceManagement%2528SAPNetworkWeblogs%253AEnterprisePerformanceManagement%2529|/people/pravin.datar/blog/2010/02/17/what-you-should-know-about-transports-in-bpc7xnwSAPWeblogs_CorporatePerformanceManagement%2528SAPNetworkWeblogs%253AEnterprisePerformanceManagement%2529]

and an article:

[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b048ecf4-9414-2c10-ceac-fb2492a8016c|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b048ecf4-9414-2c10-ceac-fb2492a8016c]

Regards,

Sheldon

[Former Member]

Hi,

I´ve tried to transport again the appset after modifing the ujs_trans_table for the workstatus tlogo = development.

After transport it should have update the worstatus customizing on the target system, That´s ok, the configuration of the states have changed on the target system. But when we try to modify the work status on the target system, we get next error:

Org state does not exist.

Did i forget any step on the trasport process?

Regards.

[esjewett]

David,

What support package level are you on? There were serious issues with work status transport that I believe were not resolved until SP06.

If you are you SP06 or SP07, can you give some more information about your work status configuration? What work states have you set up for your appset and have you checked that they came across correctly in the transport? What dimensions have you assigned to drive work status in your application?

Thanks,

Ethan

[Former Member]

We have 3 work states.

The driver dimension is ENTITY

The work states were transported correctly to the target system but we can not block any region of data in production becouse of the error the system returns.

Regards.

[Former Member]

Problem solved.

The parameter APPROVALORG was not on the target system.

Thank you very much.