PO20 Error: "Value not in List: "

I got an offline email on this issue and from what I saw the customization was beyond what Design Studio was intended for. If I understand what happened is the XML source code was also modified (not DS standard) - but since I've done that in the past myself I don't think it was wrong, just harder to debug and correct.

I think the program recompile messed up your modification (when the screen regeneration was done). Your modification added a custom "Z" function to the standard "A", "C", etc. functions and that's what you're using to trigger your flow. Maybe someone knows a way to put that back in.

Ok Lawson support is basically not going to help us here. They are turning us over to professional services.

We have had this code in place for a long time now and it still works in our PROD environment. Has anyone else out there had this problem? I cannot believe we would be the only ones to see something like this? Lawson has issued patches for other releases and platforms to address this very error. Everything was working just fine right until we applied the latest set of patches.

Any help would be greatly appreciated!

Have you tried adding a "Z" FunctionCode to the PO20.D source file and regenerating the screen with CRTSCRN8? This is where the function code values originate.

ok I did some digging into the custom code. I added alerts everywhere to isolate the code and determine the source of the error message.
It is coming from inside the "OnBeforeTransaction" function. In there we have an AGS call to form PO22.1 which is passing a "LINEFCr1=E" this is whats causing the error message "value not in list: " to be thrown.

Here is the actual AGS call:

This code was written by a consultant for us, prior to my joining the company. Thus I am not familiar with what he is trying to do here? Does anyone have any ideas on how can I fix this issue now?

He's doing an AGS call to PO22.1, but he's passing for the detail line FC an "E" when the only valid values are "X" (Select) and "R" (Release).

I think if you just change the parameter on the AGS call to "&LINE-FCr1=R" it should work.

Of course maybe you have a custom PO22.1 with a FC of "E" which is why the code is correct. I'd check PO22.1 and see what the valid line FC values are.

It's possible a custom line function code of "E" was added to the screen source code. Valid values for the 8 version should be X and R.

Check in production and see if you have an "E" line function code on the screen.