Edi invoice 810 Version 4010 Technical Requirements September 20, 2000




Yüklə 93.34 Kb.
tarix14.04.2016
ölçüsü93.34 Kb.




®



EDI

INVOICE

810 - Version 4010

Technical Requirements
September 20, 2000
Document Version 4010.4
Revised August, 2012
® - Registered Trade Mark of the Hudson’s Bay Company

Transaction Set Summary 1

Transaction Set Summary cont. 2

Transaction Set Requirements 3

ST Segment 3

SE Segment 3

BIG Segment 4

CUR Segment 5

N1 Segment 6

ITD Segment 6

DTM Segment 8

TDS Segment 11

SAC Segment 13

ISS Segment 14

CTT Segment 15



Data Mapping: Functional Acknowledgement (997) 16

Functional Group Envelope 16

GS Segment 16

GE Segment 16

Transaction Set Summary 17

Transaction Set Requirements 18

ST Segment 18

SE Segment 18

AK1 Segment 19

AK9 Segment 19

AK2 Segment 20

AK5 Segment 20


Transaction Set Summary




Individual descriptions of each segment follow.
Segment POS Segment HBC HBC

Id Name Reqt Usage
. Header Area

. ST 010 Transaction Set header M 1 occurrence

. BIG 020 Begin IN segment M 1 occurrence

. CUR 040 Currency - 1 occurrence

. REF 050 Reference Numbers - not used

. PER 060 Admin Contact - not used

. N1 070 Name Reference 1 M 2 occurrences

. N2 080 Name Reference 2 - not used

. N3 090 Name Reference 3 - not used

. N4 100 Name Reference 4 - not used

. ITD 130 Terms of Sale - 1 occurrence

. DTM 140 Date Reference - 1 occurrence

. FOB 150 F.O.B. Related Instructions - not used

. PID 160 Production / Item Desc - not used

. Detail Area

. IT1 010 Item Base Data M 999 occurrences max.

. IT3 030 Additional Item Data - not used

. CTP 050 Pricing Information - not used

. MEA 059 Measurements - not used

. PID 060 Production / Item Desc - not used

. MEA 070 Measurements - not used

. PKG 090 Marking, Packaging, Loading - not used

. PO4 100 Item details - not used

. REF 120 Reference Identification - not used

. SDQ 140 Destination Qty - 500 occurrences max

. CAD 160 Carrier Detail - not used

. SAC 180 Service, Promotion, Allowance - not used

. SLN 200 Subline Item Detail - not used

. TC2 235 Commodity - not used

Transaction Set Summary cont.




. Summary Area

. TDS 010 Total Monetary Val Summary M 1 occurrence



. CAD 030 Carrier Detail O 1 occurrence

. SAC 040 Service, Promotion, Allowance M more than 1 occurrence

. ISS 060 Invoice Shipment Summary M 1 occurrence

. PID 065 Production / Item Desc - not used

. CTT 070 Transaction totals M 1 occurrence

. SE 080 Transaction Set trailer M 1 occurrence


Transaction Set Requirements




ST Segment

Purpose: To indicate the start of a transaction set and to assign a control number.


Element Value Length Comment
. ST01 810 X(3)

. ST02 control Nbr X(9)




SE Segment

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments.



Element Value Length Comment
. SE01 Nbr. of segments 9(6)

included

. SE02 Control Nbr. X(9) same as ST02

BIG Segment


Purpose: To indicate the beginning of the invoice and transmit identifying dates.



Element Value Length Comment
. BIG01 Invoice Date X(8) format ccyymmdd

. BIG02 Invoice Nbr. X(15)

. BIG03 Purchase Order Date X(8) format ccyymmdd

. BIG04 Purchase Order Nbr. 9(11) Purchase Order Number (Notes)

. BIG05 not used

. BIG06 not used

. BIG07 not used

. BIG08 not used

. BIG09 not used

. BIG10 Consolidated Nbr. X(10) ASN Shipment Nbr. (Notes)




Important Notes:
1. BIG04 Purchase order number is used as part of 3 Way Match it must match what was sent on the EDI850.

Example: 12345670596 11 bytes 7 for PO# 4 for location DC

