Hide it in the screen dictionary, save and validate. Then validate the purchase transaction screen.

Thank you ! It worked.

I have a question though.
We have several transactions for purchase orders:

STD - Standard entry
ALL - Full entry
TST - My test entry

Is it possible to hide the fields only in TST for example?
For the moment I have not validated the others entry so that the changes are not taken into account, but this may not be the right way to do it.

After changing the POH2 screen (Development->Script Dictionary->Screens) and validating the screen, you then have to go to the purchase order transaction entry screens (Setup → purchasing → Entry Transaction → Order) and validate the transaction entry screens.

FYI, if you are changing several screens in a Window (poh1, poh2,...), you can go to the Window and click on Global Validation to re-validate all associated Screens, Object and the Window.

If a function is not behaving as expected, the first action you should do is to the Window, do a global validation, then (if the function has entry transactions), validate the active entry transactions for the function.

Tom

In the transaction screens you can only control the fields that are available there other fields you'll need to control on the screen. If you hide a field on the screen then it would be hidden for all transactions. To accomplish what you want you'll need to write some programming code to hide the field for some transactions and not for others.