Price unit of measure

Dear SD Conultants,
the base unit of measure is M2 and the sales unit of measure is CAR so when I create a price cindition recored the system automatically determing the condition unit as CAR which is the sales unit of measure but what i want is that the sustem automatically determins the condition unit as M2 which is the base unit of measure.
Regards,
SD consultant

Hello,
1. Delete sales UoM from sales screens, in material master data.
2. Create a condition record with base UoM.
3. Use transaction VD51.
In fact: where is the problem? I document or in condition record?
M
Edited by: Marian Solomon on May 16, 2011 2:06 PM

Similar Messages

How to handle different Unit of measures in ALV reports? Quantity/Price

Anyone knows how to handle different unit of measures for quantity or price in hierarchy ALV reports?

hi,
use the below fields:
Link to measurement unit
qfieldname (measurement unit field name)
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
regards,
madhumitha

Price by multiple unit of measure

I have a requirement to price in multiple units of measure for the same material number. For example material # 12345
1 Box = $500
1 Ea = $1.50
1 Box = 500 ea
Customer orders 501 each of material 12345 on one line item of the sales order. Requirement is to price at $501.50 not $501.00
I have tried to use condition supplements without success. Does anyone have suggestions without using pricing requirements or forumals of how this requirement can be met?

hello, atul and friends.
i think interval pricing alone may not be enough, but definitely it could be part of the solution. (ms. gina, please confirm if i understood the requirement correctly)
let's say the customer orders 999 units, which will translate to 1 box and 499 loose units. the pricing will be something like:
$1 per unit times 999 units = $999.00
$0.10 per unit times 499 units loose = $49.90
total should be $ $1048.90
however, if order is 1000 units, pricing will be:
$500 time 2 boxes = $1000.00
so, the "surcharge" of $0.10 applies only to the loose units. but in the order, the quantity is entered either in boxes or units. the challenge is to create condition records that recognize this packing/grouping option. interval pricing must be supported by a feature that can recognize capacity.
regards!
Edited by: jonathan y on Jun 4, 2009 2:14 PM
Edited by: jonathan y on Jun 4, 2009 2:15 PM

Report for Units of measurement for Material

Hi
Is there any report to extract the alterante unit of measurements for materials in a plant.
Thanks

Hi,
Please use the below table,
Related to Materials:
MARA - Material Master: General data
MAKT - Material Master: Description
*MARM - Material Master: Unit of Measure*
MAPE - Material master: Export control file
MARC - Material master: Plant data
MARD - Material master: Storage location
MAST - Material link to BOM
MBEW - Material valuation
MLGN u2013 Material Master: WM Inventory
MLGT u2013 Material Master: WM Inventory type
MDIP - Material: MRP profiles (field contents)
MKOP - Consignment price segment (old versions of SAP)
EBEW - Valuation of sales order stock
QBEW - Valuation of project stock
MVER u2013 Material Master: Consumption <Plant>
DVER u2013 Material Master: Consumption <MRP Area>
MVKE u2013 Material Master: Sales <Sales Org, Distr Ch>
MLAN - Material Master: Tax indicator
MARC - Material Master: Plant data
MAPR u2013 Material Master: Forecast
MARD u2013 Material Master: Storage Location
MCH1 u2013 Material Master: X Plant Batches
MCHA u2013 Material Master: Batches
MCHB u2013 Material Master: Batch Stock
MDMA - MRP Area data
DBVM - MRP Planning File Entry: MRP Area
MOFF - Outstanding Material Master Records (Maintenance status)
MARCH - Material Master C Segment: History
MARDH - Material Master Storage Location Segment: History
MBEWH - Material Valuation: History
MCHBH - Batch Stocks: History
MKOLH - Special Stocks from Vendor: History
MSCAH - Sales Order Stock at Vendor: History
MSKAH - Sales Order Stock: History
MSKUH - Special Stocks at Customer: History
MSLBH - Special Stocks at Vendor: History
MSPRH - Project Stock: History
MSSAH - Total Sales Order Stocks: History
MSSQH - Total Project Stocks: History
Regards,
Mohd Ali.

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 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....

