Qty reject in UD

Hi ,
I am a MM guy , just trying to understand the implications of QM rejections on Inventory.
I have a purchase Order with Qty say 10 , I performed MIGO (101) aginst this order.It created 1) Mtrl document 2) Inspection Lot 3) batch 4) TR (WM).The stock moved into Quality stock and batch status is restricted.
I created a TO aganist this TR and confirmed it so that material can be transferred to normal Storage bin.
Now while doing UD , i rejected the entire Qty of this lot by assigning appropriate UD code.
I was expecting it will create 102 material document automatically with respective financial effects , but It didn't create it but batch is now not visible thru MMBE.It has only created a PCN (Posting change Notice) in WM.
Could anyone pls help me to understand the implications of QM testing on INVENTORY.
Thx in advance.,
regards
Shrey

THX

Similar Messages

Qual Insp:Perform partial qty REJECT in QA12 for Material GR inspection lot

Dear All,
Please advice me for a scenarion.
I perform MIGO-GR - MType 103 for 5 qty, material moves to GR Blkd Stk.
Then perform MIGO-RelBlkSTk - MType 105 for 5 qty, the material moves from GRBlkStk to QualtInspStk.
The perform QA32 for the insp lot , and ACCEPT the 5 qty to UnrestStk.
This acceptence movement calculates the Vendor Evaluation Quality criteria also.
I can also REJECT the above inspection lot by QA12 : Change Usage Decision, this rejects the full 5 qty, and this also has impact in vendor evaluation quality criteria rating. Then Return to the Vendor the 5 qty.
My query is:
Now if i want to return PARTIAL qty to the vendor ALONG WITH VENDOR RATING RETURN CALCULATION.
I am unable to enter partial qty in the QA12, in the 'Inspection Lot tab' in the 'To Be Posted' column.
The whole column is non-editable, is it standard by default as non-editable?
Am i performing the right steps for my requirement?
Thanks in advance,
Joy Ghosh

Hi
In QA12, after entering appropriate Usage decision, click on "defective quantity" tab at header, and there enter the quantity.
Umakanth R

Purchase order quantity QM rejection (all qty)

Dear SAP Gurus
In single PO, Whole qty rejected from Quality and i have made return to vendor, it then also it is allowing for making LIV . Can any body guide please to block for payment.
Thanxs!!
Raghu.

make your PO for GR based invoice verification on Invoice tab and if it is parmenant then make it in Inforecrd.

In Production Return & Rejected Qty Prod Order wise required

Hi Experts,
In Production, Parent Item to be produced 100. Two Child items are there for the parent Item.
Parent Item A- 100 Qty
Child Item A1- 100 Qty -- Issue method Back flush
Child ItemA2 -100 Qty -- issue method Manual
Child Item A2 Issued Manually. Production Completed........
In the receipt from Production
Parent Item A -90 Qty completed
Child Item A1- 8 Qty Returned (Good Raw Material Returned)
Child Item A2- 3 Qty Returned (Good Raw Material Returned)
Child Item A1 -2 Qty rejected (To be scraped)
Child Item A2 - 7 Qty rejected (To be scraped)
We would like to take query/Report......... Production Order Wise, Child Item Issued, Component Returned, Component Rejected.
Plz Guide Me,
Thanks and Regards,
Manikandan

Hi,
In SAP, for items defined as Back-flush, you cannot change the issue qty of Raw Material components. This will always correspond exactly to the qty of Finished Goods and the relation between the FG qty and the component qty in BOM. In you example, the RM Item A will be issued as 100 qty as the FG produced is 100 qty.
Or if you are recording 90 qty then RM Item A will be consumed automatically equal to 90 qty.
In SAP, the FG reject is prodcued only for numerical record and is recorded in the Receipt from Production screen. Total prodcued qty will be reject qty + completed qty.
The scrap of FG item is not possible as FG item. Fixed qty of Scrap can be defined in the BOM or the production order as a row with negative qty. This will be prodcued automatically based on the qty relationship between Scrap item and the FG item.
Say if in the Production Order for a FG of 100 qty, scrap is produced equal to 20 qty, then this srap item will be entered in the Production Order as a row of -20 qty. When production of X qty is recorded, scrap will be prodcued in the following ratio:
Scrap produced = X * (20/100)
Regards

