SAP QIM

SAP Quality Issue Management (SAP QIM) PDF download from SAP Help Portal: http://help.sap.com/saphelp_qim100/helpdata/en/26/d50f49b6a54a37839e4326987edeb1/frameset.htm Created on March 21, 2015 The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal. Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. © 2015 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. The information contained herein may be changed without prior notice. 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 and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Table of content PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 1 of 106 Table of content 1 SAP Quality Issue Management (SAP QIM) 1.1 What's New in SAP QIM 1.0 1.1.1 Support Package 5 1.1.1.1 End of Purpose Check for Personal Data 1.1.1.2 Flexible Search Helps for Quick Access to Quality Issues 1.1.2 Support Package 4 (Feature Pack 2) 1.1.2.1 Flexible Selection Options in Worklist 1.1.2.2 BAdIs for Pushbuttons in Worklist 1.1.2.3 BAdI for Date Calculation in Activities 1.1.2.4 Search for Activity Data Using Enterprise Search 1.1.2.5 Basic Search in Issue Long Texts 1.1.2.6 Archiving of Activities and Issues 1.1.2.7 Customer-Specific Field Control 1.1.2.8 Enhanced Definition and Assignment of Reference Objects 1.1.2.9 Side Panel for Applications for Processing Issues and Activities 1.1.2.10 Workflow for Notification of New Issues 1.1.2.11 Problem-Solving Process Using 8D Methodology 1.1.2.12 Adaptation Options for the User Interface 1.1.2.13 QIM-Specific CHIP for Quick Access to Quality Issues 1.2 Use of SAP QIM 1.2.1 Connection of Systems in a Side-by-Side Scenario 1.3 Worklists for Quality Issues and Quality Activities 1.3.1 Selection Criteria 1.3.2 Layout 1.3.3 Definition of Queries 1.3.3.1 Selection According to Calculated Dates 1.3.3.2 Selection According to Variable User or Business Partner 1.3.4 Structure Mapping 1.3.5 Jumps 1.3.6 Additional Information 1.3.7 Status Change 1.3.8 Monitoring Control of Issues and Activities 1.4 Issue Processing 1.4.1 Overview: Creating Quality Issues 1.4.1.1 Create Quality Issue (Quick) 1.4.1.2 Create Quality Issue (Guided) 1.4.1.3 Create Quality Issue (Advanced) 1.4.1.4 Issue Status 1.4.1.4.1 Status Profile for Issues 1.4.2 Changing of Quality Issues 1.4.3 Subitems: Defect, Cause, Effect 1.4.4 Quality Activities 1.4.4.1 Activity Templates 1.4.4.1.1 Proposed Activity Templates 1.4.4.2 Determination of Activities Using BRFplus 1.4.4.3 Determination of Partner for Activities Using BRFplus 1.4.4.4 Transfer of User Data for Activity Driver/Completed By for Activ 1.4.4.5 Activity Status 1.4.4.5.1 Status Profile for Extended Activities 1.4.4.6 Definition of Follow-Up Actions 1.4.5 Settings Dependent on the Text Type 1.4.6 Codes and Code Groups 1.4.6.1 Determination of Codes and Code Groups Using BRFplus 1.4.7 Partners 1.4.7.1 Partner Roles 1.4.7.2 Partners in a QIM Issue 1.4.7.2.1 Transfer of User Data for Issue Submitter 1.4.7.3 Determination of Partner for Issues Using BRFplus 1.4.8 Reference Objects 1.4.8.1 Reference Objects for Issue Types PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 2 of 106 1.4.8.2 Reference Objects for Activity Templates 1.4.9 Printing of Issues or Activities 1.4.10 E-Mailing of Issues or Activities 1.4.11 Additional Information in Side Panel 1.4.12 Change Documents 1.4.13 Workflow Scenarios for Issue Processing 1.4.13.1 Technical Implementation 1.4.14 Issue Processing with Digital Signatures 1.4.15 Problem Analysis Using 8D Methodology 1.4.15.1 8D: Technical Implementation 1.4.15.2 8D Report 1.5 System Administration Work Center 1.5.1 Process Control 1.5.2 Configure Rules 1.5.3 Communication with External Systems 1.5.4 Audit Trail 1.5.5 Environment 1.5.6 System Settings for Reporting 1.6 Enterprise Search 1.7 Reports 1.7.1 Reports in Business Context Viewer (BCV) 1.7.1.1 Example: BCV Query via BAPI Search Connector 1.7.2 Reports Using Search and Operational Analytics 1.7.3 Reports for Related Issues or Defects 1.7.4 Reports in Other Systems 1.8 Technical System Integration 1.8.1 ID Mapping 1.8.2 Setting Up System Connections 1.9 User Interface Adaptation 1.9.1 Adaptation of the Role Menu 1.9.2 Adaptation of the QIM Work Centers 1.9.2.1 Launchpads in QIM 1.9.3 Adaptation of the Web Applications in QIM 1.9.3.1 Context-Based Adaptation of QIM Web Applications 1.9.3.2 Adaptation Using Field Control 1.9.4 Terminology Redefinition 1.9.5 User Status 1.9.6 Web Dynpro Personalization and Customizing 1.9.7 Web Dynpro Configuration 1.10 Roles in SAP Quality Issue Management 1.10.1 Coordinator 1.10.2 Issue Driver 1.10.3 Authorizations 1.10.4 Generation of Portal Roles 1.11 System Architecture 1.12 Sequence of Configuration Steps in SAP QIM 1.13 Search and Operational Analytics: Content for SAP QIM 1.13.1 Search and Analytics Models 1.13.1.1 Issue 1.13.1.2 Defect 1.13.1.3 Cause 1.13.1.4 Effect 1.13.1.5 Issue Attachment 1.13.1.6 Activity 1.13.1.7 Activity Attachment 1.13.1.8 ODP for Issue and Subissue 1.13.2 TransientProviders 1.13.2.1 QIM Issues 1.13.3 DataSources 1.13.3.1 QIM Issues 1.13.4 Content Objects in Software Component IAM 1.13.4.1 Content Objects for Customizing in IAM PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 3 of 106 1 Checks for /IAM/ISSUE 1.14.1.2 Creating Preprocessing Variants for /IAM/ACT 1.14 Archiving QIM Data 1.1.2 Creating Preprocessing Variants for /IAM/ISSUE 1.14. All rights reserved.4 Displaying Archived QIM Data PUBLIC © 2014 SAP SE or an SAP affiliate company.14.1 Archiving Activities with /IAM/ACT 1.14.14.2.3 Setting Up Application-Specific Customizing 1.1.14.2.1 Checks for /IAM/ACT 1.14.2 Archiving Issues with /IAM/ISSUE 1. Page 4 of 106 .14. 1 Support Package 5 1. All rights reserved. available on SAP Service Marketplace under PUBLIC © 2014 SAP SE or an SAP affiliate company.sap. After this. you will find information about new features in SAP QIM 1.1. Effects on Customizing For information about how you define the end of purpose for personal data in SAP QIM. see Customizing for QIM under for Personal Data .1. Personal data can also be customers and vendors in connected ERP systems that you have assigned as reference objects. Page 5 of 106 .0 In this structure. You will find the Release Notes for previous Support Packages as usual on SAP Service Marketplace under Solutions SAP Quality Issue Management and in the QIM system under Help Release Notes .0 SP05 Documentation Published August 2014 See SAP Note 2015336 for corrections that are made after the documentation has been delivered. see: SAP NetWeaver by Key Capability Processes and Tools for Enterprise Applications SAP NetWeaver Information Lifecycle Management 1.0 SP05 Required Business Functions Information Lifecycle Management (ILM) Effects on Existing Data This product feature allows you to control the deletion and blocking of the business partner master data used in SAP QIM by means of the component SAP Information Lifecycle Management (ILM). Personal data can be assigned partners in the QIM system that are stored in the system as SAP business partners. More Information For more information about cross-application components that are relevant for SAP QIM. Environment Define End of Purpose More Information Section Security Information Data Protection in the Administrator's Guide for SAP QIM. the blocked personal data can be destroyed so that it is irretrievable.1 What's New in SAP QIM 1. http://service.0 as of Support Package 4. Technical Details Technical Name of Product Feature QIM_105_EOP Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Available as of SAP QIM 1. Once the retention period has also expired.com/releasenotes SAP 1.1 SAP Quality Issue Management (SAP QIM) Product Information Product SAP QIM Release 1.1. only those users who have additional authorization can access this data. The personal data stored in the business partner master data can be blocked if the business activities for which the master data is required are completed and the residence time for this data has expired.1 End of Purpose Check for Personal Data You can specify the end of purpose for personal data in SAP QIM.0 SP05 Based On SAP enhancement package 3 for SAP NetWeaver 7. This means that the end of purpose check using SAP Information Lifecycle Management (ILM) also takes into account the personal data stored in SAP QIM. 2.1. this is also integrated in the quick access so you can run a free text search. Page 6 of 106 . effects.com/instguides SAP Business Suite Applications SAP Quality Issue Management 1. implement your own print or export function.2.2 Flexible Search Helps for Quick Access to Quality Issues In the QIM_QUICK_ACCESS CHIP for quick access to quality issues. you can define your own pushbuttons in the worklists for issues and activities and thus. If you use Enterprise Search in SAP QIM. for example. More Information QIM-Specific CHIP for Quick Access to Quality Issues 1.1. you can use flexible selection options by means of variables for the business partner or user or by having the system calculate dates. Technical Details Technical Name QIM_104_POWL_SELECTION Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1.1.0 SP05 Effects on System Administration To include a search help.1 Flexible Selection Options in Worklist When you define queries for worklists for issues and activities. All rights reserved.1.1.2 BAdIs for Pushbuttons in Worklist With two new Business Add-Ins (BAdIs).sap.2 Support Package 4 (Feature Pack 2) 1. Then choose Configuration Settings in the setup menu of the CHIP and assign the search help. Technical Details Technical Name QIM_104_BADI_POWL Product Feature Is New Country Dependency Valid for all countries PUBLIC © 2014 SAP SE or an SAP affiliate company.http://service. it is possible to include flexible search helps. defects. and causes. open the Quality Issues page in Customizing mode (see also Adaptation of the QIM Work Centers).0 SP04 More Information Selection According to Variable User or Business Partner Selection According to Calculated Dates 1. Technical Details Technical Name of Product Feature QIM_105_QUICKACCESS_SEARCH Product Feature Is Changed Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Available as of SAP QIM 1. 1. also known as Embedded Search. the long texts of the objects are now also included in the search. 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.2.1. defects. causes.3 BAdI for Date Calculation in Activities You can use this BAdI to calculate one or more timepoints for one or more activities. it is possible to make data for QIM issues and QIM activities available to the Enterprise Search component of SAP NetWeaver Application Server ABAP.2. Technical Details Technical Name QIM_104_BADI_ACTVTY Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1.5 Basic Search in Issue Long Texts When searching for QIM issues. This means that you can search across all structured data of the objects listed above in the system in which you are running SAP QIM. and effects using the basic search in Embedded Search.0 SP04 Effects on Customizing You set up the search for quality activities in Customizing for QIM under Search and Analytics Configure Search .0 SP04 Effects on Customizing You will find the BAdI in Customizing for QIM under information. Page 7 of 106 . see the documentation for the BAdI. An example implementation is delivered for this use case.2. For more 1.1. Issue Processing Business Add-Ins (BAdIs) BAdI: Date Calculation for Activities . Technical Details Technical Name QIM_104_ESH_ACT Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1.4 Search for Activity Data Using Enterprise Search With the search for activity data in Enterprise Search. Worklists for Quality Issues and Activities Business Add-Ins (BAdIs) for Enhancement of Lists of 1. For example.0 SP04 Effects on Customizing You will find the BAdIs in Customizing for QIM under Worklists . More Information Search and Operational Analytics: Content for SAP QIM 1.Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1. All rights reserved. PUBLIC © 2014 SAP SE or an SAP affiliate company. 1. no influence on the interface is necessary using context-based adaptations (CBAs) of the Web Dynpro applications. to an archive file and thus free up space in the database. Technical Details Technical Name QIM_104_FIELD_CONTROL Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) PUBLIC © 2014 SAP SE or an SAP affiliate company. 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 Technical Details Technical Name QIM_104_ARCH Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1. to define certain input fields as required-entry fields or show them in display mode. 1. for example. Effects on System Administration You can access all archiving functions.7 Customer-Specific Field Control You can store a customer-specific field control for the Web Dynpro applications for processing issues and activities. All rights reserved.0 SP04 Effects on Existing Data After archiving.2. Archive administration can also be accessed from the QIM work center System Administration . This allows you. but need to retain for documentation purposes. More Information Archiving QIM Data 1. and Customizing and the documentation for the QIM archiving objects. you can export data that you no longer require in the system. in archive administration (transaction SARA). As field control directly affects the BOPF node. enter the technical name of the archiving object in archive administration and choose Goto -> Documentation . the data can be displayed but no longer changed. To open the documentation for the archiving objects.1.2. To be able to use the modification. Page 8 of 106 .Technical Details Technical Name QIM_104_ESH_ISS Product Feature Is Changed Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1.6 Archiving of Activities and Issues Using archiving. you must regenerate the connectors. for example.0 SP04 Effects on Existing Data The relevant delivered search models were therefore changed. in a completed issue all fields are shown in display mode.Availability SAP QIM 1. see SAP Note 1820834. 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. see also SAP Note 1909219. or when processing or displaying issues and activities. Effects on Customizing You make the settings for field control in Customizing for QIM under documentation for the Customizing activity. You can open the side panel when creating issues or activities using the advanced create function.8 Enhanced Definition and Assignment of Reference Objects 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. When processing issues. the following CHIPs are available: The generally available CHIP Notes for adding public or private notes about the current object The new QIM-specific CHIP Related Issues or Subissues that shows in graphical form which other issues or defects exist with the same reference objects or the same code When processing activities. The new object type Storage location (STL) is delivered as an example of an object type copied in this way.0 SP04 Effects on Customizing You make the settings for the object types for reference objects in Customizing for QIM under Basic Settings Generic Settings for Reference Objects Define Object Types .1. Page 9 of 106 . You can select several objects at once when assigning reference objects. For more information about the procedure.0 SP04 Effects on Existing Data The general field control in BOPF for the business object overrides the customer-specific settings for field control. All rights reserved. For more information about the procedure. using the link Additional Information . For more information about the procedure. For example.2.2. You can adapt the search dialog box for existing reference objects. Technical Details Technical Name QIM_104_REF_OBJ Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1. for example. Environment Define Field Control . see the 1.1. A new column for the assignment of a search help is only ready for input for the object type GOJ and its copies. you can only add notes.9 Side Panel for Applications for Processing Issues and Activities 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. see SAP Note 1909219. Technical Details Technical Name QIM_104_SIDEPANEL Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1. 1. regardless of the settings for field control. For more information about the procedure.0 SP04 PUBLIC © 2014 SAP SE or an SAP affiliate company. by adding additional search helps or hiding existing search helps. The new functions also allow you to define the content for other problem-solving methodologies yourself. Within the scope of the content delivered for 8D.10 Workflow for Notification of New Issues With the workflow for notification of new issues. New functions and new content are delivered for this. you can use a new Business Add-In that you can find in Customizing for QIM under Processing Business Add-Ins (BAdIs) BAdI: Enhancement of QIM Web Dynpro Applications . it is possible to inform the issue driver when an issue is reported that he or she needs to process. To do this. see Customizing for QIM under Environment Activate Workflow .2.2.11 Problem-Solving Process Using 8D Methodology You can map problem-solving processes using 8D methodology in SAP QIM. All rights reserved. New workflow objects are delivered for this. enter the effectiveness of an activity in percent.1. As part of the scope of content for 8D. The new functions include the following: Customizing activities to divide a QIM issue into steps (or phases). it is possible to create an 8D problem analysis from a defect (for example. You can copy activities from step D5 to step D6. Issue More Information Additional Information in Side Panel Reports for Related Issues or Defects 1. eight steps are delivered for the eight disciplines. and store a free text for the verification of the result. This application configuration depicts the 8D steps on the interface and also permits the following: You can create immediate containment actions in step D3 using a quick entry function. The option of defining a follow-up issue for a QIM issue. to which the new PDF-based form QAM_ISSUE_8D is assigned in Customizing. A special print form (I8D) for printing or e-mailing an 8D report. You can enter the percentage contribution of different causes for a defect. 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 emailing. for example: Workflow template 56900008 Standard task 56907941 Technical Details Technical Name QIM_104_WORKFLOW Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1.0 SP04 Effects on Customizing For information about how you activate the new workflow. for a customer complaint).Effects on Customizing You can make other CHIPs available in the side panel.1. You can assign the validation status Effectiveness Check Outstanding . The option of assigning a specific Web Dynpro application configuration to an issue type. Page 10 of 106 . You can influence the copy process using a new Business Add-In (BAdI). The option of selecting according to steps in the worklist for activities. Within the scope of the content for 8D. 1.0 SP04 PUBLIC © 2014 SAP SE or an SAP affiliate company. Technical Details Technical Name QIM_104_8D Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1. a new issue type for 8D problem analyses (Q8D) and the application configuration QIM_OVP_8DISS are delivered. You can include a new field in the Web Dynpro component configuration for activity details in which you can enter the effectiveness of an activity in percent. you can define steps and make settings for them. the Web Dynpro component configuration QIM_OVP_8DISS_D30_ACTIVITY_FRMRP is delivered for the creation of 8D containment actions. In Customizing. As an application example. For the easy capturing of a number of activities. Effects on Customizing The Customizing settings for the issue types were enhanced. If you set the relevant indicator in Customizing for print forms. As an application example. you can add new columns from the column set with the information relating to the follow-up issues. More Information Problem Analysis Using 8D Methodology 1. it is possible to select individual defects when printing or e-mailing issues. For issue processing or problem analysis. the Web Dynpro component configuration QIM_OVP_8DISS_D50_ACTIVITY_TREE is delivered. As an application example. In the table for defects. for example.12 Adaptation Options for the User Interface In addition to the existing enhancement options. see the documentation for the Customizing activity in Customizing for QIM under Issue Processing Define Issue Types . the Web Dynpro application configuration QIM_OVP_8DISS is delivered for the processing of 8D problem analyses. Effects on System Administration PUBLIC © 2014 SAP SE or an SAP affiliate company. You can also make settings for follow-up issues. there is a new Defect Selection indicator.0 SP04 Effects on Existing Data If you adapt the Web Dynpro configurations centrally. you can include a UIBB that is based on the FPM form repeater component and uses the delivered FPM feeder class /IAM/CL_ACTIVITY_FORMRP_FEEDER. If issue types for follow-up issues are stored in Customizing. You do this in Customizing for QIM under Issue Processing ProblemSolving Methodologies Activate BC Sets for 8D . the Web Dynpro component configuration QIM_OVP_8DISS_ACT_OVERVIEW is delivered.2. You can include a new field in the Web Dynpro component configuration for processing causes in which you can enter the percentage contribution of the causes to a defect. You can also include a field for storing a free text for the verification of the result. users may have to reset their personalization for the central changes to become visible. the Trigger Problem Analysis pushbutton appears automatically on the user interface. As an application example. there are also new activities for defining the steps of a problem-solving process (under Issue Processing Problem-Solving Methodologies ). All rights reserved. For more information. In Customizing for the print forms. For example. As an application example. Page 11 of 106 .1. You can enter follow-up issue types for an issue type. You will find the BAdI for influencing the copy process for activities in Customizing for QIM under Issue Processing Business Add-Ins (BAdIs) BAdI: Influence Copying of Activities .Effects on Existing Data New validation status for activities: Effectiveness Check Outstanding Effects on System Administration Adapt your PFCG roles as described in SAP Note 1994956. You can include a pushbutton for copying activities. the Web Dynpro component configuration QIM_OVP_8DISS_CAUSE_OVERVIEW is delivered. You can use the Customizing content delivered for 8D by activating the BC Set. This function is relevant when processing defects for a QIM issue. You can influence the copy process using the new Business Add-In (BAdI) /IAM/BADI_COPY_ACTIVITY. Technical Details Technical Name QIM_104_UI_ADAPT Product Feature Is New Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Availability SAP QIM 1. you have other options for adapting the Web user interfaces for the processing of QIM issues and QIM activities: You can assign a specific Web Dynpro application configuration to an issue type. which you can use to specify that individual defects of an issue can be selected in the dialog box for printing or e-mailing issues. This allows you to vary the user interface for the processing of issues of an issue type without context-based adaptations. You can use these step settings in your issue type-specific Web Dynpro application configurations. for a question catalog. there is a new column for the assignment of an issue type-specific Web Dynpro application configuration. which you can use to specify that individual defects of an issue can be selected in the dialog box for printing or e-mailing issues. the delivered application configuration QIM_CHIP_PAGE_ISSUES was changed for the page for opening quality issues. processing them by initiating suitable quality activities.If you assign a specific Web Dynpro application configuration to an issue type. Effects on System Administration If you used Customizing to redefine the page for opening quality issues or the generic CHIP for quick access. FMEA. there are also new activities for defining the steps of a problem-solving process (under Issue Processing Problem-Solving Methodologies ).2 Use of SAP QIM SAP Quality Issue Management (SAP QIM) offers you the option of capturing various types of quality issues. All rights reserved. Technical Details Technical Name of Product Feature QIM_104_QUICKACCESS Product Feature Is Changed Country Dependency Valid for all countries Software Component Version QAM Application Component CA-IAM-QIM (Quality Issue Management) Available as of SAP QIM 1. You can integrate different SAP systems and – with the help of the open interfaces supported by ABAP systems – also integrate non-SAP systems. and activities Comprehensive analytical functions that reach beyond application and system boundaries Transparent documentation of the issue handling process and thus better cost control With SAP QIM. For example. SAP QIM thus offers you the following advantages: Integrated solution and a central point of access for processing and monitoring quality issues. and determine responsible partners Use terminology to fit your requirements thanks to the adaptable user interface Determine partners. For more information. define quality activities. also from other applications and systems (for example. you must adapt your PFCG roles as described in SAP Note 1994956. and causes) and to improve performance. effects. and monitoring the processing status throughout the resolution process. you can do the following: Access quality issues and quality activities using role-based worklists Create new quality issues. Effects on Customizing The Customizing settings for the issue types were enhanced. SAP QIM is therefore a generic framework that supports you with mapping and tracking all kinds of issues and ideas and with continuous improvement processes. you may have to make your changes again after you install the support package. 1. you can map the capturing and processing of quality issues in one end-to-end process. customizable user interface Standardized and efficient processes for issue processing. The application thus supports the entire issue resolution process from issue capturing to issue resolution and a final validation. claims) Intuitive usability owing to a Web-based. You can also map use cases that go beyond classical quality management. In Customizing for the print forms.1.13 QIM-Specific CHIP for Quick Access to Quality Issues To allow easier access to subitems of a QIM quality issue (defects. 1. there is a new Defect Selection indicator. for example. see the documentation for the Customizing activity in Customizing for QIM under Issue Processing Define Issue Types . rule-based determination of partners. there is a new column for the assignment of an issue type-specific Web Dynpro application configuration. codes.2. You will find the BAdI for influencing the copy process for activities in Customizing for QIM under Issue Processing Business Add-Ins (BAdIs) BAdI: Influence Copying of Activities .0 SP04 Effects on Existing Data To include the new CHIP. codes. You can also make settings for follow-up issues. the generic quick-access CHIP was replaced by the QIM-specific CHIP QIM_QUICK_ACCESS. For example. audits. such as improvement requests or service requests. Users may also have to reset their personalization so that the central changes become visible. Page 12 of 106 . and activities automatically (based on rules) at the level of quality issue and quality activity Display quality issues in hierarchy form Check the effectiveness of the quality activities initiated (own status) Create quality activities quickly and efficiently using activity templates Use the wide range of issue and activity types provided Use activity templates to create quality activities more quickly Request a response from the issue or activity driver depending on the quality issue type or activity type PUBLIC © 2014 SAP SE or an SAP affiliate company. In Customizing. quality notifications. You can. For more information.0 ERP 6. Side-by-side: SAP QIM as a standalone solution parallel to an existing system In this variation. The master data and organizational data in SAP ERP is available as a basis. claims) to be able to coordinate and monitor their processing. and control communication with external systems. SAP ERP In this variation. see Overview: Creating Quality Issues. for example. for example. audit questions. you can access a specific quality activity directly or search for quality activities. A graphic shows an analysis of the number of quality issues by priority and status. Several applications are available for creating new issues. There. you can create and process catalogs. display all quality issues resolved within a specific time period or analyze quality issues and quality activities according to different criteria. Quality Activities Create new quality activities for a quality issue and process existing quality activities. You can use SAP QIM in the following scenarios: Standalone: SAP QIM as a standalone solution Add-on: SAP QIM as an add-on solution to an existing system.sap. More Information System Architecture Administrator's Guide for SAP QIM (on SAP Service Marketplace under Quality Issue Management ) https://service. For more information. The home page provides an overview of the Worklists for Quality Issues and Quality Activities. see System Administration Work Center.0 X General notification item X General notification task X Service notification X Service notification item As of enhancement package 5 for SAP X PUBLIC © 2014 SAP SE or an SAP affiliate company. you can search for issues.com/instguides SAP Business Suite Applications SAP Features Using the various adaptable work centers in SAP NetWeaver Business Client. You can sort issues and activities according to their status. Features You can integrate the following SAP ERP objects as of the specified releases: Worklists Object General notification As of SAP ERP 4. Quality Issues Create new quality issues and process existing quality issues. and document the process clearly and transparently. such as SAP ERP systems. and codes using BRFplus. The systems communicate via RFC connections or services. All rights reserved. For example. 1. you have access to exactly those applications and functions that you require to perform your tasks: Home Get an initial overview of the existing issues and activities. You can integrate objects from other systems by including them in the worklists for issues and activities or by assigning them as reference objects to a QIM quality issue or a QIM quality activity.1 Connection of Systems in a Side-by-Side Scenario To use the advantages of SAP QIM to the full. For more information. see User Interface Adaptation. Reports Use comprehensive analytics options. System Administration Access comprehensive process control and configuration functions. for example. For example. and notifications directly. process them efficiently. Using Enterprise Search. quality notifications. alerts. access decision tables for rulebased determination of activities.6C As of enhancement package 6 for SAP ERP 6. you can get an overview of the urgency of unresolved quality issues and activities. you can access a specific quality issue directly or search for quality issues. For more information. see Worklists for Quality Issues and Quality Activities. The worklist provides you with a central point of access for objects from different source systems. For more information.Map the problem-solving process using 8D methodology Implementation Considerations You should install this component if you want to capture quality issues within one system or across different systems. For more information.2. see Quality Activities. For more information. via RFC connections or services. Worklists Create personal worklists for existing quality issues and quality activities of different origins (for example. see Connection of Systems in a Side-by-Side Scenario. a typical scenario is the installation of SAP QIM as a separate solution to which you can connect various existing systems. SAP QIM and SAP ERP run on separate systems. For more information. see Reports. for example. You have a wide range of options for adapting the delivered structure of the work center and the interfaces in the applications to fulfill the requirements of your enterprise. SAP QIM and SAP ERP run on the same system. For example. partners. Page 13 of 106 . see Inbox (CA-EPT-IBO). Inbox Access work items. about constraints and the BAPIs that are used for access). All rights reserved. More Information Technical System Integration Setting Up System Connections 1.0 X X Action-relevant audit question X FMEA defect item X Batch X Customer X Outbound delivery X Outbound delivery item X Document X Equipment X Functional location X Storage location X Plant X Purchase order X Purchase order item X Material in ERP X Material in NW (product) Vendor X X Note For more information about the integration of the objects (for example. then under the settings for object categories using the Reference objects Object As of SAP ERP 4. about constraints and the remote POWLs that are used for access).Service notification task X Quality notification X Quality notification item X Quality notification task X Maintenance notification X Maintenance notification item X Maintenance notification task X Claim X Claim task X Action-relevant audit question X Audit action X FMEA defect item X FMEA action X Note For more information about the integration of the objects in the worklists (for example. see Customizing for object access under Basic Settings Generic Settings for Reference Objects Define Object Access . see Customizing for object access under Worklists for Quality Issues and Activities ( Implementation Information ) pushbutton.3 Worklists for Quality Issues and Quality Activities PUBLIC © 2014 SAP SE or an SAP affiliate company.0 As of enhancement package 6 for SAP ERP 6. you can check whether the function modules listed are available in your system.6C General notification X Service notification X Quality notification X Maintenance notification X Maintenance order Claim As of enhancement package 5 for SAP ERP 6. see SAP Note 1820834. Page 14 of 106 . . If you want to connect to an object from a system with different release level. For more information about how you add additional reference objects yourself. then under the settings for categories using the ( Implementation Information ) pushbutton. a mapping in Customizing. for example. Integration The worklist provides you with a central point of access for objects from different source systems. You create a new worklist under New Worklist . For more information about the enhancement of worklists in QIM. To improve performance when selecting entries. Status For a selection of the status of issues and activities across all systems. Page 15 of 106 . the source system is mandatory for the selection. and general notification tasks in an SAP ERP system Service notifications. PUBLIC © 2014 SAP SE or an SAP affiliate company. To get a harmonized view in a list with different source systems and different object categories.3 Worklists for Quality Issues and Quality Activities To get an overview of existing quality-related issues and activities in different systems and applications. and service notification tasks from an SAP ERP system FMEA defect items and FMEA actions in an SAP ERP system Maintenance notifications. 4. These objects include the following: Quality issues. for example.in particular for the issue ID . A structure mapping is stored for each object category. for example. All other entries for the selection criteria depend on which object category you have selected. and quality notification tasks from an SAP ERP system General notifications. 5. This provides you with a harmonized overview from which you can jump to the various systems. the following selection criteria are particularly important: Issue Type So a user can select all issue types from various systems in the same manner in his or her worklist. for example. 3. maintenance notification items. notification items. about the underlying object category.1. for the monitoring control of quality issues. see SAP Note 1865206. you can create worklists in QIM based on various selection criteria. You should make your entry dependent on the capacity of the respective source system. you can specify the selection criteria for the list of worklists. according to status or according to the requested start and end date. and quality activities from an SAP QIM system (see also Issue Processing) Quality notifications. You can display and print the displayed list of worklists in PDF format (under Print Version ). A worklist for quality notifications. see Technical System Integration. For more information about the technical integration of the objects.1 Selection Criteria When you create or change a worklist. You change the layout of a worklist under ( Open Settings Dialog ). To improve monitoring.than a worklist for FMEA defect items. you can specify the maximum number of hits to be displayed in the result list for the combination of source system and object category. Prerequisites You have made the following settings in Customizing under Activities to call up worklists correctly: Cross-Application Components Quality Issue Management Worklists for Quality Issues and Settings to access quality issues and quality activities Settings for assigning authorizations in the POWL cockpit If you wish. see Customizing for QIM under Worklists for Quality Issues and Activities Define Access to Quality Issue Types .3. you can display additional information. In combination with the object category. 10. You change the selection criteria for a worklist under Change Worklist if you have authorization to do this. deleting. you can also make other settings in Customizing. for example. quality notification item. 6. For one or more rows in the worklist. you can show a traffic light in the worklist for a monitoring control of issues and activities. 1. choose ( Personalization ). You can make a status change for several rows simultaneously and thus set a number of issues in process. you specify for each object category which system is to be used to read the data. if necessary. the objects in QIM were decoupled from a specific data model. You can change the layout of the worklist page. Activities 1. For each source system object. you specify the selection criteria for the issues or activities to be listed. 9. You can open the object in the respective row of the worklist and its reference objects in the source system via links (see Jumps). there is an object category in QIM. 2. defects. or renaming the worklists. and maintenance notification tasks from an SAP ERP system Claims and claim tasks in an SAP ERP system Action-relevant audit questions and audit actions in an SAP system To facilitate the view across all systems. All rights reserved. you can store a list of issue types across all systems and. quality notification items. by grouping. 7. for example. This conversion is stored in Customizing for the object category in a structure mapping. Here. service notification items. The monitoring control is possible. The worklist draws together objects from the QIM system itself and from connected SAP systems and non-SAP systems. some statuses are automatically converted by the system. Features The most important selection criterion for a worklist is the object category. 8. To do this. For more information. requires different entries . for example. In Customizing. You can export the displayed list of worklists to Microsoft Excel (under Export ). you can thus define queries with variable time periods or partners. Here.1 Selection According to Calculated 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. All rights reserved. administrators can create queries centrally in the back-end system and make them available to all users. each user can adapt the layout of his or her own worklist. see the documentation for SAP NetWeaver ABAP under View with Settings. for example. For more information. You can also deactivate queries here. PUBLIC © 2014 SAP SE or an SAP affiliate company.2 Layout You can change the layout of the worklist page overall and also change the layout of each individual list of worklists. On the one hand. 6. 5. 1. With these default queries (also known as admin queries). for which a specific user is responsible. each user can define user-specific queries in the worklist using the New Worklist pushbutton. For more information. it is possible that you are not permitted to change the selection criteria. In Customizing for QIM under (transaction POWL_COCKPIT). choose More Field Help in the respective context menu (right mouse button). The layout of a list of worklists can be adapted for all users centrally and by each user personally. You access personalization by choosing ( Personalization ). divide these into categories. or print versions. 1. In the standard system. little effort is required to make worklists with flexible selection and a specific layout available to a number of users. sorting.3.3. you can make settings for the column selection. You can select objects whose requested end will be reached in four weeks. for example. For more information about the individual selection criteria. For example. filtering.3. Worklists for Quality Issues and Activities Make Settings in POWL Cockpit .3 Definition of Queries You define the layout of a list of worklists and make default settings for selection criteria in a query. sort them. a separate query is delivered for each object category. In addition. you can restrict the worklist using other selection criteria and thus list only those quality issues. On the other hand. Any changes you make in the POWL Cockpit are relevant for all users. In addition. and rename them if necessary. If problems occur with the selection of data. For more information. 3. you can display the relevant messages in the list display under Logs Worklist . Select Standard POWL and choose Execute . see the documentation for SAP NetWeaver ABAP under Personalization. see Definition of Queries. You create a worklist for the combination of object category and source system (multiple selection is also possible). Activities 1. More Information Selection According to Calculated Dates Selection According to Variable User or Business Partner 1.Activities 1. This is available in Customizing for QIM under Worklists for Quality Issues and Activities Make Settings in POWL Cockpit (transaction POWL_COCKPIT). List Layout The layout of a list of worklists depends on the query that the list is based on. For more information. Here. see the documentation for the Customizing activity. When searching using the input help for a selection criterion. you can copy several values from a table or a text editor and paste them in a field. the respective number of new rows are inserted for the copied values where these values are entered. 4. Under Display . 2. You can also paste value intervals. open the POWL Administrator Cockpit 2. you can specify the number of hits displayed per combination. each user can specify a choice of worklists. You change the selection criteria for an existing worklist under Change Worklist if you have authorization to do this. which is stored in Customizing for QIM in the POWL Administrator Cockpit (POWL Cockpit). This is possible via ( Open Settings Dialog ). you have the option of specifying hierarchy columns.3. Activities You define default queries in the POWL Administrator Cockpit . In both cases. Additional settings for the layout support your personal requirements. With centrally defined worklists that you did not create yourself. Page 16 of 106 . for example. Features Page Layout Using personalization. there is also an ID mapping for the assignment of different values in the source system and QIM system in a nonharmonized system landscape. If necessary. for example. Integration You use the Service Mapping Tool (SMT) for the definition of the structure mapping.4 Structure Mapping To display a harmonized list of all the different objects in the worklist. the system also performs a value mapping for the status by transformation. under Worklists for Quality Issues and Activities Define Access to Quality Issues . open the POWL Administrator Cockpit 2. For the object categories delivered with QIM.5 Jumps Using the link following an object ID in the worklist. 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 worklist. This is possible if you enter a variable in the respective selection field. you can jump directly to the object itself or to its reference objects in the source system and display or edit the object there. This Web application is available in SAP QIM under Administration Edit Structure Mapping . 4. 1. the business partner for the user must exist. 5. which is then replaced by the current user or business partner who opens the worklist. If you want to use the variable <USER2BP>.3.3. switch to change mode and choose Calculated Dates . In Customizing for QIM under (transaction POWL_COCKPIT). Select the personalization application QIM_GQIA_POWL and choose Register Query . Prerequisites In Customizing for QIM under objects in the worklist. You can change this mapping as required. Choose Maintain Query . for example. However. . Select the query for which you want to define a calculated date and choose Maintain Query . Select Standard POWL . the system performs a structure mapping. You can use the following variables: <USER2UNAME> &ndash. In this case. the structure mapping is also provided. 6.3. In addition to the field mapping for the assignment of source and target structures. You can find the assignment of the mapping to the object category in Customizing for QIM. 1.3. only the fields that are relevant for the respective object are filled. 4. is replaced by the current user ID <USER2BP> &ndash. If this ID mapping fails to work. the system displays the value from the source system in the worklist. 3.2 Selection According to Variable User or Business Partner You can define a default query for a worklist that shows for each individual user which QIM issues or QIM activities he or she is assigned to. not every field of the generic target structure in QIM is filled by each source object. Select the personalization application QIM_GQIA_POWL and choose Register Query . All rights reserved. Activities 1. Open the query in which you want to use a variable and choose Query Parameters . System Features The structure mapping defined in SMT is stored in Customizing for the respective object category. Enter the corresponding variable in a user or business partner 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). 1. This is useful.3. you have made the settings for the reference objects of the Page 17 of 106 . which you can display in the worklist to check the ID mapping. The user can then enter the variable <USER2BP> in the respective selection field. 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 system sets a Local <Object> indicator. As well as this value mapping within the structure mapping. 5. This means that different status values of source objects are converted to a common status in QIM. This allows harmonized selection by status in the worklist (see Selection Criteria). Basic Settings Generic Settings for Reference Objects PUBLIC © 2014 SAP SE or an SAP affiliate company. Worklists for Quality Issues and Activities Make Settings in POWL Cockpit . This assigns the different structures of the objects in the source systems to a generic structure in QIM. 3. for example. 1. For products (object category Material in NW . If you select one or more rows in the worklist. and a list of available fields. If a digital signature is necessary for a status change (see Issue Processing with Digital Signatures). The user that is stored in the RFC connection for the respective source system must have authorization to access the required object in the source system. 1. the navigation options in the source system are restricted. Note Some objects have no status. Information about the object category If you select a row. see Reports in Business Context Viewer (BCV). All rights reserved.6C) and you are working with SAP NetWeaver Business Client for HTML. For example. Page 18 of 106 . The following statuses are possible: Set in Process Complete The status is automatically changed in the source system. you can access information about the object category that is relevant for the selected row by choosing Object Category . you can edit the object directly in the source system.8 Monitoring Control of Issues and Activities To monitor the quality issues and quality activities listed in the worklists. 1. In the respective Customizing activity. In the following cases.7 Status Change You can change the status of several objects in one step. no mass change of the status is possible. that is. you can display lists of system messages relating to the respective status change. If necessary. only restricted navigation is possible in the source system for each release level for technical reasons.3. for example. Features If you select one or more rows in your worklist. For the object category plant (PLANT_ERP) . detailed information. you can display additional information for one or more objects. only restricted navigation is possible in the source system. you can access the relevant information in the settings for the object category by choosing ( Implementation Information ). see the various Customizing activities for access to quality issues and quality activities in the worklist or for access to reference objects. Under Logs .Note In the worklist. This opens the side panel in which Business Context Viewer (BCV) query views are displayed in the form of diagrams for the rows that are currently selected. however: If objects are located in an older system that does not support the display of Web applications (for example. Information is displayed about possible restrictions in the selection criteria. such as any detailed descriptions available in the source system. the defect in the QIM system. SAP R/3 4. MAT_NW). you cannot jump to other applications. Features If an object is located in an SAP system that supports Web applications. is displayed below the list. For information about which RFCs are relevant for which object. Features The monitoring control is enabled technically by implementations of the following Business Add-Ins (BAdIs): PUBLIC © 2014 SAP SE or an SAP affiliate company. In addition to object-specific authorizations. other steps are triggered by the system. the data is displayed via the material master display (transaction MM03). Retail articles and product groups are handled as ERP materials and belong to the object category MAT_ERP. For more information. the function Additional Information is available. Features You can access the following information for one row: Detailed information If you select a row in the worklist. A status change is not possible for these objects. the underlying RFCs must be stored in the authorization object S_RFC.6 Additional Information In the worklists for quality issues and activities. you can store different criteria for a monitoring control in the system. that is for one or more rows in the list of worklists.3. you can change the status for the selected objects under Issues or Activities . You can visualize the result in the worklist in the form of a traffic light. reference objects other than those defined for processing quality issues in SAP QIM can be relevant (see also Reference Objects). no jump is supported. To display the traffic light for monitoring. The filter values stored here are available to users of the worklist as options when they select a criterion for monitoring control. it controls the default settings of code groups. and which subitems can be created for an issue. Create the filter value for the implementation in Customizing for QIM under Worklists for Quality Issues and Activities Define Monitoring Control of Issues and Activities . 1. that is. All rights reserved. You can also map use cases that go beyond classical quality management. 1. you have the option of capturing different types of quality issues and processing them by initiating suitable quality activities. you must select the issue type for which you want to create the issue. Issue Type You always create issues with an issue type. and activity templates. 1. such as improvement requests or service requests. specify the criterion (that is. PUBLIC © 2014 SAP SE or an SAP affiliate company. 2. and canceled ones get a red traffic light. For example. you can also create a quality issue in QIM from a corrective or preventive action. In the selection criteria for the list under Monitoring Control . The issue type specifies the central settings for the processing of an issue.BADI_QAM_POWL_ISSUE_VALUATION for the monitoring control of quality issues BADI_QAM_POWL_ACT_VALUATION for the monitoring control of quality activities In the standard system. You can use the existing implementations supplied as a guide.4 Issue Processing In issue processing in SAP QIM. insert the Traffic Light column in the layout of the respective list.1.1 Overview: Creating Quality Issues You have three ways of creating an issue in Quality Issue Management: Create Quality Issue (Guided) Create Quality Issue (Quick) Create Quality Issue (Advanced) Note If you use SAP Audit Management. Monitoring control according to requested start and end date Examples: When the requested start date is reached. The issue type also predefines the possible reference objects for an issue. Define Your Own Monitoring Control 1.4. From this list. issues and activities in process get a yellow traffic light. partners. set the Inactive indicator for the respective filter value in the Customizing activity Define Monitoring Control of Issues and Activities . Activities Display Traffic Light in Worklist 1. see the documentation for the BAdI implementations. For more information. For more information. but the end date is not reached. Page 19 of 106 . see SAP Note 1771893. All BAdI implementations delivered in the standard system are activated. you can use these monitoring control criteria immediately in the worklist. Features You can use the functions Create Quality Issue (Guided) and Create Quality Issue (Quick) to create a quality issue quickly. You can use the Create Quality Issue (Advanced) function for the comprehensive entry of all data. the issue or the activity gets a yellow traffic light. the BAdI implementation) for the monitoring control. a red traffic light is set.1 Create Quality Issue (Quick) You use this function to create a quality issue without needing to know detailed data about the issue. two implementations are delivered for each of the two BAdIs: Monitoring control according to status Examples: Completed quality issues or quality activities get a green traffic light.4. When you open a create function. 2. Note If individual BAdI implementations (and thus criteria for monitoring control) are not to be available to the users of the worklist. You can create your own BAdI implementations for other criteria. you get a list of all the issue types defined in Customizing. If both dates are exceeded. Create your own BAdI implementation in Customizing for QIM under Worklists for Quality Issues and Activities Business Add-Ins (BAdIs) for Monitoring Control . 1. In this case. it is possible that conflicts may occur if mandatory partners are missing or an approval is required. these can be displayed.4 Issue Status Status Assignment During the course of processing.1.Quick creation allows entries in the following areas: Reported by Issue description Main reference object Issue code Urgency Timeframe Business partners In quick creation. or effects for an issue. you cannot finish processing with Save & Set in Process . entered the business partner for a mandatory partner role. You can make customer-specific changes to the sequence of the predefined steps (see Adaptation of the Web Applications in QIM). must be completed (see also Activity Status). Set in Process. All rights reserved. You can use the function Determine Partners and Codes to trigger the determination of partners using predefined business rules. Page 20 of 106 .2 Create Quality Issue (Guided) In guided creation of a quality issue.4.1. you can document defects. 1. you cannot save using Save & Set in Process . Effect). you can enter comprehensive data about an issue. The status modeling cannot be changed to meet PUBLIC © 2014 SAP SE or an SAP affiliate company. activities for which the Long-Term Activity indicator is not set. Features Issue Hierarchy You can show the issue hierarchy in the advanced create function and view a hierarchical structure of all elements that are assigned to an issue. Which business transaction triggers which status change is stored in the SAM editor (transaction SAMDT). Subitems Depending on the issue type.3 Create Quality Issue (Advanced) With this create function. for example. Conflicts can occur here if mandatory partners are missing and you cannot add these. the issue is set directly to the status In Process . You can set the issue status to In Process when you have entered all required information and. Not Successful .4. Only when the issue is further processed are all partners displayed that were found using the business process rules. or if an approval is required. causes. for example: Reference objects Business partners Attachments Defects and their subobjects Activities and their subobjects Change documents When you double-click an element in the issue hierarchy. Issue 1. The settings for this are made in Customizing for QIM under Processing Define Issue Types (see also Subitems: Defect. you can specify whether you set the status for the issue directly to In Process or whether you save the issue with the status New . for example.4. you can assign the issue status manually. In this case. you can assign a validation status. Successful. Complete ).1. only the Person Responsible is specified as a business partner. If you finish processing with Save & Set in Process . the creation of an issue is subdivided into the following individual steps: Describe issue Define reference objects Define urgency and partners Define activities Review and finish If you finish processing with Save & Set in Process . you can only use the Save function to save the issue in the status New . Depending on the entries required. You can only close the application with the Save function. all mandatory short-term activities. When you finish processing. When an issue was completed. an issue can be assigned different statuses (for example. the details of the element are displayed. Detailed description Attachments You can assign an attachment. If the business rules find other partner roles than the Person Responsible . that is. To be able to complete an issue. Cause. A newly created issue is assigned the status New . All rights reserved. it is still possible to process the issue in the status New .1 Status Profile for Issues The status profile /IAM/ISSUE_ROOT stored in the SAM editor defines the process flow for issue processing. Approval Process In addition. Digital Signature You can document status changes using digital signatures (see also Issue Processing with Digital Signatures). The following section describes the lifecycle status and approval status in more detail. Also note that the decision whether an approval is required or not is stored in Customizing for the issue type. all status types that an issue can have are displayed (with the exception of customer-specific user statuses). User Status You can add your own customer-specific user statuses to the issue status (see also User Status).customer-specific needs. an issue must be approved via an additional status. When this indicator is set. 1. set the Approval Required indicator. Page 21 of 106 . Only certain actions are allowed for certain statuses.4. However. you can activate an approval process for an issue type in Customizing. Other status types. archiving status or digital signature status. The following diagram shows a graphical representation of the possible status changes: Status Diagram The following table shows which status changes are possible for each initial status and which actions initiate the status change: PUBLIC © 2014 SAP SE or an SAP affiliate company. This cannot be displayed in the SAM editor. To do this. Activities You can display the status profile for issues in the SAM editor (transaction SAMDT). for example. are not taken into account.1. To do this. Note In the SAM editor. An issue can then only be assigned the status In Process if it was approved. enter the following data: Business Object: /IAM/ISSUE Node Name: ROOT Schema Name: /IAM/ISSUE_ROOT More Information You can find a simplified graphical representation of the possible status changes of an issue under Status Profile for Issues.4. in Customizing for Quality Issue Management under Issue Processing Define Issue Types . 2 Changing of Quality Issues You can change issues in SAP QIM under Quality Issues . You always make changes in the advanced maintenance function of a quality issue. you can create activities at the level of issues. All rights reserved. There is no status management for defects. Prerequisites Check the following settings in Customizing: Quality Quality Quality Quality Issue Management Issue Management Issue Management Issue Management Issue Processing Issue Processing Issue Processing Issue Processing Define Settings for Activity Categories Define Activity Types Define Activity Templates Define Issue Types Features The processing of activities is controlled via the activity category. 1. for example (see Codes and Code Groups). You assign the issue types to other issue types as subitems. causes. determines the partner roles for an activity. for example. Thus. Activities are created with a specific activity type. in turn. you must have completed all mandatory short-term activities of the subitems to be able to complete an issue. Activities with the category Information do not have status management. When an issue is saved. You make the settings for the subitems in Customizing for the issue types: The subitems have their own issue categories: QDF: Defect QEF: Effect QCA: Cause For subitems. the other activities remain locked so that several activities can still be processed by different users at the same time. Cause. which cannot be changed. In the Web Dynpro configuration delivered by SAP. To change an activity. In issue processing. you can define activity templates to simplify the creation of activities. for example. the subitems receive their own ID and can be processed individually in SAP QIM under Quality Issues . you must select the activity and choose Edit Activity . and causes.4. and effects represent subitems of an issue. The selected activity is then ready for input.3 Subitems: Defect. such as the status profile. you can create your own issue types in which the relevant settings can be made. also be created as subitems for a defect. Prerequisites You have made the settings for the subitems in Customizing for Quality Issue Management under Issue Processing Define Issue Types . Causes and effects can. causes.4. The activities can be changed independently of each other in SAP QIM under Quality Activities .4. For an activity type. The activity category determines basic properties of an activity. However. in which all subareas are displayed. you can also store your own BRFplus rules for activity determination and code determination and configure settings for the code groups.4 Quality Activities Activities include all types of actions or measures taken to resolve an issue. Effect Defects. the activities that were already entered for the issue are then not ready for input. When you change an issue. for each subitem. 1. defects.Status Possible Actions to Trigger Status Change New Status New Set in Process/ Save and Set in Process In Process Deletion Flag Flagged for Deletion Approve Approval Status: Approved New and To Be Approved Issue Status: New Reject Approval Status: Rejected Issue Status: Completed In Process/ In Process After Completion Completed Cancel Canceled Complete Completed Reopen In Process After Completion 1. In the standard system. and effects. you can enter your own activities for defects and causes. the subitems are all displayed as their own subarea. Page 22 of 106 . PUBLIC © 2014 SAP SE or an SAP affiliate company. which. The Create Quality Issue (Guided) and Create Quality Issue (Quick) functions are not available in change mode. Only the selected activity can be edited. that is. Origin The origin is specified for each activity: For activities that are copied over from Customizing automatically or as a proposal. you can specify that activity templates are automatically assigned to an issue. Adding New Activities There are different ways of adding activities: Using predefined business rules (see Determination of Activities Using BRFplus). You specify the sort sequence in Customizing when building a hierarchy for subordinate activity templates and when assigning activity templates to an issue type. you can define activity templates as proposals. and in which a partner is not necessarily involved. you must specify the activity type. For activities that are assigned manually. Question These can be activities whose answer can describe the issue and its context. the Proposal indicator is also set in the activity properties. or a cause. Activity Templates To simplify the creation of activities. no response and no partner assignment is possible. This allows you to group activities with a specific objective or purpose. The activity type includes the following settings: The role of the responsible partner Whether an activity is automatically set to the In Process status after having been created Whether the user who created the activity is automatically entered as the person responsible for the activity (see also Transfer of User Data for Activity Driver/Completed By for Activity). the hierarchical relationship of these activities is always taken into account. it is inserted as a subnode for the activity on which the cursor is positioned. regardless of which row is selected. for example. the origin is given as Predefined . Note When you create activities manually. You can group activities regardless of their category. code groups. for example. a defect. you can complete an issue but the activity still has the status In Process and can still be processed after completion of the issue. In the Partner Role Settings folder. You can also build up a hierarchy when you define activity templates (see Activity Templates). All rights reserved. you can specify whether it is mandatory to enter a partner for a role. Page 23 of 106 . PUBLIC © 2014 SAP SE or an SAP affiliate company. for example. You can change the sort sequence of the activities in the issue manually. via codes. Sort Number You use the sort number to specify the sort sequence in which the activities are to be processed. Information These can be activities that serve to provide information about an issue and can also be used as an element to group a number of activities. The activities are sorted in the sequence that is laid down by the sort number when an issue is created. Extended activity These are activities that contain comprehensive tasks and can usually only be processed together with a partner. or the template text. Activity Type You can create any activity types in Customizing for each activity category. a defect. The proposed activities are displayed as a list in the application and can be copied to an issue. When you add a new activity. Then. or a cause (see Proposed Activity Templates). Entered manually You can create activities without an activity template. You can only define response values in Customizing for the activity templates. In Customizing In Customizing. From activity template pool You can copy the required template from the list of activity templates defined in Customizing. an effect. The indicator can be set in Customizing for the activity template as a proposal. so that. no activity must be selected. If you want to insert an activity at the top level of a hierarchy. a partner must be entered for the activity before it can be set to In Process . For proposed activities. You can specify that only one partner can be entered for a partner role. For activities that are determined using BRFplus rules. the origin is given as Manually Entered . you can define activity templates in which you make certain default settings for the activities (see Activity Templates). When you insert proposed activities in the activity list that are part of an activity hierarchy. you cannot specify a response value. for example. When you create an activity. a proposed activity is always inserted beneath its parent activity.SAP delivers four activity categories: Basic activity These can be activities that must be performed immediately after an issue is created. the origin is given as Rule . You can search for the templates. Proposed activities In Customizing or in the decision table for determining activities using BRFplus. The answer can be specified via the type of response. Activity Properties Long-term activity If you set the Long-Term Activity indicator. Only restricted processing functions are available for information activities. Structuring Activities As a Hierarchy You can structure the activity list in an issue as a hierarchy. you can simplify the creation of activities when you create an issue. you can specify for an activity template that a response is necessary and also specify a response value: Date Code Quantitative A unit must be specified for the response value. you can specify the type of response. you cannot specify a response value. you can copy the activity templates from Customizing and create new activities with the templates. Activity templates can be copied to an issue. for example. or that the activity templates can be selected manually from a template pool.4. All rights reserved. 1. A bundle can be inserted in another bundle of activity templates. defects. or causes. defect. and set default activity properties. the issue itself cannot be completed. As long as an issue contains a mandatory activity that is not completed.1 Activity Templates Using activity templates. You then assign activity templates to an issue type. you can build a hierarchy for activity templates: You can bundle activities that belong together and transfer the whole bundle when you process an issue. a defect. If both the Long-Term Activity indicator and the Mandatory Activity indicator are set. activity templates are copied over automatically for an issue. Activities You create activities in the Web Dynpro configuration delivered by SAP when processing an issue. you can specify certain defaults that apply for all activities that are created with this template. effects. If this indicator was set in Customizing for the activity template. You can specify the duration at the level of activity templates. In the template. When you create an issue.1 Proposed Activity Templates At the level of the issue type and at the level of the activity templates. In Customizing. By means of the issue category. Note When you create activities manually in the issue without an activity template. or effect using rule determination in Business Rule Framework plus (BRFplus). it cannot be unset in the application.4. Page 24 of 106 . you can control whether the activity templates apply for issues. you can specify follow-up actions. cause. All types of activity categories can be inserted or used as a parent node. you can specify that activity templates should be transferred automatically to the issue. More Information See also Proposed Activity Templates and Determination of Activities Using BRFplus. If a start date is specified for an activity. You can display activity hierarchies for an issue type graphically in SAP Quality Issue Management under System Administration in the screen area Process Control Activity Network . Boolean None If you have not specified a response value.4. Response Type You can enter responses for all activity categories apart from Information . but you cannot delete the activity after the issue is completed. PUBLIC © 2014 SAP SE or an SAP affiliate company. Prerequisites You have checked the following Customizing settings: Quality Issue Management Quality Issue Management Issue Processing Issue Processing Define Activity Templates Define Issue Types Features When defining activity templates in Customizing. In activity templates. the end date is calculated automatically based on the duration specified in Customizing. 1. you can specify that in the application.4. You can process activities individually in SAP QIM under Quality Activities . or a cause. or that activity templates should be proposed and must then be transferred by the user. You create activity templates in Customizing for a specific activity type.1. Each activity is assigned an activity ID. When you build an activity template hierarchy. the Response Value field is not visible in the application. you can complete the issue even if the activity is still open.Mandatory activity Mandatory activities must be completed within the issue resolution process. Activity templates that were already copied over to the issue are grayed out in the dialog box. You select the proposed activity templates in the application in the Activities assignment block under Add Activities Proposed Activities . built up activity hierarchies in Customizing under Define Activity Templates .4. the subordinate activity templates are proposed: The subordinate templates are not copied over automatically.2 Determination of Activities Using BRFplus Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities. automatic transfer is specified for the subordinate nodes: If the parent activity template is copied over. When determining activity templates using BRFplus.Activity templates without the Proposal indicator are copied over directly when an issue is created. BRFplus rule set: DETERMINE_ACTIVITY This rule set specifies the process for rule evaluation through to evaluation of the decision table. All rights reserved.4. Decision table: DECISION_TABLE The decision table contains condition and result columns in which you specify the input and output parameters. just as for the whole BRFplus application. Note You can also call the decision table for activity determination and the activity determination workbench directly in QIM under System Administration in the screen area Configure Rules . The rules are specified in decision tables. The following BRFplus objects are delivered for activity determination: BRFplus application: QIM_ISSUE_DETERMINE_ACTIVITIES This application has the BRFplus storage type Customizing and can be transported like other Customizing. Activity templates with the Proposal indicator are not specified directly. using CTRL+mouse click. you have set the Proposal indicator in the decision table. The activity template contains more subordinate activity templates that are also proposed. They can still be selected and copied over to the issue multiple times. The activity template contains more subordinate activity templates that are copied over automatically. You can also determine proposed activity templates using the decision table for activity determination in Business Rule Framework plus (BRFplus). Activities 1. and codes. the subordinate templates are also copied over. Select the activity template that you want to copy over. if required. Add Activities Proposed Activities You define automatic or proposed activity templates at two levels: When you build an activity hierarchy When you assign activity templates to an issue type The following scenarios result from this: An activity template was marked as proposed when assigned to the issue type. If you want to create the activity at the top level. the BRFplus application can be replaced by customer-specific applications. If necessary. for example. The parent activity template is proposed and the subordinate templates are also proposed: Each template in the hierarchy can be selected individually. you must deselect all rows. Prerequisites You have defined activity templates and. The rule set can be replaced by a customer-specific one. The activity template contains more subordinate activity templates that are proposed. the new activity is created as a subnode of the selected row. Behavior in an activity hierarchy: The parent activity template is proposed. a specific activity template is automatically entered in an issue. partners. 1. 2. These activity templates are also displayed in the list of proposed activity templates. Page 25 of 106 . but can be copied over to the issue using . Example You can specify that depending on a specific issue code and priority. PUBLIC © 2014 SAP SE or an SAP affiliate company. An activity template was marked as automatic when assigned to the issue type. A dialog box appears with all activity templates that were assigned to the issue type and that were not copied over automatically. Note If you have selected a row in the list of activities. The activity template contains more subordinate activity templates that are also copied over automatically. You have assigned activity templates to the issue types in Customizing under Quality Issue Management Quality Issue Management Issue Processing Issue Processing Define Issue Types . The parent activity template is automatically copied over. BRFplus function: QIM_ISSUE_DETERMINE_ACTIVITY This function is part of the BRFplus application QIM_ISSUE_DETERMINE_ACTIVITIES that is defined as Customizing and can be replaced by a customerspecific function. but can be selected as proposals in the dialog box. 4. Enter the required data. Note The documentation for BRFplus exists in English only. each customer-specific rule set must be assigned to the BRFplus function /IAM/ACT_PARTY_DET_QIM. 5. Create Quality Issue (Quick) . Activities To activate activity determination using BRFplus. specify the BRFplus application and function that you 3. Page 26 of 106 . All activity templates for which a parent activity template was specified are positioned beneath the parent activity template when you create the issue. proceed as follows: 1. To create your own applications and functions for different issue types. Enter the relevant BRFplus function and application in Customizing for an issue type. just as for the whole BRFplus application. those activities are inserted that fulfill the specified criteria. More Information For more information about BRFplus. Output parameter Position : The position refers here either to a business partner group hierarchy or a position in HR Organizational Management. a specific partner is directly entered in the activity. 7. 2. Create an issue in Quality Issue Management. You use the position origin to specify whether the position is determined from a business partner group hierarchy or from HR Organizational Management. see Business Rule Framework plus (BRFplus). 4. Via the BAdI. Issue Processing Define Issue Types . all business partners that are assigned to this node are found by expanding the node. Open the table QIM Issue . If necessary. and codes. BRFplus rule set: DETERMINE_PARTY This rule set specifies the process for rule evaluation through to evaluation of the decision table. If you do not specify a BRFplus application or function in Customizing. Search for the application QIM* and choose Application as the object type. partners. Call the transaction BRFPLUS. You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus . The entry of the partner role as an output parameter is mandatory. If you choose the function Determine Activities for activities. For example. you can specify a parent activity template in the result columns for an activity template. BRFplus function: /IAM/ACT_PARTY_DET_QIM This BRFplus function is the interface to the QIM applications Create Quality Issue (Guided). the BRFplus application can be replaced by customer-specific applications. All rights reserved.3 Determination of Partner for Activities Using BRFplus Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities. The BRFplus function /IAM/ACT_PARTY_DET_QIM is an SAP object with the BRFplus storage type System and cannot be changed or replaced. whereby the specified partner role is always used. Drill down in the tree to Expression Decision Table . The following BRFplus objects are delivered for partner determination in activities: BRFplus application: QIM_ACTIVITY_DETERMINE_PARTY (QIM Activity Determine Partners) This application has the BRFplus storage type Customizing and can be transported like other Customizing.Decision Table for Activity Determination . The position specifies the task that certain employees in an enterprise have. 6.Features To be able to derive bundles of activity templates. The rule set can be replaced by a customer-specific one.Decision Table for Partner Determination) The decision table contains condition and result columns in which you specify the input and output parameters. such as experts. For each of the business partners assigned to the node. you can use the BRFplus application QIM_ISSUE_DETERMINE_ACTIVITIES as a template. To be able to derive values for a position. an entry is made in the list of partners in the QIM issue. The rules are specified in decision tables. You can specify the BRFplus application and BRFplus function for activity determination for each issue type in Customizing. Example You can specify that for a specific activity template.4. filter value 01 determines the assigned business partners for a position (= node) in a business partner group hierarchy and calls the implementation /IAM/IMPL_BUPA_HIERARCHY in BAdI /IAM/BADI_POSITION_TO_BUPA. To enable this. and Create Quality Issue (Advanced) . Note PUBLIC © 2014 SAP SE or an SAP affiliate company. In Customizing for Quality Issue Management under want to use for activity determination. no activities are determined for an issue type via BRFplus. Decision table DETERMINE_PARTY_DCSN_TABLE (QIM Issue . you must define a position origin for a partner role in Customizing for Quality Issue Management under Issue Processing Partners Define Partner Roles . 1. no redundant entries are added to the list of partners for the QIM issue. when you insert new entries with partner role and business partner (either directly or those found by the function). you can specify that the logged-on SAP user is automatically determined as the activity driver: A unique business partner ID must be created for the SAP user in the transaction BP or using the report /IAM/APP_CREATE_BUPA. In Customizing under Issue Processing Define Activity Types . You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus . Determine 'Completed By' for Activity Automatically If a business partner ID was created for the SAP user. set the Automatically Add 'Created By' User As Responsible indicator and specify the responsible partner role. Constraints The following restrictions apply for the transfer of employee data as the activity driver and activity completer: If a partner was already entered. 1.4. This application has the storage type Customizing and can be transported like other Customizing settings. Here also. The decision table is evaluated when you create a new activity. The data can only be copied over if one business partner only can be assigned to an employee. the data is copied over automatically and displayed in the Completion screen area when an activity is completed. For the activity categories. 1.4. Activities To maintain the values in the decision table. enter the initiator role. Open the application QIM_ACTIVITY_DETERMINE_PARTY (QIM Activity Determine Partners) with the object type Application . 5.You can also call the decision table for partner determination in activities and the partner determination workbench for activities directly in QIM under System Administration in the screen area Configure Rules . Table fields that are empty will not be taken into account in the evaluation. Save your entries. Features If. Enter the required values. If you select Employee as the business partner role. Page 27 of 106 . If more than one business partner ID exists for an employee.5 Activity Status The status management for activities depends on the activity category. Drill down in the hierarchy tree to Expression Decision Table . 3. see Business Rule Framework plus (BRFplus). it is done automatically by the system when a new activity is created. you can assign the employee data Personnel Number and User Name on the Identification tab. Note The documentation for BRFplus exists in English only. Open the decision table Determine_Party_Dscn_Table . the system cannot transfer the data.4. no new entry is created if entries were derived using the decision table. proceed as follows: 1. an existing entry with the same partner role but without a partner ID is found. You cannot start partner determination for activities directly when processing an issue. 2. no new entry is created but the partner ID is added in the existing entry. 4. Note You can jump to the relevant transactions for the business partner settings in SAP QIM under System Administration . All rights reserved. More Information For more information about BRFplus.4. This also applies in the case where several identical combinations of partner role and position or business partner result when the decision table is evaluated.4 Transfer of User Data for Activity Driver/Completed By for Activity Transfer of User Data for Activity Driver For each activity type. Specifying a partner role is mandatory. Call the transaction BRFPLUS. In Customizing for Quality Issue Management under Issue Processing Define Issue Types . If identical entries exist for a combination of partner role and business partner. the entry is not overwritten. different status profiles were defined in the SAM editor PUBLIC © 2014 SAP SE or an SAP affiliate company. Activities To display the status profiles delivered for activities. User Status You can add your own customer-specific status to the activity status (see also User Status). for example.(transaction SAMDT): Basic activity: simple status profile Information: technical status profile (required. are not taken into account. Only certain actions are allowed for certain statuses.1 Status Profile for Extended Activities The status profile /IAM/ACT_ROOT_EXTENDED_ACT stored in the SAM editor defines the process flow for processing extended activities. for example. Other status types. Under Node Name . enter /IAM/ACTIVITY. Note In the SAM editor. All rights reserved. The following section describes the lifecycle status in more detail. Open the SAM editor using the transaction SAMDT. 1. Page 28 of 106 . Under Schema Name . 2. The following diagram shows a graphical representation of the possible status changes: PUBLIC © 2014 SAP SE or an SAP affiliate company. More Information You can find a simplified graphical representation of the possible status changes &ndash.4. An activity can be validated with the following statuses: Successful Not successful Not measurable Digital Signature You can document status changes using digital signatures (see also Issue Processing with Digital Signatures). you can validate the activity. In this status. under Status Profile for Extended Activities.Validation As soon as an activity has the status Completed .5. for the archiving status. Activity&nbsp. Under Business Object . An activity can only be set to In Process when all required data was entered.4. 3. This is useful for activities that do not require any preliminary clarification. 4. the activity is no longer ready for input. all follow-up actions that exist for an activity must have been completed successfully. use the input help to select the status profile you want to display. such as a mandatory partner. enter the node ROOT. the status Postpone is possible. but not for the lifecycle status) Question: simple status profile Extended activity: extended status profile For extended activities. In Customizing under SAP Quality Issue Management Issue Processing Define Activity Types . all status types that an extended activity can have are displayed (with the exception of customer-specific user statuses). process as follows: 1. but can be changed back to the status In Process at a later stage. you can specify that the activities of an activity type are immediately set in process and do not have the status New . archiving status or digital signature status. Activity Completion To be able to complete activities. using the example of extended activities &ndash. for example. All rights reserved.4. the business partners.Status Diagram The following table shows which status changes are possible for each initial status and which actions initiate the status change: Status Possible Actions to Trigger Status Change New Status New Set in Process In Process Postpone Postponed Complete Completed Cancel Canceled Deletion Flag Flagged for Deletion Postponed Set in Process In Process In Process Complete Completed Return Returned Cancel Canceled Postpone Postponed Cancel Canceled Set in Process In Process Reopen In Process Returned Completed 1. Page 29 of 106 . Here. A follow-up action can. The follow-up action is assigned to an activity template in Customizing for Quality Issue Management. Features Each follow-up action requires an active implementation of the Business Add-In (BAdI) /IAM/BADI_ACT_FOLLOW_UP . The processing of follow-up actions is documented by their own processing status and their own processing log. The following properties apply to follow-up actions: If a follow-up action was specified for an activity template. A follow-up action can only be executed once. quantities. batch. It can only be repeated if it was not successful. Activities with a follow-up action cannot be completed directly.6 Definition of Follow-Up Actions Follow-up actions define actions or functions that are triggered automatically by the system when an activity is set to the status In Process . You define follow-up actions in Customizing for Quality Issue Management under Issue Processing Define Follow-Up Actions . and so on). New reference objects can be added to the list of reference objects via follow-up actions (for example.4. Activities 1. Create the BAdI implementation in Customizing under Issue Processing Business Add-Ins (BAdIs) BAdI: Definition of Follow-Up Actions PUBLIC © 2014 SAP SE or an SAP affiliate company. A follow-up action is fixed to an activity and cannot be moved to another activity. 2. a newly created material document). The BAdI implementation defines the required reference objects (material. . specify that an e-mail is sent to a partner. date fields. and parameters. the Follow-Up Action tab is visible when you are processing the activity. you can also specify defaults for parameters. you enter the key and the text for the follow-up action and the possible target systems for each follow-up action. they must first be set to the status In Process . Here. this code group is proposed by default in issue processing in the Issue Resolution screen area. You cannot change the existing assignment of the text schema. A specific text type was defined in Customizing for each text area. 4. in the issue resolution. you can specify a text type and a default code group for the text types (see also Codes and Code Groups). Note You can. All rights reserved. The Follow-Up Action tab is displayed. the text schema is assigned to an issue category or an activity category under Define Settings for Issue Categories or Define Settings for Activity Categories . the text type IDESC was created for the description of an issue. Page 30 of 106 . In the Follow-Up Action Parameters folder. Detailed Description. you can define defaults for a The permitted text schema is preset via the issue or activity category. The follow-up action cannot be executed without these objects. 3. Code Group . the fields for entering the issue description. you can specify default values for the parameters. it is also possible to set a default catalog when searching for codes. defects. or activities. Assign the follow-up action to an activity template in Customizing under Issue Processing Define Activity Templates . In Customizing for QIM. The standard schemas for QIM have the prefix QIM_* . The text schema QIM_ISSUE is assigned to the issue category Quality Issue . The mandatory objects are indicated accordingly. the fields Issue Description. In the Text Type to Text Schema Assignment folder. The reference objects are determined automatically by the BAdI and displayed under Issue Processing Define Activity Templates in the Reference Objects folder. The issue or activity categories are assigned to an issue type or activity type under Define Issue Types or Define Activity Types . The text schema is therefore valid in all issue types to which the issue category QIM is assigned. you should choose a customer-specific namespace that starts with Z or Y so that no identical entries are created. From the text schema.3. in Customizing for QIM choose Basic Settings Text Types Define Settings for Text Types . 5. The settings for text types include the following activities in Customizing: 1. extend the text schema by including your own text types in it. When processing an issue. Storing Historical Texts PUBLIC © 2014 SAP SE or an SAP affiliate company. 2. Presetting Code Groups via the Text Type In Customizing for QIM under Issue Processing code group depending on a text type. for example. Example In the standard system. The object types that are created via the follow-up action are also listed and indicated accordingly. the codes and code groups in the Issue Overview screen area belong to this text type. the text types IDESC and ISOLU are assigned to the text schema QIM_ISSUE. In the issue overview. Reusable Objects and Note If you want to include your own text types. You must then add the new fields for creating texts to the Web UI configuration so that they are displayed on the interface.5 Settings Dependent on the Text Type In issue processing. Example You have created an issue type with the issue category Quality Issue . Example The text schema QIM_ISSUE with the two text types IDESC and ISOLU is assigned to the issue category QIM (quality issue). If you now assign a code group COD_1 to the text type ISOLU. Note For example. You can assign a catalog to a text type. for example. and Code belong to the text type IDESC. Defining a Catalog for the Text Type Using the text type.4. The existing text types are listed in the Text Type folder. however. To do this. which is then displayed as a proposal for the code search in the text area for this text type. You therefore make presets for codes and code groups depending on the text types (see section Presetting Code Groups via the Text Type ). create an activity using the activity template to which the relevant follow-up action was assigned. One text area comprises the fields for the description and detailed description and the fields for codes and code groups. 1. You find the existing text types under Cross-Application Components Processes and Tools for Enterprise Applications Functions for BOPF Environment Dependent Object Text Collection Maintain Text Schema . the detailed description. The corresponding fields in the Issue Resolution screen area belong to the text type ISOLU. The text schema contains the two text types IDESC and ISOLU. Define Issue Types or Issue Processing Define Activity Templates . The catalog serves only as a proposal for the search and can also be changed if necessary (see also Codes and Code Groups). the respective text types are assigned to a text schema. a number of different text areas are available in which you can enter descriptions for issues. thus making the respective text schema effective in the application. that is. choose Codes In Customizing for Quality Issue Management. you can specify that a history is stored for the long texts entered in the various text areas. The identification of a code is unique and does not depend on a code group. you can also control the default setting of the code group for defects. sorted according to the time of entry. you can select all codes each time you use one. You can assign codes to the following areas: Issues Activities Defects Causes Effects Responses Resolutions You define codes globally in Customizing for Quality Issue Management. the text types DDESC (defect description) and DLCTN (defect location) are defined for defects. By means of the issue type. The newest text is at the top.4.4. and causes: In the standard system. a history is displayed directly beneath the respective long text field. The frozen long texts are displayed in their own text area and cannot subsequently be changed. effects. The text type CDESC is defined for causes. The default catalog setting is made in Customizing for the text types. You can assign your own code groups to these text types per issue type.For each text type. you can specify that the catalog is set by default when you search for codes. You can therefore assign codes to different code groups. independent of its assignment to a code group. the code groups are copied over by the system during issue processing: The code group for the issue description is copied over during issue definition. see Settings Dependent on the Text Type. in individual processing of activities. code groups. If you assign a specific code group to these two text types for an issue type. choose Basic Settings Text Types Issue Processing Codes Issue Processing Define Catalogs and Code Groups Issue Processing Define Issue Types Issue Processing Define Activity Templates . you can also control the search to be more specific by assigning codes to catalogs.1 Determination of Codes and Code Groups Using BRFplus PUBLIC © 2014 SAP SE or an SAP affiliate company. and by building code group hierarchies. Prerequisites Check the following settings in Customizing: Assignment of catalogs to text types In Customizing for Quality Issue Management. also sorted according to the time of entry. independent of their use. The display of the historical texts is integrated in the advanced processing of issues. In principle. The prerequisite here is that you have activated the response in Customizing for the activity template. the text types ADESC (activity description) and ARESP (response description) are defined for activity templates. The code group for the response description is copied over in the response. The default can be changed when searching for codes. Basic Settings Text Types Define Settings for Text Types . 1. In the standard system. In the standard system. the code group is copied over for the activities: The code group for the activity description is copied over during activity definition. You activate long text history in Customizing for QIM under whether historical texts can be stored. choose Default setting of code groups in issue types In Customizing for Quality Issue Management. Example You define a code 10 with the text red. You can also set defaults for code groups for each issue type and activity template. Page 31 of 106 . however. The code 10 can only exist once and it can be identified uniquely. There is also an overview of the historical texts of all text types. If you assign a specific code group to these two text types for an activity template. In Customizing.6 Codes and Code Groups You can use codes and code groups to classify different objects in Quality Issue Management according to specific aspects. and in the hierarchy view.6. Code Group folder . Specify for each text type For each text type. All rights reserved. Long texts entered are frozen and become historical if the text is changed in a different language or if the text is changed by another user. 1. You can therefore specify different catalogs for different areas of issue or activity processing. choose Default setting of code groups in activity templates In Customizing for Quality Issue Management. choose Catalogs and code groups In Customizing for Quality Issue Management. The default settings for code groups are also dependent on the text type. The text type EDESC is defined for effects. the text types IDESC (issue description) and ISOLU (issue resolution) are defined for issues. Code Group folder More Information For more information. The code group for the issue resolution is copied over during issue assessment. In Customizing for Quality Issue Management under Issue Processing Define Issue Types .4. or quality manager. Example You can specify that depending on a specific priority. the BRFplus application can be replaced by customer-specific applications. you can specify a BRFplus application and a BRFplus function for each issue type. The rules are specified in decision tables. If necessary. Issue Processing Define Issue Types . such as issue submitter. specify the BRFplus application and function that you 3. You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus . a specific code is directly entered in an issue. business partner master records must exist in the QIM system. just as for the whole BRFplus application. Note You can also call the decision table for code and code group determination in issues and the code determination workbench directly in QIM under System Administration in the screen area Configure Rules . Open the table QIM Issue . More Information For more information about BRFplus. you can define different partner roles that are necessary when processing an issue or activity.Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities. proceed as follows: 1.Decision Table for Code Determination . In SAP QIM. 1. 5. Call the transaction BRFPLUS. The rule set can be replaced by a customer-specific one. You can specify partner roles in Customizing for each issue type or activity type. Activities To activate code determination using BRFplus. BRFplus rule set: DETERMINE_CODE This rule set specifies the process for rule evaluation through to evaluation of the decision table. Features The BRFplus application and BRFplus function can be used per issue type for code determination or code group determination. BRFplus function: QIM_ISSUE_DETERMINE_CODE This function is part of the BRFplus application QIM_ISSUE_DETERMINE_CODE that is defined as Customizing and can be replaced by a customerspecific function. This also allows you to run code determination for defects. Search for the application QIM* and choose Application as the object type. The specific partners for an activity or an issue are identified by business partner IDs. More Information PUBLIC © 2014 SAP SE or an SAP affiliate company. issue driver. Decision table: DECISION_TABLE The decision table contains condition and result columns in which you specify the input and output parameters. 2. Drill down in the tree to Expression Decision Table . In addition. Enter the required data. depending on specific details such as the priority. causes. partners. partner roles and partner IDs can be determined using predefined business rules that were set up in Business Rule Framework plus (BRFplus). interested party. Page 32 of 106 . To create different BRFplus applications. In Customizing for Quality Issue Management under want to use for code determination. see Business Rule Framework plus (BRFplus). a number of people are involved in an issue and its resolution. you can copy the BRFplus application QIM_ISSUE_DETERMINE_CODE. The following BRFplus objects are delivered for code determination: BRFplus application: QIM_ISSUE_DETERMINE_CODE This application has the BRFplus storage type Customizing and can be transported like other Customizing. Note The documentation for BRFplus exists in English only. and effects separately. It is therefore necessary to assign different people with different roles to an issue or an activity.7 Partners Normally. For this to work. All rights reserved. and codes. 4. All rights reserved. that the role can only be assigned once. 1.4. such as issue driver. this ID is used to identify a specific partner. you can also specify whether a partner role is mandatory and unique. Page 33 of 106 . Prerequisites Settings in Customizing In Customizing for Quality Issue Management under Issue Processing Define Issue Types you can jump to master data maintenance and define default partners for a partner role.2 Partners in a QIM Issue You assign a partner ID to the partner role of a QIM issue.1 Partner Roles Partner roles describe the tasks of persons or groups of people who are involved in an issue or activity. the role of the person responsible. interested party. The data for a partner is maintained in the business partner master data. In this Customizng activity. You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus . you have also specified whether you want to plan the business partner IDs via a position in HR Organizational Management or a position (node) in a business partner group hierarchy.4. The partner role of the issue submitter.7. that is.For more information. or activity driver. . For activity types. you can also specify whether you want to plan business partner IDs based on a business partner group hierarchy or HR Organizational Management. see Business Rule Framework plus (BRFplus). Note The documentation for BRFplus exists in English only. 1. You have assigned the relevant partner roles to the issue types and activity types in Customizing under Quality Issue Management Define Issue Types or Quality Issue Management Issue Processing Define Activity Types . You have created business partners from customer masters and vendor masters using the synchronization cockpit (transaction MDS_LOAD_COCKPIT) (see also SAP Library SAP ERP SAP ERP Cross-Application Functions Cross-Application Components Master Data Synchronization ). and mandatory partner roles are copied directly to the issue or activity and displayed. Issue Processing Features You can copy all partner roles to an issue or activity that were assigned to the respective issue type or activity type in Customizing. You can also define partner roles freely to fulfill your own requirements. Optional partner roles can be selected for an issue or activity as required. For more information about BRFplus. Various partner roles are delivered by SAP as proposals.7. you must specify a business partner ID for the issue or activity at the latest when the status is changed to In Process . You can create business partners from HR master data and organizational data using the report HRALXSYNC (see also SAP Library SAP ERP Central Component Human Resources Personnel Management (PA) Personnel Administration Integration of Personnel Administration with Other PUBLIC © 2014 SAP SE or an SAP affiliate company. Business partner maintenance is a central function for storing and managing all partner information. Note The responsible partner role can only be assigned to one unique partner per activity or issue. see Partner Roles and SAP Business Partner. At the level of the partner role. Prerequisites You have created all partner roles in Customizing under Quality Issue Management Issue Processing Partners Define Partner Roles . For mandatory partner roles. You set the indicator for the unique Features Create Business Partners There are different methods of creating business partners in the SAP system: You have created the business partners in your SAP system using the function Maintain Business Partner (transaction BP) (see also SAP Library SAP ERP SAP ERP Cross-Application Functions Cross-Application Components SAP Business Partner Functions Processing Business Partner Data ). Default Partners using the Define Partners pushbutton. Otherwise the status change is not possible. you define default partners under Issue Processing Define Activity Templates assignment of business partner and partner roles under Issue Processing Define Activity Types Details . In this Customizing activity. In Customizing for Quality Issue Management under Issue Processing Define Issue Types . You use the position origin to specify whether the position is determined from a business partner group hierarchy or from HR Organizational Management.2. partners. Decision table DETERMINE_PARTY_DCSN_TABLE (QIM Issue . The BRFplus function /IAM/ISSUE_PARTY_DET_QIM is an SAP object with the BRFplus storage type System and cannot be changed or replaced. The following restrictions apply here: If a partner was already entered. To be able to derive values for a position. The rule set can be replaced by a customer-specific one. when you insert new entries with partner role and business partner (either directly or those found by the function). you can assign the employee data Personnel Number and User Name on the Identification tab. You can link business partners with SAP users in SAP QIM by choosing System Administration Create Business Partners for Users . Via a PFCG role. Note You can also call the decision table for partner determination in quality issues and the partner determination workbench in issues directly in QIM under System Administration in the screen area Configure Rules . Note You can jump to the relevant transactions for the business partner settings in SAP QIM under System Administration . All rights reserved. the business partner ID is entered in the partner list when an issue is created. Example You can specify that for a specific issue type. If you select Employee as the business partner role. whereby the specified partner role is always used. filter value 01 determines the assigned business partners for a position (= node) in a business partner group hierarchy and calls the implementation /IAM/IMPL_BUPA_HIERARCHY in BAdI /IAM/BADI_POSITION_TO_BUPA.4. If identical entries exist for a combination of partner role and business partner. no new entry is created if entries were derived using the decision table. For each of the business partners assigned to the node. the entry is not overwritten.7. For example. The position specifies the task that certain employees in an enterprise have. and codes. just as for the whole BRFplus application. If necessary. The rules are specified in decision tables. and Create Quality Issue (Advanced) . Once a business partner ID is assigned to the SAP user. BRFplus rule set: DETERMINE_PARTY This rule set specifies the process for rule evaluation through to evaluation of the decision table. 1.3 Determination of Partner for Issues Using BRFplus Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities. Page 34 of 106 . you can create or change business partners via System Administration Maintain Business Partner SAP ERP Cross-Application . such as SAP_QIM_COORDINATOR.1 Transfer of User Data for Issue Submitter For each issue type. you must define a position origin for a partner role in Customizing for Quality Issue Management under Issue Processing Partners Define Partner Roles . The data can only be copied over if one business partner only can be assigned to an employee. each customer-specific rule set must be assigned to the BRFplus function /IAM/ISSUE_PARTY_DET_QIM. Features If. You can transfer the business partner data to SAP QIM using the SAP distribution functions (see also SAP Library SAP ERP Functions Cross-Application Components SAP Business Partner Functions Distribution of Business Partner Data ). you can specify that the logged-on user is automatically entered in the partner list as issue submitter: A unique business partner ID must be created for the SAP user in the transaction BP or using the report /IAM/APP_CREATE_BUPA. a specific partner is directly entered in an issue. the system cannot transfer the data. no new entry is created but the partner ID is added in the existing entry. all business partners that are assigned to this node are found by expanding the node. In SAP QIM.Decision Table for Partner Determination) The decision table contains condition and result columns in which you specify the input and output parameters. This also PUBLIC © 2014 SAP SE or an SAP affiliate company.4.Applications Integration with SAP Business Partner ). an entry is made in the list of partners in the QIM issue. an existing entry with the same partner role but without a partner ID is found.7. If more than one business partner ID exists for an employee. Via the BAdI. The following BRFplus objects are delivered for partner determination in issues: BRFplus application: QIM_ISSUE_DETERMINE_PARTY (QIM Issue Determine Partners) This application has the BRFplus storage type Customizing and can be transported like other Customizing. To enable this. such as experts. Create Quality Issue (Quick) . the report /IAM/APP_CREATE_BUPA selects the users that are assigned to this role and creates a business partner for the selected users. BRFplus function: /IAM/ISSUE_PARTY_DET_QIM This BRFplus function is the interface to the QIM applications Create Quality Issue (Guided). The entry of the partner role as an output parameter is mandatory. the BRFplus application can be replaced by customer-specific applications. enter the initiator role. Output parameter Position : The position refers here either to a business partner group hierarchy or a position in HR Organizational Management. 1. there are several object categories for different release levels of the system in which the object is available (for example. vendors. You can find out which object types and object categories are available for reference objects in Customizing for QIM under for Reference Objects . 3. For some object types. Basic Settings Generic Settings General Reference Objects One notable case is the delivered External reference object (object type GOJ) that is intended for flexible use because it does not have a technical equivalent in another system. the object category describes the origin more exactly (for example. 1. you can reuse the delivered BAdI implementation /IAM/ACCESS_ERP_GENERALOBJECT with another filter value. When you select the function Determine Partners . you cannot jump to the respective object in another system. the following features for some delivered reference objects: If reference objects are located in an older system that does not support the display of Web applications (for example. Features Delivered Reference Objects In the standard system. For example. Table fields that are empty will not be taken into account in the evaluation. 5. see Technical System Integration. you can define your own search help in the external system if required and assign it in Customizing for the object type. It is based on the BOL component IAMGOJ for the business object GeneralObject . In the copied enhancement implementation. For this purpose. Open the decision table Determine_Party_Dscn_Table . it is the basis for another delivered object type Storage location (STL). All rights reserved.6C) and you are working with SAP NetWeaver Business Client for HTML. see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus . If you create your own reference objects on the basis of IAMGOJ. delivery items) as reference objects. Note. proceed as follows: 1. material in ERP or material/product in SAP NetWeaver). For information about how the technical integration is implemented. This BOL component can also be used as the basis for other reference objects. Specifying a partner role is mandatory. the partner roles and partners that match the specified criteria are entered in the partner table. maintenance notification). Create an issue in Quality Issue Management. Open the application QIM_ISSUE_DETERMINE_PARTY (QIM Issue Determine Partners) with the object type Application . All reference objects that are based on the BOL component IAMGOJ have the following special features: The reference to the object in another system only means that you can search for this object in the external system. Page 35 of 106 . Note The documentation for BRFplus exists in English only. object types and object categories are delivered for numerous types of reference objects. SAP R/3 4. 2. however. 6. For example. no redundant entries are added to the list of partners for the QIM issue. you can navigate to the assigned reference objects in the remote systems. More Information For more information about BRFplus. only restricted navigation is possible in the source system. PUBLIC © 2014 SAP SE or an SAP affiliate company. the reference objects can be located in other systems. Technically. Here also. this type of search help has the constraint that you can only search for the technical name and description (or for a combination of two technical names as with the reference object storage location). 4. material). Integration You can open the reference objects in the source system via links from the QIM system. you do not need to create your own BAdI definition. Drill down in the hierarchy tree to Expression Decision Table .8 Reference Objects You can assign objects to which a quality issue refers (such as materials. you can copy the enhancement implementation /IAM/ACCESS_GENERALOBJECT_NW for the delivered BAdI /IAM/BADI_GENERALOBJECT_CAT. Activities To maintain the values in the decision table. Call the transaction BRFPLUS. Navigation and Jumps From the QIM user interface. Save your entries.4. you cannot jump to other applications.applies in the case where several identical combinations of partner role and position or business partner result when the decision table is evaluated. batches. This application has the storage type Customizing and can be transported like other Customizing settings. In the QIM Web application. The object type describes an entity in general (for example. However. Enter the required values. batch numbers. and so on. see the Customizing activity for object access in the settings for the object category under ( Implementation Information ). the underlying RFCs must be stored in the authorization object S_RFC. An easier means of maintaining object access is provided by a wizard. you can select batches or a plant as subobjects for the material using the Subobject function.8. Retail articles and product groups are handled as ERP materials and belong to the object category MAT_ERP. such as materials. For reference objects. you can select the access to subobjects for a reference object of the issue type. batch number. Page 36 of 106 . customers.8. customers. PUBLIC © 2014 SAP SE or an SAP affiliate company.For products (object category Material in NW . you can specify a main reference object that is displayed in the header data of an issue. Reference Objects folder. access to the dependent objects batch and material was specified. see SAP Note 1820834. In addition to object-specific authorizations. MAT_NW). it is necessary to assign the activities the relevant reference objects. When you select material as the reference object for an issue. bills of material. Example For the reference object material . it is important to be able to assign issues the relevant reference objects. bills of material. All rights reserved. For information about which RFCs are relevant for which object. In Customizing for Quality Issue Management.4. and so on. From this list. Here.4. access to the dependent objects must be set up in Customizing under Basic Settings Generic Settings for Reference Objects Define Access to Dependent Objects . a logical system must be specified that is the original system of the reference object. Defining Other Reference Objects For more information about how you define additional reference objects. Note The user that is stored in the RFC connection for the source system must have authorization to access the required object in the source system. More Information Reference Objects for Issue Types Reference Objects for Activity Templates 1. only restricted navigation is possible in the source system for each release level for technical reasons. the data is displayed via the material master display (transaction MM03). such as materials.2 Reference Objects for Activity Templates To be able to specify activities in connection with the relevant objects. 1. Prerequisites You have made the settings for the object types in Customizing for Quality Issue Management under Objects . Basic Settings Generic Settings for Reference Features You can specify the relevant reference objects for each issue type.1 Reference Objects for Issue Types As issues mostly arise in connection with other business processes. that is. which you can find in Customizing for QIM under Start QIM Customizing Wizards . choose Issue Processing Types . you specify in which systems the reference objects are located (under Basic Settings Generic Settings for Reference Objects Define Object Access ). you can also define access to subobjects that can be copied over to the issue when you select the corresponding reference object. For reference objects. Define Issue All object types that you specified in Customizing for an issue type are available for you to specify as objects in the Reference Objects assignment block when you create an issue. When you create an issue. For reference objects. For this to work. No jump is supported for the following object categories: External reference object (GOJ_NW) Plant (PLANT_ERP) Activities Entering Systems for Reference Objects In Customizing for QIM. you can select the subobjects for an object using the Subobject function. a logical system must be specified that is the original system of the reference object. 4. You have assigned the respective print forms to an issue type under Processing Define Activity Types . Issue Processing Define All object types that you specified in Customizing for an activity template are available for you to specify as objects in the Reference Objects assignment block when you create an activity. 2. or to an activity type under Issue Features Defaults set in Customizing: In Customizing. you use Adobe PDF forms. You can set a default country so that the form can be formatted using country-specific conventions. Basic Settings Generic Settings for Reference Features You can specify the relevant reference objects for each activity template. you can specify that e-mailing is created as a separate activity and the PDF document is appended as an attachment: When you define the print forms. A dialog box appears showing the individual work steps.Prerequisites You have made the settings for the object types in Customizing for Quality Issue Management under Objects . Prerequisites In Customizing under Issue Processing Define Print Forms . specify an activity template with which an activity for e-mailing is then created.4. Issue Processing Define Issue Types . Process the individual work steps. The reference objects required by follow-up actions are automatically copied over to the activity without you having to specify the corresponding object types in Customizing. choose Activity Templates . specify an activity template with which an activity for printing is then created. In Customizing for Quality Issue Management. 2. You can set a default country so that the print data is formatted using country-specific conventions. Activities 1.11 Additional Information in Side Panel PUBLIC © 2014 SAP SE or an SAP affiliate company. 1. Reference Objects folder. Activities 1. you have specified the print forms that can be used when printing an issue.9 Printing of Issues or Activities To print activities or issues.10 E-Mailing of Issues or Activities To be able to send an issue or activity by e-mail. you have specified the print forms that can be used when printing an issue. You make the settings for printing in Customizing. 1. 1. You have assigned the respective print forms to an issue type under Processing Define Activity Types . Page 37 of 106 . or to an activity type under Issue Features Defaults set in Customizing: In Customizing. All rights reserved. you must have configured the print settings in Customizing. Choose the e-mailing function when processing an issue or an activity. Specify a document type so that a PDF document can be appended to the newly created activity as an attachment. Choose the print function when processing an issue or an activity. A dialog box appears showing the individual work steps. Issue Processing Define Issue Types . Prerequisites In Customizing under Issue Processing Define Print Forms . Specify a document type so that a PDF document can be appended to the newly created activity as an attachment. Process the individual work steps.4. you can specify that printing is created as a separate activity and the PDF document is appended as an attachment: When you define the print forms. see Customizing for QIM under Issue Processing Business Add-Ins (BAdIs) BAdI: Enhancement of QIM Web Dynpro Applications . More Information See also Audit Trail 1. The activity driver is informed as soon as the activity processor sets the activity in process. or when processing or displaying an issue. 1. for example. to enable collaboration using SAP Jam (Web Dynpro CHIP BSSP_SW_FEEDS). The following scenarios are mapped as examples for the workflow objects delivered with QIM: The issue driver is informed when a new issue is created.12 Change Documents Changes to an issue or activity in SAP Quality Issue Management are documented by means of change documents. the following CHIPs are available: Notes Related Issues or Subissues When processing activities. you can inform the interested parties and the drivers of the issue and activity. when an issue is created. The side panel can include various Web Dynpro CHIPs that relate to the object being displayed or processed in the main application. The issue driver is informed as soon as all activities for an issue are completed. you can notify the new driver. You can open the change documents via the evaluation of the audit trail or display them when processing issues or activities via the issue or activity hierarchy.1. Reports for Related Issues or Subissues For more information.4. You can use the external ID of the change document in the table to open the document in the audit trail. Activities To open the change documents for SAP Quality Issue Management in the audit trail.31 SP06. Page 38 of 106 . only an aggregated view for the subordinate objects. proceed as follows: 1. When certain status changes take place. 2.4. He or she can then initiate relevant activities. All rights reserved. When an issue is created for which an approval is required.13 Workflow Scenarios for Issue Processing To improve the cooperation of all persons involved in processing an issue. PUBLIC © 2014 SAP SE or an SAP affiliate company. set in process. When processing issues. see the SAP NetWeaver documentation about Web Dynpro ABAP Page Builder under Enhancing Web Dynpro Applications with a Side Panel.4. A list appears containing all the change documents found that meet the selection criteria. Features Adding Notes In the Web Dynpro CHIP BSSP_NOTES. Call the evaluation of the new audit trail in QIM under System Administration (transaction S_AUT10) in enhancement mode. Enter the selection data and start the evaluation. For more information about the BAdI. Integration The transfer of the ID for the current issue or activity to the CHIPs in the side panel for the context reference (tagging) is enabled via the Business Add-In (BAdI) BADI_QAM_GEN_APPL_CONTROLLER. you use the functions of SAP Business Workflow. you can inform the approver. For more information. You can add further CHIPs yourself. you can create your own workflow templates and thus map other scenarios. The prerequisite for this is that you have activated the business function Enable Social Media ABAP Integration 3 (BC_SRV_STW_03). you can store public or private notes about the object currently being displayed or processed. When you display them in the issue or activity hierarchy. for example. All change documents are displayed for the selected object. or completed. you can inform interested parties. see Reports for Related Issues or Defects.11 Additional Information in Side Panel When creating issues using the advanced create function. such as the following: If the driver of an issue or activity was changed. which is available as of SAP NetWeaver AS ABAP 7. When an activity is completed. you can only add notes. For this. all change documents for the selected object and its subordinate objects are displayed. you can use the link Additional Information to open the side panel. In addition. you can set the system up to send notification e-mails or work items automatically following certain events. The issue driver can then validate the activities and close the issue. copy the delivered workflow templates in the Workflow Builder (transaction SWDD) and adapt your copies. The actual agent assignment is done via the respective partner role in QIM. If a user name is assigned to the business partner. For more information.4. the automatic Customizing has been executed. you must perform the task-specific Customizing. Communication takes place via Business Objects Processing Framework (BOPF) . you must ensure that they are classified as General Tasks . Task Description Agent TS 56907941 Process Issue Issue Driver (expression &ISSUE_RESPONSIBLE_USER&) TS 56907924 Check Issue Completion Issue Driver (expression &ISSUE_RESPONSIBLE_USER&) TS 56907929 Activity in Process Activity Driver (expression &ACTIVITY_RESPONSIBLE_USER&) In addition. and in particular. see SAP Business Workflow: Reference Documentation in the documentation for SAP NetWeaver. If no e-mail address is stored either. You do this this in Customizing for SAP NetWeaver under Application Server Business Management SAP Business Workflow Maintain Standard Settings . 2. For these standard tasks. Delivery of Workflow Whether notification is by e-mail or by work item depends on the settings in the business partner master record for the respective partner (see also Partners in a QIM Issue): 1. More Information For general information about SAP Business Workflow. he or she receives an e-mail under the e-mail address stored in the business partner master record. To do this. you can activate logging via an event trace in the System Administration work center under Environment. PUBLIC © 2014 SAP SE or an SAP affiliate company. Standard Tasks The following standard tasks delivered with QIM can be edited in the dialog. When the workflows are active. Page 39 of 106 . In addition. If no user name is assigned to the business partner. All rights reserved. the workflow cannot be executed. the user receives a work item in the Inbox work center in QIM. For more information about the delivered objects. Activities If you want to use the delivered workflow templates and tasks.13.Prerequisites SAP Business Workflow is set up. A direct jump to the object is possible from the e-mail or the work item. Features Delivered Objects Workflow templates and workflow objects are delivered to map the following workflow scenarios: Inform issue driver when an issue was created Workflow template WS56900008 (abbreviation Q Issue Info ) Inform issue driver when all activities are completed Workflow template WS56900002 (abbreviation Q Acty Compl ) Inform activity driver when activity is in process Workflow template WS56900003 (abbreviation Q Acty Proc ) You can open the workflow template in the Workflow Builder (transaction SWDD). Object Types The following ABAP Objects classes are relevant as object types for the workflows: CL_QAM_ISSUE_WF_CONNECT CL_QAM_ACTIVITY_WF_CONNECT The events that trigger a workflow can therefore be all events of these ABAP Objects classes. there are delivered standard tasks that run in the background. you can develop your own workflow templates using the standard tasks delivered with QIM. 1. You do this in the task-specific Customizing or in the transaction PFTC under Additional Data Agent Assignment . 3. see Technical Implementation. see Customizing for SAP QIM under Environment Activate Workflow .1 Technical Implementation The interface between SAP QIM and SAP Business Workflow is implemented by means of ABAP Objects . An activity to start an escalation process can only be set in process by a digital signature from the quality manager and the escalation manager responsible. There is a separate screen area for each discipline.com. The signatures that were already executed are then revoked and the object returns to the status that it had before the start of the signature process. In Customizing for the issue type. you specify in the issue type or the activity type how the signature process is to be executed. Note In SAP QIM.15 Problem Analysis Using 8D Methodology 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 . the QIM system provides you with a tool that allows you to sign and log business transactions. is documented in the system.4. 1. All rights reserved.The delivered standard tasks are available as modules and can be used unmodified in your own workflow scenarios. With a synchronous signature process.4. 1. and time. You do this in Customizing for QIM under Issue Processing Define Issue Types . The user interface for 8D problem analysis differs from the user interface for the processing of other QIM issues. such as status changes. Only when the last required signature has been executed can a new application be called. 2. Page 40 of 106 . and also a cancelation of the process &ndash. Workflow Template The following workflow templates are delivered with QIM: Workflow Templates Description Triggering Event WS 56900008 Inform Issue Driver About Issue A new issue was created (CL_QAM_ACTIVITY_WF_CONNECT-CREATED) WS 56900002 Inform Issue Driver About Activity Completion All activities in the issue are completed WS 56900003 Inform Activity Driver About Activity Processing (CL_QAM_ACTIVITY_WF_CONNECT-COMPLETED) The activity driver has set the activity in process (CL_QAM_ACTIVITY_WF_CONNECT-INPROCESS) You can use these workflow templates directly and also use them as the basis for your own workflow templates by copying and modifying them. The digital signature ensures that the signatory can be identified unambiguously and that the name of the signatory is documented together with the business transaction. Example An issue can only be approved with the digital signature of the quality manager. you have different options: You can create it directly by choosing the issue type for an 8D problem analysis under PUBLIC © 2014 SAP SE or an SAP affiliate company. you can specify which business transactions must be signed and whether the signature is to be executed by one or more persons.sap. synchronously. or asynchronously. the various signatories must provide their signature directly one after the other in the application. To do this. You can display the log in the issue or activity hierarchy when processing issues or activities. date. Features You can activate the digital signature for business transactions when processing issues and activities. you have specified the business transactions for which a digital signature is required. The signature is automatically queried when the user attempts to execute the business transaction. To create an 8D problem analysis. the signatories can provide their signature independently of one another at their own workplace. In Customizing. when changing issues. a signature process with several signatories is possible. otherwise the whole signature process is invalid. This signature process can run synchronously or asynchronously. you can list the issues and activities for which a digital signature is required. The digital signature is only possible when creating issues using the advanced create function. within the context of issue processing. you can only use signature strategies to which a system signature based on user ID and password is assigned as the signature method. With an asynchronous signature process. Prerequisites 1.14 Issue Processing with Digital Signatures With the digital signature function. look up the keyword Digital Signature (CA-DSG) at http://help. The signature process &ndash. You can also open the logs under System Administration Environment (see also Environment). You have made the settings for the digital signature in Customizing for QIM under Environment Digital Signature . More Information For more information. To ensure that the eight disciplines in 8D are covered. Create Quality Issue (Advanced) . an 8D problem analysis is divided into steps. Each user authorized to provide a signature within a signature strategy who has not yet signed the respective object can cancel a signature process. or when processing activities. A dialog box appears in which the signature must be entered. Using the Worklists for Quality Issues and Quality Activities. In addition to an individual signature. you can assign other documents to the 8D problem analysis. 3. the system copies the data (for the codes and description. The defect is also entered automatically as the referenced defect. Here. The D5 activity is then set to Completed by the system. Issue Processing Problem-Solving Methodologies Activate If you want to use the delivered Customizing for a Defect with Problem Analysis (issue type QDP). If you want to process specific activities within an 8D problem analysis. Technically. you can specify activities for remedying the cause of a defect in the step D5 – Chosen Permanent Corrective Action(s) . and the attachments.You can trigger a problem analysis for a defect that. you can also set the end date of the 8D problem analysis. To do this. When processing a defect. When you create an 8D problem analysis as a follow-up issue. More information about the individual screen areas: In the Issue Overview . In the step D2 – Problem Description . choose Trigger Problem Analysis . For more information. some data is filled automatically. at the level of the 8D problem analysis. you can also assign these. you can define activities: in this case. you must also 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 ). If you want to do this at a later date. The end date of this step is set automatically when all activities are completed. for example. for example) from the defect.4. you can search for related issues or defects in the side panel. If you find a suitable 8D problem analysis. Technically. For all activities in the 8D process. see 8D: Technical Implementation. Result You can print out the results of the 8D problem analysis or send them by e-mail using a special PDF form for 8D reports.15. you can add other data manually. you must activate the BC Sets in Customizing for QIM under BC Sets for 8D . The end date of this step is set automatically when all activities are completed. with the issue type 8D Problem Analysis . The end date of this step is set automatically when all activities are completed. If you have done a root cause analysis of the defect. you enter the members of the problem-solving team by specifying the partner roles and business partners.1 8D: Technical Implementation PUBLIC © 2014 SAP SE or an SAP affiliate company. for example. For each cause. To be able to use the delivered Customizing settings. the activities that you entered in Customizing for the 8D issue type under Automatic and Proposed Activity Templates are listed automatically. you can enter an assessment of the resolution in the step D8 – Congratulate Your Team . In the step D1 – Team . 4. The step D6 – Implemented Permanent Corrective Action(s) includes the activities that you introduced in the D5 step. This allows you. the customer complaint. 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). In the step D7 – Action(s) to Prevent Recurrence . it is possible to select by steps in the worklist for activities. you can enter the effectiveness in percent and store a free text for the verification of the result. a customer complaint. With the exception of the status. see Reports for Related Issues or Defects. Recommendation You can save the documentation of your root cause analysis as an attachment to the 8D problem analysis in the QIM system. select the defect and choose Additional Information . however. you can create immediate containment actions for the 8D problem analysis using a quick entry function. you create a follow-up issue. You can add other activities manually. Process The following process describes how to create an 8D problem analysis when it is created for a defect: 1. Page 41 of 106 . 1. You can also link a directly created 8D problem analysis with an existing defect. you can assign the current defect to this existing problem analysis under Referenced Defects if required. such as documents relating to the defect analysis. you can assign the validation status Effectiveness Check Outstanding for the 8D problem analysis. for example. this creates a new activity for which some of the data is copied. Under Documentation . The system uses the activity type or activity template that you stored in Customizing for the respective step. you can enter the root causes in the step D4 – Root Causes . for example. If the problem analysis is relevant for other similar defects. You can overwrite this copied data. belongs to a QIM issue with the issue type Customer Complaint . Prerequisites The Customizing necessary for the 8D methodology (for example. date fields. The main reference object is the material of the defect from the customer complaint. To create a new 8D problem analysis. see below in the process description. For creating the problem analysis. In this case. for example. 6. the issue type 8D Problem Analysis (Q8D) is delivered via BC Sets. you can specify under % Contribution which portion of the defect was contributed by each cause. you can trigger or assign an 8D problem analysis. 2. the option to divide an issue into steps) to implement other problem-solving methodologies. For more information. The end date of this step is set automatically when all activities are completed. Here. the system automatically copies the dates for the requested start and requested end from the original issue. When planning is completed. For more information about the technical implementation of 8D in SAP QIM. An activity with this status cannot be archived. All rights reserved. For each cause. the system copies all data from the corresponding D5 activity. 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). 5. Under Attachments . see 8D Report. To wrap up an 8D problem analysis. In the step D3 – Containment Action(s) . For more information. some fields are automatically copied from the customer complaint or the defect to the 8D problem analysis. Here. You can use the method framework delivered with 8D (for example. you can use the copy pushbutton with the quick info Implement Activity to copy the activity to the D6 step. the system creates causes with the issue type Cause for Problem Analysis (QCP) (subitem of the 8D issue type). all issues types are available that are entered in Customizing for the issue type of the defect under Follow-Up Issues . 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. 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).4. If several defects are assigned to the 8D problem analysis or the customer complaint. some data is also taken from the defect. Customer Customer No. Each step corresponds to an 8D discipline. If you want the printed forms to appear under Documentation in the problem analysis. for example. You can use the 8D print form when printing or mailing from the 8D problem analysis or from the underlying customer complaint. This application configuration is assigned to the issue type Q8D in Customizing for issue types. More Information For technical background information about the concept of the QIM Web applications. and partly from the 8D problem analysis. The PDF-based form QAM_ISSUE_8D is assigned to this print form. In both cases. 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 &ndash. incl. customer complaint) Progress 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. contact data) First business partner with partner role CONTACT of 8D First business partner with partner role CONTACT of parent PUBLIC © 2014 SAP SE or an SAP affiliate company. 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 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 Material Main reference object Material of 8D problem analysis Issue description (short text) of 8D problem analysis of parent QIM issue (for example. see Adaptation of the Web Applications in QIM. The 8D reports for all selected defects are output consecutively in a PDF document. customer complaint) Material No.15. partly from the defect. If you create the 8D report from the 8D problem analysis and referenced defects are assigned to it. For this print form. If you create the 8D report from the customer complaint.bmp 8D Report Fixed title Type Text for issue type of 8D problem analysis External Reference No. a special PDF-based print form is available for 8D reports.Technically. If Different Title Block Bar code Logo Issue ID of 8D problem analysis as bar code type EAN128 Object Navigator (transaction SE80) Repository PUBLIC QIM MIME LOGO_8D. Reference object Customer (object type CUS) of 8D Reference object Customer (object type CUS) of parent problem analysis QIM issue (for example. you must assign an activity template and a document type. the print form I8D is delivered in the 8D BC Set. you can specify whether you can select the defects in the print dialog that are to be included in the 8D report.2 8D Report To print the result or interim versions of the 8D problem analysis or send them by e-mail. For this issue type. steps are delivered in Customizing for QIM under Issue Processing Problem-Solving Methodologies Define Steps for which you can make other settings (for example. you must select the respective print form for 8D reports in the dialog box for printing or e-mailing. assign timepoints). Page 42 of 106 . 1. you can choose which defects are to be included in the 8D report (if you made the respective settings in Customizing). All rights reserved. an 8D problem analysis is a QIM issue with a special issue type for 8D problem analysis (Q8D). For the issue type 8D Problem Analysis (Q8D). the data is taken partly from the original customer complaint. If you select several defects. Prerequisites You have made the settings for the print form in Customizing for QIM under Issue Processing Define Print Forms . 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). The first External Reference Object (object type GOJ) in The first External Reference Object (object type GOJ) in the reference object list of the 8D problem analysis the reference object list of the parent QIM issue (for example. customer complaint) Contact (at customer. Features You can create an 8D report directly from the 8D problem analysis or from the underlying customer complaint. problem analysis QIM issue (for example, customer complaint) D1 &ndash; Team Role First Name Last Name E-Mail Telephone Business partner from 8D problem analysis Department Department entered in SAP user of business partner D2 &ndash; Problem Description Issue description Issue description (short text) and detailed description (long Issue description (short text) and detailed description (long text) of 8D problem analysis text) of referenced defect Defect Code Defect Location Code group and code of respective fields of 8D problem analysis Code group and code of respective fields of assigned referenced defect Number of Parts Affected 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 &ndash; Containment Action(s) Containment actions D4 &ndash; Root Cause(s) Root causes of defects Data on all causes from the 8D problem analysis D5 &ndash; 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 &ndash; Implemented Permanent Corrective Action(s) Per cause: Implemented permanent corrective actions Data on all activities from the D6 step of the 8D problem analysis D7 &ndash; Action(s) to Prevent Recurrence Actions to prevent recurrence Data on all activities from the D7 step of the 8D problem analysis D8 &ndash; 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) Activities 1. In the 8D problem analysis or customer complaint, choose the icon for printing or sending e-mails. 2. Select the form for 8D reports (I8D). 3. Select the images that you want to be included at the end of the 8D report. Note The images from the underlying customer complaint are not included in the 8D report and are thus not available for selection. 4. 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. 5. When mailing, you can choose which of the attachments that were added in the various 8D steps should be attached to the e-mail. 6. The created PDF document is then displayed in the print preview. 7. 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 . More Information Problem Analysis Using 8D Methodology 1.5 System Administration Work Center In the System Administration area, a coordinator in SAP Quality Issue Management can make settings in the productive system. Prerequisites The System Administration area is available only to users with the role of coordinator. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 43 of 106 Features In the standard system, the following settings are possible under System Administration : Process Control Enables the user to make settings that are relevant for issue processing. Configure Rules Enables the user to configure rules, for example, for partner or activity determination. Communication with External Systems Enables the user to make mapping settings and monitor data transfer. Audit Trail Enables the user to manage the logging of changes in the system. Environment Enables the user to access messages in the application log and workflow settings. System Settings for Reporting Enables the user to define reports and queries in Business Context Viewer. If you want other setting options to be available under System Administration , you must change the relevant launchpads. You do this in Customizing for QIM under Environment Set Up Launchpads (see also Launchpads in QIM). 1.5.1 Process Control As coordinator for SAP QIM, you can check some of the settings relevant for issue processing in the System Administration work center. Features You can do the following: Call Customizing settings for codes and catalogs (see Codes and Code Groups) Display Customizing settings for issue type (see Overview: Creating Quality Issues) Make settings for business partners (see Partners in a QIM Issue) Display the Customizing settings for activity templates and display an activity hierarchy graphically as an activity network (see Activity Templates) 1.5.2 Configure Rules As coordinator for SAP QIM, in the System Administration work center you can use Business Rule Framework plus (BRFplus) to define rules for the determination of partners, activities, and codes or code groups. BRFplus is a Web-based application in which you can define rules and specify parameters in decision tables. Features You can set up the following rules: Determination of Activities Using BRFplus Determination of Partner for Issues Using BRFplus Determination of Partner for Activities Using BRFplus Determination of Codes and Code Groups Using BRFplus For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus . Note The documentation for BRFplus exists in English only. 1.5.3 Communication with External Systems As coordinator for SAP QIM, you can make some settings for system integration in a running system and monitor the communication in the System Administration work center. Features Monitoring To monitor communications, you can open and manage the logs for system access. This is possible for access to issues and activities in the worklists and for reference objects for QIM issues (under Access Object Types ). The same settings are also possible in Customizing for QIM. Mapping PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 44 of 106 You can make settings for structure mapping and ID mapping. You can access the Service Mapping Tool (SMT) and make settings for structure mapping. You can assign this structure mapping in Customizing for QIM in the settings for access to object categories (for reference objects and for objects in the worklist). The assignment is possible for the object category in general or for specific systems. For more information about structure mapping, see the example relating to worklists under Structure Mapping. In a nonharmonized system landscape, you can store a key mapping for individual values. For more information, see ID Mapping. For more information about the procedure for editing the ID mapping, see Creation, Editing, and Deletion of Key Mapping Information. 1.5.4 Audit Trail As coordinator for SAP QIM, you can make settings for the logging of data changed in SAP QIM in the System Administration work center. You can also evaluate the logged data. The functions of the Audit Trail component are available for this. Features The following change document objects are relevant for SAP QIM: /IAM/ISSUE /IAM/ACTIVITY For information about the functional scope, see the documentation for the Audit Trail component under Audit Trail (BC-SRV-ASF-AT). More Information Change Documents 1.5.5 Environment As coordinator for SAP QIM, you can access various logs and make workflow settings in the System Administration work center. Features Application Log For information about the functional scope when displaying logs, see the documentation for the application log under Displaying Logs. Workflow You can make settings for workflow tasks and assign agents for them, for example. In addition, you can activate the logging of workflow events (event trace) and display the results of the trace. Digital Signature You can access logs for the digital signature. The following applications and signature objects are relevant for QIM: Application Signature Object IAM: Quality issue/Change request Quality issue IAM: Quality activity/Activity Quality activity For more information, look up the keyword Digital Signature (CA-DSG) at http://help.sap.com. Archiving You can access Archive Administration and make all settings for archiving activities and issues. For more information, see Archiving QIM Data. 1.5.6 System Settings for Reporting As coordinator for SAP QIM, you can define and manage reports in the System Administration work center. To do this, you use the configuration center of Business Context Viewer (BCV). Prerequisites You have activated the following business functions: BCV_MAIN BCV_MAIN_01 You have made the necessary settings for the query cache. For more information, see Customizing for QIM under Viewer . PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Environment Configure Business Context Page 45 of 106 This is relevant particularly when searching for reference objects.Viewer . the selection options for a search criterion are dynamically adapted to the values already selected for other criteria. Example If you want to search for issues that have a particular plant and a particular customer as reference objects. The basis for this are search and analytics models. all issues that a user SMITH processed in any way or all issues in which the name Smith appears in the attachment. 2. see the documentation for BCV under Configuration Center. More Information Getting Started &ndash. Features For information about the functional scope of the BCV configuration center. As your search criterion. Only those customers are available that are assigned to issues to which the plant you already selected is also assigned. and a minus sign (-) instead of NOT to exclude terms. You should therefore use a plus sign (+) for AND operations or no operator. see Customizing for QIM under Search and Analytics Configure Search . Here. 4. 1. add an additional row using the plus sign after the input field. for example. the terms AND and NOT are not operators. Note here that different search criteria are linked with AND. you must use the specific search criterion (for example. If required. All rights reserved. see the SAP NetWeaver documentation about search and operational analytics under Searching. you can enter values for various search criteria under Advanced Search . This displays several of the search criteria that are relevant for this category.6 Enterprise Search With Search and Operational Analytics. However. you can search for the string SMITH and get a result list with all occurrences of this term. To refine the search. For information about the search and analytics models that are delivered with SAP QIM. Enterprise Search offers a central point of access to find structured and unstructured business data in your current system using a search screen. For more information about the settings required. such as attachments to a quality issue. Using the Search 1. Structured business data can be business objects. but are also searched for as strings. As your search criterion. Note Note that in the Enterprise Search version that SAP QIM uses. Prerequisites For all objects that you want to search using Enterprise Search. the corresponding values are linked with OR. you have created connectors and indexed the data in the transaction ESH_COCKPIT. Page 46 of 106 . Note Via the PFCG role SAP_BCV_ADMIN2. you can insert the search criterion Reference Object twice and select the respective values. you have access to additional administration functions. Features For information about the default search options in the basic search. select Reference Object Customer and select a specific customer. Filter according to the category in which you want to search. Within this. select Reference Object Plant and select a specific plant. Example In the basic search. 3. if you enter the same search criterion twice. unstructured data can be documents. If you want to search for issues in which either the plant or the customer is assigned.7 Reports You can evaluate issues and activities with different objectives: The evaluation of context-sensitive information when processing an issue by analyzing related issues for the same reference objects such as material and customer to recognize any systematic defects or trends in the process The comparison of frequencies of defects or numbers of different status values for issues of all types PUBLIC © 2014 SAP SE or an SAP affiliate company. see Search and Operational Analytics: Content for SAP QIM. proceed as follows: 1. SAP NetWeaver provides a common technical infrastructure that supports and harmonizes data provisioning for analytics and also for searching data. If you want to search for different reference objects for an issue. Reference Object Material ) and not the general criterion Reference Object . such as QIM quality issues. see the documentation for Business Suite Foundation under Business Context Viewer (BCV). a CHIP is integrated in the QIM home page that shows the number of issues by priority and status as a graphic. for example. and Number of Issues . Features Reports in QIM are mainly possible using the following technologies: Business Context Viewer (BCV) BCV reports are integrated into the QIM home page and in the Worklists for Quality Issues and Quality Activities. navigation to a transaction in a connected system). Search and Analytics Configure Business Context Viewer Features Side Panel You can open context-sensitive query views in BCV in the side panel of the QIM worklists by selecting entries in the list of worklists and choosing Additional Information .Regular analyses and reports for management To meet these objectives. PUBLIC © 2014 SAP SE or an SAP affiliate company. You define the required queries and key figures in the BCV configuration center. add their own queries and reports. individual key figures are displayed directly in graphical form in the side panel overview. or integrate links to further information (for example. For more information. For more information. which are described in detail in the documentation for BCV under Side Panel. Reports and transactions in connected systems For more information. Prerequisites If you are assigned to the PFCG role SAP_BCV_ADMIN2. the BCV query 1QAM_ISSUE_PRIORITY_LC is delivered for this graphic.1. for example. To display key figures in an overview and in a dashboard. Status . 1. For example. 1. you also specify the display format of the results and key figures in the form of a query view. For more information. They can use predefined queries for evaluating issues and activities. business content in the form of queries. For more information. For more information. This information can then be analyzed according to the business requirements of the user.7. For example. see Reports in Business Context Viewer. for Reports for Related Issues or Defects. You then have access to the functions of the BCV side panel. Here. showing the number of issues by priority and status. and a dashboard is delivered for QIM. For more information about this example. you can display groups of query views as dashboards. CHIPs in the side panel You can call up context-sensitive information about an issue that you are displaying or processing by displaying the side panel using the Additional Information link.1 Example: BCV Query via BAPI Search Connector As an example of a BCV query for a BAPI search connector. see Additional Information in Side Panel. see Customizing for QIM under . as a graphic or in table format. All rights reserved. see Reports Using Search and Operational Analytics. see Reports in Other Systems. CHIPs You can also integrate BCV queries into the QIM user interface as CHIPs. see Example: BCV Query via BAPI Search Connector.7. a graphic is available on the home page. you can use your own queries to determine the data so trends can be displayed. you can define your own BI queries on the basis of supplied Operational Data Providers (ODPs) as part of search and analytics models. you must define a new search connector. For more information about the settings necessary for using BCV. Search and Operational Analytics For operative reporting. query views. For detailed analyses. This query uses the BAPI search connector 1QAM_ISSUE_PRIO_LC. You can enlarge each key figure in the main window and use other BCV functions there. and dashboards can be created centrally by an administrator. You can add other CHIPs. To display other result fields. evaluations.1 Reports in Business Context Viewer (BCV) BCV in SAP QIM offers a framework that allows different types of additional information to be integrated in the application. you have a wide range of configuration options available. Features Technically. see the documentation for BCV under Configuration Center. You can adapt and extend this business content. Note Note that the search connector only provides the fields Priority . queries. Page 47 of 106 . You can use the search connector supplied as a template. Users can also integrate their own personal favorites and reports. Various CHIPs are available in the side panel. As an example. You also use the BCV configuration center to group several query views in a dashboard. you can use Operational Analytics with Operational Data Provisioning. The Operational Data Provider (ODP) 0QAM_ISSUES. Features When you have created a connector for the search and analytics model 0QAM_ISSUES. You have created a connector for the search and analytics model 0QAM_ISSUES in the transaction ESH_COCKPIT. or when processing or displaying an issue.7. to identify an existing 8D problem analysis that fits for a defect.4 Reports in Other Systems PUBLIC © 2014 SAP SE or an SAP affiliate company. for example. Therefore you must activate this DataSource in the transaction RSA5. You do this in the transaction RSA5. which is called once for issues and once for defects. the related issues or defects displayed in the graphic are related to the issue being processed. the corresponding related issues or defects are listed in a table below the graphic. which is part of the search and analytics model 0QAM_ISSUES. The link can be a common reference object or the code. see the SAP NetWeaver documentation about Web Dynpro ABAP Page Builder under Embedding the Side Panel. For operational reporting. SAP NetWeaver provides a common technical infrastructure that supports and harmonizes data provisioning for analytics and also for searching data. a maximum of three circles can be displayed: A circle with the parameter distance 0. enhance the structure QAMS_REL_ISSUES_DYNAMIC and the selection and result structure of the BOPF query SELECT_ISSUES_FOR_CONTEXT for the business object /IAM/ISSUE. The common parameters used for selection in the CHIP are stored in the back-end system. that encompasses the issues that have the same code only The size of the circles displayed depends on the number of issues with matching parameters. Page 48 of 106 . for performance reasons. see the documentation for the class /IAM/CL_I_Q_SEL_FOR_CONTEXT. For more information. is available for the definition of analytical queries for operational reporting. The BAPI search connector provided uses the DataSource 0QAM_ISSUES for access. 1.7. that encompasses the issues that have the same material only A circle with the parameter distance 1. For information about calling the side panel editor.3 Reports for Related Issues or Defects When creating issues using the advanced create function. generated at runtime. in which certain parameters match. the report is provided by the CHIP Related Issues or Subissues (QAM_RELATED_ISSUES). The TransientProvider 2O0QAM_ISSUES. you can use the link Additional Information to open the side panel. A circle represents a group of issues. If no subitem is selected. For more information. see Problem Analysis Using 8D Methodology. which you can then assign to the defect. 1.7. you can configure the timeframe for selection and a table view of the data. you can define analytical queries with the Business Explorer (BEx) Query Designer. 2. a defect or a cause). or the code. You can display detailed information about the related issues via a link. is available as the InfoProvider. Features The QAM_RELATED_ISSUES CHIP displays the related issues in a portfolio graphic that takes into account the time interval between the related issues and the number of parameters that do not match (parameter distance). If you wish to add additional reference objects. You can use this feature. Prerequisites 1.Note also that. that encompasses the issues that have the same material and the same code A circle with the parameter distance 1. Integration Technically. When you select a circle in the graphic. If the CHIP is passed a material and a code. For more information about creating analytical queries for operational reporting. for example. for example. the reference objects customer and material . In the side panel editor.2 Reports Using Search and Operational Analytics With Search and Operational Analytics . the search connector for the class CL_QAM_BCV_SIN_DS_QAM_ISSUES only provides the fields to which a meaning has been assigned. where graphics appear showing the issues and the defects that are related to the current issue or a selected subitem (for example. You have activated the DataSource 0QAM_ISSUES. All rights reserved. The graphics are updated depending on the context. see the documentation for SAP NetWeaver under: Using Analytic Queries for Operational Data Providers BEx Query Designer More Information Search and Operational Analytics: Content for SAP QIM 1. For nonharmonized systems. To use the delivered entries. Here you can evaluate notifications. reports in the connected systems are available to you. For more information. This object may be located in another source system. depending on whether the settings are for worklists or reference objects: Worklists: Worklists for Quality Issues and Activities Reference objects: Basic Settings Generic Settings for Reference Objects The technical implementation is the same in both areas. All rights reserved. the object types are subdivided into object categories. Here you must store the RFC destination of the connected system as the system alias. Setting Options You make the settings for the object types and object categories in Customizing for QIM. audit issues. see ID Mapping. The following genIL components are relevant for SAP QIM: Worklists Quality issue: QAM_QI Quality activity: QAM_QA Quality issue type: QAMQIT Reference objects (examples) Material: IAMMAT Plant: IAMPLA Customer: IAMCUS Vendor: IAMVEN Document: IAMDOC In SAP QIM.8 Technical System Integration One important feature of SAP Quality Issue Management is the option of integrating objects beyond system boundaries. the system accesses an object with a specific data model. For more information. abstract definitions were stored in the business object layer (BOL) via the geNIL Model Editor (transaction GENIL_MODEL_EDITOR). Page 49 of 106 . if available &ndash. see the example relating to worklists under Structure Mapping. see Launchpads in QIM. instance REPORTS). The BOL calls the genIL component. This is relevant particularly for the following functions: Worklists for quality issues and activities Assignment of reference objects Features General Features To enable the integration of different objects and systems. For all object types. Mapping The assignment of the different data models is done via structure mapping. see the documentation for the respective Customizing activities. or FMEA defects in the transactional system (such as SAP ERP). object types were defined in SAP QIM. or it may be located in the same system. such as an SAP ERP system. Depending on the object category. you can also store an ID mapping (key or value mapping). in SAP NetWeaver BI. for example. More Information Connection of Systems in a Side-by-Side Scenario Setting Up System Connections PUBLIC © 2014 SAP SE or an SAP affiliate company.In the Reports work center. or &ndash. This is stored in Customizing for the object category. 1. you can add additional reports and transactions by extending the appropriate launchpad in Customizing for QIM under Environment Set Up Launchpads (role QIM. for example. Access to the specific objects in the source systems is technically executed by categorydependent implementations of Business Add-Ins (BAdIs): The system accesses the business object layer (BOL) via the object category. Prerequisites You have defined RFC destinations for the systems in which the reports and transactions are to be opened. For more information about the setting options. For more information. which in turn calls the category-dependent BAdI implementation. For this. the following RFC destinations (connection type H) must exist: SAP_ERP_QualityManagement SAP_BW Activities In addition to the delivered reports. You specify for an object category which system is to be used to display the data. the objects in SAP QIM were decoupled from a specific data model. In the same Customizing activity. You do this in Customizing for SAP NetWeaver under Application Link Enabling (ALE) Basic Settings Logical Systems Define Logical System . client 000. 4. The following RFC connections are required: Under ABAP Connections .2 Setting Up System Connections To be able to display objects from other SAP systems in your QIM worklist or to be able to assign reference objects from other systems to QIM objects. Communication with External 2. you must first set up the connection to the relevant system. In the System Administration work center under Communication with External Systems Edit ID Mapping . You do this in the same section of Customizing for SAP NetWeaver in the Customizing activity Assign Logical System to Client . Assign all the logical systems you just created to their respective client. Procedure 1. the local system is the reference system. specify in the system-dependent settings for an object category whether an ID mapping is required. 4. If you do not enter a system. 2. to a QIM issue. Key mapping is relevant for master data. In the same Customizing activity. Activities Key Mapping 1. you can store a key or value mapping for individual IDs (keys or values) so that the data is displayed in a harmonized manner in a QIM system. Note Alternatively. Define a logical system for the local QIM system. Value mapping is relevant for Customizing data. This column shows an indicator that is set if the ID field shows the key from the source system and not from the reference system. Application Server IDoc Interface / Example If you are running SAP QIM in system QIX. Page 50 of 106 . You do this in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Communication Create RFC Connections . 3. proceed as described in Customizing for QIM under Quality Issue Types . Integration For ID mapping. you can display the Local <Reference Object> column in the worklist. Create RFC connections for the logical systems you created. The system uses the data model and the respective API for the reference system category for access to the objects.1. Reference system category: Select an object category that is supported in the reference system. After a successful ID mapping. whose values do not match in the various systems. create an RFC destination for the local QIM system with the connection type 3.8. specify the assignment of the values.1 ID Mapping In a nonharmonized system landscape. Value Mapping For value mapping for the issue types. All rights reserved. If you assign a reference object. MAT_ERP in an ERP system. a coordinator can make the settings for the object type in the System Administration work center under Systems Access Object Types .8. 3. you define logical systems for all systems that you want to connect to SAP QIM. If you want to make a selection across different issue types in the worklist (see Selection Criteria). you name the logical system QIXCLNT000. Worklists for Quality Issues and Activities Define Access to 1. functions in the Master Data Governance component are used: Key mapping Value mapping Prerequisites You have activated the business function MDG_FOUNDATION. Provider of list agency ID: We recommend that you specify the local system with its logical systems. you can store a mapping. for example. The ID mapping is done between the source system and the reference system specified for the respective object type. PUBLIC © 2014 SAP SE or an SAP affiliate company. To check whether a mapping to the reference system was done. you can store a mapping in Customizing. the value from the reference system is displayed in QIM. Make the following settings for each object type in Customizing for QIM under Basic Settings Generic Settings for Reference Objects Define Object Access : Reference system: The values from the other systems are mapped to this system. These changes can be made at different levels with different ranges of coverage: Personalization: Only visible for the respective user Customizing: Visible throughout the client Configuration: Visible throughout the system For more information. For more information. customizing.1 Adaptation of the Role Menu PUBLIC © 2014 SAP SE or an SAP affiliate company. for example. 7. More Information Web Dynpro Personalization and Customizing Web Dynpro Configuration 1. System Administration) You can change the SAP QIM work center using the functions of the Web Dynpro ABAP Page Builder. You can change these launchpad link lists in Customizing. You assign the application configuration in Customizing for QIM under Issue Processing Define Issue Types in the Configuration ID field. various wizards are available in Customizing for QIM under Start QIM Customizing Wizards . Also. Home. see Adaptation of the Web Applications in QIM.9. texts for object types. you can hide whole steps. you can add new functions such as a new status. Assign the RFC connections to the logical systems. Ensure that the user who is stored in the RFC connection has authorization to access the objects in the source system. under HTTP Connections to ABAP System (connection type H). 1. create an RFC connection with the same name plus the suffix _HTTP for all source systems. see User Status. see Adaptation of the QIM Work Centers. For more information. Redefine terminology You can adapt messages. Features The following adaptations are possible: Change navigation structure You can change the appearance of the navigation structure by adapting the role menu in the transaction PFCG.9 User Interface Adaptation You can adapt the user interface at different levels to the requirements of your enterprise. For more information. also create RFC destinations with connection type 3. There. for example. For example. 6. You do this in the Customizing activities for object access in SAP QIM: Reference objects: Basic Settings Generic Settings for Reference Objects Define Object Access Worklists: Worklists for Quality Issues and Activities Define Access to <Object> In the system-dependent settings for an object category. All rights reserved. For more information. For more information. see the documentation for NetWeaver AS ABAP under Utilizing the Help Center for SAP Business Suite Applications. For more information.For all source systems that you want to connect to the QIM system. Adapt work center pages (for example. enter the logical systems from which the respective object is to be read and then set the Active indicator. Note To support you with setting up the system connections. Link to help documents You can create links to your own documents via the Help Center. The changes can also be made at different adaptation levels (personalization. you select the logical system and choose Standard BAPI Destination . 5. Change applications for processing issues and activities You can change the Web applications by hiding individual fields or whole blocks or specifying default values. and interface texts to the terminology commonly used in your enterprise. In the configuration. Allow access to other applications Many applications in SAP QIM are made available via CHIPs of the type launchpad link list . Specify which object is to be read from which system. you can access the relevant information in the settings for the object category by choosing ( Implementation Information ). This is required to call applications via object-based navigation. delete. In the guided application. configuration). see Terminology Redefinition. see Launchpads in QIM. the underlying RFCs must be stored in the authorization object S_RFC. you can also make context-based adaptations and thus display the same application differently for the issue driver and the issue submitter. For more information. see Adaptation of the Role Menu. This allows you to vary the user interface for the processing of issues of an issue type without context-based adaptations. Change layout of worklists You can change the layout of the worklist page overall and also change the layout of each individual list of worklists. An icon shows whether the QIM system supports access to the specified logical system. Page 51 of 106 . Create user statuses Using additional pushbuttons. You do this in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Communication Determine RFC Destinations for Method Calls . see the various Customizing activities for object access in Customizing for QIM: Reference objects: Basic Settings Generic Settings for Reference Objects Define Object Access Worklists: Worklists for Quality Issues and Activities Define Access to <Object> In the respective Customizing activity. or add individual blocks (CHIPs). For information about which RFCs are relevant for which object. see Layout. you can move. In addition to object-specific authorizations. Assign issue type-specific application configuration You can assign a specific application configuration to an issue type. 2 Adaptation of the QIM Work Centers The work centers serve as a central point of access for different tasks that can be performed in QIM. This structure can be adapted to fulfill the requirements of your enterprise and of each individual user. Technically. Features For general information about the functional scope of launchpad link lists. CHIPs of the type launchpad link list serve to call up applications or reports. All rights reserved. Environment Set More Information Launchpads 1. You do this in Customizing for QIM under Up Launchpads . you also find information about how to embed additional launchpads. 1.9. More Information Web Dynpro Personalization and Customizing Web Dynpro Configuration 1. customizing. Activities Changes can be made to the work centers with different ranges of coverage: Users in an enterprise can adapt the work centers to their own needs by moving. or adding CHIPs using the Personalization function. Administrators can adapt the work centers for the whole client (using Customizing) or for the whole system (using Configuration).9. Activities You can specify centrally which applications are to be made available to the users for selection. They help to structure your work. For more information. see the documentation for Web Dynpro ABAP Page Builder under Launchpad Link List.SAP NetWeaver Business Client (NWBC) is the user interface for SAP QIM. they are page configurations of the Web Dynpro component WDR_CHIP_PAGE. You can also make further changes via an entry in the role menu in the transaction PFCG by starting personalization. In NWBC.3 Adaptation of the Web Applications in QIM PUBLIC © 2014 SAP SE or an SAP affiliate company. Via these launchpads.1 Launchpads in QIM Various CHIPs of the type launchpad link list are integrated in the work centers. the users have access to different applications that are relevant for QIM. the menu for a role that is stored in the transaction PFCG determines the navigation structure and the call of other applications via object-based navigation (OBN). If changes to a work center are delivered and these are to be made visible. in the System Administration Work Center.2. choose Details in the context menu of a node. This creates a user-specific copy of the work center. For more information. see Web Dynpro Configuration. In the documentation for this Customizing activity. see the documentation for NWBC under 5 Role Maintenance in PFCG. users can also make settings via the menu of the CHIP. They include NetWeaver CHIPs of different types. You can also make settings for CHIPs of the type launchpad link list centrally in Customizing for QIM (see Launchpads in QIM). Page 52 of 106 . Features The work centers in QIM are defined as pages in the Web Dynpro ABAP Page Builder. the users must reset their personalized copies to the default using the appropriate pushbutton. Features For detailed information about the interaction between the settings in the transaction PFCG and the display in NWBC. Note The documentation for NWBC exists in English only. for example.9. see the documentation for Web Dynpro ABAP Page Builder under Creating Mashups with the Page Builder. To do this. or configuration. deleting. Depending on the type of CHIP. The applications in QIM with which you can process issues or activities are based on various floorplans of the Floorplan Manager for Web Dynpro ABAP (FPM). other adaptations are possible. 1. you must integrate the new codes or text types in the respective feeder parameters for the FPM configuration. Page 53 of 106 . Note If you want to include additional fields for new quantity codes. for example. processing. change the sequence of the blocks. dependent on specific parameters (adaptation dimensions) such as the partner role or the issue type.1 Context-Based Adaptation of QIM Web Applications You can adapt the applications for displaying. display) in Customizing without having to directly change the interface. You can find general information about context-based adaptations in the SAP NetWeaver documentation about Floorplan Manager under Context-Based Adaptations (CBAs). Depending on the floorplan. Here. In customizing. The adaptation schema QIM_ADAPT is relevant for the overview page for issues and 8D problem analyses. and for displaying or changing an issue or activity are based on the Floorplan for the Overview Page (OVP). You can add help texts for Web Dynpro applications to all applications. you can hide individual fields or default values. More Information As well as the general Web Dynpro functions. you can hide individual steps or change the sequence of the steps. Configuration More extensive adaptations are possible by configuration in the Flexible User Interface Designer (FLUID) of the Floorplan Manager: The application for the guided creation of an issue is based on the Floorplan for Guided Activity (GAF) in FPM. Example You can provide a restricted user interface to a user that has the partner role Interested Party . For more information about the procedure. end users can use personalization and administrators can use customizing to make changes at field level. The following table shows in PUBLIC © 2014 SAP SE or an SAP affiliate company. required entry field. various adaptations are possible. for example. for different partner roles in QIM. note that you should not add any unnecessary codes or text types to the feeder parameters.3. Here. Features Personalization and Customizing In all applications.9. or text types on the interface. see the documentation for Web Dynpro ABAP under Personalization and Customizing. Using context-based adaptations (CBAs) in the Floorplan Manager. For example. The applications for advanced creation and quick creation of an issue. To improve the performance of the Web application. see Web Dynpro Configuration. In addition to these adaptations to the user interface. and advanced creation of issues and activities based on context. timepoint codes. Note You can also store a default value for the source system of reference objects in the user master record under the user parameter /IAM/DEF_SRC_SYSTEM. see Adaptation Using Field Control. you can also extend the functionality of the QIM applications by defining a user status. you can hide individual assignment blocks. For more information. The delivered adaptation schemas each include different adaptation dimensions. that is. for example. the addition of decorative UI elements. Features Content-based adaptations are possible in the UIBB component configurations for the following application configurations: QIM_OVP_ISSUE: Overview page (OVP) for issues QIM_OVP_8DISS: Overview page for 8D problem analyses QIM_OVP_ACTIVITY: Overview page (OVP) for activities The possible adaptation dimensions are stored in different adaptation schemas. or display them in stacked form (also possible in personalization). All rights reserved. For more information. for example. you can create different configurations. Field Control You can control attributes for individual fields (for example. for example. you have the option of adapting QIM-specific terminology by making settings for terminology redefinition in Customizing for QIM. Some of the included dimensions can be used for the UIBBs for processing the issue or problem analysis itself and some for the UIBBs for processing the corresponding activities. for example. DEP_OBJ_TY Object type - - ACT_W_TMPL With template? Activity details (all tabs. Overview. date. Business Partners. Attachments) ACT_FOA Follow-up action? USER_ROLE Partner role code ACTHD_TYPE Activity type header ACTHDWTMPL Template? header ACTHD_CAT Activity category header ACTHD_FOA Follow-up action? header AHD_PROC Activity processor header _TAB and QIM_OVPH_ACTIVITY_ACTIVIT Y_TAB Activity data (including header data All (QIM_OVP_ACTIVITY_CC and Can also be set as an application in overview and partner.D7 0}_ACTIVITY_TAB) ISS_APPR Approval required Issue data/activity data All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lowerlevel UIBBs) USER_ROLE Partner role code Issue data/activity data All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lower- Can also be set as an application parameter in the PFCG role. Reference Objects.detail which dimension of the adaptation schema QIM_ADAPT is relevant for what: Dimension Description Use UIBB Level Comment ISSUE_TYPE Issue type Issue data/activity data All (QIM_OVP_ISSUE_CC and Can also be set as an application parameter in the PFCG role. you must first specify parameter values yourself. lower-level UIBBs) reference objects. Overview. Overview. QIM_OVPH_ISSUE_ACTIVITY_T AB. Reference Objects. for example. Attachments) UIBBs for activity data. Business Partners.D60. To use it. Attachments) example. Reference Objects. Is not currently used in QIM. level UIBBs) DSIGN_CD Issue with digital signature Issue data/activity data All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lowerlevel UIBBs) ACT_DS_CD Activity with digital signature Activity details (all tabs. QIM_OVP_8DISS_CC and lowerlevel UIBBs) ISSUE_HIER Hierarchy type Issue data/activity data All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lower- Is not filled by the application. Attachments) UIBBs for activity data. level UIBBs) ISS_CAT Issue category Issue data/activity data All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lower- Can also be set as an application parameter in the PFCG role. so can only be set as an application level UIBBs) parameter in the PFCG role. attachments for activity) Note PUBLIC © 2014 SAP SE or an SAP affiliate company. Business Partners. QIM_OVP_ACTIVITY_ACTIVITY ACT_CAT Activity category Details of subactivities (all tabs. for example. or QIM_OVP_8DISS_{D50. for example. All rights reserved.D60. all UIBBs for tabs within QIM_OVP_ISSUE_ACTIVITY_TA B. for Can also be set as an application example. Business Partners. all UIBBs for tabs within parameter in the PFCG role. for example. QIM_OVPH_ISSUE_ACTIVITY_T AB. for UIBBs for activity data.D60. or QIM_OVP_8DISS_{D50. Page 54 of 106 . or QIM_OVP_8DISS_{D50. parameter in the PFCG role. all UIBBs for tabs within QIM_OVP_ISSUE_ACTIVITY_TA B. for example. Overview. Some of the included dimensions relate to the activity in the header. some to the subactivities. The following table shows in detail which dimension of the adaptation schema QIM_AADAPT is relevant for what: Dimension Description Use UIBB Level Comment ACT_TYPE Activity type ACT_W_TMPL With template? UIBBs for activity data. all UIBBs for tabs within QIM_OVP_ISSUE_ACTIVITY_TA B. Reference Objects. QIM_OVPH_ISSUE_ACTIVITY_T AB.D7 0}_ACTIVITY_TAB) ACT_CAT Activity category Activity details (all tabs.D7 0}_ACTIVITY_TAB) ISS_STATUS Issue status Issue data/activity data All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lowerlevel UIBBs) The adaptation schema QIM_AADAPT is relevant for the overview page for activities. that another field has a specific value. You can either specify the field attributes statically or determine them dynamically depending on certain conditions. the status of the digital signature is only visible for these issues. The dimensions are displayed in the table in the upper screen area. you can also include these as modifiable or influencing fields in field control. For each modifiable field. 5. for issues for which a digital signature is required. Open the ABAP Workbench (transaction SE80). and interface texts to the terminology commonly used in your enterprise. Open the component configuration for the UIBB whose adaptations you want to display. If you have defined your own fields in the customer namespace. you want to PUBLIC © 2014 SAP SE or an SAP affiliate company. the user interface was simplified to allow these users to focus on processing. Also note that the adaptation dimensions expand themselves exponentially. Open the component configuration QIM_OVP_ACTIVITY_CC or QIM_OVP_ISSUE_CC or QIM_OVP_8DISS_CC. Page 55 of 106 . Example Context-based adaptations are delivered for various simplifications of the user interface. Features In field control. If. the respective field with the approval status is only displayed for issues for which an approval is required. for example. technical information such as the code group and code are invisible for the activity processor. no influence on the interface is necessary using context-based adaptations (CBAs) of the Web Dynpro applications. open the Web Dynpro application configuration QIM_OVP_ACTIVITY or QIM_OVP_ISSUE or QIM_OVP_8DISS. 7. Activities For information about how you set up field control.3. choose the pushbutton with the quick info Adaptations & Comparisons . Therefore if you set a parameter for each of several dimensions. 1.Make sure that you only use the respective matching dimensions in the different UIBBs. You can use all other adaptation dimensions only for the adaptation of lower-level UIBBs. At lower level. Some examples are described below. texts for redefinition object types. Activity Processing For users with the partner role Activity Processor (PROCSSR). Activities To display or create an adaptation. you can specify which influencing fields have control. for example. 8. This is achieved. This is done in an adaptation of the component configuration QIM_OVP_ACTIVITY_CC that forms the framework for the overview page. on the detailed screen of the activity to be processed (in the UIBB QIM_OVP_ACTIVITY_OVERVIEW_FORM). As field control directly affects the BOPF node. Choose Display Configuration . 4. which do not necessarily have to be visible on the user interface. The reason for this is that. additional programming is necessary even at this level.9. 2. If you select an existing adaptation. 1. Similarly. you must also define a component configuration for adaptation for each possible combination. 6.9. Integration Field control is available for the applications for processing issues and activities. see Customizing for QIM under Environment Define Field Control . only an adaptation on the basis of the adaptation dimension Partner role is possible at this upper level. select the base configuration or an existing adaptation and choose Add . for example. To create a new adaptation. in addition to the adaptation. for the adaptation dimension Template? header . All rights reserved. In the package QAM_UI. for example. A condition could be. There are other adaptations in the UIBB QIM_OVP_ACTIVITY_OVERVIEW_FORM. for example. proceed as follows: 1. there is a distinction between modifiable and influencing fields. by hiding the activity hierarchy. To display the possible adaptation dimensions and the existing adaptations. Control is exercised by the influencing fields. which was only implemented for the partner role.4 Terminology Redefinition You can adapt messages. Note In QIM.2 Adaptation Using Field Control You can adapt the attributes for individual fields and thus display them as required entry fields or in display mode. 3. Issue Processing On the detailed screen for the issue being processed (in the UIBB QIM_OVP_ISSUE_OVERVIEW_FORM). the adapted component configuration is displayed in the lower screen area. The modifiable fields are visible on the user interface and can be influenced by field control. Only for activities with a template are the fields with detailed information about the template visible on the user interface. 3. Use the where-used list to display all the places where the OTR alias you want to replace is used. store the values that the status can have. To do this.use a different term instead of quality issue . Enhance the business object in the enhancement browser of the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). object type ITY for the issue type. You set up terminology redefinition in Customizing for QIM under Environment Redefine Terminology . Copy the data type in the transaction SE11 and make your changes. Open the generated enhancement. Activities To define a user status. you must replace the alias name there manually. you can replace this term at the specified places. which reads out the user status. Under Value Range . 2. Features Messages You can copy the messages for the QIM applications and QIM Customizing used in the standard system and adapt them to your terminology. Example When processing an activity. proceed as follows: 1. create the append structure for the BOPF enhancement structure /IAM/INCL_EEW_ACT_ROOT. for example. Create a status variable in the Data Dictionary (DDIC. Create an append structure and add the data element you created to it: If the status variable is to apply to an issue. by displaying the user status in the worklist. Page 56 of 106 .9. If the status variable is to apply to an activity. This means you can enhance the control of business processes by the system statuses by including a user status. You can have the user status set manually by the user or by a BOPF action. This provides you with a flexible method for implementing a user status and running reports with it without modification. you must only enter the new text under the respective number. 1. Interface Texts You can replace texts on the interface that are technically stored in the online text repository (OTR) with an OTR alias in the packages /IAM/UI or QAM_UI (or subpackages) with your own OTR texts. Create an enhancement for the business object for which you want to define the status: /IAM/ISSUE: Quality issue /IAM/ACTIVITY: Quality activity The system generates the enhancement according to your entries in the wizard and creates a corresponding node beneath the business object. you can add a selection list that is used to prompt for approval by the board. All rights reserved. You can use the input help to find out which data type corresponds to the object type. Redefinition Object Types You can change texts for many DDIC data types (structures or data elements). in Customizing for terminology redefinition select the corresponding object type using the input help. transaction SE11).5 User Status You can add your own customer-specific user status to the applications for creating and processing issues and activities. The following QIM message classes are relevant for this: /IAM/OBJECT: Messages that are relevant when creating issues and activities /IAM/CONFIG: Messages that are relevant within QIM Customizing To do this. If the text is also used directly in a Web Dynpro configuration. You can also use the user status to control a delivered system status if you define a validation action in BOPF for the standard action of the system status. You recognize OTR texts in a Web Dynpro configuration by their prefix $OTR:. PUBLIC © 2014 SAP SE or an SAP affiliate company. Create a new OTR alias and save the assignment to the alias that is to be replaced in Customizing for terminology redefinition. 1. create your own message class and save this in QIM Customizing for terminology redefinition. In your message class. Parameters 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 1. 2. Create a data element to which you assign this domain. which can be set in addition to the delivered system statuses. Features You can implement a user status using the extensive options available in Web Dynpro configuration and by changes in the Business Object Processing Framework (BOPF). first create a domain in Character String (CHAR) format with a length of 2 characters. To do this. you can create different variants of the terminology redefinition and then store them as user parameters in the user master record or as application parameters in the role. 2. create the append structure for the BOPF enhancement structure /IAM/INCL_EEW_I_ROOT. Then enter the copy with your changes in Customizing. Here. use the prefix I_ for issues and A_ for activities.6 Web Dynpro Personalization and Customizing In the Web Dynpro environment. Page 57 of 106 . open the Web Dynpro application configuration and choose Web Dynpro Configuration Test Execute in Administration Mode . which you access in Customizing under Cross-Application Components Processes and Tools for Enterprise Applications Enterprise Services Enhance Enterprise Services Extend Mappings Extend Mappings : Mapping QAM_QI_QI for issues Mapping QAM_QA_QA for activities Enhance one of the following mapping steps in the field mapping to include a new field relationship: Issues: Mapping step ISSUE_TO_GQI. followed by the action that you created in BOPF. see: Adaptation of the QIM Work Centers Adaptation of the Web Applications in QIM For general information about the adaptation of Web Dynpro applications. Create actions for the status change by choosing Create Action in the context menu for the ROOT node. Use the delivered action CHECK_ACTION_ATTACHMENT_AUTH for the business object /IAM/ISSUE as a guide. More Information The configuration framework also allows the configuration of Web Dynpro applications or pages for more extensive adaptations by an administrator or developer (see Web Dynpro Configuration).7 Web Dynpro Configuration PUBLIC © 2014 SAP SE or an SAP affiliate company. To activate the digital signature. create a determination for the ROOT node. Which settings exactly are possible depends on whether a page (for example. 5. Include the user status in the worklist. For the FPM event ID. create an append structure for the corresponding delivered structure in the transaction SE11: QAMS_GQI_ATTRIBUTE for issues QAMS_GQA_ATTRIBUTE for activities Use the same component name as for the append structure for the BOPF structure (see step 1. the text is displayed immediately on the interface. Customizing is done by an administrator with the appropriate authorization and is for the whole client in a system. by graying out an option). For the determination pattern.3. you can only use the digital signature for a BOPF action without a parameter structure. If the user status is only to be changed by actions. choose the option Create Properties . change the layout and display the field for the user status. 2. for example. Check first in the class documentation whether the business logic suits your requirements: Class: /IAM/CL_SET_USER_STATUS Parameter structure: /IAM/S_SET_USER_STATUS 4. For more information. You can attach a digital signature to a user status. If you use the delivered class /IAM/CL_SET_USER_STATUS in the action. transformation 00001 Field relationship QAMS_QGI_ATTRIBUTE-<user status field> to QAMIS_ISSUE_MAP-<user status field> Activities: Mapping step ACTIVITY_2_GQA. Optional (programming required): If you want to prevent the execution of a standard action using a user status. 4. use Customizing to include it in the Web Dynpro application configuration or component configuration. In the worklist. If you want to include the user status as a selection list. 3. To visualize the user status and execute actions. fill the event parameters according to the parameter structure /IAM/S_SET_USER_STATUS. Enhance the structure mapping in the Service Mapping Tool. The basis for this is the Web Dynpro ABAP configuration framework. Example For a board approval. create an action validation for the standard action. Insert pushbuttons for the status change in Customizing mode. Note For technical reasons. To do this. a work center) or an application is to be adapted. 4. 1. transformation 00001 Field relationship QAMS_QGA_ATTRIBUTE-<user status field> to QAMAS_ACTIVITY_MAP-<user status field> 3.9. 5. it is possible using personalization and customizing to edit the interface directly when you call an application or a page. Features Personalization is done by individual users. store the BOPF action you created as a business transaction.9. see the documentation for Web Dynpro ABAP under Personalization and Customizing. Optional (programming required): If you want to indicate visually whether a status change is possible on the user interface (for example. you can create the following actions: Change from initial value to To Be Approved by Board Change from To Be Approved by Board to Approved by Board Change from To Be Approved by Board to Rejected by Board Here you can use the following delivered class and parameter structure. In the ABAP Workbench (transaction SE80). The adaptations are only relevant for these users. include the status field as read-only.3 above). 3. 1. You do this in the transaction SM30 via the following views: Quality issues: /IAM/V_I_ACT_DS Quality activities: /IAM/V_A_ACT_DS 1. 2. All rights reserved. 1. Use the delivered determination SET_DYNAMIC_ROOT_PROPERTIES as a guide. QIM Support &ndash. for use in NWBC. create RFC destinations for the systems in which the reports are located. For general information about the configuration of Web Dynpro components and applications.10 Roles in SAP Quality Issue Management To allow task-specific access to the applications in SAP Quality Issue Management. you must upload them to the portal (see Generation of Portal Roles). Also. see the documentation for Web Dynpro ABAP under Configuration. BRFplus. The role includes all available authorization profiles for executing Web Dynpro ABAP-based applications and the work center for system administration. Implementation Considerations You make the settings for the roles in the transaction PFCG. If you want to configure pages. see the documentation for the respective component. also create RFC destinations with connection type 3. In a role. but is only for the display of information within the scope of support. for example. you can use the functions of the Floorplan Manager for Web Dynpro ABAP. you can assign different roles to the employees in your enterprise. To call reports in the Reports work center. use the Web Dynpro ABAP Page Builder. For more information about the Page Builder. and authorizations for access are specified. The exception to this is the work center for system administration. Enterprise Search. are possible. and pages.12 Object-Based Navigation (OBN).7 Web Dynpro Configuration By configuration of Web Dynpro components. All rights reserved. For more information. note that the entries in the transaction PFCG must match the OBN parameters under Other Node Details and the following entries in Customizing for QIM for jumps: Basic Settings Generic Settings for Reference Objects Define Details for Jump to Linked Applications Worklists for Quality Issues and Activities Define Details for Jump to Linked Applications The system alias that is stored in the Customizing activities for a jump must also be assigned to the parameter portal_bo_alias in the corresponding OBN entry in the transaction PFCG. see the documentation for NWBC under: 5. General Settings Configure the following RFC connections in the transaction SM59: Under ABAP Connections .11 Remote Systems 5. that is the arrangement of the work centers. the configurator. Note that you may require other authorizations stored in roles for those components that are reused in SAP QIM. The following roles are delivered in the standard system with SAP QIM: Role Use Coordinator SAP_QIM_COORDINATOR Employees who are assigned this role have comprehensive authorizations in SAP Quality Issue Management. major adaptations to the user interface in the development environment. PUBLIC © 2014 SAP SE or an SAP affiliate company. To be able to use the roles in the portal as well. Master Data Governance. 1. Features Which functions exactly are available depends on whether you want to adapt a page (for example. see Reports. see the documentation under Creating Mashups with the Page Builder. You can assign the following system aliases in these places: SAP_QIM for the system in which SAP QIM itself is installed SAP_IAM for the systems that are used from SAP QIM More Information For more information.1. This assignment guarantees the call of the actual system. Business Context Viewer. display authorizations only SAP_QIM_SUPPORT The QIM Support role is not intended as an operational role for SAP QIM users. For more information. applications. create an RFC connection with the same name plus the suffix _HTTP for all source systems. You can use the roles in SAP NetWeaver Business Client (NWBC) and SAP NetWeaver Portal. Issue Driver SAP_QIM_ISSUE_DRIVER Employees who are assigned this role have all necessary authorizations for executing Web Dynpro ABAP-based applications in SAP Quality Issue Management. Page 58 of 106 . Adaptations made by configuration are visible throughout the system. For all source systems that you want to connect to the QIM system. a work center) or an application. This is required to call applications via object-based navigation.9. If you want to adapt an application. however. under HTTP Connections to ABAP System (connection type H). create an RFC destination for the local QIM system with the connection type 3. Notes on Object-Based Navigation When you make new entries for object-based navigation (OBN). The definition of the delivered PFCG roles is. the navigation structure. for example. codes.10. Activities In detail. Reports and queries are available to support the coordinator in fulfilling his or her tasks. or configuring access to other systems. The issue driver documents the overall resolution and completes the process. partners. or activities. the issue driver is responsible for the following tasks: Analyzing and tracking his or her own quality issues with the aid of the worklists for quality issues and quality activities across all systems Coordinating the quality activities for a quality issue Assigning partners to a quality issue Providing additional information about a quality issue Creating new quality issues Completing and validating a quality issue Integration In addition to this role. see Generation of Portal Roles. see Generation of Portal Roles. For more information. Activities In detail. for change requests and activities in the SAP Management of Change application.10. the role of Coordinator is also relevant for SAP Quality Issue Management. 1. For more information. The issue driver typically reviews the status of the issue when the activities related to it are set in process or completed. so that all data required for its subsequent resolution process is available and all partners are clearly defined.Note The documentation for NWBC exists in English only. and triggers workflow processes for distinct steps by. the coordinator can access audit trail transactions to be able to track all changes in the SAP QIM system. assigning additional or different partners. derives follow-up actions.3 Authorizations The authorizations for executing functions in SAP QIM are specified in the roles in the transaction PFCG.10.1 Coordinator Role: SAP_QIM_COORDINATOR The main task of the coordinator in SAP Quality Issue Management (SAP QIM) is to track and coordinate the processing of quality issues and the related quality activities. adds additional information. if possible. SAP QIM adheres to the standard AS ABAP authorization concept.2 Issue Driver Role: SAP_QIM_ISSUE_DRIVER The task of the issue driver in SAP Quality Issue Management is to process a quality issue and initiate appropriate quality activities. Page 59 of 106 . Coordinators also act as power users by managing settings in productive systems. Integration The authorization objects are located in the IAM layer and are also used for objects that do not belong to SAP QIM. and activities Integration In addition to this role. 1. 1. All rights reserved. setting up business rules for the automatic determination of partners. Within the scope of compliance coordination. Both roles can be used in SAP NetWeaver Business Client and in SAP NetWeaver Enterprise Portal. for example. Both roles can be used in SAP NetWeaver Business Client and in SAP NetWeaver Enterprise Portal. such as adding codes. Then the issue driver sets the issue in process and thus triggers the resolution process and the workflows connected with it. The coordinator analyzes existing content. the coordinator is responsible for the following tasks: Analyzing and tracking the worklists for quality issues and quality activities across all systems Coordinating the quality activities Assigning partners or processors to a quality issue Providing additional information about individual quality issues Creating new quality issues Completing and validating a quality issue Managing and changing system settings (without transport) Managing and editing decision tables for the rule-based determination of codes. the role of Issue Driver is also relevant for SAP Quality Issue Management. The coordinator also checks the overall progress of the resolution of an issue. PUBLIC © 2014 SAP SE or an SAP affiliate company. the issue driver checks the content of an incoming issue and adds more information to it. To do this. All rights reserved. You can use the Business Add-In (BAdI) /IAM/BADI_ISSUE_AUTHORITY to extend the authorizations of individual users. In many authorization objects.11 System Architecture SAP QIM uses various different generic tools that are part of different software components.Features The following authorization objects are delivered with SAP QIM (object class IAM): Authorization Object Name IAM_CAT_AC Authorization object to restrict access to QIM worklist object /IAM/IAUTH Authorization object for issue/change request /IAM/AAUTH Authorization object for activity /IAM/ATTMT Authorization object for attachments for issue/change request/activity IAM/I_RLCD Authorization object for role codes for issue/change request IAM/A_RLCD Authorization object for role codes for activity IAM/A_ATTR Authorization object for attribute maintenance for activity /IAM/TXTTY Authorization object for descriptions IAM_CODEGR Authorization object for code groups IAM/I_STAT Authorization object for lifecycle status for issue/change request IAM/A_STAT Authorization object for lifecycle status for activity /IAM/OREF Authorization object for reference objects for issue/change request/activity /IAM/CODGR Authorization object for selection of code groups/codes IAM/CHGLOG Authorization object for change log in IAM Note Note that the authorization object /IAM/IAUTH includes the Reported By field. For information about the upload tool. In the portal. This Business Package includes the business objects necessary for navigation. The business content lies in the software components IAM and QAM. During generation of the roles. the following systems must be available with their respective assigned system aliases: The QIM system must be available and have the system alias SAP_QIM assigned. the corresponding systems must be available and the system aliases SAP_BW or SAP_QualityManagement must be assigned. Structure PUBLIC © 2014 SAP SE or an SAP affiliate company. One of the SAP ERP systems that is connected to the QIM system must have the system alias SAP_ECC_IAM assigned. You set up authorization groups in Customizing for QIM under Environment Define Authorization Groups for Issues/Activities . the corresponding portal roles are generated automatically. By doing this. To call the delivered reports (see Reports).4 Generation of Portal Roles If you want to use the PFCG roles in SAP NetWeaver Portal. The portal component BP ERP05 COMMON PARTS 1. you can set the authorization dependent on an authorization group. 1. You can find the names of the logical systems in QIM Customizing for access to the respective object under the System-Dependent Settings node. see the documentation for the BAdI in Customizing for QIM under Environment BAdI: Enhanced Authorization Check for Issues/Activities . checks are made for which these placeholder entries are necessary. see SAP Note 1685257 and the documentation for the portal under Upload of Roles from ABAP-Based Systems. Activities Upload the PFCG roles to the portal with the role upload tool. you must upload the roles to the portal. Technical checks are made using this system when the roles are generated.61 SP03 (Business Package for Common Parts) must be installed. Page 60 of 106 .10. The authorization groups are used to map organizational units in your enterprise. For more information. Each system that you connected to the QIM system via system integration must be available in the portal and have a system alias assigned that corresponds to the name of the assigned logical system. make sure that only data is stored in this field that is not subject to additional confidentiality. 1. Within your organization. Prerequisites Make sure that the placeholder SAP_ECC_IAM is stored in the transaction PFCG in the role menu under Other Node Details in the Target System field for the entries that refer to other SAP ERP systems. All rights reserved. Page 61 of 106 .Below is a list of the software components required for SAP QIM with their most important tools or content objects: SAP NetWeaver Application Server ABAP (software components SAP_BASIS and PI_BASIS) Web Dynpro ABAP Framework Floorplan Manager (FPM) for the user interface of Web Dynpro applications Page Builder and Launchpad for navigation pages Personal Object Worklist (POWL) for worklists Operational Search and Analytics for Enterprise Search and reports Status and Action Management (S&AM) Archive Development Kit (ADK) for data archiving Adobe Document Services (ADS) for printing PDF-based forms TREX as search engine Knowledge Provider (KPro) to connect a content management system for attachments (documents and links) General services (software component SAP_ABA) SAP business partner SAP Web UI Framework (software component WEBCUIF) Business object layer (BOL) and generic interaction layer (genIL) as the link between business object logic and remote APIs to external data SAP Business Suite Foundation (software component SAP_BS_FND) Business Object Processing Framework (BOPF) for object modeling Business Context Viewer (BCV) for reports Business Rule Framework plus (BRFplus) for rule-based determinations Master Data Governance (MDG) for ID mapping Issue and Activity Management (software component IAM) Business objects /IAM/ISSUE and /IAM/ACTIVITY in BOPF FPM feeder classes Object types and object type configurations for reference objects Quality Issue Management (software component QAM) Web Dynpro applications and application configurations POWL queries BCV queries Search models Object types and object type configurations for worklists SAP NetWeaver Business Client (NWBC) as UI client The following diagram shows a graphical representation of this system architecture: System Architecture of SAP QIM Other Optional Components Portal as alternative UI client SAP Information Lifecycle Management (ILM) to define rules for data archiving and data destruction PUBLIC © 2014 SAP SE or an SAP affiliate company. For more information. SAP NetWeaver provides a technical infrastructure that supports and harmonizes data provisioning for analytics and also for searching data. In a commonly used modeling environment. In the documentation for the individual Customizing activities. More Information In addition to this basic configuration. 16. 15. see Settings Dependent on the Text Type. activities. 10. and code groups. Optional: Copy over the delivered Customizing settings for SAP QIM by activating the corresponding BC Sets. You have then made all the necessary settings in the system for the predefined standard processes. 1. Search and Operational Analytics therefore provides the prerequisites for mapping search and analysis scenarios for QIM data. Optional: For the rule-based determination of partners. codes. You access the wizard in Customizing for QIM under Start QIM Customizing Wizards . You do this in Customizing for QIM under Activate BC Sets for QIM . Optional: If you want to use Enterprise Search to search for issues. Alternatively. Optional: Make the settings for priorities and criticalities in Customizing for QIM under Issue Processing Urgency . Optional: Set up the rules for activity determination with BRFplus. quantity codes. 19. Optional: Make the settings for follow-up actions in Customizing for QIM under Issue Processing Define Follow-Up Actions . Make the settings for printing and e-mailing issues and activities in Customizing for QIM under Issue Processing . with the exception of the access to remote systems. work through the process as detailed below. 1. Optional: Make the settings for text types in Customizing for QIM under Basic Settings Text Types . search and analytics models are made available for this. For more information. 6. 11. Make the settings for issue types in Customizing for QIM under Issue Processing Define Issue Types .1. see Setting Up System Connections. you will find information about the exact procedures. 14. 18. For more information. see Customizing for QIM under Search and Analytics . you can also make more major adaptations and. In this Customizing section. Make the settings for codes and code groups in Customizing for QIM under Issue Processing Codes . You do this in Customizing for QIM under Basic Settings Generic Settings for Reference Objects Define Object Access . you can use Business Rule Framework plus (BRFplus). Make the settings for document management in Customizing for QIM under Basic Settings Attachments Define Document Types and Document Schemas . PUBLIC © 2014 SAP SE or an SAP affiliate company. you can make the settings using the respective QIM Customizing wizard. Prerequisites For information about the necessary Customizing settings. and issue types in Customizing for QIM under Worklists for Quality Issues and Activities . Make the settings for access to the reference objects for an issue or activity. and timepoints in Customizing for QIM under Basic Settings . 7. Create partner roles in Customizing for QIM under Issue Processing Partners . Make the settings for activity templates in Customizing for QIM under Issue Processing Define Activity Templates . For more information. see Configure Rules. 13. 4. 8. In particular. Integration The content objects delivered for SAP QIM are in the software components IAM and QAM. particularly for access to issues. you must create and index connectors for the search and analytics models supplied. Features In this documentation structure. adapt the user interface (see User Interface Adaptation) or define other reference objects. Page 62 of 106 . Optional steps are indicated accordingly. Configure the system connections to the remote systems that you want to connect to SAP QIM. 12. Make the settings for activity types in Customizing for QIM under Issue Processing Define Activity Types . 17. 2. Assign the document schema to the issue and activity categories in Customizing for QIM under Issue Processing . see Determination of Activities Using BRFplus. Make the settings for number range intervals. you will find detailed technical information about the content objects delivered. For more information. you can adapt the delivered settings to suit your requirements.13 Search and Operational Analytics: Content for SAP QIM With Search and Operational Analytics. see Customizing for QIM under Search and Analytics Configure Search and Search and Operational Analytics: Content for SAP QIM. Quality Issue Process To configure SAP QIM. All rights reserved. 3. Make the settings for the worklist. for example. 5.12 Sequence of Configuration Steps in SAP QIM You perform most of the configuration steps in the SAP Customizing Implementation Guide under Cross-Application Components Management . set up the target systems here. 9. see Printing of Issues or Activities. For more information. you also define the authorizations for access under Make Settings in POWL Cockpit . In the next stages of the configuration process. More Information Enterprise Search in SAP QIM Reports in SAP QIM 1. For more technical information about the nodes. To change the models. To search for subissues or attachments to an issue or subissue.13. All rights reserved. you require the authorizations in the role SAP_ESH_TRANSPORT. Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_I_QIM_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA.1 Issue : 0QAM_I_QIM_T01 This search and analytics model is used to search for QIM quality issues. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE. you will find information about the nodes of the search and analytics model. 1. you must have made your settings in Customizing for QIM under Configure Search .1. Page 63 of 106 .1 Search and Analytics Models You can display the search and analytics models supplied in the transaction ESH_MODELER and extend them if required. if required. Root Node: Issue Header Extraction Technical Name for Root Node QAM_I_ROOT DDIC Structure /IAM/S_ESO_I_ROOT Generally. Operational Data Provider: Issue Header Extraction Technical Name 0QAM_I_QIM ODP Semantics Master data attributes Direct Access Activated No PUBLIC © 2014 SAP SE or an SAP affiliate company. see the steps Model Nodes . you require the authorizations in the role SAP_ESH_LOCAL_ADMIN. Technical Data Model Use Application model Software Component for Search and Analytics QAM Prerequisites To use the search and analytics model for Embedded Search. Operational Data Provider in the system in the transaction ESH_MODELER. and. Node Response . use the following models: Defect Cause Effect Issue Attachment Default Request (All Response Attributes) Technical Name DEFAULT Use Attribute search Overview of the Nodes in the Model In the following sections.13. Prerequisites To display the models. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ISSUE. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QIM_OREF_T01 /IAM/OREF Authorization object for reference objects for issue/change request/activity Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QIM_OREF_T01 Analytics 0QAM_I_QIM_OREF_T01 Analytics result filter 0QAM_I_QIM_OREF_T01 Node: Issue Partner Extraction Technical Name for Node QAM_I_PARTY PUBLIC © 2014 SAP SE or an SAP affiliate company.Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QIM_IAUTH_T01 /IAM/IAUTH Authorization object for issue/change request Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QIM_IAUTH_T01 Analytics 0QAM_I_QIM_IAUTH_T01 Analytics result filter 0QAM_I_QIM_IAUTH_T01 Navigation Target Navigation Target Description Details UI Technology 0QAM_I_QIM_OVP_ISSUE_T01 Display issue Displays the issue in the QIM Web Dynpro Web Dynpro (Application Server) application Node: Issue Descriptions Extraction Technical Name for Node QAM_I_DESC DDIC Structure /IAM/S_ESO_I_DESC Generally. Page 64 of 106 . All rights reserved. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QIM_TXTTY_T01 /IAM/TXTTY Authorization object for descriptions Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QIM_TXTTY_T01 Analytics 0QAM_I_QIM_TXTTY_T01 Analytics result filter 0QAM_I_QIM_TXTTY_T01 Node: Issue Object Reference with Description Technical Name for Node QAM_I_OREF DDIC Structure /IAM/S_ESO_I_OREF Generally. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Code Node 0CODE./IAM/CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_DESC. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node PARTY of business object /IAM/ISSUE. Node: Issue Quantity Extraction Technical Name for Node QAM_I_QUANTITY DDIC Structure /IAM/S_ESO_I_QUANTITY Generally. Value Join Operator Equal Page 65 of 106 . All rights reserved./IAM/CODE_GROUP Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_DESC. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node QUANTITY of business object /IAM/ISSUE. you will find information about the node relationships of the search and analytics model. Foreign Keys Attributes of Parent Node CODE_GRP Value Attributes of Child Node CODEGROUP PUBLIC © 2014 SAP SE or an SAP affiliate company. see the step Node Relations in the system in the transaction ESH_MODELER. For more technical information about the nodes.DDIC Structure /IAM/S_ESO_I_PARTY Generally. Overview of the Node Relationships in the Model In the following sections. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE Value Join Operator Equal CODE Node Relationship: Code Group Node 0CODE_GROUP. Node Relationship: Issue Descriptions Extraction Node QAM_I_DESC Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator TYPE_CD TYPE Equal SUBTYPE_CD SUBTYPE Equal Node Relationship: Issue Partner Extraction Node QAM_I_PARTY Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Object Type Code Node 0OBJ_TYPE_CODE. All rights reserved. Page 66 of 106 ./IAM/OBJ_TYPE_CODE Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_OREF.Node Relationship: Issue Object Reference with Description Node QAM_I_OREF Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery Yes This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node Value DB_KEY Attributes of Child Node PARENT_KEY Value Join Operator Equal Node Relationship: Partner Role Code PUBLIC © 2014 SAP SE or an SAP affiliate company. Foreign Keys Attributes of Parent Node Value Attributes of Child Node TYPE_CD Value Join Operator Equal TYPE Node Relationship: Object Subtype Code Node 0OBJ_SUBTYPE_CODE./IAM/OBJ_SUBTYPE_COD Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_OREF. Foreign Keys Attributes of Parent Node Value Attributes of Child Node PARTY_ROLE_CODE Value APPLICATION Join Operator Equal PARTY_ROLE_CODE QIM Node Relationship: Issue Quantity Extraction Node QAM_I_QUANTITY Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT.Node 0PARTY_ROLE_CODE. Foreign Keys Attributes of Parent Node DB_KEY Value Attributes of Child Node Value Equal PARENT_KEY DESC_TYPE Join Operator IDESC Node Relationship: Issue Descriptions Extraction &ndash. Text Type Issue Resolution (ISOLU) Node 0QAM_I_QIM_T01. All rights reserved. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Unit of Measure Node 0UNIT_OF_MEASURE. Text Type Issue Description (IDESC) Node 0QAM_I_QIM_T01./IAM/UNIT_OF_MEASURE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QUANTITY. Foreign Keys Attributes of Parent Node Value Attributes of Child Node UNITCODE Value Join Operator Equal MSEHI Node Relationship: Issue Descriptions Extraction &ndash.QAM_I_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT. Page 67 of 106 .QAM_I_DESC PUBLIC © 2014 SAP SE or an SAP affiliate company./IAM/PARTY_ROLE_CODE Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_PARTY. Node 0QAM_I_QIM_T01.QAM_I_OREF there are multiple associations: one for each QIM object type. All rights reserved. Page 68 of 106 . Responsible Node 0QAM_I_QIM_T01. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value DESC_TYPE Join Operator Equal PARENT_KEY ISOLU Node Relationships: Issue Object Reference with Description For the node 0QAM_I_QIM_T01. Foreign Keys. Same for All Associations Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Other Foreign Keys by Association Association Attributes of Child Node Value QAM_I_ROOT2QAM_I_OREF_CUS Reference object customer TYPE_CD CUS QAM_I_ROOT2QAM_I_OREF_PLA Reference object plant TYPE_CD PLA QAM_I_ROOT2QAM_I_OREF_MAT Reference object material TYPE_CD MAT QAM_I_ROOT2QAM_I_OREF_BAT Reference object batch TYPE_CD BAT QAM_I_ROOT2QAM_I_OREF_DLV Reference object outbound delivery TYPE_CD DLV Reference object functional location TYPE_CD FL QAM_I_ROOT2QAM_I_OREF_VEN Reference object vendor TYPE_CD VEN QAM_I_ROOT2QAM_I_OREF_MAI Indicator main reference object MAIN_REF_IND X QAM_I_ROOT2QAM_I_OREF_FL Description Note Cardinality: Up to one N_IND Node Relationship: Issue Partner Extraction &ndash.QAM_I_PARTY Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT. This section describes all these associations collectively. Complaint Quantity PUBLIC © 2014 SAP SE or an SAP affiliate company. Foreign Keys Attributes of Parent Node DB_KEY Value Attributes of Child Node Value RESPONSIBLE_IND Join Operator Equal PARENT_KEY X Node Relationship: Issue Quantity Extraction &ndash.QAM_I_OREF Relationship Type Association Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT.Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT. All rights reserved. Foreign Keys Attributes of Parent Node Value Attributes of Child Node LCYCLE_CD Value Join Operator Equal KEY1 Node Relationship: Issue Type and Text Node 0ISSUE_TYPE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Equal PARENT_KEY ROLE_CD Join Operator COM Node Relationship: Authorization Group Node 0AUTH_GROUP./IAM/ISSUE_TYPE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT. Page 69 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal AUTH_GROUP AUTH_GROUP Equal Node Relationship: Lifecycle Status (Issue Status) Node 0ISS_LCYC_STAT.QAM_I_QUANTITY Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_ROOT.Node 0QAM_I_QIM_T01./IAM/AUTHORIZATION_G Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT./IAM/ISSUE_LCYCLE_ST Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal ISSUE_TYPE ISSUE_TYPE Equal Node Relationship: Priority PUBLIC © 2014 SAP SE or an SAP affiliate company. QAM_I_QEF_ROOT PUBLIC © 2014 SAP SE or an SAP affiliate company. Foreign Keys Attributes of Parent Node EFFECTIVENESS_CD Value Attributes of Child Node Value KEY1 Join Operator Equal Node Relationship: Issue Header Extraction &ndash. Page 70 of 106 .Node 0PRIORITY. Issue Category Effect Node 0QAM_I_QEF_T01. Foreign Keys Attributes of Parent Node Value Attributes of Child Node VALIDATION_CD Value Join Operator Equal KEY1 Node Relationship: Effectiveness Check Status of an Object Node 0EFFECTIVENESS_STAT./IAM/EFFECTIVENESS_C Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT./IAM/CRITICALITY Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT. All rights reserved./IAM/PRIORITY Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal PRIORITY PRIORITY Equal Node Relationship: Criticality Node 0CRITICALITY. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal CRITICALITY CRITICALITY Equal Node Relationship: Validation Status of an Object Node 0VALIDATION_STAT./IAM/VALIDATION_CD Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_ROOT. Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_I_QDF_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. To search for other issue categories or attachments to an issue or subissue.QAM_I_QDF_ROOT Relationship Type Association Cardinality Arbitrary Reverse Cardinality Up to one Subquery No This node is a subnode of the root node QAM_I_ROOT. Issue Category Cause Node 0QAM_I_QCA_T01.Relationship Type Association Cardinality Arbitrary Reverse Cardinality Up to one Subquery No This node is a subnode of the root node QAM_I_ROOT. Page 71 of 106 . use the following models: Issue Cause Effect PUBLIC © 2014 SAP SE or an SAP affiliate company. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ISSUE_ID Value Join Operator Equal ROOT_ISSUE_ID Node Relationship: Issue Header Extraction &ndash. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ISSUE_ID Value Join Operator Equal ROOT_ISSUE_ID Node Relationship: Issue Header Extraction &ndash. All rights reserved. you must have made your settings in Customizing for QIM under Configure Search . Foreign Keys Attributes of Parent Node Value Attributes of Child Node ISSUE_ID Value ROOT_ISSUE_ID Join Operator Equal 1. Issue Category Defect Node 0QAM_I_QDF_T01.13.QAM_I_QCA_ROOT Relationship Type Association Cardinality Arbitrary Reverse Cardinality Up to one Subquery No This node is a subnode of the root node QAM_I_ROOT. Technical Data Model Use Application model Software Component for Search and Analytics QAM Prerequisites To use the search and analytics model for Embedded Search.2 Defect : 0QAM_I_QDF_T01 This search and analytics model is used to search for QIM quality issues of the category Defect .1. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE. Node Response . Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QDF_TXTTY_T01 /IAM/TXTTY Authorization object for descriptions Logical Conjunction Authorization Type Logical Conjunction PUBLIC © 2014 SAP SE or an SAP affiliate company.Issue Attachment Default Request (All Response Attributes) Technical Name DEFAULT Use Attribute search Input help Overview of the Nodes in the Model In the following sections. Operational Data Provider: Defect Header Extraction Technical Name 0QAM_I_QDF_T ODP Semantics Master data attributes Direct Access Activated No Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QDF_IAUTH_T01 /IAM/IAUTH Authorization object for issue/change request Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QDF_IAUTH_T01 Analytics 0QAM_I_QDF_IAUTH_T01 Analytics result filter 0QAM_I_QDF_IAUTH_T01 Navigation Target Navigation Target Description Details 0QAM_I_QDF_OVP_SUBISSUE_T01 Display defect Displays the defect in the QIM Web Dynpro Web Dynpro (Application Server) application UI Technology 0QAM_I_QDF_OVP_ROOT_ISSUE_T01 Display root issue Displays the parent issue in the QIM Web Dynpro application Web Dynpro (Application Server) Node: Defect Description: Code and Texts Technical Name for Node QAM_I_QDF_DESC DDIC Structure /IAM/S_ESO_I_DESC Generally. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE. Operational Data Provider in the system in the transaction ESH_MODELER. Root Node: Issue Header Extraction Technical Name for Root Node QAM_I_QDF_ROOT DDIC Structure /IAM/S_ESO_I_ROOT Generally. you will find information about the nodes of the search and analytics model. Page 72 of 106 . see the steps Model Nodes . and. For more technical information about the nodes. All rights reserved. if required. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QDF_OREF_T01 /IAM/OREF Authorization object for reference objects for issue/change request/activity Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QDF_OREF_T01 Analytics 0QAM_I_QDF_OREF_T01 Analytics result filter 0QAM_I_QDF_OREF_T01 Node: Issue Partner Extraction Technical Name for Node QAM_I_QDF_PARTY DDIC Structure /IAM/S_ESO_I_PARTY Generally. For more technical information about the nodes. see the step Node Relations in the system in the transaction ESH_MODELER. Page 73 of 106 .Search 0QAM_I_QDF_TXTTY_T01 Analytics 0QAM_I_QDF_TXTTY_T01 Analytics result filter 0QAM_I_QDF_TXTTY_T01 Node: Object References with Description Technical Name for Node QAM_I_QDF_OREF DDIC Structure /IAM/S_ESO_I_OREF Generally. you will find information about the node relationships of the search and analytics model./IAM/CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No PUBLIC © 2014 SAP SE or an SAP affiliate company. Overview of the Node Relationships in the Model In the following sections. Node Relationship: Defect Description: Code and Texts Node QAM_I_QDF_DESC Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node PARTY of business object /IAM/ISSUE. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ISSUE. All rights reserved. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY PARENT_KEY Value Join Operator Equal Node Relationship: Code Node 0CODE. /IAM/OBJ_TYPE_CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QDF_OREF./IAM/CODE_GROUP Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QDF_DESC. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Object Type Code Node 0OBJ_TYPE_CODE. Value Join Operator Page 74 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node TYPE_CD Value Join Operator Equal TYPE Node Relationship: Object Subtype Code Node 0OBJ_SUBTYPE_CODE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE Value Join Operator Equal CODE Node Relationship: Code Group Node 0CODE_GROUP. Foreign Keys Attributes of Parent Node Value Attributes of Child Node PUBLIC © 2014 SAP SE or an SAP affiliate company.This node is a subnode of the node QAM_I_QDF_DESC. All rights reserved./IAM/OBJ_SUBTYPE_COD Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QDF_OREF. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE_GRP Value Join Operator Equal CODEGROUP Node Relationship: Object References with Description Node QAM_I_QDF_OREF Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery Yes This node is a subnode of the root node QAM_I_QDF_ROOT. PUBLIC © 2014 SAP SE or an SAP affiliate company. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Partner Role Code Node 0PARTY_ROLE_CODE.TYPE_CD TYPE Equal SUBTYPE_CD SUBTYPE Equal Node Relationship: Issue Partner Extraction Node QAM_I_QDF_PARTY Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. Page 75 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node PARTY_ROLE_CODE Value APPLICATION Join Operator Equal PARTY_ROLE_CODE QIM Node Relationship: Defect Description: Code and Texts &ndash. Text Type Defect Description (DDESC) Node 0QAM_I_QDF_T01.QAM_I_QDF_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT./IAM/PARTY_ROLE_CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QDF_PARTY. All rights reserved. Text Type Defect Location (DLCTN) Node 0QAM_I_QDF_T01.QAM_I_QDF_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Equal PARENT_KEY DESC_TYPE Join Operator DDESC Node Relationship: Defect Description: Code and Texts &ndash. Responsible Node 0QAM_I_QDF_T01. Page 76 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value RESPONSIBLE_IND Join Operator Equal PARENT_KEY X Node Relationship: Criticality Node 0CRITICALITY. This section describes all these associations collectively.QAM_I_QDF_PARTY Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. Node 0QAM_I_QDF_T01.Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Equal PARENT_KEY DESC_TYPE Join Operator DLCTN Node Relationships: Object References with Description For the node 0QAM_I_QDF_T01. Foreign Keys./IAM/CRITICALITY Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No PUBLIC © 2014 SAP SE or an SAP affiliate company.QAM_I_QDF_OREF Relationship Type Association Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. All rights reserved. Same for All Associations Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Other Foreign Keys by Association Association Description Attributes of Child Node Value TYPE_CD MAT TYPE_CD CUS TYPE_CD VEN QAM_I_QDF_ROOT2QAM_I_QDFO Reference object outbound delivery REF_DLV TYPE_CD DLV QAM_I_QDF_ROOT2QAM_I_QDFO Reference object batch TYPE_CD BAT TYPE_CD PLA QAM_I_QDF_ROOT2QAM_I_QDFO Reference object material Note REF_MAT QAM_I_QDF_ROOT2QAM_I_QDFO Reference object customer REF_CUS QAM_I_QDF_ROOT2QAM_I_QDFO Reference object vendor REF_VEN REF_BAT QAM_I_QDF_ROOT2QAM_I_QDFO Reference object plant REF_PLA Node Relationship: Issue Partner Extraction &ndash.QAM_I_QDF_OREF there are multiple associations: one for each QIM object type. This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal CRITICALITY CRITICALITY Equal Node Relationship: Application Node 0APPLICATION.QAM_I_ROOT Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ISSUE_CATEGORY Value Join Operator Equal ISS_CATEGORY Node Relationship: Issue Type and Text Node 0ISSUE_TYPE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node APPLICATION Value Join Operator Equal APPLICATION Node Relationship: Issue Category Node 0ISSUE_CATEGORY./IAM/ISSUE_TYPE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT./IAM/APPLICATION Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. All rights reserved. Page 77 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal ISSUE_TYPE ISSUE_TYPE Equal Node Relationship: Issue Header Extraction Node 0QAM_I_QIM_T01./IAM/ISSUE_CATEGORY Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QDF_ROOT. PUBLIC © 2014 SAP SE or an SAP affiliate company. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE. Operational Data Provider in the system in the transaction ESH_MODELER.3 Cause : 0QAM_I_QCA_T01 This search and analytics model is used to search for QIM quality issues of the category Cause . if required. you must have made your settings in Customizing for QIM under Configure Search . Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_I_QCA_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. Root Node: Issue Header Extraction Technical Name for Root Node QAM_I_QCA_ROOT DDIC Structure /IAM/S_ESO_I_ROOT Generally. Technical Data Model Use Application model Software Component for Search and Analytics QAM Prerequisites To use the search and analytics model for Embedded Search. and. you will find information about the nodes of the search and analytics model.1. For more technical information about the nodes. use the following models: Issue Defect Effect Issue Attachment Default Request (All Response Attributes) Technical Name DEFAULT Use Attribute search Overview of the Nodes in the Model In the following sections. All rights reserved.Foreign Keys Attributes of Parent Node Value Attributes of Child Node ROOT_ISSUE_ID Value Join Operator Equal ISSUE_ID 1. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QCA_IAUTH_T01 /IAM/IAUTH Authorization object for issue/change request Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QCA_IAUTH_T01 Analytics 0QAM_I_QCA_IAUTH_T01 Analytics result filter 0QAM_I_QCA_IAUTH_T01 Navigation Target Navigation Target Description Details PUBLIC © 2014 SAP SE or an SAP affiliate company. UI Technology Page 78 of 106 .13. To search for other issue categories or attachments to an issue or subissue. see the steps Model Nodes . Node Response . see the step Node Relations in the system in the transaction ESH_MODELER. Node Relationship: Issue Descriptions Extraction Node QAM_I_QCA_DESC Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node PUBLIC © 2014 SAP SE or an SAP affiliate company. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE. you will find information about the node relationships of the search and analytics model. All rights reserved. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QCA_OREF_T01 /IAM/OREF Authorization object for reference objects for issue/change request/activity Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QCA_OREF_T01 Analytics 0QAM_I_QCA_OREF_T01 Analytics result filter 0QAM_I_QCA_OREF_T01 Overview of the Node Relationships in the Model In the following sections. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ISSUE.0QAM_I_QCA_OVP_SUBISSUE_T01 Display cause Displays the cause in the QIM Web Dynpro Web Dynpro (Application Server) application 0QAM_I_QCA_OVP_ROOT_ISSUE_T01 Display root issue Displays the parent issue in the QIM Web Dynpro application Web Dynpro (Application Server) Node: Issue Descriptions Extraction Technical Name for Node QAM_I_QCA_DESC DDIC Structure /IAM/S_ESO_I_DESC Generally. For more technical information about the nodes. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QCA_TXTTY_T01 /IAM/TXTTY Authorization object for descriptions Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QCA_TXTTY_T01 Analytics 0QAM_I_QCA_TXTTY_T01 Analytics result filter 0QAM_I_QCA_TXTTY_T01 Node: Object References with Description Technical Name for Node QAM_I_QCA_OREF DDIC Structure /IAM/S_ESO_I_OREF Generally. Value Join Operator Page 79 of 106 . /IAM/CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QCA_DESC. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Object Type Code Node 0OBJ_TYPE_CODE./IAM/CODE_GROUP Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QCA_DESC. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE Value Join Operator Equal CODE Node Relationship: Object References with Description Node QAM_I_QCA_OREF Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery Yes This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE_GRP Value Join Operator Equal CODEGROUP Node Relationship: Code Node 0CODE.DB_KEY Equal PARENT_KEY Node Relationship: Code Group Node 0CODE_GROUP. Foreign Keys Attributes of Parent Node TYPE_CD Value Attributes of Child Node TYPE PUBLIC © 2014 SAP SE or an SAP affiliate company./IAM/OBJ_TYPE_CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QCA_OREF. All rights reserved. Value Join Operator Equal Page 80 of 106 . Node Relationship: Object Subtype Code Node 0OBJ_SUBTYPE_CODE. Foreign Keys. Same for All Associations Attributes of Parent Node Value DB_KEY Attributes of Child Node Value Join Operator Equal PARENT_KEY Other Foreign Keys by Association Association Description Attributes of Child Node Value TYPE_CD MAT TYPE_CD CUS TYPE_CD PLA TYPE_CD VEN QAM_I_QCA_ROOT2QAM_I_QCAO Reference object outbound delivery REF_DLV TYPE_CD DLV QAM_I_QCA_ROOT2QAM_I_QCAO Reference object batch TYPE_CD BAT QAM_I_QCA_ROOT2QAM_I_QCAO Reference object material Note REF_MAT QAM_I_QCA_ROOT2QAM_I_QCAO Reference object customer REF_CUS QAM_I_QCA_ROOT2QAM_I_QCAO Reference object plant REF_PLA QAM_I_QCA_ROOT2QAM_I_QCAO Reference object vendor REF_VEN REF_BAT PUBLIC © 2014 SAP SE or an SAP affiliate company. Node 0QAM_I_QCA_T01. All rights reserved./IAM/OBJ_SUBTYPE_COD Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QCA_OREF. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator TYPE_CD TYPE Equal SUBTYPE_CD SUBTYPE Equal Node Relationship: Issue Descriptions Extraction Node 0QAM_I_QCA_T01.QAM_I_QCA_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT. This section describes all these associations collectively.QAM_I_QCA_OREF Relationship Type Association Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT.QAM_I_QCA_OREF there are multiple associations: one for each QIM object type. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Equal PARENT_KEY DESC_TYPE Join Operator CDESC Node Relationships: Object References with Description For the node 0QAM_I_QCA_T01. Page 81 of 106 . QAM_I_ROOT Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ISSUE_CATEGORY Value Join Operator Equal ISS_CATEGORY Node Relationship: Issue Type and Text Node 0ISSUE_TYPE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ROOT_ISSUE_ID Value Join Operator Equal ISSUE_ID Node Relationship: Application Node 0APPLICATION.1.4 Effect PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 82 of 106 ./IAM/ISSUE_TYPE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT. All rights reserved./IAM/APPLICATION Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT./IAM/ISSUE_CATEGORY Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QCA_ROOT.13.Node Relationship: Issue Header Extraction Node 0QAM_I_QIM_T01. Foreign Keys Attributes of Parent Node Value Attributes of Child Node APPLICATION Value Join Operator Equal APPLICATION Node Relationship: Issue Category Node 0ISSUE_CATEGORY. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal ISSUE_TYPE ISSUE_TYPE Equal 1. To search for other issue categories or attachments to an issue or subissue. and. you will find information about the nodes of the search and analytics model. see the steps Model Nodes . Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_I_QEF_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. you must have made your settings in Customizing for QIM under Configure Search . All rights reserved. Technical Data Model Use Application model Software Component for Search and Analytics QAM Prerequisites To use the search and analytics model for Embedded Search. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE. Node Response . Operational Data Provider in the system in the transaction ESH_MODELER. For more technical information about the nodes. Root Node: Issue Header Extraction Technical Name for Root Node QAM_I_QEF_ROOT DDIC Structure /IAM/S_ESO_I_ROOT Generally. Page 83 of 106 . if required.: 0QAM_I_QEF_T01 This search and analytics model is used to search for QIM quality issues of the category Effect . Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QEF_IAUTH_T01 /IAM/IAUTH Authorization object for issue/change request Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QEF_IAUTH_T01 Analytics 0QAM_I_QEF_IAUTH_T01 Analytics result filter 0QAM_I_QEF_IAUTH_T01 Navigation Target Navigation Target Description Details UI Technology 0QAM_I_QEF_OVP_SUBISSUE_T01 Display effect Displays the effect in the QIM Web Dynpro application Web Dynpro (Application Server) 0QAM_I_QEF_OVP_ROOT_ISSUE_T01 Display root issue Displays the parent issue in the QIM Web Dynpro application Web Dynpro (Application Server) Node: Effect Description: Code and Texts PUBLIC © 2014 SAP SE or an SAP affiliate company. use the following models: Issue Defect Cause Issue Attachment Default Request (All Response Attributes) Technical Name DEFAULT Use Attribute search Overview of the Nodes in the Model In the following sections. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_I_QEF_TXTTY_T01 /IAM/TXTTY Authorization object for descriptions Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_I_QEF_TXTTY_T01 Analytics 0QAM_I_QEF_TXTTY_T01 Analytics result filter 0QAM_I_QEF_TXTTY_T01 Overview of the Node Relationships in the Model In the following sections./IAM/CODE_GROUP Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QEF_DESC. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE. Node Relationship: Effect Description: Code and Texts Node QAM_I_QEF_DESC Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT. see the step Node Relations in the system in the transaction ESH_MODELER. All rights reserved. you will find information about the node relationships of the search and analytics model. PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 84 of 106 ./IAM/CODE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_I_QEF_DESC.Technical Name for Node QAM_I_QEF_DESC DDIC Structure /IAM/S_ESO_I_DESC Generally. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE CODE Value Join Operator Equal Node Relationship: Code Group Node 0CODE_GROUP. For more technical information about the nodes. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Code Node 0CODE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal CRITICALITY CRITICALITY Equal Node Relationship: Issue Header Extraction Node 0QAM_I_QIM_T01.Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE_GRP Value Join Operator Equal CODEGROUP Node Relationship: Effect Description: Code and Texts &ndash. Foreign Keys PUBLIC © 2014 SAP SE or an SAP affiliate company. Text Type EDESC Node 0QAM_I_QEF_T01. All rights reserved. Page 85 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node ROOT_ISSUE_ID ISSUE_ID Value Join Operator Equal Node Relationship: Issue Type and Text Node 0ISSUE_TYPE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value DESC_TYPE Join Operator Equal PARENT_KEY EDESC Node Relationship: Criticality Node 0CRITICALITY.QAM_I_QEF_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT.QAM_I_ROOT Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT./IAM/ISSUE_TYPE Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT./IAM/CRITICALITY Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT. Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal ISSUE_TYPE ISSUE_TYPE Equal Node Relationship: Application Node 0APPLICATION. Foreign Keys Attributes of Parent Node Value Attributes of Child Node APPLICATION Value Join Operator Equal APPLICATION Node Relationship: Issue Category Node 0ISSUE_CATEGORY./IAM/ISSUE_CATEGORY Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT. defect./IAM/APPLICATION Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_I_QEF_ROOT. The data for the issue itself is part of other search and analytics models: Issue Defect Effect Cause Default Request (All Response Attributes) Technical Name Use DEFAULT Attribute search PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ISSUE_CATEGORY Value ISS_CATEGORY Join Operator Equal 1. Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_ISS_ATTACHMENT_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA.13. Page 86 of 106 . Technical Data Model Use Application model Software Component for Search and Analytics QAM Prerequisites To use the search and analytics model for Embedded Search.5 Issue Attachment : 0QAM_ATTM_T01 This search and analytics model is used to search for attachments to a quality issue or subissue (for example. you must have made your settings in Customizing for QIM under Configure Search . effect.1. cause) in QIM. /IAM/ Lifecycle status Association Arbitrary Exactly one No Effectiveness check status of Association an object Arbitrary Exactly one No /IAM/EFFECTIVENESS_C 0VALIDATION_STAT.1. Page 87 of 106 ./IA Validation status of an object Association Arbitrary Exactly one No Document type Association Arbitrary Exactly one No Issue type and text Association Arbitrary Exactly one No MIME code Association Arbitrary Exactly one No ISSUE_LCYCLE_ST 0EFFECTIVENESS_STAT. text Composition Arbitrary Exactly one Yes 0ISS_LCYC_STAT.Input help Root Node: Attachment Extraction Technical Name for Root Node QAM_S_ESO_ATT DDIC Structure /IAM/S_ESO_ATT Authorization Checks Check ID ABAP Authorization Object Description QAM_ATTMT /IAM/ATTMT Authorization object for attachments for issue/activity Logical Conjunction Authorization Type Logical Conjunction Search QAM_ATTMT Analytics QAM_ATTMT Analytics result filter QAM_ATTMT Navigation Targets Navigation Target Description Details UI Technology DISPLAYDOCUMENT Display document Displays the attachment General URL DISPLAYISSUE Display issue Displays the issue to which the attachment General URL belongs Node: Attachment Extraction &ndash. M/VALIDATION_CD 0DOC_TYPE./IAM/DOC_T YPE 0ISSUE_TYPE. Node Node Description Relationship Type Cardinality Reverse Cardinality Subquery QAM_S_ESO_ATT_T Attachment extraction &ndash./IAM/ISS UE_TYPE 0MIMECODE. Technical Data Model Use Application model Software Component for Search and Analytics QAM PUBLIC © 2014 SAP SE or an SAP affiliate company.13./IAM/MIMEC ODE 1. All rights reserved.6 Activity : 0QAM_A_ACT_T01 This search and analytics model is used to search for QIM activities. Text Technical Name for Node QAM_S_ESO_ATT_T DDIC Structure /IAM/S_ESO_ATT_T Node Relationships The node relationships listed in the following table are used to read language-specific texts. To search for attachments to an activity. All rights reserved. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_A_ACT_AAUTH_T01 /IAM/AAUTH Authorization object for activity Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_A_ACT_AAUTH_T01 Analytics 0QAM_A_ACT_AAUTH_T01 Analytics result filter 0QAM_A_ACT_AAUTH_T01 Navigation Target Navigation Target Description Details UI Technology 0QAM_A_ACT_OVP_ACTIVITY_T01 Display activity Displays the activity in the QIM Web Dynpro application Web Dynpro (Application Server) 0QAM_A_ACT_OVP_ISSUE_T01 Display root issue Displays the parent issue in the QIM Web Dynpro application Web Dynpro (Application Server) Node: Data Technical Name for Node QAM_A_ACT_DATE DDIC Structure /IAM/S_ESO_A_DATE Generally. Root Node: Header Technical Name for Root Node QAM_A_ACT_ROOT DDIC Structure /IAM/S_ESO_A_ROOT Generally. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ACTIVITY. you must have made your settings in Customizing for QIM under Configure Search . Default Request (All Response Attributes) Technical Name DEFAULT Use Attribute search Input help Overview of the Nodes in the Model In the following sections. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DATE of business object /IAM/ACTIVITY. Node: Descriptions Technical Name for Node QAM_A_ACT_DESC DDIC Structure /IAM/S_ESO_A_DESC PUBLIC © 2014 SAP SE or an SAP affiliate company.Prerequisites To use the search and analytics model for Embedded Search. use the model Activity Attachment. Page 88 of 106 . Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_A_GEN_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. you will find information about the nodes of the search and analytics model. For more technical information about the nodes. see the steps Model Nodes and Node Response in the system in the transaction ESH_MODELER. Overview of the Node Relationships in the Model In the following sections. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ACTIVITY. All rights reserved. see the step Node Relations in the system in the transaction ESH_MODELER. Node Relationships: Data Node QAM_A_ACT_DATE Relationship Type Composition PUBLIC © 2014 SAP SE or an SAP affiliate company. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node PARTY of business object /IAM/ACTIVITY. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node QUANTITY of business object /IAM/ACTIVITY. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_A_ACT_OREF_T01 /IAM/OREF Authorization object for reference objects for issue/change request/activity Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_A_ACT_OREF_T01 Analytics 0QAM_A_ACT_OREF_T01 Analytics result filter 0QAM_A_ACT_OREF_T01 Node: Partners Technical Name for Node QAM_A_ACT_PARTY DDIC Structure /IAM/S_ESO_A_PARTY Generally. the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ACTIVITY. you will find information about the node relationships of the search and analytics model.Generally. Authorization Checks Check ID ABAP Authorization Object Description 0QAM_A_ACT_TXTTY_T01 /IAM/TXTTY Authorization object for descriptions Logical Conjunction Authorization Type Logical Conjunction Search 0QAM_A_ACT_TXTTY_T01 Analytics 0QAM_A_ACT_TXTTY_T01 Analytics result filter 0QAM_A_ACT_TXTTY_T01 Node: Reference Objects Technical Name for Node QAM_A_ACT_OREF DDIC Structure /IAM/S_ESO_A_OREF Generally. For more technical information about the nodes. Node: Quantities Technical Name for Node QAM_A_ACT_QUANTITY DDIC Structure /IAM/S_ESO_A_QUANTITY Generally. Page 89 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Descriptions Node QAM_A_ACT_DESC Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. All rights reserved. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE Value Join Operator Equal CODE Node Relationship: Code Group Node 0CODE_GROUP. Page 90 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Code Node 0CODE. Foreign Keys Attributes of Parent Node Value Attributes of Child Node CODE_GRP CODEGROUP Value Join Operator Equal Node Relationship: Reference Objects Node QAM_A_ACT_OREF Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No PUBLIC © 2014 SAP SE or an SAP affiliate company./IAM/CODE Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_A_ACT_DESC.Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT./IAM/CODE_GROUP Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_A_ACT_DESC. /IAM/OBJ_TYPE_CODE Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the node QAM_A_ACT_OREF. Page 91 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Object Type Code Node 0OBJ_TYPE_CODE. PUBLIC © 2014 SAP SE or an SAP affiliate company./IAM/PARTY_ROLE_CODE Relationship Type Association Cardinality Arbitrary Reverse Cardinality Up to one Subquery No This node is a subnode of the node QAM_A_ACT_PARTY. Foreign Keys Attributes of Parent Node Value Attributes of Child Node TYPE_CD Value Join Operator Equal TYPE Node Relationship: Partners Node QAM_A_ACT_PARTY Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node PARTY_ROLE_CODE Value APPLICATION Join Operator Equal PARTY_ROLE_CODE QIM Node Relationship: Quantities Node 0QAM_A_ACT_QUANTITY Relationship Type Composition Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. All rights reserved. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Partner Role Code Node 0PARTY_ROLE_CODE.This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ROLE_CD Value Join Operator Equal QTY_ROLE_CD Node Relationships: Data For the node 0QAM_A_ACT_T01. This section describes all these associations collectively. Page 92 of 106 .QAM_A_ACT_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT.QAM_A_ACT_DATE there are multiple associations: one for each timepoint stored in Customizing. Text Type Activity Description (ADESC) Node 0QAM_A_ACT_T01. All rights reserved. Text Type Activity Response (ARESP) Node 0QAM_A_ACT_T01.QAM_A_ACT_DATE Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys.QAM_A_ACT_DESC PUBLIC © 2014 SAP SE or an SAP affiliate company. Same for All Associations Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Other Foreign Keys by Association Association Description Attributes of Child Node Value QAM_A_ACT_ROOT2QAM_A_DATE_301 Timepoint Expected start date ROLE_CD 301 QAM_A_ACT_ROOT2QAM_A_DATE_302 Timepoint Expected end date ROLE_CD 302 QAM_A_ACT_ROOT2QAM_A_DATE_303 Timepoint Effective date ROLE_CD 303 QAM_A_ACT_ROOT2QAM_A_DATE_304 Timepoint Completion date ROLE_CD 304 Node Relationship: Descriptions &ndash.Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Node Relationship: Quantity Role Code Node 0QUANTITY_ROLE_CODE. Foreign Keys Attributes of Parent Node DB_KEY Value Attributes of Child Node Value Equal PARENT_KEY DESC_TYPE Join Operator ADESC Node Relationship: Descriptions &ndash. Node 0QAM_A_ACT_T01./IAM/QUNTY_ROLE_CD Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_QUANTITY. All rights reserved.QAM_A_ACT_OREF Relationship Type Association Cardinality Arbitrary Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Page 93 of 106 . Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY DESC_TYPE ARESP Node Relationships: Reference Objects For the node 0QAM_A_ACT_T01. Responsible Node 0QAM_A_ACT_T01.0QAM_A_ACT_T01. Foreign Keys. Foreign Keys Attributes of Parent Node Value Attributes of Child Node DB_KEY Value RESPONSIBLE_IND Join Operator Equal PARENT_KEY X Node Relationship: Activity Category and Text Node 0ACTIVITY_CATEGORY.QAM_A_ACT_PARTY Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT.QAM_A_ACT_OREF there are multiple associations for the different object types./IAM/ACT_CATEGORY Relationship Type Association Cardinality Exactly one PUBLIC © 2014 SAP SE or an SAP affiliate company. Node 0QAM_A_ACT_T01. Same for All Associations Attributes of Parent Node Value Attributes of Child Node DB_KEY Value Join Operator Equal PARENT_KEY Other Foreign Keys by Association Association Description Attributes of Child Node Value QAM_A_ACT_ROOT2QAM_A_OREF_CUS Reference object customer TYPE_CD CUS QAM_A_ACT_ROOT2QAM_A_OREF_PLA Reference object plant TYPE_CD PLA QAM_A_ACT_ROOT2QAM_A_OREF_MAT Reference object material TYPE_CD MAT QAM_A_ACT_ROOT2QAM_A_OREF_BAT Reference object batch TYPE_CD BAT QAM_A_ACT_ROOT2QAM_A_OREF_DLV Reference object outbound delivery TYPE_CD DLV QAM_A_ACT_ROOT2QAM_A_OREF_FL Reference object functional location TYPE_CD FL QAM_A_ACT_ROOT2QAM_A_OREF_VEN Reference object vendor TYPE_CD VEN Node Relationship: Partner &ndash.QAM_A_ACT_DESC Relationship Type Association Cardinality Up to one Reverse Cardinality Exactly one Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. This section describes all these associations collectively. Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ACT_CATEGORY Value Join Operator Equal ACT_CATEGORY Node Relationship: Activity Template and Text Node 0ACTIVITY_TEMPLATE./IAM/ACT_TEMPLATE Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal ACT_TEMPLATE ACTIVITY_TYPE Equal (contains the activity template despite the differing technical name) Node Relationship: Activity Type and Text Node 0ACTIVITY_TYPE./IAM/ACT_TYPE Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal 0ACTIVITY_TYPE ACTTYPE Equal Node Relationship: Activity Lifecycle Status (Activity Status) Node 0ACT_LCYC_STAT./IAM/ACT_LCYCLE_ST Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node LCYCLE_CD KEY1 Value Join Operator Equal Node Relationship: Activity Origin Code Node 0ACT_ORIGIN_CD./IAM/ACTIVITY_ORIGIN Relationship Type Association PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 94 of 106 Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node ORIGIN_CD Value Join Operator Equal KEY1 Node Relationship: Validation Status of an Object Node 0VALIDATION_STAT./IAM/VALIDATION_CD Relationship Type Association Cardinality Exactly one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node VALIDATION_CD Value Join Operator Equal KEY1 Node Relationship: Issue Header Extraction Node 0QAM_I_QIM_T01.QAM_I_ROOT Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal ROOT_ISSUE_ID ISSUE_ID Equal Node Relationship: Authorization Group Node 0AUTH_GROUP./IAM/AUTHORIZATION_G Relationship Type Association Cardinality Up to one Reverse Cardinality Arbitrary Subquery No This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node Value Attributes of Child Node Value Join Operator APPLICATION APPLICATION Equal AUTH_GROUP AUTH_GROUP Equal 1.13.1.7 Activity Attachment : 0QAM_A_ATTM_T01 This search and analytics model is used to search for attachments to a quality activity in QIM. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 95 of 106 Technical Data Model Use Application model Software Component for Search and Analytics QAM Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search . Search and Analytics Integration The data is read from the DDIC by the BAdI implementation QAM_ACT_ATTACHMENT_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. The data for the activity itself is part of the search and analytics model Activity. Default Request (All Response Attributes) Technical Name DEFAULT Use Attribute search Root Node: Attachment Extraction Technical Name for Root Node QAM_S_A_ESO_ATT DDIC Structure /IAM/S_ESO_ATT Authorization Checks Check ID ABAP Authorization Object Description QAM_A_ATTMT /IAM/ATTMT Authorization object for attachments for issue/activity Logical Conjunction Authorization Type Logical Conjunction Search QAM_A_ATTMT Analytics QAM_A_ATTMT Analytics result filter QAM_A_ATTMT Navigation Targets Navigation Target Description Details UI Technology DISPLAYDOCUMENT Display document Displays the attachment Web Dynpro DISPLAYACTIVITY Display activity Displays the activity to which the attachment belongs Web Dynpro DISPLAYISSUE Display issue Displays the issue to which the activity belongs Web Dynpro Node: Attachment Extraction &ndash; Text Technical Name for Node QAM_S_A_ESO_ATT_T DDIC Structure /IAM/S_ESO_ATT_T Node Relationships The node relationships listed in the following table are used to read language-specific texts. Node Node Description Relationship Type Cardinality Reverse Cardinality Subquery QAM_S_A_ESO_ATT_T Attachment extraction &ndash; text Composition Arbitrary Exactly one No 0DOC_TYPE./IAM/DOC_T Document type Association Up to one Arbitrary No MIME code Association Up to one Arbitrary No YPE 0MIMECODE./IAM/MIMEC PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 96 of 106 /IAM/AUT HORIZATION_G 0ISSUE_CATEGORY./IAM/PRIOR Priority Association Arbitrary Exactly one No Issue type and text Association Arbitrary Exactly one No 0CODE.2 TransientProviders PUBLIC © 2014 SAP SE or an SAP affiliate company./IAM/ ACT_TYPE 0ACT_LCYC_STAT.1. you can run analyses for QIM issues by defining queries for the TransientProvider QIM Issues./IA M/VALIDATION_CD 1./IAM/ ACT_LCYCLE_ST 0VALIDATION_STAT./IAM/ISS UE_TYPE ISSUE_LCYCLE_ST 0AUTH_GROUP./IAM /ISSUE_CATEGORY 0CRITICALITY.ODE 0ISSUE_TYPE./IAM/CR ITICALITY 1.13./IAM/ISS Issue type and text Association Up to one Arbitrary No Activity type and text Association Up to one Arbitrary No Activity lifecycle status Association Up to one Arbitrary No Validation status of an object Association Up to one Up to one No UE_TYPE 0ACTIVITY_TYPE./IAM/ Lifecycle status Association Arbitrary Exactly one No Authorization group Association Arbitrary Exactly one No Issue category Association Arbitrary Exactly one No Criticality Association Arbitrary Exactly one No ITY 0ISSUE_TYPE. Node Node Description Relationship Type Cardinality Reverse Cardinality Subquery 0PRIORITY.13. Technical Data Model Use Application model Software Component for Search and Analytics QAM Root Node: Quality Issues Technical Name for Root Node QAM_ISSUES DataSource 0QAM_ISSUES Operational Data Provider: Quality Issues Technical Name 0QAM_ISSUES ODP Semantics Transaction data Direct Access Activated Yes Authorization Checks Check ID ABAP Authorization Object Description QAM_ISSUES_CHECK /IAM/IAUTH Authorization object for issue/change request Logical Conjunction Authorization Type Logical Conjunction Search QAM_ISSUE_CHECK Analytics QAM_ISSUE_CHECK Analytics result filter QAM_ISSUE_CHECK Node Relationships The node relationships listed in the following table are used to read language-specific texts. Page 97 of 106 ./IAM/CODE Code Association Arbitrary Exactly one No 0ISS_LCYC_STAT.8 ODP for Issue and Subissue : 0QAM_ISSUES On the basis of this model. All rights reserved. 2 TransientProviders 1. you can define analytical queries for evaluating QIM issues.13. Prerequisites The connector for the search and analytics model ODP for Issue and Subissue is active.1.3.13. Structure Data Modeling Requires Object Type Name Technical Name Operational Data Provider (ESH-Based) Quality Issues 0QAM_ISSUES InfoObject Default Quantity Unit 2O-DEF_QUANT_UN InfoObject Number of issues 2O-ISSUE_COUNT-INT4 InfoObject Complaint Quantity 2O-Q_COMSUM-DEC InfoObject Complaint divided by Reference Quantity 2O-Q_COM_D_Q007-DEC InfoObject Issues for Complaint divided by Reference Quantity 2O-Q_COM_D_Q008-INT4 InfoObject Number of Occurrences 2O-Q_OCCSUM-INT4 InfoObject Reference Quantity 2O-Q_REFSUM-DEC InfoObject Expected Start minus Expected End Date in seconds 2O-T_302_S_T009-DEC InfoObject Issues for Expected Start minus Expected End Date in 2O-T_302_S_T010-INT4 seconds InfoObject Application 2O0APPLICATION InfoObject Authorization Group 2O0AUTH_GROUP InfoObject Code 2O0CODE InfoObject Criticality 2O0CRITICALITY InfoObject Lifecycle Status 2O0IAMISS_LCYC InfoObject Issue Category 2O0ISSUE_CATEG InfoObject Issue type and text 2O0ISSUE_TYPE InfoObject Priority 2O0PRIORITY InfoObject Approval Status 2O0QAM_ISSUES-APPROVAL_CD InfoObject Archiving Status 2O0QAM_ISSUES-ARCHIVING_CD InfoObject Cause Code 2O0QAM_ISSUES-CDESC_CD InfoObject Changed By 2O0QAM_ISSUES-CHANGED_BY InfoObject Batch Number 2O0QAM_ISSUES-CHA_REF_ID InfoObject Consistency 2O0QAM_ISSUES-CONSIST_CD InfoObject Country Key 2O0QAM_ISSUES-COUNTRY InfoObject Created By 2O0QAM_ISSUES-CREATED_BY InfoObject Customer 2O0QAM_ISSUES-CUSTOMER_REF InfoObject Defect Code 2O0QAM_ISSUES-DDESC_CD InfoObject Deferral Status 2O0QAM_ISSUES-DEFERRAL_CD InfoObject Digital Signature Status Code 2O0QAM_ISSUES-DIGSIGN_CD InfoObject Delivery Item 2O0QAM_ISSUES-DLI_REF_ID InfoObject Delivery 2O0QAM_ISSUES-DLV_REF_ID InfoObject Duration 2O0QAM_ISSUES-DURATION_CD InfoObject Effect Code 2O0QAM_ISSUES-EDESC_CD InfoObject Effectiveness Check Status of an Object 2O0QAM_ISSUES-EFFECTIVENES PUBLIC © 2014 SAP SE or an SAP affiliate company. Page 98 of 106 . All rights reserved.1 QIM Issues : 2O0QAM_ISSUES On the basis of this TransientProvider. 1 QIM Issues DataSource Transactional Data: 0QAM_ISSUES You can use this DataSource for various analyses of issues in SAP QIM: Operational reporting with Search and Operational Analytics The search and analytics model ODP for Issue and Subissue is available for this purpose.0 SP02 Shipment n/a Content Versions QAM100 RemoteCube-Capable n/a Delta-Capable No Extraction from Archives No Verifiable n/a Data Modeling Fields of Origin for the Extract Structure Fields in the Extract Structure Description of the Field in the Extract Structure Table of Origin Field in the Table of Origin ISSUE_COUNT Number of issues /IAM/D_I_ROOT N/A KEY_MAX Node ID /IAM/D_I_ROOT DB_KEY Q_COMSUM Complaint quantity /IAM/D_I_QTY QUANTITY Q_OCCSUM Number of occurrences /IAM/D_I_QTY QUANTITY Q_REFSUM Reference quantity /IAM/D_I_QTY QUANTITY Q_COM_D_Q_REF Complaint quantity / Reference quantity /IAM/D_I_QTY QUANTITY Q_COM_D_Q_REF_CT Number of issues for calculation /IAM/D_I_QTY N/A T_302_S_T_301 UTC timestamp in short form (expected end date &ndash.3 DataSources 1. All rights reserved. Page 99 of 106 .13.InfoObject Emergency Indicator 2O0QAM_ISSUES-EMERGENCY InfoObject Equipment 2O0QAM_ISSUES-EQ_REF_ID InfoObject Functional Location 2O0QAM_ISSUES-FL_REF_ID InfoObject Resolution Code 2O0QAM_ISSUES-ISOLU_CD InfoObject Issue ID 2O0QAM_ISSUES-ISSUE_ID InfoObject Issue Type Change Status 2O0QAM_ISSUES-ISSUE_TYPE_C InfoObject Reference Object ID 2O0QAM_ISSUES-MAIN_REF_ID InfoObject Material 2O0QAM_ISSUES-MATERIAL_REF InfoObject Plant 2O0QAM_ISSUES-PLA_REF_ID InfoObject Business Partner Number of Responsible 2O0QAM_ISSUES-RESPONSIBLE_ InfoObject Validation 2O0QAM_ISSUES-VALIDATION_C InfoObject Vendor 2O0QAM_ISSUES-VENDOR_REF_I 1.3. Reports in Business Context Viewer (BCV) The DataSource supports direct access with preaggregation.13. Technical Data Application Component QAM Available as of Release SAP QIM 1. expected start date) /IAM/D_I_DATE DATE_TIME T_302_S_T_301_CT Number of issues for calculation /IAM/D_I_DATE N/A CUSTOMER_REF_ID Customer /IAM/D_I_OBJ_REF ID MATERIAL_REF_ID Material /IAM/D_I_OBJ_REF ID VENDOR_REF_ID Vendor /IAM/D_I_OBJ_REF ID CHA_REF_ID Batch number /IAM/D_I_OBJ_REF ID DLI_REF_ID Delivery item /IAM/D_I_OBJ_REF ID PUBLIC © 2014 SAP SE or an SAP affiliate company. 13. Page 100 of 106 .DLV_REF_ID Delivery /IAM/D_I_OBJ_REF ID EQ_REF_ID Equipment /IAM/D_I_OBJ_REF ID FL_REF_ID Functional location /IAM/D_I_OBJ_REF ID PLA_REF_ID Plant /IAM/D_I_OBJ_REF ID MAIN_REF_ID Reference object ID (main reference object) /IAM/D_I_OBJ_REF ID IDESC_CD Code /IAM/S_I_DESC CODE CDESC_CD Cause code /IAM/S_I_DESC CODE DDESC_CD Defect code /IAM/S_I_DESC CODE EDESC_CD Effect code /IAM/S_I_DESC CODE ISOLU_CD Resolution code /IAM/S_I_DESC CODE LCYCLE_CD Issue life cycle status /IAM/D_I_ROOT LCYCLE_CD CONSIST_CD Consistency status of an object /IAM/D_I_ROOT CONSIST_CD DEFERRAL_CD Deferral status of an object /IAM/D_I_ROOT DEFERRAL_CD ARCHIVING_CD Archiving status of an object /IAM/D_I_ROOT ARCHIVING_CD VALIDATION_CD Validation status of an object /IAM/D_I_ROOT VALIDATION_CD EFFECTIVENESS_CD Effectiveness check status of an object /IAM/D_I_ROOT EFFECTIVENESS_CD APPROVAL_CD Approval status of an object /IAM/D_I_ROOT APPROVAL_CD ISSUE_TYPE_CD Issue type status of an object /IAM/D_I_ROOT ISSUE_TYPE_CD DIGSIGN_CD Digital signature status code /IAM/D_I_ROOT DIGSIGN_CD ISSUE_ID Issue ID /IAM/D_I_ROOT ISSUE_ID APPLICATION Application in Issue and Activity Engine /IAM/D_I_ROOT APPLICATION ISSUE_TYPE Issue type /IAM/D_I_ROOT ISSUE_TYPE ISSUE_CATEGORY Issue category /IAM/D_I_ROOT ISSUE_CATEGORY AUTH_GROUP Authorization group /IAM/D_I_ROOT AUTH_GROUP CRITICALITY Criticality /IAM/D_I_ROOT CRITICALITY PRIORITY Priority /IAM/D_I_ROOT PRIORITY EMERGENCY Emergency indicator /IAM/D_I_ROOT EMERGENCY DURATION_CD Duration /IAM/D_I_ROOT DURATION_CD COUNTRY Country key /IAM/D_I_ROOT COUNTRY DEF_QUANT_UNIT Default quantity unit /IAM/D_I_ROOT DEF_QUANT_UNIT CREATED_BY Created by /IAM/D_I_ROOT CREATED_BY CHANGED_BY Changed by /IAM/D_I_ROOT CHANGED_BY RESPONSIBLE_ID Business partner number /IAM/D_I_PARTY PARTNER_ID 1.4.1 Content Objects for Customizing in IAM The following table displays the DataSources and technical search and analytics models relevant for SAP QIM in the software component IAM.13.4 Content Objects in Software Component IAM 1. All rights reserved.Boolean 0APPLICATION /IAM/APPLICATION Application 0APPROVAL_STAT /IAM/APPROVAL_STATUS_CD Approval status 0AUTH_GROUP /IAM/AUTHORIZATION_GROUP Authorization group PUBLIC © 2014 SAP SE or an SAP affiliate company. which serve to extract texts for Customizing entries and make them available for searching or analytics. Features Search and Analytics Model DataSource Text 0ACTIVITY_CATEGORY /IAM/ACTIVITY_CATEGORY Activity category 0ACTIVITY_TEMPLATE /IAM/ACTIVITY_TEMPLATE Activity template 0ACTIVITY_TYPE /IAM/ACTIVITY_TYPE Activity type 0ACT_LCYC_STAT /IAM/ACTIVITY_LCYCLE_STAT_CD Activity life cycle status (activity status) 0ACT_ORIGIN_CD /IAM/ACTIVITY_ORIGIN_CD Activity origin code 0ACT_RESP_VAL_BOOL /IAM/ACT_RESPONSE_VALUE_BOOL Activity response value . Using data archiving. First archive the activities for an issue and its subissues (see Archiving Activities with /IAM/ACT). Archive the QIM objects (issues and activities) using the respective archiving object. proceed as described in Customizing for QIM under Search and Analytics Configure Search . These functions are available for QIM quality issues and QIM quality activities with the delivery of the following archiving objects: Activities: /IAM/ACT Issues: /IAM/ISSUE The archiving objects are based on the Archive Development Kit (ADK) and use functions of the BOPF archiving adapter. Data archiving An efficient management of data includes the archiving of data belonging to completed business processes. 1. you can export data that you no longer require in the system. You have made the required settings in Customizing for data archiving: SAP NetWeaver Application Server System Administration Archiving To use the archiving functions. an end of purpose check is possible for the following data: Business partners that are assigned to a QIM quality issue or a QIM quality activity Customers and vendors that are assigned as reference objects in QIM Prerequisites To be able to use the functions of Information Lifecycle Management (ILM). users must have the authorizations provided by the authorization object S_ARCHIVE. Data retention/data destruction With SAP NetWeaver Information Lifecycle Management (ILM). you can store rules for retention in ILM Retention Management.14 Archiving QIM Data SAP supports your data management by providing suitable functions for data archiving and for data retention and data destruction. PUBLIC © 2014 SAP SE or an SAP affiliate company.0CODE /IAM/CODE Code 0CODE_GROUP /IAM/CODE_GROUP Code group 0CRITICALITY /IAM/CRITICALITY Criticality 0DEFERRAL_STATUS /IAM/DEFERRAL_STATUS_CD Deferral status 0DIGIT_SIGN_CD /IAM/DIGIT_SIGN_CD Digital signature status 0DOC_TYPE /IAM/DOC_TYPE Document type 0DURATION /IAM/DURATION Duration 0EFFECTIVENESS_STAT /IAM/EFFECTIVENESS_CD Effectiveness check status 0ISSUE_CATEGORY /IAM/ISSUE_CATEGORY Issue category 0ISSUE_TYPE /IAM/ISSUE_TYPE Issue type 0ISS_LCYC_STAT /IAM/ISSUE_LCYCLE_STAT_CD Issue life cycle status (issue status) 0LOGICAL_SYSTEM /IAM/LOGICAL_SYSTEM Logical system 0MIMECODE /IAM/MIMECODE MIME code 0OBJ_SUBTYPE_CODE /IAM/OBJ_SUBTYPE_CODE Object subtype code 0OBJ_TYPE_CODE /IAM/OBJ_TYPE_CODE Object type code 0PARTY_ROLE_CODE /IAM/PARTY_ROLE_CODE Partner role code 0PRIORITY /IAM/PRIORITY Priority 0PROCESSING_CODE /IAM/PROCESSING_CD Processing status of an object 0QUANTITY_ROLE_CODE /IAM/QUANTITY_ROLE_CODE Quantity role code 0RESPONSIBLE_IND /IAM/RESPONSIBLE_IND Responsible indicator 0UNIT_OF_MEASURE /IAM/UOM Unit of measure 0VALIDATION_STAT /IAM/VALIDATION_CD Validation status Activities To use the objects for SAP QIM. SAP provides suitable tools to fulfill legal requirements for the retention of data. to an archive file. Data Procedure 1. 2. the archive file is stored in a file system or content repository and the data is deleted from the database. 1. but need to retain for documentation purposes. For example. To reduce the load on the database. To support you with the destruction of personal data. for example. Then archive the issue and the corresponding subissues (see Archiving Issues with /IAM/ISSUE). Familiarize yourself with the functions of the Archive Development Kit and ILM Retention Management: Data Archiving with Archive Development Kit (ADK) SAP NetWeaver Information Lifecycle Management 2. All rights reserved. and for the destruction of data. Page 101 of 106 . you must have activated the business function ILM. If the check was successful. see Checks for /IAM/ACT. even if you are logged on to the system in another language. For more information. Procedure 1. If the read was successful. 1. If you want to store retention rules for business partners. 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. and attachments stored in the system. 3. In the transaction SARA.1. you can use the options in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). You can change this setting in Customizing for the archiving object (in the transaction SARA under Goto Customizing Archiving Object-Specific Customizing Technical Settings ).1 Checks for /IAM/ACT The preprocessing program checks whether archiving can run for the selected activities based on the lifecycle status. such as reference objects. create a variant for the preprocessing program and schedule it. it sets the status to Archived and deletes the data from the database. or register other archiving classes. the ILM object IAM_ACTIVITY is delivered. Usage in ILM Retention Management To be able to use the archiving object /IAM/ACT in Information Lifecycle Management (ILM). Note When QIM data is archived. partners.14. 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. In the transaction SARA. you can archive activities and their corresponding information.3.1 Archiving Activities with /IAM/ACT With the archiving object /IAM/ACT. create a variant for the write program and schedule it. customers. these texts will be shown in English when you display the archived data at a later stage. field /IAM/A_ACT Authorization to Perform Activity-Related Activities . 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 . All rights reserved. PUBLIC © 2014 SAP SE or an SAP affiliate company. Environment 1. descriptions. and vendors. If you want to extend the archivability checks. The delete program is executed automatically after the write program. proceed as described in Customizing for QIM under Define End of Purpose for Personal Data . For more information. Page 102 of 106 . archive additional data. such as the descriptions of codes stored in Customizing. Settings in ILM object Customizing (transaction IRM_CUST) for IAM_ACTIVITY: Available Time References: Created On (CREATION_DATE) Last Changed On (LAST_CHANGE_DATE) Available Condition Fields: IAM Application (APPLICATION) IAM Authorization Group (AUTH_GROUP) Available Policy Categories: Retention Rules (RTP) Assigned BOR Object: /IAM/ACT Prerequisites You have authorization for the activity 12 Archive in the authorization object IAM/A_STAT Authorization Object for Lifecycle Status (Activity) .14. For more information. residence time) to check for which activities archiving is possible and then assigns them the archiving status Marked for Archiving . transient texts. Result The archived data is deleted from the database but can still be displayed. if you perform the archiving in English. see Business Object Builder. The write program also sets the Activities Archived indicator in the parent issue or subissue. Delete program /IAM/ACT_ARCH_DEL The delete program reads the data from the archive file. For more information. Note The residence time is already taken into account in the selection criteria for the preprocessing program (see Creating Preprocessing Variants for /IAM/ACT). the program sets the archiving status Marked for Archiving . are also archived in one specific language. see Displaying Archived QIM Data. see Creating Preprocessing Variants for /IAM/ACT 2. activity type. 5. 6. you can. and lifecycle status. 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 .2 Creating Preprocessing Variants for /IAM/ACT The preprocessing program selects the activities based on your specified selection criteria and checks whether they can be archived (see Checks for /IAM/ACT). cause. relating to the date of the last change). Recommendation You can store the application QIM in your user profile as the value for the parameter /IAM/APPLICATION. Enter the required data for the selection criteria and the variant attributes. immediate archiving is possible: Canceled (10) Flagged for Deletion (64) If you want to archive the respective activities immediately. There are various selection criteria and options available for you to create a variant: Application First. If an activity has further subactivities. if the residence time is 365 days. partners. To create the job. 1. Open archive administration (transaction SARA). only complete activity hierarchies for an issue or subissue (defects. choose Execute . 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 . If the check was successful.14. for reasons of consistency. only those activities are selected that were last changed at least a year ago. The following programs are available for this archiving object: Preprocessing program /IAM/ISSUE_ARCH_PRE The preprocessing program uses the issue status and the chosen selection criteria (for example. Result You have now entered all the data required for the background job.Since. you can then schedule the write program analogously. Enter a name for the variant and choose Maintain . Save the variant. Logging You can specify in which form and with which level of detail the log is to be displayed. Enter the start date and the spool parameters. 2. All rights reserved. Recommendation You can store a default value for the residence time in application-specific Customizing (see Setting Up Application-Specific Customizing). Page 103 of 106 . Procedure 1. For example. Following this. and attachments stored in the system. descriptions. you must specify the application QIM to archive QIM data. activity category. causes) can be archived. specify the activity ID. 1. The selection criteria for the preprocessing program and the write program do not have to match. these must also have 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. You can execute the preprocessing program in test mode or production mode. defect. or effect are archivable. Independent of this. you can define an additional variant that incorporates the relevant lifecycle statuses and a residence time of 0 days. Activity selection To determine the activities to be archived. the preprocessing program checks whether all activities that belong to one activity branch beneath an issue. Only then are the other application-specific selection criteria visible. effects. Residence time You can enter the residence time for activities in the QIM system (in days. then the value is entered automatically in the selection criteria.2 Archiving Issues with /IAM/ISSUE With the archiving object /IAM/ISSUE.14. 4. you must always use a variant and schedule it. the preprocessing program sets the archiving status Marked for Archiving . Enter the technical name of the archiving object and choose Preproc . you can archive issues and their corresponding information. Note that with the following lifecycle statuses. for example. 3.1. residence time) to check for which issues archiving is PUBLIC © 2014 SAP SE or an SAP affiliate company. such as reference objects. see Creating Preprocessing Variants for /IAM/ISSUE 2. regardless of their lifecycle status. if you perform the archiving in English. The delete program is executed automatically after the write program. Note When QIM data is archived. transient texts. all subissues (defects. Usage in ILM Retention Management To be able to use the archiving object /IAM/ISSUE in Information Lifecycle Management (ILM). If the check was successful. If the read was successful. or register other archiving classes. Settings in ILM object Customizing (transaction IRM_CUST) for IAM_ISSUE: Available Time References: Created On (CREATION_DATE) Last Changed On (LAST_CHANGE_DATE) Available Condition Fields: IAM Application (APPLICATION) IAM Authorization Group (AUTH_GROUP) Available Policy Categories: Retention Rules (RTP) Assigned BOR Object: /IAM/ISSUE Prerequisites You have authorization for the activity 14 Archive in the authorization object IAM/I_STAT Authorization Object for Lifecycle Status (Issue) . these texts will be shown in English when you display the archived data at a later stage. For reasons of consistency. In the transaction SARA. create a variant for the preprocessing program and schedule it. effects. create a variant for the write program and schedule it. Procedure 1. 1. PUBLIC © 2014 SAP SE or an SAP affiliate company. effects. Note The residence time is already taken into account in the selection criteria for the preprocessing program (see Creating Preprocessing Variants for /IAM/ISSUE). such as the descriptions of codes stored in Customizing.1 Checks for /IAM/ISSUE The preprocessing program checks whether archiving can run for the selected issues based on the lifecycle status. All rights reserved. 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. and causes are archived as well. only complete issue hierarchy branches can be archived when archiving issues. field /IAM/I_ACT Authorization to Perform Issue-Related Activities . it sets the status to Archived and deletes the data from the database. You can change this setting in Customizing for the archiving object (in the transaction SARA under Goto Customizing Archiving Object-Specific Customizing Technical Settings ). For more information. Result The archived data is deleted from the database but can still be displayed. see Business Object Builder. For more information. If you want to extend the archivability checks. you can use the options in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). see Displaying Archived QIM Data. You have already activated the activities that belong to the issue and its subissues or marked them for archiving. are also archived in one specific language. In the transaction SARA. Delete program /IAM/ISSUE_ARCH_DEL The delete program reads the data from the archive file.possible and then assigns them the archiving status Marked for Archiving . causes) belonging to an issue must be archived as well. the program sets the archiving status Marked for Archiving . Page 104 of 106 . even if you are logged on to the system in another language.2. For more information. archive additional data. For more information. the ILM object IAM_ISSUE is delivered. That means. The assigned activities must already have been archived or be marked for archiving (see also Archiving Activities with /IAM/ACT). see Checks for /IAM/ISSUE 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. 3.14. 4. Procedure 1.2. Enter the following data: Business Object : Enter /IAM/ACT for activities or /IAM/ISSUE for issues. you must always use a variant and schedule it. Reusable BO Usage (corresponds to the application in the component IAM): Enter QIM. you can define an additional variant that incorporates the relevant lifecycle statuses and a residence time of 0 days. To create the job. Logging You can specify in which form and with which level of detail the log is to be displayed. 2. choose Execute . 3. you can.14. for example. Enter a name for the variant and choose Maintain . Independent of this. only those issues (and their subissues) are selected that were last changed at least a year ago. Result You have now entered all the data required for the background job. and causes) are automatically selected as well. specify the issue type and the lifecycle status. 5. 6. for all issues selected their subissues (defects. BO Node Name : Leave the field blank. 2. you must specify the application QIM to archive QIM data. effects. 1. Residence Period : Enter your required residence period for the business object in days. Procedure 1. Recommendation You can store the application QIM in your user profile as the value for the parameter /IAM/APPLICATION. To ensure data consistency.2 Creating Preprocessing Variants for /IAM/ISSUE The preprocessing program selects the issues based on your specified selection criteria and checks whether they can be archived (see Checks for /IAM/ISSUE). the preprocessing program sets the archiving status Marked for Archiving . Enter the start date and the spool parameters. regardless of their status. Open the Customizing activity. You can execute the preprocessing program in test mode or production mode. Residence time You can enter the residence time for issues in the QIM system (in days. immediate archiving is possible: Canceled (10) Flagged for Deletion (64) If you want to archive the respective issues immediately. enter the technical name of the archiving object and then choose Goto Customizing Application-Specific Customizing: Maintain BO-Specific Residence Time . If the check was successful.3 Setting Up Application-Specific Customizing You can store a default value for the response time of a business object in Customizing. Issues with the status Marked for Archiving can then only be displayed in the application but no longer changed. Recommendation You can store a default value for the residence time in application-specific Customizing (see Setting Up Application-Specific Customizing). Enter the technical name of the archiving object and choose Preproc . There are various selection criteria and options available for you to define a variant: Application First. Enter the required data for the selection criteria and the variant attributes. Create a new entry if required. then the value is entered automatically in the selection criteria. Page 105 of 106 . Issue selection To determine the issue to be archived. All rights reserved. PUBLIC © 2014 SAP SE or an SAP affiliate company. you can then schedule the write program analogously. Note that with the following lifecycle statuses. For example. Open archive administration (transaction SARA). Save the variant. SAP Customizing Implementation Guide: Choose Cross-Application Components Processes and Tools for Enterprise Applications Objects and Functions for BOPF Environment Archiving Adapter Maintain BO-Specific Residence Periods . 3. Only then are the other application-specific selection criteria visible. Following this. The selection criteria for the preprocessing program and the write program do not have to match. if the residence time is 365 days. You have two options for doing this: Transaction SARA: First.The activities belonging to the issue or subissue must have one of the following archiving statuses: Marked for Archiving (02) Archived (03) 1. relating to the date of the last change).14. In the results list. you can use various selection criteria. All rights reserved. In archive administration (transaction SARA). you can display the object in the QIM Web application by double-clicking the node ID. Page 106 of 106 . 2. Specify the archiving object and the archive infostructure. you can only call individual objects via their ID. In the search help for the quick access. 3. archived objects are not taken into account. 1. Enter the selection criteria for the objects that you want to display.14.4 Displaying Archived QIM Data You have various options for displaying archived issues and activities: Quick access via the QIM user interface Here. Various infostructures and field catalogs are delivered for display in the archive information system.Result The residence period stored in Customizing is displayed as the default value when you create the preprocessing variant. proceed as follows: 1. enter the ID in the relevant quick access CHIP. To display objects via the archive information system. choose Information System Archive Explorer . 4. PUBLIC © 2014 SAP SE or an SAP affiliate company. For activities: Infostructure /IAM/ACT Field catalog /IAM/ACT For issues: Infostructure /IAM/ISSUE Field catalog /IAM/ISSUE Procedure To display specific individual objects. Archive information system (transaction SARI) Here.