Unit of measure changed in BOM not reflected in Production order

We noticed the following problem in one of our production order.
1. We have a bom component having a unit of measure MT.
2. A planned order already exists for this header material.
3. We changed the unit of masure in the same BOM component to KG.
4. We processed the production order and did confirmations and did auto GR.( Value 20 times high)
5. The cost at GR is very high , although the material consumption is considering the changed unit of measure KG.
Any possible solution to this problem,
Thanks,
Manohar

All steps suggested including read PP master data , rerun MRP and generate a new planned order and then convert to a new production order, have been done but the effect at 101 remains same with high actual costs.
The production order is acocunt-assigned to a WBS.
In table QBEW , the standard price is updated as very high. We havs S as price control in header material master.
May be , some one has some idea about how the standard price in Table QBEW gets updated. What is the source for this standard price which gets updated on doing GR ( It comes to project stock and we see the standard price being very high and so the actual cost is very high)
Thanks,
Manohar

Unit of measure for calculation type C must be completed

Hi All
When releasing some contracts in SRM , we are getting the error message as above.
The error message doesn't specify any particular part and the contract has more than 3000 parts.
There are no conditions at header or item level.
There is no Target quantity also. Just a Target value for the contract and prices for individual items are maintained.
We are using extended classic scenario and the contract is manually created in SRM.
I have checked the OSS notes for this error, but they are mostly for contract creation in Bidding and not for a manually created SRM contract.
We checked the UOMs for all the contract parts with the UOMs ( Base and Purchasing) in ECC Material Master and they are OK.
In our scenario , MM changes in ECC are replicated to SRM in real time
Any pointers towards pin pointing the error will be rewarded!
Regards
Kedar

Hi,
We encountered this error message and resolved the problem by applying the following 3 SAP Notes:
a)     Note #1022928 - Unit of Measure for Calculation Type C Must Be Completed
        (Previously Mentioned)
b)     Note #1702484 - Unit of Measure for Calculation Type C Must Be Completed
c)     Note #1517648 - Default Conditions Added for Product Category Item Type
Although the contract required is similar to a "Limit" item, but had to be placed for bid, then the RFX PS Item Type was set to "Service" to receive the bid responses. After accepting the bid response, then we created a contract from the bid response. Since it was to be a "Limit" type contract, then we immediately removed the data from the following fields:
Remove the Quantity
Remove the Unit of Measure
Remove the Price
Remove the Price Condition
After removing the values from these fields, then we switched the PS Item Type from "Service" to "Product Category". We added the Guaranteed Minimum and account assignment data to encumber the funds. We were able to "Release" the contract successfully.
Bob Zinsmeister

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.

Unit of Measure Calculation in Query

Hi,
I have a few calculated keyfigures in my query for example:
whats happening:
KEY 1= Standard Price * Qty A = Output in (LBS) Qty unit of measure
What I want is:
KEY 1= Standard Price * Qty A = Output in $
How can i fix that on the query level so that my output is in $
Thanks
Edited by: DANIEL GREEN on Jun 12, 2008 2:33 AM

Hi
change the target currency and conversion type.
--- Pravin

Units of Measures found in the material master.

Hi,
What is significance of different Units of Measures found in the material master.
Ajay

Hi,
Order unit
Unit of measure in which a material is ordered. It is the default unit in purchasing functions.
Order price unit
Unit in which the vendor invoices you. The order price unit is defined in the purchase order or in the purchasing info record. If you have defined an order price unit in the PO, the goods receipt will be recorded in both the order unit and the order price unit.
Sales unit
Unit of measure in which a material is sold. It automatically appears as the default in a sales order and can be changed there.
Unit of issue
Unit of measure in which a material is issued from the warehouse/stores. You can use this unit of measure in conjunction with goods issues and physical inventory activities.
Any quantities that you specify in a unit of measure other than the base unit are automatically converted into the base unit by the system. To make this possible, you must enter the ratio for conversions between alternative units and the base unit (the conversion factor) in the material master record. You can enter this information when specifying the alternative unit of measure
Regards,
Santosh

