Hi Biju,
Please find below an extract on how to approach the problem
1. The field exit was created with CMOD, but is not processed when the screen is called.
Field exits can be defined only for data elements whose name is shorter than 19 characters. The name of the data element plus the prefix "FIELD_EXIT_" must not exceed the maximum length of a function module name (30).
Since the field exit is not processed until PAI, an action must be triggered on the screen (choose enter, save, and so on).
Set the profile parameter abap/fieldexit = YES and restart the system.
After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen you want to execute the field exit. The relevant screen is only generated when the transaction is called.
Do not work on different application servers since there may be some delay before the field exit is activated.
The profile parameter must be set on all or no application servers.
If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen number (take care with subscreens).
Use transaction SE51 to generate the screen on which the exit should be active. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can copy the report rsmodfdg from the correction instructions and start it with transaction SE38. The report uses the affected data element as the input parameter and regenerates all screens that use the data element.
Use transaction SE51 and choose 'Field list' to check that the screen field actually has a reference to a data element. In the name of the field exit, use the name of the data element and not the field name.
After the transport, field exits are marked as active but are not processed. Tip: First try to deactivate the field exit once more and then activate it again.
http://www.saptechies.com/faqs-field-exits-cmod/
Regards
Byju
Bluesky
