EANCOM CHANGE REQUEST |
|
|||||
| A. ORIGINATOR | Originator Reference | |||||
| Number | : | |||||
| Name | : | Title | : | |||
| Company | : | Phone | : | |||
| Address | : | Fax | : | |||
| E-Mail address | : | |||||
| EAN location number | : | |||||
| Numbering Organisation | : | |||||
| B. OBJECT OF THE REQUEST | ||||||
| Message Tag (e.g. INVOIC): | EANCOM Version number: | |||||
| Segment Tag (e.g. NAD): | Segment
Number: (for existing segments) |
|||||
| Data Element Tag (e.g. 1153): | ||||||
| C. BUSINESS REASON FOR CHANGE | ||||||
| Explain in detail the problem and the business case that will be satisfied by the change. | ||||||
| D. PROPOSED CHANGE | ||||||
| Provide details of the proposed change, e.g. data element and segment of change. | ||||||
| Date: | Signature: | |||||
| Attach any additional information and supporting documentation, such as proposed layout of segments, proposed branching diagram of the message, impact on other EANCOM messages, etc. | ||||||
(c) Copyright EAN 1997