Scess value field is grey out in MIGO while posting rejection excise invoic

HI..
In Return delivery ,i am capturing & posting excise invoice...
The problem is while we can change the values of BED,AED,ECS but the SCESS field is coming grey out.Therefore i cannot change it.
How can we remove the grey out so that we can enter manually whatever amount we have credited.
here the print program is made considering in MIGO we can capture/post excise invoice..
plz reply fast.
Thanx & regards,
Satpal

When it is return delivery tranaction and if you don't select no excise entry system by default captures all data from original document except quantity field and hence all the fileds will be non modifiable. However it is better to select 'No Excise Entry" at the time of Return Delivery and then go for "create excise invoice for other movements" T Code "J1IS" so that you could enter all the duties correct based on the qty rejected in return delivery.
Hope it would suits you.
Cheers

Report error- All fields are not taking

Hi,
I
have created Program for the report ,But it does ,not selecting all foelds,
What will the possible reason.
I have created report for rows as
Notification Inspection lot qty Ok Qty Rejected Qty Defect Group Defect Code Code Qty Code Description.
But Report is picking data for the coloumns of NOTIFICATION and CODE QTY.
Is there i am missing in program?
Details as following
*& Report ZQMLOTDTL
REPORT ZQMLOTDTL.
*Table Declarations.
TABLES:QALS,QMEL,QMFE,QPCT.
*Data Declarations
TYPE-POOLS : slis.
TYPES : BEGIN OF ty_qals,
       werk            TYPE qals-werk,
       budat           TYPE qals-budat,
       prueflos        TYPE qals-prueflos,
       matnr           TYPE qals-matnr,"'Part Number'.
       maktx           TYPE makt-maktx,
       mblnr           TYPE qals-mblnr,
       zeile           TYPE qals-zeile,
       losmenge        TYPE qals-losmenge,
       lmenge01        TYPE qals-lmenge01,
       lmenge04        TYPE qals-lmenge04,
       compd           TYPE makt-maktx,
END OF ty_qals.
DATA :it_qals TYPE STANDARD TABLE OF ty_qals WITH HEADER LINE.
TYPES:BEGIN OF ty_qmfe,
        qmnum   TYPE qmfe-qmnum,
        fegrp     TYPE qmfe-fegrp,
        fecod     TYPE qmfe-fecod,
        kurztext TYPE qpct-kurztext,
        anzfehler TYPE qmfe-anzfehler,
        werks    TYPE qmfe-werks,
        compd1    TYPE qpct-kurztext,
END OF ty_qmfe.
DATA:it_qmfe TYPE STANDARD TABLE OF ty_qmfe WITH HEADER LINE.
TYPES:BEGIN OF ty_qmel,
        qmnum    TYPE qmel-qmnum,
        erdat    TYPE qmel-erdat,
        matnr    TYPE qmel-matnr,
        maktx     TYPE makt-maktx,
        prueflos TYPE qmel-prueflos,
        mblnr    TYPE qmel-mblnr,
        mblpo    TYPE qmel-mblpo,
        compd    TYPE makt-maktx,
END OF ty_qmel.
DATA:it_qmel TYPE STANDARD TABLE OF ty_qmel WITH HEADER LINE.
*----------------------FINAL ITAB------------------------
TYPES:BEGIN OF itab,
   werk            TYPE qals-werk,
   budat           TYPE qals-budat,
   prueflos        TYPE qals-prueflos,
   matnr           TYPE qals-matnr,
   maktx           TYPE makt-maktx,
   mblnr           TYPE qals-mblnr,
   zeile           TYPE qals-zeile,
   losmenge        TYPE qals-losmenge,
   lmenge01        TYPE qals-lmenge01,
   lmenge04        TYPE qals-lmenge04,
   qmnum    TYPE qmfe-qmnum,
   fegrp     TYPE qmfe-fegrp,
   fecod     TYPE qmfe-fecod,
   kurztext   TYPE qpct-kurztext,
   anzfehler TYPE qmfe-anzfehler,
   werks     TYPE qmfe-werks,
   compd     TYPE makt-maktx,
   compd1    TYPE qpct-kurztext,
   erdat    TYPE qmel-erdat,
   mblpo    TYPE qmel-mblpo,
