Table for Lot size.......

Hi All,
I am an ABAPER. I have to create a Lot size Review Report. In which transaction will i find the Lot size key, Lot size description and MRP Controller.
Thanks,
Ibrahim

Hi,
Happy new year,
U can get the lot size and mrp controller details in MARC table.
U can get the details in MRP 1 view of material master(which also has the lot size description)(t'code:mm01 /02 /03)
Regards
Edited by: Hemanth Krishna.Rai on Jan 7, 2009 2:59 PM

Similar Messages

MRP net requirement calcualtion for Lot sizes

Hi all ,
Can some one help me on this ..
I want to set up the MRP for the Raw materials Procurement .
for this i want use MRP type as PD and lot size as WB Weekly lot size .
but as per the requirement the MRP is run daily , i need clarification on certain things such as how does the system calculates the weekly lot size ? say if the requirement is converted into PR on the first day of the MRP run ,followed by that if the requirement varies does the system creates a new PR or it changes the Qty in the existing PR if its was not converted to PO .
what are the stock types considered during PR creation and how are the delivery dates determined during the PR creation ?
thanks ,
ksr

Hi Chris
You can try to set up a maximum lot size and a takt time on the material master.
Take a look on the F1 help of this field on the material master:
Takt time
If a requirement quantity (for example, for capacity reasons) cannot be procured in a single lot, you have to schedule several receipts. In conjunction with the overlap indicator in the lot size (set in Customizing for the lot size), you can use the takt time to specify that these receipts are offset, that is, that they are delayed by the takt time.
You enter the takt time in workdays.
Use
The system uses the takt time if a requirement is covered by several receipt elements due to restrictions on lot size such as maximum lot size (with all lot-sizing procedures) or rounding value (with fixed lot size with splitting).
BR
Caetano

Minimum and max lot size

Hai All,
Can anyone please tell exactly from which table we can get the data "Minimum and max lot size".
Is it "MAST" or "PLKO" or "MARC"?

Hi Kavitha,
check with the table MARC and the fileds BSTMI (Minimum lot size ) BSTMA ( Maximum lot size )
for more info
Re: Table for Lot size.......
hope it helps you.
Thanks!
Edited by: Prasanth on Mar 7, 2009 7:26 PM

Different fix lot size depending on the production version

Hi all,
I have the next scenario:
2 production versions. 2 different fix lot size por each. So:
Prod Version 1 - Fix lot size 200
Prod Version 2 - Fix lot size 300
I created the Quota Arrangement just to make SAP to take my favourite version. And trought the quota, I can define the lot size for each version. BUT.
If I change the version in the order or in the planned order, the quantity don't change.
So: How can I manage 2 different fix lot size for 2 different product versions? If I change the version once the order is created, how can I do the system change de quantity to the right one?
Thanks in advante
<< Please do not offer points >>
Edited by: Rob Burbank on Oct 1, 2010 2:53 PM

I have n't tried this scenario,
This is my Idea
Create a two production version
for ex: lot size 100 to 1000, set the rounding profile qty as 1000
for lot size 1001 to 99999, set the lot rounding profile value to 5000
BY this way u can get the two lot based on the rounding profie
Expert; please correct if i am wrong
Edited by: Sundaresan . E. V on Oct 1, 2010 4:12 PM

How to make lot size dependent in Material master?

Hello Experts,
I created a Material master for a Finished product in Pharma industry and in work scheduling screen, under the section "In house production time in days", I see that "lot size independent". What change(s) in my settings in the Material Master can change it to "lot size dependent"?
Does any changes in the "Lot size data" section in the view "MRP1" have any effect on this field?
Also one more question:
Where is the Usage for BOM first specified? Is it in material Master or when creating a BOM?
Thank you.
Message was edited by: Visu Venkat

Hi Visu
No,Lot size data in MRP1 view will not have any effect in inhouse production time in work scheduling view.
You need to maintain the base qty in work scheduling in order to get the scheduling time for lot size dependant.
BOM useage is first specified only during BOM creation.
Suppose if u maintain the BOM useage in material master before creation of BOM, then still u can create a BOM with different useage. During these case, there will be always inconsistencies.
Hence Useage is always specified first during BOM creation.
Hope u r clear now.
Regards
Vijay

SNP - Lot Size Query

Hi Experts,
I have a typical scenario for lot size.
For given product, Minimum lot size is 10000 qty.
But the incremental qty is 100.
i.e. I can product 10000, 10100, 10200, 10300 and so on..
Can anyone suggest settings required for this condition?
Thanks in Advance,
Vipul Shah

Consider maintaining 100 as Rounding Value along with the Minimum Lot Size of 10000.
Somnath

Table for the recorded result.Result automatically calculated using formula

Hi experts,
I want to know where this results will be saved(table name) when we use formula in inspection plan.I have marked char.calc in control indicator and formula has been entered in inspection plan.While entering the result when i click on calc button it is displaying correct result and i have saved.when i check the table QAMR,QASR it is not displaying the result for the MIC which i have used formula.I am able to see the formula in QAMV table.When i want to display this result can i retrive the result directly from any of the table or shall i calculate the formula in the program to display? If i should calculate the formula how to calculate?
Regards,
Shwetha.

Hii,
If u are using Inspection point for the results recording then results will get stored in QASR table. The manually entered results alone will get stored in the Original_ Input field. Calculated parameters will get stored in the mittelwert field (mean value). Kindly check QASE table for lot without inspection points.
For ex : Results Field name mean value (1.7500000000E+02)
with regards,
K.Lokesh.

Lot size EX with Minimum lot size

Hi all,
I have a query like how will the material behave if the following settings are made
MRP type:M0
Lot size:EX
Minimum lot size:100
Rounding value:100
Maximum lot size:300
My main question is is it right to use lot size EX along with mimium lot size value,rounding value,Maximum lot size defined.

Hi Anshul
Ex is lot for lot order quqntity. It will put lot size exactly what is required from MRP run. During MRP run after net requirement calculation the system will look for Lot size,Rounding value and Rounding profile before making procurement proposal.
You can use EX with Rounding value
If you requirement is 180 Nos and the rounding vaule is 100 the lot size for this will be 200.
Hope this will clear your doubt.
Regards
J. Saravan
Edited by: Jagannathan Saravanan on Feb 28, 2008 10:21 AM

Function Module Extraction from KONV Table taking lot of time for extractio

Hi
I have a requirement wherein i need to get records from KONV Table (Conditions (Transaction Data) ). i need the data corresponding to Application (KAPPL) = 'F'.
For this i had written one function module but it is taking lot of time (@ 2.5 hrs) for fetching records as there are large number of records in KONV Table.
I am pasting the Function Module code for reference.
<b>kindly guide me as to how the extraction performance can be improved.</b>
<b>Function Module Code:</b>
FUNCTION ZBW_SHPMNT_COND.
""Local interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*"     VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE OPTIONAL
*"     VALUE(I_DATAPAKID) TYPE SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
*"     VALUE(I_PRIVATE_MODE) OPTIONAL
*"     VALUE(I_CALLMODE) LIKE ROARCHD200-CALLMODE OPTIONAL
*" TABLES
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*"      E_T_DATA STRUCTURE ZBW_SHPMNT_COND OPTIONAL
*"      E_T_SOURCE_STRUCTURE_NAME OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
The input parameter I_DATAPAKID is not supported yet !
TABLES: KONV.
Auxiliary Selection criteria structure
DATA: l_s_select TYPE sbiwa_s_select.
Maximum number of lines for DB table
STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
Select ranges
RANGES: L_R_KNUMV FOR KONV-KNUMV,
          L_R_KSCHL FOR KONV-KSCHL,
          L_R_KDATU FOR KONV-KDATU.
Declaring internal tables
DATA : I_KONV LIKE KONV OCCURS 0 WITH HEADER LINE.
DATA : Begin of I_KONV occurs 0,
         MANDT LIKE konv-mandt,
         KNUMV LIKE konv-knumv,
         KPOSN LIKE konv-kposn,
         STUNR LIKE konv-stunr,
         ZAEHK LIKE konv-zaehk,
         KAPPL LIKE konv-kappl,
         KSCHL LIKE konv-kschl,
         KDATU LIKE konv-kdatu,
         KBETR LIKE konv-kbetr,
         WAERS LIKE konv-waers,
         END OF I_KONV.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
The input parameter I_DATAPAKID is not supported yet !
Invalid second initialization call -> error exit
    IF NOT g_flag_interface_initialized IS INITIAL.
      IF
        1 = 2.
        MESSAGE e008(r3).
      ENDIF.
      log_write 'E'                    "message type
                'R3'                   "message class
                '008'                  "message number
                ' '                    "message variable 1
                ' '.                   "message variable 2
      RAISE error_passed_to_mess_handler.
    ENDIF.
Check InfoSource validity
    CASE i_isource.
      WHEN 'X'.
     WHEN 'Y'.
     WHEN 'Z'.
      WHEN OTHERS.
       IF 1 = 2. MESSAGE e009(r3). ENDIF.
       log_write 'E'                  "message type
                 'R3'                 "message class
                 '009'                "message number
                 i_isource            "message variable 1
                 ' '.                 "message variable 2
       RAISE error_passed_to_mess_handler.
    ENDCASE.
Check for supported update mode
    CASE i_updmode.
For full upload
      WHEN 'F'.
      WHEN 'D'.
      WHEN OTHERS.
       IF 1 = 2. MESSAGE e011(r3). ENDIF.
       log_write 'E'                  "message type
                 'R3'                 "message class
                 '011'                "message number
                 i_updmode            "message variable 1
                 ' '.                 "message variable 2
       RAISE error_passed_to_mess_handler.
    ENDCASE.
    APPEND LINES OF i_t_select TO g_t_select.
Fill parameter buffer for data extraction calls
    g_s_interface-requnr    = i_requnr.
    g_s_interface-isource   = i_isource.
    g_s_interface-maxsize   = i_maxsize.
    g_s_interface-initflag = i_initflag.
    g_s_interface-updmode   = i_updmode.
    g_s_interface-datapakid = i_datapakid.
    g_flag_interface_initialized = sbiwa_c_flag_on.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF i_t_fields TO g_t_fields.
Interpretation of date selection for generic extraktion
   CALL FUNCTION 'RSA3_DATE_RANGE_CONVERT'
     TABLES
       i_t_select = g_t_select.
ELSE.                 "Initialization mode or data extraction ?
   CASE g_s_interface-updmode.
     WHEN 'F' OR 'C' OR 'I'.
First data package -> OPEN CURSOR
    IF g_counter_datapakid = 0.
   L_MAXSIZE = G_S_INTERFACE-MAXSIZE.
      LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'KNUMV'.
        MOVE-CORRESPONDING l_s_select TO l_r_knumv.
        APPEND l_r_knumv.
      ENDLOOP.
      LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'KSCHL'.
        MOVE-CORRESPONDING l_s_select TO l_r_kschl.
        APPEND l_r_kschl.
      ENDLOOP.
      Loop AT g_t_select INTO l_s_select WHERE fieldnm = 'KDATU'.
        MOVE-CORRESPONDING l_s_select TO l_r_kdatu.
        APPEND l_r_kdatu.
      ENDLOOP.
*In case of full upload
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
   APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
      OPEN CURSOR G_CURSOR FOR
        SELECT MANDT
               KNUMV
               KPOSN
               STUNR
               ZAEHK
               KAPPL
               KSCHL
               KDATU
               KBETR
               WAERS
        FROM   KONV
        WHERE KNUMV IN l_r_knumv
        AND   KSCHL IN l_r_kschl
        AND   KDATU IN l_r_kdatu
        AND   KAPPL EQ 'F'.
    ENDIF.
    Refresh I_KONV.
    FETCH NEXT CURSOR G_CURSOR
               APPENDING CORRESPONDING FIELDS OF TABLE I_KONV
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR G_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    LOOP AT I_KONV.
     IF I_KONV-KAPPL EQ 'F'.
      CLEAR :E_T_DATA.
      E_T_DATA-MANDT = I_KONV-MANDT.
      E_T_DATA-KNUMV = I_KONV-KNUMV.
      E_T_DATA-KPOSN = I_KONV-KPOSN.
      E_T_DATA-STUNR = I_KONV-STUNR.
      E_T_DATA-ZAEHK = I_KONV-ZAEHK.
      E_T_DATA-KAPPL = I_KONV-KAPPL.
      E_T_DATA-KSCHL = I_KONV-KSCHL.
      E_T_DATA-KDATU = I_KONV-KDATU.
      E_T_DATA-KBETR = I_KONV-KBETR.
      E_T_DATA-WAERS = I_KONV-WAERS.
      APPEND E_T_DATA.
   ENDIF.
    ENDLOOP.
    g_counter_datapakid = g_counter_datapakid + 1.
ENDIF.
ENDFUNCTION.
Thanks in Advance
Regards
Swapnil.

Hi,
one option to investigate is to select the data with a condition on KNUMV (primary IDX).
Since shipment costs are store in VFKP I would investigate if all your F condition records are used in this table (field VFKP-KNUMV).
If this is the case then something like
SELECT *
FROM KONV
WHERE KNUMV IN (SELECT DISTINCT KNUMV FROM VFKP)
or
SELECT DISTINCT KNUMV
INTO CORRESPONDING FIELD OF <itab>
FROM VFKP
and then
SELECT *
FROM KONV
FOR ALL ENTRIES IN <itab>
WHERE...
will definitively speed it up.
hope this helps....
Olivier

Sequence dependent lot-size planning as a basis for PP/DS blocks?

Hi ,
I consider the following system setup for a Mill Products planning implementation .
1) In SNP one performs SOP planning with common goals to adjust sales plan, establish equipment maintenance plan, transportation plan, etc. The first month of the SNP plan is supposed to be in daily buckets. Using the SNP optimizer is a good option since the business goal is to use equipment more efficiently, let's say to minimize setup costs, and there are warehouse limitations for semifinished products as well.
2) In PP/DS we are going to use CDP and block planning since it is the best practice.
3) SNP planned orders can be used as a basis for PP/DS blocks on the resource, upon the condition that the configuration of SNP product - kmat variant and block requirements match.
In SNP i see that the SNP PDS has a duration of 1 day (that's fine), but the sequence dependent lot-size planning requires a bucket of at least 1 week long (1 month in my case) since the SNP orders are sequence-optimized only inside of one bucket. The result of such an optimization are additional counters assigned to SNP orders according to their sequence minimizing setup costs. However, orders are not scheduled according to the sequence.
So far it looks like such a combination is not useful as
- Orders in monthly buckets are not scheduled on days and cannot serve as a basis for block dates proposal for PP/DS block planning.
- If a product production volume is less than 1 day, SNP cannot create any more detailed block in principle since the minimal time bucket is daily bucket.
I searched over forums on these or similar topics, however no definitive answer so far for the question in the subj.
Could anyone bring more light on this ? Maybe I am missing something in the setup or sequence dependent lot size planning was designed for other purposes/industries?
Best regards
Vladimir

Hello Asim,
Issue one
in product selection for propagation range you can set your selection criteria which selects the products dynamically. You just have to change your report variants for planning run. Do I misunderstand your concerns?
Issue two
Changing to planning procedure 1 will not delete the PFE but will prevent APO to create a new entry after any MRP-relevant changes happen or heuristic SAP_PP_020 (which creates the initial entry and does the low level code determination) is run.
In some cases procedure 1 will still create a PFE. Please check customizing for details. Thats why I would recommend to create a new planning procedure with "no reactions".
As soon as you prevent APO from creating new PFEs you can just once delete the PFEs in /SAPAPO/NETCH by just setting the first column for these materials blank (select your materials, mark column, delete indicator).
Corresponding table to MDVM is /SAPAPO/PEGKEY. Indicator for PP/DS is NETCH_RRP.
If material is not planned in APO you do not need a PFE in APO.
Issue 3
Maybe utilize table /SAPAP/PEGKEY
As I said if you prevent creating the entry you just have to delete (set indicator blank) once.
Hope that helps.
Regards,
Uli

Report for Reorder point, safety stock, current stock and fixed lot size

Hi,
Purchasing Dept. is looking for a report which can give list of materials falling below the reorder point, so that they can go ahead and create procurement proposals for those materials.
They also want to see the Reorder Point, Safety Stock, current stock and fixed lot size in the same report.
Let me know if there ia any standard report availbale which displays the same or any approach to get the same.
Thanks in Advance.
Regards,
Shankar Goud.

Hi,
There is no standard report because this is meant to be managed by the MRP run.
The MRP lists show all materials that have a problem (such as stock below reorderpoint) but MRP generates requirements for these anyway and so all you need to do is to look for the MRP generated requirements (requisitions?) and you have your list?
Are you using MRP?
If so then please use the standard functions in MRP to get this.
If not, then WHY NOT?
Steve B

Lot size calculation for Purchase order

Hi all,
I want to purchase Labels which comes in lot qty such as in lot of 100,200 etc.
For that particular items i want to do mandatory qty lot size in PO when buyers places the purchase order.
Can anybody tell me How i can map that lot size for the particular item.
Regards,
Anant

Hi,
You can done it with change Material Master.
Enter MM02 t-code, enter your material code and select MRP1 view.
Here maintain Rounding value as 100 in material master.
After when your create purchase order system put quantity as 100, 200, 300 etc.
Regards,
Mahesh R.

Lot size in BOM as well as for alternate material

how can we define the Lot size and validity period for a BOM means we want to define that 1 to 100 qty are to be produced with alternate 1 and 101 to 1000 for alternate 2. How the same can be defined in the master BOM.
There is one component in the BOM and there is a alternate material is also, Users want to define that while issuing the material , system allow to issue only say qty " 50" and then alternate material for next lot.
Is there any possibility to define the BOM as per the above requirement.
thanks
harish

Dear Harish,
if u have alternative BOM's, then creat production versions
1) creat BOM with two alternatives (say alt 1 1to 100 & alt 2 101 to 200)
2) creat multiple Routings with two group counters
3) creat production version in MM02 in MRP 4 view or work scheduling view
4) in BOM slection in MRP 4 view maitain the prameter as 3 or 4
Then MRP takes care of lot sizes difined in PV & BOM and creat procurment proposals
Regards
kumar
Edited by: kumar kumar on Aug 3, 2009 8:02 AM

