Section 3.5.1.2 Decimal Number of the 4010 manual: "A decimal data element contains an explicit decimal point and is used for numeric values that have a varying number of decimal positions. The representation for this date element type is R. The decimal point always appears in the character stream if the decimal point is at any place other than the right end. If the value is an integer (decimal punt at the right end) the decimal point should be omitted." further down it states: "Trailing zeros following the decimal point should be suppressed unless necessary to indicate precision." In example B it shows: Value is 12345 Decimal type symbol is R The data stream value is 12345 The length is 5 Clearly showing it is allowable to send without a decimal point. Because you should suppress the trailing zeros following the decimal point that would put the decimal at the "right end", thus making the decimal point itself omit able. So if you have a value of "15.00" in your system it seems reasonable to send "15". This is of course as far as the standards are concerned and not necessarily your trading partner. Tor
Tor Myers, Support Engineer Level 2 Edifecs, Inc. - "The DNA of B2B" __________________________ tel: 425.452-0644 www.edifecs.com <http://www.edifecs.com/> - Home of The Industry-Leading FREE Transaction Testing and Certification Service CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review; use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender immediately by replying to this e-mail and destroy all copies of the original message. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Joe McVerry Sent: Saturday, September 08, 2007 8:11 AM To: [email protected] Subject: [EDI-L] What's The Real Deal On Real Elements? A client, an ultra large retailer, is having issues with my translator converting a real element (type is "R") value. The element is defined such: <dataElement name="Unit Price" id="212" sequence="4" description="Price per unit of product, service, commodity, etc." type="R" required="X" minLength="1" maxLength="17" xmlTag="unitPrice"/> Incoming the value is "15.00." The translator outputs the value as "15" (sans decimal point and trailing zeros). Should the translator drop or keep trailing zeros and decimal point for outgoing messages? Is there a definitive X12 specification on how to treat reals? I can't find any rules on reals in any X12 related documentation or website. Thanks in advance, Joe McVerry americancoders.com [Non-text portions of this message have been removed] ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
