Unit Of Measure of table PLPO

Hello,
I wiould like to ask, in the Unit Of Measure (UoM) of table PLPO we cannot see the description of this UoM (STD) was it stands for?
Thanks
Edited by: SAP_PHIL on Mar 23, 2009 10:01 AM

Description of UOM is stored in table T006A-MSEHT. Link PLPO with T006A

Similar Messages

How to retrieve the values from a table if they differ in Unit of Measure

How to retrieve the values from a table if they differ in Unit of Measure?

If no data is read
- Insure that you use internal code in SELECT statement, check via SE16 desactivating conversion exit on table T006A. ([ref|http://help.sap.com/saphelp_nw70/helpdata/en/2a/fa0122493111d182b70000e829fbfe/frameset.htm])
If no quanity in result internal table
- There is no adqntp field in the internal table, so no quantity is copied in itab ([ref|http://help.sap.com /abapdocu_70/en/ABAPINTO_CLAUSE.htm#&ABAP_ALTERNATIVE_1@1@]).
- - Remove the CORRESPONDING, so quantity will fill the first field adqntp1. ([ref|http://help.sap.com/abapdocu_70/en/ABENOPEN_SQL_WA.htm])
- - Then loop at the internal table and move the quantity when necessary to the 2 other fields.
* Fill the internal table
SELECT msehi adqntp
INTO TABLE internal table
FROM lipso2
WHERE vbeln = wrk_doc1
    AND msehi IN ('KL','K15','MT').
* If required move the read quantity in the appropriate column.
LOOP AT internal_table ASSIGNING <fs>.
CASE <fs>-msehi.
    WHEN 'K15'.
      <fs>-adqnt2 = <fs>-adqnt1.
      CLEAR <fs>-adqnt1.
    WHEN 'MT'.
      <fs>-adqnt3 = <fs>-adqnt1.
      CLEAR <fs>-adqnt1.
ENDCASE.
ENDLOOP.
- You could also create another table with only fields msehi and adqntp and then collect ([ref|http://help.sap.com/abapdocu_70/en/ABAPCOLLECT.htm]) the data to another table.
Regards,
Raymond

Unit of measure in condition table

Hi,
I'm creating a new condition type and it should be maintained in MEK1/2/3.
The new condition type is copied from RUC1.
According to the business requirement, I have set REST as the access sequence to the new condition type.
Requirement;
1. The condition record should be determined by vendor
2. The validity period will not in use (i.e. 1900/01/01-9999/12/31)
3. The unit of measure of the material to be purchased can be either PCE or PR
Issue;
It seems I can create a condition record per one vendor per only one UoM.
I have create a condition record for PCE, and set a scale 1PR = 1PCE for that condition record.
However, when I've tried to create a PO, I've got a quantity conversion error.
Does any one know how I can configure the 2 UoM for one vendor?
Restriction;
The material master is shared with other companies.
Therefore, we cannot maintain material master for this local requirement.
It has to be managed only by configuration.
Your help would be much appreciated.
Best Regards,
Mari

Test once by using your own custom condition table.
Create a condition table for the fieldCatlg Vendor, Material, Oder Unit etc (as per your requirement)
Then rest of all as per your settings. Then you can maintain the condition record as per order unit.
For more about create condition table refer to the blog Pricing procedure Steps and Details in SAP MM

" Unit of measure ****** is not defined; check your entry in table T006

I´m Trying to create a material from MDM to SAP and I´m monitoring the IDOC in WE05 and i get the next message:
" Unit of measure ****** is not defined; check your entry
Message no. M3490
Diagnosis
The key for the unit of measure you entered is not defined in table T006.
Procedure
Define the unit of measure through Customizing (Materials Management). "
In MDM we are sending as remote key the SAP Code and this code exists in the table T006, but in the information of failed IDOC say:
" Messages have been issued: number 0000000000184470
Message no. MK101
Diagnosis
During inbound processing for the IDoc, messages have arisen while checking material data. "
If someone has information about it ,pls I´ll appreciate your answer.
Regards Itzell T.

I´m Trying to create a material from MDM to SAP and I´m monitoring the IDOC in WE05 and i get the next message:
" Unit of measure ****** is not defined; check your entry
Message no. M3490
Diagnosis
The key for the unit of measure you entered is not defined in table T006.
Procedure
Define the unit of measure through Customizing (Materials Management). "
In MDM we are sending as remote key the SAP Code and this code exists in the table T006, but in the information of failed IDOC say:
" Messages have been issued: number 0000000000184470
Message no. MK101
Diagnosis
During inbound processing for the IDoc, messages have arisen while checking material data. "
If someone has information about it ,pls I´ll appreciate your answer.
Regards Itzell T.
Hi Itzell T,
      While creating the material the unit of measurement which is entered is not existing in the SAP System. The unit of measurement entered during creation of material is cross checked from enteries of check table T006.
      So, functional consultant should take care of this issue just let him know the message.
   He know what problem actually is and fix the problem as Ankur had said.

Formatting metrics in a pivot table differently based on a unit of measure

I have a generic metrics table with columns for METRIC NAME, UNIT OF MEASURE, ACTUAL VALUE, BUDGETED VALUE, and PRIOR YEAR VALUE. Each metric has a unit of measure associated to it, and I need to be able to format these metrics differently in the same field based on that unit of measure.
For example, I may have an actual value for a "cost per unit" that needs to be formatted in dollars to 3 decimal places (Unit of measure = USD3) while another metric may be a simple "number of items" that needs to be formatted as numberic to 0 decimal places (NUM0).
Has anyone ever formatted the same column in OBIEE with different data formats depending on the unit of measure needed? I know I can conditionally format the cell with colors or images, but I haven't figured out how to change the data format in a table or pivot table.

Hi,
I've read all the tips that are offered in this forum. I tried all the solutions provided here, but I can not get the grand total formatted conditionally, what I get is the following error nell'answer:
DXE compiler error. No table 'GTGT' found in DXE. Source name: DxeAPI. XML: None
Error details
Codici di errore: YV3KVTDM
Location: saw.hypercube.dxeApi, saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads
I'm use the version: OBIEE 11.1.1.6.2
Anyone have any ideas for me?!

How to model a conversion table for unit of measures?

Hi
I am looking for some input on how to model a many-to-many relationship.
The situation:
A fact table with columns:
Product
Unit of Measure
Date
Value
1 product is stored with 1 and only 1 unit of measure - e.g. Product = Oil, unit of measure = m3
The fact contains several products, each having its own unit of measure.
A dimension 'Unit of measures' with columns
Unit Of Measure
Unit Of Measure Name
Measure System
While reporting on the facts it should be possible to chose the unit of measure I want to see my facts in. E.g. I want to be able to show Oil-production in m3 or barrels or liters, etc.
My challenge:
How to model this requirement?
Right now I tend to go for a bridge table between the fact and the dimension.
But I was wondering:
a) are there other ways to model it
b) are there pitfalls in using Bridge tables?
c) Can I re-use the bridge table in combination with other facts as the model grows?
c.2) do I need to create an alias on the bridge table to re-use it?
Thanks for your help
regards
Andy

Hi Kart,
ok let's say my model looks like this (columns below the tables names, sample in brackets) - again ignoring a date dimension:
Dim_Product --- 1:n --- Fact ----- n:1 ----- Dim_UOM
Id (1,2) Prod_id Id (1,2,3)
Name (Oil, Gas) UOM_id Name (m3, Barrel, Litre)
Value
So the products are coming from the Dim_product, Unit_of measures coming from Dim_UOM.
Fact values would look like this
Prod_id UOM_id Value
1 1 10
1 2 84
1 3 10000
etc
If I need to report in a new measure, I would be forced to add a new record to the fact table
Prod_id UOM_id Value
1 1 10
1 2 84
1 3 10000
1 4 150
with 4 being the new measure id.
What I am looking for is a way to be more flexible when it comes to converting values to different measures.
Thanks
Regards
Andy

Table for alternative unit of measure

HI
I have created a material whose Basic UOM is Kg
I have maintained alternative unit of measure as TON and maintained the relationship 1 ton = 1000 Kg in material master -- additional data -
units of measure.
I want to capture the data for creation of report ....In which table this data is stored ?
Thanks
Sara

MARM

Standard report for unit of measures

Is there any standard report to see the Fert material unit of measures and its alternate unit of measures.

HI
there is no standard reprot for you requirment.
only UOM of material you canget from MM60.
but if you want alternate also got with table data MARM
1.use SE16-- enter the table name MARM
2.enter the material(field MATNR), and execute you get the report
-ashok

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.

Error of Unit of Measure in Invoice Parking

Hi ,
I am trying the invoice parking from a vendor portal by using BAPI_INCOMINGINVOICE_PARK ... we have created ZPTP_INVOICE_PARK function module for it ... now I have an issue that when I am paassing the following fields
in FM
LIFNR : 107411
Header table entries
Doc_date : 01.06.2011
Gr_date : 01.06.2011
Com : 1500
Curre : INR
Gross amt : 46676.22
Vendor Inv : keep blank
DO : keep blank
Vendor Inv Amnt : 46676.22
Input Table IT_INV_Table
EBELN     1540027236
EBELP     00020
MBLNR     5000781648
MJAH     2011
ZEIL     0001
MW     01
ITM_AMT     46676.22
WAERS     10
PO_QTY     50
MENGE : 50
MEINS : EA
Now,I am getting an error that "Unit of measure SET differs from unit of measure EA in order item 1540027326 00020" where my 00020 item no. is having UOM as EA and item no. 10 is having UOM as SET(and it is a deleted line item ).
My question is why it is saying unit diffres as even in FM I am giving the right UOM i.e. EA
While SET is a unit of first line item which is deleted.

Thanks for the response.
But the Unit is not fixed for D. there are number of transaction takes place and accordingly the units are. That is why I can not hard code it.
Plz advice.

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

Material Master Unit Of Measurement Changes Clarification

Hi
We have a material master with base unit of measurement as FT in basic data 1 view.
For this we have already some purchsing documents like PO's and PR's
But currently we dont have any open PO (or) PR and stock in system.
Still we could not change the base unit of measurement from FT to M..
Why?
Vijay

Hello All,
The error shows some of PR's and PO's numbers.
when i check the material in table MBEWH i can see some of the stocks for previous period like year 2009 and the period 06 and some of the previous year like 2008 and 2007 also having some stocks.
Now advise.
Vijay

Unit of measure

Hi
I want to procure same material from same vendor for different plants with different unit of measure.I tried maintaining different unit of measure in inforecord but it is not posible...
How to maintian differnet unit of measure with plant level for same material..
kindly need your inputs
-Prabu

hi,
soory for delay,
to create condition table and assigning to access sequence go to
spro-mm-purchasing-condition-create contion table(in this create table in 900 ser.and enter. then double click on field u wnt eg. pur.org plant etc and then generate the table)-then go to acc. seq. in that go to change and assign that con. table before the info record table i.e. if info record acc, no. is 20 give earlier no. which is available and save it .
then go to MEK1 t. code u will get the pop up in which u will get u r combination ok.

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 of table PLPO

Similar Messages

Maybe you are looking for