Hello folks,
System Information:
NW AS 7.03 ABAP Stack 731 Level 11, ECC 606 (EHP 6) with SAP_HR 604 Level 73 and EA_HR 607 (HR-Renewal 1) Level 24
Background:
For Our WDA Leave Request application, our special department has requested to provide certain additional fields for particular Leave Types, all in all these are three check boxes and one Link-To-URL-UI. I have created these fields, or rather configured them via IMG Customizing Tables V_PT_FIELD_SEL / V_PT_FIELD_SEL_C, using the ten standard customer fields provided by SAP CUSTOMER01 - CUSTOMER10.
After making the subsequential customizing configurations, I have enhanced the WDA OVP-FPM CC "HRESS_CC_GUIBBF_LEAVREQ" to change the respective fields' UI-Type from "Inputfield" to "Checkboxgroup" and "LinkToAction". So far so good; it's nothing fancy and everything works out the way it should.
Problem:
Our special department has recently noted, that the Link-To-Action provided is also taken into account by the Confirmation Dialogue Popup-Box and correctly set read-only like any other field as well. However, the fact that this read-only-link is then also shown in the Popup-Box is confusing to some users and should therefore be hidden. My plan was to enhance the WDA OVP-FPM CC "HRESS_CC_GUIBBF_LEAVREQDIALOG" and simply set the field CUSTOMER01(that's the one field I use for the Link-To-Action-UI) invisible and that's exactly what I did. But look what the effect is:
You can see behind the lightbox in the Form, how the field is usually displayed in the Form-UIBB. What I "achieved" now, though, is, that only the lable is hidden in the Popup-Box through my enhancement in "HRESS_CC_GUIBBF_LEAVREQDIALOG" and the LinkText is still visible.
What I did so far / Question:
So... I went ahead and debugged the feeder class CL_HRESS_PTARQ_LEAVREQ_GUIBBF. I found out that in the Methods "FIELDS_SHOW_HIDE_CLEAR" and "FIELD_SETTING_BY_CUSTOMIZING" I would theoretically be able to manipulate the visibility, but:
- This would mean I'd have to create overwrite-exits, which I would like to avoid, because maintenance is a pain.
- Manipulating the process flow here probably has side effects on the field control of the overall application which must not happen. If I'm extremely unlucky it might even effect the data flow.
This brings me to my ultimate question: How do I make a field from this Confirmation Dialogue Popupbox cleanly disappear/invisible in a super-duper-elegant way without using a sledgehammer? Maybe there is a customizing-way I have overlooked so far? (please?)
Cheers, Lukas