END OF itab.
DATA : it_itab TYPE STANDARD TABLE OF itab with HEADER LINE.
*Internal Table for field catalog
DATA : t_fieldcat TYPE slis_t_fieldcat_alv WITH HEADER LINE.
DATA : fs_layout TYPE slis_layout_alv.
*Internal Table for sorting
DATA : t_sort TYPE slis_t_sortinfo_alv WITH HEADER LINE.
"For Variant.
DATA : g_variant LIKE disvariant,
       g_save(1) TYPE c,
       gx_variant LIKE disvariant,
       g_exit(1) TYPE c,
       g_tabname_header TYPE slis_tabname,
       g_tabname_item   TYPE slis_tabname.
**********************SELECTION-SCREEN**************************
SELECTION-SCREEN:BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS:s_werk FOR qals-werk.
SELECT-OPTIONS:s_budat FOR qals-budat.
SELECTION-SCREEN:END OF BLOCK b1.
" Added By Mayur% on 07.03.2013.
"For Variant
SELECTION-SCREEN BEGIN OF BLOCK 0 WITH FRAME TITLE text-p01.
PARAMETERS: s_var TYPE slis_vari.
SELECTION-SCREEN END OF BLOCK 0.
"Get the default variant
"F4-Help for variant
AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_var.
INITIALIZATION.
PERFORM default_var.
"Validates the diplay variant
*********************END-OF-SELECTION**************************
START-OF-SELECTION.
PERFORM data_select.
PERFORM data_collect.
PERFORM sort_list.
PERFORM data_fieldcat.
*&      Form DATA_SELECT
*       text
FORM data_select.
SELECT
     qmnum
     fegrp
     fecod
     anzfehler
     werks
FROM qmfe INTO CORRESPONDING FIELDS OF TABLE it_itab
     WHERE werks = it_itab-werks.
SORT it_qmfe BY qmnum.
IF it_qmfe IS NOT INITIAL.
SELECT
        qmel~qmnum
        qmel~erdat
        qmel~prueflos
        qmel~matnr
        makt~matnr
        qmel~mblnr
        qmel~mblpo
*       makt~compd
INTO CORRESPONDING FIELDS OF TABLE it_itab
FROM qmel INNER JOIN makt ON qmel~matnr = makt~matnr
FOR ALL ENTRIES IN it_itab
WHERE qmnum = it_itab-qmnum
AND    prueflos = it_qals-prueflos.
SORT it_qmel BY prueflos.
SELECT
       prueflos
       FROM qals INTO CORRESPONDING FIELDS OF TABLE it_itab
       FOR ALL ENTRIES IN it_qmfe
       WHERE prueflos = it_qmel-prueflos
       AND      werk = it_qmfe-werks
       AND      matnr = it_qmel-matnr
       AND      mblnr = it_qmel-mblnr
       AND      zeile = it_qmel-mblpo
       AND   losmenge = it_itab-losmenge
       AND   lmenge01 = it_itab-lmenge01
       AND   lmenge04 = it_itab-lmenge04.
