Reversal of Usage Decision for insp type 10 lot

Dear Friends,
I am using the inspection type 10 for the inspection during despatch.
Please explain the process of reversing the usage decision specifically for a lot of insp type 10.
Regards,
Avinash

If the UD was already made, why do you have to cancel the UD?
You can change a UD via QA12.
You can cancel the delivery document.
Since inspection type 10's don't control stock, (they can block the PGI on the delivery), I wouldn't see any need to actually cancel the inspection lot once a UD was made.
Craig

Similar Messages

Usage decision for movment type 323

Hello
Can anyone tell me how I can post movment type 323 through QA11 with a usage decision?
I can see in config Quality Management>Quality Inspection>Inspection Lot Completion>Define Inventory Postings that there is a posting UD TRANSFER02 that uses 323 but I cannot see how this is posted through transaction QA11!
Thanks
Sue

hello,
Can you do this. in the config path Quality Management>Quality Inspection>Inspection Lot Completion>Define Inventory Postings , create a new entry with 08 suffix. Assign mvt type 323 to it.
In my system it comes with a description "other qty posting". Save it. now this new entry will show up in qa 11 in the inspection lot stock tab where you could post the quantity with this entry to trigger 323 mvt type.
Now go OMJJ and check for mvt 323 whether QA11 is in the allowed transactions , if not add it there/. ( Caution: 323 isnt meant to work with QA11)
now run qa11, it works fine.
But my question is if you arent accepting , rejecting or doing a sample, or other functions described for QA 11 UD , then you can just do a MB1B 323 and this should serve your purpose, why do this though QA11.
Hope this helps
Thanks,

QA40 making usage decision for 03 lots with rejected MIC also

Hi Friends ,
QA40 is making Usage decision for 03 type lots having defects also and also for the lost having rejected MICs . can anybody explain why its so because SAP help has mentioned that for automatic UD there should be no rejected MIC .
Regards

What you are thinking about is QA10, not QA40.
QA40's criteria for making the UD is based upon the order status. I.e. the three radio buttons in the screen, orders completed, technically complete and confirmed.
The idea is once one of these statuses is reached, you wouldn't have any more testing. Also, it is not unusual to have out of spec results during in-process testing. In many industries that would be the norm, not the exception as often times a step in the process has a test repeatedly perform until a certain result is achieved. % water or % solids for instance.
03 lots also do not control stock. So it's not as critical that tests be in spec at this point to perform the UD.
Craig

No Automatic Transfer order creation upon usage decision for 553 mtype

Scenario: We have quality and warehouse management active. Goods receipt is done against a purchase order. Stock comes into 902 storage type under stock category u201CQu201D. From 902 storage type, Goods issue to scrapping under quality( using IM movement type 553 ) is done using QA11. Normally, once GI to scrap under quality is done at IM level, WM movement type 551 gets triggered automatically in the background which creates a transfer order to move stock from 902 to 999 storage type under u201CQu201D stock category.
Problem: System unable to find storage bin for storage type 902 Q.
In our system, automatic TO creation from TR isnu2019t happening once the usage decision for 553 movement type happens. The TO creation process couldnu2019t recognize the stock which is available as u201CQu201D. It throws an error message u201Csource storage bin could not be foundu201D at the time of TO creation from TR. Putaway strategy for the physical storage types is FIXED BIN, MIXED STOCK ALLOWED and ADDITION TO EXISTING STOCK. 902 storage type has ADDITION TO EXISITNG STOCK and MIXED STOCK as a putaway strategy.
We have already activated auto TO creation settings at WM-IM reference movement types interface configuration.
Is there any setting missing at QM-WM interface?
Can someone please tell us a methodology to activate this transfer order creation process (WM mtype 551) for 553 IM mtype ?
Thanks in advance. Please reply.
Regards
Preetinder Singh
Phone: 404-468-8422

Hello,
I do not understand your scenario , u are saying are posting inspection lot to non WM storage location and again saying system can not find bin automatically.
"A transfer requirement (movement type 311 / destination u201C921 Transferu201D) is created after the inspection lot posting (QA11) but the auto-creation functionality is not possible since the u201CSystem cannot find source storage binu201D.
How can this auto-creation of a transfer order be realized since it is possible to create the transfer order manually via LB11 (entering source u201C902u201D / storage bin u201CPurchase Order no.u201D)?
The system cannot find the storage bin automatically.
Thank you in advance!"
Please let me know are u using quality interim storage area. If you clear material from quality and want material to go to bin then it should be warehouse managed storage location.
Regards,
Prashant

Changing posting date at usage decision for handle units. How?

