BIZTALK EDIFACT decimal point issues

HI,
Am getting below error when i pass my EDIFACT file.
SegmentID: MEA
Position in TS: 337
Data Element ID: C17402
Position in Segment: 4
Position in Field: 2
Data Value: 11.557
37: Invalid character(s) found in data element
I have defined the properties for that in below image.
c17402 datatype is EDIFACT_N, does it allow decimals?or could you please tell me where am making wrong?

I already told you:
You would need to change the EFactDelimiter to:
0x3A, 0x2B, 0x2E, 0x3F, 0x20, 0x27
instead of 
0x3A, 0x2B, 0x2C, 0x3F, 0x20, 0x27
Morten la Cour

Similar Messages

  • Condition type decimal point issue in pricing

    Hi
    I have a import pricing Procedure as shown
    The condition types JEDB and JSED were calculated on 0.16 EUR,
    Like JEDB 2% of 0.16EUR= 0.0032
    and JSED 1% of 0.16EUR= 0.0016
    it is taking the first two digits of the value, ie 0.00 only
    Please confirm how to come with the corrected values,
    Thanks,

    Yes it is intended for TM but you can do the manual changes as recommended in the note and for technical coding, you can copy that logic.  Else, have a look at this note:-
    Note 38881 - Pricing with different decimal places
    G. Lakshmipathi

  • How to resolve the decimal point issue??

    hello friends,
    I had declared a variable of variable type P(16) decimals 6 for price. The price is calculated accurately and stored in the variable. The value that got stored is 5094390.000000. I declared one more variable of type ekpo-netpr and moved that value into this field. In the fieldcatalog i used cfieldname = 'waers'.....while displaying through ALV for waers 'IDR' (no decimals should be displayed ) it is displaying as 509.439.000 instead of 5094390.
    Could you tell me any one dd variable that can hold of type P(16) decimals 6 .
    pls help me to resolve this issue. All helpful answers would be highly rewarded.
    Thanks,
    Ramineni

    Hi Ramineni,
    Check this..
    WA_FCAT-TABNAME = 'I_OUTTAB'.
    WA_FCAT-FIELDNAME = 'AUFNR'.
    WA_FCAT-REF_TABNAME = 'AUFK'.
    WA_FCAT-HOTSPOT = 'X'.
    APPEND WA_FCAT TO I_FCAT.
    WA_FCAT-TABNAME = 'I_OUTTAB'.
    WA_FCAT-FIELDNAME = 'ACTL'.
    WA_FCAT-SELTEXT_M = 'Total Act Amount'(010).
    WA_FCAT-QFIELDNAME = 'TWAER'.
    WA_FCAT-QTABNAME = 'T_OUTTAB'.
    wa_fcat-decimals_o = '0'.
    APPEND WA_FCAT TO I_FCAT.
    CLEAR WA_FCAT.
    <b>Decimals in this will be restricted</b>
    Regards,
    Omkar.

  • Conversion issues with decimal points from v5.1.5 to XI

    Several reports which were converted from v5.1.5 full client to XI Webi have numeric differences. When comparing v5.1.5  to XI, the sums on the columns don't exactly match. The cell format on these numbers is set to eight decimal points. When we converted, I noticed the cell format changed from number 0.00000000 in 5.1.5 to custom 0.00000000 in XI. I don't know if this is the reason the sums don't match or if it's something else.

    Hello Ellen,
    as you refer to a Webi problem I recommend to post this query to the [BusinessObjects Web Intelligence|SAP BusinessObjects Web Intelligence; forum.
    This forum is dedicated to topics related to the creation and design of Web Intelligence documents using the Web Intelligence Report Panels. This includes areas such as universe connectivity, prompts, charting, formatting, filters, and formulas.
    It is monitored by qualified technicians and you will get a faster response there.
    Also, all Webi queries remain in one place and thus can be easily searched in one place.
    Best regards,
    Falk

  • Purchase price to have 4 digits after decimal point

    Hi Friends,
    Would you please help me out with this issue?
    The purchase price needs to have 4 digits after the decimal point, because the product/component would be packed and sold in other unit, which may give huge value difference.
    The price can be set for the product/component per 100, but is there any setting in SAP Reference IMG?
    Thanks for your help.
    Regards,
    JT

    Hi,
    In material Master (MM01) which unit you maintain for that material. Go to MM02 and keep Base Unit of Measure as storing unit as earlier and maintain Sales unit (unit of measure in which the material is sold) or Order Unit (Specifies the unit of measure in which the material is ordered) in the Purchase Order according to your requirement and Enter the factor for converting the alternative unit to the base unit. In your case product/component would be packed in a Different unit.
    OR
    In your case product/component would be packed in a Different unit.
    Maintain the (BOM) Bill of Material for the finished product you are selling and its component.Create Finished Product as material type as FERT and Components as material type as HALB or ROH.
    Now try your transaction with Finished Product only and sale.
    Hope the above  will help.
    Regards,
    Biju K

  • Mail adapter ignores decimal point

    Message going out from Mail adapter ignore decimal point. One of the attibutes in xml file has a value "1.0". When I check the message in SXI_MONITOR -> Call adapter -> Payloads -> MainDocument, attribute value is "1.0". But when file is received by receiver atribute value is "10". Can any one give some advice how to fix this issue?
    Thanks
    Ranji

    Hi,
    I hope , in general mail adapter may not ignore the decimal points , please check in mapping itself..
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/bf93409c663228e10000000a1550b0/content.htm
    Regards
    Chilla

  • Decimal points not displayed correctly

    Hi team,
    I am experiencing issues with displaying decimal points in the following fashion (selected element spinner and changing the number format in the appearance tab):
    Number Format: Percent
    Decimal Points: 0
    50%
    Number Format: Percent
    Decimal Points: 1
    50%
    Number Format: Percent
    Decimal Points: 2
    050%
    Number Format: Percent
    Decimal Points: 3
    0.050%
    Number Format: Percent
    Decimal Points: 4
    00.50%
    I was expecting something like this:
    Number Format: Percent
    Decimal Points: 0
    50%
    Number Format: Percent
    Decimal Points: 1
    50.0%
    Number Format: Percent
    Decimal Points: 2
    50.01%
    Number Format: Percent
    Decimal Points: 3
    50.012%
    Any views?
    Many thanks,
    Frank

    Amit/Frank,
    This is stange...
    Spinner is working differently in different systems...:) I tried it on 3 different systems...
    One system shows..
    Value is 50
    Number Format: Percent
    Decimal Points: 1
    5000.0%
    Number Format: Percent
    Decimal Points: 2
    5000.00%
    Second system...
    Value is 50
    Number Format: Percent
    Decimal Points: 1
    50%
    Number Format: Percent
    Decimal Points: 2
    050%
    and 3rd system..does not show up any change be it Decimal Points 1 or 2, it still shows 50
    -Anil

  • LSMW field with 5 decimal points

    Hi All,
    I need to pass a field in the LSMW with 5 decimal points.
    we cannot pass the data type as "PAC5". can any one suggest how this can be done in LSMW.
    Also, I am passing the currency key as USDN in the LSMW using Idoc method. But it is taking only as USD even though the length of the field is 5 chars. But I am able to acheive this if I manually post it as USDN.
    please suggest on the above 2 issues.
    Helpful answers will definitely be rewarded.
    Thanks in Advance,
    Asif Ali Khan

    hi khan,
    see the below link
    http://www.abapcode.sapbrainsonline.com/2008/03/write-output-formatting-options-abap.html
    http://www.abapcode.sapbrainsonline.com/2008/03/types-abap-keyword.html
    sapabap.iespana.es/manuales/pdf/lsmw.pdf
    abapprogramming.blogspot.com/2008/03/sap-abap-syntax-for-assign.html - 122k
    abapprogramming.blogspot.com/2008/03/sap-abap-syntax-for-assign.html - 122k
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90cef248-29e0-2910-11bb-df8dece7e22c
    thanks
    karthik

  • Sql loader & decimal point

    Hello,
    I need to import data with field containing floating point number. When I do this load on linux it goes ok. But when I try to load the same data from my windows there is problem with decimal point character. (My oracle server is 9i on linux).
    I trid to use after logon trigger to issue statement alter session set nls_numeric_characters (enclosed in execute immediate statement) but it don't helped me.
    Thanks for advice
    sasa

    ok.
    I have following values in file to import:
    45.5
    50.3
    60.2
    38.7
    ("." is decimal point)
    If I use sqlldr on linux it is imported correctly. If I try to to import data from windows machine I get error message ORA-01722: Invalid number. So somewhere on my windows machine is set another decimal separator and i would like to change it to ".". But i don't know where I can change it.
    Is it more understandable?

  • In a pages table change the decimal point to a comma

    I live in Italy and love it. However, there are issues. One that you might be able to help me with is changing the usual decimal point in a table to a comma. In Italy they use a comma for separating change from dollars instead of the usual decimal point.

    Scott Fox wrote:
    I live in Italy and love it. However, there are issues. One that you might be able to help me with is changing the usual decimal point in a table to a comma. In Italy they use a comma for separating change from dollars instead of the usual decimal point.
    I apologize but _*in many countries*_ the usual decimal separator is not the decimal point, it's the comma.
    It's time to understand that American habits aren't the universal rules or ways of life !
    I'm not saying that American habits are bad, just that they are local ones, not better than others.
    Yvan KOENIG (VALLAURIS, France) mercredi 30 septembre 2009 16:01:23

  • Regarding decimal points in QATR

    Hi ,
    I am having an issue regarding the decimal points descrepancy in QATR (Quality Assurance test report).
    The settings for decimal points for some of the inspection characteristics are not matching with the QATR report. Please help me in sorting out this issue.
    Regards
    vivek

    Hi ,
    I was just trying to change the decimal point values in the inspection characteristics for this material inspection plan & tried to run the report again to see the certificate.The is no change in the report.
    So please tell that whether is there is any connection here??
    Regards,
    Vivek

  • Change decimal points in SD Condition type from 2 to 3, for EU

    Hello,
    We have a slight problem with the amounts. We are using resource related billing in the project and to track some expenses, there are some condition types created. Since the currency is maintained as EU, the decimal places are maintained as 2 decimals in OY04 and we dont want to change that.
    We face an issue, when SAP Converts condition value from 3 to 2 decimals
    For example, when in Contract we have an Condition Value of 100.025, this is converted to 100.03 and tax is applied on this amount.
    When we create an invoice and subsequently a Credit Memo request, that will contain more than one item, and the sum of all items will have to sum up to 100.03, but this is never the case, as with the application of tax rate, the value comes to something like 100.02 or 100.04..
    With 3 decimal points, this amount adds upto correct value.
    So our ideal solution will be the have the Condition Values as 3 decimals and the Net value in 2 decimals.
    Is there something  that can be done for this?
    Hoping for a quick response.
    Regards
    Maddy

    SAP stores the 3 decimal value in XKOMV-kbetr and Xkomv-kwert is calculated based on this 3 decimal values...
    I had a similar scenario with currency conversion and rounding issue in sales Order and Invoice processing, in VOFM routines... so I used a Floating point  value and converted to character value and then used that 3 decimal value for calculation.

  • Labview Database Connection Toolkit and decimal point

    Hi,
    on my system I use "," (comma) as decimal point.
    In Labview Options I unflagged "Use localized decimal point", and numeric controls and indicators use "." (dot) as decimal point.
    The problem is that Labview Database Connection Toolkit keeps returning floating point numbers as strings with comma as decimal point.
    Has anyone experienced this issue?
    Is this related to Labview or MySQL ODBC Connector (that I'm using to connect to a mySQL DB)?
    Thanks in advance for any help,
    Marco

    You have two or three places to look. First there is the DCT. Second, there's a couple layers there that could cause problems (the mySQL drivers and ADO) and then there's even the posibility that the issue could be in the DBMS itself.
    I would start by burrowing down through all the DCT layers and find the spot where the results are actually being read back fromt he database. If the resutls are read as variants and converted to LV datatypes, the problem is on the LV side. If the values are being read as strings and converted, the problem coiuld be on the other side.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Problems with the system decimal point with german regional settings

    I have a Labview 6 app that needs deploying to Germany.
    My app sends strings over VISA RS232 and GPIB instruments with floating point numbers.
    When changing from English to German regional settings, in Windows XP, periods are now interpreted as commas and the app starts truncating my decimal numbers. So in the English Regional Setting when I send 1.234 I get 1.234 but in the German Regional Settings when I send 1.234 I get 1.000.
    I have turned off the "Use localized decimal point" in Tools - Options - Front Panel as well as set any function (Frac/Exp String to Number) that has a "Use System Decimal Point" connector to FALSE.
    Now here's my problem....
    This fixed the issue I was having as long as I am in the development environment, however, once I build the application I still get the truncated numbers. Example: I send 1.234 to an instrument and it sees 1.000.
    Again this works fine in the development enviroment, sending 1.234 reads 1.234 with German regional settings.
    Any help is appreciated.
    Adam

    You can use a simple function of the "Scan from string" function.
    Place "%.;" (Without the quotes) in the scanning string, and this will tell LV to use a decimal point for interpretation. If you place "%,;", this will tell it to use a comma.
    You can place this at the beginning of your format string, and it simply tells the parser how to work, it doesn't otherwise produce an output.
    Using simply "%;" sets the seperator to the system default (maybe the best idea after the code has been run as the changed decimal point character apparently remains changed otherwise). From the LV help
    The following codes control the decimal separator used for numeric output. These codes do not cause any input or output to occur. They change the decimal separator for all further inputs/outputs until the next %; is found.
    %,; comma decimal separator
    %.; period decimal separator
    %; system default separator
    Hope this helps
    Shane.
    Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

  • 2 Decimal points in inventory module

    Dear Expert,
    In SAP 2005, inventory module allowed for 6 decimal points somehow in SAP 2007, it does not allow for 6 decimal points only 2 decimal points are allowed.  When I try to zerolise my Inventory quantity, they still remain some quantity in the in stock field.
    Please advice.
    Regards,
    Saw Hua, Ng

    Hi,
    Refer this thread for what the decimal settings determines
    Difference between Decimal places for  Quatities and Units
    Even if the quantity is set to 6 decimal,the item master shows only 2 decimal places.
    Where as in the documents you can use upto 6 decimal places and same is stored in the OITM table.
    And also you can only increase the decimal places and once if it increased it cannot be decreased in 2007 version,refer this note:1147799 on the same.
    Hope this clarifies your issue !

Maybe you are looking for