ENDIF.
ENDFORM.                         " SELECT_DATA
*&      Form fill_fieldcatalog
*       text
FORM data_fieldcat.
PERFORM f_fieldcatalog USING '1'   'QMNUM'       'Notification number'.
PERFORM f_fieldcatalog USING '2'   'PRUEFLOS'    'Inspection Lot Number'.
PERFORM f_fieldcatalog USING '3'   'LOSMENGE'    'Inspection Lot Quantity'.
PERFORM f_fieldcatalog USING '4'   'MBLNR'       'Material Document'.
perform f_fieldcatalog USING '5'   'ZEILE'       'Item Number'.
PERFORM f_fieldcatalog USING '6'   'MATNR'       'Material Number'.
PERFORM f_fieldcatalog USING '7'   'MAKTX'       'Material Description'.
PERFORM f_fieldcatalog USING '8'   'WERK'        'Plant'.
PERFORM f_fieldcatalog USING '9'   'BUDAT'      'Date'.
PERFORM f_fieldcatalog USING '10' 'LMENGE01'   'OK'.
PERFORM f_fieldcatalog USING '11' 'LMENGE04'   'Rejected'.
PERFORM f_fieldcatalog USING '12' 'FRGRP'   'Codegroup'.
PERFORM f_fieldcatalog USING '13' 'FRCOD'   'Code'.
PERFORM f_fieldcatalog USING '14' 'kurztext' 'Code Text'.
PERFORM f_fieldcatalog USING '14' 'ANZFEHLER'   'DefectQty'.
PERFORM g_display_grid.
ENDFORM.            " DATA_FIELDCAT
*&      Form f_fieldcatalog
*       text
*      -->VALUE(X)   text
*      -->VALUE(Y)   text
*      -->VALUE(Z)   text
*      -->VALUE(W)   text
FORM f_fieldcatalog USING value(x) value(y) value(z).
t_fieldcat-col_pos = x.
t_fieldcat-fieldname = y.
t_fieldcat-seltext_l = z.
t_fieldcat-no_zero = 'X'.
APPEND t_fieldcat.
CLEAR t_fieldcat.
ENDFORM.                    "f_fieldcatalog
*&      Form COLLECT_DATA
*       text
FORM DATA_COLLECT.
LOOP AT it_qmfe.
it_itab-qmnum     = it_qmfe-qmnum.
it_itab-fegrp     = it_qmfe-fegrp.
it_itab-fecod     = it_qmfe-fecod.
it_itab-anzfehler = it_qmfe-anzfehler.
READ TABLE it_qmel WITH KEY qmnum = it_qmfe-qmnum.
it_itab-prueflos = it_qmel-prueflos.
it_itab-qmnum     = it_qmel-qmnum.
READ TABLE it_qals WITH KEY prueflos = it_qmel-prueflos.
it_itab-werk     = it_qals-werk.
   it_itab-matnr    = it_qals-matnr    .
It_itab-mblnr    = it_qals-mblnr.
It_itab-zeile    = it_qals-zeile.
it_itab-losmenge   = it_qals-losmenge.
it_itab-lmenge01   = it_qals-lmenge01.
it_itab-lmenge04   = it_qals-lmenge04.
    APPEND it_itab.
CLEAR :it_itab,it_qals,it_qmel,it_qmfe.
ENDLOOP.
ENDFORM.
*&      Form SORT_LIST
*       text
FORM sort_list .
* t_sort-spos      = '1'.
* t_sort-fieldname = 'werk'.
* t_sort-tabname   = 'it_itab[]'.
* t_sort-up        = 'X'.
* t_sort-subtot    = 'X'.
* append t_sort.
* t_sort-spos      = '2'.
* t_sort-fieldname = 'BUKRS'.
* t_sort-tabname   = 'it_itab[]'.
* t_sort-up        = 'X'.
* t_sort-subtot    = 'X'.
* append t_sort.
ENDFORM.                    " SORT_LIST
*&      Form G_DISPLAY_GRID
*       text
FORM g_display_grid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program     = sy-repid
      is_layout              = fs_layout
      i_callback_top_of_page = 'TOP-OF-PAGE'
      it_fieldcat            = t_fieldcat[]
      it_sort                = t_sort[]
      i_save                 = 'X'
    TABLES
      t_outtab               = it_itab[]
    EXCEPTIONS
      program_error          = 1
      OTHERS                 = 2.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 4.
