Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

what is mean by N 1/35

Status
Not open for further replies.

rpolisetti

Programmer
Jul 27, 2006
12
AU
Hi All,

I am trying to find out what is mean by N 1/35. As per my knowledge, N 1/35 means number(integer & real) with min 1 digit and maximum of 35 digits.

My actual question is, how many digitis we can have after decimal point? could some one please let me know what is limit on number of decimal points.

Thanks in advance,
Raja
 
depends on the item. is this a quatity, percent, $ amt? What transaction or segment/element?
 
Thanks eyetry.

I am using it in MOA segment.... for the moneytoary amount. What would be the maximum numbher decimals points that i can specify .. when I use N 1/35. Please advice.

Thanks,
Raja
 
Ok, N 1/35 in an EDI/X12 element should mean 'numeric 1-35 bytes'.

I believe the 'Monetary Amount' (MOA02) element in the 'Medicare Outpatient Adjudication Info' (MOA) segment is defined as

Usage: Situational
Data Type: Numeric (including minus sign or decimal point)
Size: 1 - 18 bytes

Within those guide lines trading partners can define rules that better meet their situations. For example two TPs could agree that Monetary Amount elments must be 3 - 12 bytes. They could not create a compliant Monetary Amount element that's 1 - 35 bytes.

When dealing with dollar amounts typically up to 2 bytes are reserved for cents (ok to trim trailing zeros). There is no hard rule that I'm aware of though, so you could in theory define the number of allowed decimals with your TP.

eyetry

PS: I'm not an EDI expert but, assuming you are woring with an EDI/X12, I believe you can be confident with the above.
 
If this is defines as just an "N 1/35 " max Total Length is 35 digits and the decimal point must be sent in the data to show where in the data it is to reside.

If define as "N4 1/35" then Max length is 35 digits with and last 4 digits residing after the decimal point (trailing zeros will be needed to fill in if not a total of 4 sent).

Some vendor software will allow a decimal point to be sent in the last one and not fail complaince checking other will throw a waning and some will ever fail and send back a reject FA.
 
True and the trading partner may want an N4 format.

However, the element defined by Raja is 'Monetary Amount'. The EDI/X12 standards state Monetary Amount is Optional, Numeric, 1-18 bytes. For the most part for HIPAA EDI/X12 'Optional' really means 'Situational'. I'm assuming his transaction is HIPAA related because he referred to the MOA segment which is used in the 835 and most 837 transactions for 'Medicare Outpatient Adjudication Information'.

Assuming that's true he probably needs a numeric value with up to 2 decimal positions based on need. Samples below

100
100.1
100.01
-100
-100.1
-100.01

Typically the TP agreement or internal standards will define whether 100 should be 100 or 100.00 or 100.0000. No matter what the agreement is though the element will still be defined an 'N'

eyetry

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top