Example: 12345679999 11 bytes 7 for PO # 4 location DTS
2. BIG10 must be exactly what was sent on the ASN 856 BSN02.
3. The ASN number is verified as part of the 3 Way Match on vendor Invoice.

CUR Segment


Purpose: To indicate the currency used in the invoice.



Element Value Length Comment

. CUR01 Entity ID Code X(2) ‘BY’

. CUR02 Currency Code X(3) ‘USD’ or ‘CAD’ (Note)

. CUR03 not used

. CUR04 not used

. CUR05 not used

. CUR06 not used

. CUR07 not used

. CUR08 not used

. CUR09 not used

. CUR10 not used

. CUR11 not used

. CUR12 not used

. CUR13 not used

. CUR14 not used

. CUR15 not used

. CUR16 not used

. CUR17 not used

. CUR18 not used

. CUR19 not used

. CUR20 not used

. CUR21 not used



Important Notes:
1. CUR02 must be exactly what was sent on the PO 850.
2. The Currency Code is verified as part of the 3 Way Match on vendor Invoice.

N1 Segment


Purpose: To identify the Vendor Name, Number and Store / DC information.




Element Value Length Comment
. Segment 1
. N101 ‘BY’ X(2) Buying Party (Purchaser0

. N102 not used

. N103 ‘92’ X(2) Assigned by Buyer

. N104 Store /DC Number X(6) Truncated to the left (Notes)

. N105 not used

. N106 not used


Important Notes:
1. N104: Bulk and or Pre-Disturbed orders use the DC#.

Example: DC# 0596 000596
2. N104: DTS (Direct to Store) use the Store #.

Example: Store# 640 000640

. Segment 2


. N101 ‘SU’ X(2) Supplier / Manufacturer

. N102 Vendor Name X(35)

. N103 ‘92’ X(2) Assigned by Buyer

. N104 Vendor Nbr X(9)

. N105 not used

. N106 not used




ITD Segment

Purpose: Terms of Sale / Deferred Terms of Sale



Element Value Length Comment
. ITD01 Terms Type Code X(2) ‘05’, ‘02’, ‘12’, ‘08’

. ITD02 Terms Basis Date Code X(2) ‘15’

. ITD03 Discount Percent 9(6) Terms Discount Percent (Notes)

. ITD04 Terms Disc Due Date X(8) format ccyymmdd

. ITD05 Terms Disc Days Due X(3)

. ITD06 not used

. ITD07 Terms Net Days X(2)

. ITD08 not used

. ITD09 not used

. ITD10 not used

. ITD11 not used

. ITD12 not used

. ITD13 Day of Month X(2)

. ITD14 not used

. ITD15 not used

Important Notes:
1. ITD segments are not used for HBC 3 Way Match.
2. Terms and Discounts are calculated based on Vendor MMVA terms (Off PO Adjustment). Refer to EDI820 to review

adjustments.

DTM Segment

Purpose: Date Reference



Element Value Length Comment
. DTM01 Date Qualifier X(3) ‘011’ Shipped Date

. DTM02 Date X(8) Format ccyymmdd

. DTM03 not used

. DTM04 not used

. DTM05 not used

. DTM06 not used



IT1 Segment
Purpose:

Specify invoice line item data. One occurrence, for each line item.

One of either UPC # or Item # is mandatory
Element Value Length Comment
. IT101 Assigned Id nbr 9(6)

. IT102 Item Qty Invoiced S9(10)

. IT103 Unit of Measure X(2) ‘EA’ or ‘CA’

. IT104 Unit Price 9(12)v99 (Notes)

. IT105 Basis of Unit Price Code X(2) ‘WE’ Wholesale cost / each

. IT106 ‘UP’ or ‘EN’ X(2) ‘UPC’ or ‘EAN’ ID Qual

. IT107 UPC or EAN # 9(13) * (Notes)

. IT108 ‘VA’ X(2)

. IT109 Vendor Style Nbr. X(20) optional (Notes)

. IT110


. IT111

. IT112 not used

. IT113 not used

. IT114 not used

. IT115 not used

. IT116 not used

. IT117 not used

. IT118 not used

. IT119 not used

. IT120 not used

. IT121 not used

. IT122 not used

. IT123 not used

. IT124 not used

. IT125 not used

Important Notes:
1. UPC and Item number must be left justified.

2. Vendor Style optional if UPC is present.

3. Item Price must have a decimal point

The decimal point is only required if there are decimals greater than zero

Example: $ 29.00 would be sent as 29

$12.95 would be sent as 12.95

SDQ Segment: Optional (Note)

Purpose: To describe Destination Quantity information.


Element Value Length Comment
. SDQ01 Unit of Measure Code X(2) ‘EA’

. SDQ02 Identification Code Qual X(2) ‘92’ assigned by Buyer

. SDQ03 Identification Code X(6) Store Number

. SDQ 04 Quantity Invoiced 9(10)

. SDQ 05 Identification Code X(6) Store Number

. SDQ 06 Quantity Invoiced 9(10)

. SDQ 07 Identification Code X(6) Store Number

. SDQ 08 Quantity Invoiced 9(10)

. SDQ 09 Identification Code X(6) Store Number

. SDQ 10 Quantity Invoiced 9(10)

. SDQ 11 Identification Code X(6) Store Number

. SDQ 12 Quantity Invoiced 9(10)

. SDQ 13 Identification Code X(6) Store Number

. SDQ 14 Quantity Invoiced 9(10)

. SDQ 15 Identification Code X(6) Store Number

. SDQ 16 Quantity Invoiced 9(10)

. SDQ 17 Identification Code X(6) Store Number

. SDQ 18 Quantity Invoiced 9(10)

. SDQ 19 Identification Code X(6) Store Number

. SDQ 20 Quantity Invoiced 9(10)

. SDQ 21 Identification Code X(6) Store Number

. SDQ 22 Quantity Invoiced 9(10)



Important Notes:
1. SDQ segments currently not used by HBC for 3 Way Match.

TDS Segment

Purpose: To provide Total Monetary Value Summary.


Element Value Length Comment
. TDS01 Total Amt. of Invoice S9(9)v99 Invoice Gross Amount

Including all applicable Taxes

. TDS02 Amount Subject to terms S9(9)v99

. TDS03 Amount Due if paid by

Terms date S9(9)v99

. TDS04 Amount of Terms

discount S9(9)v99




Important Notes:
1. TDS01 segments are used for HBC 3 Way Match must be gross amount including all applicable taxes.
2. TDS01 The decimal point is assumed.

Example: $5000.00 would be sent as 500000

$6000.95 would be sent as600095
3. Terms and Discounts are calculated based on Vendor MMVA terms (Off PO Adjustment) Refer to EDI820 to review

adjustments.

CAD Segment
Purpose: To provide Carrier Transportation Details
Element Value Length Comment
. CAD01 Transportation Method

type code X(2) A, AE, C, L, M, U

.CAD02 not used

.CAD03 not used

.CAD04 Standard Carrier

Alpha Code X(4) SCAC Code

.CAD05 Routing X(35) Free form carrier name

. CAD06 not used

. CAD07 Reference ID Qual X(2) ‘BM’ for BOL Number

. CAD08 Reference ID X(17) BOL Number (Note)


Important Notes:
1. CAD08 BOL number must match what’s on ASN856

SAC Segment

Purpose: To convey information relative to order allowances and charges.


Occurrences: possible 2
Element Value Length Comment
. SAC01 Charge X(1) ‘C’

. SAC02 Tax Charge Code X(4) D360’ GST or HST



‘H770’ QST

. SAC03 not used

. SAC04 not used

. SAC05 Charge Amt. 9(9)v99 (Note)

. SAC06 not used

. SAC07 not used

. SAC08 not used

. SAC09 not used

. SAC10 not used

. SAC11 not used

. SAC12 not used

. SAC13 not used

. SAC14 not used

. SAC15 Description X(10) GST, HST or QST (Note)

. SAC16 not used
Important Notes:
1. SAC02 Tax Charge Cod must match SAC15.
2. SAC05 segment assumes the decimal point.

Example: $135.75 would be sent as 13575

$100.00 would be sent as 10000
3. SAC15 segment must state GST, HST or QST for description.


ISS Segment

Purpose: To convey Invoice Shipment Summary.


Element Value Length Comment
. ISS01 Nbr of units shipped 9(10)

. ISS02 Unit of Measure X(2) ‘EA’

. ISS03 Weight X(10) in ‘lbs or oz optional

. ISS04 Weight Unit of Measure

Code X(2) ‘LB’, ‘OZ’ optional

CTT Segment


Purpose: To provide a hash total.


Element Value Length Comment
. CTT01 Nbr. of IT1 segments 9(6)

. CTT02 not used

. CTT03 not used

. CTT04 not used

. CTT05 not used

. CTT06 not used

. CTT07 not used

Data Mapping: Functional Acknowledgement (997)




Functional Group Envelope




GS Segment


Purpose: To indicate the beginning of a functional (997) group and provide control information. HBC transmit the following format for Functional Acknowledgements from their business partners:



Element Value Length Comment
. GS01 FA X(2) Functional Acknowledgement (997)

. GS02 X(12) Sender Id. (Note)

. GS03 Receiver Id. X(12) assigned by receiver

. GS04 Interchange Date X(8) format ccyymmdd

. GS05 Interchange Time X(4) hhmm

. GS06 Control # 9(9)

. GS07 X X(1) ASC.X12 standards

. GS08 004010VICS X(12) VICS Version 4010


Important Note:

Please distinguish on your GS02 between The Bay and Zellers

GE Segment

Purpose: To indicate the end of a functional group and provide control information.



Element Value Length Comment
. GE01 # of ST segments 9(6)

. GE02 control # 9(9) same as GS06



Transaction Set Summary

HBC return a Functional Acknowledgement for each transmission at the transaction set level. The table below shows the segments that will be sent.

A detailed description, of each segment follows.



Segment Segment HBC HBC

ID Name Req Usage




. ST Transaction Set header M 1 occurrence

. AK1 Functional Group header M 1 occurrence

. AK2 Transaction Set header M 1 occurrence for each

Transaction set



. AK3 Data Segment Note - not used

. AK4 Data Element Note - not used

. AK5 Transaction Set trailer M 1 occurrence for each

Transaction set

. AK9 Functional Group trailer M 1 occurrence

. SE Transaction Set trailer M 1 occurrence

Transaction Set Requirements




ST Segment

Purpose: To indicate the start of a transaction set and to assign a control number.




Element Value Length Comment
. ST01 997 X(3) Trans ID for acknowledgement

. ST02 Control Nbr. X(9)



SE Segment

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments.



Element Value Length Comment
. SE01 Nbr. of segments 9(6)

. SE02 Control Nbr. X(9) Same as ST02


AK1 Segment

Purpose: To start the acknowledgement of a functional group.




Element Value Length Comment
. AK101 Functional Group ID X(2)

. AK102 control Nbr Z(9)


AK9 Segment

Purpose: To acknowledge acceptance or rejection of a functional group and report the number of included transaction sets, accepted sets, and received sets within this functional group.




Element Value Length Comment
. AK901 Functional Group Ack Cde X(1) eg. 'A" - Accepted

. AK902 Transaction Sets Included 9(6)

. AK903 Transaction Sets received 9(6)

. AK904 Transaction Sets accepted 9(6)

. AK905 Error Code X(1)

. AK906 Error Code X(1)

. AK907 Error Code X(1)

. AK908 Error Code X(1)

. AK909 Error Code X(1)

AK2 Segment

Purpose: To start the acknowledgement of a single transaction set.




Element Value Length Comment
. AK201 Trans. Set ID X(2)

. AK202 Trans. Set Control Nbr. X(9)



AK5 Segment

Purpose: To acknowledge acceptance or rejection and to report errors in a transaction set.



Element Value Length Comment
. AK501 Set Ack Code X(1) e.g. 'A' - Accepted

. AK502 Error Code X(1)

. AK503 Error Code X(1)

. AK504 Error Code X(1)

. AK505 Error Code X(1)

. AK506 Error Code X(1)






Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©azrefs.org 2016
rəhbərliyinə müraciət

    Ana səhifə