ENDIF.
ENDFORM.          " G_DISPLAY_GRID
*&      Form top-of-page
*       text
FORM top-of-page.
DATA: t_header TYPE slis_t_listheader,
       wa_header TYPE slis_listheader,
       t_line LIKE wa_header-info,
       ld_lines TYPE i,
       ld_linesc(10) TYPE c.
* Title
wa_header-typ = 'H'.
wa_header-info = 'QMLOTDTL'.
APPEND wa_header TO t_header.
CLEAR wa_header.
DESCRIBE TABLE it_itab LINES ld_lines.
ld_linesc = ld_lines.
CONCATENATE 'Total No. of Records Selected: ' ld_linesc
     INTO t_line SEPARATED BY space.
wa_header-typ = 'A'.
wa_header-info = t_line.
APPEND wa_header TO t_header.
CLEAR: wa_header, t_line.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = t_header.
ENDFORM.
                   "top-of-page
*&      Form SORT_LIST
*       text
* --> p1        text
* <-- p2        text
*&      Form DEFAULT_VAR
*       text
* --> p1        text
* <-- p2        text
FORM DEFAULT_VAR .
g_variant-report   = sy-repid.
g_variant-username = sy-uname.
g_variant-variant = s_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
    I_SAVE              = 'A'
CHANGING
    cs_variant          = g_variant
EXCEPTIONS
    NOT_FOUND           = 2.
IF sy-subrc = 0.
    s_var = g_variant-variant.
ENDIF.
                    " DEFAULT_VAR
*&      Form VARIANT
*       text
* --> p1        text
* <-- p2        text
*----------------------------------------------------------------------*form VARIANT .
g_variant-report   = sy-repid.
g_variant-username = sy-uname.
g_variant-variant = s_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant                = g_variant
*     I_TABNAME_HEADER          =
*     I_TABNAME_ITEM            =
*     IT_DEFAULT_FIELDCAT       =
      I_SAVE                    = 'A'
*     I_DISPLAY_VIA_GRID        = ' '
    IMPORTING
      E_EXIT                    = g_exit
      ES_VARIANT                = g_variant
    EXCEPTIONS
      NOT_FOUND                 = 1
      PROGRAM_ERROR             = 2
      OTHERS                    = 3.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    IF g_exit = space.
      s_var = g_variant-variant.
    ENDIF.
ENDIF.
ENDFORM.
With Regards,
Dev

Hello Dev,
have a look at the select:
SELECT
        qmel~qmnum
        qmel~erdat
        qmel~prueflos
        qmel~matnr
        makt~matnr
        qmel~mblnr
        qmel~mblpo
*       makt~compd
INTO CORRESPONDING FIELDS OF TABLE it_itab
This probably does not fill any column in it_itab because the "CORRESPONDING FIELDS" part does not find columns named "qmel~erdat", for example, but only "erdat".
So you may want to change your select to something like this:
SELECT
        qmel~qmnum    AS qmnum
        qmel~erdat    AS erdat
        qmel~prueflos AS prueflos
        qmel~matnr    AS matnr
        qmel~mblnr    AS mblnr
        qmel~mblpo    AS mblpo
*       makt~compd    AS compd
INTO CORRESPONDING FIELDS OF TABLE it_itab
In addition, using it_itab in the select as data sink (INTO ... TABLE it_itab) and at the same time as data source (FOR ALL ENTRIES IN it_itab) is probably also not a good idea and may lead to unexpected side effects.
Best regards,
Frank.

Customisation of SAP-B1