Rounding Value is not considered for MB lot size

Hi
I have a scenario where MB (Monthly Lot size) lot size is used with rounding value. Example as below:
Lot size: MB
Min Lot size: 15000
Rounding Value: 20000
DEMAND: 16000
When MRP run, System is creating the 16000 as P Req instead of 20000 which is the rounding value.
Pl let me know, if I need to apply OSS note / any other solution for this.
Thanks,
JK
Edited by: Janakiram Katakam on May 17, 2010 4:57 AM

Dear ,
Are you using any Rouding Profile in MRP1 view ?
What is the Setup in OMI4 for MB-Lot Size .Remove the tick mark in Last Lot Exat if it is marked .By specifing the rounding value, the system will determine during lot size calculation that lot size qty is a multiple of of an order unit(eg : pallet size if mtrl is delivered in entire pallets...).
Please check what is the Lot Size Indicator or Lot size procedure assinged to it ?
2.you can use rounding profiles...its used to define the setting of rounding up or rounding down the order proposal qty into deliverable quantities...rounding profile maintenance the t-code is OWD1. Here for static rounding profile
Rounding profiles are defined under:
spro-> purchasing->consumption based planning->planning->lot size calculation ->maintain rounding profiles...
it consist of threshold value and rounding value...
the threshold val is the value from which the system rounds the value of the next deliverable units upto...
the rounding value is from which the systemshd round up to as soon as threshold value is exceeded...
Otherwise , Check FM MD_ROUNDING_VALUE
Regards
JH
Regards
JH

Default lot size for MRP type

Hi,
Can we set default Lot size for MRP type ?
Regards
Karthik

Dear,
Yes you can do it by creating material master with MRP Pofile.
First you need to create MRP Pofile in MMD1 where you need to define the LOT SIZE and MRP TYPE which you want then make these value as Fix Value.
Then Create material master MM01 with this MRP Profile and check your result.
Regards,
R.Brahmankar

Table for Lot size.......

Similar Messages

Maybe you are looking for