Substitution issue

[Former Member]

Hi all,

I have a new requirement to fix a substitution issue. Here's the scenario:

There's a substitution in place to derive the Location of a FI document from either the Cost Center or an Order, both in the Coding Block screen of FB01 or FB50. At the time of the document creation, the user can also manually enter the Location, overwriting the derived one.

The issue now is - if the user comes back to this coding block screen after manually entering the Location and decides to change the cost center or the order, the substitution kicks in again and replaces the manual entry.

Any thoughts on how to prevent this? I cannot ask the developer to check if the Location is already populated before deriving the value otherwise I won't be able to change its value if I initially enter one Order and then decide to use another one.

Hope I made myself clear!

Thanks!

[Former Member]

Hi all,

I have a new requirement to fix a substitution issue. Here's the scenario:

There's a substitution in place to derive the Location of a FI document from either the Cost Center or an Order, both in the Coding Block screen of FB01 or FB50. At the time of the document creation, the user can also manually enter the Location, overwriting the derived one.

The issue now is - if the user comes back to this coding block screen after manually entering the Location and decides to change the cost center or the order, the substitution kicks in again and replaces the manual entry.

Any thoughts on how to prevent this? I cannot ask the developer to check if the Location is already populated before deriving the value otherwise I won't be able to change its value if I initially enter one Order and then decide to use another one.

Hope I made myself clear!

Thanks!

[Former Member]

Hi

If the user change Cost Center or Order, your substitution should check if the actual value of Location is equal to derived value from old Cost Center/Order:

If it's equal than the subistitution should be triggered again else it can leave the current location (because it can suppose the user doesn't change it manually)

Max

[Former Member]

Thanks - you gave me a good starting point and I was able to find a solution.