Usage Decision IP address / Terminal Number

How to get Usage Decision IP address / Terminal Number?

Hi Vivek.
Just a note, your posting was reported as probably being in the wrong forum and more suited to a BASIS or security forum. But the question is about UD's so it's a borderline call for me so I left it.
Now, as far as the question goes, I don't think what you want is possible without modifications. There is no log tracking IP address for when a UD is given. I.e. the IP address is not stored with the UD administrative data anywhere. So once the user logs off, any chance of getting that data would be zero.
I do know your BASIS or security team can definitely get the IP address for user's online and depending on what they are recording and monitoring, they may have logs but probably not directly related to the transactions used.
This discussion has a lot of info in it: SAP User Login Transaction code History details
The trick will be to capture the info and store it some where. My suggestion might be to utilize a user exit when the UD is saved, and use the FM "TERMINAL_ID_GET" to get the IP address. (Note: I have not personally done this or used that FM, but I am told that it will return a user's IP address), then store the IP address in the UD long text.
Craig

Similar Messages

Usage Decision to post new material.

I need a FM which posts material as New Material when the Usage decision is made. I get the Usage decision and the material number(new)from the shopfloor and post it using the t-code qa11. Any help will be rewarded.

Function Modules
http://www.erpgenie.com/abap/functions.htm
http://www.sapdevelopment.co.uk/fmodules/fmssap.htm
http://www.erpgenie.com/abap/index.htm
http://www.geocities.com/victorav15/sapr3/abapfun.html
Rewards if useful................
Minal

QM_Follow up action in usage decision

Dear QM Experts,
1. We can record the defects in inspection lot (01 origin) which creates quality notification in background under F2 type.
2. If the defects are recorded usage decision is given as Rejected.
Requirement is auto email should be sent to predefined email addresses briefing defects and number of defects. This has to be done only for those lots whose UD have been given as Rejected. Question is which follow up action and which function module to be used for this?
Best Regards,
Anand Rao

hi
kindly check whether the following FM can be used
QFOA_MAIL_REJECTED_RESULTS-Follow-Up Action Module: Send Mail for Rejected Characteristics
QFOA_MAIL_SENDING-Send Info MAIL After Usage Decision (Mail Contains UD Data)
QFOA_MAIL_SENDING_STANDARD-Send a Short Info MAIL After Usage Decision
you have to assign these follow up actions with FM to the rejected UD code
regards
thyagarajan

Need to send data, after Usage decision in quality inspection (QA11)

Hi all,
After Usage decision in quality inspection (QA11), i need to send some data like material number, qty etc to external database or to external party. is there anyway i can achive this in real time? real time means, it should send the appropriate data to external party after usage decision is made.
Thanks
Pabi

Hi,
You can change results recording in case the MIC in the inspection plan of the lot are marked as "long term characteristics", else it wont be possible to change result recording.
you can change the UD code only after giving the Usage decision.
you cannot change the defects recording.
Thanks
SUMIT

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 *

Quality score by usage decision?

Dear SAPIENTS,
Can any one help me in creation of this configuration setting?
I would like to have quality score calculation from usage decision. Score calculation should be done by number of quantity received against order.
Suppose if 100 quantity ordered:
25% Deviation means 75 only received then score is 75
Likewise for 50%, 75% and 100%
Regards,

Hi
please refer
Re: Quality Score in Vendor Rating
Regards'
Sujit

Usage Decision QA32

Hi,
After doing Usage Decision in QA32 and when trying to save system is asking for a serial number. Why is the system asking the Serial number at this stage..??
Should I need to define the Serial number earlier only..?? If so when and where should I define? What for system is asking to define the Serial number..??
Regard's,
Uday.

Hi,
System asks Serial number because the material is already has been assigned serialised profile in material master.
Secondly if serialised profile in config is made mandatory for QMSL object
third. If you give UD as accepted or blocked and stock post full qty to unrestricted or blocked stock,system wont ask u to give serial number as all serial nos are accepted.
Where as if you are posting only partail qty. system do not understand how which serial number needs to be posted to which stock hence it asks for serial number.
Hope this helps u upto certain extent.
Regards,
Nitin

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.

Production Order Receipt Block before Usage Decision is Made

Dear all,
I have a requirement to block production order receipt through MIGO into any storage location before the usage decision has been made for that production order.
This should be the rule for all non serial items, meaning that it should only apply to batch controlled and neither batch nor serial controlled materials.
Could someone please help me on this?
Thanks,
Sergiy

Hi,
Is it possible through by maintaining the inspection type for the material master. Then the material will be moved to quality stock after usage decision then you can move that material to unrestricted material.
For Batch managed or serial number profile defined material don't activate the inspection type.
Hope this might help you.
Regards
Ravi shankar.

Serial Numbers in QA11 Record Usage Decision

Hi all,
We are using the serial numbers scenario in goods receipt. The user has to enter the serial numbers of the equipment/devices at the time of preparing goods receipt in MIGO_GR against a purchase order. An Inspection Lot is generated after posting the goods receipt. The has to prepare the GR approx 5000 nos. of material in each goods receipt.
Usage Decision has to be recorded for all these 5000 serial numbers in a particular inspection lot. Once we run the Tcode : QA11 and enter the quantity to be posted to blocked stock as 5000 and click on the save icon.
The system throw a screen for selection of serial numbers for which the usage decision is to be recorded. On this screen, all the 5000 serial numbers entered in the inspection lot should be available for selection. But the system sometimes shown only 5, sometimes it shows 2500, sometimes 1000 nos. for selection.
Please suggest if this might be due to some configuration problem or due to constraint of memory in the lock table in SM12. We are facing the same problem while processing the goods receipt for 5000 nos. through a BAPI.
Thanks in advance.
AJ

HI Anand,
Thanks for your immediate response. You have perfectly understood my problem. The following are the clarifications for your queries :-
Point No. 01 : We are posting the entire quantity (5000 nos.) to blocked stock. We enter 5000 in the To Blocked Stock field of Inspection Lot quantity Tab of the Inspection Lot. After entering the quantity we click on the Save button to post the Usage Decision. A pop of the serial numbers for select is given after clicking on the Save button. The serial number pop up is given if we try to process the usage decision for full quantity of 5000 nos. But sometimes if we put a smaller quantity say 20 nos. then the popup is not given and the usage decision is successfully posted for 20 nos. So the system behaves very randomly.
Point No. 02 : The serial numbers displayed for the selection is also random say sometimes 13/5000, 2500/5000, 0/5000.
Point No. 03 : I have checked the SER03 and OBJK tables and all the 5000 serial numbers are allocated to the material document.
We already have escalated to SAP, but do you feel there is some configuration issue for the same. Please give your valuable suggest.
Thanks in advance.
AJ

Issue in usage decision

Hi,
During usage decision, i have moved the stock to scrap by mistake , can you please tell me how to reverse the UD.
I tried through MB1B. The problem is we dont know in which storage location it is posted
Can you please suggest me , how to proceed.
One more issue.
I want to bring down the scrap field in inspection lot stock screen, how to do it.
Thanks in advance.
Regards
Karthik

Hi
To find material document no. :
1. if you know the lot number, you can use QA03 (Display lot) Tcode and click on the item mat doc. The doc no with type 3 assigned is your required material doc.
2. Goto MB51, and use movement type 553, material and plant and execute to get the material no.
To reverse from scrap to QI:
1. Activate insp. type 05 in QM view of material master.
2. Goto MB1A, use movement type 554 to transfet the quantity. Lot will be generated in QI, do UD and transfer the lot to unrestricted usage.

Regarding problem with updating usage decision in QA11

Hi Experts,
I am trying to use the Bapi "BAPI_INSPLOT_SETUSAGEDECISION" to update the usage decision in QA11 in a proxy. I am not being able to understand what parameters to be used and how.
CALL FUNCTION 'BAPI_INSPLOT_SETUSAGEDECISION'
EXPORTING
    NUMBER               = INPUT-SAP_USAGEDECISION-DETAILS-UD_INSPLOT "inspection lot no from the proxy structure.
    UD_DATA              = lw_data
LANGUAGE             =
IMPORTING
UD_RETURN_DATA       =
STOCK_DATA           =
   RETURN               = li_return
TABLES
SYSTEM_STATUS        =
USER_STATUS          =
Please help.

Hi,
Just pass the inspection lot number to the field NUMBER and try, because there are no standard programs in which this FM is called apart from a Business Object BUS2045, it is called in the method InspectionLot.StatInterface.
You can check that for any clarification, but it is not clear there as well.
Thanks,
Mahesh.

Transfer Posting error upon u201CQM Usage Decision with WM HUu201D

Hello,
I am switching from the SAP system u201CUsing MIGO with WM (no SU) and Inspection Lot processingu201D to a process using u201CInbound Delivery with WM-HU and Inspection Lot processingu201D.
For e.g. I have a material with 10 pcs packed in one HU, PGRd and putaway. Inspection Lot is created for the HU containing 10 pcs. I am ideally hoping to do Posting change of 6 pcs to Unrestricted (with underlying mvmt typ 321) and Transfer Posting of 4 pcs to Qty. for Sample usage (with underlying mvmt typ 331).
In QA11, when I select posting key u201CVMENGE01 To Unrestricted useu201D, I get the error message u201CHandling Unit is locked. No assignment possible. Message No. HUFUNCTIONS007u201D. (I donu2019t have any document open to cause locking).
When I select posting key u201CVMENGE03 Qty. for Sample usageu201D, I get the error message u201CHandling Unit is locked. No assignment possible. Message No. QHU17u201D.
Here is the status in u201CInspection Lot Stocku201D tab of QA11.
u2022     Inspection Lot Qty.: 10 pcs
u2022     Sample size: 4 pcs
u2022     Status for u201CHU Transfer Postingu201D is Green
I am currently doing GR first and then putaway. Though I am open to doing putaway and then do PGR, if that can help, in any way.
Can anyone please help me with this issue? Please let me know if I need to provide more info. Thanks for your help in advance.

hi
I did GR for 10 PCs with serial numbers. During QM, when usage decision, in the tab "Inspection lot stock", I input 8 PCs to the unres, 2 to blocked stock.
Upon posting, system pops up a Serial Number dialog showing "TF quality to unrest" with No. serial no is 10/8, and a list of 10 serial numbers.
I select 8 serial to post to unres. But still, the system keeps having error "Exactly 8 serial numbers must be selected (instead of 10)"...
This error is dur to
You have selected 28 to U/r & rest you want to put to Block.
so what system does is by default it will select first U/R qty which is 8.
While stock posting it is showing 10 Sr numbers.out of which you have to select 8 for U/R.
so only select those 2 numbers which you want to put to block...Click on delet(bucket)
now only 8 will remain which you wnat to put to U/R.
select all 8 and click on ok
save.
Rest of the 2 Sr number will automatically move to unrestricted.
This is how sap in UD works for Sr nos.
This will solve your problem.
Regards
Sujit

[HELP] - QM cancel usage decision

Hello SAP gurus,
I need dome help with a QM scenario.
How can I cancel a UD and move the stock again to Quality Inspection?
Thanks in advance,
Adelmo

Hi
here is some more help,
Follow the link (page 27) http://help.sap.com/printdocu/core/Print46c/EN/data/pdf/QMIMUD/QMIMUD.pdf
Reversing Stock Postings
1. Choose Logistics > Materials Management > Inventory Management > Goods Movement> Goods receipt > For purchase order> PO number known.
The initial screen for creating a goods receipt for a purchase order appears.
2. In the field for the movement type, enter 102 (goods receipt for a purchase order into
warehouse - reversal).
3. In the field for the purchase order, enter the purchase order number for the original goods
receipt.
You can copy the purchase order number from the inspection lot.
4. Choose Enter to display the selection screen for the purchase order items.
5. Select the purchase order item for which you want to create the goods receipt and set the
Stock type indicator to the stock to which the goods were originally posted with the
usage decision (for example, F for unrestricted-use stock or S for blocked stock).
6. Save the goods receipt and exit the Materials Management component.
7. Choose Logistics > Quality management > Quality inspection > Inspection lot> Usage
decision > Change with history.
The initial screen for changing a usage decision appears.
8. Enter the number of the inspection lot for which you previously made the usage decision and
choose Usage decision (UD).
9. To cancel the inspection lot, choose Usage decision > Functions . Cancel lot in the usage
decision screen.
Regards
Suhas

Record usages decision- inspection lot stock

hi gurus,
when i am using a record usages decision screen (QA11) after putting my inspection lot number it show me only two tabs Defects and charterstics it didn't show me an inspection lot stock tab.
Please suggest
Regards
Maashish

Hi Maashish,
I believe that your PO is for cost center.
when you will recieve the material using MIGO for This PO, then matieal stock/Value will be posted to Consumtion Account ( Stck will not posted to store) and GR/IR for Vendor.
In this case if Inpection lot generated, then using QA11/QA32 you can records quality information in Result & UD.
In this case Transfer posting 321/105 for material will not take place.you can input quality inforamation only.
Hope this piece of info. will help to resolve your query..
Cheers
Manoj Singh

Usage Decision IP address / Terminal Number

Similar Messages

Maybe you are looking for