on 2015 Jan 28 11:06 AM
In our company there was a requirement to enhance the screen of std transaction CO11N which they have achieved through the exit CONFPP07 where the implementation partners some 9 yrs back, had created screens 0900, 0910, and 0920. Over a period of time it was found that the screen 0920 was redundant and was to be removed and accordingly the abaper then has deleted the screen from the function group XCOF. The transaction CO11N is still running smoothly.
However the problem that is arising now is that there is a new requirement to add a custom field in the screen through standard configuration procedure(ie by appending field to AFRU table). So when through SPRO or through T-Code OPK0 when we select the freely definable screen 3 in the drop down and click on the display screen the transaction goes to a dump saying "The system attempted to use dynpro 0920 in program "SAPLXCOF"..
The problem that as far as I am seeing seems that though the screen 920 doesnt exist in Function group XCOF, in the Project using the exit CONFPP07 I can still see a reference to that field under screen exit.
Has anyone faced a problem in deleting the screen exits? And what are the steps that one needs to check?
Request clarification before answering.
Hi,
I would ask the ABAPer to debug OPK0 and find what is the problem that is causing the dump.
When the screen 0920 was deleted, probably part of the code was not removed, so it is necessary to fix the problem and remove the inconsistency.
Kind Regards,
Mariano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
61 | |
9 | |
8 | |
7 | |
5 | |
4 | |
3 | |
3 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.