Rds Qissue Mgmt Qim10v2 How to Qim en Xx

EHP7 for SAP ERP6.0 October 2014 English Tips&Tricks for Implementation of Quality Issue Management (QIM) SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Copyright © 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. © SAP SE Page 2 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Content Tips & Tricks............................................................................................................................. 5 1 System Access.................................................................................................................. 5 1.1 How to Setup the Access to Other Systems............................................................5 2 POWL/Worklists................................................................................................................. 6 2.1 How to Setup the POWL in the System...................................................................6 2.2 How to Change the Layout of the Power Lists (Work Lists).....................................7 2.2.1 How to Display Additional Fields in a Power List for an Issue/Activity.................7 2.2.2 How to Change the Displayed Fields in Section Issue/Activity Details................8 2.3 How to do a flexible Selection According to Variable User or Business Partner......8 2.4 How to do a flexible Selection According to Calculated Dates.................................9 2.5 How to implement a BAdI for Pushbuttons in Issue or Activity Worklists...............10 2.6 How to implement a BAdI for Date Calculation in Activities...................................11 3 UI Adaptions.................................................................................................................... 13 3.1 How to Redefine Terminology................................................................................13 3.1.1 Copy Message Class /IAM/OBJECT to Customer Namespace and Modify Messages........................................................................................................................ 13 3.1.2 Create Data Type.............................................................................................. 14 3.1.3 Create Redefinition............................................................................................ 15 3.1.4 Use Redefinition in Application..........................................................................16 3.2 How to Add New Time Points and Quantity Fields.................................................16 3.2.1 Create Data Element......................................................................................... 17 3.2.2 Define Quantity Code........................................................................................ 18 3.2.3 Maintain User Interface Configuration...............................................................18 3.3 How to Add New Code Fields................................................................................19 3.3.1 Add Text Types to Text Schema........................................................................19 3.3.2 Define Settings for Text Types...........................................................................20 3.3.3 Add Text Fields to User Interface.......................................................................21 3.4 How to Add Additional Columns within the Activities Table of an Issue..................22 3.4.1 Adjust Configuration – Add Columns in Existing Table......................................22 3.5 How to Implement a User Status to SAP QIM.......................................................23 3.5.1 Create Domain and Data Element for User Status............................................23 3.5.2 Create Enhancement (via BOPF Enhancement Workbench) to Create Append 25 3.5.3 Create Business Object Enhancement..............................................................25 3.5.4 Create Actions for Status Change and Define Dependencies (to Lifecycle Status) 26 3.5.5 Add a Button and a Field to Set and Display the User Status...........................27 3.6 How to Implement Issue Type-Dependent Configurations.....................................30 3.6.1 Adjust Configuration – Create a Context Based Adaption.................................30 4 Issue Processing............................................................................................................. 31 4.1 How to Activate the QIM Workflow.........................................................................31 4.2 How to implement a Workflow for Notification of New Issues................................32 4.3 How to implement a Problem-Solving Process Using 8D Methodology.................34 4.3.1 Activate BCSets for 8D......................................................................................35 4.3.2 Define Issue Types............................................................................................ 35 © SAP SE Page 3 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 4.3.3 Define Steps for Problem-Solving Methodologies.............................................36 4.3.4 Define Settings for Steps for Problem-Solving Methodologies..........................36 4.3.5 BAdI: Influence Copying of Activities.................................................................37 4.3.6 Adapt Print Form............................................................................................... 38 4.3.7 How to generate a 8D Report............................................................................38 4.4 How to enhance Definition and Assignment of Reference Objects........................43 4.5 How to implement Side Panel for Applications for Processing Issues and Activities 44 4.6 How to implement Archiving of Activities and Issues.............................................46 4.6.1 Archiving Activities with /IAM/ACT.....................................................................46 4.6.2 Archiving Issues with /IAM/ISSUE.....................................................................49 4.7 Further References................................................................................................ 52 © SAP SE Page 4 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Tips & Tricks 1 System Access 1.1 How to Setup the Access to Other Systems Use This section explains how to enable the access to other systems in order to display additional quality related information (for example, quality notifications, audit actions, quality notification tasks, …) from other systems in the QIM POWLs. The documented example demonstrates how to display quality notifications from a connected SAP ERP system. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Work lists for Quality Issues and Activities  Define Access to Quality Issues Transaction Code n/a 2. On the Change View “General Settings for Issues”: Overview screen, select object type I and double-click the Object Categories folder. 3. On the Change View “Object Categories”: Overview screen, select object category QI_QMNO (Quality Notification) and double-click the System-Dependent Settings folder. 4. On the Change View “System-Dependent Settings”: Overview screen, enter the following data: Field Name Entry Logical System Enter the logical system containing the quality notifications (for example, RD6CLNT002) you want to display in the QIM POWLs If the target logical system is supported, the icon displayed in the Supported field will be green. If the target system is not supported, the icon will be grey. You have to set up the access to the target logical system in transaction SM59 before. Furthermore, you have to define the logical system itself (search for Define Logical Systems in the IMG tree). 5. Choose Save. 6. Choose Back (F3) to get back to the Object Categories folder. 7. Ensure that object category QI_QMNO (Quality Notification) is set active. Otherwise enter the following data in table Object Categories. Field Name Entry Active Set flag 8. Choose Save. 9. Choose Back (F3) twice. © SAP SE Page 5 of 54 SAP Best Practices 2 Tips&Tricks for Implementation of Quality Issue Management (QIM) POWL/Worklists 2.1 How to Setup the POWL in the System 1. You are logged in the SAP QIM system using SAP NetWeaver Business Client and are on the SAP QIM Home screen. Different Logon Options: Via SAP NetWeaver Business Client (regular way) a. Click on the Icon SAP NetWeaver Business Client. b. Open the link to your SAP QIM system. The system displays the home screen of your QIM system. Via SAP GUI and SAP NetWeaver Business Client for HTML a. Open your SAP QIM system and enter the transaction code nwbc. b. Select your user role for QIM Issue_Driver. The system displays the home screen of your QIM system. 2. Choose Work lists to navigate to your work lists. You can either define a new worklist or change an existing worklist to display the quality notifications saved in the connected SAP ERP system. In this example, we will define a new POWL. 3. Choose New Work List. 4. On the New Work List screen, enter the following data: 5. 6. 7. 8. 9. 10. Field Name Entry Selected Object Type Generic Quality Issues If you want to create a POWL for displaying quality related activities, choose Generic Quality Activities instead. Choose Next to maintain the selection criteria. Position the cursor in the Combination of Object Category and Source System field and choose F4. In the Search: Combination of Object Category and Source System screen, choose Search to display all available connected systems and their respective object categories. Select the appropriate combination of object category and logical system (for example, QI_QMNO/ RD6CLNT002). If necessary, you can maintain other selection criteria like materials, creation time, and so on. Choose Next. Enter the following data: Field Name Entry Enter Query Description enter a description for your new query Activate Query Set flag © SAP SE Page 6 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Field Name Entry Select Category Issues (select from the drop-down menu) 11. Choose Finish to create the new query. If you want to personalize the queries regarding the setting for refreshing them automatically or manually, choose Set Default Query and select manual only or on first page visit. 2.2 How to Change the Layout of the Power Lists (Work Lists) Use This section describes how to display additional columns in a work list used to display issues and activities. Furthermore, it explains how to display additional fields (e.g. role assignment and business partner name of issue responsible) in the detailed view for an issue/activity on the page Worklists in the QIM application. 2.2.1 How to Display Additional Fields in a Power List for an Issue/Activity Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Development Programming Environment  Messages Transaction Code NWBC 2. Choose applicable role (for example, Z_SAP_QIM_ISSUE_DRIVER. 3. In the navigation pane choose Worklists. 4. On the Worklists page, open the issue/activity work list you want to modify (for example, Quality Issues YCC). 5. Choose Open Settings Dialog (upper right corner of the table view of the work list). 6. On the Settings screen choose tab Column Selection, select entry User status and choose Add to add the column User status to the displayed columns. If you want to change the order of the displayed columns (e.g. move one column one step to the left), select the applicable column and move it to the desired location by choosing Move Selected Columns Up or Move Selected Columns Down. 7. Choose OK. If desired, you can save this view or create a new table view by choosing Save or Save As, respectively before choosing OK. © SAP SE Page 7 of 54 SAP Best Practices 2.2.2 Tips&Tricks for Implementation of Quality Issue Management (QIM) How to Change the Displayed Fields in Section Issue/Activity Details Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Development  Programming Environment  Messages Transaction Code NWBC 2. Choose an applicable role (for example, Z_SAP_QIM_ISSUE_DRIVER. 3. In the navigation pane, choose Worklists. 4. On the Worklists screen, right-click an empty screen area below the table view of the actual work list. 5. Choose Technical Help... from the context menu. 6. On the Technical Help screen, choose Application Configuration QIM_GQIA_POWL_OVP. 7. On the Application Configuration QIM_GQIA_POWL_OVP screen, in table Assign Web Dynpro Component choose component usage OVP, configuration name QIM_GQIA_POWL_OVP_CC. 8. On the Component Configuration QIM_GQIA_POWL_OVP_CC, choose the Overview Page Schema tab, expand the Section: SECTION_1 node and select UIBB for Configuration ID QAM_GQI_POWL_PREVIEW_CC or QAM_GQA_POWL_PREVIEW_CC to modify the details section of an issue or activity, respectively. 9. Choose Configure UIBB. In this example, the detailed section of an activity is modified. Therefore select UIBB for Configuration ID QAM_GQI_POWL_PREVIEW_CC. 10. Choose Edit to change from display to edit mode. 11. In section Preview, choose Element  Add Element (STRG+E) and select the element that shall be displayed on the screen from the displayed list. Choose Partner Role and Partner Role Name from the list and choose OK. 12. Position both fields to the desired location and change the display types to Text View. 13. Choose Save and select Local Object. 2.3 How to do a flexible Selection According to Variable User or Business Partner Use When you define queries for work lists for issues and activities, you can use flexible selection options by means of variables for the business partner. You can define a default query for a work list that shows for each individual user which QIM issues or QIM activities he or she is assigned to. This is possible if you enter a variable in the respective selection field, which is then replaced by the current user or business partner who opens the work list. You can use the following variables: <USER2UNAME> – is replaced by the current user ID © SAP SE Page 8 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) <USER2BP> – is replaced by the business partner ID for the current user You can also use the variables in the front end during user-specific creation of a new work list. This is useful, for example, if the business partner has to be entered in a field but the current user does not know the business partner assigned to him or her. The user can then enter the variable <USER2BP> in the respective selection field. Prerequisites   You have assigned the conversion class CL_QAM_MAP_USER2PARTNER to the user or business partner search field in SMT mapping (see also Structure Mapping). If you want to use the variable <USER2BP>, the business partner for the user must exist. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Worklists for Quality Issues and Activities  Make Settings in POWL Cockpit Transaction Code POWL_COCKPIT 2. On the POWL Administrator Cockpit screen select Standard POWL and choose Execute (F8). 3. On the Display View “Maintain application ID”: Overview screen select the personalization application QIM_GQIA_POWL (Work list for Generic Quality activities and Issues) and choose Register Query. 4. On the Display View “Register POWL Query (Role based)”: Overview choose Maintain Query. 5. Double-click the query (QIM_GQA_QA or QIM_GQI_QI) for which you want to use a variable and choose Query Parameters. 6. Decline the following popup. 7. In the Parameters for query screen enter the corresponding variable in the partner or partner role field and choose Cancel.. 8. Choose Save. 2.4 How to do a flexible Selection According to Calculated Dates Use When you define queries for worklists for issues and activities, you can use flexible selection options by means of variables for having the system calculate dates. You can define a default query for a worklist whose selection is not based on fixed dates but for which the timeframe is calculated relatively in the future. You can select objects whose requested end will be reached in four weeks, for example. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG © SAP SE Page 9 of 54 Cross-Application Components  Quality Issue Management  Worklists for Quality Issues and Activities  Make Settings in POWL Cockpit SAP Best Practices Transaction Code Tips&Tricks for Implementation of Quality Issue Management (QIM) POWL_COCKPIT 2. On the POWL Administrator Cockpit screen select Standard POWL and choose Execute (F8). 3. On the Display View “Maintain application ID”: Overview screen select the personalization application QIM_GQIA_POWL (Worklist for Generic Quality activities and Issues) and choose Register Query. 4. On the Display View “Register POWL Query (Role based)”: Overview choose Maintain Query. 5. Double-click the query for which you want to define a calculated date and choose Maintain Query. 6. If necessary, switch to change mode and choose Calculated Dates. 7. In the Define Calculated Dates screen select the from the input help the desired From and To dates for the requested start and requested end and choose Accept. 8. Choose Save. 2.5 How to implement a BAdI for Pushbuttons in Issue or Activity Worklists Use With the two new Business Add-Ins (BAdIs) QAM_ISSUE_WORKLIST_BUTTONS and QAM_ACTIVITY_WORKLIST_BUTTONS) you can define your own pushbuttons in the worklists for issues as well as in worklists for activities and thus, for example, implement your own print or export function. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG For pushbuttons in Issues: Cross-Application Components  Quality Issue Management  Worklists for Quality Issues and Activities  Business Add-Ins (BAdIs) for Enhancement of Lists of Worklists  BAdI: Pushbuttons in Worklist for Issues For pushbuttons in Activities: Cross-Application Components  Quality Issue Management  Worklists for Quality Issues and Activities  Business Add-Ins (BAdIs) for Enhancement of Lists of Worklists  BAdI: Pushbuttons in Worklist for Activities Transaction Code 2. 3. 4. 5. n/a Choose Execute. On the Implementations for BAdI Definition QAM_ISSUE_WORKLIST_BUTTONS screen (or the Implementations for BAdI Definition QAM_ACTIVITIES_WORKLIST_BUTTONS screen) choose Create Implementation. Confirm the information message. In the Create Enhancement Implementation screen enter the following data: Field Name Entry Enhancement Implementation Enter an ID for your enhancement implementation Short Text Enter a short text for your enhancement implementation © SAP SE Page 10 of 54 SAP Best Practices 6. 7. 8. 9. 10. 11. 12. 13. Tips&Tricks for Implementation of Quality Issue Management (QIM) Choose Creation of Enhancement. In the Create Object Directory Entry screen enter a package name and choose Save. Please be aware that you have to use your customer namespace for naming the package. For example the package name could start with “Z” or “Y”. In the Enhancement Implementation …: Create BAdI Implementations screen enter a BAdI implementation and an implementation class and choose Continue. In the Create BAdI Implementation screen decide whether to reuse the example implementation (in this case select the example implementation) or to create an empty class (to do so choose Create Empty Class), to copy a sample class (to do so choose Copy Sample Class), or to inherit from a sample class (to do so choose Inherit from Sample Class). In the Create Object Directory Entry screen enter a package and choose Save. In the Enhancement Implementation … Change screen drill-down the BAdI implementation tree. Double-click your implementation class. Adapt the class and adapt the following methods to your personal needs:  IF_EX_QAM_ISSUE_POWL_BUTTONS~HANDLE_BUTTON_ACTION or IF_EX_QAM_ACTIVITY_POWL_BUTTON~HANDLE_BUTTON_ACTION, respectively (to define other pushbuttons (actions), which are displayed to the right of the application pushbuttons).Parameters: ET_ACTION_DEF: This table contains the definition of the new pushbuttons. Start the technical name of the action (ACTIONID field) with Z.  IF_EX_QAM_ISSUE_POWL_BUTTONS~GET_BUTTON_ACTION or IF_EX_QAM_ACTIVITY_POWL_BUTTON~GET_BUTTON_ACTION, respectively (to specify what the system should do when an action (pushbutton) defined in the BAdI method GET_BUTTON_ACTION is called). 14. Double-click the top root node and set the flag Implementation is active to activate your class. 15. Choose Activate to activate your BAdI-Implementation. 16. Choose Save. 2.6 How to implement a BAdI for Date Calculation in Activities Use You can use this BAdI to calculate one or more timepoints for one or more activities. For example, you can use it to automatically calculate an expected end date of an activity from an expected start date entered for this activity using the duration maintained for the corresponding activity template in the Customizing settings. An example implementation is delivered for this use case. The BAdI is called via the business object layer of the application. It is closely related to the date node of the activity business object:  It is triggered either implicitly by relevant changes to activity date node data, or explicitly via a direct call of a related activity function at date node level.  The system will always store the calculation results in this node. Prerequisites The BAdI methods will only be executed if: © SAP SE Page 11 of 54 SAP Best Practices   Tips&Tricks for Implementation of Quality Issue Management (QIM) The system detects an implicit trigger. (A BAdI implementation can override or stop an implicit execution.) Changes to the following activity attributes will implicitly start the execution of the BAdI: o Change of the date/time value of an activity date o Change of the role code of an activity date o Change of the source time zone code of an activity date The BAdI is triggered explicitly for example if a user has clicked on a button. This can be done by calling the action SCHEDULE_DATES of the node DATE in the business object /IAM/Activity as a reaction to a button click (for more information about calling business object actions, see the BS_FND BOPF Enhancement Workbench documentation attached to SAP Note 1457235). Procedure 1. 2. 3. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Issue Processing  Business Add-Ins (BAdIs)  BAdI: Date Calculation for Activities Transaction Code n/a Choose Execute (F8). On the Implementations for BAdI Definition /IAM/BADI_SCHED_ACTIVITY screen choose Create Implementation. The enhancement implementation /IAM/ACT_END_DATE_CALCULATE is already delivered as an active implementation. If you want to create your own implementation from scratch, remove the Active flag before choosing Create Implementation. For more details on the functions of this implementation see the enhancement implementation documentation. 4. 5. 6. 7. 8. 9. Confirm the information message, if necessary. On the Create Enhancement Implementation screen enter the applicable data and choose Creation of Enhancement. In the Create Enhancement Implementation screen enter the following data: Field Name Entry Enhancement Implementation Enter an ID for your enhancement implementation Short Text Enter a short text for your enhancement implementation Choose Creation of Enhancement. In the Create Object Directory Entry screen enter a package name and choose Save. In the Enhancement Implementation …: Create BAdI Implementations screen enter a BAdI implementation and an implementation class and choose Continue. © SAP SE Page 12 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 10. In the Create BAdI Implementation screen decide whether to reuse the example 11. 12. 13. 14. implementation (in this case select the example implementation) or to create an empty class (to do so choose Create Empty Class), to copy a sample class (to do so choose Copy Sample Class), or to inherit from a sample class (to do so choose Inherit from Sample Class). In the Create Object Directory Entry screen enter a package and choose Save. In the Enhancement Implementation … Change screen drill-down the BAdI implementation tree. Double-click your implementation class. Adapt the class and adapt the following methods to your personal needs:  /IAM/IF_EX_SCHED_ACTIVITY~DETERMINE_OPTIONS (to prepare the execution of the calculation, for example, preselect necessary data or perform additional checks to decide whether the calculation shall be executed at all or shall be executed automatically, and for which specific dates it shall be done.)  /IAM/IF_EX_SCHED_ACTIVITY~CALCULATE (to execute the required date calculations) 15. Double Click Filter Val. and choose Create Filter Combination. 16. In the Choose Filter screen select the entries for filter CLIENT and TIME_POINT_ROLE_CODE and choose Continue. 17. In the Enhancement Implementation … Change screen double-click filter CLIENT and maintain your desired filter values. Repeat this step for the filter TIME_POINT_ROLE_CODE. The filter TIME_POINT_ROLE_CODE defines the role code of the timepoint for which the calculation shall be performed. Timepoints are defined in Customizing: Cross-Application Components  Quality Issue Management  Basic Settings  Define Timepoints. The filter CLIENT defines the system client for which the calculation shall be performed. 18. Double-click the top root node and set the flag Implementation is active to activate your class. 19. Choose Activate to activate your BAdI-Implementation. 20. Choose Save. 3 UI Adaptions 3.1 How to Redefine Terminology This section describes how to adapt messages, texts for object types, and interface texts to the terminology commonly used in your enterprise. For example, the object type Issue can be renamed to Problem or the standard object message Status of issue changed from X to Y can be redefined to Status of problem changed from X to Y. 3.1.1 Copy Message Class /IAM/OBJECT to Customer Namespace and Modify Messages Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Development  Programming Environment  Messages Transaction Code SE91 2. On the Message Maintenance: Initial Screen, enter the following data: © SAP SE Page 13 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Field Name Entry Message class /IAM/OBJECT 3. Choose Copy Message Class. 4. On the Copy Message Class screen, enter the following data: Field Name Entry To message class Y_IAM_OBJECT 5. Choose Continue. 6. Choose Local Object. 7. On the Message Maintenance: Initial Screen, enter the following data: Field Name Entry Message class Y_IAM_OBJECT Messages Set flag Number 290 8. Choose Change. 9. On the Message Maintenance: Change Messages screen, change message as follows: Field Name Old Entry Old Entry Message Short Text Status of issue changed from &1 to &2 Status of problem changed from &1 to &2 10. Choose Save. 11. Choose Back (F3). The redefinition is valid on the client level. 3.1.2 Create Data Type Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Development  ABAP Dictionary Transaction Code SE11 2. On the ABAP dictionary: Initial Screen, enter the following data: Field Name Entry Data type Set flag Data type /IAM/ISSUE_TYPE 3. Choose Copy… 4. On the Copy Data Element screen, enter the following data: Field Name Entry To Data Element Y_IAM_PROBLEM 5. Choose Continue. © SAP SE Page 14 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 6. Choose Local Object. 7. On the ABAP dictionary: Initial Screen, enter the following data: Field Name Entry Data type Set flag Data type Y_IAM_PROBLEM 8. Choose Change. 9. On the Dictionary: Change Data Element screen enter the following data: Field Name Entry Short Description Problem Type 10. Choose tab strip Field Label and enter the following data: Field Name Lenght Entry Value Short 10 Prob Typ Medium 15 Problem Type Long 20 Problem Type Heading 10 Prob Typ 11. Choose Activate. 12. Choose Save. 13. Choose Back (F3) twice. 3.1.3 Create Redefinition Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Environment  Redefine Terminology Transaction Code SPRO 2. On the Change View “Terminology Redefinition”: Overview screen, choose New Entries and enter the following data: Field Name Entry Value Redefin. Y01 Redefinition Text Issue2Problem Message Class /IAM/OBJECT Cust. Message Class Y_IAM_OBJECT 3. Select redefinition Y01 and double-click the Redefinition of Object Types folder in the dialog structure. 4. On the Change View “Redefinition of Object Types”: Overview screen, choose New Entries and enter the following data: Field Name Entry Value Obj. Type ITY Data Type Y_IAM_PROBLEM © SAP SE Page 15 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 5. Choose Save. 6. Choose Back (F3) twice. Interface texts which are displayed as alias names must be changed by using transaction SOTR_EDIT: On the OTR: Maintain Initial Screen, choose the applicable language for the text you want to create, enter an alias name and choose Create. On the OTR: Change Concept screen, enter the package name $TMP, the object type WDYV, and the required text. Choose Save. After having created the OTR text, access customizing as described in this section (see step 3) and enter the OTR redefinition in “Redefinition of User Interface Texts” instead. 3.1.4 Use Redefinition in Application If the redefinition should be used when creating a quality issue (or quality problem as it will be called here) in quick mode proceed as follows. Procedure 1. In SAP GUI, choose Favorites  Add other objects. 2. On the Add additional objects screen, select Web Dypro Application. 3. On the Web Dynpro Application screen enter the following data by using the input help (F4): Field Name Entry Value Web Dynpro Applicat. QIM_OVP_ISSUE_CRT Description Issue Creation via Quick OVP Application Config. QIM_OVP_ISSUE_CRT Parameter Name Redefinition Parameter Value Y01 4. Choose Continue. 5. When starting the application via this link, the defined redefinition will be used. In addition to creating a new link in SAP GUI, you can store the redefinition that you have created in QIM Customizing in the following places:  As the user parameter /IAM/REDEFINITION in the user master record in transaction SU01 (centrally) or SU3 (by the users themselves).  As an application parameter in the menu for the role (transaction PFCG) in the details view of a Web Dynpro application. 3.2 How to Add New Time Points and Quantity Fields Use Quantity codes are different types of quantities that are used in an application based on the Issue and Activity Management component. Each quantity code corresponds to an input field on the © SAP SE Page 16 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) user interface. If you want to define a new quantity code or if you do not want to use the quantity codes provided, you must adapt the FPM UI configuration. As soon as a code is used in the configuration, you can no longer delete it, otherwise the application that uses the configuration will abort. This also applies for time points. 3.2.1 Create Data Element Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Development  ABAP Dictionary Transaction Code SE11 2. In the ABAP Dictionary: Initial Screen screen, select Data type and enter a name for the new data element, e.g. Y_QIM_AddQuantity. 3. Choose Create. 4. In the popup window Create Type, select Data element and choose Continue. 5. In the Dictionary: Change Data Element screen, enter the following data: Field Name Entry Domain Select radio button Domain /IAM/QTY_DF34_DEC_SIGN Short Description For example, Additional Quantity for QIM By assigning the domain /IAM/QTY_DF34_DEC_SIGN to the data element, the data type of the element is specified (decimal floating point of length 31 with 14 decimal places). If you want to create a data element for a time point, you have to enter the following data instead: Field Name Entry Predefined Type Select radio button Data Type DATS Short Description e.g. Additional time point for QIM 6. Choose the Field Label tab and enter the following data: Length Field Label Short 10 Add.Qty Medium 15 Addit.Qty Long 25 Additional Quantity Heading 17 Additional Qty 7. Choose Save. 8. Choose Local Object 9. Choose Activate (STRG+F3). © SAP SE Page 17 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 10. Choose Back (F3) twice. 3.2.2 Define Quantity Code Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: IMG Path Cross-Application Components  Quality Issue Management  Basic Settings  Define Quantity Codes Transaction Code SPRO 2. In the Change View “Quantity Codes”: Overview screen choose New Entries. 3. In the New entries: Overview of Added Entries screen enter the following data: Field Name Entry Value Role Code YQT Text Additional Quantity Quantity Element Y_QIM_AddQuantity 4. Choose Save If the usage of a quantity code should be restricted to a specific application (for example, QIM, Issues), select the newly created entry and double-click the Quantity Code Usage Restrictions folder. Choose New Entries and enter the following data: Field Name Entry Appl. QIM Business Object /IAM/ISSUE 5. Choose Save. 6. Choose Back (F3) twice. 3.2.3 Maintain User Interface Configuration If you define a new quantity code (or if you do not want to use the quantity codes provided), you must adapt the FPM UI configuration in order to display the new quantity code in the application. This example describes how to add the Additional Quantity field on the quick creation screen. These adjustments of the user interface only can be carried out in DE, since the original language of this UI is DE. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Overview  Object Navigator Transaction Code SE80 2. In the Object Navigator screen click Repository Browser. 3. Choose Package from the drop-down menu. 4. Choose package QAM_UI. © SAP SE Page 18 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 5. Drill down the following menu path: QAM_UI  Web Dynpro  FPM Applications  QIM_OVP_ISSUE_CRT  FPM Application Configurations  QIM_OVP_ISSUE_CRT. 6. Double-click configuration QIM_OVP_ISSUE_CRT. 7. Choose Display Configuration to open the application configurator in NWBC for HTML. 8. On the Application Configuration QIM_OVP_ISSUE_CRT screen click configuration QIM_OVP_ISSUE_QUICK_CRT_CC to open the corresponding component configuration. 9. On the Component Configuration QIM_OVP_ISSUE_QUICK_CRT_CC, Main Screen screen choose tab strip Overview Page Schema and expand node Section: SECTION_1. 10. Click Element UIBB, Component FPM_FORM_UIBB_GL2 and choose Configure UIBB. 11. In the Component Configuration FPM_FORM_UIBB_GL2 screen, choose Edit to switch from display to edit mode, if not already in edit mode. 12. Choose tab strip Preview and select the line where you want to display the new field. 13. Choose Element  Add Element (STRG+E). 14. In the Add Fields screen choose Group Additional Quantity. 15. Select lines QUANTITYYQT and UNIT_TEXTYQT and choose OK. 16. Select field UNIT_TEXTYQT and change field type to Text View. Furthermore, remove the label by choosing Label Visibility: Is not visible. 17. Position both fields to the desired positions via drag-and-drop. You can also specify the desired positions directly using a grid when filling in the fields Start Row of Element, End Row of Element, Start Column of Element, and End Column of Element which are located in section Position on tab Attributes of Element. 18. Choose Save. You may test the modified configuration by choosing Additional Functions  Test. If you want to display the additional field on the screens used for advanced and guided creation of an issue, modify the component configurations QIM_OVP_ISSUE and QIM_GAF_ISSUE_CRT, respectively. 3.3 How to Add New Code Fields Use SAP QIM offers the ability to add new code fields on issue, activity, effect and defect level. For example, this can be used to specify a defect location or to enter an organizational unit being responsible for issue investigation. As predefined codes (instead of free-text fields) are used, the available information can afterwards be processed more effectively. 3.3.1 Add Text Types to Text Schema Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: © SAP SE Page 19 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) SAP QIM IMG Cross-Application Components  Processes and Tools for Enterprise Applications  Reusable Objects and Functions for BOPF Environment  Dependent Object Text Collection  Maintain Text Schema Transaction Code SPRO 2. On the Change View “Text Type”: Overview screen choose New Entries. 3. On the New Entries: Overview of Added Entries screen enter the following data: Field Name Entry Text Type YCT Description CAPA Type 4. Choose Enter. 5. Select text type YCT and double-click Text Type to Text Schema Assignment in the dialog structure. 6. On the Determine Work Area: Entry screen enter the following data: Field Name Entry Text Schema QIM_ISSUE Depending on the level where the new code fields shall be added, the text scheme needs to be chosen (e.g. issue level: QIM_ISSUE, cause level: QIM_CAUSE, defect level: QI_DEFECT, effect level: QIM_EFFECT or activity level: QIM_ACT). 7. Choose Continue. 8. On the Change View „Text Type to Text Schema Assignment“: Overview screen choose New Entries. 9. On the New Entries: Overview of Added Entries screen enter the following data: Field Name Entry Text Type YCT 10. Choose Save. 11. Choose Back (F3) twice. 3.3.2 Define Settings for Text Types Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Basic Settings  Text Types  Define Settings for Text Types Transaction Code SPRO 2. On the Change View “Define Catalog for Text Type”: Overview screen choose New Entries. 3. On the New Entries: Overview of Added Entries screen enter the following data: Field Name Entry Text Type DIVIS Catalog DIV © SAP SE Page 20 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Field Name Entry Hist. Text Historical Text The catalog (e.g. catalog divisions, code-group divisions, code-assignment research, production, sales) needs to be in the system. Otherwise you need to maintain it (SAP QIM IMG: Cross-Application Components  Quality Issue Management  Issue Processing  Codes  Define Catalogs and Code Groups) before you can assign it here. 4. Choose Save. 3.3.3 Add Text Fields to User Interface Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Overview  Object Navigator Transaction Code SE80 2. On the Object Navigator screen, choose Repository Browser. 3. Choose Package from the drop-down menu. 4. Choose package QAM_UI. 5. Choose QAM_UI  Web Dynpro  FPM Applications  QIM_OVP_ISSUE  FPM Application Configurations  QIM_OVP_ISSUE. 6. Double-click the configuration that needs to be modified (for example, QIM_OVP_ISSUE). 5. Choose Display Configuration to open the application configurator in NWBC for HTML. 6. On the Application Configuration QIM_OVP_ISSUE screen, choose configuration QIM_OVP_ISSUE_CC to open the corresponding component configuration. 7. On the Component Configuration QIM_OVP_ISSUE_CC, Main Screen “MAIN” screen, choose tab strip Overview Page Schema and expand node Section: SECTION_1. 8. Choose element UIBB, Component QIM_OVP_ISSUE_OVERVIEW_FORM and choose Configure UIBB. 9. In the Component Configuration QIM_OVP_ISSUE_OVERVIEW_FORM screen, choose Navigation & Repositories  Repositories to open the object repository. 10. Choose Edit to switch from display to edit mode, if not already in edit mode. 11. In the dialog structure Repositories enter the following data: Field Name Entry Filter CAPA Type 12. Drag&drop the desired fields from the repository to their desired locations on the screen. To display the field Code as input field, drag&drop the field CODEYCT to the screen. If you also want to display the value for CAPA code, add the field CODE_TYTYCT to the screen and change the display type to Text View. To do so, select the field CODE_TYTYCT in the Preview tab, scroll down to the Attributes of Element tab and change the display type to Text View. 13. Choose Save. © SAP SE Page 21 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) If desired, the new component configuration can be tested by choosing Additional Functions  Test. Result You have added an additional code field on issue level. The field must be added for each issue input method (quick, guided, and advanced mode) separately, if required. If the new field has been added to the advanced view, the field will also be displayed when editing an issue (independently of the respective mode the issue was created in), as the same user interface form is used in the advanced creation mode and the issue display mode. The component configuration is language dependent and must be edited for each language separately, as long as there are no language dependent OTR texts are used. To access the new configuration, create a new favorite in the SAP Gui for a Web Dynpro Application: Choose Favorites  Add other objects  Web Dynpro Application), enter the following data and choose Continue: Field Name Entry Web Dynpro Applicat. QIM_OVP_ISSUE Description <Description Text> Application Config. The name of the new or modified application configuration, for example, QIM_OVP_ISSUE 3.4 How to Add Additional Columns within the Activities Table of an Issue This example describes how to display additional columns in the activities assignment tab of an issue. For example, you can display (and fill in) the activity description directly in the activities assignment table. 3.4.1 Adjust Configuration – Add Columns in Existing Table These adjustments of the user interface only can be carried out in DE, since the original language of this UI is DE. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Overview Object Navigator Transaction Code SE80 2. On the Object Navigator screen, open package QAM_UI and drill down to the web dynpro component configuration you want to modify (e.g. QAM_UI  Web Dynpro  Component © SAP SE Page 22 of 54 SAP Best Practices 3. 4. 5. 6. 7. 8. 9. Tips&Tricks for Implementation of Quality Issue Management (QIM) Configurations  QIM_OVP_ISSUE_ACTIVITY_TREE) and double-click this component configuration. Select the component configuration and choose Display Configuration. Choose Edit to switch from display to edit mode. On tab Tree UIBB Schema, choose Add Column. Select the column you want to add and choose OK. To modify the display type, select the applicable entry and choose the desired display type (for example, Text Field) from the drop-down menu of column Display Type. To change the order of columns, select the applicable column and choose Up or Down to move the column to the desired position. Choose Save and select Local Object. To display the digital signature status of an activity via a symbol, select Display Type Image instead of Text Field. 3.5 How to Implement a User Status to SAP QIM SAP QIM offers the ability to add a user status concept. The approach is based on the extensibility of Web Dynpro applications, not on the user status concept as in SAP ERP. We will describe how to implement a user status which is used to document the status of board approval of the issue. Preliminary Remarks The following section describes how to modify the default web dynpro application configuration of QIM. In a customer system, the default settings should not be changed. Instead, it is recommended to copy the default web dynpro application configuration and all dependent component configurations into the customer namespace and make the required settings there. The customer specific application configuration can then be called by assigning them to the PFCG role or by creating a favorite entry in the user menu of the SAP GUI. 3.5.1 Create Domain and Data Element for User Status Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP ERP Menu Tools  ABAP Workbench  Development  ABAP Dictionary Transaction Code SE11 2. On the ABAP Dictionary: Initial Screen screen mark the radio button Domain and enter a name for your domain, e.g.: Field Name Entry Value Domain ZZ_USERSTATUS1 3. Choose Create. 4. On the Dictionary: Change Domain screen choose tab Definition and enter the following data: © SAP SE Page 23 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Field Name Entry Value Short Description User Status QIM Data Type CHAR No. Characters 2 5. Choose tab Value Range and enter your user status data, e.g.: Fix. Val. Short Descript. Initial 6. 7. 8. 9. 02 To be approved by board 03 Approved by board 04 Rejected by board Choose Save. Choose Activate. Choose Back (F3). On the ABAP Dictionary: Initial Screen screen mark the radio button Data type and enter a name for your new data element, for example: Field Name Entry Value Data type ZZ_USERSTATUS1 10. Choose Create. 11. On the Create Type ZZ_USERSTATUS1 screen mark radio button Data element and choose Continue. 12. On the Dicitionary: Change Data Element screen choose tab Data Type and enter the following data: Field Name Entry Value Short Description User Status QIM Domain ZZ_USERSTATUS1 (use input help [F4] to select your domain) 13. On the Dicitionary: Change Data Element screen choose tab Field Label and enter the following data: Field Name Lenth Entry Value Short 10 U Stat QIM Medium 18 User Status QIM Long 18 User Status QIM Heading 18 User Status QIM 14. Choose Save. 15. Choose Activate. 16. Choose Back (F3) twice. © SAP SE Page 24 of 54 SAP Best Practices 3.5.2 Tips&Tricks for Implementation of Quality Issue Management (QIM) Create Enhancement (via BOPF Enhancement Workbench) to Create Append Procedure 1. Access the transaction using one of the following navigation option: Transaction Code BOBF 2. On the Business Object Processing Framework screen choose Business Object Browser and drill down the entry Business Process Objects. 3. Double-click the Business Process Object /IAM/ISSUE. 4. On the Display Business Object /IAM/ISSUE, Active Version screen drill down the entry Node Elements, check for node element Root, double-click the entry ROOT and open Extension Include /IAM/INCL_EEW_I_ROOT by a double-click on the respective entry on the right side (tab Node, area Data Model). 5. On the Dictionary: Change Structure screen (make sure to change from display to change mode, if applicable), choose Append Structure…. 6. In the Create Append Structure for /IAM/INCL_EEW_I_ROOT dialog box, enter a name for the new append structure, for example, ZZUSERSTATUS. 7. On the Dictionary: Change Append Structure screen, make the following settings: Field Name Entry Value Component ZZUSERSTATUS Typing Method Types Component Type ZZ_USERSTATUS1 Data Type CHAR Length 2 Short Description User Status QIM 8. Choose Save. 9. On the Create Object Directory Entry screen, choose Local Object. 10. Choose Activate to activate the newly created append structure. Make sure that you have the appropriate authorization for creating an append structure. 3.5.3 Create Business Object Enhancement Procedure 1. Access the transaction using one of the following navigation option: Transaction Code /n/BOBF/CUST_UI 2. On the Business Object Builder: Initial Screen screen, choose Create Business Object Enhancement. 3. The Create Enhancement Wizard starts. 4. Choose Continue and enter the following data: © SAP SE Page 25 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Field Name Entry Value Base Business Object /IAM/ISSUE Enhancement Name ZISSUE Description User Status QIM Namespace ZUS_ Prefix 5. Choose Continue  Continue. 6. Select Enhancement is extensible and choose Continue  Complete. 3.5.4 Create Actions for Status Change and Define Dependencies (to Lifecycle Status) 1. Access the transaction using one of the following navigation option: Transaction Code /n/BOBF/CUST_UI 2. On the Business Object Builder: Initial Screen screen, double-click in the Business Object Browser Business Object Enhancement ZUS_ZISSUE. 3. On the Business Object Builder: ZUS_ZISSUE screen, drill-down in the dialog structure the entry ZUS_ZISSUE. 4. Select Root and open the context menu by clicking the right mouse button. 5. Choose Create Action. 6. The Create an Action Wizard starts. 7. Choose Continue and enter action name and description for your action, e.g.: Field Name Entry Value Node Name ROOT Action Name ZUS_APPROVED Description Approved by board 8. Choose Continue and enter the following data. Field Name Entry Value Implementing Class /IAM/CL_SET_USER_STATUS Action Cardinality Multiple Node Instances Description /IAM/S_SET_USER_STATUS 9. Choose Continue. 10. Choose Complete. 11. Repeat step 5 to 10 and enter the following data: Field Name Entry Value Node Name ROOT Action Name ZUS_TO_BE_APPROVED Description To be approved by board Implementing Class /IAM/CL_SET_USER_STATUS © SAP SE Page 26 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Field Name Entry Value Action Cardinality Multiple Node Instances Description /IAM/S_SET_USER_STATUS 12. Repeat step 5 to 10 and enter the following data: Field Name Entry Value Node Name ROOT Action Name ZUS_REJECTED Description Rejected by board Implementing Class /IAM/CL_SET_USER_STATUS Action Cardinality Multiple Node Instances Description /IAM/S_SET_USER_STATUS 3.5.5 Add a Button and a Field to Set and Display the User Status Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: Transaction Code SE80 SAP ERP Menu Tools  ABAP Workbench  Overview  Object Navigator 2. In the Object Navigator screen choose Repository Browser and enter the following data: Field Name Entry Value Package QAM_UI 3. Choose Enter. 4. Drill-down the entry QAM_UI in the dialog structure. 5. Choose QAM_UI  Web Dynpro  Web Dynpro Applicat.  QIM_OVP_ISSUE  Appl. Configurations. 6. Double-click QIM_OVP_ISSUE. 7. In the Web Dynpro Explorer:Display Web Dynpro Configuration screen choose Start Configurator. 8. In the Editor for the Web Dynpro ABAP Application Configuration screen, make sure that the following entries are maintained and choose Continue in Change Mode: Field Name Entry Value Application Name QIM_OVP_ISSUE Configuration ID QIM_OVP_ISSUE 9. In the Application Configuration QIM_OVP_ISSUE screen, open sub screen Assign Web Dynpro Component and click Configuration Name QIM_OVP_ISSUE_CC. © SAP SE Page 27 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 10. On the Component Configuration QIM_OVP_ISSUE_CC, Main Screen “MAIN” screen access the Toolbar Schema tab, open and select node Global Toolbar and choose Add Toolbar element. 11. Select ButtonChoice. 12. In sub-screen Attribute of Element: ButtonChoice, enter the following data: Field Name Entry Value Element-ID <Automatically filled in by system> Sequence Index <Automatically filled in by system> Text Board Approval Status Tooltip Board Approval Status Enabled x Visibility Is Visible Alignment Left 13. Scroll down to maintain the items and event parameters. Add the following items by choosing Add Item (If displayed, remove the default entry after having created the following items): Text FPM Event ID Action Type To be approved by board I_ZUS_TO_BE_APPROVED Standard Approved by board I_ZUS_APPROVED Standard Rejected by board I_ZUS_REJECTED Standard 14. Select entry To be approved by board and make the following settings in table Enter Event Parameters (note that additional lines can be added by choosing Add Parameter): Parameter Name Parameter Value STATUS_TO 02 FIELDNAME ZZUSERSTATUS The parameter value of the parameter fieldname must be identical to the name of the component as set up in the append structure ZZUSERSTATUS. 15. Select entry Approved by board and make the following settings in table Enter Event Parameters: Parameter Name Parameter Value STATUS_TO 03 FIELDNAME ZZUSERSTATUS 16. Select entry Rejected by board and make the following settings in table Enter Event Parameters: Parameter Name Parameter Value STATUS_TO 04 FIELDNAME ZZUSERSTATUS 17. Choose Save. © SAP SE Page 28 of 54 SAP Best Practices 18. 19. 20. 21. 22. 23. Tips&Tricks for Implementation of Quality Issue Management (QIM) In the following, we will describe how to add a field to the user interface for displaying the actual value of the user status. Access tab Overview Page Schema and open node Section: SECTION_1. Select entry with Config ID QIM_OVP_ISSUE_OVERVIEW_FORM and choose Configure UIBB. Open tab Preview. To add the new field below the effectiveness check status, select field EFFECTIVE_STATUS_DESCR and choose button Add Element. From the list, select entry ZZZZUSERSTATUS and choose OK. Change the Display Type of the field to Text View and enter a label text (e.g. Status of Board Approval) in field Label Text. Instead of a Text View, you could also select the display type Dropdown. Now the user status can be set by the button in the global toolbar and the dropdown field. 24. Choose Save. You can test the new application configuration by choosing Additional Functions → Display. © SAP SE Page 29 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 3.6 How to Implement Issue Type-Dependent Configurations This section explains how to setup context based adaptations (CBA) of the user interface. CBA can be used to modify the user interface according to the actual application context. For example, additional fields (which have been created in an append structure) should only be displayed for certain issue types. Prerequisites The append field ZZ_Area has been defined in an append structure of the business object /IAM/ISSUE. For a detailed description how to create an append field, please refer to section 4.6.3. 3.6.1 Adjust Configuration – Create a Context Based Adaption These adjustments of the user interface only can be carried out in DE, since the original language of this UI is DE. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  ABAP Workbench  Overview  Object Navigator Transaction Code SE80 2. On the Object Navigator screen, open package QAM_UI and drill down to the web dynpro application configuration you want to modify (e.g. QAM_UI  Web Dynpro  FPM Applications  QIM_OVP_ISSUE  FPM Application Configurations  QIM_OVP_ISSUE) and double-click this application configuration. 3. Select the application and choose Display Configuration. 4. Click configuration name QIM_OVP_ISSUE_CC. 5. On tab Overview Page Schema, select configuration ID QIM_OVP_ISSUE_OVERVIEW_FORM (first entry) and choose Configure UIBB to open the UIBB of this entry. 6. Choose Edit to switch from display to edit mode. 7. Select the element you want to modify and choose Adaptations & Comparisons  Adaptations to display the Adaptations table. 8. Choose Add and fill in the desired filter settings. To display the field ZZ_Area only for issue type YCC make the following entries: Field Name Entry Non-specific Deselect toolbox left to the field Issue Type Issue Type YCC 9. Choose OK. 10. Choose Local Object. 11. To add an element to the screen, select an empty screen area and choose Element  Add Element. © SAP SE Page 30 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) You do not need to add a new element in any case, you can also adjust already existing elements. To do so, select the element you want to adjust, choose Copy, make your ajustment and replace the original element by your adjusted one. 12. On the Add Fields screen select the required element (e.g. ZZ_Area) from the displayed list and choose OK. 13. Drag&drop the element to the desired position. 14. Choose Save. If fields are merged to a group, the display properties of the entire group can be influenced in a similar way. Just select the group element in the user interface preview instead of the individual field. If the same user interface should be used for several adaptations (combinations of different selection criteria), the corresponding user interface must be built for each adaptation separately. 4 Issue Processing 4.1 How to Activate the QIM Workflow Use In this Customizing activity, you make the settings for the workflows delivered with QIM. You activate the triggering events and assign possible agents. Procedure Requirements:  You have executed the automatic Customizing for SAP Business Workflow under Maintain Standard Settings.  You have completed the Customizing for issue processing in QIM.  A user name or an e-mail address is stored for the workflow recipients in the business partner master data record. Various workflow templates and standard tasks are delivered for the component CAIAM-QIM. With these, the system can inform the activity driver when an activity was set in process and the issue driver when all activities for an issue were completed, so that the issue driver can check the completion of the issue. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Environment  Activate Workflow Transaction Code SPRO Activities © SAP SE Page 31 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) If you want to use the delivered workflows, when setting up the Customizing for SAP Business Workflow perform the task-specific Customizing. To do this, navigate to the component CA-IAMQIM and choose Assign Agents and Activate event linking. Assign agents: To use the delivered tasks, you do not need to assign specific agents. The actual agent is determined via the responsible partner role assigned to an Issue Type or Activity Type. You therefore define the following tasks as general tasks:  TS56907924 Check Issue Completion  TS56907929 Activity in Process The other tasks are background tasks. Activate event linking: Activate event linkage for the following workflow templates and classes:  WS56900002: CL_QAM_ACTIVITY_WF_CONNECT-COMPLETED  WS56900003: CL_QAM_ACTIVITY_WF_CONNECT-INPROCESS You can develop your own workflow templates using the standard tasks delivered with QIM. To do this, copy the delivered workflow templates in the Workflow Builder transaction SWDD and adapt your copies. More tools for developing workflows are available in the SAP Easy Access menu under Tools  Business Workflow  Development. 4.2 How to implement a Workflow for Notification of New Issues Use With the workflow for notification of new issues it is possible to inform the issue driver when an issue is reported that he or she needs to process. New workflow objects are delivered for this, for example:  Workflow template 56900008  Standard task 56907941 Prerequisites Requirements:   You have executed the automatic customizing for SAP Business Workflow under SAP NetWeaver  Application Server Business Management SAP Business Workflow  Maintain Standard Settings. You have performed the task-specific customizing for SAP Business Workflow under SAP NetWeaver  Application Server Business Management SAP Business Workflow  Perform task-specific Customizing.  You have completed Customizing for issue processing in QIM.  A user name or an e-mail address is stored for the workflow recipients in the business partner master data record. © SAP SE Page 32 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Various workflow templates and standard tasks are delivered for the component CA-IAMQIM. With these, the system can, for example, inform the activity driver when an activity was set in process and the issue driver when all activities for an issue were completed, so that the issue driver can check the completion of the issue. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM Menu Tools  Business Workflow  Development  Definition tools Workflow Builder Workflow Builder Transaction Code 2. SWDD To develop your own workflow templates using the standard tasks delivered with QIM, copy the delivered workflow templates. 3. To use the delivered tasks, you do not need to assign specific agents. The actual agent is determined via the responsible partner role of an Issue Type. You therefore define the following tasks as general tasks: o TS56907941 Process Issue o TS56907924 Check Issue Completion o TS56907929 Activity in Process The other tasks are background tasks. 4. Activate event linkage for the following workflow templates and classes: o WS56900008: CL_QAM_ISSUE_WF_CONNECT-CREATED o WS56900002: CL_QAM_ACTIVITY_WF_CONNECT-COMPLETED o WS56900003: CL_QAM_ACTIVITY_WF_CONNECT-INPROCESS 5. Choose Save. Although if no user is assigned to the business partner the workflow function can send an email to a business partner. You only need to assign an email address to the business partner. For sending emails the standard functionality of the workflow implementation is used. Due to technical restrictions of the QIM implementation the link (URL) to the applicable issue or activity that is delivered in the workflow email is cut off and therefore, cannot be accessed directly. The user needs to cut and paste the link to the Browser. To solve this issue note 2021811 for SP05 is available. © SAP SE Page 33 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 4.3 How to implement a Problem-Solving Process Using 8D Methodology Use You can conduct a problem analysis in SAP QIM according to the 8D methodology by creating and processing a QIM issue with the issue type 8D Problem Analysis. To ensure that the eight disciplines in 8D are covered, an 8D problem analysis is divided into steps. The user interface for 8D problem analysis differs from the user interface for the processing of other QIM issues. There is a separate screen area for each discipline. You can map problem-solving processes using 8D methodology in SAP QIM. The functions allow you to define the content for other problem-solving methodologies yourself. The functions include the following:    Customizing activities to divide a QIM issue into steps (or phases). As part of the scope of content for 8D, eight steps are delivered for the eight disciplines. The option of defining a follow-up issue for a QIM issue. Within the scope of the content delivered for 8D, it is possible to create an 8D problem analysis from a defect (for example, for a customer complaint). The option of assigning a specific Web Dynpro application configuration to an issue type. Within the scope of the content for 8D, a new issue type for 8D problem analyses (Q8D) and the application configuration QIM_OVP_8DISS are delivered. This application configuration depicts the 8D steps on the interface and also permits the following: o You can create immediate containment actions in step D3 using a quick entry function. o You can copy activities from step D5 to step D6. You can influence the copy process using a new Business Add-In (BAdI). o You can enter the percentage contribution of different causes for a defect. o You can assign the validation status Effectiveness Check Outstanding, enter the effectiveness of an activity in percent, and store a free text for the verification of the result.  The option of selecting according to steps in the worklist for activities.  A special print form (I8D) for printing or e-mailing an 8D report, to which the new PDFbased form QAM_ISSUE_8D is assigned in Customizing.  The option of combining several 8D reports (one 8D report for each defect for which the problem analysis is relevant) in one PDF document for printing or e-mailing. After implementation you have different options to create an 8D problem analysis:  You can create it directly by choosing the issue type for an 8D problem analysis under Create  Quality Issue (Advanced) . © SAP SE Page 34 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM)  You can trigger a problem analysis for a defect that, for example, belongs to a QIM issue with the issue type Customer Complaint. Here, you create a follow-up issue, for example, with the issue type 8D Problem Analysis. In this case, some fields are automatically copied from the customer complaint or the defect to the 8D problem analysis.  You can also link a directly created 8D problem analysis with an existing defect. You can use the method framework delivered with 8D (for example, the option to divide an issue into steps) to implement other problem-solving methodologies. Prerequisites  Adapt your PFCG roles as described in SAP Note 1994956. 4.3.1 Activate BCSets for 8D Use Procedure 1. To use the customizing content delivered for the problem-solving process using the 8D methodology access in SAP GUI the transaction using one of the following navigation options: 2. 3. 4. 5. 6. SAP QIM IMG Cross-Application Components  Quality Issue Management  Issue Processing  Problem-Solving Methodologies  Activate BC Sets for 8D Transaction Code n/a Activating a BC Set means that all data from the BC Set is transferred to the corresponding original tables. Note that existing entries for an object in the original tables are overwritten when this is done. You can only activate a BC Set if there is no production client in the system. In the following, we will describe how to add a field to the user interface for displaying the actual value of the user status. In the Business Configuration Sets: Display screen choose New BC Set Selection Select by Attributes. In the New BC Set Selection screen enter QAM_8D_DELIVERY_CUSTOMIZING in the Business Configuration Set field and choose Execute. Display the contents of the subordinate BC Set. To activate the BC Set, choose Goto -> Activation Transaction. Choose Activate BC Set (F7). For more information, see the documentation for the Business Configuration Sets (BC-CUS) component, which can be found under Help -> Application Help. 4.3.2 Define Issue Types Use Procedure © SAP SE Page 35 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 1. To use the delivered issue type for the problem-solving process using 8D the methodology access in SAP GUI the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Issue Processing Define Issue Types Transaction Code n/a 2. In the Change View Issue Type”: Overview check whether the settings of issue type Q8D fit to your needs. 3. If you need to change settings select the issue type Q8D and choose Copy As... Ensure that the object type QID is maintained in the folder Reference Object for the issue type. 4. Change the settings as needed and save your settings. If you want to use the delivered Customizing for a Defect with Problem Analysis (issue type QDP), you must exchange the usual issue type for Defect (QDF) when defining hierarchies of issue types (in Customizing for QIM under Issue Processing  Define Issue Types  Subitems ). This allows you, for example, to create an 8D problem analysis (issue type Q8D) as a follow-up issue from the issue type for customer complaints (QI1) at defect level (issue type QDP). For each issue type used within the 8D-methology you can define the used Web dynpro application configuration (field Configuration ID). Note: the configuration ID must belong to the Web dynpro application QIM_OVP_ISSUE. 4.3.3 Define Steps for Problem-Solving Methodologies Use Procedure 1. To define steps that subdivide the processing of an issue or problem into phases or stages to implement problem-solving methodologies like 8D in SAP QIM access in SAP GUI the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Problem-Solving Methodologies  Define Steps Transaction Code n/a 2. Check if the default settings delivered fit to your needs. © SAP SE Page 36 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 3. Each step corresponds to an 8D discipline. To enable the eight disciplines or steps to be displayed on the user interface, a dedicated Web Dynpro application configuration is delivered for the 8D issue type (QIM_OVP_8DISS). This application configuration is assigned to the issue type Q8D in Customizing for issue types. You may add new steps or change the step description. You should not delete steps, because the delivered steps are used in the the delivered Web Dynpro application configuration for 8D methology. 4. Choose Save. 4.3.4 Define Settings for Steps for Problem-Solving Methodologies Use Procedure 1. To make the settings for the individual steps access in SAP GUI the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Problem-Solving Methodologies  Define Settings for Steps Transaction Code n/a 2. Assign timepoint codes for the start date, end date of a step and requested end date, or enter an activity type or template for containment actions. The activity type or template is only relevant, however, if the option for the quick creation of an activity is implemented in the Web Dynpro application configuration, for example, by means of a + pushbutton. If you enter an activity type and an activity template, the system uses only the activity template; the entry for the activity type is ignored. No check is made to establish whether the activity type and activity template are compatible. Before you can assign a timepoint you must create the applicable timepoint codes and assign the created timepoint to the business object /IAM/ISSUE. (SAP QIM IMG: CrossApplication Components  Quality Issue Management  Basic Settings  Define Timepoints) Ensure, that you have defined the activity types or templates that you want to assign here. 4.3.5 BAdI: Influence Copying of Activities Use This BAdI is used to copy activities from step D5 to D6 to simplify the implementation of the activities in step D6 that were already defined in step D5. An active implementation of this BAdI is already delivered by SAP and activated for 8D-methology. Procedure © SAP SE Page 37 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 1. To influence the copy process for activities for the problem-solving process using the 8D methodology access in SAP GUI the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Issue Processing Business Add-Ins (BAdIs)  BAdI: Influence Copying of Activities Transaction Code n/a 2. Adapt the BAdI according to the information provided in the performance assistant of the customizing activity, if you need to adapt the copying process to your special needs. You need to use filter type 01 for your implementation because this filter type is used within the Web application configuration for 8D. If you want to create an own use case you need to use an own filter type within your implementation. To create an own filter type go to transaction SE11 (Tools  ABAP Workbench Development ABAP Dictionary), enter domain /IAM/ACT_COPY_TYPE and choose Change. Choose tab Value Range to maintain your own fixed value append. 3. Choose Activate. 4. Choose Save. 4.3.6 Adapt Print Form Use Procedure 1. To adapt the print form for the problem-solving process using the 8D methodology access in SAP GUI the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Issue Processing Define Print Forms Transaction Code n/a 2. In the Change View “Print forms”: Overview specify by selecting or deselecting the indicator defect Selection to define, if individual defects of an issue can be selected in the dialog box for printing or e-mailing issues A user wants to print an 8D report with three reference defects assigned. If the indicator is not set in Customizing, the system will include all defects assigned to the 8D problem analysis. This means, one PDF document comprising three 8D reports is printed. If the indicator is set, the user can select one of the defects for which just one 8D report is printed. 4.3.7 How to generate a 8D Report Use To print the result or interim versions of the 8D problem analysis or send them by e-mail, a special PDF-based print form is available for 8D reports. You can use the 8D print form when printing or © SAP SE Page 38 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) mailing from the 8D problem analysis or from the underlying customer complaint. If several defects are assigned to the 8D problem analysis or the customer complaint, you can choose which defects are to be included in the 8D report (if you made the respective settings in Customizing). If you select several defects, an 8D report is created for each defect in which some data is taken from the defect and some data is taken from the 8D problem analysis (see below in the Features section for more information). The 8D reports for all selected defects are output consecutively in a PDF document. Prerequisites You have made the settings for the print form in Customizing for QIM under Issue Processing  Define Print Forms. For the issue type 8D Problem Analysis (Q8D), the print form I8D is delivered in the 8D BC Set. The PDF-based form QAM_ISSUE_8D is assigned to this print form. For this print form, for example, you can specify whether you can select the defects in the print dialog that are to be included in the 8D report. If you want the printed forms to appear under Documentation in the problem analysis, you must assign an activity template and a document type. Features You can create an 8D report directly from the 8D problem analysis or from the underlying customer complaint. In both cases, you must select the respective print form for 8D reports in the dialog box for printing or e-mailing. If you create the 8D report from the customer complaint, the data is taken partly from the original customer complaint, partly from the defect, and partly from the 8D problem analysis. If you create the 8D report from the 8D problem analysis and referenced defects are assigned to it, some data is also taken from the defect. Which data comes from where is shown in the following table: Field/Screen Area Origin in 8D Report Without Reference to Defects Origin in 8D Report With Reference to Defects – If Different Title Block Bar code Logo Issue ID of 8D problem analysis as bar code type EAN128 Object Navigator (transaction SE80)  MIME Repository  PUBLIC  QIM  LOGO_8D.bmp 8D Report Fixed title Type Text for issue type of 8D problem analysis External Reference No. © SAP SE Page 39 of 54 The first External Reference Object (object type GOJ) in The first External Reference Object (object type GOJ) in SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) the reference object list of the 8D problem analysis the reference object list of the parent QIM issue (for example, customer complaint) Shows the progress status of each D step as a color code:   White: Requested end date is not defined Gray: Requested end date is defined, end date is open  Yellow: Requested end date lies one day before today's date  Green: Requested end date lies before or is identical to the end date  Red: Requested end date is later than the end date/current date Progress Start Date Start date from the issue overview and the D8 step of the 8D problem analysis (date fields of the steps are identical) Report Date Current printing date Header Data 8D Title Issue description (short text) of 8D problem analysis Issue description (short text) of 8D problem analysis of parent QIM issue (for example, customer complaint) Material Material No. Customer Customer No. Contact (at customer, incl. contact data) © SAP SE Page 40 of 54 Main reference object Material of 8D problem analysis Reference object Customer (object type CUS) of 8D problem analysis Reference object Customer (object type CUS) of parent QIM issue (for example, customer complaint) First business partner with partner role CONTACT of 8D problem analysis First business partner with partner role CONTACT of parent QIM issue (for example, customer complaint) SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Vendor Vendor No. Reference object Vendor (object type VEN) of 8D problem analysis Reference object Vendor (object type VEN) of parent QIM issue D1 – Team Role First Name Last Name E-Mail Business partner from 8D problem analysis Telephone Department Department entered in SAP user of business partner D2 – Problem Description Issue description Defect Code Defect Location Number of Parts Affected Issue description (short text) and detailed description (long text) of 8D problem analysis Issue description (short text) and detailed description (long text) of referenced defect Code group and code of respective fields of 8D problem analysis Code group and code of respective fields of assigned referenced defect Defect quantity from No. of Occurrences field in 8D problem analysis Defect quantity from No. of Occurrences field in referenced defect Data on all activities from the D3 step of the 8D problem analysis Data on all activities from the D3 step of the 8D problem analysis and on all activities of the referenced defect D3 – Containment Action(s) Containment actions D4 – Root Cause(s) Root causes of defects Data on all causes from the 8D problem analysis D5 – Chosen Permanent Corrective Action(s) Per cause: Chosen permanent corrective actions Data on all activities from the D5 step of the 8D problem analysis D6 – Implemented Permanent Corrective Action(s) Per cause: Implemented © SAP SE Page 41 of 54 Data on all activities from the SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) permanent corrective actions D6 step of the 8D problem analysis D7 – Action(s) to Prevent Recurrence Actions to prevent recurrence Data on all activities from the D7 step of the 8D problem analysis D8 – Congratulate Your Team Result Issue assessment from 8D problem analysis Close Date Completion date from the issue overview and the D8 step of the 8D problem analysis (date fields of the steps are identical) Procedure The following process describes how to create an 8D problem analysis when it is created for a defect: 1. When processing a defect, for example, a customer complaint, you can trigger or assign an 8D problem analysis. 2. To first identify any similar QIM issues or defects that may have the same material as a reference object or the same code as the defect, you can search for related issues or defects in the side panel. To do this, select the defect and choose Additional Information. For more information, see Reports for Related Issues or Defects. If you find a suitable 8D problem analysis, you can assign the current defect to this existing problem analysis under Referenced Defects if required. 3. To create a new 8D problem analysis, choose Trigger Problem Analysis. For creating the problem analysis, all issues types are available that are entered in Customizing for the issue type of the defect under Follow-Up Issues. 4. When you create an 8D problem analysis as a follow-up issue, some data is filled automatically; you can add other data manually. More information about the individual screen areas: o o In the Issue Overview, the system automatically copies the dates for the requested start and requested end from the original issue, for example, the customer complaint. The main reference object is the material of the defect from the customer complaint. The defect is also entered automatically as the referenced defect. If the problem analysis is relevant for other similar defects, you can also assign these. In the step D1 – Team, you enter the members of the problem-solving team by specifying the partner roles and business partners. © SAP SE Page 42 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) o In the step D2 – Problem Description, the system copies the data (for the codes and description, for example) from the defect. You can overwrite this copied data. o In the step D3 - Containments Action(s), you can create immediate containment actions for the 8D problem analysis using a quick entry function. The system uses the activity type or activity template that you stored in Customizing for the respective step. The end date of this step is set automatically when all activities are completed. o If you have done a root cause analysis of the defect, you can enter the root causes in the step D4 – Root Causes. Technically, the system creates causes with the issue type Cause for Problem Analysis (QCP) (subitem of the 8D issue type). For each cause, you can specify under % Contribution which portion of the defect was contributed by each cause. You can save the documentation of your root cause analysis as an attachment to the 8D problem analysis in the QIM system. o o For each cause, you can specify activities for remedying the cause of a defect in the step D5 – Chosen Permanent Corrective Action(s). When planning is completed, you can use the copy pushbutton with the quick info Implement Activity to copy the activity to the D6 step. Technically, this creates a new activity for which some of the data is copied. The D5 activity is then set to Completed by the system. The end date of this step is set automatically when all activities are completed. The step D6 – Implemented Permanent Corrective Action(s) includes the activities that you introduced in the D5 step. With the exception of the status, date fields, and the attachments, the system copies all data from the corresponding D5 activity. You can add other activities manually. The end date of this step is set automatically when all activities are completed. o In the step D7 – Action(s) to Prevent Recurrence, you can define activities: in this case, however, at the level of the 8D problem analysis. Here, the activities that you entered in Customizing for the 8D issue type under Automatic and Proposed Activity Templates are listed automatically. The end date of this step is set automatically when all activities are completed. o To wrap up an 8D problem analysis, you can enter an assessment of the resolution in the step D8 – Congratulate Your Team. Here, you can also set the end date of the 8D problem analysis. o Under Documentation, the PDF forms are stored that you created during the course of the process by printing or e-mailing an interim status of the problem analysis or the final 8D report (see also 8D Report). o Under Attachments, you can assign other documents to the 8D problem analysis, such as documents relating to the defect analysis. 5. For all activities in the 8D process, you can enter the effectiveness in percent and store a free text for the verification of the result. If you want to do this at a later date, you can assign the validation status Effectiveness Check Outstanding for the 8D problem analysis. An activity with this status cannot be archived. © SAP SE Page 43 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 6. If you want to process specific activities within an 8D problem analysis, it is possible to select by steps in the worklist for activities. 7. In the 8D problem analysis or customer complaint, choose the icon for printing or sending e-mails. 8. Select the form for 8D reports (I8D). 9. Select the images that you want to be included at the end of the 8D report. The images from the underlying customer complaint are not included in the 8D report and are thus not available for selection. 10. If the relevant indicator is set in Customizing for the print form, you can select the defects for which the PDF document is to be created.  When printing or mailing from the 8D problem analysis, the referenced defects from the 8D problem analysis are available for selection.  When printing or mailing from a customer complaint, the defects from the customer complaint are available for selection. 11. When mailing, you can choose which of the attachments that were added in the various 8D steps should be attached to the e-mail. 12. The created PDF document is then displayed in the print preview. 13. Only if you actually print or send the PDF document is an activity with the PDF document added to the 8D problem analysis as an attachment under Documentation. Result You generated 8D problem analysis and printed out the results or sent them by e-mail using a special PDF form for 8D reports. 4.4 How to enhance Definition and Assignment of Reference Objects Use You want to assign an object as reference to an issue or activity for which the corresponding object type does not exist. If a suitable object type exists, it is sufficient to create a new implementation of the corresponding Object-Category-BAdI to connect to another Application Programming Interface (API). © SAP SE Page 44 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) You have the following enhanced options when defining reference objects in Customizing and when assigning reference objects to issues or activities:  You can define several reference objects without a fixed technical reference to an SAP system by copying the delivered object type External reference object (GOJ) and adapting the copy accordingly. For more information about the procedure, see SAP Note 1820834. There are several different approaches to create a new object type, differing in functionality and effort: o Use object category 'External Reference Object' (GOJ_NW). o Use object category 'External Reference Object' (GOJ_NW) with enhancements. o Implement a new object category for a new or existing object type. Special case: Your search help is using the special search exit implementation F4UT_DOMAHLP_EXECUTE for domain values.   The new object type Storage location (STL) is delivered as an example of an object type copied in this way. You can define and assign a search help for the object type External reference object (GOJ) and for the copies of the object type GOJ you create yourself. For more information about the procedure, see SAP Note 1820834 (section B: Use object category 'External Reference Object' (GOJ_NW) with enhancements.  You can adapt the search dialog box for existing reference objects, for example, by adding additional search helps or hiding existing search helps. For more information about the procedure, see also SAP Note 1909219.  In the dialog to assign reference objects it is possible to select several objects at once to assign them to the current issue or activity if the receiving UI element supports this (e.g. if it is a list or a tree). Procedure for Reusing the object type GOJ 1. 2. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Cross-Application Components  Quality Issue Management  Basic Settings  Generic Settings for Reference Objects  Define Object Types Transaction Code n/a Copy the existing object type GOJ and adapt the copy as described in SAP Note 1820834. A new column for the assignment of a search help is only ready for input for the object type GOJ and its copies. The delivered object type External Reference Object (GOJ) has the distinctive feature that it does not correspond to any specific object in another system, but is intended for flexible use. Its underlying BOL component IAMGOJ can be used for different flexible reference objects. © SAP SE Page 45 of 54 SAP Best Practices 3. Tips&Tricks for Implementation of Quality Issue Management (QIM) Choose Save. 4.5 How to implement Side Panel for Applications for Processing Issues and Activities Use The side panel for applications for issue and activity processing allows the display of various Web Dynpro CHIPs that relate to the object being displayed or processed in the main application. You can open the side panel when creating issues or activities using the advanced create function, or when processing or displaying issues and activities, using the link Additional Information. When processing issues, the following CHIPs are available:   Notes: In the Web Dynpro CHIP BSSP_NOTES, you can store public or private notes about the object currently being displayed or processed. Related Issues or Subissues: In the side panel graphics appear showing the issues and the defects that are related to the current issue or a selected subitem (for example, a defect or a cause). The context data can be a common reference object or the code. The graphics are updated depending on the context. If no subitem is selected, the related issues or defects displayed in the graphic are related to the issue being processed. You can use this feature, for example, to identify an existing 8D problem analysis that fits for a defect, which you can then assign to the defect. You can add further CHIPs yourself, for example, to enable collaboration using SAP Jam (Web Dynpro CHIP BSSP_SW_FEEDS). The prerequisite for this is that you have activated the business function Enable Social Media ABAP Integration 3 (BC_SRV_STW_03), which is available as of SAP NetWeaver AS ABAP 7.31 SP06. You may add additional parameters which refers to object references to the delivered CHIP for related issues or subissues. To do so follow the following procedure. Prerequisites A suitable panel must be available. Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM EASY Access Menu Tools  ABAP Workbench  Development  ABAP Dictionary Transaction Code SE11 2. In the ABAP Dictionary: Initial Screen set the radio button Data type, andenter the structure name /IAM/S_I_Q_SELECT_FOR_CONTEXT 3. In the ABAP Dictionary: Initial Screen choose Display. 4. In the Dictionary: Display Structure choose Append Structure… © SAP SE Page 46 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) 5. Enter an Append Name in the customer namespace and choose Continue. 6. Enter a short description for your Append Structure. 7. Enter the following data for each object type, which corresponding object references should be used as context: Parameter Name Parameter Value Component <enter a descriptive name for your component(s)> Typing Method Types Component Type <choose a data element(s) from database table /IAM/I_TYPE) To find the data elements from database table /IAM/I_TYPE for the component type parameter choose SAP QIM IMG  Cross Application Components  Quality Issue Management  Basic setting  Generic Settings for Reference Objects  Define object types. In the field Key Element you may find the data elements for your append structure. 8. Choose Save. 9. Choose Activate. Result The additional parameters are used in the side panel for related issues and subissues. 4.6 How to implement Archiving of Activities and Issues Use Using archiving, you can export data that you no longer require in the system, but need to retain for documentation purposes, for example, to an archive file and thus free up space in the database. After archiving, the data can be displayed but no longer changed. The following archiving objects are delivered:  /IAM/ACT for archiving QIM quality activities with the corresponding data  /IAM/ISSUE for archiving QIM quality issues with the corresponding data The archiving objects are based on the Archive Development Kit (ADK) and use functions of the BOPF archiving adapter. Prerequisites   To be able to use the functions of Information Lifecycle Management (ILM), you must have activated the business function ILM. You have made the required settings in Customizing for data archiving: SAP NetWeaver  Application Server  System Administration  Data Archiving. © SAP SE Page 47 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Go to transaction SARJ. Choose Archive Infostructure /IAM/ACT and /IAM/ISSUE and choose Activate.   To use the archiving functions, users must have the authorizations provided by the authorization object S_ARCHIVE. You have authorization for the activity 12 Archive in the authorization object IAM/A_STAT Authorization Object for Lifecycle Status (Activity), field /IAM/A_ACT Authorization to Perform Activity-Related Activities.  You have authorization for the activity 14 Archive in the authorization object IAM/I_STAT Authorization Object for Lifecycle Status (Issue), field /IAM/I_ACT Authorization to Perform Issue-Related Activities.  Familiarize yourself with the functions of the Archive Development Kit and ILM Retention Management: o Data Archiving with Archive Development Kit (ADK) o SAP NetWeaver Information Lifecycle Management First archive the activities for an issue and its subactivities (/IAM/ACT), then archive the issue and the corresponding subissues (/IAM/ISSUE). 4.6.1 Archiving Activities with /IAM/ACT Use With the archiving object /IAM/ACT, you can archive activities and their corresponding information, such as reference objects, descriptions, partners, and attachments stored in the system. Which information is archived in detail is listed in archive administration (transaction SARA) under Database Tables and in the application for archiving object definition (transaction AOBJ) under Structure Definition. The following programs are available for this archiving object:  Preprocessing program /IAM/ACT_ARCH_PRE The preprocessing program uses the activity status and the chosen selection criteria (for example, residence time) to check for which activities archiving is possible and then assigns them the archiving status Marked for Archiving. Activities with the status Marked for Archiving can then only be displayed in the application but no longer changed Since, for reasons of consistency, only complete activity hierarchies for an issue or subissue (defects, effects, causes) can be archived, the preprocessing program checks whether all © SAP SE Page 48 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) activities that belong to one activity branch beneath an issue, defect, cause, or effect are archivable. Features Basic and extended activities and questions can only be archived if they have one of the following lifecycle statuses:   Completed (09) Canceled (10)  Flagged for Deletion (64) Activities of the category Information can be archived regardless of their lifecycle status if the parent activity has the archiving status Marked for Archiving. If an activity has further subactivities, these must also have the archiving status Marked for Archiving.  Write program /IAM/ACT_ARCH_WRI The write program creates archive files and stores the activities with the status Marked for Archiving in the file. The write program also sets the Activities Archived indicator in the parent issue or subissue. When QIM data is archived, transient texts, such as the descriptions of codes stored in Customizing, are also archived in one specific language; if you perform the archiving in English, these texts will be shown in English when you display the archived data at a later stage, even if you are logged on to the system in another language.  Delete program /IAM/ACT_ARCH_DEL The delete program reads the data from the archive file. If the read was successful, it sets the status to Archived and deletes the data from the database. If you want to extend the archivability checks, archive additional data, or register other archiving classes, you can use the options in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). To be able to use the archiving object /IAM/ACT in Information Lifecycle Management (ILM), the ILM object IAM_ACTIVITY is delivered. Settings in ILM object Customizing (transaction IRM_CUST) for IAM_ACTIVITY: © SAP SE Page 49 of 54 SAP Best Practices  Available Time References: o Created On (CREATION_DATE) o  Tips&Tricks for Implementation of Quality Issue Management (QIM) Last Changed On (LAST_CHANGE_DATE) Available Condition Fields: o IAM Application (APPLICATION) o IAM Authorization Group (AUTH_GROUP)  Available Policy Categories: Retention Rules (RTP)  Assigned BOR Object: /IAM/ACT Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Data Archiving  Administration  Administration Tools Transaction Code SARA 2. In the Archive Administration: Initial Screen enter the technical name of the archiving object select the Archiving Object IAM/ACT and press the pushbutton Preproc. 3. Enter a name for the variant and choose Maintain. 4. In the Edit Variants: Variant… specify the application QIM to archive QIM data. Only then the other application-specific selection criteria are visible. You can store the application QIM in your user profile as the value for the parameter /IAM/APPLICATION, then the value is entered automatically in the selection criteria. 5. Enter the required data for the selection criteria and choose variant Attributes. To determine the activities to be archived, you can, for example, specify the activity ID, activity category, activity type, and lifecycle status. You can enter the residence time for activities in the QIM system (in days, relating to the date of the last change). For example, if the residence time is 365 days, only those activities are selected that were last changed at least a year ago. You can store a default value for the residence time in application-specific Customizing. Note: With the following lifecycle statuses, immediate archiving is possible: o o Canceled (10) Flagged for Deletion (64) © SAP SE Page 50 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) If you want to archive the respective activities immediately, you can define an additional variant that incorporates the relevant lifecycle statuses and a residence time of 0 days. You can specify in which form and with which level of detail the log is to be displayed. 6. Select the required variant attributes. 7. Choose Save. 8. Enter the start date and the spool parameters. You can execute the preprocessing program in test mode or production mode. Independent of this, you must always use a variant and schedule it. 9. Create a variant for the write program and schedule it. The delete program is executed automatically after the write program. You can change this setting in Customizing for the archiving object (SARA  Goto  Customizing Archiving Object-Specific Customizing Technical Settings). 10. Choose Save. 11. To execute the job immediately, choose Execute. You can execute the preprocessing program in test mode or production mode. Independent of this, you must always use a variant and schedule it. There are various selection criteria and options available for you to define a variant Result The selected data are archived. Archived data is deleted from the database but can still be displayed. 4.6.2 Archiving Issues with /IAM/ISSUE Use With the archiving object /IAM/ISSUE, you can archive issues and their corresponding information, such as reference objects, descriptions, partners, and attachments stored in the system. Which information is archived in detail is listed in archive administration (transaction SARA) under Database Tables and in the application for archiving object definition (transaction AOBJ) under Structure Definition. The following programs are available for this archiving object:  Preprocessing program /IAM/ISSUE_ARCH_PRE The preprocessing program checks whether archiving can run for the selected issues based on the lifecycle status. It uses the issue status and the chosen selection criteria (for example, residence time) to check for which issues archiving is possible and then assigns them the archiving status Marked for Archiving. Issues with the status Marked for Archiving can then only be displayed in the application but no longer changed. © SAP SE Page 51 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) For reasons of consistency, only complete issue hierarchy branches can be archived when archiving issues. That means, all subissues (defects, effects, causes) belonging to an issue must be archived as well. The assigned activities must already have been archived or be marked for archiving. Features Issues can only be archived if they have one of the following lifecycle statuses:   Completed (09) Canceled (10)  Flagged for Deletion (64) The corresponding defects, effects, and causes are archived as well, regardless of their lifecycle status. The activities belonging to the issue or subissue must have one of the following archiving statuses:    Marked for Archiving (02) Archived (03) Write program /IAM/ISSUE_ARCH_WRI The write program creates archive files and stores the issues with the status Marked for Archiving in the file. When QIM data is archived, transient texts, such as the descriptions of codes stored in Customizing, are also archived in one specific language; if you perform the archiving in English, these texts will be shown in English when you display the archived data at a later stage, even if you are logged on to the system in another language.  Delete program /IAM/ISSUE_ARCH_DEL The delete program reads the data from the archive file. If the read was successful, it sets the status to Archived and deletes the data from the database. If you want to extend the archivability checks, archive additional data, or register other archiving classes, you can use the options in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). To be able to use the archiving object /IAM/ISSUE in Information Lifecycle Management (ILM), the ILM object IAM_ISSUE is delivered. © SAP SE Page 52 of 54 SAP Best Practices Tips&Tricks for Implementation of Quality Issue Management (QIM) Settings in ILM object Customizing (transaction IRM_CUST) for IAM_ISSUE:  Available Time References: o Created On (CREATION_DATE) o  Last Changed On (LAST_CHANGE_DATE) Available Condition Fields: o IAM Application (APPLICATION) o IAM Authorization Group (AUTH_GROUP)  Available Policy Categories: Retention Rules (RTP)  Assigned BOR Object: /IAM/ISSUE Procedure 1. In SAP GUI, access the transaction using one of the following navigation options: SAP QIM IMG Data Archiving  Administration  Administration Tools Transaction Code SARA 2. In the Archive Administartion: Initial Screen enter the technical name of the archiving object select the Archiving Object IAM/ISSUE and press the pushbutton. Preproc 3. Enter a name for the variant and choose Maintain. 4. In the Edit Variants: Variant… specify the application QIM to archive QIM data. Only then the other application-specific selection criteria are visible. You can store the application QIM in your user profile as the value for the parameter /IAM/APPLICATION, then the value is entered automatically in the selection criteria. 5. Enter the required data for the selection criteria and choose variant Attributes. To determine the issue to be archived, you can, for example, specify the issue type and the lifecycle status. To ensure data consistency, for all issues selected their subissues (defects, effects, and causes) are automatically selected as well, regardless of their status. You can enter the residence time for issues in the QIM system (in days, relating to the date of the last change). For example, if the residence time is 365 days, only those issues (and their subissues) are selected that were last changed at least a year ago. You can store a default value for the residence time in application-specific Customizing. Note: With the following lifecycle statuses, immediate archiving is possible: © SAP SE Page 53 of 54 SAP Best Practices o o Tips&Tricks for Implementation of Quality Issue Management (QIM) Canceled (10) Flagged for Deletion (64) If you want to archive the respective issues immediately, you can define an additional variant that incorporates the relevant lifecycle statuses and a residence time of 0 days. You can specify in which form and with which level of detail the log is to be displayed. 6. Select the required variant attributes. 7. Choose Save. 8. Enter the start date and the spool parameters. You can execute the preprocessing program in test mode or production mode. Independent of this, you must always use a variant and schedule it. 9. Create a variant for the write program and schedule it. The delete program is executed automatically after the write program. You can change this setting in Customizing for the archiving object (SARA  Goto  Customizing Archiving Object-Specific Customizing Technical Settings). 10. Choose Save. 11. To execute the job immediately, choose Execute. You can execute the preprocessing program in test mode or production mode. Independent of this, you must always use a variant and schedule it. There are various selection criteria and options available for you to define a variant Result The archived data is deleted from the database but can still be displayed. 4.7 Further References You can find furher references regarding the QIM setting and for frequently asked questions. FAQ-QIM.pdf © SAP SE Page 54 of 54