Shulou(Shulou.com)06/01 Report--

Today, I would like to share with you what are the relevant knowledge points about the common questions in the SAP quality management module, which are detailed in content and clear in logic. I believe most people still know too much about this knowledge, so share this article for your reference. I hope you can get something after reading this article.

If you encounter the error message TK430 (client & 1 has an "immutable" status) when creating a decision code or selecting a set using the transaction code QS41 / QS51, KBA 1911886 should be able to solve this problem.

When the preparations are ready, it is time to create an inspection batch. What if you find the following problems during the inspection batch creation process?

Inspection batch number jumps: SAP Note 1832772 explains the possible reasons and provides a solution.

The inspection batch status has always been CRTD, and the system cannot find a suitable inspection plan: KBA 2112741 covers most of the possible causes of this problem

The inspection status SPRQ is missing and the inspection batch does not have quality inspection inventory: please see the explanation given by KBA 2136634.

Once the inspection batch is created, you can move on to the next step-recording the inspection results. If you have problems recording the test results, you can see if the following can help you:

After recording the test results using QE51N or QA32, it is found that the start time of the test result record is actually later than the end time of the test result record: please make sure that SAP Note 2017397 has been called in your system.

If you want to use the function of copying verification results, only to find that there is no relevant configuration menu in the system: KBA 1680949 is sure to help you.

If you find a result recording error after making a use decision, you want to correct it, but the system no longer allows you to modify the result: KBA 1716024 gives you two tips.

The tables of test results in the system are QAMR and QASR,QASE. Do you sometimes get confused about these tables? KBA 1649587 clears up your mind.

When the record of the inspection results is complete, it is necessary to make a decision on the use of the inspection batch. There are a lot of problems when using decisions, and here's a list of problems that customers have encountered:

If you find that the quality inspection inventory in the system does not have a corresponding inspection batch, or although there is an inspection batch with a status of SPRQ, there may be no corresponding quality inspection inventory in the system: you need to manually create and run ZQEVAC20, the program included in SAP Note 48815, in the transaction code SE38. It will list the inventory inconsistencies in the system, you just need to click the small pencil button to correct it.

If the status of an inspection batch is UD, but the use decision code is empty, or the decision code is already used but there is no UD status: the program ZQEVAC22 included in SAP Note 174877 will help you correct the status of the inspection batch.

Note: if you find problem 1 or 2, check if there are self-developed user egress / BADI/ enhancements in the system. Many system data inconsistencies are caused by self-developed code. Note that statements like "commit" and "commit work" generally cannot be used in self-developed user exit / BADI/ enhancements, which can easily lead to data inconsistencies.

Standard SAP systems do not provide the ability to cancel practical decisions, but what if users do have a need for this? Don't worry, SAP Note 33924 provides a user exit that can do this. You just need to activate this user exit and activate the sample code in it.

SAP Note 33924 can only cancel the UD status of the inspection batch, but what if the user wants to transfer the inventory back to the quality inspection inventory? You can execute the program RQEVAC50 in SAP Note 175842 to cancel the inventory movement vouchers generated during the usage decision.

When making the use decision and choosing to use the decision code, the system lists the selection sets of all factories, which may affect the performance of the system and cause trouble to users. How to control the system to display only the selection sets of the factories to which the inspection batch belongs? KBA 2022028 is sure to help you.

If the inspection batch contains one batch and the batch inventory is moved during the usage decision, but the batch inventory table MCHB is not consistent with the actual inventory: make sure that SAP Note 1935699 is included in your system.

After the system upgrade, you find that the field QAVE-VAENAME (the changer of the usage decision) has not been updated after the usage decision is made with the transaction code QA11. This is because SAP Note 1805920 modified the system design, and with this Note, the field QAVE-VAENAME will not be updated until the usage decision is modified using the transaction code QA12.

When using the transaction code QA16 to make a batch collective use decision, the error message QV121 "the selected set code does not exist or the input data is incomplete" appears. This message does not appear until the system is upgraded. What's going on? Check to see if SAP Note 1699641 is included in the system. This Note modifies the system design. You need to check the configuration of the system for using decision selection sets in accordance with KBA 2114045.

SAP Note 1970287 contains more frequently asked questions about usage decisions.

If you use dynamic Modification rules (Dynamic Modification Rule) to control inspection batches in the quality management module, you must look at the following SAP Notes:

SAP Note 86925: this Note explains in detail several system configurations that affect skipping inspection batches (skip lot). If you find that a skipped inspection batch (skip lot) is not generated, then checking the system configuration mentioned in Note will certainly solve your problem.

SAP Note 612299: if you find that a verification phase is performed too frequently or is always skipped, you can refer to the explanation and solution in this Note.

SAP Note 942073: if you are not clear about the logic of when the system modifies the quality level and are not sure how to configure dynamic modification rules, please refer to this Note's explanation of system design.

SAP Note 844979: there are a variety of configurations in the system that will affect the changes in the verification phase. If you have questions about the dynamic modification process, you can use this Note to track this change.

These are all the contents of this article entitled "what are the common problems in the SAP quality management module?" Thank you for reading! I believe you will gain a lot after reading this article. The editor will update different knowledge for you every day. If you want to learn more knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.