04.02.2013 Views

E A I U S E R M A N U A L - Favv

E A I U S E R M A N U A L - Favv

E A I U S E R M A N U A L - Favv

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

For “datetimes” this includes:<br />

No tag<br />

Null values<br />

<br />

BOV<br />

BE10014385-0101<br />

<br />

<br />

BOV<br />

BE10014385-0101<br />

0001-01-01T00:00:00<br />

0001-01-01T00:00:00<br />

<br />

<br />

For other XML types there is only the No Tag option<br />

19. Q: How can I see the field lengths<br />

A: Technically speaking, field length specifications are not standard part of XML.<br />

There have been proposed some standards but the general conclusion of any such<br />

debate is always that XML should not be specifying lengths.<br />

For informational purpose these are our standards<br />

Strings are by default 50 characters UNLESS:<br />

- They represent “User Codes” -> Length 5<br />

- They represent “Descriptions” -> Length 255<br />

- They represent “Comments” -> Length 800<br />

- They are explicitly constrained to another length for technical reasons. An<br />

example of this is street in the current interfaces which are constrained to 40 for<br />

printing reasons<br />

- Examples:<br />

o NAM VARCHAR2(50 CHAR)<br />

o AL1 VARCHAR2(50 CHAR)<br />

o AL2 VARCHAR2(50 CHAR)<br />

o STR VARCHAR2(40 CHAR)<br />

o ZIP VARCHAR2(50 CHAR)<br />

o CTY VARCHAR2(50 CHAR)<br />

o MCP VARCHAR2(50 CHAR)<br />

o EMA VARCHAR2(50 CHAR)<br />

o TPH VARCHAR2(50 CHAR)<br />

o TPH_ALT VARCHAR2(50 CHAR)<br />

o GSM VARCHAR2(50 CHAR)<br />

o FAX VARCHAR2(50 CHAR)<br />

o GNDR_CDE VARCHAR2(5 CHAR)<br />

(*) = Slaughtering Module only<br />

Sanitel EAI Manual – v1.28 EAIManual.doc 131

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!