Batch specific unit of measure - Purchase order history correction

I have maintained an alternate proportional unit for a material. This alternate unit is used as the order price unit in the purchase order. I have created a batch characteristic which is linked to this proportional unit of measure. I have also created a Master inspection characteristic which is linked to this batch characteristic.
I want to correct the purchase order history using quality management by transaction code MWBQ. However, when I perform transaction MWBQ, the inventory is reduced to zero and entire amount is posted to price difference account after correction. Hence, my inventory value becomes zero after MWBQ. I cannot maintain the proportional unit at standard price since this is a raw material. Need a solution on how to post correction in purchase order history without actualy making the inventory zero and with moving average price.

Thanks for caring!
As for transaction MMBE it all looks fine. So basic definitions must be OK up to that point.
I think the point is to set requirement for the amount of active ingredient.
Do the batch determination for this.
Do the goods issue in physcial quantity which is the base unit of measure.
I did try now with KG in the BOM. I still get double items in the process order. Now both in KG.
One line is correclty copied.
The incorrect line which is the same in both cases says 1 KG. which is the correct conversion from 0,01KAI.
Regards,
Tor

Purchase Requisition - Unit Of Measure

Hi,
We have a business requirement whereby the customer would like to see requisitions showing the purchase order unit of measure from the PIR, and not the base unit of measure from the material master.
SAP standard will not allow this nor is thee a plan to change this functionality in the near future.
The standard solution gives the users issues as they are having to validate the ordering quantity and price in the requisition, as the system will not show nor calculate the correct ordering price.
Does anyone know of a standard SAP user exit that could be manipulated to achieve this function?
Thanks in advance,
Cheers
Craig

Hi,
Do you know of any standard BADI's, user exits etc that can be utilised within the requisition process that can be accessed? I would like to use an exit to pull in the purchase order unit of measure from the PIR. (EINA-MEINS)
Any help is greatly appreciated,
Thanks in advance,
Cheers Craig

Unit of Measurment

Hello
Can any one help me to understand the meaning/significance of diffrenet Units of Measures found in the material master
regards
Narendra

Hi,
Alternative Units of Measure
In addition to the base unit of measure, used by the system in managing stocks and carrying out all its computations, other departments can use their own units of measure.
All units of measure other than the base unit are known as alternative units. The following are examples of alternative units of measure:
Order unit
Unit of measure in which a material is ordered. It is the default unit in purchasing functions.
Order price unit
Unit in which the vendor invoices you. The order price unit is defined in the purchase order or in the purchasing info record. If you have defined an order price unit in the PO, the goods receipt will be recorded in both the order unit and the order price unit.
Sales unit
Unit of measure in which a material is sold. It automatically appears as the default in a sales order and can be changed there.
Unit of issue
Unit of measure in which a material is issued from the warehouse/stores. You can use this unit of measure in conjunction with goods issues and physical inventory activities.
Any quantities that you specify in a unit of measure other than the base unit are automatically converted into the base unit by the system. To make this possible, you must enter the ratio for conversions between alternative units and the base unit (the conversion factor) in the material master record. You can enter this information when specifying the alternative unit of measure.
Variable Units of Measure
In the material master record, you can specify that the material can be procured in a unit of measure that differs from the order unit.
If the material can be ordered in more than one unit of measure, enter 1 in the Variable order unit field.
This setting is then adopted in the purchasing info record and allows you to enter an order unit that differs from the one in the purchasing info record when creating or maintaining a purchase order or source list.
If you do not allow a variable order unit in the material master record, you must use the order unit from the material master record.
If you wish to specify a different order unit for a purchase requisition, you must assign a source with a different order unit to the requisition.
Regards,
Chinna

Price unit of measure

Similar Messages

Maybe you are looking for