Register Login

Inspection lot, Reversal of goods movements from UD

Updated May 18, 2018

You can no longer reverse goods movements that were created from the transactions of the usage decision.

You can use the attached program corrections to reset stock transfer postings for the usage decision.

In doing so, note the following:

1. The system analyses all goods movements that have already been executed and summarizes them in a new material document, which may contain several lines if required. 
If it is possible to post this document in the stock management, the inspection lot is also corrected and, if required, the Quality Management Information System is updated. After the reset has been successfully carried out, the inspection lot, related to the stocks, has the status that it had before the first stock credit entry. The system does not reset the usage decision. After the usage decision transfer posting, if you make further transfer postings in the stock management, meaning that you cannot reset the usage decision transfer postings due to missing availability, you must reverse these postings first.

2. The goods movement is carried out in each case with the reversal movement type (document-neutral reversal). The original documents are not reversed in relation to the document. This may lead to valuation condition deviations in the accounting.

3. We do not support the resetting of postings for materials that require serial numbers.

4. This correction program does not enable you to reverse goods movements for inpection lots for handling units (HU).

5. The restrictions from Note 318278 also apply here. For example: In the case of subcontracting, the system creates an additional posting line with movement type 543 when you post into the unrestricted use stock. When you use the report that is described in this note (the MB_CREATE_GOODS_MOVEMENT function module is technically executed there) to reverse the material document, you must carry out a goods movement with movement type 544. According to Note 318278, this is not possible.

6. Any batch status changes that you may have made are not cancelled.

7. The system does not delete batches that have been created in the usage decision during a transfer posting. The classification of these batches is also not changed.

8. Within the adjustment posting, in Release 4.x, the system also adjusts the reference records between the material document and inspection lot. This may lead to an incorrect description of the reference type when you display the material document for the inspection lot. In Release 3.x, the system deletes the reference records to ensure that individual documents cannot be cancelled several times.

9. The program does not contain any of its own authorization checks and you should only use it with utmost care and ONLY after a successful test. You should ONLY apply the program in exceptions and not as part of the standard procedure.

10. You should not, under any circumstances, change the logic that was implemented in the program to generate material documents or to update the inspection lot quantities and the inspection lot status, as this may result in inconsistent data. Since this is a program that is not contained in the standard system, you can deal with problems that are created as a result of the program application in the same way as problems that have arisen as a result of a customer modification.

11. If an industry solution is active in your system (for example, IS-CWM), open a CSN message under the relevant IS component BEFORE you implement this note to check whether problems may occur when you execute this report.

To implement the program, proceed as follows:

1. Create an executable program and implement the attached source code corrections. Then transfer the Dictionary text to maintain the text for the PRUEFLOS selection parameter.

2. If you a use a release that is lower than 4.6, you must create function group ZQMB. In this function group, you must create function module 'ZQMB_QAMB_CANCEL'. Flag the function module as an update function module (Start immediately) and include the 'I_QAMB_TAB' table interface parameter (type specification LIKE, reference structure QAMB). You must then include the 'ERROR_DURING_UPDATE' exception and implement the attached source code corrections.

3. Use transaction OMJJ to enter further entries in level 'Allowed transactions' (table T158B) for transaction code 'QA11' (Record Usage Decision). The movement types for which these entries must be created are derived from the system settings for the goods movements for the usage decision (table TQ07M): You must determine the reversal movement type for every movement type that is entered in table TQ07M with the key VMENGE01 - VMENGE09, and you must include the relevant entry in the above-mentioned table. You can use the T156N table to determine the reversal movement type: You can enter the movement type (BWART) and function code (FCODE) ST to determine the reversal movement type (BWART_NEXT). For missing entries, the system issues error M7 096 'Goods movement not possible with mvmt type &'.

Other Attributes

Transaction codes