| Version: | D |
|---|---|
| Release: | 01C |
| Contr. Agency: | UN |
| Revision: | 3 |
| Date: | 2001-11-07 |
| SOURCE: | D2 Purchasing (SWG) |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Product exchange reconciliation message (PRODEX) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
This paper provides the definition of the United Nations Standard Product Exchange Message to be used in Electronic Data Interchange (EDI) between trading partners.
The Product Exchange Message is a communication between two trading partners with agreements for the loan of products to each other, to provide information about movements of products from and to various locations on particular dates.
The message gives additional information on the outstanding balances of each product between the trading partners.
No financial value is attached to the products and settlement is usually carried out between like products.
The Product exchange reconciliation message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
Each product exchange is covered by a bilateral contract and exchange accounts are balanced at agreed period ends.
Each contract will define the units in which the product (or group of products) should be measured. This is known as The Unit of Account.
A transaction forms the basis on which Product Exchanges are reconciled. A Transaction is defined as: a change of product title supported by the required data set for Delivery note/Ticket; or subsequently agreed Adjustments, Rebrands or Transfers.
There may be many transactions within an accounting period.
The product exchanged is identified by its product name, supply location, mode of transport, and date.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message:
All specified dates/times should be in the format 'ccyymmdd'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, months, etc.)
Where a choice of code or text is given only the code element should be used wherever possible.
Due to the high volume of data that will be usually transmitted in the Product Exchange Reconciliation message, it is highly recommended to use codes for products and locations. Conditional data that is not required in the message should not be included.
Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of a group.
A service segment starting and uniquely identifying a message. The message type code for the Product exchange reconciliation message is PRODEX.
Note: Product exchange reconciliation messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | PRODEX |
| 0052 | D | |
| 0054 | 01C | |
| 0051 | UN |
A segment to indicate the type and function of the Product Exchange Message and to transmit its unique identifying number.
A segment identifying the date and time that the statement was generated and the end period to which the transaction statement refers.
This identifies the primary unit of account pertaining to the contract.
A segment identifying the two partners involved in the transaction identified in the following message. In this message the segment is mandatory and must appear twice; once for each partner.
A segment group to give the relevant exchange references (contract number with -if necessary- its dates) relating to the whole message.
A segment identifying the product exchange contract reference.
A segment specifying general dates and, when relevant, times related to the reference.
A group of segments giving transaction details of the product groups exchanged and opening and closing balances for the accounting period (or as a result of the transactions).
A segment identifying the product group exchanged between the interchange partners.
A segment identifying the exchange balances for the contract during the period. It is used for opening balances and for closing balances.
A group of segments giving transaction details for each exchange transaction effected during the period.
A segment identifying the product exchanged between the interchange partners.
A segment identifying the transaction type (receipt, delivery etc) and (where required) duty status.
A segment identifying e.g. the oil terminal location involved in sending and receiving the product.
A segment identifying the date of supply.
A segment identifying measurement information for the product exchanged.
A segment identifying the quantity(ies) for the product exchanged.
A segment identifying the transport mode and appropriate movement identifier(s) for transaction.
A group of segments identifying some unique number for each transaction.
A segment identifying the consignment note, ticket reference or some unique number for each transaction.
A segment specifying general dates and, when relevant, times related to the reference.
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
| BGM | Beginning of message | |
| DTM | Date/time/period | |
|
GIS | General indicator |
| IMD | Item description | |
| LIN | Line item | |
| LOC | Place/location identification | |
| MEA | Measurements | |
| NAD | Name and address | |
| QTY | Quantity | |
| RFF | Reference | |
| TDT | Details of transport | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×2 | (M) |
| ├─MEA Measurements | ×1 | (M) |
| ├─NAD Name and address | ×2 | (M) |
| ├─Segment Group 1 | ×5 | (M) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| ├─Segment Group 2 | ×99 | (M) |
| │─├─IMD Item description | ×1 | (M) |
| │─├─QTY Quantity | ×10 | (C) |
| │─└─Segment Group 3 | ×9999 | (C) |
| │───├─LIN Line item | ×1 | (M) |
| │───├─GIS General indicator | ×2 | (C) |
| │───├─LOC Place/location identification | ×2 | (C) |
| │───├─DTM Date/time/period | ×1 | (C) |
| │───├─MEA Measurements | ×5 | (C) |
| │───├─QTY Quantity | ×5 | (C) |
| │───├─TDT Details of transport | ×5 | (C) |
| │───└─Segment Group 4 | ×5 | (C) |
| │─────├─RFF Reference | ×1 | (M) |
| │─────└─DTM Date/time/period | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |
