Download Distribution Central requires a valid Purchase. Order (PO) for each product and/ or service order. No order will be processed without a valid PO. To be considered as valid, a PO must contain the following information. Arista. A signed end
Download 11. Prepaid and Partial Payment PO's. 11. Purchasing Process. 7. Procurement Card. 9. Receiving. 9. Record Retention. 8. Requesting New Vendors. 11. Ship to Locations. 11. Signature Authority. 6. Simple Outline of Punching Procedures
Download 11. Prepaid and Partial Payment PO's. 11. Purchasing Process. 7. Procurement Card. 9. Receiving. 9. Record Retention. 8. Requesting New Vendors. 11. Ship to Locations. 11. Signature Authority. 6. Simple Outline of Punching Procedures
Download CP is implementing the Purchase. Order for Services program (PO4S) in order to streamline invoice payments and the overall purchasing process. The process will improve coordination between CP and suppliers. The process is designed to e
Download 9. iPOS eProcurement solution. 10. Punch Out or Catalogues. 14. Electronic Interfaces for POs, goods receipt and supplier invoices. 16. Purchase Orders. 16. Supplier Invoices. 16. Benefits. 16. Drivers for electronic purchasing. 18. Abou
Download All of the materials covered in this workshop are also covered in the online tutorials http://www.hawaii.edu/kualifinancial/?page=training. This online tutorial can be useful before or after training in case you want to get a head start
Download Purchase Requisition and Purchase Order Policy. As part of Molloy's internal financial controls, the Purchasing and Accounting departments have implemented the purchase requisition process to help manage requests for purchases. Req
Download CP is implementing the Purchase. Order for Services program (PO4S) in order to streamline invoice payments and the overall purchasing process. The process will improve coordination between CP and suppliers. The process is designed to e
Download 9. iPOS eProcurement solution. 10. Punch Out or Catalogues. 14. Electronic Interfaces for POs, goods receipt and supplier invoices. 16. Purchase Orders. 16. Supplier Invoices. 16. Benefits. 16. Drivers for electronic purchasing. 18. Abou
Download 30 Sep 2010 ... UNSW Procedure. Procurement. Purchase Order Procedures. Responsible Officer. Director of Procurement. Contact Officer. Procure to Pay and Purchasing Manager. Superseded Documents. Accounting Manual Section 11 Items 2 - 45
Download Distribution Central requires a valid Purchase. Order (PO) for each product and/ or service order. No order will be processed without a valid PO. To be considered as valid, a PO must contain the following information. Arista. A signed end
Download A number of fields will be automatically populated: • PO, Rev - The system will provide the purchase order number automatically when the document is saved. • Created - This date will default in automatically. • Type. - Accept the system
Download 30 Sep 2010 ... UNSW Procedure. Procurement. Purchase Order Procedures. Responsible Officer. Director of Procurement. Contact Officer. Procure to Pay and Purchasing Manager. Superseded Documents. Accounting Manual Section 11 Items 2 - 45
Download A number of fields will be automatically populated: • PO, Rev - The system will provide the purchase order number automatically when the document is saved. • Created - This date will default in automatically. • Type. - Accept the system
Download All of the materials covered in this workshop are also covered in the online tutorials http://www.hawaii.edu/kualifinancial/?page=training. This online tutorial can be useful before or after training in case you want to get a head start
Download Purchase Requisition and Purchase Order Policy. As part of Molloy's internal financial controls, the Purchasing and Accounting departments have implemented the purchase requisition process to help manage requests for purchases. Req
Download Purchase Order Summary. Reference Guide. Revision 00. Page 1 of 4. Report Basics. What is the purpose of this report? What key business questions does this report answer? Who uses this report? How often is the report refreshed with data
Download Purchase Order Summary. Reference Guide. Revision 00. Page 1 of 4. Report Basics. What is the purpose of this report? What key business questions does this report answer? Who uses this report? How often is the report refreshed with data
Download Departments issue purchase requisition requests to procure goods or services to City. Purchasing. Requisitions leading to the creation of standard purchase orders go through the review and approval path of the requisitioning departments
Download 1 Feb 2018 ... Roles and Responsibilities. The system used to initiate, approve and track a purchase order at the university is the Kuali Financial System (KFS). The basic purchase order process is as follows: Unit/BSC creates requisitio
Download 1 Feb 2018 ... Roles and Responsibilities. The system used to initiate, approve and track a purchase order at the university is the Kuali Financial System (KFS). The basic purchase order process is as follows: Unit/BSC creates requisitio
Download Departments issue purchase requisition requests to procure goods or services to City. Purchasing. Requisitions leading to the creation of standard purchase orders go through the review and approval path of the requisitioning departments
1 standard purchase order terms and conditions for the provision of goods and/or services
Download 14 Sep 2010 ... the supplier of what is being purchased, the agreed cost, and the payment terms of the. University. • Communicating this in advance in an approved document minimizes the likelihood of queries, disputes and possible legal
PURCHASE ORDER TRADACOM 9 MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS
This document describes the Tradacom Purchase Orders message format that House of Fraser offers. You can receive your Purchase Orders in more than one format comprising of XML and EDI. The EDI formats we offer is in Edifact and Tradacom and the messages are dispatched via FTP only. In this document the format of the Tradacom Version 9 Purchase Order message is described and displayed to give a full view and understanding of the schema. Please see the following linked document for list of House of Fraser Ordering Types: http://www.hofsuppliers.co.uk/info/pdf/purchase_order_types.pdf
TRADACOM Orders 9 HOF
Page 3 of 15
26/01/09
HOUSE OF FRASER
TRADACOM Orders 9 HOF
EDI ‘ORDERS’ Message Version 9
Page 4 of 15
26/01/09
HOUSE OF FRASER
2.
EDI ‘ORDERS’ Message Version 9
SEGMENTS LAYOUT
` SEGMENT
STX
DATA ELEMENT = STDS
DATA ELEMENT NAME
Mandatory/ Fixed/ PICTURE Conditional Variable
START OF TRANSMISSION
M
Syntax Rules Identifier
M
Identifier
M
V
X(4)
M
F
9
: Version +
+
+
FROM
UNTO
TRDT
Value = ‘ANA’ Value = ‘1’
Identification of Transmission Sender
M
Code
M
F
X(14)
‘5019589000016’
: Name
C
V
X(35)
Value = ‘House of Fraser’
Identification of Transmission Recipient
M
Code
M
F
X(14)
Trading partners identification number.
: Name
C
V
X(35)
Trading Partner Name
Date and Time of Transmission
M
Date
M
F
9(6)
Format = ‘YYMMDD’
: Time
C
F
9(6)
Format = ‘HHMMSS’ Reference for the Transmission
+
SNRF
Sender's Transmission Reference
M
V
X(6)
+
RCRF
Recipient's Transmission Reference
M
V
X(8)
+
APRF
Application Reference
M
V
X(6)
+
PRCD
Transmission Priority Code
C
F
X(1)
TRADACOM Orders 9 HOF
COMMENTS
Page 5 of 15
Value = ‘ORDHDR’ Value = ‘ORDTES’ Code Values List 1 Not used by HoF
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
MHD
EDI ‘ORDERS’ Message Version 9
=
+
DATA ELEMENT NAME
Mandatory/ Conditional
MESSAGE HEADER
M
MSRF
Message Reference
M
TYPE
Type of Message
M
Type : Version Number = TYP +
COMMENTS
V
9(12)
Consecutive count of messages within the transmission
M
F
X6)
Value = ‘ORDHDR’
M
F
9(1)
Value = ‘9’ for this version
Value = ‘0470’ Mixed Order Types
TRANSACTION TYPE DETAILS
M
TCDE
Transaction Code
M
F
9(4)
TTYP
Transaction Type
C
V
X(12)
Not used by HoF
SUPPLIER DETAILS
M
Supplier's Identity
M
Supplier's ANA Location Code
C
F
9(13)
Trading Partner ANA Number (Where Used)
C
V
X(17)
Trading Partner Send / Receive Code (if no ANA No)
V
X(40)
Trading Partner Name
= SDT
Fixed/ PICTURE Variable
SIDN
: Supplier's Identity Allocated by Customer +
SNAM
Supplier's Name
C
+
SADD
Supplier's Address
C
Supplier's Address Line 1
C
V
X(35)
: Supplier's Address Line 2
C
V
X(35)
: Supplier's Address Line 3
C
V
X(35)
: Supplier's Address Line 4
C
V
X(35)
: Supplier's Post Code
C
V
X(8)
C
F
9(9)
Not used by HoF Not used by HoF Not used by HoF Not used by HoF Not used by HoF
+
VATN
TRADACOM Orders 9 HOF
Supplier's VAT Registration Number
Page 6 of 15
Not used by HoF
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
CDT
EDI ‘ORDERS’ Message Version 9
= CIDN
DATA ELEMENT NAME
Mandatory/ Conditional
MTR
M
Customer's Identity
M
Customer's ANA Identity
C
F
9(13)
Tradanet = ‘5019589000016’
C
V
X(17)
Edi*net = ‘HOUSEOFFRASER’
+
CNAM
Customer's Name
C
V
X(40)
Value = ‘House of Fraser’
+
CADD
Customer's Address Line 1
C
V
X(35)
Not used by HoF
: Customer's Address Line 2
C
V
X(35)
Not used by HoF
: Customer's Address Line 3
C
V
X(35)
Not used by HoF
: Customer's Address Line 4
C
V
X(35)
Not used by HoF
: Customer's Post Code
C
V
X(8)
Not used by HoF
=
=
COMMENTS
CUSTOMER DETAILS
: Customer's Identity as used by Supplier
FIL
Fixed/ PICTURE Variable
FILE DETAILS
M
FLGN
File Generation Number
M
V
9(4)
This message is sequential, per message type, per Trading Partner
+
FLVN
File Version Number
M
V
9(4)
+
FLDT
File Creation Date
M
F
9(6)
Original (which is always 1) is incremented by 1 for each additional copy created. Date File Created. Format = ‘YYMMDD’
+
FLID
File (Reel) Identification
C
V
X(6)
Not used by HoF
NOSG
MESSAGE TRAILER
M
Number of Segments in Message
M
TRADACOM Orders 9 HOF
Page 7 of 15
Control count of the number of segments comprising messages. V
9(4)
The count includes the MHD and MTR segments surrounding the message.
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
MHD
EDI ‘ORDERS’ Message Version 9
=
+
DATA ELEMENT NAME
Mandatory/ Conditional
MESSAGE HEADER
M
MSRF
Message Reference
M
TYPE
Type of Message
M
Type : Version Number CLO
= CLOC
Fixed/ PICTURE Variable
V
9(12)
Commences with 2 and increments by 1 for each order
M
F
X(6)
Value = ‘ORDERS’
M
F
9(1)
Value = ‘9’ for this Version
CUSTOMER'S LOCATION
M
Customer's Location
M
Customer's ANA Location Code
C
F
9(13)
HOF EAN13 Location Code Digits 9 to 12 HoF Store Number
: Customer's Own Location Code
C
V
X(17)
HoF Store Number 9(4)
: Supplier's Identification of Customer's Location
C
V
9(13)
HOF EAN13 Location Code if delivery to HDS Depot
V
X(40)
Value = ‘Customer’s Name’ for delivery
Delivery Address
+
CNAM
Customers Name
C
+
CADD
Customer's Address
C
Customer's Address Line 1
C
V
X(35)
: Customer's Address Line 2
C
V
X(35)
: Customer's Address Line 3
C
V
X(35)
: Customer's Address Line 4
C
V
X(35)
: Customer's Post Code
C
V
X(8)
TRADACOM Orders 9 HOF
COMMENTS
Page 8 of 15
Could be - Customer Store Warehouse
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
ORD
EDI ‘ORDERS’ Message Version 9
= ORNO
DATA ELEMENT NAME
Mandatory/ Conditional
COMMENTS
ORDER REFERENCES
M
Order Number and Date
M
Customer's Order Number
C
V
X(17)
HoF Order Number 9(6)
: Supplier's Order Number
C
V
X(17)
Not used by HoF
: Date Order Placed by Customer
C
F
9(6)
Order Date. Format = ‘YYMMDD’
: Date Order Received by Supplier
C
F
9(6)
Not used by HoF
+
CLAS
Order Classification
C
F
X(1)
Code Values List 6
+
ORCD
Order Code
C
F
X(1)
‘N’ = New Order ‘A’ = Amended Order
+
SCRF
Specification/Contract References
C
Specification Number
C
V
X(17)
Promotion Number x(4)
C
V
X(17)
Promotion Narrative x(17)
: Contract Number DIN
Fixed/ PICTURE Variable
=
‘X’ = Christmas ‘P’ = Promotion Blank = Not Applicable ‘P’ = Proposed Order ‘C’ = Canceled Order
Used for Promotion and Christmas Orders Only
DELIVERY INSTRUCTIONS
C
EDAT
Earliest Delivery Date
C
F
9(6)
Earliest Delivery Date. Format = ‘YYMMDD’
+
LDAT
Latest Delivery Date
C
F
9(6)
Latest Delivery Date. Format = ‘YYMMDD’
+
RATM
Required Arrival time
C
Earliest time
C
F
9(4)
Not used by HoF
: Latest Time
C
F
9(4)
Not used by HoF
TRADACOM Orders 9 HOF
Page 9 of 15
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
+
+ DNA
EDI ‘ORDERS’ Message Version 9
Mandatory/ Conditional C
Delivery Instruction Narrative Line 1
C
V
X(40)
: Delivery Instruction Narrative Line 2
C
V
X(40)
: Delivery Instruction Narrative Line 3
C
V
X(40)
: Delivery Instruction Narrative Line 4
C
V
X(40)
Delivery Instruction Number
C
V
X(17)
DATA NARRATIVE
C
SEQA
First Level Sequence Number
M
V
9(4)
DNAC
Data Narrative Code
C
Code Table Number
C
V
9(4)
C
V
X(3)
DINN
: Code Value +
Fixed/ PICTURE Variable
Delivery Instruction Narrative
DINS
=
+
DATA ELEMENT NAME
RTEX
TRADACOM Orders 9 HOF
Delivery Instructions applied to this order (If Applicable)
Not used by HoF
Starts at 1 and increments by 1 for each segment of this type in this message Not used by HoF
Registered Text
C
First Registered Application Code
C
V
X(3)
: Application Text
C
V
X(40)
: Second Registered Application Code
C
V
X(3)
: Application Text
C
V
X(40)
: Third Registered Application Code
C
V
X(3)
: Application Text
C
V
X(40)
: Fourth Registered Application Code
C
V
X(3)
: Application Text
C
V
X(40)
Page 10 of 15
COMMENTS
Not used by HoF
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
+
OLD
EDI ‘ORDERS’ Message Version 9
GNAR
=
+
DATA ELEMENT NAME
Mandatory/ Conditional
Fixed/ PICTURE Variable
COMMENTS
General Narrative
C
General Narrative Line 1
C
V
X(40)
Carrier (X(20)) / Port (X(20))
: General Narrative Line 2
C
V
X(40)
Agent (X(30)) / Agreement Number (X(10))
: General Narrative Line 3
C
V
X(40)
Freight Method
: General Narrative Line 4
C
V
X(40)
Agreed Delivery Dates (Up to 4 Agreed Delivery Dates), Expected Date, Ex-Works Date (dates are in the format: YYMMDD)
V
9(4)
Starts at 1 and increments by 1 for each segment of this type in this message
ORDER LINE DETAILS
M
SEQA
First level Sequence Number
M
SPRO
Supplier's Product Number
M
EAN13 Code for the Traded Unit
C
F
9(13)
EAN13 / UPC allocated by supplier
: Supplier's Code for the Traded Unit
C
V
X(30)
Supplier Code. Only if no EAN13 (by special agreement)
: DUN-14 Code for the Traded Unit
C
F
9(14)
Not used by HoF
F
9(13)
Not used by HoF
+
SACU
Supplier's EAN Code for his Designated Consumer Unit
C
+
CPRO
Customer's Product Number
C
Customer's Own Brand EAN Number
C
F
9(15)
HoF EAN13 Bar-code (2 leading zeros)
C
V
X30)
HoF Line Item Number 9(9)
9(15)
Consumer Units in Traded Unit. Value = ‘1’
: Customer's Item Code +
UNOR
TRADACOM Orders 9 HOF
Unit of Ordering
M
Consumer Units in Traded Unit
C
V
: Ordering Measure
C
V
: Measure Indicator
C
V
Page 11 of 15
9(10)v999 Not Used by HoF X(6)
Not Used by HoF
26/01/09
HOUSE OF FRASER
SEGMENT
EDI ‘ORDERS’ Message Version 9
DATA ELEMENT +
+
OQTY
OUCT
DATA ELEMENT NAME
Mandatory/ Conditional
Fixed/ PICTURE Variable
Quantity Ordered
M
Number of Traded Units Ordered
C
V
: Total Measure Ordered
C
V
: Measure Indicator
C
V
9(15)
COMMENTS
Number of units ordered (Excluding HoF decimal departments)
9(10)v999 Number of units ordered (3 implied decimal places) HoF decimal departments only X(6)
Not used by HoF
Ordering Unit Cost
C
Cost Price
C
V
C
V
X(6)
Not used by HoF
9(10)v9999 Unit Cost 9(10)V9999
+
PIND
Special Price Indicator
C
V
X(4)
Code Values List 5. Not Used by HoF
+
TFIN
To Follow Indicator
C
F
X
Code Values List 8. Not Used by HoF
+
TDES
Traded Unit Description
C
Traded Unit Description Line 1
C
V
X(40)
HoF Style Code x(8)
: Traded Unit Description Line 2
C
V
X(40)
HoF Style Description. Up to 40(x) Could contain a 2 line Narrative Description for those lines which are not normally carried on the HoF Catalogue and therefore no valid Product Code is available. These orders are identified with Value = ‘NARRATIVE’ in OLD Segment CPRO Element Value = ‘NO-PRODUCT-CODE’ in OLD Segment SPRO Element
+
SCRF
Specification/Contract References
C
Specification Number
C
V
X(17)
Not Used by HoF
C
V
X(17)
Not Used by HoF
: Contract Number
NB
Lines with no Product Codes have:
TRADACOM Orders 9 HOF
Segment Segment Segment
OLD OLD OLD
Element Element Element
Page 12 of 15
SPRO Value ‘NO-PRODUCT-CODE’ CPRO Value ‘NARRATIVE’ TDES Value ‘Up to 80 Characters of product description’ 26/01/09
HOUSE OF FRASER
SEGMENT
DNB
EDI ‘ORDERS’ Message Version 9
DATA ELEMENT =
DATA ELEMENT NAME
Mandatory/ Conditional
COMMENTS
Fixed/ PICTURE Variable
DATA NARRATIVE
C
SEQA
First Level Sequence Number
M
V
9(4)
Takes the value of SEQA in the preceding segment with which this Segment is nested
+
SEQB
Second Level Sequence Number
M
V
9(4)
Starts at 1 and is incremented by 1 for each 2nd level repeat (1)
+
DNAC
Data Narrative Code
C
Code Table Number
C
V
9(4)
Value = ‘22’ ANA Code Values List 22
C
V
X(3)
Value = ‘17’ Order subject to our current Terms and Conditions
: Code Value +
+
RTEX
GNAR
TRADACOM Orders 9 HOF
First Occurrence of DNB
Registered Text
C
First Registered Application Code
C
V
X(3)
Value = ‘108’ Selling Price
: Application Text
C
V
X(40)
Selling Price 9(6,7) - Pence
: Second Registered Application Code
C
V
X(3)
Value = ‘144’ HoF Season Code
: Application Text
C
V
X(40)
Season Code x - 1 digit alpha Season code
: Third Registered Application Code
C
V
X(3)
Value = ‘109’ HoF Merchandise Department
: Application Text
C
V
X(40)
HoF Department Number 9(1,4) – 1 to 4 digit number
: Fourth Registered Application Code
C
V
X(3)
Value = ‘141’ Colour Description of the Product
: Application Text
C
V
X(40)
HoF colour description up to x(40) Additional Description at Product Level
General Narrative
C
General Narrative Line 1
C
V
X(40)
Line 1 of ‘Additional Description’
: General Narrative Line 2
C
V
X(40)
Line 2 of ‘Additional Description’
: General Narrative Line 3
C
V
X(40)
Line 3 of ‘Additional Description’
: General Narrative Line 4
C
V
X(40)
Line 4 of ‘Additional Description’
Page 13 of 15
26/01/09
HOUSE OF FRASER
SEGMENT
DNB
EDI ‘ORDERS’ Message Version 9
DATA ELEMENT =
Mandatory/ Fixed/ PICTURE Conditional Variable
DATA ELEMENT NAME
COMMENTS
DATA NARRATIVE
C
SEQA
First Level Sequence Number
M
V
9(4)
Takes the value of SEQA in the preceding segment with which this segment is nested
+
SEQB
Second Level Sequence Number
M
V
9(4)
Starts at 1 and is incremented by 1 for each 2nd level repeat (2)
+
DNAC
Data Narrative Code
C
Code Table Number
C
V
9(4)
Value = ‘22’ ANA Code Values List 22
C
V
X(3)
Value = ‘17’ Order subject to our current Terms and Conditions
: Code Value +
+
RTEX
GNAR
TRADACOM Orders 9 HOF
Second Occurrence of DNB
Registered Text
C
First Registered Application Code
C
V
X(3)
Value = ‘142’ - Size Description of the Product
: Application Text
C
V
X(40)
HoF size description - up to x(40)
: Second Registered Application Code
C
V
X(3)
Value = ‘200’ - In-Store Price
: Application Text
C
V
X(40)
HoF Ticket Price 9(10).99 - (Decimal Point Output)
: Third Registered Application Code
C
V
X(3)
Value = ‘249’ - Type of ticket used by HoF
: Application Text
C
V
X(40)
HoF Ticket Type -
: Fourth Registered Application Code
C
V
X(3)
Not used by HoF
: Application Text
C
V
X(40)
Not used by HoF
‘W’ = Swing ‘L’ = Large Adhesive ‘S’ = Small Adhesive ‘D’ = Dumbbell
Additional Description at Product Level
General Narrative
C
General Narrative Line 1
C
V
X(40)
Line 5 of ‘Additional Description’
: General Narrative Line 2
C
V
X(40)
Line 6 of ‘Additional Description’
: General Narrative Line 3
C
V
X(40)
Line 7 of ‘Additional Description’
: General Narrative Line 4
C
V
X(40)
Line 8 of ‘Additional Description’
Page 14 of 15
26/01/09
HOUSE OF FRASER
DATA ELEMENT
SEGMENT
OTR
MTR
=
DATA ELEMENT NAME
Mandatory/ Conditional
Fixed/ PICTURE Variable
COMMENTS
ORDER TRAILER
M
Lines Ordered
M
MESSAGE TRAILER
M
Number of Segments in Message
M
MESSAGE HEADER
M
MSRF
Message Reference
M
TYPE
Type of Message
M
Type
M
F
X(6)
Value = ‘ORDTLR’
M
F
9(1)
Value = ‘9’ for this version
V
9(10)
Total number of order details messages on file
V
9(4)
Value = ‘3’ for this message
V
9(5)
Control count of number of messages in transmission
LORD
= NOSG
MHD
EDI ‘ORDERS’ Message Version 9
=
V
9(10)
Number of 'OLD' segments for this order
V
9(4)
Control count of the number of segments comprising message. Count includes MHD and MTR segments surrounding message.
V
9(12) Consecutive count of messages within the transmission