Bypassing work status lock in FX Restatement

[Former Member]

Hi,

We have a requirement to bypass the work status lock when we run an FX Restatement as part of our budgeting process. I was hoping to achieve this by writing my own BPC Process Type and piggy-backing off standard code. However, hereu2019s my problem:

1. The currency conversion is part of the main consolidation program logic.

2. This program calls the main WRITE BACK logic to write the data back to the application once the conversions have been performed.

3. The WRITE BACK logic (method cl_ujr_write_back->write_back_int) has a parameter (I_BYPASS_LOCK) which, when set to TRUE, allows the work status locks to be bypassed.

4. However, the consolidation program calls the WRITE_BACK in such a way that the parameter is not set, which means the default value is taken, which is FALSE, which means the locks are respected:

So, from what I can see, my only options are:

A. Implement the WRITE_BACK BAdI and use it to bypass the lock in the special circumstance that a currency conversion is being performed (Iu2019m not even sure this is possible u2013 will need to check).

B. Create my own version of the Consolidation and Currency Conversion program by inheriting from CL_UJP_CURR_CONVERSION (annoyingly itu2019s a FINAL class) and redefining the method that calls the write back. The problem with this will be how to get the script logic parser to call my class, instead of the standard class.

Has anyone faced the same problem and found a solution?

Thanks,

Tristan

[Former Member]

Hi Tristan,

I may be confirming what you already know that it is not possible to bypass the work status in NW version. At one of our implementations, where the customer had OLS 4.2, had a keyword which is used then in a script logic to check the work status code along with the script.

We had a solution which worked in our case as we have opened up the DM method in work status code 'Submitted' where the managers could run the packages. Not sure if this would also be applicable in your scenario.

Thanks,

Sreeni