One of the very frequently asked questions in this space, is about the subject matter, i.e., How can I add Custom fields to a Notification? A documentation on this subject would be helpful to the forum for ready reference.
This documentation is intended to enable the readers to create the Custom fields in different tabs of Maintenance Notification, update the Noyification Master data Table and also display these fields in IW28 / IW29 output.
Let’s see how it is done.
Create Custom fields in the Notification Table
The table of our context is QMEL. We need to append our Z-fields to this through the include structure namely CI_QMEL.
The process of creating any custom field starts with creating a Data Element with desired Type and Length or with desired Domain name and with the Field Labels we want to have for the Customer fields. For our Demo, we have created Two Data Elements, namely :
- Z_DELAY – Type DEC Len 3 Dec 1 and Field Label ‘Delay(H)’
- Z_REASON – Domain TXT40 and Field Label ‘Reason for Delay’)
Now let us create our Customer fields.
Run Tcode SE11 –> give value QMEL in the Database Table field –> Click on Display. Scroll-down to find include table CI_QMEL. Double click on this, Go to Change mode and Add Two new fields of our interest as shown in the picture and Activate.
As seen in the picture, we have created Two Customer-Fields namely ZZDELAY and ZZREASON. It is essential for all Customer fields used in Enhancement purposes to be prefixed with ZZ.
Enhancement and Screen-Exit
1, Create an Enhancement Project say ZPMNOT using Tcode CMOD.
2. Assign Enhancement QQMA0001 to this project .
3. Click on Components in the picture above to reach this screen.
4. Activate by clicking on the Activate Icon (shown in picture above)
Now the screen is like this.
As we see here, there are several screen-exits (27) and Two Function-Exits namely EXIT_SAPMIWO0_008 and EXIT_SAPMIWO0_009 in this enhancement.
Double Click on this screen number to create a Sub-Screen for holding our Custom Fields. You’ll get this pop-up. Press Enter and Continue.
Please note that in EHP environment you may have to go through SE51 instead of above to create the screen by giving the program name SAPLXQQM and Screen number as 0103.
You’re in the screen below, where you’ll give a Description, Select the Subscreen Radio button, Save and Activate.
Click on Layout Arrow in the Application Toolbar of (See the picture above) to reach the Screen-Painter pop-up window, where we will be creating :
- A Box to hold our Z-fields
- Text Fields to for Z-field labels
- Input Fields for Z-fields
The input fields should be referred to the Dictionary fields we have just created. (QMEL-ZZDELAY and QMEL-ZZREASON) as shown above.
Activate the screen-painter.
Codes to be given in Function-Exits
Go to the following screen
Double click on the Function-Exit EXIT_SAPMIWO0_008 and
put the following code in the include ZXQQMU07 .
MOVE-CORRESPONDING I_VIQMEL TO QMEL.
Similarly put the following code in the include ZXQQMU08 of the Function-Exit EXIT_SAPMIWO0_009.
E_VIQMEL-ZZDELAY = QMEL-ZZDELAY.
E_VIQMEL-ZZREASON = QMEL-ZZREASON.
SPRO setting to be done
Navigate to the Overview of Notification Type in SPRO.
Select your Notification Type (Here we are doing it in M2) and Enter the Screen Structure for Extended view
Give the following settings in the Malfunction Tab (the tab where we want to have our custom fields)
Please note that the custom screen should be the last i.e., below all standard screen areas of the Tab. The reason for this can be understood in this discussion. —> Blank Screen coming in Tcode IW21 after our custom screen area
Let’s see the effect of work done so far.
Create a Maintenance Notification (IW21). You will see the following addition of subscreen area in the Malfunction Start/End Tab.
Enhancement has been added here by the system, in which our Custom fields appear with their labels and the input fields.
Now let’s add some values in these fields and Save the Notification.
Run IW22, open the Notification and verify whether the values are updated to table or not. If they are appearing as you have entered and saved, this means the QMEL table has been updated with these values when Notification was saved.
Let’s have these Custom fields in the Notification list reports namely the ALV of Tcode IW28/29 (QM10/QM11 in case of Quality Notifications)
So far we have succeeded in creating our Custom fields and updating the values to the Notification Master data. Next natural requirement of a user would be to have these fields in IW28/29 ALV screen. For this purpose we, need to create an Append Structure in the Structure RIHQMEL_LIST (RQMQMEL1 in case of QM10/QM11 reports), as shown in the picture below. The Tcode is SE11 again for this task. Here we have created an Append Structure named ZDLAY and in this structure we have added both the Custom fields.
Now let’s create few more Notifications, with custom fields filled with some values. Now run IW28 with selection parameters to display these Notifications we created. Click on the icon shown , You’d find the Custom fields in the Column-set list, Bring them to Displayed list on the Right hand side.
Related SAP Note: 370191 (Image of the note is attached herewith for the benefit of the members who can not access OSS)
Now if you go to IW23 of any of these Notifications, unlike all other greyed-out fields, the Custom fields will be seen Editable. Though there is no provision to Save the edits here, you’d definitely like to have these fields too in Greyed-out mode.
For this we need to write a small code in the PBO (Process Before Output) module of the screen 0103 we have created. Double click on the Screen number 0103 of the enhancement,
Un-comment line MODULE STATUS_103. and D’Click on the STATUS_0103 of the PBO module. Insert the following code between the MODULE, END MODULE lines like this.
MODULE STATUS_0103 OUTPUT.
IF SY-TCODE = ‘IW23’.
LOOP AT SCREEN.
SCREEN-INPUT = ‘0’.
Lastly Rememebr to
Activate the Function Group XQQM from Tcode SE80. Right click on the Function Group and click on the Activate option
…… and thus we reach to the end of this knowledge sharing Documentation.
1. As this is largely a Technical job, it is recommended to be developed through an experienced ABAPer, especially Part1 which involves Activating the Standard table QMEL.
2. The Environment of Author is ECC 6.0 with no EHPs, hence the document applicability.
Expecting this document too would be of use to many members from mainly from EAM and QM spaces.