How to Post Real-Time Usage Decisions with the Automatic Usage Decision Functionality in SAP Quality Management

  • by Caetano Almeida, Senior Support Engineer, SAP
  • April 17, 2017
Learn the necessary customizing steps and technical prerequisites to implement the automatic usage decision immediately after posting the results recording in SAP Quality Management (QM).
Learning Objectives

Reading this article you will learn:

  • The technical prerequisites to activate the automatic usage decision
  • Implementation of the relevant customizing changes
  • How to switch the event type linkage for inspection lots to trigger the business object event
  • How to post the results recording with an automatic usage decision
  • The SAP Quality Management (QM) functionalities delivered by the SAP Customer Connection process
Key Concept
Usage decision is a key part of the SAP Quality Management (QM) module. As part of the SAP Customer Connection process, the usage decision was enhanced to be performed automatically after the results recording. The SAP Customer Connection process is part of the SAP Influence program and it collects requirements from customers and tries to identify the major pain points for the business users. These requirements are then evaluated, and the most relevant ones are introduced into the standard system by means of a Support Package or an advanced development note, such as SAP Note 2191172.

Usage decision is a key part of the quality inspection process, as it is by means of the usage decision that a material becomes available as part of the inventory, if approved by the quality inspection. The usage decision was typically carried out manually after the results recording, or automatically if you schedule the program RQEVAI30 to run in a background job.

With both of these options you have a delay between recording the results of the last inspection characteristic and posting the usage decision. This delay means that the material is not immediately available to be shipped to the customer or used as a component of a production order. It means there is an unnecessary delay in lead time.

For a long time, companies tried different approaches to avoid this lead time, but now SAP has delivered a standard way to immediately trigger the usage decision after posting the results of the last inspection characteristic.

Review of the Technical Prerequisites to Activate the Automatic Usage Decision

This automatic usage decision functionality is available as of Support Package 16 of enhancement package 6 and Support Package 9 of enhancement package 7. Alternatively, it can be implemented with SAP Note 2161987 on systems running lower Support Packages of enhancement packages 6 and 7.

Even though it is not mandatory, I recommend the implementation of SAP Notes 2234667 and 2179854, as these are corrections to program errors related to the automatic decision.

If the system is already running on the mentioned or higher Support Packages, you don’t need to worry about the implementation of SAP Note 2161987, and you can go directly to the “Switching on the Event Type Linkage for Inspection Lots” section.

However, if the system is running a lower Support Package, the first step to activate the automatic usage decision is to implement this note in the system. This note can be directly accessed in the SAP Support Launchpad through the link https://launchpad.support.sap.com/#/notes/2161987 or you can download it directly in transaction code SNOTE.

This note must be very carefully implemented, as it contains several manual steps.

SAP Note 1729128 is a prerequisite, and it should be implemented even before you start with the manual steps for implementation.

Because SAP Note 2161987 brings changes in the Data Dictionary, it brings attached the report NOTE_2161987 (Figure 1). This report must be manually created in transaction code SE38 and executed before the note implementation in transaction code SNOTE.


Figure 1
Report NOTE_2161987 attached to SAP Note 2161987
 

You can change the report name to ZNOTE_2161987 so that it won’t use the SAP namespace and subsequently you can avoid the request of an access key. Figure 2 shows the report main screen.


Figure 2
Execution of report ZNOTE_2161987

Caetano Almeida

Caetano Almeida is a computer engineer with an MBA in IT management. He has more than nine years of experience in production planning, with the last six years working at SAP Support, where he supports SAP customers and writes documentation and correction notes.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.