hi all,
iam new in SAP B1-2005 ,here we started Customisation of SAPB1 my modules are like thisie
1.)Purchasing A/P ->
1.1)Goods Receipt P.O -->Step1)In this i had to modify the Menu Item to be changed as "Material Inward Receipt"(Requirement).
Step2)"Qty Accepted" and "Qty Rejected" fields are to be added after "Quantity" field.
Step3) "Qty Accepted" is to be update in the stock table instead of "Quantity".i had doubt regarding this requirement how is it possible update this field.But, in checked in this Database their is no such like table(stock) in SBODemo_India can u tell me where it is Find.
1.2)Purchase Order-->step1)Presently "Delivery date" field is in the main form ie it belongs to POR1(table) how can i shift this field to grid Can u suggest me which code i have to get where i had to modify in Code. Mainly we are doing only for Maintanence one code ie i am too hard to where to modify in that predefined code.
1.2)Purchase Orde (New Requirement)-->Auto generation of Purchase Order. If the Stock for any "Item" falls below the minimum level, a Purchase Order to be generated on the name of the "Supplier" who narmally supplies those items.
1.3)Purchase Order - Report-->step1) we have to modify the report regarding the Client supplied the format. we have to modify in that format.Can u suggest which report tables ie predefined tables to change the extra fields to get.
Regards
anand

Hi Anand,
1. Goods Receipt P.O
Go to Administration -->System Initialization -->Document Numering --> Click Change Name --> You can very few menu item names. One of that is Goods Receipt P.O
2. Change the name of existing Quantity field as Quantity Accepted by use Ctr+double click. Add user defined field for other fields. Use the formated search for calculations.
3. Delivery date field: I am able to get your thread
4. Purchase order report: By using Print layout designer you can achieve this.
I hope this will help you.
Venkatesan G.

Vendor Auto Mail Information

Hi QM Gurus,
My client requirement is
Scenario 1: Once procurement goods rejected in Quality that time rejection information (Defect details, UD details, Accepted qty, rejected qty) send to vendor as well as concern vendor follow up person automatically by the system.
Scenario 2: Once received the shop floor complaint related to procurement product, the concern Quality people create the notification against the vendor with defect details, complaint qty etc, after that the same information send to vendor as well as concern vendor follow up person automatically by the system.
How to generate automatic mail in SAP.
please any one give the suggestion.
Thanks in Advance.
Babusingh.S

Hello Singh
1. You can define follow-up action in selected sets (QS51). At the time of UD system ll send a mail if you use the slected sets with follow-up action.
2. Mail through notification, activate the workflow for the same. You can customize your action box & can send mail through your action to the concerned person (Person Responsible) assigned in the notification Tab 2.
Let me know if you need any other info.
Regards
APS

QM Report-Standard Possible???????

Dear Friends
is there any standard report available with following details
Daily report showing
- Prod/Purc order no.
- Material
- Qty
-Reject Qty
-Reject description
Regards
Swananand

Hi
Check MCXX ,MCXV,MCXP,MCVX,MCVZ,MCVP transactions for the relevant information, make lay out settings if required to get ur required details
Regards
Venugopal

Vendor Evaluation and inspection type 17

All,
Iam using EWM QIE as a result of which i have to use inspection type 17. Does Vendor Evaluation work with inspection type 17. I know for a fact that in standard ECC Vendor Evaluation works with the 01 inspection type, but i am not sure of inspection type 17. Any input will be appreciated.
Thanks

Dear Ramki,
Thanks for your input; if I don't use the user exit, then the quality score is being shown there for the material level.
But still, there are a few problems:
1. Material wise Quality score, which is being displayed in ME64, is not getting updating in any of the table. Table ELBM is also blank. There is not even a single record.
2. The quality rating that is being calculated here is as per following:
     The user gives disposition for the incoming material as
          Qty accepted directly: A1
          Qty accepted after segregation: A2
          Qty accepted as major deviation: A3
          Qty accepted as minor deviation: A4
          Qty Rejected.     : A5
The formula is
Q.R. = (A11 + A2(-0.5) + A30.5 + A4(0.8) +A5(-1) - Line Rej. qty(-1)) /
               Total No. of Qty Received.
