Problems with Transporting Responsibilities

[Former Member]

I am using rules with responsibilities to determine the agents for a workflow I am developing. The ultimate destination system will be lockeed down for modification. The actual data required to determine the responsibility will only be available on the destination system, so it will need to be maintained there. Is there a way to unlock the system just for the maintenance of the data for the responsibility? I am using PFAC to maintain the rule. Will transaction oocu_resp allow me to maintain a rule in a client that is not modifiable? I do not have a client available to check it out - any thoughts out there?

[Former Member · Accepted solution]

Hi,

You can transport your rule to the non-modifyable client. From OOCU_RESP, you can maintain the agents in the production client. This is changeable.

Cheers,

Satish

[Former Member]

Thank you very much for your fast response!

[Former Member]

You can maintain Responsibility using Tcode OOCU_RESP provided you have the authorization for it.

Thanks

Arghadip