Code List 2: Transaction Code

Used in data element TCDE. Appears in all file header messages, in segments TYP.

Complete transmissions of the master files shown below (eg Product and Price Information Files) contain the full details of the database file, with type of change (TYPC) given as REPORT. Update transmissions will contain only parts of the master file, where details have changed since the last transmission. The type of change will be ADD, AMEND or DELETE.

Code	Meaning
PROHDR: First message of the Product Information File, File Format 1
`0100`	Complete transmission of Product Information File with products chained together
`0101`	Update transmission of Product Information File with products chained together
`0102`	Complete transmission of Product Information File with products linked together in a hierarchy
`0103`	Update transmission of Product Information File with products linked together in a hierarchy
PRIHDR: First message of the Price Information File, File Format 2
`0150`	Complete transmission of Price Information File from supplier to customer
`0151`	Update transmission of Price Information File from supplier to customer
`0152`	Complete transmission of Price Information File sent from customer to supplier
`0153`	Update transmission of Price Information File sent from customer to supplier
CUSHDR: First message of the Customer Information File, File Format 3
`0200`	Complete transmission of Customer Information File
`0201`	Update transmission of Customer Information File
LOCHDR: First message of the Location Information File, File Format 24
`0205`	Complete transmission of Location Information File
`0206`	Update transmission of Location Information File
RDBHDR: First message of the Retailer Standing Database File, File Format 109
`0210`	Complete transmission of Retailer Standing Database File
`0211`	Update transmission of Retailer Standing Database File (Was previously issued as code 0206 in error)
RDAHDR: First message of the Retailer Database Report File, File Format 110
`0215`	Complete transmission of Retailer Database Report
`0216`	Update transmission of Retailer Database Report ORDHDR & CORHDR: First messages of the Order File (File Format 4) and the Complex Order File (File Format 17), respectively. Also used in the Book Trade Order (File Format 103) in message BTOHDR and the Home shopping Order (File Format 105) in message HSOHDR.
`0350`	Proposed Orders - planned orders which will subsequently be confirmed. Usually sent to help a supplier plan production.
`0355`	Order for goods on approval/inspection - order for goods which may be returned after a period of inspection without being invoiced
`0360`	Exceptions to Proposed Orders - changes to a previously sent proposed order, which could be made either by the customer or the supplier
`0365`	Planning Orders - follow Proposed Orders and will subsequently be confirmed by the customer. Used to show all lines with details of quantities required and delivery locations. Intended to give a firm basis for the supplier to plan production and supplies.
`0400`	Cancelled Orders - used to cancel outstanding orders. These may originate either from the customer, when their requirements have changed, or the supplier if they cannot meet the order
`0405`	Confirmation of Cancelled Orders - confirms that outstanding orders have been cancelled within the sender's system
`0410`	Export Order - order placed on UK supplier for delivery overseas
`0420`	Standing Order - an order for regular supplies, valid over a long term
`0430`	New Orders - new order for goods and/or services
`0435`	Order for retained approval goods - retrospective order to cover goods already received on approval/inspection when these are being retained
`0440`	Order Amendment - contains changes to an outstanding order, such as quantities, prices and delivery dates. To minimise transmission costs, only send the details for the products which have been amended. Use transaction codes 0475 for re-scheduled orders or transaction code 0485 for additional lines. Note that order amendments can rarely be processed automatically.
`0445`	Order Chaser - used to chase delivery of an outstanding order
`0450`	Copy Orders - a copy of an order previously sent by EDI or other media.
`0460`	Confirmation of Order by Ordering Company - used for example when an order is placed by telephone or fax
`0470`	Mixed Order Types - the file contains a mixture of different types of order. Each order should be processed according to the Order Code given in ORD ORCD.
`0475`	Re-Scheduled Orders - used to change the delivery date of an order or order line. Only the lines which have been re-scheduled need be sent
`0480`	Call-Off Orders - request for delivery against a contract, blanket or standing order
`0485`	Addition to Existing Orders, Existing Requirements Unchanged - additional lines to be added to an outstanding order. Only the new lines need be sent
`0490`	Order Commitment - a contract to supply, not an instruction to deliver
HOTHDR: First message of the Hot Card File, File Format 27
`0500`	Complete transmission of Hot Card File
`0501`	Update transmission of Hot Card File
DELHDR: First message of the Delivery Notification File, File Format 6
`0600`	Delivery - a notification of delivery against an order, containing details of all the lines on the order. Normally produced by the supplier once goods have been picked for that order
`0610`	Consignment Note - sent by the supplier to the carrier to control the movement of a consignment through the distribution network to the customer
`0620`	Instruction to Deliver - a request for a delivery to be made
`0630`	Planned Delivery - used to report the status of a future delivery
`0640`	Delivery Adjustment - a notification of changes to a delivery, used when amendments are made or requested after a proposed delivery or request to deliver has been sent
`0650`	Balance - used to notify details of a part delivery when balances are accepted. Only includes those lines which are being delivered, not all the lines on the order, some of which may already have been received.
`0660`	Proposed Delivery - advance notice of an impending delivery
`0695`	Warehouse Receipt - notification that goods have been received at a warehouse Many goods are distributed on pallets, which may come from a different supplier to the goods, and which need to be controlled. Normally empty pallets are exchanged for full pallets to ensure the continued supply of goods.
`6001`	Pallet Exchange Note - notification that pallets have been, or are to be exchanged. These may be either full or empty pallets. Used when different types of pallet movements are being recorded (ie mixed file type).
`6002`	Pallet Control Voucher - control document issued when goods have been delivered on pallets and no empty pallets were available for exchange.
`6003`	Pallet Issue Note - notification that fresh pallets have been, or are to be issued. May also be used when goods on pallets have been recalled.
`6004`	Pallet Return Note - notification that pallets have been, or are to be returned
`6005`	Pallet Transfer Note - record of, or request for transfer of pallets
`6006`	Pallet Query Note - request for information on the status of pallet movements. Used when no empty pallets or control vouchers were received.
`6007`	Pallet Return Advice Note - notification that returns have been made
`6008`	Pallet Ex Factory Movement - record of pallet transfers out of a factory. Pallets may be empty or full.
`6009`	Pallet Collection Request - request for pallets to be collected/uplifted
`6010`	Load Collection Request - request for goods to be collected/uplifted
DLCHDR: First message of the Delivery Confirmation File, File Format 7
`0670`	Confirmation of Delivery - confirms the goods and quantities which have been delivered at a location
`0680`	Confirmation of Despatch - confirms the goods and quantities which have been despatched to a location
`0690`	Confirmation of Delivery Status Report - confirms the status of a delivery in preparation or transit
`6000`	Equipment Movement Confirmation - confirms the transfer of an item of equipment
INVFIL: First message of the Invoice File, File Format 8
`0700`	Invoices Only - commercial document (sales invoice) issued by a supplier to a customer listing the goods or services supplied and stating the sum of money due. For ease of reconciliation it is recommended that one invoice relates to one order and/or one delivery. Contains tax details where applicable.
`0701`	Self Billed Invoices - commercial invoice raised by the customer based on the order placed, delivery received and the contract of supply
`0702`	Retrospective Self-Billed Invoice - commercial invoice raised by the customer retrospectively
`0705`	Factored Invoice - commercial invoice sent by a supplier to a factor who will be receiving the payment from the customer
`0707`	Assigned Debt Invoice. Used by sellers to send an invoice file via EDI to the buyers advising them that the debt has been assigned to the factoring company
`0709`	Copy Invoice - not for VAT purposes. Raised when copies of an invoice document are sent from one party to another by EDI for information purposes only. The original invoice may have been sent by EDI or on paper.
`0750`	Provisional invoice, not valid for tax purposes. A periodic consolidated tax invoice must follow (either EDI or paper document). (Was originally notified as 0711 in error)
CLAHDR: First message of the Claims File, File Format 100
`0710`	Credit Claims (News trade) - claim for credit against unsold copies of a newspaper or magazine
`0711`	Sales Report - not final claim for credit. Report of sales of newspapers and magazines
UTLHDR: First message of the Utility Bill File, File Format 26
`0715`	Utility Bill - commercial invoice for metered services. Contains tax details where applicable.
`0716`	Copy Bill - not for VAT purposes. Copy of a utility bill previously sent by EDI or other means. For information purposes only.
`0717`	Utility Credit Note - credit notes only
CREHDR: First message of the Credit Note File, File Format 9
`0720`	Debit Notes Only - notification of a sum or sums owing, raised by the debtor (customer). Trading partners should agree whether this will contain VAT details, or whether the supplier will subsequently raise a Credit Note as the VAT document.
`0740`	Credit Notes Only - notification of a sum or sums to be credited. Usually sent by a supplier to a customer
`0741`	Self Billed Credit Notes - a credit note raised by the customer based on information already known
`0742`	Retrospective Self-Billed Credit Note - credit note raised by the customer retrospectively
`0749`	Copy Credit Note - not for VAT purposes. Copy of a credit note sent by EDI or other means for information only
EFTHDR: First message of the Electronic Funds Transaction File, File Format 28
`0810`	Electronic Funds Transaction
SRMHDR: First message of the Statement/Remittance File, File Format 10
`0820`	Statement Details Only - list of credits and debits with the outstanding balance, sent either as a report or to request payment from the customer by the supplier
`0830`	Remittance Details Only - details of the items against which a payment is being made. Sent by the payer to the payee.
UPLHDR: First message of the Uplift Instruction File, File Format 11
`0900`	Uplift Notification - notification of a an uplift (collection) of goods which is being, or has been made
`0910`	Planned Uplift - advance notification of an uplift (collection) of goods which is to be made
UNCHDR: First message of the Uplift Confirmation File, File Format 12
`0920`	Uplift Confirmation - confirmation of the items and quantities which are being, or have been, uplifted
`0930`	Confirmation of Uplift Status Report - report of the status of an uplift (collection) which is being, or is due to be, made
PICHDR: First message of the Picking List File, File Format 5
`1000`	Picking Instructions Only - instructions on what to pick for an order or delivery
`1010`	Picking Instructions Amendments - change to a picking instruction
AVLHDR: First message of the Availability Report, File Format 15
`2000`	Availability Report Only - report of actual or planned stock availability
SNPHDR: First message of the Stock Snapshot File, File Format 13
`2100`	Stock Snapshot Only - report of current stock holdings, usually sent by the stockholder to a supplier
SADHDR: First message of the Stock Adjustment File, File Format 14
`2200`	Stock Adjustment Only - notification of adjustments to stock holdings, usually sent by a third party stockholder (eg a carrier) to the owner of the stock
PPRHDR: First message of the Product Planning Report File, File Format 19
`2300`	Product Planning Report - planning report on products held at different locations
LPRHDR: First message of the Location Planning Report File, File Format 25
`2305`	Location Planning Report - report for locations holding various products
ACKHDR: First message of the Acknowledgement of Order File, File Format 18
`3100`	** Acknowledgement that an Order has been received, with no further reference to the original purchase order line details.
`3110`	Acknowledgement that an Order, with line details as shown, has been received, with no reference as to whether or not the supplier can meets its requirements
`3120`	Acknowledgement, including expected delivery, for ALL lines ordered.
`3130`	Acknowledgement, including expected delivery, for SOME lines ordered. Assumes the remaining lines will be, or have been, acknowledged separately. (Not used by EDICUG)
`3140`	Acknowledgement providing expected delivery information ONLY for those lines where the Supplier cannot meet the requested delivery date(s). Assumes the lines not included will be delivered as requested. (Not used by EDICUG)
`3145`	** Acknowledgement of order not able to be supplied. Query outstanding on customer account. No reference is made to the order line details
`3150`	Acknowledgement changing details which have previously been advised, eg. change in Date, Quantity, Price, etc. All details for a line must be shown, including those which have not changed
`3160`	** Acknowledgement category NOT defined. Will be used where the supplier's system does not have inbuilt indicators
`3170`	** Acknowledgement that a request to cancel an order has been received and actioned. No reference is made to the order line details.(Not used by EDICUG)
`3180`	Acknowledgement that an order has been received and that stock has been allocated to all lines.
`**`	3100, 3145, 3160 and 3170 can also be used in ACKMNT segment AOR if no line details are being sent
CAKHDR: First message of the Claims Acknowledgement File, File Format 107
`3200`	Claims Acknowledgement (News trade) - response to a claim for credit, indicating which claims have been accepted or rejected
PAYHDR: First message of the Payment Order File, File Format 20
`0835`	Payment Order - instruction on a bank to make a payment to a third party
DRAHDR: First message of the Debit Advice File, File Format 21
`0840`	Debit Advice - notification given by the bank to the payer to confirm that a payment has been, or will be, taken from their account
CRAHDR: First message of the Credit Advice File, File Format 22
`0845`	Credit Advice - notification given by the bank to the payee that a credit payment has been, or will be, made to their account
EXCHDR: First message of the Exception Condition File, File Format 23
`0850`	Exception - report from the bank to the payer that a problem has been identified with a payment
ISSUES: First message of the Issues File, File Format 101
`9000`	Issues (News trade) - master file showing details of the current issues of a magazine or newspaper, with selling restrictions
SORHDR: First message of the Supply and Returns File, File Format 106
`9005`	Supply and Returns (News trade) - report of the number of copies of an issued newspaper or magazine which have been sold or remain unsold
DYEHDR: First message of the Dye Instruction File, File Format 102
`9010`	Dye Order - order for special textile dying and finishing operations
`9011`	Return Dye Instruction - accompanies the returned dyed and finished items
PVUHDR: First message of the Price and Availability Updates File, File Format 108
`9020`	Complete transmission of Price and Availability Update File
`9021`	Update transmission of Price and Availability Update File

Need to exchange TRADACOMS messages with a UK retailer?

SupplyLens connects your ERP, e-commerce or accounting system to any TRADACOMS or EDIFACT trading partner: orders in, invoices out, fully managed.

Book a demo Learn about retail EDI →