Net weight in unit of measure (MM03)

Hi,
I have to extract all the units of measure for an article and i was wondering where does this field (Net weight) come from.
I think it's calculated but how ?
Allready have some other fields from MARM and find the net weight in mara but as i have many lines of untis of measure, the mara net weight does not apply to all.
Thanks

Thank you again for your time.
I'm trying to extract all datas from that screen so the access to the screen is MM03 or MM02 (i checked and they both have same datas) if that was your concern.
I see those two fields (Number of Lower-Level Units of Measure (SMEINH-AZSUB) and Lower-Level Unit of Measure in a Packing Hierarchy (SMEINH-MESUB), at the end of both records under Number and LUn as you can see in that screen copy
http://img354.imageshack.us/img354/3219/sanstitredx2.jpg
i found a fm (BAPI_MATERIAL_GETALL) that returns the weight for every record so the weight is not a problem anymore for my report. Even if i don't understand why i can change some lines and can not others.
But i really can't find those two last column
Edited by: Alan Ford on Jul 10, 2008 2:27 PM

Similar Messages

  • Gross weight and net weight of line item in a delivery

    Hi what exactly the meaning of gross weight and netweight of delivery line item?
    Where can i see these 2 fields in the transaction?How weight differs to the quantity for a particular delivery item?
    Thanks in advane
    Mahesh

    Hi,
    <b>Gross Weight</b>
    The system can use the <b>gross weight</b> at a later stage, depending on what kind of capacity check you run, to check storage bin capacity for warehouse management purposes.
    The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order. If there is no related sales order, the system uses the gross weight from the material master record. You can change the gross weight manually in the delivery document.
    <b>Net weight</b>
    The total net weight of all items in the delivery.
    Use
    The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record.
    Please reward if helpful.
    Thanks & Regards
    Sadhu Kishore

  • Production Order for a Material with two units of measure?

    Hi Everybody I have the following issue.
    In my company there is a new production process with a Material that should be configured in the master data with the field "Base Unit of Measure" as per unit (each). But the production process, should be confirmed by tx CO11N, in Kilograms. I know that I can use the additional Data in tx MM03 to set a Production Unit, but the value of convertion would be fixed. For example 122 Kg = 1 each, the thing is that the value in kilograms for each lot can vary, one lot can weight 122 and another one can weghr 125, and in each case I shoul have two units in stock. And as I have the value of convertion fixed, when I confirm each lot one for 122 kg and another for 125 kg I will have 2.025 units in MB52.
    How can I solve this problems? I need to have the chance the confirm in kg changing for each lote the quantity but in the base Unit of Measure have one unit for lot. As if for tx CO11N I could have a field where I can set tha x quantity of Kilograms is x each.
    Kind regards
    Leandro. 

    Hi Ayoub, First thank`s for your promt answer,
    1. The Quantity is different, because is not a perfect process, there is a manual work in the process that makes this quantity differ, there is no big difference, maybe a Kilo or Two but the production mannager wants to have this registered. And besides in productions they manage kilograms, but for selling the comercials manage units (each - EA)
    2.The convertion rate is known at the end of the process after cutting and packaging a unit, they weight it.
    Regards
    Leandro

  • Unit of measure error in BAPI_MATERIAL_SAVEDATA

    Hi Guru's,
    i am trying to upload the material master data using BAPI...while uploading ia m getting beloow error ..please guide me anyone you..where i am doing mistake.....
    1st this error i am getting while executing:
    internal unit HR ,language EN is not maintained.
    and afetr execution in gs_return i am getting below error:
    Unit of measure ****** is not defined; check your entry
    error number :490
    dont get tence for code and all the values ae moving properly into BAPI...and
    here i am consider the unit of mesure as HR (hour)..
    here i am caliculating like ex: for employe (material) generating bill in hour basis.that is per 1hour $100.
    please let me know if my question is not clear..
    thanks in advance and will full points to reply....
    *& Report  ZERP_MATERIAL_CREATE_UPLOAD
    REPORT  zerp_material_create_upload.
    DATA:gs_bapimathead          TYPE bapimathead,
         gs_clientdata           TYPE bapi_mara,
         gs_clientdatax          TYPE bapi_marax,
         gs_plantdata            TYPE bapi_marc,
         gs_plantdatax           TYPE bapi_marcx,
         gs_forecastparameters   TYPE bapi_mpop,
         gs_forecastparametersx  TYPE bapi_mpopx,
         gs_valuationdata        TYPE bapi_mbew,
         gs_valuationdatax       TYPE bapi_mbewx,
         gs_salesdata            TYPE bapi_mvke,
         gs_salesdatax           TYPE bapi_mvkex,
         gs_storagelocationdata  TYPE bapi_mard,
         gs_storagelocationdatax TYPE bapi_mardx,
         gt_materialdescription  TYPE STANDARD TABLE OF bapi_makt,
         gwa_materialdescription TYPE bapi_makt,
         gt_taxclassifications   TYPE STANDARD TABLE OF bapi_mlan,
         gwa_taxclassifications  TYPE bapi_mlan,
         gt_prtdata              TYPE STANDARD TABLE OF bapi_mfhm,
         gwa_prtdata             TYPE bapi_mfhm,
         gt_prtdatax             TYPE STANDARD TABLE OF bapi_mfhmx,
         gwa_prtdatax            TYPE bapi_mfhmx,
         gt_unitsofmeasure       TYPE STANDARD TABLE OF bapi_marm,
         gwa_unitsofmeasure      TYPE bapi_marm,
         gt_unitsofmeasurex      TYPE STANDARD TABLE OF bapi_marmx,
         gwa_unitsofmeasurex     TYPE bapi_marmx,
         gs_return               TYPE bapiret2.
    TYPES:BEGIN OF gty_itab1,
             matnr(18),   "material
             mbrsh(1),    "industry sector
             mtart(4),    "material type
             vkorg(4),    "sales org
             vtweg(2),    "distr chan
             kondm(2),    "mat prcing grp
             ktgrm(2),    "acc asgn grp
             dwerk(4),    "plant
             meins(3),    "base uom
             tragr(4),    "tarns grp
             matkl(9),    "mat grp
             spart(2),    "division
             ntgew(13),   "net weight
             gewei(3),    "weight unit
             werks(4),    "plant
             ladgr(4),    "loading grp
             dismm(2),    "mrp type
             mtvfp(2),    "available check
             disgr(4),    "mrp grp
             dispo(3),    "mrp controller
             beskz(1),    "procurement type
             prmod(1),    "forecasting mode
             bklas(4),    "valution class
             stprs(11),   "std price
             vprsv(1),    "price control
             peinh(5),    "price unit
             lgort(4),    "storage location
             maktx(40),   "mat description
             taxkm(1),    "tax class
             planv(3),    "task list usage
             brgew(13),   "gross weight
             mtpos(4),    "gen it gross grp
          END OF gty_itab1.
    DATA:gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
         gwa_itab1 TYPE gty_itab1.
    TYPES:BEGIN OF gty_itab2,
          abc(178),
    END OF gty_itab2.
    DATA:gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
         gwa_itab2 TYPE gty_itab2.
    PARAMETERS:p_files TYPE string.
    *START-OF-SELECTION.
    START-OF-SELECTION.
    *using call method uploading CSV file into internal table
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename                = p_files
          filetype                = 'ASC'
        TABLES
          data_tab                = gt_itab2
        EXCEPTIONS
          file_open_error         = 1
          file_read_error         = 2
          no_batch                = 3
          gui_refuse_filetransfer = 4
          invalid_type            = 5
          no_authority            = 6
          unknown_error           = 7
          bad_data_format         = 8
          header_not_allowed      = 9
          separator_not_allowed   = 10
          header_too_long         = 11
          unknown_dp_error        = 12
          access_denied           = 13
          dp_out_of_memory        = 14
          disk_full               = 15
          dp_timeout              = 16
          OTHERS                  = 17.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      LOOP AT gt_itab2 INTO gwa_itab2.
        gwa_itab1 = gwa_itab2-abc(178).
        APPEND gwa_itab1 TO gt_itab1.
      ENDLOOP.
      LOOP AT gt_itab1 INTO gwa_itab1.
        SPLIT gwa_itab1 AT ',' INTO
              gwa_itab1-matnr
              gwa_itab1-mbrsh
              gwa_itab1-mtart
              gwa_itab1-vkorg
              gwa_itab1-vtweg
              gwa_itab1-kondm
              gwa_itab1-ktgrm
              gwa_itab1-dwerk
              gwa_itab1-meins
              gwa_itab1-tragr
              gwa_itab1-matkl
              gwa_itab1-spart
              gwa_itab1-ntgew
              gwa_itab1-gewei
              gwa_itab1-werks
              gwa_itab1-ladgr
              gwa_itab1-dismm
              gwa_itab1-mtvfp
              gwa_itab1-disgr
              gwa_itab1-dispo
              gwa_itab1-beskz
              gwa_itab1-prmod
              gwa_itab1-bklas
              gwa_itab1-stprs
              gwa_itab1-vprsv
              gwa_itab1-peinh
              gwa_itab1-lgort
              gwa_itab1-maktx
              gwa_itab1-taxkm
              gwa_itab1-planv
              gwa_itab1-brgew
              gwa_itab1-mtpos.
    *header data
        gs_bapimathead-material                      = gwa_itab1-matnr.
        gs_bapimathead-ind_sector                    = gwa_itab1-mbrsh.
        gs_bapimathead-matl_type                     = gwa_itab1-mtart.
        gs_bapimathead-basic_view                      = 'X'.
        gs_bapimathead-sales_view                      = 'X'.
        gs_bapimathead-purchase_view                   = 'X'.
        gs_bapimathead-mrp_view                        = 'X'.
        gs_bapimathead-storage_view                    = 'X'.
        gs_bapimathead-account_view                    = 'X'.
        gs_bapimathead-cost_view                       = 'X'.
    *sales data
        gs_salesdata-sales_org                       = gwa_itab1-vkorg.
        gs_salesdatax-sales_org                      = '8888'.   "'X'.
        gs_salesdata-distr_chan                      = gwa_itab1-vtweg.
        gs_salesdatax-distr_chan                     = '88'.   "'X'.
        gs_salesdata-mat_pr_grp                      = gwa_itab1-kondm.
        gs_salesdatax-mat_pr_grp                     = 'X'.
        gs_salesdata-acct_assgt                      = gwa_itab1-ktgrm.
        gs_salesdatax-acct_assgt                     = 'X'.
        gs_salesdata-delyg_plnt                      = gwa_itab1-dwerk.
        gs_salesdatax-delyg_plnt                     = 'X'.
    *client data
        gs_clientdata-base_uom                       = 'HR '.   "gwa_itab1-meins.
        gs_clientdatax-base_uom                      = 'X'.
        gs_clientdata-trans_grp                      = gwa_itab1-tragr.
        gs_clientdatax-trans_grp                     = 'X'.
        gs_clientdata-matl_group                     = gwa_itab1-matkl.
        gs_clientdatax-matl_group                    = 'X'.
        gs_clientdata-division                       = gwa_itab1-spart.
        gs_clientdatax-division                      = 'X'.
        gs_clientdata-net_weight                     = gwa_itab1-ntgew.
        gs_clientdatax-net_weight                    = 'X'.
        gs_clientdata-unit_of_wt                     = gwa_itab1-gewei.
        gs_clientdatax-unit_of_wt                    = 'X'.
       gs_clientdata-item_cat                       = gwa_itab1-mtpos.
       gs_clientdatax-item_cat                      = 'X'.
    *Plant data
        gs_plantdata-plant                           = '8888'. "gwa_itab1-werks.
        gs_plantdatax-plant                          = '8888'.   "'X'.
        gs_plantdata-loadinggrp                      = gwa_itab1-ladgr.
        gs_plantdatax-loadinggrp                     = 'X'.
        gs_plantdata-mrp_type                        = gwa_itab1-dismm.
        gs_plantdatax-mrp_type                       = 'X'.
        gs_plantdata-availcheck                      = gwa_itab1-mtvfp.
        gs_plantdatax-availcheck                     = 'X'.
        gs_plantdata-mrp_group                       = gwa_itab1-disgr.
        gs_plantdatax-mrp_group                      = 'X'.
        gs_plantdata-mrp_ctrler                      = gwa_itab1-dispo.
        gs_plantdatax-mrp_ctrler                     = 'X'.
        gs_plantdata-proc_type                       = gwa_itab1-beskz.
        gs_plantdatax-proc_type                      = 'X'.
        gs_plantdata-period_ind                      = 'M'.   "HARD CODED FOR PERKZ peroid indicator
        gs_plantdatax-period_ind                     = 'X'.
        gs_plantdata-inhseprodt                      = '0'.   "hard coded for DZEIT inhouse production
        gs_plantdatax-inhseprodt                     = 'X'.
    *forecast parameeters
        gs_forecastparameters-plant                  = '8888'.   "gwa_itab1-prmod.
        gs_forecastparametersx-plant                 = '8888'.   "'X'.
        gs_forecastparameters-fore_model             = gwa_itab1-prmod.
        gs_forecastparametersx-fore_model            = 'X'.
    *valution data
        gs_valuationdata-val_area                   = '8888'. "gwa_itab1-bklas.
        gs_valuationdatax-val_area                  = '8888'.   "'X'.
        gs_valuationdata-val_class                   = gwa_itab1-bklas.
        gs_valuationdatax-val_class                  = 'X'.
        gs_valuationdata-std_price                   = gwa_itab1-stprs.
        gs_valuationdatax-std_price                  = 'X'.
        gs_valuationdata-price_ctrl                  = gwa_itab1-vprsv.
        gs_valuationdatax-price_ctrl                 = 'X'.
        gs_valuationdata-price_unit                  = gwa_itab1-peinh.
        gs_valuationdatax-price_unit                 = 'X'.
    *storage location dat
        gs_storagelocationdata-plant              = '8888'.  "gwa_itab1-lgort.
        gs_storagelocationdatax-plant             = '8888'.  "'X'.
        gs_storagelocationdata-stge_loc              = gwa_itab1-lgort.
        gs_storagelocationdatax-stge_loc             = '8888'.   "'X'.
    *material discription
        gwa_materialdescription-langu                = 'E'.
        gwa_materialdescription-matl_desc            = gwa_itab1-maktx.
    *tax classification
       gwa_taxclassifications-taxclass_1            = gwa_itab1-taxkm.
        gwa_taxclassifications-depcountry            = 'US '.         "HARD CODE FOR TAX
    *prt data
        gwa_prtdata-plant                        = '8888'.   "gwa_itab1-planv.
        gwa_prtdatax-plant                       = '8888'.   "'X'.
        gwa_prtdata-prt_usage                        = gwa_itab1-planv.
        gwa_prtdatax-prt_usage                       = 'X'.
    *unitsof measure
        gwa_unitsofmeasure-alt_unit                  = 'HR '.   "gwa_itab1-brgew.
        gwa_unitsofmeasurex-alt_unit                  = 'HR '.  "'X'.
        gwa_unitsofmeasure-unit_of_wt                  = 'KG'.    "gwa_itab1-brgew.
        gwa_unitsofmeasurex-unit_of_wt                  = 'X'.
        gwa_unitsofmeasurex-sub_uom                  = 'X'.
        gwa_unitsofmeasure-gross_wt                  = gwa_itab1-brgew.
        gwa_unitsofmeasurex-gross_wt                  = 'X'.
    *appending workarea to table's
        APPEND gwa_materialdescription    TO gt_materialdescription.
        APPEND gwa_taxclassifications     TO gt_taxclassifications.
        APPEND gwa_prtdata                TO gt_prtdata.
        APPEND gwa_prtdatax               TO gt_prtdatax.
        APPEND gwa_unitsofmeasure         TO gt_unitsofmeasure.
        APPEND gwa_unitsofmeasurex        TO gt_unitsofmeasurex.
    *calling FM BAPI for uploading the Material master data
        CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
          EXPORTING
            headdata            = gs_bapimathead
            clientdata          = gs_clientdata
            clientdatax         = gs_clientdatax
            plantdata           = gs_plantdata
            plantdatax          = gs_plantdatax
            forecastparameters  = gs_forecastparameters
            forecastparametersx = gs_forecastparametersx
            valuationdata       = gs_valuationdata
            valuationdatax      = gs_valuationdatax
            salesdata           = gs_salesdata
            salesdatax          = gs_salesdatax
          IMPORTING
            return              = gs_return
          TABLES
            materialdescription = gt_materialdescription
            unitsofmeasure      = gt_unitsofmeasure
            unitsofmeasurex     = gt_unitsofmeasurex
            taxclassifications  = gt_taxclassifications
            prtdata             = gt_prtdata
            prtdatax            = gt_prtdatax.
    Check the return table.
        IF sy-subrc NE 0.
          CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
          WRITE: / 'Error occured while creating material'.
        ELSE.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
          WRITE: / 'material',gwa_itab1-matnr,'created'.
        ENDIF.
      ENDLOOP.

    Hi Aparna..
    even with HUR also i am getting same error.....
    is there any changes required in the SPRO .......
    i mean in BAPI had ..unitofmeasure we have around 21 fields( here extra fields is DEL FLAG)
                          but in unitofmeasurex has only 20 fields...
    we need to anything in SPRO for avoiding DEL FLAG.....
    sorry if i am confusing u.....
    thanks for responce and send few more inputs for resolving the issuee....

  • Pricing Procedure for diffrent unit of measure for diffrent product

    1) Existing Pricing procedure --> Condition type based on Quantity
    2) Existing Product --> Sales Unit & Base Unit of Measurement is in NOS ( Numbers )
    3) New Product ( Belt ) ---> Pricing of product based on weight
    ex :--> Rubber Belt -->   1 belt = 11.50 kg , Price = Rs. 100/ kg
    As the production of material will go on weight of Belt will reduce in range of 11.50 to 11 kg . For different batch of production weight will change
    every time weight of material will be calculated and price will be charged on basis of net weight ( Kg)
    4) New product is assigned to new division ( it will bw sold in new division only )
    Question
    1) What should be Base Unit / Sales Unit  of measurement ?
    2) Do we need to create new pricing procedure or existing pricing procedure will work ?
      for new product  we need to create new condition type for which calculation type will be Net Weight .
    3) do we need to do any customization for this ?
    Exice people say that if pricing is done in KG (Net weight ) they want to see stock in KG
    Management want to see stock in KG & Numbers

    May be you can Create a New Unit Of Measure called ZPC. For using ZPC you need to assign Additional Base Unti Of Measure as ZPC in your Material Masters as well.
    Use ZPC to create your condition records of pricing and in Sales order you will still have Unit of Measure as PC which the management wants to see..
    Similarly you can create Constion records for new product based on Kg.

  • Alternative unit of measure.. how in this scenario?

    Hi,
    KG is our base unit of measure
    and we would to use Littres(L) as the purchasing unit for this material.
    Therefore, we tried in system adding litres as alternative unit of measure.
    But we cannot figure out how to put in the density 0,87 kg/l as net weight only as gross weight.
    I have tried the below but system complained that "decimal places are not permitted"
    X----AUN-<=YBUnGrossWeight--NetWeight
    1-----L--<=-0,87--KG-0,87--
    1,000
    1,149-L--<=1--KG-0,87--
    1,000
    any clue?
    tjanks
    Tuff

    In purchasing view after defining alternative unit of measurement as L a POP up appears there you maintain as ,
    For ex:1kg-0.87L, then maintain such as 100 KG-87L.to avoide the decimal places.

  • Base and alternate unit of measure  - Per PO conversion

    Hi,
    Here is my problem :
    I buy let's say 100 M of Configurable Material A, the weight  Stock unit (KG) is expected 50 .
    Now buy another 100 M of Configurable Material A, the weight  Stock unit (KG) is expected 100 . because of a slightly configuration change.
    I which I can change the conversion between Buying Unit and Stock Unit on the PO itself ( UMREN - UMREZ ) depending on the user input or config changes (feg dependency like we do on sales).
    I didn't find the right zone to unlock these two fields  in the "SPRO  ... Define screen layout at doc level" , and I am not sure it is the right way to reach my goal.

    Hi,
    BASE UOM is the unit of measure which will be used by business to calculate the weight of the goods or rather the Unit of measure in which stocks of the material are managed.
    Say for example I create one bulb. The base UOM is PCE or Piece.
    It means that the Bulb will be referred to as 1 Piece irrespective of its weight.
    So if in the sales order i put 10 PCE of Bulb it means 10 individual unit of the bulb.
    Alternative UOM is the Unit of measure in which quantities can be entered alternatively to the base unit of measure / stockkeeping unit.
    Say for example in our cases; we are selling these bulbs in boxes.
    I BOX = 10 PCE .
    So BOX becomes your alternate UOM.
    The relation is maintained in MARM table via the additional view in the Material Master (MM01/ MM02/ MM03 transaction)
    The relation 1 : 10 is managed by the UMREN UMREZ fields in MARM.
    I hope this is useful for you.
    Regards,
    Ankur Parab

  • Base and alternate unit of measure

    HI,
    can anyone please tell me
    1) what is base unit of measure and alternate unit of measure.
    2) what is the relationship between these two.
    i have one program which currently calculates base unit of measure for all the unit costs and now i need to calculate the alternate unit of measure for all the unit cost
    I heard that relationship of these two will be found in MARM table but i couldnt find it
    Please tell me how do i do achieve it.
    Thanks,
    Ahmed.

    Hi,
    BASE UOM is the unit of measure which will be used by business to calculate the weight of the goods or rather the Unit of measure in which stocks of the material are managed.
    Say for example I create one bulb. The base UOM is PCE or Piece.
    It means that the Bulb will be referred to as 1 Piece irrespective of its weight.
    So if in the sales order i put 10 PCE of Bulb it means 10 individual unit of the bulb.
    Alternative UOM is the Unit of measure in which quantities can be entered alternatively to the base unit of measure / stockkeeping unit.
    Say for example in our cases; we are selling these bulbs in boxes.
    I BOX = 10 PCE .
    So BOX becomes your alternate UOM.
    The relation is maintained in MARM table via the additional view in the Material Master (MM01/ MM02/ MM03 transaction)
    The relation 1 : 10 is managed by the UMREN UMREZ fields in MARM.
    I hope this is useful for you.
    Regards,
    Ankur Parab

  • Alternate Unit of Measure with several Qty KF's

    Case is as follows:
    3 different plain KFs related to qty. Sales volume, net weight anddelivery qty.
    All need to be dispalyed in the same report. All have different base unit of measure.
    I have only one variable [YTAUNIT) for entering required unit.
    Now if I enter all KFs using this same YTAUNIT variable for them each separately I get error message on the query that this is not permitted.
    How should I change the structure ?
    - add new variable for each KF ? (YTAUNIT1, YTAUNIT2, .....) -> do I need to change any of the ABAP codes? is there a link only picking YTAUNIT ?
    Please can You give me an example (detailed) how to proceed ?
    Thanks in advance
    Petri

    Hi,
    I have worked on single variable But from the understanding of working I feel you need to create three diff variable (input var) YTAUNIT1, YTAUNIT2 ect Because they are on same base unit of measure with different units of measures. And you will have to take corresponding variable for every key figure in the calculated KF.
    Just try with different variables.
    Assign points if it helps.
    Regards,
    Wrushali

  • Reg. Net weight for AUOM

    Hi All,
    I have a doubt.
    In Material master for a material i have maintained Gross weight and Net weight.Besides i have maintained AUOM in Additional data tab.
    But here i am unable to key in the Net weight for AUOM and it is getting updated accoridng to the proportion with the net weight of BUOM. The field net weight is non ediatble for AUOM only gross weight is editable.
    Is this standard behavior?
    If i want to edit the Net weight of AUOM means is it possible?
    Kindly advise.
    Regards,
    MBN.

    Hi MBN,
    Gross and net weight will have same unit of measure that would be alternative unit of measure or base unit of measure. Same values will get captured to unit of measure tab from basic data.
    As standard net and gross weight fields are editable. You can check your material  master field setting.
    Regards,
    R.Brahmankar

  • Material Ledger Unit Of Measurement different from Material Master

    Dear Team,
    In my client, there is a difference between unit visible in CKM3N and MM03. The base unit of measurement in MM03 is MT. Other than that, there are some other units maintained (not M3) in additional data tab in material master. In CKM3N, the visible unit is M3. M3 is not present anywhere in MM03.
    Why would such unit flow in material ledger table? (CKMLPP has unit M3). Please advise.
    One more observation is that when there is some price change document in Material Ledger, the proper UoM (MT) is being captured. Only in the basic price determination structure visible unit for each head is M3. Please check the attached screen shot.
    Any help would be appreciated.
    Thanks.
    Jay Shah.

    Hi..
    Refer to Data Inconsistency of BUOM in Material Ledger Tables

  • Unit of Measure in material master

    Hi
    I have a Raw material consider (Forging) for which material master is maintained  "PC"  as Base unit of Measure. I have defined in Additional Unit of Measure as 500 KG = 1 PC. Also my order unit is also maintained as PC.
    Here when they procure castings they order it as 1 PC only. But when the actual material comes there may be some variation in weight.  The client wants to make payment on actual weight basis only .
    Also stock keeping unit and issue of material is done as PC only.
    Please guide me how to address this issue.
    Regards
    Kumar.

    Hi
    With the existing master data you can acheive your requirement.You can maintain the price in info record in Kgs or in PO Item conditions tab you can maintain the price per kg.
    while doing the miro please enter the actual quantity in<b> Qty in PO price unit</b> in Quantity tab ans save the GR.When you do MIRO, system will propose Qty as 1PC and value as <b>Qty in PO price unit X Price per kg</b> maintained in PO.Please try this solution.
    Regards
    Ramakrishna

  • Unit of measure for a pallet layer in MATMAS03

    Hi all,
    maybe ths is not the correct forum where to post this question, if  it's out of topic I apologize in advance.
    Fast question:
    What is LAY? it is  alternative unit of measure for pallet layers?
    When i receive the IDOC i recieve LR as UOM, what is the relation between LR and LAY?
    Thanks & regards
    Andrea

    These units could have been defined only in your system (I don't see them in ours). If it is so, no one here will be able to answer.
    The conversion factors could be in Material Master (MM03), on Basic Data screen click Additional Data button and go to the Units of Measure tab. Also see tables MARM and T006.

  • Multiple units of measure

    Dear all MM experts,
    I have one semi finished goods which having two units of measure.I m giving one example as per the client business process.
    One artificial cubicle stone is being manufactured of weight 8.00 metric tonnes. In one production order @ 20 stones are
    manufactured. When the production gets completed, the weight cannot be same for each stone. It is like 7.9 tonnes,8.1 Tonnes.7.96 tonnes,7.5 Tonnes and so on. means all 20 stones have different weight.
    Now in this case if i decide to keep base unti of measure for stone is "each", then  where should i take the "weight" factor? as
    for stones, two units of measure are given one is "each" and another is "tonnes" in client excel system.
    and moreover the another measurement i.e. length,breadth,and height are also mentioned for the cubic stones after manufacturing , so during GR after production how will i make all these entries like each,tonnes,length,breadth and height  on single SAP screen? what should be my base unit of measure in this case? Client also want the stock report of all these measurement factors.
    please guide me how to map this process?

    Hi Ravi,
    This is already addressed by SAP .This functionality is called Batch specific unit of materials .kindly go through the following blog which will give you step by step guide to configure the same. Material code will be 1 but each piece will be treated as Batch and each will have different weight.
    /people/raja.ramasamy/blog/2010/02/22/batch-specific-units-of-measure-step-by-step-configuration-for-steel-industry
    Regards
    Raja

  • Getting an error in CIF Inbound queue:"Only 0 decimal places are permitted for unit of measure PC"

    Hi,
    I am getting an error in CIF Inbound queue (function: CIF_ORDER_INBOUND_30A). The error text says "Only 0 decimal places are permitted for unit of measure PC".
    Can anyone point out the solution to resolve this error? It would be a big help for me as I am new to APO and so getting difficult to find a clue for it.
    Thanks.
    Regards
    Mansi

    Hi Mansi,
    Please check the cif queue you will get the order number from that order number you can find out material code. Then check the material master unit of measure in MM03 you have used some alternative unit of measure and system is unable to convert order to  alternative unit of measure because of decimal setting. If you go to CUNI and check the unit if measure PC it is not permitted for decimal places. If you need decimal than change the UoMof Material and use diff UoM or allow the decimal for PC which is not good practice.
    Regards,
    R.Brahmankar

Maybe you are looking for

  • How to increase the number of row displayed in the result set.

    Hi All, I have a seeded oracle page OA.jsp?page=/oracle/apps/pa/structure/webui/FPStructVersionPG from projects module. On the above page, when we click on the financial tab to see the tasks, it shows only 180 tasks out of 298. I dont find any link o

  • External portable drive for mac/pc?

    was going to get a western digital passport drive but after reading in several places that the powerbook doesn't have enough juice to drive it I'm looking for a plan b. I need to have it work on both platforms so firewire is out. Any suggestions for

  • Scorned by bad hard drive!

    My MacBook Pro is only 1.5 years old. I did not purchase the apple protection plan and I guess this is my mistake. Out of nowhere, the hard drive on the computer quit working. In the last two years I have convinced everyone in my immediate family to

  • Poor performance: portal report using inline views

    I have created a portal report that uses inline views that performs terribly. It has 6 inline views. When I cut out half the views, the performance doubles. When I run the same query in sql + on my portal database with all the views, I get the result

  • Siri talking when I type text and email

    The Genius Bar did a reset on my phone in an effort to correct an issue.  After the reset (which did not solve my initial issue), Siri started trying to help me type my text and emails by speaking the words I am typing.  How do I shut her up without