Tag Archive for 'ABAP'

Problem we ran into today: we added a couple user-defined fields in the customer data tab in ME21N – Purchase Order. This worked fine, but we found that when in transaction ME22N after we saved the changes in these fields, the fields themselves would still be editable. Also going to a purchase order in ME23N, the UDF would always show as editable fields. After a search we found that function MEPO_DOC_GET_TRANSACTION_STATE was able to return the transaction state (I_TRTYP) that is required to tell the system to lock or unlock the new fields.