February 2013 English

SAP Quality Issue app Enhancement Guide

Bertrand Moyo SAP Consulting Hasso-Plattner-Ring 9 69190 Walldorf Germany

1 Introduction ......................................................................................................................... 3 2 Quality issue Frontend extension ........................................................................................ 4

2.1 User Responsible & Area/Plant .................................................................................... 4 2.2 Material ......................................................................................................................... 5 2.3 Subject Coding and Defect type ................................................................................... 6 2.4 Subject description and Priority .................................................................................... 6

3 Quality Issue App Backend Add-ons Extensions ................................................................ 8 3.1 Extend the service definition for creation of issue reports ............................................ 8 3.2 Extend the service definition for display of issues ........................................................ 8 3.3 Pass additional fields to BAPI_QUALNOT_CREATE ................................................... 9 3.4 Pass additional fields after issues are selected .......................................................... 10 3.5 Add functionality reading data for e.g. value help (list of material numbers, material description for material number etc.) ................................................................................... 10

1 Introduction The purpose of this document is to describe how to customize the SAP Quality Issue app to implement the Q Note Type Z3 for John Deere. It shows how additional fields can be added to the SAP quality issue app frontend and Backend component. The Hierarchical views of dataset (e.g subject and issue codes) will be supported by the next version of the quality issue app, therefore partially covered in this document. Note: This is not a cookbook with step-by-step instructions.

2 Quality issue Frontend extension This part will explain how to add new Fields on the UI. The next version of SAP Quality issue app (2.x) will offer the skinnable UI features. Therefore this part will focus on the UI Implementation of the additional fields according to Z3 in Backend.

2.1 User Responsible & Area/Plant In Z3 there are more than 500 users responsible the end user can choose by creating a new Q Note. To avoid waiting time, the list of frequents users responsible can be pre-filled by the End user. This End user would open the settings of SAP Quality Issue App and enter the most frequent User responsible by tapping on a Add item Button. The end User would remove a user responsible from the list by using the iOS standard wipe feature. This pre-defined List will be used in the app to create a new Q Note. Please see the screenshot below.

User responsible

The End user would define a similar list in the setting for frequents Area/plant prior using the app. The app would use this list to create a new Q Note.

2.2 Material The End user would enter the material number in a text field manually. The app would pop up an alert with the corresponding error message if the entered material number is not supported by Z3. See the Screenshot below:

Entry of the Material number

2.3 Subject Coding and Defect type Z3 uses a hierarchical list for Subject Coding and Defect type. The next version of the SAP Quality Issue App (2.x) will support hierarchical structures. The iOS Table views suits best the realization of hierarchical data sets. The implementation of the Subject coding and Defect type can be done using table views. The screenshots below presents how it would look like.

Hierarchical view of the Issue Code using Table views.

2.4 Subject description and Priority The fields subject description and priority can be left as in the default app because it is supported by Z3. By adding the fields like described above the app should be ready to fill all required fields in Z3. Additional fields to support others Q Note type can be implemented in a similar way. The next Part will describe how to modify the backend Add-Ons component to support the new fields.

Recorded Issue

3 Quality Issue App Backend Add-ons Extensions The backend component has no modification free extension techniques implemented (BADI or similar). Changes need to be done by modifying the relevant code or by copying the code and creation of a new service.

3.1 Extend the service definition for creation of issue reports To allow the creation of issue reports with additional fields new properties need to be added to the entity type QMNotification . The entity type is defined in method CREATE_NOTIFICATION of class CL_LWM_QUALITY_ISSUE_MD. Since the dictionary information of structure LWM_QUALITY_ISSUE is used to create the properties it is sufficient to add the fields to the structure, the name of the fields in the structure determine the name of the properties. Add the following fields to structure LWM_QUALITY_ISSUE: MATERIAL_PLANT Types QMAWERKS MATERIAL Types MATNR SHORT_TEXT Types QMTXT

3.2 Extend the service definition for display of issues To add fields to the display of issue reports the entity type QMIssueList needs to be extended. The entity type is defined in method CREATE_ISSUE_LIST of class CL_LWM_QUALITY_ISSUE_MD. Structure LWM_S_QI_SELECTED_NOTIF is used to create the properties. Add the following fields to structure LWM_S_QI_SELECTED_NOTIF: MATERIAL_PLANT Types QMAWERKS MATERIAL Types MATNR SHORT_TEXT Types QMTXT

3.3 Pass additional fields to BAPI_QUALNOT_CREATE After extension of the service definition for the creation of issue reports the following coding needs to be adjusted to forward the additional fields to the BAPI which is used to create the Quality Notifications: 1. Extend the signature of method CONSTRUCTOR of class CL_LWM_MOBILE_QUALITY_ISSUE with the three parameters IV_MATERIAL_PLANT Types QMAWERKS IV_MATERIAL Types MATNR IV_SHORT_TEXT Types QMTXT 2. Extend the exporting list of the CREATE OBJECT LO_QUALITY_ISSUE command in method CREATE_NOTIFICATION in class CL_LWM_QUALITY_ISSU_DPC by: IV_MATERIAL_PLANT = MS_ISSUE-MATERIAL_PLANT IV_MATERIAL = MS_ISSUE-MATERIAL IV_SHORT_TEXT = MS_ISSUE-SHORT_TEXT 3. Extend attribute list of class CL_LWM_MOBILE_QUALITY_ISSUE by HDR_MATERIAL_PLANT Types QMAWERKS HDR_MATERIAL Types MATNR 4. Add the following code to the end of method CONSTRUCTOR move IV_MATERIAL_PLANT to HDR_MATERIAL_PLANT. move IV_MATERIAL to HDR_MATERIAL. move IV_SHORT_TEXT to HDR_SHORT_TEXT. 5. Extend the signature of method PREP_NOTIFHEADER of class CL_LWM_MOBILE_QUALITY_ISSUE by the parameters IV_MATERIAL_PLANT Types QMAWERKS IV_MATERIAL Types MATNR 6. Add the following code at the end of method PREP_NOTIFHEADER move IV_MATERIAL_PLANT to LS_NOTIFHEADER-MATERIAL_PLANT move IV_MATERIAL to LS_NOTIFHEADER-MATERIAL.

3.4 Pass additional fields after issues are selected After extension of the service definition for the display of issue reports the following coding needs to be adjusted. Method POST_SELECT_NOTIFS class CL_LWM_QI_SELECT_NOTIF add the following code at the end of the method: ls_selected_notifs-material_plant = is_notif-mawerk. s_selected_notifs-material = is_notif-matnr.

3.5 Add functionality reading data for e.g. value help (list of material numbers, material description for material number etc.)

For this task a new entity type needs to be created and a new function to read the data. A new method similar to the methods found in CREATE_ENTITY_TYPES in class CL_LWM_QUALITY_ISSUE_MD needs to be added to that method to create a new entity. A new function needs to be created in method CREATE_ACTION. To read material tests I would e.g. recommend a new entity MATERIAL_DESCR with key field MATERIA and property MATERIAL_TEXT and a function with parameters PLANT and MATERIAL.