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 PCO request For Customs ESD Identifier | ||
---|---|---|
Document |
PCO request For Customs ESD Identifier (New) | |
Description | Request for an identifier for a ESD (Export Shipment Dossier) to a customs authority. | |
Release date | 05/11/2018 | |
Scope | This document is used to request a customs authority to send an identifier for an ESD (Export Shipment Dossier), which has already been internally identified by the sender, associated with a hash and placed in a position reachable by the receiver (when authorised) . | |
Credits | This document was produced by Piero De Sabbata, Arianna Brutti e Gessica Ciaccio for ENEA X-LAB with the contribution of Marco Mattiocco, Teresa Donnoli and Roberto Fulgido of ADM and the partners of the TRICK project. | |
Back compatibility | New | |
Document Code | TRC21 | |
Resources |
[Guide] [XML Schema] [JSON Schema] | |
Used in Processes |
|
|