4 DECIMALS UOM

Hi All,
i want to use UOM with 4 decimals in SERVICE PR , PO but system is not accepting value more than 3 decimals.
message : input must be in the format ,,_,__~._ -..
please suggest.
thanks and regards
mahesh

Hello,
The work around is to use price per 10 PC in stead of price per PC.
Thanks,
Venu

Similar Messages

  • UOM with 4 Decimals in PR , PO.

    Hi All,
    I want to use UOM with 4 decimals in SERVICE PR , PO but system is not accepting value more than 3 decimals.
    we created UOM with 4 decimals.
    When i input the quantity with 4 decimals the following message appears: input must be in the format ,,_,_~. -..
    please suggest.
    Thanks and Regards
    Mahesh

    looks like you need some help to find your posted questions
    4 DECIMALS UOM
    and
    Re: Input must be in the format _,___,___,__~.___   -
    why do you post the question again and again, without providing new information?

  • Sales order item quantity not rounded and allowing decimals with UoM EA

    Hi gentlemens,
    I noticed something strange in our SAP ERP system.
    When we enter a material in a new sales order item, we are allowed to enter quantity 1,5 EA (1 and half Each).
    But when I check the config of the UoM EA in table T006, the number of decimals (field DECAN) is 0 and the decimal place for rounding (field ANDEC) is also 0.
    As far as I remember from other other SAP system, there should be an error message when entering the quantity 1,5 EA saying that decimals are not allowed for this unit of measure.
    Can someone help and tell me wich error message or which rounding program should normally be active when entering decimals with uom EA ?
    Thanks and regards,
    BDT

    Hi Mani,
    Thanks for the thread reference. I found the related OSS notes yesterday evening but this was for procurement.
    Here the question I have is more for a sales item.
    The strange case we are facing is:
    In a sales order, we can enter a particular material as a standalone item with a quantity of 1.5 EA without any problem.
    But if we create the same new item as a sub-item of a previous one (filling UEPOS), with qty 1,5 EA, then a rounding is triggered by the system based on the T006 config.
    I am wondering if this is a problem with the SAP standard program or if we did anything wrong in the past in our system?
    Best regards,
    BDT

  • UOM EA is taking data in decimals

    Dear Guru's,
    I have a FERT with UOM (EA) when i am doing production booking with mfbf material is moving to quality inspection,there while doing the UD system is allowing the UD to be happened in decimles places.
    Production qty is 2 EA
    System is allowing the UD in .5,1.5 EA.
    How to over come this issue.
    With Regards

    There is no solution in standard SAP. All quantity fields use the domain MENG13. It has 3 decimal places you can only hide the three decimal zeros using CUNI but if the user enters decimal places SAP won't prevent user from entering decimals.
    You can look at this note [931971|https://service.sap.com/sap/support/notes/931971]
    You need to implement user exit to prevent this EXIT_SAPMM07M_001 (include ZXMBCU02)

  • OLE: export quantity with decimals according to UoM

    Dear Guru,
    I encounter a problem when exporting data from Itab to Excel using OLE.
    In the itab, there are many Quantity fields (with UoM). When I export to Excel, I want the number of decimals of each quantity field must comply with UoM (for ex: PC with 0 decimal, Kgs with 3 decimals).
    I try to write the qty to text, it's ok but I also need the exporting qty is formatted as a number in Excel so user can do a sum.
    The solution for this problem seems complicated. I have to write qty to text, convert text to number...But for a large number of data, it is really slow.
    Is there anybody encounter the same problem? Please advice the solution.
    Thanks.

    > The solution for this problem seems complicated. I have to write qty to text, convert text to number...But for a large number of data, it is really slow.
    You make confusion about the real problem. Converting the quantity is not time consuming (or your program is really badly programmed ).
    What is time consuming is making many calls to OLE.
    To avoid that issue, SAP uses the Data Provider and the Desktop Office Integration (DOI). The whole data is sent to the frontend once (more or less), and sends only a few instructions to the frontend to process this data. I don't really know the exact process, but it's really, really  much faster.
    DOI can be programmed directly (there are SAP demo programs which show how it works, search forum), and there is an upper abstraction if you only need to paste data, set colors, that is indicated by Pedro.

  • Sales order schedule line quantities in decimals

    Gurus - Required your help to resolve the following scenario.
    I'm facing with the problem where schedule lines of a sales order allocated with decimal quantities even though materials with UOM as EA(Each). For example Material A of sales qty 13 has the schedule lines allocated as 11.960 and 2.040. The delivery has been created as per the schedule lines with qty 11.960 and 2.040 and it has been pick/packed and delivered to the customer. Now, while issuing goods for the delivery, received the error message as <b>"Serial number management only allows whole numbers".</b>
    Can anyone provide what are the possible ways to round the delivered qty and issue the goods, when the delivery is complete?

    Sree - Question 1 - Why would you deliver the product and then try goods issue it (In general ;)...anyway....I know, a lot of companies do that way....
    Question 2 - How much exactly did you ship out, surely must not have shipped products in decimals, since you've EACHES defined and not KGs....or LBs...
    I would suggest finding out the correct quantities shipped out and then cancelling this delivery document....you can then go on to modify sales order schedule line accordingly and then process it again..."WHAT ABOUT PICK PACK DETAILS"....before cancelling this delivery doc out..capture the packing details (HUs) and then apply them to the new delivery doc... if you are using external system for packing HUs.....process the IDOC (or file etc) using the new delivery doc number....
    Hope you got the direction )
    Thanks
    Nikhil

  • Unit of measure EA allows transactions in decimals ? Is EA indivisible?

    Unit of measure EA allows transactions in decimals ? Is EA indivisible?
    There are two scenarios. While creating a Bill of material - based on the configuration (see below) if you enter a quantity with decimals for a part number for which the Basic UOM is EA the system displays a message "Unit of measure EA does not support decimal places" THIS IS GOOD AS EXPECTED
    While transacting using MB1B, MB1C, MB1A, MFBF, MIGO or other transactions the system DOES NOT check and it is currently allowing us to post with decimals (1.25, 1.312) for part number for which the unit of measure is EA.
    Was not EA supposed to be an indivisible unit of measure? why is the warning message getting activated while creating or changing a BOM and why not while transacting stock?
    We have configured EA in the CUNI transaction as follows:
    Int. meas. unit      EA                                                  
    Commercial           EA              each                               
    Technical            EA              each                               
    Decimal places                                                          
    float. point exp.                                                                               
    ISO code             EA            
                                          Primary code                       
    Numerator            1                                                  
    Denominator          1                                                  
    Exponent             0                                                  
    Additive constant    0.000000       X Commercial meas.unit               
    Decimal pl. rounding                 Value-based commt                  
    Unit of meas.family

    you cannot restrict this behaviour with CUNI customizing, you can only check and stop this in a user exit.
    SAP inventory managment allows and stores 3 decimals for any unit of measure. You can only define how it will show the value to the users and how it will round the decimals if it calculates the conversion. But if you enter manually with decimals, then SAP will not round this.
    please read OSS Note 931971 - Decimal places in stocks and stock postings
    and
    Note 77525 - Quantity unit conversion in inventory management

  • Block decimals for EA

    How to Block decimal entry for UOM ea in Purchase order/ Delivery or Sales order.
    I have checked Material Master-Additional Data--UOM settings, but htere is no way to change 1.000 to 1
    I have also check transaction CUNI--Configuration of UOM, but for EA, decimal is blank i.e 0.
    I have also tried to create UOM group,but cannot block decimals.
    Please advice
    Thanks
    Sandeep

    Hi Huong and All,
    Is there any way to block the decimals for EA in MIGO? As informed by you, PO, SO and DO can be blocked by System Message but shall we implement the same for MIGO?
    I couldn't find the available user exit to be implemented as I've recived the SAP OSS which there is no option to avoid this behaviour from MM-IM* point of view.There is no solution withing standard methods (user exit or Badi's).As it is not an error, Unfortunately at this time it is not planned to change the current process.
    Our users insisted to block the decimals while issuing the materials with EA but so far as we concern that it may impact other transactions with movement as well.
    Hope to get this solution soonest to avoid high stock variances.
    Thanks and Regards,
    Ku

  • How to retrieve UoM-conversion Numerator and Denominator with 5 digits?

    Hi,
    in pricing i am using condition base formula to fill the condition amount and condition base value.
    Condition amount might be a price per UoM which is different from the order uom.
    konv-kbetr konv-waers / konv-kpein konv-kmein (e.g. 1.200 USD / 1 LB )
    Thus i also convert my base quantity to konv-kmein.
    Using UNIT_CONVERSION_SIMPLE i retrieve the used DENOMINATOR and NUMERATOR which i want to pass over to
    KONV-KUMNE and KONV-KUMZA.
    Problem is that KONV-KUMNE and KONV-KUMZA are DEC5_0, while the Conversion factors defined in customizing (T006-ZAEHL and T006-NENNR) have 10 decimals, and these are the values passed back by UNIT_CONVERSION_SIMPLE.
    Standard pricing somehow manages to derive 5 digits denominator and numerator even if the conversion is customized using larger numbers.
    Anyone an idea how to do that??
    Thanks for any help! Kind Regards,
    Guido
    Edited by: Guido76 on May 25, 2010 3:42 PM

    Hi,
    in pricing i am using condition base formula to fill the condition amount and condition base value.
    Condition amount might be a price per UoM which is different from the order uom.
    konv-kbetr konv-waers / konv-kpein konv-kmein (e.g. 1.200 USD / 1 LB )
    Thus i also convert my base quantity to konv-kmein.
    Using UNIT_CONVERSION_SIMPLE i retrieve the used DENOMINATOR and NUMERATOR which i want to pass over to
    KONV-KUMNE and KONV-KUMZA.
    Problem is that KONV-KUMNE and KONV-KUMZA are DEC5_0, while the Conversion factors defined in customizing (T006-ZAEHL and T006-NENNR) have 10 decimals, and these are the values passed back by UNIT_CONVERSION_SIMPLE.
    Standard pricing somehow manages to derive 5 digits denominator and numerator even if the conversion is customized using larger numbers.
    Anyone an idea how to do that??
    Thanks for any help! Kind Regards,
    Guido
    Edited by: Guido76 on May 25, 2010 3:42 PM

  • Uom urgent

    Hi experts,
    plz go through this issue
    I am in SAP 4.70
    Base UOM in MMR is MT
    Unit of Issue is KG
      When I try to issue 0.4 kg
    System populating the message "Quantity in stockkeeping unit is zero
    Message no. M7106
    Diagnosis
    The system has converted the quantity entered in the unit of entry into the quantity in the stockkeeping unit. The conversion results in a quantity that is smaller than 0.001. As only three decimal places are possible for a quantity, a quantity that is smaller than this (for example, 0.0003) is interpreted as 0.000.
    I would like to know is there any solution for this in further releases or any SAP notes exist for this.
    And now the UOM cannot be changed
    Plz throw some light on this.
    TR

    you cannot solve your problem to be satisfied, you violated the recommendations of SAP for setup of material units.
    SAP recommends to always use the smalles unit as base unit to avoid rounding issues.
    The quantity fields have 3 decimals only. CUNI settings will have no impact on this. This is just a technical settings for the field domain.
    1 MT = 1000 kg
    1 kg = 0,001 MT
    0,04 kg = 0,0004 MT
    but: SAP has only 3 decimals for quantity fields --> hence it needs to round --> in this case DOWN --> which is
    0,04 kg = 0,000 MT
    See OSS note 362932. It has all kind of information about conversion, ...
    The easies solution is to create a new material master with KG as base unit and MT as alternative unit .
    Then issue all the quantity of old material number with 201 to cost center
    then do a 202 to write on the quantity at the new material.
    Edited by: Jürgen L. on May 28, 2008 12:01 PM

  • UOM Convertion in GR Issue

    Hello Gurus,
    I have a material that have the next UOM:
    1 PC (BUM) = 3 BAG
    When I make a GR (mov. 261) for this material in 1 BAG (UOM at the BOM) the system makes the convertion to PC and discounts 0.333. See the next example:
    Initial Stock:         1        PC = 3 BAG
    GR ( - 1 BAG):    0.667 PC = 2.001 BAG
    So, at the end I have a little surplus that obviously doesn't exists.
    Is there any possibility for fix this? Can the system discounts 1/3 instead of 0.333?
    Thanks in advance.

    Hi
    I once had this issue in one of my projects. I'm afraid, as far as I know, this is the standard SAP, UoM can only accomodate 3 digits of decimals.
    Thus, when you define the Base UoM not with the smallest unit, you will face this kind of case where SAP will round the qty, resulting in an excess in stock (when physically it doesn't exist).
    My advice is, you should define the smallest unit as the base UoM, so this problem will not arise.
    Or, for material which already have this problem, you should do adjustment at least every month for this qty rounding problem.

  • Not to allow material movements with qty in decimals

    Hi All,
    A material X is having the Basic UoM as PC(piece) and alternate Uoms as kg & EA .
    conversion factor is : 1 PC=1EA  &  1PC=1 kg
    I want to restrict the system from allowing the Goods Receipt / Goods Issue in decimals. eg: 0.6 PC
    Also, in production order if possible.

    Hi
    In Tcode CUNI, ensure no decimal places are maintained for all the PC, KG and EA
    Regards,
    Raman

  • Remove Decimals in Smartform not working

    Hi,
    I use
    &struc-field(C)&
    to hide decimals in a SF.
    The type of this field is LGMNG.
    This code works for all instances, except when the UOM is type ROL (Role). I have put a break-point in the SF just before the value is output and they are identical.
    But the output would be, for example say five units:
    a) 5 SH (Correct)
    b) 5,000 ROL (incorrect)
    Anyone seen this before?
    Thanks.

    Nick,
    thanks for the reply. I tried both of these already:
    &struc-field(.0)&
    &struc-field(C.0)&
    And, for both, I am told at runtime that (.0) is not a correct "formatting option for the field struc-field".
    I'm going to put a code block in to convert to an integer and display that. It will work - I just thought that (C) or (.0) would work too?
    Thanks.

  • KP06 cannot enter number with decimals in fxd. consumption

    Hi!
    When using transaction
    KP06 Change Cost Element/Activity Input Planning with
    Planner Profile SAP102,
    layout 1-102 Std.layout Activity input ActInd/ActDep
    we cannot enter number with decimals in field Fxd. consumption
    Field name MEF
    Data element MEFXXX
    When we enter number with decimals like 12,45 it gets rounded in 13.
    I have tried to change number format of this collumn from Not defined
    to 0,00 but this is not helping. The rounding still takes place.
    My question is where can I assign the unit (of measurement) for posting of quantities.
    Regards,
    Marina

    The UOM is assosiated with Activity Type, and has a certain number of decimal points in the definition of UOM.  The other place to influence decimal points in the proper planning layout (column settings).

  • Troy Ounce UOM Conversion

    A troy ounce is equal to .0311034768 KGs.  SAP will only go out 13 decimals.  What should the numerator and denominator be (must be a whole number not greater then 5 places) to get the appropriate precision?
    Edited by: BR on Sep 10, 2009 2:22 AM

    Hello,
    Thank you for your response. 
    In configuration setting CUNI you define a UOM for MASS as troy ounce.  Since KG is SAP base you need to define the conversion between troy ounce and KG.  This can only be represented in whole numbers not exceeding 5 places represented by a numerator and demoninator in order to get to the precision without exceeding 13 places.  I am looking for what the numerator and denominator should be.
    Cheers,
    B

Maybe you are looking for