Final Q.R. = Q.R. - Mix up complaints*10 - Genuine complaints * 5
Since the formula have subtraction(negative quality score) also, I don't think that this subtraction or negative score would be able to capture in FM for Quality score procedure and the notification qty will not be able to be calculated.
So, to get the quality rating as per above and getting the same for the material wise also.
After that i need to get one report for vendor wise material wise report at month period.
How should I proceed?
Thanks once again for your valuable input.
Thanks & Regards,
SUMIT GUPTA

MRP FOR On order stock

hi
Can anybody pls tell me does system consider open PO qty, On order stock qty(rejected materials), Open PR qty while MRP run.
If yes How does it happen?
If suppose I want system not to consider above stock in MRP run,
How can I do It?
Pls suggest..
Pravin

Hi,
I am not sure what you mean by "on order stock qty" (rejected materials), but if you are using MRP type PD it will look at all documents and items that will affect stock (POs, Planned orders, requisitions, sales orders, production orders, PM orders etc. etc.).
This is not configurable or changeable because the logic of PD is "Full planning" or "Plan Deterministic" (determining everything that affects stock).
You have some minor control over things such as "stock in transafer" and "blocked stock", you can decide if MRP should ignore or include these. But if you use PD then all of the above will be considered.
You can use other MRP types such as reorder point planning and this ignores all of the above and just maintains the stock levels above or equal to the reorder point. (although you can even configure reorder point MRP to take orders etc. into consideration).
So unless you switch to reorder point planning or forecast planning you will find that the above types of document / orders will be considered by MRP.
Steve B

Suppress repeated values.

Dear all,
In one of our report, we use the value PPM which is provided as user entry value. This is populated in the column of the report. This value is appearing in the report for all the charactereistic element for example material etc.,
Alongwith this there are other key figures like qty received etc., my requirement is that if the value for the keyfigure (qty received) is present only then the keyfigure PPM be displayed in the column otherwise the column should be blank.
Can any experts throw some light on how to achieve this.
Thanks in advance.
Regards,
M.M

Dear Sam,
Thank you very much for the information. I did the same and found that it is working fine. In one of the columns we have the PPM - plan which will be default display values in all rows. I have used the suppression for column,rows which have zero values (option in the query properties)- even after this i am not getting the requirement met.
My requirement is as follows.
There are key figures like receipt qty,accepted qty, rejected qty,ppm-plan and ppm.
Based on the calculation , the ppm will be displayed - if there is no receipt qty ,accepted qty and rejected qty , the ppm will also be blank(Zero) - in this case i don't want the line to be displayed. Now the line is displayed because of the default value for PPM plan.
Your suggestion is working as far as the plan is not in the column - is there any provision of achieving my requirement even when the plan is present in the column.
Your expert advise will be of much use.
Regards,
M.M

How to process TR created for 122 mov ?

Dear All,
How to process the TR created in the background for 122 mov. through QA module ?
I have not processed the TR created for the GR document. When I try to process it, the open qty in the TR is the difference between (Total GR Qty - Return Qty).
Hence the TR created for 122 mov is Open.
Please guide me how we process such TR's.
Hope my query is clear.
Regards,

Hi Prakash & Vineet,
Thanks a lot for your reply's.
See my scenario goes like this & hope this is a common one in case of vendor rejections.
when we create a GR an Inspection lot & TR will be created for the whole GR Qty say (100) with Stock type as Q (Quality).
Suppose If I do the UD for the Inspection lot where I accept 70 Qtys & Reject 30 Qtys then automatically a TR will be created for the 30 Qtys.
Since I have already rejected 30 qtys, only 70 qtys will be open in the TR which was created at the time of GR (which is yet to be processed).
So this TR can be converted into a TO & Stock can be placed in the Destination Storage type & Bin.
Now coming to the rejected qty which is getting knocked off in the interim bin itself the stock level in MM-IM & WM is balanced.
But my concern is TR which was created against the Rejected Material Doc (122) is Still Open. So what do we do with such TR's which are open?
In LB02 we can either delete this TR or change the Status to Processed.
I hope many of you might have come across this scenario. So how did you manage this? Is there any T.CODE available where we can delete or change the status of TR's as processed in a mass way ?
Hope my query is clear now.
Thanks & Regards,

