The structure of the XML documents is the very prescriptive part of the eBIZ/TC Upstream framework:
using the eBIZ/TC Upstream documents, the prescriptions must be completely respected about structure of the documents, names and coding,
optionality or mandatory use of elements, meaning of each element.
Otherwise the documents could be not validable with the XML Schema (that are the only way to check the
formal compliance of the documents) or could generate misunderstandings about the meaning of the message on the side of your partners.
The allowable customisations are about the use or not of a document or about the elements of the document that are declared 'optional'; they can
be used to simplify the documents (not all the elements are always necessary).
The (template of) eBIZ/TC Upstream documents of each release are on www.ebiz.enea.it or www.moda-ml.org and are represented by:
Document Knitting-Clothing Order Status | ||
---|---|---|
Document | Knitting-Clothing Order Status | |
Description | Knitting/Clothing Order status | |
Release date | 18/11/2011 | |
Scope |
The present guide has been issued to assist the companies of the Apparel (Knitting/Clothing) sector in the implementation of the standard XML document type "KNITTING/CLOTHING ORDER STATUS REPORT”, providing all the instruction required for its use in any context of e-commerce between Apparel Producers and their Subcontractors. All the rules required for the construction and validation of the document are embedded into the specific XML-Schema, which is detailed in section "Implementation guide".
| |
Generalities |
The message is issued by the Subcontractor to report to his Client (Apparel Producer) the status of his Commission Orders and the updated delivery dates, with the possibility of splitting an order line into several consignements. The message may concern all the articles ordered (Type = H "historic"), all the articles ordered and not yet delivered (type = C "complete") or just the articles in the “ready for shipment” status (type = S "for shipping"). For each article, the status report can be consolidated or partial for each Order line.
| |
Back compatibility | Unchanged | |
Document Code | G041 | |
Resources |
[Guide] [XML Schema] | |
Used in Processes |
|
|