Annex

Semantic Notes 

These notes are not exhaustive, they are there only for clarification.

The following Semantic Notes concern the use of the BGM segment.

If an Order is to be cancelled, use of Message Function Code '1'
indicates that the transmitted message requests a complete
cancellation of a referenced Purchase Order. All data is to be
cancelled.

If an Order is to be changed, use of Message function code '4'
indicates that the transmitted message requests specified changes of
the referred Purchase Order.

If an Order is to be replaced, use of Message Function Code '5'
indicates that the transmitted message effects a complete replacement
of the referenced Purchase Order. All data are to be replaced in their
entirety by that in the current message.

If an Order response with changes is to be confirmed, use of Message
Function Code '6' indicates the confirmation by the buyer of
amendments proposed by the seller.

If an Order is to be duplicated, use of Message Function Code '7'
indicates that the transmitted message is an exact duplication of a
previous Purchase Order Change Request.

If an order is to be cancelled and to be re-issued, use of Message
Function Code '17' indicates that the transmitted message effects a
complete cancellation of the referenced Purchase Order, and that an
Purchase Order will be issued.

If only the heading section of an order is to be replaced, use of
Message Function Code '20' indicates that the transmitted message
effects changes in Heading Section data only. The complete Heading
Section data is transmitted to replace all data previously sent.
Detail and Summary Section data remain unchanged.

If only item detail and summary is to be replaced, use of Message
Function Code '21' indicates that the transmitted message effects
changes in Detail Section data, and may affect Summary data. Heading
Section data remains unchanged.

To indicate the last and final release of an order, use Message
Function Code '22'.

If an order is to be placed on hold, use of Message Function Code '23'
indicates that the processing against the referenced purchase order
has been suspended until further release information. An order placed
on hold is subsequently released by Message Function Code 'XX'.

If an Order is to be accepted without amendment, use of Message
Function Code '29' indicates that the buyer accepts the reference
message without amendments.

If an order is to be Changed in detail section, use of Message
Function Code '36' indicates that the transmitted message requests
specified changes in data in the Detail section. Changes are indicated
at the line item level.

LIN, Line Item, Group SG 25 The following Semantic Notes concern the
use of the LIN segment and D/E 1229 Action Request Code for segment
group 25.

If a line item is requested to be added, use of Action Request Code
'1' indicates that the line item is to be added to the Purchase Order
as a new or additional item. All required data must be transmitted.

If a line item is requested to be deleted, use of Action Request Code
'2' indicates that the line item is to be deleted from the Purchase
Order. The item is cancelled completely. No other data for the line
item need be transmitted.

If a line item is requested to be changed, use of Action Request Code
'3' indicates that the line item is to be changed. The data
transmitted in the LIN segment, and segments attached to the LIN,
replaces that previously held for the order item.

If a line item is not requested to be amended, use of Action Request
Code '11' indicates that the line item has not changed and no action
has been taken, and the item is transmitted for information purposes
and/or positioning.


Contents of ORDCHG