- This topic has 3 replies, 1 voice, and was last updated 7 years, 8 months ago by
.
-
Posts
-
-
I think the data type recognition is misconceived. If I have diagnosed this correctly, Microsoft has implemented the validation of Alpha Numeric (AN) fields as ONLY letters and numbers. The reality is we expect to be able to pass any text in the character set. For example, we are guaranteed to sometimes have a colon in the part number.
So, out of the box, the product will not let you send the segment PO1*1*****VP*12345:67890~ because of the “:” in the part number
It will also not let an AN field start with a space.
Do I have to modify all of the provided EDI schemas to remove the type definition? Or is it possible to modify the validation to be more sane and in line with what is traditionally allowed in an EDI translator?
-weak architect
-
Here is the character standard definition from an X12 guide:
Matrix A4. Data Element Types
SYMBOL TYPE
Nn – Numeric
R – Decimal
ID – Identifier
AN – String
DT – Date
TM – Time
B – BinaryA.1.3.1.4 String
A string data element is a sequence of any characters from the basic or extended
character sets. The significant characters shall be left justified. Leading spaces,
when they occur, are presumed to be significant characters. Trailing spaces
should be suppressed unless they are necessary to satisfy a minimum length.
The representation for this data element type is “AN.”A.1.2.2 Basic Character Set
The section that follows is designed to have representation in the common character
code schemes of EBCDIC, ASCII, and CCITT International Alphabet 5. The
ASC X12 standards are graphic-character-oriented; therefore, common character
encoding schemes other than those specified herein may be used as long as a
common mapping is available. Because the graphic characters have an implied
mapping across character code schemes, those bit patterns are not provided
here.
The basic character set of this standard, shown in figure A2, Basic Character Set,
includes those selected from the uppercase letters, digits, space, and special
characters as specified below.
A…Z 0…9 ! “ & ’ ( ) * +
’ . / : ; ? = “ ” (space)(note the colon in the basic character set)
-
One more followup – this was not detected as an issue in BT2006 or BT2004 because the Covast schemas defined the AN properly, as a string.
I can see how the acronym “AN” might have been misleading to Microsoft, but I can’t imagine how this error went to gold bits. Is anyone really using R2 in production? Because it seems like a flaw this big would have revealed itself by now and been corrected if anyone were really using R2 for production EDI.
Also, why are there no 4060 EDI schemas? They stop at 4050. Is microsoft going to step up to bat wi th the schemas? Seems like they need a service pack release for R2 before this thing is ready for prime time.
– weak architect
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.