Unit of Measure Tables

Hi,
   Can anyone tell me.
   1.  What tables store UoM in BW?
   2.  How I can maintain data in those tables.
   Thanks.
Dave

1) Go to RSA1 in BW.
2) Sleect the Source System tab.
3) Right click and select TRansfer Global Settings.
4) Select UOM and check Simulation.That gives the list of all the tables in Source System.
5) Select UOM and then select Update.This will bring in all the updated data into BW.
In order to manage this data,try to have automated as process
Hope it helps..

Similar Messages

  • Oracle and EPSG and Units Of Measure tabel.

    I believe there is a wrong value in the Oracle 11g Enterprise database on Windows 64 bit.
    We installed this a couple of months ago and found out that the Units Of Measure table is different from a Oracle 10g.
    Here is what I think is wrong.
    Oracle 10g Express Edition
    9101 radian                    Radian          angle      9101 1                   1         ISO 1000:1992   EPSG FALSE
    9102 degree                    Decimal Degree  angle      9101 3.14159265358979     180                       EPSG FALSE
    9103 arc-minute                                angle      9101 3.14159265358979     10800                     EPSG FALSE
    9104 arc-second                                angle      9101 3.14159265358979     648000                    EPSG FALSE
    9105 grad                                      angle      9101 3.14159265358979     200                      EPSG FALSE
    9106 gon                                       angle      9101 3.14159265358979     200                       EPSG FALSE
    9107 degree minute second                      angle      9102                                 EPSG           EPSG FALSE
    9108 degree minute second hemisphere           angle      9102                                 EPSG           EPSG FALSE
    9109 microradian                               angle      9101 1    1000000                   ISO 1000.      EPSG FALSE
    9110 sexagesimal DMS                           angle      9102                                EPSG           EPSG FALSE Oracle 11g Enterprise
    9101 radian                    Radian          angle      9101 1                   1         ISO 1000:1992   EPSG FALSE
    9102 degree                    Decimal Degree  angle      9101 3,14159265358979     180                       EPSG FALSE
    9103 arc-minute                                angle      9101 3,14159265358979     10800                     EPSG FALSE
    9104 arc-second                                angle      9101 3,14159265358979     648000                    EPSG FALSE
    9105 grad                                      angle      9101 3,14159265358979     200                       EPSG FALSE
    9106 gon                                       angle      9101 3,14159265358979     200                       EPSG FALSE
    9107 degree minute             second          angle      9101                                 EPSG           EPSG FALSE
    9108 degree minute second      hemisphere      angle      9101                                 EPSG           EPSG FALSE
    9109 microradian                               angle      9101 1    1000000                   ISO 1000.      EPSG FALSE
    9110 sexagesimal DMS                           angle      9101                                EPSG           EPSG FALSE It is all about the conversion from 9110 to 9101.
    11g tells me do nothing.
    While 10g tells me to go via 9102, which in the end does pi/180.0.
    I've checked EPSG v6.17 (Access database) which is similar as 10g.
    Is it a know bug in Oracle 11g (why change it in the first place? it was correct).

    I filed this as a bug (9534127), and it's fixed.
    The following is the workaround (as mentioned in the bug description):
    begin
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9107; -- degree minute second, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9108; -- degree minute second hemisphere, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9110; -- sexagesimal DMS, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9111; -- sexagesimal DM, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9203; -- coefficient, based on 9201
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9115; -- degree minute, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9116; -- degree hemisphere, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9117; -- hemisphere degree, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9118; -- degree minute hemisphere, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9119; -- hemisphere degree minute, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9120; -- hemisphere degree minute second, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
    uom_id = 9121; -- sexagesimal DMS.s, based on 9102
    end;
    begin
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9107; -- degree minute second,
    based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9108; -- degree minute second
    hemisphere, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9110; -- sexagesimal DMS, based on
    9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9111; -- sexagesimal DM, based on
    9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9115; -- degree minute, based on
    9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9116; -- degree hemisphere, based
    on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9117; -- hemisphere degree, based
    on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9118; -- degree minute hemisphere,
    based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9119; -- hemisphere degree minute,
    based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9120; -- hemisphere degree minute
    second, based on 9102
      update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
    = 180, target_uom_id = 9101 where uom_id = 9121; -- sexagesimal DMS.s, based
    on 9102
    end;
    begin
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10031; -- Meter, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10032; -- Meter, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10033; -- Kilometer, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10034; -- Kilometer, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10035; -- Centimeter, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10036; -- Centimeter, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10037; -- Millimeter, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10038; -- Millimeter, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 1609.344, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10039; -- Mile, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 1852, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10040; -- Nautical Mile, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .3048006096012, factor_c =
    1, target_uom_id = 9001 where uom_id = 10041; -- U.S. Foot, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .3048, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10042; -- Foot (International), based on
    10032
      update mdsys.sdo_units_of_measure set factor_b = .0254, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10043; -- Inch, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = .9144, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10044; -- Yard, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 20.1168, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10045; -- Chain, based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 5.0292, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10046; -- Rod, based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .20116619497596571965479068149417, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10047; -- Link, based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .30481225298450596901193802387605, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10048; -- Modified American Foot, based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .30479726511509957523453133559723, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10049; -- Clarke's Foot, based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .30479951799004225054718498468167, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10050; -- Indian Foot, based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .20116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10051; -- Link (Benoit), based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .20116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10052; -- Link (Sears), based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    20.116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10053; -- Chain (Benoit), based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    20.116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10054; -- Chain (Sears), based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .914398553970126751641554954045, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10055; -- Yard (Indian), based on 10032
      update mdsys.sdo_units_of_measure set factor_b =
    .91439841461602873872937279101345, factor_c = 1, target_uom_id = 9001 where
    uom_id = 10056; -- Yard (Sears), based on 10032
      update mdsys.sdo_units_of_measure set factor_b = 1.8288, factor_c = 1,
    target_uom_id = 9001 where uom_id = 10057; -- Fathom, based on 10032
    end;
    begin
      update mdsys.sdo_units_of_measure set factor_b =
    .017453292519943295769236907684886, factor_c = 1, target_uom_id = 9101 where
    uom_id = 10001; -- Decimal Degree, based on 10002
      update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
    target_uom_id = 9101 where uom_id = 10002; -- Radian, based on 10002
      update mdsys.sdo_units_of_measure set factor_b =
    .0000048481368110953599358991410235795, factor_c = 1, target_uom_id = 9101
    where uom_id = 10003; -- Decimal Second, based on 10002
      update mdsys.sdo_units_of_measure set factor_b =
    .00029088820866572159615394846141477, factor_c = 1, target_uom_id = 9101
    where uom_id = 10004; -- Decimal Minute, based on 10002
      update mdsys.sdo_units_of_measure set factor_b =
    .015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
    uom_id = 10005; -- Gon, based on 10002
      update mdsys.sdo_units_of_measure set factor_b =
    .015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
    uom_id = 10006; -- Grad, based on 10002
    end;
    /

  • MB51 Material Document List Unit of Measure

    Can/How is this list displayed with the unit of measure converted to one unit?
    Example Material movements for liquid with units in gallons and pounds.
    Want to list all in pounds.
    Conversion is entered in material unit of measure tables.

    you can see this in MMBE but not MB51 because this is the material document list and which will shows the Gr unit ( you can display the base unit but not conversion)
    convesion can only be displayed in MMBE

  • 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

  • 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

  • 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

Maybe you are looking for

  • Backup to external drive already used by Windows

    Total Mac newbie who wants to back up a MacBook Pro. I'd like to use one of the external drives I already own. The trouble is, they've been used for Windows storage already and so have that file system on them. They also have files and/or system back

  • Customized AP aging report

    we are checking the customized ABAP program, if we set today as open item key date, the program retrieved data and show the total open item for a company correctly and tie to vendor line item report, if we choose previous date(for example 2010, 12.30

  • Preview pdf files in Safari before potentially save them

    In fact I have 2 questions: when I do a web search if I click on a link to a pdf file, 2 things can randomly happen :      1 The pdf opens in a safari window and I can directly read it (that's what I want)      2  The pdf file is directly downloaded

  • The customers and orders form modules

    Please,i am new to oracle forms.I have been reading a book on forms ,but the book uses two form modules created by Oracle for demo purposes, the Customer and Orders form modules.I need to access and open these form modules from my form builder.I have

  • How do I backup my Profiles (passwords, bookmarks, security, etc.)?

    I followed the steps in the troubleshooting file and found the profile files, but am not sure how to back up that folder because although the files and other folders were there, I have no idea where the main folder is on my computer. I plan on restor