Does anybody know how to change posting date at usage decision for handle units (HU)?
If the material is not managed by HU, SAP allows this modification (there's a button with a hat on it referring the material document header).
For HU I cannot seem to change posting date!
Seba

Yes it's possible! Well,...unless for versions 4.6C, 4.7 and ECC 5.
I've found SAP Note #752131 by which SAP declares that you can create the pushbutton from the Screen Painter referring the document header.
That's all,.....so simple, and it works fine!
This note applies ONLY to version 4.6C, 4.7and ECC 5 (which is the version the customer I am with has installed).
Thanks anyway.
Sebas

Usage Decision for an insp. lot

dear all
i want to make UD for an insp. lot of insp. type 06(return delivery).when i made ud it did not ask me for posting of that material.there is no insp. lot stock tab.can anybody help me to resolve this issue.

hi
inspection type 06 is non stock relevant ,hence you cannot able to post the material .
Processing materials as non-stock-relevant goods
If a material is not stock relevant, the system does not valuate and track the quantity of goods in an inspection lot. All inspection lots with the following inspection lot origins are not stock relevant:
·        02 - Goods issue
·        03 - Production
·        06 - Return from customer
·        07 - Audit
·        10 - Delivery to customer with sales order
·        11 - Delivery to customer without sales order
·        12 - Delivery (general)
·        13 - Production inspection on basis of run schedule header
·        14 - Plant maintenance
·        17 Externally triggered inspection
Posting stock-relevant materials to inspection stock
In inspection stock, QM has exclusive control over the material stock. This means that the material can only be posted in and out of inspection stock via the inspection lot. Materials can be posted to inspection stock for the following inspection lot origins:
·        01 - Goods receipt
·        04 - Goods receipt from production
·        05 - Miscellaneous goods receipt
·        08 - Stock transfer
·        09 - Recurring inspection
regards
thyagarajan

Solution to Non-Reversal of Usage Decision

Hi Experts,
I have facing an Issue over Goods movement .
Issue is User has done GR against PO using Transaction MIGO with mvmt Type - 101 and GR is posted to Quality stock for inspection , there user has accepted the usage Decision using QA32 and posted the Stock to Unrestricted using movement type -321. But Now they want to cancel the GR earlier done because they have posted wrong Quantity.
Now since reversal of UD is not a standard solution and also is not a immediate solution to this problem, so what solution i should suggest to client to have his requirement fulfilled for this Issue without doing reversal of UD. We can think of Developing Zprogram of reversal of UD later.
your response will be appreciated.
Thanks in Advance
Regards
kaushik Ghosh

It is time to correct something.
first of all the initial question was already a frequently discussed question.
The question " will any accounting entries get effected" is again a basic and frequently discussed question.
You have to search before posting - this is a rule in SCN
Unfortunately I was not present to reject this question right away, as this would have been a better solution, as it had forced you to search. But rejecting it now will only create damage since you got wrong advice.
Not sure where all these myths come from and why they are spread.
A return is something quite different from a cancellation, even that both lead to zero stock at the end, a return is used in external processing, it is about sending materials back to your vendor, a cancellation of a receipt is pure internal processing to correct a wrong entered value (no physical movement). It is statistically not the same, receiving and cancelling it again is just as good as not received anything as it nullifies. Receiving and doing a return are different processes , an inbound and an outbound process, it is visible separately. It is taken into account in vendor evaluation.
To cancel the receipt movement after the usage decision you can use MIGO, but do not choose cancel material document, because the material document only knows that the stock is in quality status, which is not the case anymore after a usage decision.
just do again goods receipt - reference to PO - but change then the movement type to the cancellation movement type (102).
Then goto the detail into WHERE tab and change status to the stock status your stock has right now.
Do you really think that "Developing Zprogram of reversal of UD" would do any good (or just create inconsistencies) if the processes and basic handling of MIGO are not even understood?

QM Module: Usage Decision for Inspection Lot

Dear All,
After made of Usage Decision the Notification will receive to the respective Managers as mentioned below:
IF Usage Decision is QCR then Notification will receive to only Marketing Manager
IF Usage Decision is MR then Notification will receive to Logistics Manager, QC manager and Production Manager
IF Usage Decision is MA then Notification will receive to Logistics Manager, QC manager and Production Manager
IF Usage Decision is MAC then Notification will receive to Logistics Manager, QC manager and Production Manager
IF Usage Decision is QCA then Notification will receive to Logistics Manager, Marketing Manager and Production Manager
Any Suggestions pls, workflow logic in this requirement.
Is there any Solutions without ABAP coding.
Thanks and Regards,
Prabhakar Dharmala
Message was edited by:
Prabhakar Dharmala

I'm sorry, I am not sure if I understand any more now, but one quick check: When you write RULE, are you specifically meaning RESPONSIBILITY RULE?
I said that a rule is needed to specify work item agents (workflow step specification of selected agents). It is not quite true, you can specify the selected agents in other ways such as using expressions etc. You could therefore create a subtype of your business object where you define virtual attributes for the different agents you mentioned, i.e. a virtual attribute AG_MARKETING_MANAGER, another one called AG_LOGISTICS_MANAGER, a third one called AG_QC_MANAGER, and finally one called AG_PRODUCTION_MANAGER. These should have the data type TSWHACTOR.
However, you are asking for a method that does not involve rules, AND does not involve ABAP coding. I think you are out of luck there, because the virtual attributes will require (some) ABAP coding, and of course this approach is of more interest if these managers can be determined based on data that are maintained anyway - to save you the addition maintenance of the responsibility matrix in the workflow (responsibility) rule.
You can obtain exactly the same by creating a workflow rule that takes whatever parameters are relevant, plus the Usage Decision.
If you want to send a single step/mail to all the managers (I couldn't quite understand if you wanted a single step to a varying number of managers or a varying number of steps) the latter solution would be the best one, as the rule would give you the correct list of managers without any additional steps in the workflow.
If you create virtual attributes you can use container operations in the workflow to put all the relevant managers into one multiline container element. But that seems rather awkward compared to creating a workflow rule.

Error during usage decision for Test Equipment

Hi,
I have completed results recording for Test Equipment using QE51N (results closed and confirmation completed). When I tried to make usage decision (QA11) for the lot the pop-up message shows as "Not all equipment is valuated! Do you want to force inspection completion. I also noticed that in equipment tab of qa11 code valuation column shows as Not Valuated.
I request you to help me to solve this problem.
Thanks & Regards
V.Devaraj

HI,
You may try changing the valuation mode in IA06. In the inspection characteristic overivew, click on details -> operation, scroll down, you will find Quality management inspection points -> maintain automatic valuation based on inspection points.
The changes if made will be effective only for the next inspeciton lots.
Regards,
M.M

Reverse the usage decision

Dear
I wrongly give a UD as accepted and material is posted as unrestricted automatically
1.Give me a solution that how i can reverse this material from unrestricted,
2.If i change my UD material will be reverse to inspection stock?
3.How we can reverse a UD
Faisal

1.To reverse Stock posting : Using SAP note 175842 you can reverse stock to inspection stock then you can cancel the original material document
2.To cancel UD : Exit QEVA0008 can be used. Also explore SAP Note 33924
This will only cancel the UD.

Number Range for '01' type inspection lot

Dear QM gurus,
Inspection lot numebr getting increment by two instead one when doing GR against purchase order, please guide.
Thanks in advance
Kailash Thakkar

It is impossible in SAP standard because the inspeciton lot origin can have one number range only.
You can check why it is impossible in configuration.
Customizing > Quality Management > Quality Inspection > Inspection Lot Creation > Maintain Inspection Lot Origins and Assign Inspection Types
Regards
Luke

Wrong usage decision

Dear sirs,
I have one issue.
One of materials is assigned to quality.
GR (101 mvt type) is posted for that material for 20000 litres and inspection lot is created.
While performing transaction QA32, usage decision is to be made with 20000 litres and this much quantity is to be moved from quality stock to unrestricted stock.
Unfortunately user has posted usage decision with zero quantity.
With this,20000 litres of stock is left in quality only.
Now how can I change usage decision?
Please suggest me the solution
Regards,
Sastry

Dear sir,
When I take QA32 and try to post usage decision for the same inspection lot, system is throwing error message "The function you selected can not be carried out"
When I try to post "return deliery to vendor " using MIGO keeping the stock type as Quality stock, then also system throws message "You do such changes in quality"
Please help me
Regards,
Sastry

The Usage decision cancellation & quantity reversal

Daer All,
While cancelling the Goods receipt, system gives the error Deficit of SL Stck.in qual.insp 10 M : 5000017/1 PMT1 RMST as the usage decision of quality lot generated for the goods receipt is done.
I want to cancel/reverse the usage decision made & the quantity release from the lot to be initialised, so I can cancel the Goods receipt.
I have applied the Note 175842 & User Exit QEVA0008
But when I cancel the usage decision in QA11, only the usage decision is cancelled. The quantity which is moved to un-restricted stock after usage decision is not reversed.
I want to reverse the quantity, so i can cancell the goods receipt.
Regards,
Prakash

Hi Prakash,
Please note that SAP doesnt provide an option to reverse a UD once its done.
Now to solve your issue, Since you have already done QA inspection the stock is moved to Un-res.
So when you cancel the Material/GR document, select the stock type as un-res then system will allow to post the document.
Regards,

PP - QM: Reversal of the usage decision

Hi Gurus,
We have completed Result Recording using QE51N transaction and Usage decision using QA11. It has posted a stock from QI to Unrestricted use. Now I want to take it back from Unrestricted use to QI. This needs reversal of usage decision (What I think).
Can you suggest me the proper way of performing the said transaction?
I will really appreciate your concern.
Thanks
Shiv

R/3 note no. 175842 14.12.2001 Page 1
 Number 0175842
 Version 0021 from 29.11.2001
 Status Released for customer
 Set by SAP AG on 03.12.2001
 Language EN
 Short text Inspection lot: Reversal of goods movements from UD
 Administrator SAP AG
 Component QM-IM-UD Inspection Lot Completion
 Long text
 Symptom
 Goods movements, which were created from the transactions of the usage
 decision, can no longer be reversed.
 Additional key words
 QA11, QA12, QA14, MBST, MF41
 Inspection lot, usage decision, goods movements, reversal, material
 document
 Cause and preconditions
 Presently, the function is not provided in the standard system.
 Solution
 The function is not provided in the standard system up to and including
 Release 4.6C.
 When you do this bear the following in mind:
 1. Using the attached program corrections, stock transfer postings can
 be reset for the usage decision.If it is possible to post this
 document in the stock management, the inspection lot is also
 corrected and the Quality Management Information System is if
 necessary updated.After the reset has been successfully carried out,
 the inspection lot, related to the stocks, has the status before the
 first stock credit entry.The usage decision is not reset.If, after
 the usage decision, further transfer postings are carried out in the
 stock management which lead to the usage decision transfer postings
 not being able to be reset due to missing availability, these
 postings must be reversed 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 related to the document.This may lead to deviations in
 the accounting caused by valuation.
 3. Resetting postings for materials requiring serial numbers is not
 supported.
 4. With this correction program, you cannot reverse goods movements for
 inpection lots for handling units (HU).
 5. Batch status changes which have possibly been carried out are not
 cancelled.
 6. Batches which have been created in the usage decision during a
 transfer posting are not deleted.The classification of these batches
 is not changed either.
 Page 2
 7. Within the adjustment posting, in Release 4.x, the reference records
 are also adjusted between the material document and inspection
 lot.This can possibly lead to an incorrect description of the
 reference type when displaying material documents for the inspection
 lot.In Release 3.x, the reference records are deleted in order to
 make sure that individual documents cannot be cancelled several
 times.
 8. The program does not contain any own authorization checks and should
 be used with utmost care and ONLY after a successful test. The
 program should ONLY be applied in exceptions and should not be part
 of the standard procedure.
 9. The logic implemented in the program for the generation of material
 documents or for the update of inspection lot quantities and
 inspection lot status should under no circumstances be be changed as
 this might lead to inconsistent data. Since this is a program that is
 not contained in the standard system, problems that are created as a
 result of the program application can be dealt with as problems that
 have arisen as a result of a customer modification.
 To implement the program, proceed as follows:
 1. Create an executable program and copy the attached source code.Then
 maintain the text for selection parameter PRUEFLOS by transferring
 the Dictionary text.
 2. If you a use a Release < 4.6, you must create the 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 table interface parameter
 'I_QAMB_TAB' (type specification LIKE, reference structure QAMB).
 Afterwards you must include exception 'ERROR_DURING_UPDATE' and
 implement the attached source code.
 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):The reversal movement type must be
 determined for every movement type that is entered in table TQ07M
 with the key VMENGE01 - VMENGE09 and the corresponding entry must be
 included in the above-mentioned table.You can use table T156N for
 determining the reversal movement type:You can determine the reversal
 movement type by entering the movement type (BWART) and function code
 (FCODE) ST (BWART_NEXT).For missing entries, the system generates
 error M7096 'Goods movement not possible with mvmt type &'.
 Source code corrections
 Page 3
 Valid releases
 R/3 Standard 46C - 46D
 46A - 46B
 45A - 45B
 40A - 40B
 30F - 31I
 Other components
 QM-IM Quality Inspection
 Reference to related notes
 Number Short text
 0033924 Cancelling usage decisions
 0048815 Checking possible inconsistencies between MM and QM
 Page 4
 Assigned correction instructions
$$----
$$
$ Correction Instr. : 0120024545 0000111772 $
$ Software Component : SAP_APPL SAP Application $
*$----
$*
$ Validity : 40A SAPKH40A01 - SAPKH40A25 $
$ : 40B All Patches $
$ : 45A All Patches $
$ : 45B All Patches $
*$----
$*
$ Changes/Objects Not Contained in Standard SAP System $
$$----
$$
 *& Object FUNC ZQMB_QAMB_CANCEL
 *& Object Header FUGR ZQMB
 *& FUNCTION ZQMB_QAMB_CANCEL
 *>>>> START OF INSERTION <<<<
 UPDATE QAMB FROM TABLE I_QAMB_TAB.
 IF NOT SY-SUBRC IS INITIAL.
 RAISE ERROR_DURING_UPDATE.
 ENDIF.
 *>>>> END OF INSERTION <<<<<<
 *& Object REPS RQEVAC50
 *& Object Header PROG RQEVAC50
 *& REPORT RQEVAC50
 *>>>> START OF INSERTION <<<<
 REPORT RQEVAC50 MESSAGE-ID QA.
 TYPES:
 T_QAMB_TAB LIKE QAMB OCCURS 0,
 T_MKPF_TAB LIKE MKPF OCCURS 0,
 T_MSEG_TAB LIKE MSEG OCCURS 0.
 PARAMETERS:
 PRUEFLOS LIKE QALS-PRUEFLOS OBLIGATORY MEMORY ID QLS.
 DATA:
 G_MSGV1 LIKE SY-MSGV1,
 G_QALS LIKE QALS,
 G_QALS_LEISTE LIKE QALS,
 G_QAMB_TAB TYPE T_QAMB_TAB,
 G_QAMB_VB_TAB TYPE T_QAMB_TAB,
 G_MKPF_TAB TYPE T_MKPF_TAB,
 G_MSEG_TAB TYPE T_MSEG_TAB,
 G_SUBRC LIKE SY-SUBRC.
 START-OF-SELECTION.
 Page 5
 PERFORM ENQUEUE_QALS USING PRUEFLOS
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM READ_QALS USING PRUEFLOS
 G_QALS
 G_QALS_LEISTE
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID 'QA' TYPE 'S' NUMBER '102'
 WITH PRUEFLOS.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM CHECK_LOT USING G_QALS
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 CASE G_SUBRC.
 WHEN 128.
 G_MSGV1 = 'Material & is serialized'.
 REPLACE '&' WITH G_QALS-MATNR INTO G_MSGV1.
 WHEN 64.
 G_MSGV1 = 'Lot & is not stock relevant'.
 WHEN 32.
 G_MSGV1 = 'Lot &: No stock transferred'.
 WHEN 16.
 G_MSGV1 = 'Lot & is cancelled'.
 WHEN 8.
 G_MSGV1 = 'Lot & is archived'.
 WHEN 4.
 G_MSGV1 = 'Lot & is blocked'.
 WHEN 2.
 G_MSGV1 = 'Lot & is HU managed'.
 ENDCASE.
 REPLACE '&' WITH PRUEFLOS INTO G_MSGV1.
 MESSAGE ID '00' TYPE 'S' NUMBER '208'
 WITH G_MSGV1.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM READ_QAMB USING G_QALS
 G_QAMB_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID 'QA' TYPE 'S' NUMBER '068'
 WITH PRUEFLOS.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM READ_MKPF USING G_QAMB_TAB
 G_MKPF_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 Page 6
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM CHECK_MKPF USING G_MKPF_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID 'QA' TYPE 'S' NUMBER '068'
 WITH PRUEFLOS.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM READ_MSEG USING G_MKPF_TAB
 G_MSEG_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM CHECK_MSEG USING G_MSEG_TAB
 G_QAMB_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID 'QA' TYPE 'S' NUMBER '068'
 WITH PRUEFLOS.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM CREATE_GOODS_MOVEMENT USING G_QALS
 G_MSEG_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID 'QA' TYPE 'S' NUMBER '068'
 WITH PRUEFLOS.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 PERFORM POST_GOODS_MOVEMENT.
 PERFORM POST_DATA USING G_QALS
 G_QALS_LEISTE
 G_QAMB_TAB
 G_QAMB_VB_TAB
 G_SUBRC.
 IF NOT G_SUBRC IS INITIAL.
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ELSE.
 COMMIT WORK AND WAIT.
 G_MSGV1 = 'inspection lot &'.
 REPLACE '&' WITH PRUEFLOS INTO G_MSGV1.
 MESSAGE ID '00' TYPE 'S' NUMBER '368'
 Page 7
 WITH 'Stock posting reversed for ' G_MSGV1.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 Form ENQUEUE_QALS *
 Los sperren *
 FORM ENQUEUE_QALS USING P_PRUEFLOS LIKE QALS-PRUEFLOS
 P_SUBRC LIKE SY-SUBRC.
 CLEAR: P_SUBRC.
 CALL FUNCTION 'ENQUEUE_EQQALS1'
 EXPORTING
 PRUEFLOS = P_PRUEFLOS
 EXCEPTIONS
 FOREIGN_LOCK = 1
 SYSTEM_FAILURE = 2
 OTHERS = 3.
 P_SUBRC = SY-SUBRC.
 ENDFORM. " ENQUEUE_QALS
 Form READ_QALS *
 Prüflos lesen *
 FORM READ_QALS USING P_PRUEFLOS LIKE QALS-PRUEFLOS
 P_QALS LIKE QALS
 P_QALS_LEISTE LIKE QALS
 P_SUBRC LIKE SY-SUBRC.
 CLEAR: P_SUBRC.
 CALL FUNCTION 'QPSE_LOT_READ'
 EXPORTING
 I_PRUEFLOS = P_PRUEFLOS
 I_RESET_LOT = 'X'
 IMPORTING
 E_QALS = P_QALS
 EXCEPTIONS
 NO_LOT = 1.
 P_SUBRC = SY-SUBRC.
 IF P_SUBRC IS INITIAL.
 P_QALS_LEISTE = P_QALS.
 ELSE.
 CLEAR: P_QALS,
 P_QALS_LEISTE.
 ENDIF.
 ENDFORM. " READ_QALS
 Form CHECK_LOT *
 Page 8
 Prüflos prüfen *
 FORM CHECK_LOT USING P_QALS LIKE QALS
 P_SUBRC LIKE SY-SUBRC.
 DATA:
 L_STAT LIKE JSTAT,
 L_STAT_TAB LIKE JSTAT OCCURS 0 WITH HEADER LINE.
 P_SUBRC = 128.
 */Serialized Material
 IF NOT P_QALS-SERNP IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 64.
 ENDIF.
 */BERF
 CALL FUNCTION 'STATUS_CHECK'
 EXPORTING
 OBJNR = P_QALS-OBJNR
 STATUS = 'I0203'
 EXCEPTIONS
 STATUS_NOT_ACTIVE = 2.
 IF NOT SY-SUBRC IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 32.
 ENDIF.
 */BTEI & BEND
 CLEAR L_STAT. CLEAR L_STAT_TAB. REFRESH L_STAT_TAB.
 L_STAT-STAT = 'I0219'. APPEND L_STAT TO L_STAT_TAB. "BTEI
 L_STAT-STAT = 'I0220'. APPEND L_STAT TO L_STAT_TAB. "BEND
 CALL FUNCTION 'STATUS_OBJECT_CHECK_MULTI'
 EXPORTING
 OBJNR = P_QALS-OBJNR
 TABLES
 STATUS_CHECK = L_STAT_TAB.
 IF L_STAT_TAB[] IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 16.
 ENDIF.
 */LSTO & LSTV
 CLEAR L_STAT. CLEAR L_STAT_TAB. REFRESH L_STAT_TAB.
 L_STAT-STAT = 'I0224'. APPEND L_STAT TO L_STAT_TAB. "LSTO
 L_STAT-STAT = 'I0232'. APPEND L_STAT TO L_STAT_TAB. "LSTV
 CALL FUNCTION 'STATUS_OBJECT_CHECK_MULTI'
 EXPORTING
 Page 9
 OBJNR = P_QALS-OBJNR
 TABLES
 STATUS_CHECK = L_STAT_TAB.
 IF NOT L_STAT_TAB[] IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 8.
 ENDIF.
 */ARSP & ARCH & REO1 & REO2 & REO3
 CLEAR L_STAT. CLEAR L_STAT_TAB. REFRESH L_STAT_TAB.
 L_STAT-STAT = 'I0225'. APPEND L_STAT TO L_STAT_TAB. "ARSP
 L_STAT-STAT = 'I0226'. APPEND L_STAT TO L_STAT_TAB. "ARCH
 L_STAT-STAT = 'I0227'. APPEND L_STAT TO L_STAT_TAB. "REO3
 L_STAT-STAT = 'I0228'. APPEND L_STAT TO L_STAT_TAB. "REO2
 L_STAT-STAT = 'I0229'. APPEND L_STAT TO L_STAT_TAB. "REO1
 CALL FUNCTION 'STATUS_OBJECT_CHECK_MULTI'
 EXPORTING
 OBJNR = P_QALS-OBJNR
 TABLES
 STATUS_CHECK = L_STAT_TAB.
 IF NOT L_STAT_TAB[] IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 4.
 ENDIF.
 */SPER
 CALL FUNCTION 'STATUS_CHECK'
 EXPORTING
 OBJNR = P_QALS-OBJNR
 STATUS = 'I0043'
 EXCEPTIONS
 STATUS_NOT_ACTIVE = 2.
 IF SY-SUBRC IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 2.
 ENDIF.
 */HUM
 CALL FUNCTION 'STATUS_CHECK'
 EXPORTING
 OBJNR = P_QALS-OBJNR
 STATUS = 'I0443'
 EXCEPTIONS
 STATUS_NOT_ACTIVE = 2.
 IF SY-SUBRC IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 0.
 ENDIF.
 Page 10
 ENDFORM. " CHECK_LOT
 Form READ_QAMB *
 QAMBs lesen *
 FORM READ_QAMB USING P_QALS LIKE QALS
 P_QAMB_TAB TYPE T_QAMB_TAB
 P_SUBRC LIKE SY-SUBRC.
 CLEAR: P_SUBRC.
 SELECT * FROM QAMB INTO TABLE P_QAMB_TAB
 WHERE PRUEFLOS = P_QALS-PRUEFLOS
 AND TYP = '3'.
 P_SUBRC = SY-SUBRC.
 ENDFORM. " READ_QAMB
 Form READ_MKPF *
 Read material document header *
 FORM READ_MKPF USING P_QAMB_TAB TYPE T_QAMB_TAB
 P_MKPF_TAB TYPE T_MKPF_TAB
 P_SUBRC LIKE SY-SUBRC.
 DATA:
 BEGIN OF L_MKPF_KEY_TAB OCCURS 0,
 MBLNR LIKE MKPF-MBLNR,
 MJAHR LIKE MKPF-MJAHR,
 END OF L_MKPF_KEY_TAB.
 DATA:
 L_QAMB LIKE QAMB,
 L_MKPF LIKE MKPF,
 L_TRTYP LIKE T158-TRTYP VALUE 'A',
 L_VGART LIKE T158-VGART VALUE 'WQ',
 L_XEXIT LIKE QM00-QKZ.
 P_SUBRC = 4.
 LOOP AT P_QAMB_TAB INTO L_QAMB.
 L_MKPF_KEY_TAB-MBLNR = L_QAMB-MBLNR.
 L_MKPF_KEY_TAB-MJAHR = L_QAMB-MJAHR.
 COLLECT L_MKPF_KEY_TAB.
 ENDLOOP.
 LOOP AT L_MKPF_KEY_TAB.
 CALL FUNCTION 'ENQUEUE_EMMKPF'
 EXPORTING
 MBLNR = L_MKPF_KEY_TAB-MBLNR
 MJAHR = L_MKPF_KEY_TAB-MJAHR
 EXCEPTIONS
 FOREIGN_LOCK = 1
 Page 11
 SYSTEM_FAILURE = 2
 OTHERS = 3.
 IF NOT SY-SUBRC IS INITIAL.
 L_XEXIT = 'X'.
 EXIT.
 ENDIF.
 CLEAR: L_MKPF.
 CALL FUNCTION 'MB_READ_MATERIAL_HEADER'
 EXPORTING
 MBLNR = L_MKPF_KEY_TAB-MBLNR
 MJAHR = L_MKPF_KEY_TAB-MJAHR
 TRTYP = L_TRTYP
 VGART = L_VGART
 IMPORTING
 KOPF = L_MKPF
 EXCEPTIONS
 ERROR_MESSAGE = 1.
 IF NOT SY-SUBRC IS INITIAL.
 L_XEXIT = 'X'.
 EXIT.
 ELSE.
 APPEND L_MKPF TO P_MKPF_TAB.
 ENDIF.
 ENDLOOP.
 IF NOT L_XEXIT IS INITIAL.
 EXIT.
 ELSE.
 P_SUBRC = 0.
 ENDIF.
 ENDFORM. " READ_MKPF
 Form READ_MSEG *
 MSEGs lesen *
 FORM READ_MSEG USING P_MKPF_TAB TYPE T_MKPF_TAB
 P_MSEG_TAB TYPE T_MSEG_TAB
 P_SUBRC LIKE SY-SUBRC.
 DATA:
 L_MKPF LIKE MKPF,
 L_MSEG_TAB LIKE MSEG OCCURS 0 WITH HEADER LINE,
 L_TRTYP LIKE T158-TRTYP VALUE 'A',
 L_XEXIT LIKE QM00-QKZ.
 P_SUBRC = 4.
 LOOP AT P_MKPF_TAB INTO L_MKPF.
 CLEAR: L_MSEG_TAB. REFRESH: L_MSEG_TAB.
 CALL FUNCTION 'MB_READ_MATERIAL_POSITION'
 EXPORTING
 Page 12
 MBLNR = L_MKPF-MBLNR
 MJAHR = L_MKPF-MJAHR
 TRTYP = L_TRTYP
 */ ZEILB = P_ZEILE
 */ ZEILE = P_ZEILE
 TABLES
 SEQTAB = L_MSEG_TAB
 EXCEPTIONS
 ERROR_MESSAGE = 1.
 IF NOT SY-SUBRC IS INITIAL.
 L_XEXIT = 'X'.
 EXIT.
 ELSE.
 APPEND LINES OF L_MSEG_TAB TO P_MSEG_TAB.
 ENDIF.
 ENDLOOP.
 IF NOT L_XEXIT IS INITIAL.
 EXIT.
 ELSE.
 */ XAuto-Zeilen und Chargenzustandsänderung werden gelöscht
 DELETE P_MSEG_TAB WHERE XAUTO NE SPACE
 OR BWART EQ '341'
 OR BWART EQ '342'.
 P_SUBRC = 0.
 ENDIF.
 ENDFORM. " READ_MSEG
 Form CREATE_GOODS_MOVEMENT *
 Warenbewegung anlegen *
 FORM CREATE_GOODS_MOVEMENT USING P_QALS LIKE QALS
 P_MSEG_TAB TYPE T_MSEG_TAB
 P_SUBRC LIKE SY-SUBRC.
 DATA:
 L_LMENGEZUB LIKE QALS-LMENGEZUB,
 L_LMENGEGEB LIKE QALS-LMENGEZUB,
 L_MBQSS LIKE MBQSS,
 L_IMKPF LIKE IMKPF,
 L_IMSEG LIKE IMSEG,
 L_IMSEG_TAB LIKE IMSEG OCCURS 1,
 L_EMKPF LIKE EMKPF,
 L_EMSEG LIKE EMSEG,
 L_EMSEG_TAB LIKE EMSEG OCCURS 1,
 L_MSEG LIKE MSEG,
 L_MSEG_TAB LIKE MSEG OCCURS 1,
 L_TCODE LIKE SY-TCODE VALUE 'QA11',
 L_TABIX LIKE SY-TABIX VALUE 1,
 L_XSTBW LIKE T156-XSTBW.
 CLEAR: P_SUBRC.
 Page 13
 */QAMB initialisieren
 CALL FUNCTION 'QAMB_REFRESH_DATA'.
 */Kopf füllen
 L_IMKPF-BLDAT = SY-DATLO.
 L_IMKPF-BUDAT = SY-DATLO.
 L_IMKPF-BKTXT = 'Cancellation of QM UD postings'.
 */Ursprüngliche zu buchende Menge merken + inkrementieren
 L_LMENGEZUB = P_QALS-LMENGEZUB.
 L_LMENGEGEB = P_QALS-LMENGE01
 + P_QALS-LMENGE02
 + P_QALS-LMENGE03
 + P_QALS-LMENGE04
 + P_QALS-LMENGE05
 + P_QALS-LMENGE06
 + P_QALS-LMENGE07
 + P_QALS-LMENGE08
 + P_QALS-LMENGE09.
 */Zeilen aufbauen
 L_MSEG_TAB[] = P_MSEG_TAB[].
 LOOP AT L_MSEG_TAB INTO L_MSEG.
 MOVE-CORRESPONDING L_MSEG TO L_MBQSS.
 MOVE-CORRESPONDING L_MBQSS TO L_IMSEG.
 */ Referenzbeleg übergeben, falls Bestellnummer gefüllt
 IF NOT L_MSEG-EBELN IS INITIAL.
 MOVE: L_MSEG-LFBNR TO L_IMSEG-LFBNR,
 L_MSEG-LFBJA TO L_IMSEG-LFBJA,
 L_MSEG-LFPOS TO L_IMSEG-LFPOS.
 ENDIF.
 MOVE L_MSEG-KDAUF TO L_IMSEG-KDAUF.
 MOVE L_MSEG-KDPOS TO L_IMSEG-KDPOS.
 MOVE L_MSEG-PS_PSP_PNR TO L_IMSEG-PS_PSP_PNR.
 */ Umlagerungsfelder setzen
 MOVE:
 L_MSEG-UMMAT TO L_IMSEG-UMMAT,
 L_MSEG-UMWRK TO L_IMSEG-UMWRK,
 L_MSEG-UMLGO TO L_IMSEG-UMLGO,
 L_MSEG-UMCHA TO L_IMSEG-UMCHA.
 */ Storno-Beleg setzen
 MOVE: L_MSEG-MJAHR TO L_IMSEG-SJAHR,
 L_MSEG-MBLNR TO L_IMSEG-SMBLN,
 L_MSEG-ZEILE TO L_IMSEG-SMBLP.
 */ Falsch gefüllte Felder initialisieren
 CLEAR: L_IMSEG-MBLNR,
 L_IMSEG-MENGE,
 L_IMSEG-MEINS.
 */ Bewegungsart lesen
 SELECT SINGLE XSTBW FROM T156 INTO L_XSTBW
 WHERE BWART = L_IMSEG-BWART.
 Page 14
 IF NOT SY-SUBRC IS INITIAL.
 P_SUBRC = 4.
 EXIT.
 ENDIF.
 */ Werk/Lagerort füllen
 IF P_QALS-STAT11 IS INITIAL.
 IF L_XSTBW IS INITIAL.
 MOVE P_QALS-LAGORTVORG TO L_IMSEG-LGORT.
 ELSE.
 MOVE P_QALS-LAGORTVORG TO L_IMSEG-UMLGO.
 ENDIF.
 ENDIF.
 IF L_XSTBW IS INITIAL.
 MOVE P_QALS-WERKVORG TO L_IMSEG-WERKS.
 ELSE.
 MOVE P_QALS-WERKVORG TO L_IMSEG-UMWRK.
 ENDIF.
 */ Zusätzliche Felder
 MOVE P_QALS-MENGENEINH TO L_IMSEG-ERFME.
 "MOVE P_GRUND TO L_IMSEG-GRUND.
 "MOVE P_ELIKZ TO L_IMSEG-ELIKZ.
 */ Kennzeichen Storno-Buchung setzen
 MOVE 'X' TO L_IMSEG-XSTOB.
 MOVE P_QALS-PRUEFLOS TO L_IMSEG-QPLOS.
 APPEND L_IMSEG TO L_IMSEG_TAB.
 IF P_QALS-STAT11 IS INITIAL.
 ADD L_IMSEG-ERFMG TO L_LMENGEZUB.
 SUBTRACT L_IMSEG-ERFMG FROM L_LMENGEGEB.
 ELSE.
 IF L_IMSEG-KZBEW EQ SPACE
 AND L_IMSEG-WERKS NE SPACE
 AND L_IMSEG-LGORT NE SPACE
 AND L_IMSEG-UMWRK NE SPACE
 AND L_IMSEG-UMLGO NE SPACE
 AND L_IMSEG-WERKS EQ L_IMSEG-UMWRK
 AND L_IMSEG-UMLGO EQ L_IMSEG-UMLGO.
 */ Dummy Buchung bei WE-Sperrbestand & Stichprobe
 ELSE.
 ADD L_IMSEG-ERFMG TO L_LMENGEZUB.
 SUBTRACT L_IMSEG-ERFMG FROM L_LMENGEGEB.
 ENDIF.
 ENDIF.
 ENDLOOP.
 IF NOT P_QALS-STAT11 IS INITIAL.
 */ Bei WE-Sperrbestand und Stichprobenbuchung Zeilen tauschen
 DO.
 READ TABLE L_IMSEG_TAB INDEX SY-INDEX INTO L_IMSEG.
 IF SY-SUBRC IS INITIAL
 AND L_IMSEG-KZBEW EQ SPACE
 AND L_IMSEG-WERKS NE SPACE
 AND L_IMSEG-LGORT NE SPACE
 AND L_IMSEG-UMWRK NE SPACE
 AND L_IMSEG-UMLGO NE SPACE
 Page 15
 AND L_IMSEG-WERKS EQ L_IMSEG-UMWRK
 AND L_IMSEG-UMLGO EQ L_IMSEG-UMLGO.
 IF SY-TABIX NE L_TABIX.
 DELETE L_IMSEG_TAB INDEX SY-TABIX.
 INSERT L_IMSEG INTO L_IMSEG_TAB INDEX L_TABIX.
 L_TABIX = L_TABIX + 1.
 ELSE.
 L_TABIX = L_TABIX + 1.
 CONTINUE.
 ENDIF.
 ELSEIF SY-SUBRC IS INITIAL.
 CONTINUE.
 ELSE.
 EXIT. "from do
 ENDIF.
 ENDDO.
 ENDIF.
 */QM deaktivieren
 CALL FUNCTION 'QAAT_QM_ACTIVE_INACTIVE'
 EXPORTING
 AKTIV = SPACE.
 */Buchen
 CALL FUNCTION 'MB_CREATE_GOODS_MOVEMENT'
 EXPORTING
 IMKPF = L_IMKPF
 XALLP = 'X'
 XALLR = 'X'
 CTCOD = L_TCODE
 XQMCL = ' '
 IMPORTING
 EMKPF = L_EMKPF
 TABLES
 IMSEG = L_IMSEG_TAB
 EMSEG = L_EMSEG_TAB.
 */QM wieder aktivieren
 CALL FUNCTION 'QAAT_QM_ACTIVE_INACTIVE'
 EXPORTING
 AKTIV = 'X'.
 */Buchung auswerten
 IF L_EMKPF-SUBRC GT 1.
 IF L_EMKPF-MSGID NE SPACE.
 */ Fehler auf Kopfebene
 MESSAGE ID L_EMKPF-MSGID TYPE 'S'
 NUMBER L_EMKPF-MSGNO
 WITH L_EMKPF-MSGV1 L_EMKPF-MSGV2
 L_EMKPF-MSGV3 L_EMKPF-MSGV4.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ELSE.
 */ Fehler auf Zeilenebene (Ausgabe des ersten Fehlers)
 LOOP AT L_EMSEG_TAB INTO L_EMSEG.
 IF L_EMSEG-MSGID NE SPACE.
 MESSAGE ID L_EMSEG-MSGID TYPE 'S'
 NUMBER L_EMSEG-MSGNO
 WITH L_EMSEG-MSGV1 L_EMSEG-MSGV2
 L_EMSEG-MSGV3 L_EMSEG-MSGV4.
 Page 16
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 ENDLOOP.
 ENDIF.
 ENDIF.
 LOOP AT L_EMSEG_TAB INTO L_EMSEG.
 CALL FUNCTION 'QAMB_COLLECT_RECORD'
 EXPORTING
 LOTNUMBER = P_QALS-PRUEFLOS
 DOCYEAR = L_EMKPF-MJAHR
 DOCNUMBER = L_EMKPF-MBLNR
 DOCPOSITION = L_EMSEG-MBLPO
 TYPE = '7'.
 ENDLOOP.
 */Sonderkorrektur für Frei-An-Frei & WE-Sperr-An-We-Sperr
 IF NOT P_QALS-STAT11 IS INITIAL.
 IF P_QALS-LMENGE04 EQ L_LMENGEGEB.
 ADD P_QALS-LMENGE04 TO L_LMENGEZUB.
 SUBTRACT P_QALS-LMENGE04 FROM L_LMENGEGEB.
 ENDIF.
 ELSEIF P_QALS-INSMK IS INITIAL.
 IF P_QALS-LMENGE01 GE L_LMENGEGEB
 AND NOT P_QALS-LMENGE01 IS INITIAL.
 ADD L_LMENGEGEB TO L_LMENGEZUB.
 SUBTRACT L_LMENGEGEB FROM L_LMENGEGEB.
 ENDIF.
 ENDIF.
 CLEAR: P_QALS-STAT34,
 P_QALS-MATNRNEU,
 P_QALS-CHARGNEU,
 P_QALS-LMENGE01,
 P_QALS-LMENGE02,
 P_QALS-LMENGE03,
 P_QALS-LMENGE04,
 P_QALS-LMENGE05,
 P_QALS-LMENGE06,
 P_QALS-LMENGE07,
 P_QALS-LMENGE08,
 P_QALS-LMENGE09.
 P_QALS-LMENGEZUB = L_LMENGEZUB.
 IF NOT L_LMENGEGEB IS INITIAL.
 P_SUBRC = 4.
 ENDIF.
 ENDFORM. " CREATE_GOODS_MOVEMENT
 Form POST_GOODS_MOVEMENT *
 Warenbewegung buchen *
 FORM POST_GOODS_MOVEMENT.
 CALL FUNCTION 'MB_POST_GOODS_MOVEMENT'.
 Page 17
 ENDFORM. " POST_GOODS_MOVEMENT
 Form POST_DATA *
 QM-Daten verbuchen *
 FORM POST_DATA USING P_QALS LIKE QALS
 P_QALS_LEISTE LIKE QALS
 P_QAMB_TAB TYPE T_QAMB_TAB
 P_QAMB_VB_TAB TYPE T_QAMB_TAB
 P_SUBRC LIKE SY-SUBRC.
 DATA:
 L_STAT LIKE JSTAT,
 L_STAT_TAB LIKE JSTAT OCCURS 0,
 L_QAMB LIKE QAMB,
 L_UPDKZ LIKE QALSVB-UPSL VALUE 'U'.
 */QAMBs umsetzen (7 = VE-Buchung storniert)
 LOOP AT P_QAMB_TAB INTO L_QAMB.
 L_QAMB-TYP = '7'.
 APPEND L_QAMB TO P_QAMB_VB_TAB.
 ENDLOOP.
 */BERF & BTEI zurücknehmen
 CLEAR L_STAT. CLEAR L_STAT_TAB.
 L_STAT-INACT = 'X'.
 L_STAT-STAT = 'I0219'. APPEND L_STAT TO L_STAT_TAB. "BTEI
 L_STAT-STAT = 'I0220'. APPEND L_STAT TO L_STAT_TAB. "BEND
 CALL FUNCTION 'STATUS_CHANGE_INTERN'
 EXPORTING
 OBJNR = P_QALS-OBJNR
 TABLES
 STATUS = L_STAT_TAB
 EXCEPTIONS
 ERROR_MESSAGE = 1.
 IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 SUBMIT (SY-REPID) VIA SELECTION-SCREEN.
 ENDIF.
 */Prüflos aktualisieren
 CALL FUNCTION 'QPL1_UPDATE_MEMORY'
 EXPORTING
 I_QALS = P_QALS
 I_UPDKZ = L_UPDKZ.
 CALL FUNCTION 'QPL1_INSPECTION_LOTS_POSTING'.
 CALL FUNCTION 'STATUS_UPDATE_ON_COMMIT'.
 */QAMB initialisieren
 CALL FUNCTION 'QAMB_REFRESH_DATA'.
 Page 18
 PERFORM UPDATE_QAMB ON COMMIT.
 P_SUBRC = 0.
 ENDFORM. " POST_DATA
 Form UPDATE_QAMB *

Reverse Production Confirmation After Usage Decision (UD)

Hi All ,
We are using Quality Inspection Type 04 ("Good Recipt production Inspection ") . We have Done some wrong Entry in Production Confirmation after that quality person also did Usage Decision for the inspection Lot. now we want to cancel this confirmation . will some one help me how we can reverse UD (Usasge Decision) and Cancel the production confirmation .
Thanks In Advance .
Regards

Dear Jaideep,
Check out this,
Do you mean to say you want to cancel the document for which 321 movement has been made where the stock has been
cleared from quality to un-restricted?
This is not possible,unless if you have used SAP notes,
Note 1108313 - Cancelling usage decision and lot
Note 175842 - Inspection lot: Reversal of goods movements from UD.
Otherwise cancel the confirmation and the error movement 102 will be going to COGI.
Do 102 through MB31 against that order and delete the 102 error from COGI.
Check and revert back.
Regards
Mangalraj.S

Reversal of Usage Decision for insp type 10 lot

Similar Messages

Maybe you are looking for