Scenario for GRPO

Hi All,
         I am facing a problem here while handling a scenario in GRPO. Any suggestions would be greatly appreciated.
Scenario :
GRPO is copied from Purchase order. PO can have upto 200 line items. If the qty of any item is recieved less than the qty in the po, then we have following udf's in the GRPO at row level to update the qty;"Accepted qty, Short/Excess qty, Rejected Qty". The problem arises when accepted qty is zero, coz if the qty field of GRPO is 10 and accepeted is zero, the system still counts 10 in stock as it is system behaviour. NOw we want the stock to be updated by the accepted qty. How can this be handled??
                                                      I thought of using dropship whse in case where item is not received, but the problem arises as this can still be copied to A/P Invoice. It solves the issue at inventory level but the accounting gets affected as the material is not recieved physically.How can we handle this scenario???
Thanks in advance,
Joseph

Hi Thanga Raj,
                        Also to clear this scenario a bit more, I'll try to explain it again in brief; Billed Qty of Purchase Order would be the Qty in GRPO. Now the following cases arise;
a. The qty in the GRPO i.e. the receieved qty can be zero, meanin the item didnt arrive in the consignment.
b. The qty in GRPO can be recieved partially.
c. The clients wants to capture the details of "Accepted Qty, Short/Excess qty, Rejected Qty" on PLD and also the stock should be updated accordingly.
Any suggestions??
Thanks,
Joseph

Complex query for Reports

Hi !!
I have to create a report,which would be called from a form, and I require your help to code a query for a complex logic involving two tables. My application is on Oracle8i and Developer6. The table structures and their values are as below:
Table1
(Main-Part, Sub-Part is a composite key)
MainPart Sub-part
M0001 S0001
M0001 S0002
M0001 S0003
M0002 S0004
M0002 S0101
M0002 S0909
M0003 S1909
Table2 (Part is a primary key)
Part Qty-in-store qty-in-prodn qty-rejected
M0001 10 10 10
S0001 1 10 1
M0003 1 1 1
M0002 2 1 2
S0004 3 2 5
S0003 1 1 8
S0002 10 11 12
S0101 100 200 100
The requirement is that for every fetch of the Main-Sub part pair from table1, details should be fetched from the table2. Since the Main-Sub part pair is a composite key in table1, details from Table2 should be fetched only once for a repeating Main part but as many times for the number of sub-parts. For example, although M0001 is repeated 3 times in table1, it's details should be fetched only once from table2 whereas for the sub-parts of M0001(S0001, S0002, S0003) details should be fetched from table2 for each sub-part.
I tried a query which first fetches the details for the main-part, and in the repeating frame I put formula columns(with appropriate select stmts) for sub-parts. This approach I feel could affect performance because select statement is fired as many times as the number of formula columns.
My report should look like this
============================================================
Part qty-in-store qty-in-prodn qty-rejected
============================================================
M0001 10 10 10
S0001 1 10 1
S0002 10 11 12
S0003 1 1 8
Total 22 32 31
M0002 2 1 2
S0004 3 2 5
S0101 100 200 100
Total 105 203 107
I would like your help to know if there is another way to code a query(or queries) in report builder which will help me solve this above requirement.
Also, is it possibe to do an Update operation on a Database Table from within a report, bcos the totals as shown above need to be updated to the table?
Thanks in advance for the help?
Regards,
Ajay

John,
I believe this is to create the column types in BIRT. Can you open a
bugzilla entry to look at this?
Jason
On 7/27/2010 10:45 AM, john mcteague wrote:
> I have resolved this by changing config.xml in oda-jdbc.jar to use
> policy 1 for the jConnect driver.
>
> Policy 2 executes the query with a maxrows of 1, gets the metadata then
> executes the query again with the desired number of rows.
> Does anyone know why jConnect was set to policy 2 in the first place?

Qty reject in UD

Similar Messages

Maybe you are looking for