![]() | Vendor Partnership Guide |
|
Error
Code |
For Requirements / Information Concerning |
Contacts |
Phone / Fax / E-Mail |
|
150 |
Cross Dock Vendor Certification
Requirements:
|
Jonny Ortiz EDI / Merchandise Support Manager |
(941) 744-4366 (941) 745-2813 jortiz2@beallsinc.com |
|
200 270 900 |
Transportation:
|
Transportation Office |
(941) 744-4658 (941) 747-4378 Traffic@beallsinc.com |
|
250 |
|
Buyer |
(941) 747-2355 |
|
300 350 |
Cross-Dock Vendor Compliance:
|
Jonny Ortiz EDI / Merchandise Support Manager |
(941) 744-4366 (941) 745-2813 jortiz2@beallsinc.com |
|
600 700 |
Cross- Dock Operations:
|
Jonny Ortiz EDI / Merchandise Support Manager |
(941) 744-4366 (941) 745-2813 jortiz2@beallsinc.com |
|
800 |
|
Vendors A-L Vendors M-Z |
(941) 744-4369 (941) 744-4404 accountspayable@beallsinc.com |
|
|
Delivery Appointments |
Transportation Office |
(941) 744-4514 |
|
|
Return to Vendors |
Area Manager |
(941) 744-4447 (941) 750-8100 Imontenegro@beallsinc.com (941) 747-2355 |
|
|
Carton Packaging Information /
Questions |
|
(941) 744-4682 dkeller@beallsinc.com |
|
BEALL’S Department Stores Inc. Dear Vendor, Beall’s has
identified your company as a candidate to enter our EDI Store Cross-Dock
Certification Program. There are
several operational requirements that must be met in order for your company
to realize the benefits of this program. The Vendor
requirements are: 1) Mark 100% of merchandise with a
scan-able UPC bar-code ticket and the retail price. 2) Make UPC data available to Beall's
through the Inovis (formerly QRS) UPC catalog. 3) Receive an EDI PO and ship to Beall’s
DC and mark for Beall's Store - store distribution will be transmitted 7 days
prior to the start ship date. 4) Transmit an EDI Advance Ship Notice
(ASN) indicating individual carton content by store. 5) Label all cartons with a
Bealls-certified UCC-128 label that matches the ASN. 6) Do not under-pack cartons - ideally,
each store’s assortment should be contained in the least number of cartons as
possible. The benefits your
company will receive are an 80% reduction in All of Beall’s
vendors who are part of our EDI Store Cross-Dock Program will be assigned a
Vendor Certification Rating, which will further reduce throughput time for
the most accurate vendor shipments. Beall’s
strongly recommends the “scan and pack” method to create an ASN. If your ASN does not match the carton
contents at the UPC level, an expense offset will be assessed. If you have
questions please call (941) 744-4366. Sincerely, Jonny Ortiz EDI/Merchandise
Support Manager Company
Name:_______________________, will comply with the EDI Store Cross-Dock
requirements. We will be able to
start EDI setup for required Purchase Order / Advance Ship Notice, by {Date} Signature:_______________________________________ Print:___________________________________________ Title:___________________________________________ |
|
Beall’s Department Stores, Beall's Inc EDI TRADING PARTNER AGREEMENT ________________________________________ (Your Company Name) ________________________________________ (Your Company Address) ________________________________________ (City, State, Zip) Since
the Beall’s Department Stores system for electronic transmission of purchase
order information does not permit the inclusion of standard terms and
conditions with each Beall’s purchase order, it is necessary that we have
written acknowledgment from our vendors that such standard terms and conditions
will be applicable to all purchase orders sent electronically. The key components
of this agreement are: Unless otherwise
specified, all EDI orders must be shipped to: Beall’s Conform to Beall’s Beall’s will
conduct electronic data interchange of business documents with its vendors as
it deems feasible and appropriate. The interchange of any such documents will
occur via a third party VAN store and forward mailbox service of Inovis.
Bealls’ will share with its vendors those costs that are directly
attributable to the interchange of business documents and will pay only those
charges incurred due to the communication and processing of such documents
between Beall’s and its third party vendor. Any and all similar costs between
the third party and the vendor will be borne entirely by the vendor. It is the vendors
responsibility to monitor duplicate control numbers to avoid double
shipments. Any arrangement other
than described above, must receive prior approval form Beall’s Vice President
of Merchandising. BY: ________________________________________________ (Beall’s EDI/Merchandise Support
Manager) ACCEPTED AND AGREED: ________________________________________________ (Your Company Name) DATE: _____________
BY: ________________________________________________ (Authorized Signature) |
The ISA segment marks the beginning of the transmission and provides sender/receiver identification. Each GS segment marks the beginning of a functional group. There may be more than one functional groups within each transmission. The ST segment marks the beginning of each transaction set (document). There can be up to 999,999 transaction sets within each functional group. The interchange control structure is common to all transaction sets.
Segment Hierarchy
|
ISA |
|
|
Transmission Envelope |
|
GS |
|
Functional Group 1 |
|
|
ST |
Transaction Set 1 |
||
|
: |
|||
|
SE |
|||
|
ST |
Transaction Set 2 |
||
|
: |
|||
|
SE |
|||
|
|
: |
||
|
ST |
Transaction Set n |
||
|
: |
|||
|
SE |
|||
|
GE |
|
||
|
|
: |
|
|
|
GS |
|
Functional Group 2 |
|
|
: |
|
||
|
GE |
|
||
|
|
: |
|
|
|
GS |
|
Functional Group n |
|
|
: |
|
||
|
GE |
|
||
|
IEA |
|
|
ISATRANSACTION SET HEADER Segment: ISA Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To start and identify an
interchange of zero or more functional groups and interchange-related control
segments
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ISA01 |
I01 |
Authorization
Information Qualifier Code identifying the
type of information in the Authorization Information 00 No authorization
information present |
M |
ID |
2/2 |
|
ISA02 |
I02 |
Authorization
Information Information used for
additional identification or authorization of the interchange sender or the data
in the interchange; the type of information is set by the Authorization
Information Qualifier blank |
M |
AN |
10/10 |
|
ISA03 |
I03 |
Security Information
Qualifier Code identifying the
type of information in the Security Information 00 No authorization information
present |
M |
ID |
2/2 |
|
ISA04 |
I04 |
Security Information This is used for
identifying the security information about the interchange sender or the data
in the interchange; the type of information is set by the Security
Information Qualifier Blank |
M |
AN |
10/10 |
|
ISA05 |
I05 |
Interchange ID
Qualifier Code indicating the
system/method of code structure used to designate the sender ID element being
qualified 12 Phone |
M |
ID |
2/2 |
|
ISA06 |
I06 |
Interchange Sender ID Identification code
published by the sender for other parties to use as the receiver ID to route
data to them; the sender always codes this value in the sender ID element 9417472355 Test ID for Beall’s 8137472355 Production ID for
Beall’s |
M |
AN |
15/15 |
|
ISA07 |
I07 |
Interchange ID
Qualifier Code indicating the
system/method of code structure used to designate the sender ID element being
qualified |
M |
ID |
2/2 |
|
ISA08 |
I08 |
Interchange Receiver ID Identification code
published by the sender for other parties to use as the receiver ID to route
data to them; the sender always codes this value in the sender ID element UCC Assigned
Communication ID |
M |
AN |
15/15 |
|
ISA09 |
I09 |
Interchange Date Date of the
interchange, YYMMDD |
M |
DT |
6/6 |
|
ISA10 |
I10 |
Interchange Time Time of the
interchange, HHSS |
M |
TM |
4/4 |
|
ISA11 |
I65 |
Standard ID U ANSI X12 |
M |
|
1/1 |
|
ISA12 |
I11 |
Interchange Control
Version Number Code specifying the
version number of the interchange control segments 00401, 00402, 00403 |
M |
ID |
5/5 |
|
ISA13 |
I12 |
Interchange Control
Number A control number
assigned by the interchange sender |
M |
N0 |
9/9 |
|
ISA14 |
I13 |
Acknowledgment
Requested Code indicating
sender’s request for an interchange acknowledgment 0 No Acknowledgment
Requested |
M |
ID |
1/1 |
|
ISA15 |
I14 |
Usage Indicator Code indicating whether
data enclosed by this interchange envelope is test or production T Test Data P Production Data |
M |
ID |
1/1 |
|
ISA16 |
I15 |
Sub-element Separator > |
M |
|
1/1 |
GSTRANSACTION SET HEADER Segment: GS Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning
of a functional group and to provide control information
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
GS01 |
479 |
Functional Identifier
Code Code identifying a
group of application related transaction sets IN Invoice (810) PD Product Activity Data
(852) SH Advanced Ship Notice
(856) |
M |
ID |
2/2 |
|
GS02 |
142 |
Application Sender ID Code identifying party
sending transmission 9417472355 Test ID for Beall’s 8137472355 Production ID for
Beall’s |
M |
AN |
2/15 |
|
GS03 |
124 |
Application Receiver ID Code identifying party
receiving transmission |
M |
AN |
2/15 |
|
GS04 |
373 |
Date Date expressed as
CCYYMMDD |
M |
DT |
8/8 |
|
GS05 |
337 |
Time Time expressed in 24
hour clock time: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD |
M |
TM |
4/8 |
|
GS06 |
28 |
Group Control Number Assigned number originated
and maintained by the sender |
M |
N0 |
1/9 |
|
GS07 |
455 |
Responsible Agency Code Code identifying the
issuer of the standard X X12 |
M |
ID |
1/2 |
|
GS08 |
480 |
Version Code indicating version
004010VICS, 004030VICS |
M |
AN |
1/12 |
GETRANSACTION SET HEADER Segment: GE Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of a
functional group and to provide control information
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
GE01 |
97 |
Number of Transaction
Sets Included Number of ST segments
within the group |
M |
N0 |
1/6 |
|
GE02 |
28 |
Group Control Number Must be the same number
value as is in the GS06 for the group |
M |
N0 |
1/9 |
IEATRANSACTION SET HEADER Segment: IEA Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To define the end of an
interchange of zero or more functional groups and interchange-related control segments
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
IEA01 |
I16 |
Number of Included
Functional Groups Number of GS segments
within the group |
M |
N0 |
1/5 |
|
IEA02 |
I12 |
Interchange Control
Number Must be the same number
value as is in the ISA13 for the transmission |
M |
N0 |
9/9 |
Bealls EDI 850 Purchase
Order will be sent in version 4010 or 4030.
It will be transmitted the day after the order has been updated in
Bealls system at approximately 6:15am, Monday through Saturday.
Bealls may transmit
pre-distributed or post-distributed orders.
The SLN is enabled to communicate by UPC the quantity to ship in a pack
(a pack may be an inner-pack within a master carton or a carton).
The following scenarios
describe the possible format of the 850:
Pre-distributed (shipped to
Vendor to pack-by/mark-for each store
A pre-distributed order may
be changed to be post-distributed.
Post-distributed (shipped to
Bealls to distribute to stores after
goods are received in
An EDI 997 Functional
Acknowledgment is expected from vendors for all documents sent by Bealls.
Order changes are
communicated via the EDI 850 (Bealls does not transmit the EDI 860) after
Bealls receives a signed “PO Changes – Request to RE-EDI” form from a vendor.
Header
|
SEG. ID |
NAME |
REQ. DES. |
MAX USE |
|
|
ST |
Transaction Set Header |
M |
1 |
|
|
BEG |
Beginning Segment for
Purchase Order |
M |
1 |
|
|
REF |
Reference
Identification |
M |
2 |
|
|
FOB |
F.O.B. Related
Instructions |
M |
4 |
|
|
|
7 |
|||
|
SAC |
Service, Promotion,
Allowance, or Charge Information |
M |
>1 |
|
|
ITD |
Terms of |
M |
1 |
|
|
DTM |
Date/Time Reference |
M |
2 |
|
|
TD5 |
Carrier Details
(Routing Sequence/Transit Time) |
M |
1 |
|
|
|
5 |
|||
|
N1 |
Name |
O |
1 |
|
|
N3 |
Address Information |
O |
1 |
|
|
N4 |
Geographic Location |
O |
1 |
|
Detail
|
|
9999 |
|||
|
PO1 |
Item Identification |
M |
1 |
|
|
|
2 |
|||
|
CTP |
Pricing Information |
M |
2 |
|
|
|
7 |
|||
|
PID |
Product/Item
Description |
M |
>1 |
|
|
PO4 |
Item Physical Details |
O |
1 |
|
|
SDQ |
Destination Quantity |
O |
8 |
|
|
TC2 |
Commodity |
O |
3 |
|
|
|
60 |
|||
|
SLN |
Item Identification |
O |
1 |
|
Summary
|
CTT |
Transaction Totals |
M |
1 |
|
|
SE |
Transaction Set Trailer |
M |
1 |
|
Header
STTRANSACTION SET HEADER Segment: ST Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of
a transaction set and to assign a control number
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ST01 |
143 |
Transaction Set
Identifier Code Code uniquely
identifying a Transaction Set 850 Purchase Order |
M |
ID |
3/3 |
|
ST02 |
329 |
Transaction Set Control
Number Identifying control
number that must be unique within the transaction set functional group
assigned by the originator for a transaction set |
M |
AN |
4/9 |
RXEQPORTING DATE/ACTION Segment: BEG Beginning Segment for
Purchase Order
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning
of the Purchase Order Transaction Set and transmit identifying numbers and
dates
105 Notes: If BEG02 contains
code RL, then BEG04 is required. BEG03 contains the blanket purchase order
number which is being released against and BEG04 contains the release number.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
BEG01 |
353 |
Transaction Set Purpose
Code Code identifying
purpose of transaction set 00 Original 07 Duplicate |
M |
ID |
2/2 |
|
BEG02 |
92 |
Purchase Order Type
Code Code specifying the
type of Purchase Order BK Blanket Order, for
future delivery of a pre-distributed order only RL Release Order, that
will exhaust all units from the Blanket Order SA Stand-alone Order, for
immediate delivery that may be pre/post-distributed |
M |
ID |
2/2 |
|
BEG03 |
324 |
Purchase Order Number Identifying number for
Purchase Order assigned by Bealls, the original 7 character Purchase Order
number that always starts with a zero |
M |
AN |
7/7 |
|
BEG04 |
328 |
Release Number Number identifying a
release against a Purchase Order previously placed by Bealls. Since Bealls exhausts all units from the
Blanket Order in one Release Order, the value sent in BEG04 is always 1 if
the value in the BEG02 is RL |
O |
AN |
1/1 |
|
BEG05 |
373 |
Date Date expressed as
CCYYMMDD, Bealls original Purchase Order date |
M |
DT |
8/8 |
RNE9FERENCE IDENTIFICATION Segment: REF Reference Identification
Usage: Mandatory
Max Use: 2
Purpose: To transmit identifying
information as specified by the Reference Identification Qualifier
105 Notes: Bealls transmits
at a minimum one REF segment with Bealls Department Number.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
REF01 |
128 |
Reference
Identification Qualifier Code qualifying the
Reference Identification DP Bealls assigned
department number PD Bealls assigned
promotion number |
M |
ID |
2/2 |
|
REF02 |
127 |
Reference
Identification Bealls assigned 3
character numeric department number, or Bealls assigned promotion date formatted
as YYMMDD for a Purchase Order that has been ad-dated at the header level
only |
C |
AN |
3/6 |
RNE9FERENCE IDENTIFICATION Segment: FOB F.O.B Related
Instructions
Usage: Mandatory
Max Use: 4
Purpose: To specify transportation
instructions relating to shipment
105 Notes: For domestic
orders, Bealls will always transmit at a minimum 1 FOB segment with AC in the
FOB02 and either the city and state shipping point or SEE GUIDE, referring to
Bealls Routing Guide online at http://www.beallsinc.com/vendorrelations/default.asp. For import orders, Bealls will transmit up to
4 FOB segments specifying freight forwarder, country of origin, factory name,
and origin shipping point in that sequence.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
FOB01 |
146 |
Shipment Method of
Payment Code identifying
payment terms for transportation charges DF Defined by Bealls and
Vendor PP Prepaid by Vendor |
M |
ID |
2/2 |
|
FOB02 |
309 |
Location Qualifier Code identifying type
of location AC City and State, for
domestic orders only FF Freight Forwarder, for
import orders only CA Country of Origin, for
import orders only FA Factory, for import
orders only OR Origin (Shipping Point)
, for import orders only |
C |
ID |
2/2 |
|
FOB03 |
352 |
Description For domestic orders,
Vendor’s City and State shipping point, or the literal SEE GUIDE. For import orders,
Freight Forwarder, Country of Origin, Factory Name, and/or the Origin
Shipping Point in that sequence. |
O |
AN |
1/80 |
RNE9FERENCE IDENTIFICATION Segment: SAC Service, Promotion, Allowance,
or Charge Information
Usage: Mandatory
Max Use: 7
Purpose: To request or identify a
service, promotion, allowance, or charge; to specify the amount or percentage
for the service, promotion, allowance, or charge
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SAC01 |
248 |
Allowance or Charge
Indicator Code which indicates an
allowance or charge for the service specified A Allowance N No Allowance or Charge |
M |
ID |
1/1 |
|
SAC02 |
1300 |
Service, Promotion,
Allowance, or Charge Code Code identifying the
service, promotion, allowance, or charge COOO Defective Allowance B720 Co-op Allowance C310 Discount (percent off
invoice) C350 Distribution Allowance D240 Freight (discount off
cost), or Prepaid Freight E170 Labeling I000 Testing |
C |
ID |
4/4 |
|
SAC03 |
559 |
Agency Qualifier Code Code identifying the
agency assigning the code values VI Voluntary
Inter-Industry Commerce Standard (VICS) EDI |
C |
ID |
2/2 |
|
SAC04 |
1301 |
Agency Service,
Promotion, Allowance, or Charge Code Agency maintained code
identifying the service, promotion, allowance, or charge TC09 Ticketing Service as
agreed to by Trading Partners HA Hanger Service E170 Labeling |
C |
AN |
1/10 |
|
SAC05 |
610 |
Amount Monetary amount When SAC01 contains
code A, then this data element is sent. |
O |
N2 |
1/15 |
|
SAC06 |
378 |
Allowance/Charge
Percent Qualifier Code indicating on what
basis allowance or charge percent is calculated 3 Discount 6 Base Price Amount |
C |
ID |
1/1 |
|
SAC07 |
332 |
Percent Percent expressed as a
percent The percent is sent
with a decimal point only when needed, e.g., 10.5% is sent as 10.5, and 2% is
sent as 2 |
C |
R |
1/6 |
|
SAC12 |
331 |
Allowance or Charge
Method of Handling Code Code indicating method
of handling for an allowance or charge 02 Off Invoice 05 Charge to be Paid by
Vendor |
O |
ID |
2/2 |
|
SAC15 |
352 |
Description A free-form description
to clarify the related data elements and their content |
O |
AN |
1/80 |
RXEQPORTING DATE/ACTION Segment: ITD Terms of
Usage: Mandatory
Max Use: 1
Purpose: To specify terms of sale
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ITD01 |
336 |
Terms Type Code Code identifying type
of payment terms 05 Discount Not Applicable 12 10 Days After End of
Month 14 Previously agreed upon |
M |
ID |
2/2 |
|
ITD02 |
333 |
Terms Basis Date Code Code identifying the
beginning of the terms period 3 Invoice Date 15 Receipt of Goods |
O |
ID |
1/2 |
|
ITD03 |
338 |
Terms Discount Percent Terms discount
percentage, expressed as a percent, available to the purchaser if an invoice
is paid on or before the Terms Discount Due Date The percent is sent
with a decimal point only when needed, e.g., 10.5% is sent as 10.5, and 2% is
sent as 2 |
O |
R |
1/6 |
|
ITD07 |
386 |
Terms Net Days Number of days until
total invoice amount is due (discount not applicable) |
O |
N0 |
1/3 |
|
ITD12 |
373 |
Description A free-form description
to clarify the related data elements and their content |
M |
AN |
1/80 |
RXEQPORTING DATE/ACTION Segment: DTM Date/Time Reference
Usage: Mandatory
Max Use: 2
Purpose: To specify pertinent
dates and times
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
DTM01 |
374 |
Date/Time Qualifier Code specifying type of
date 001 Cancel After 010 Requested Ship |
M |
ID |
3/3 |
|
DTM02 |
373 |
Date Date expressed as
CCYYMMDD, Bealls requested ship / cancel date |
C |
DT |
8/8 |
RXEQPORTING DATE/ACTION Segment: TD5 Carrier Details (Routing
Sequence/Transit Time)
Usage: Mandatory
Max Use: 1
Purpose: To specify routing
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
TD505 |
387 |
Routing Free-form description
of the routing Store Xdock PO-See
Guide, or Simple Casepack PO-See
Guide, or Direct to Store PO-See
Guide, or Bulk PO-See Guide |
M |
AN |
1/35 |
RXEQPORTING DATE/ACTION Segment: N1 Name
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by
type of organization, name, and code
105 Notes: For direct to
store orders, Bealls will not transmit this segment.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N101 |
98 |
Entity Identifier Code Code identifying an
organizational entity, a physical location, property or an individual AG Agent, for Bealls
Imports Inc orders only BY Buyer, for Bealls
Imports Inc orders only MF Factory, for Bealls
Imports Inc orders only SE Seller, for Bealls
Imports Inc orders only ST Ship to |
M |
ID |
2/3 |
|
N102 |
93 |
Name Free-form name |
O |
AN |
3/3 |
|
N103 |
66 |
Identification Code
Qualifier Code designating the
system/method of code structure used for Identification Code (67) 92 Assigned by Buyer, when
N101 is ST, or 1 DUNS#, when N101 is SE
for Bealls Imports Inc orders only; otherwise, not sent |
M |
ID |
2/2 |
|
N104 |
67 |
Identification Code Code identifying a
party or other code 050 Bealls DC ID, when N101
is ST, or Vendor’s DUNS# Bealls for Bealls Imports Inc orders only; otherwise, not sent |
M |
AN |
3/3 |
RXEQPORTING DATE/ACTION Segment: N3 Address Information
Usage: Optional
Max Use: 1
Purpose: To specify the location
of the named party
105 Notes: Bealls will
transmit this segment for Bealls Import orders only.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N301 |
166 |
Address Information |
M |
ID |
1/30 |
|
N302 |
166 |
Address Information |
O |
ID |
1/30 |
RXEQPORTING DATE/ACTION Segment: N4 Name
Usage: Optional
Max Use: 1
Purpose: To specify the geographic
place of the named party
105 Notes: Bealls will
transmit this segment for Bealls Import orders only.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N401 |
19 |
City Name |
M |
AN |
2/30 |
|
N402 |
156 |
State or Province Code |
O |
ID |
2/2 |
|
N403 |
116 |
Postal Code |
O |
ID |
3/15 |
|
N404 |
26 |
Country Code |
M |
ID |
2/3 |
Detail
ILTINEM IDENTIFICATION Segment: PO1 Baseline Item Data
Usage: Mandatory
Purpose: To specify basic and most
frequently used line item data
105 Notes: The multi-SKU case
pack is used to order cases packed with specific items, each with a specific
quantity. PO103 will contain code CA,
and no Product/Service ID in the PO1 segment is sent. The use of code CA in
PO103 and the presence of the SLN segments implies goods should be packed in a
case with the SKUs and quantities in the SLN segments. The quantity in PO102 is the number of cases
being ordered. Each SLN segment, that
follows the PO1 segment, lists the Product ID, e.g., U.P.C., and the quantity
of the SKU that is to be in the case. The
total units in each case is the sum of the quantities in the SLN segment.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
PO101 |
350 |
Assigned Identification Alphanumeric characters
assigned for differentiation within a transaction set |
M |
AN |
1/3 |
|
PO102 |
330 |
Quantity Ordered Quantity ordered |
M |
R |
1/15 |
|
PO103 |
355 |
Unit or Basis for
Measurement Code Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken EA Each CA Cases when SLN is sent |
M |
ID |
2/2 |
|
PO104 |
212 |
Unit Price Cost per unit of
product when the SLN is not sent; when the SLN is sent the cost is in the
SLN06 |
C |
R |
1/17 |
|
PO105 |
639 |
Basis of Unit Price
Code Code identifying the
type of unit price for an item WE Wholesale price per
each when the SLN is not sent |
C |
ID |
2/2 |
|
PO106 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) UP UPC (1-5-5-1) VA Vendor Style Number
when SLN is sent |
C |
ID |
2/2 |
|
PO107 |
234 |
Product/Service ID UPC or Vendor Style
Number |
C |
AN |
1/12 |
|
PO108 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) VA Vendor Style Number |
C |
ID |
2/2 |
|
PO109 |
234 |
Product/Service ID Vendor Style Number |
C |
AN |
1/12 |
|
PO110 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) CB Bealls assigned SKU |
C |
ID |
2/2 |
|
PO111 |
234 |
Product/Service ID Bealls assigned SKU |
C |
AN |
1/12 |
|
PO112 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) VE Vendor color |
C |
ID |
2/2 |
|
PO113 |
234 |
Product/Service ID Vendor color
description |
C |
AN |
1/12 |
RXEQPORTING DATE/ACTION Segment: CTP Pricing Information
Usage: Mandatory
Max Use: 2
Purpose: To specify pricing
information
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
CTP01 |
687 |
Class of Trade Code Code indicating class
of trade RS Resale |
M |
ID |
2/2 |
|
CTP02 |
236 |
Price Identifier Code Code identifying
pricing specification RES Retail price ALT Multi-price FCP First cost price |
M |
ID |
3/3 |
|
CTP03 |
212 |
Unit Price Retail price per unit
in first occurrence of the CTP; Retail price for multiple units; First Cost for
Bealls Import orders only |
M |
R |
1/17 |
|
CTP04 |
380 |
Quantity Quantity, sent for
Retail price only |
C |
R |
1/15 |
|
CTP05 |
C001 |
Composite Unit of
Measurement Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken EA Each CA Cases when SLN is sent |
C |
ID |
2/2 |
|
CTP11 |
380 |
Multiple Price Quantity Quantity of units for a
given price, i.e. 3 for $12.00 |
C |
R |
1/15 |
RXEQPORTING DATE/ACTION Segment: PID Product/Item Description
Usage: Mandatory
Max Use: 7
Purpose: To describe a product in
free-form format
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
PID01 |
349 |
Item Description Type Code indicating the
format of a description F Free-form |
M |
ID |
1/1 |
|
PID02 |
750 |
Product/Process
Characteristic Code Code identifying the
general class of a product or process characteristic 08 Product description 73 Vendor color
description 74 Vendor size description 91 Buyer’s item size
description BND Buyer’s label
description for Bealls Imports Inc orders only GEN Buyer’s item description
for Bealls Imports Inc orders only ZZ Buyer’s packing
requirement description for Bealls Imports Inc orders only |
M |
ID |
2/2 |
|
PID05 |
352 |
Description A free-form description
to clarify the related data elements and their content |
M |
AN |
1/80 |
RXEQPORTING DATE/ACTION Segment: PO4 Item Physical Details
Usage: Optional
Max Use: 1
Purpose: To specify the physical
qualities, packaging, weights, and dimensions relating to an item
105 Notes: Bealls will
transmit this segment for Bealls Import orders only.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
PO401 |
356 |
Pack The number of inner packs,
or the number of units when there are no inner packs per carton |
M |
N0 |
1/3 |
|
PO414 |
750 |
Inner Pack The number of units per
inner pack |
O |
N0 |
1/3 |
SDDEQSTINATION QUANTITY Segment: SDQ Destination Quantity
Usage: Optional
Max Use: 8
Purpose: To specify destination
and quantity detail
431 Notes: This segment is
used to distribute item quantity to various locations.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SDQ01 |
355 |
Unit or Basis for
Measurement Code Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken |
M |
ID |
2/2 |
|
SDQ02 |
66 |
Identification Code
Qualifier Code designating the
system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or
Buyer’s Agent |
M |
ID |
1/2 |
|
SDQ03 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ04 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ05 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ06 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ07 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ08 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ09 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ10 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ11 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ12 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ13 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ14 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ15 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ16 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ17 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ18 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ19 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ20 |
380 |
Quantity |
M |
R |
1/15 |
|
SDQ21 |
67 |
Identification Code Code identifying
Beall’s Store Number |
M |
AN |
2/80 |
|
SDQ22 |
380 |
Quantity |
M |
R |
1/15 |
RXEQPORTING DATE/ACTION Segment: TC2 Commodity
Usage: Optional
Max Use: 3
Purpose: To identify a commodity
or a group of commodities or a tariff page commodity
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
TC201 |
23 |
Commodity Code
Qualifier Code identifying the
commodity coding system used for Commodity Code J Harmonized System-Based
Schedule B |
M |
ID |
1/1 |
|
TC202 |
22 |
Commodity Code Code describing a
commodity or group of commodities |
M |
ID |
1/30 |
ILTINEM IDENTIFICATION Segment: SLN Subline Item Detail
Usage: Optional
Purpose: To specify product
subline detail item data
105 Notes: The multi-SKU case
pack is used to order cases packed with specific items, each with a specific
quantity. PO103 will contain code CA,
and no Product/Service ID in the PO1 segment is sent. The use of code CA in
PO103 and the presence of the SLN segments implies goods should be packed in a
case with the SKUs and quantities in the SLN segments. The quantity in PO102 is the number of cases
being ordered. Each SLN segment, that
follows the PO1 segment, lists the Product ID, e.g., U.P.C., and the quantity
of the SKU that is to be in the case. The
total units in each case is the sum of the quantities in the SLN segment.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SLN01 |
350 |
Assigned Identification Alphanumeric characters
assigned for differentiation within a transaction set |
M |
AN |
1/3 |
|
SLN03 |
662 |
Relationship Code Code indicating the
relationship between entities I Included |
M |
ID |
1/1 |
|
SLN04 |
380 |
Quantity Quantity per case |
M |
R |
1/15 |
|
SLN05 |
C001 |
Composite Unit of
Measurement Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken EA Each |
C |
ID |
2/2 |
|
SLN06 |
212 |
Unit Price Cost per unit of
product |
C |
R |
1/17 |
|
SLN09 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) UP UPC (1-5-5-1) |
C |
ID |
2/2 |
|
SLN10 |
234 |
Product/Service ID UPC |
C |
AN |
1/12 |
|
SLN11 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) SZ Vendor Alphanumeric
Size Code |
C |
ID |
2/2 |
|
SLN12 |
234 |
Product/Service ID Vendor Alphanumeric
Size Description |
C |
AN |
1/12 |
Summary
RXEQPORTING DATE/ACTION Segment: CTT Transaction Totals
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total
for a specific element in the transaction set
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
CTT01 |
354 |
Number of Line Items Total number of line
items in the transaction set The number of PO1 segments present in the
transaction set |
M |
ID |
1/1 |
STERANSACTION SET TRAILER Segment: SE Transaction Set Trailer
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of
the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments)
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SE01 |
96 |
Number of Included
Segments Total number of
segments included in a transaction set including ST and SE segments |
M |
N0 |
1/10 |
|
SE02 |
329 |
Transaction Set Control
Number Identifying control
number that must be unique within the transaction set functional group assigned
by the originator for a transaction set 9 This will be the same
number as is in the ST segment (ST02) for the transaction set. |
M |
AN |
4/9 |
Generic, sample EDI 850 data
Domestic,
future, pre-distributed
Store Cross-dock
1
ST*850*000000001
2
BEG*00*BK*0488351**20090624
3
REF*DP*701
4
FOB*DF*AC*SEE GUIDE
5
SAC*N**VI*TC09***********Ticketing Service
6
ITD*05*15*****30*****NET 30
7
DTM*001*20090930
8
DTM*010*20090915
9
TD5*****Simple Casepack PO-See Guide
10 N1*ST*050*92*050
11
PO1*001*20*CA***VA*123456
12
CTP*RS*RES*9.99*20*EA
13
PID*F*08***BLACK NOTHING
14
PID*F*73***WHITE
15
PID*F*75***WHITE
16
SLN*001**I*2*EA*5***UP*123456545663
17
SLN*001**I*2*EA*5***UP*123456545779
18
SLN*001**I*2*EA*5***UP*123456545878
19
CTT*1
20
SE*20*000000001
1
ST*850*000000001
2
BEG*07*RL*0488351*1*20090624
3
REF*DP*701
4
FOB*DF*AC*SEE GUIDE
5
SAC*N**VI*TC09***********Ticketing Service
6
ITD*05*15*****30*****NET 30
7
DTM*001*20090930
8
DTM*010*20090704
9
TD5*****Store Xdock PO-See Guide
10
N1*ST**92*050
11
PO1*001*40*EA*5*WE*UP*123456545663*VA*123456*CB*84351431*VE*WHITE
12
CTP*RS*RES*9.99*40*EA
13
PID*F*08***BLACK NOTHING
14
PID*F*73***WHITE
15
PID*F*75***WHITE
16
PID*F*91***001
17
SDQ*EA*92*012*2*015*2*018*2*021*2*024*2*030*2*036*2*043*2*051*2*053*2
18
SDQ*EA*92*057*2*060*2*061*2*066*2*067*2*070*2*075*2*078*2*084*2*099*2
19
PO1*002*40*EA*5*WE*UP*123456545779*VA*123456*CB*84351444*VE*WHITE
20
CTP*RS*RES*9.99*40*EA
21
PID*F*08***BLACK NOTHING
22
PID*F*73***WHITE
23
PID*F*75***WHITE
24
PID*F*91***002
25
SDQ*EA*92*012*2*015*2*018*2*021*2*024*2*030*2*036*2*043*2*051*2*053*2
26
SDQ*EA*92*057*2*060*2*061*2*066*2*067*2*070*2*075*2*078*2*084*2*099*2
27
PO1*003*40*EA*5*WE*UP*123456545878*VA*123456*CB*84351456*VE*WHITE
28
CTP*RS*RES*9.99*40*EA
29
PID*F*08***BLACK NOTHING
30
PID*F*73***WHITE
31
PID*F*75***WHITE
32
PID*F*91***003
33
SDQ*EA*92*012*2*015*2*018*2*021*2*024*2*030*2*036*2*043*2*051*2*053*2
34
SDQ*EA*92*057*2*060*2*061*2*066*2*067*2*070*2*075*2*078*2*084*2*099*2
35
CTT*3
36
SE*36*000000001
Domestic,
immediate, pre-distributed
Store Cross-dock
1 ST*850*000000001
2
BEG*07*SA*0461243**20090601
3
REF*DP*701
4
FOB*DF*AC*SEE GUIDE
5
SAC*N**VI*TC09***********Ticketing Service
6
ITD*05*15*****30*****NET 30
7
DTM*001*20090630
8
DTM*010*20090612
9
TD5*****Store Xdock PO-See Guide
10
N1*ST**92*050
11
PO1*001*60*EA*0.01*WE*UP*123123132127*VA*1*CB*83482678*VE*1
12
CTP*RS*RES*0.02*60*EA
13
PID*F*08***1
14
PID*F*73***1
15
PID*F*75***BLACK
16
PID*F*91***101
17
SDQ*EA*92*001*6*009*6*012*6*014*6*041*6*061*6*062*6*081*6*088*6*734*6
18
CTT*1
19
SE*19*000000001
Domestic,
future or immediate, post-distributed
Simple Case-pack
1
ST*850*000000001
2
BEG*00*SA*0483770**20090623
3
REF*DP*701
4
FOB*DF*AC*SEE GUIDE
5
SAC*N**VI*TC09***********Ticketing Service
6
ITD*05*15**********NET
7
DTM*001*20090616
8
DTM*010*20090615
9
TD5*****Simple Casepack PO-See Guide
10
N1*ST**92*050
11
PO1*001*80*CA***VA*1
12
CTP*RS*RES*0.02*80*EA
13
PID*F*08***1
14
PID*F*73***1
15
PID*F*75***WHITE
16
PID*F*91***101
17
SLN*001**I*1*EA*0.01***UP*111111111117
18
SLN*001**I*1*EA*0.01***UP*222222222224
19
CTT*1
20
SE*20*000000001
Bulk
1
ST*850*000000001
2
BEG*07*SA*0461243**20090624
3
REF*DP*701
4
FOB*DF*AC*SEE GUIDE
5
SAC*N**VI*TC09***********Ticketing Service
6
ITD*05*15*****30*****NET 30
7
DTM*001*20090630
8
DTM*010*20090602
9
TD5*****Bulk PO-See Guide
10
N1*ST**92*050
11
PO1*001*42*EA*0.01*WE*UP*123123132127*VA*BEALLSSTYL*CB*83482678*VE*BLACK
12
CTP*RS*RES*0.02*42*EA
13
PID*F*08***ANOTHER STYLE
14
PID*F*73***BLACK
15
PID*F*75***BLACK
16
PID*F*91***101
17
SDQ*EA*92*050*42
18
CTT*1
19
SE*19*000000001
Import,
future or immediate, post-distributed
1
ST*850*000000001
2
BEG*07*SA*0461084**20090603
3
REF*DP*702
4
REF*PD*090901
5
FOB*DF*FF*Expeditors International of Washington, Inc.
6
FOB*DF*CA*
7
FOB*DF*FA*Z
8
SAC*N**VI*TC09***********Ticketing Service
9
SAC*N*E170*VI*E170***********PAXAR .
10
SAC*N*I000*************Per Bealls Private Brand Testing Requirements:
see Beallsinc.com
11
ITD*05*15*****30*****NET 30
12
DTM*001*20090630
13
DTM*010*20090615
14
DTM*015*20090901
15
N1*ST**92*050
16
PO1*001*100*EA*0.04*WE*UP*123123123323*VA*2*CB*83485865*VE*2
17
CTP*RS*RES*0.08*100*EA
18
CTP*RS*ALT*0.02
19
PID*F*08***2
20
PID*F*73***2
21
PID*F*75***WHITE
22
PID*F*91***SMALL
23
SDQ*EA*92*001*100
24
CTT*1
25
SE*25*000000001
EDI 810 (Invoice) must
contain a valid Beall’s Purchase Order number in order to match the invoice for
payment.
Beall’s must receive a
separate individual invoice for each store per Purchase Order. Consolidated Invoices cannot be accepted at
this time. Purchase Orders should be
billed in eaches (by UPC).
In the event that the
vendor’s invoice errors out of the Beall’s
It is mandatory to list the
correct Bill of Lading (BOL) number within the EDI transmission. The BOL ties directly with the 856 Advance
Ship Notice. With the correct
information, invoices can be processed more swiftly and accurately.
Deviation from the below EDI
810 (Invoice) format may impact our ability to expedite payment in a timely
fashion.
Note: Functional Acknowledgments will be sent for all
documents transmitted to Beall’s by vendors
Header
|
SEG. ID |
NAME |
REQ. DES. |
MAX USE |
|
|
ST |
Transaction Set Header |
M |
1 |
|
|
BIG |
Beginning Segment for Invoice |
M |
1 |
|
|
REF |
Reference
Identification |
M |
1 |
|
|
|
4 |
|||
|
N1 |
Name |
M |
1 |
|
|
N2 |
Additional Name Information |
O |
1 |
|
|
N3 |
Address Information |
O |
1 |
|
|
N4 |
Geographic Location |
O |
1 |
|
|
ITD |
Terms of |
O |
1 |
|
|
DTM |
Date/Time Reference |
O |
2 |
|
|
FOB |
F.O.B. Related
Instructions |
O |
1 |
|
Detail
|
|
9999 |
|||
|
IT1 |
Baseline Item Data |
M |
1 |
|
|
|
3 |
|||
|
PID |
Product/Item
Description |
O |
>1 |
|
Summary
|
TDS |
Total Monetary Value
Summary |
M |
>1 |
|
|
CAD |
Carrier Detail |
M |
>1 |
|
|
|
1 |
|||
|
SAC |
Service, Promotion,
Allowance, or Charge Information |
O |
1 |
|
|
ISS |
Invoice Shipment
Summary |
M |
1 |
|
|
CTT |
Transaction Totals |
M |
1 |
|
|
SE |
Transaction Set Trailer |
M |
1 |
|
Header
STTRANSACTION SET HEADER Segment: ST Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of
a transaction set and to assign a control number
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ST01 |
143 |
Transaction Set
Identifier Code Code uniquely
identifying a Transaction Set 810 Invoice |
M |
ID |
3/3 |
|
ST02 |
329 |
Transaction Set Control
Number Identifying control
number that must be unique within the transaction set functional group
assigned by the originator for a transaction set |
M |
AN |
4/9 |
RXEQPORTING DATE/ACTION Segment: BIG Beginning Segment for Invoice
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning
of invoice transaction set and transmit identifying numbers and dates
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
BIG01 |
373 |
Invoice Date Date expressed as
CCYYMMDD |
M |
DT |
8/8 |
|
BIG02 |
76 |
Invoice Number Identifying number
assigned by issuer |
M |
AN |
1/10 |
|
BIG04 |
324 |
Purchase Order Number Identifying number for
Purchase Order assigned by Bealls, the original 7 character Purchase Order
number that always starts with a zero |
M |
AN |
7/7 |
|
BIG08 |
353 |
Transaction Set Purpose
Code Code identifying
purpose of transaction set 00 Original |
M |
ID |
2/2 |
RNE9FERENCE IDENTIFICATION Segment: REF Reference Identification
Usage: Mandatory
Max Use: 1
Purpose: To specify identifying
information
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
REF01 |
128 |
Reference
Identification Qualifier Code qualifying the
Reference Identification DP Bealls assigned
department number |
M |
ID |
2/2 |
|
REF02 |
127 |
Reference
Identification Bealls assigned 3
character numeric department number |
C |
AN |
3/6 |
RXEQPORTING DATE/ACTION Segment: N1 Name
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by
type of organization, name, and code
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N101 |
98 |
Entity Identifier Code Code identifying an
organizational entity, a physical location, property or an individual BY Buying Party, Bealls
Store Number SF Ship from RI Remit-to ST Ship to, |
M |
ID |
2/3 |
|
N102 |
93 |
Name Free-form name |
O |
AN |
3/3 |
|
N103 |
66 |
Identification Code
Qualifier Code designating the
system/method of code structure used for Identification Code (67) 92 Assigned by Buyer, when
N101 is BY or ST, or 1 DUNS#, when N101 is RI
or SF |
M |
ID |
2/2 |
|
N104 |
67 |
Identification Code Code identifying a
party or other code 050 Bealls DC ID, when N101 is ST and goods shipped to When N101 is BY and order is pre-distributed, Bealls 3-character
Store Number, otherwise Bealls DC ID When N101 is SF, Vendor’s DUNS# When N101 is RI and remit directly to the vendor, Vendor’s DUNS#;
otherwise, Bealls
Factor Number for factor payment |
M |
AN |
3/3 |
|
N106 |
98 |
Entity Identifier Code Factor Code, for factor
payments only O4 Factor |
O |
ID |
2/3 |
RXEQPORTING DATE/ACTION Segment: N2 Additional Name Information
Usage: Optional
Max Use: 1
Purpose: To specify additional
names or those longer than 35 characters in length
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N201 |
93 |
Name |
M |
AN |
1/30 |
|
N202 |
93 |
Name |
O |
AN |
1/30 |
RXEQPORTING DATE/ACTION Segment: N3 Address Information
Usage: Optional
Max Use: 1
Purpose: To specify the location
of the named party
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N301 |
166 |
Address Information |
M |
ID |
1/30 |
|
N302 |
166 |
Address Information |
O |
ID |
1/30 |
RXEQPORTING DATE/ACTION Segment: N4 Name
Usage: Optional
Max Use: 1
Purpose: To specify the geographic
place of the named party
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N401 |
19 |
City Name |
O |
AN |
2/30 |
|
N402 |
156 |
State or Province Code |
O |
ID |
2/2 |
|
N403 |
116 |
Postal Code |
O |
ID |
3/15 |
|
N404 |
26 |
Country Code |
M |
ID |
2/3 |
RXEQPORTING DATE/ACTION Segment: ITD Terms of
Usage: Mandatory
Max Use: 1
Purpose: To specify terms of sale
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ITD01 |
336 |
Terms Type Code Code identifying type
of payment terms 14 Previously agreed upon |
M |
ID |
2/2 |
|
ITD02 |
333 |
Terms Basis Date Code Code identifying the
beginning of the terms period 3 Invoice Date 15 Receipt of Goods |
O |
ID |
1/2 |
|
ITD12 |
373 |
Description A free-form description
to clarify the related data elements and their content |
O |
AN |
1/80 |
|
ITD14 |
107 |
Payment Method Code A free-form description
to clarify the related data elements and their content C Pay by Check L Letter of Credit T Wire Transfer |
O |
ID |
1/2 |
RXEQPORTING DATE/ACTION Segment: DTM Date/Time Reference
Usage: Optional
Max Use: 2
Purpose: To specify pertinent
dates and times
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
DTM01 |
374 |
Date/Time Qualifier Code specifying type of
date 001 Cancel After 010 Requested Ship |
M |
ID |
3/3 |
|
DTM02 |
373 |
Date Date expressed as
CCYYMMDD, Bealls requested ship / cancel date |
C |
DT |
8/8 |
RNE9FERENCE IDENTIFICATION Segment: FOB F.O.B Related
Instructions
Usage: Optional
Max Use: 1
Purpose: To specify transportation
instructions relating to shipment
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
FOB01 |
146 |
Shipment Method of
Payment Code identifying payment
terms for transportation charges CC Collect DF Defined by Bealls and
Vendor PP Prepaid by Vendor |
M |
ID |
2/2 |
|
FOB02 |
309 |
Location Qualifier Code identifying type
of location DE Destination FA Factory |
C |
ID |
2/2 |
Detail
ILTINEM IDENTIFICATION Segment: IT1 Baseline Item Data
Usage: Mandatory
Purpose: To specify basic and most
frequently used line item data
105 Notes: Items must be
billed in eaches by UPC.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
IT102 |
358 |
Quantity Invoiced Quantity ordered as a
whole number only, decimal values will not post to Bealls A/P system |
M |
N0 |
1/15 |
|
IT103 |
355 |
Unit or Basis for
Measurement Code Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken EA Each |
M |
ID |
2/2 |
|
IT104 |
212 |
Unit Price Cost per unit of
product when the SLN is not sent; when the SLN is sent the cost is in the
SLN06 |
C |
R |
1/17 |
|
IT106 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) UP UPC (1-5-5-1) |
C |
ID |
2/2 |
|
IT107 |
234 |
Product/Service ID UPC or Vendor Style
Number |
C |
AN |
1/12 |
RXEQPORTING DATE/ACTION Segment: PID Product/Item Description
Usage: Optional
Max Use: 3
Purpose: To describe a product in
free-form format
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
PID01 |
349 |
Item Description Type Code indicating the
format of a description F Free-form |
M |
ID |
1/1 |
|
PID02 |
750 |
Product/Process
Characteristic Code Code identifying the
general class of a product or process characteristic 08 Product description, or
for Bealls Import orders, packing requirement, item description, and label
description 73 Vendor color
description 74 Vendor size description |
M |
ID |
2/2 |
|
PID05 |
352 |
Description A free-form description
to clarify the related data elements and their content |
M |
AN |
1/80 |
Summary
RXEQPORTING DATE/ACTION Segment: TDS Total Monetary Value
Summary
Usage: Mandatory
Max Use: 1
Purpose: To specify the total
invoice amount
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
TDS01 |
610 |
Amount Total invoice amount |
M |
N2 |
1/15 |
RXEQPORTING DATE/ACTION Segment: CAD Carrier Detail
Usage: Mandatory
Max Use: 1
Purpose: To specify transportation
details for the transaction set
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
CAD04 |
140 |
SCAC |
M |
ID |
2/4 |
|
CAD05 |
387 |
Routing Free form description
of routing |
M |
AN |
1/35 |
|
CAD07 |
128 |
Reference
Identification Qualifier Code qualifying the
Reference Identification BM Bill of Lading Number |
M |
ID |
2/3 |
|
CAD08 |
127 |
Reference
Identification Bill of Lading Number |
M |
ID |
2/30 |
RNE9FERENCE IDENTIFICATION Segment: SAC Service, Promotion,
Allowance, or Charge Information
Usage: Optional
Max Use: 1
Purpose: To request or identify a
service, promotion, allowance, or charge; to specify the amount or percentage
for the service, promotion, allowance, or charge
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SAC01 |
248 |
Allowance or Charge
Indicator Code which indicates an
allowance or charge for the service specified C Charge |
M |
ID |
1/1 |
|
SAC02 |
1300 |
Service, Promotion,
Allowance, or Charge Code Code identifying the
service, promotion, allowance, or charge D240 Freight (discount off
cost), or Prepaid Freight Any other charges sent
will be applied as miscellaneous |
M |
ID |
4/4 |
|
SAC05 |
610 |
Amount Monetary amount |
M |
N2 |
1/15 |
|
SAC12 |
331 |
Allowance or Charge
Method of Handling Code Code indicating method
of handling for an allowance or charge 02 Off Invoice |
O |
ID |
2/2 |
|
SAC15 |
352 |
Description A free-form description
to clarify the related data elements and their content |
O |
AN |
1/80 |
RXEQPORTING DATE/ACTION Segment: ISS Invoice Shipment Summary
Usage: Mandatory
Max Use: 1
Purpose: To specify summary
details of total items shipped in terms of quantity
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ISS01 |
382 |
Number of Units Shipped Total units shipped |
M |
N0 |
1/15 |
|
ISS02 |
355 |
Unit or Basis for
Measurement Code Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken EA Each |
M |
ID |
2/2 |
RXEQPORTING DATE/ACTION Segment: CTT Transaction Totals
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total
for a specific element in the transaction set
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
CTT01 |
354 |
Number of Line Items Total number of line items
in the transaction set The number of IT1 segments present in the
transaction set |
M |
ID |
1/1 |
STERANSACTION SET TRAILER Segment: SE Transaction Set Trailer
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of
the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments)
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SE01 |
96 |
Number of Included
Segments Total number of
segments included in a transaction set including ST and SE segments |
M |
N0 |
1/10 |
|
SE02 |
329 |
Transaction Set Control
Number Identifying control
number that must be unique within the transaction set functional group
assigned by the originator for a transaction set 9 This will be the same
number as is in the ST segment (ST02) for the transaction set. |
M |
AN |
4/9 |
The
ASN must be in a pick and pack structure and must be in our system before
arrival of the shipment at our distribution facility. An expense offset will be assessed for
non-compliance.
A
separate ASN must be provided for each bill of lading. In the case of multiple truckloads, each
truckload requires a unique BOL and a separate ship notice. Carton level information is required for
every Store X-Dock shipment
to Beall’s distribution facility. The UCC128 serial container marking numbers cannot be
re-used within a 12-month period.
The
industry accepted practice for merchandise shipped by small package carriers
(for example, Fedex or UPS) is one 856 per carton. The tracking number should be the number used
in the REF BM segment of the ship notice.
Beall’s
Purchase Order number in the PRF01-segment is a 7-digit number. The leading
character must be a 0 (zero).
Deviation
from the below EDI 856 mapping may impact our ability to receive a shipment.
Note:
Functional Acknowledgments will be sent for all documents transmitted to
Beall’s by vendors.
Header
|
SEG. ID |
NAME |
REQ. DES. |
MAX USE |
|
|
ST |
Transaction Set Header |
M |
1 |
|
|
BSN |
Beginning Segment for Ship
Notice |
M |
1 |
|
Detail - Shipment
|
|
999999 |
|||
|
HL |
Hierarchical Level |
M |
1 |
|
|
TD1 |
Carrier Details
(Quanity & Weight) |
M |
1 |
|
|
TD5 |
Carrier Details (Routing) |
M |
1 |
|
|
REF |
Reference
Identification |
M |
1 |
|
|
DTM |
Date/Time Reference |
M |
1 |
|
|
FOB |
F.O.B. Related Instructions |
O |
1 |
|
|
|
2 |
|||
|
N1 |
Name |
M |
1 |
|
|
N2 |
Additional Name Information |
O |
1 |
|
|
N3 |
Address Information |
O |
1 |
|
|
N4 |
Geographic Location |
M |
1 |
|
Detail - Order
|
|
999999 |
|||
|
HL |
Hierarchical Level |
M |
1 |
|
|
PRF |
Purchase Order
Reference |
M |
1 |
|
|
PID |
Product/Item
Description |
M |
1 |
|
|
TD1 |
Carrier Details
(Quanity & Weight) |
M |
1 |
|
|
REF |
Reference
Identification |
M |
2 |
|
|
|
2 |
|||
|
N1 |
Name |
M |
1 |
|
Detail - Pack
|
|
999999 |
|||
|
HL |
Hierarchical Level |
M |
1 |
|
|
MAN |
Marks and Numbers |
M |
1 |
|
Detail - Item
|
|
999999 |
|||
|
HL |
Hierarchical Level |
M |
1 |
|
|
LIN |
Item Identification |
M |
1 |
|
|
SN1 |
Item Detail (Shipment) |
M |
1 |
|
Summary
|
CTT |
Transaction Totals |
M |
1 |
|
|
SE |
Transaction Set Trailer |
M |
1 |
|
Header
STTRANSACTION SET HEADER Segment: ST Transaction Set Header
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of
a transaction set and to assign a control number
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
ST01 |
143 |
Transaction Set
Identifier Code Code uniquely
identifying a Transaction Set 856 Ship Notice/Manifest |
M |
ID |
3/3 |
|
ST02 |
329 |
Transaction Set Control
Number Identifying control
number that must be unique within the transaction set functional group
assigned by the originator for a transaction set |
M |
AN |
4/9 |
RXEQPORTING DATE/ACTION Segment: BSN Beginning Segment for Ship
Notice
Usage: Mandatory
Max Use: 1
Purpose: To transmit identifying
numbers, dates, and other basic data relating to the transaction set
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
BSN01 |
353 |
Transaction Set Purpose
Code Code identifying
purpose of transaction set 00 Original 07 Duplicate |
M |
ID |
2/2 |
|
BSN02 |
76 |
Shipment Identification Identifying number
assigned by issuer |
M |
AN |
2/30 |
|
BSN03 |
373 |
Date Date expressed as
CCYYMMDD |
M |
DT |
8/8 |
|
BSN04 |
337 |
Time Time expressed in 24
hour clock time: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD |
M |
DT |
8/8 |
|
BSN05 |
1005 |
Hierarchical Structure
Code 0001 Pick and Pack Structure |
M |
ID |
4/4 |
RNE9FERENCE IDENTIFICATION Segment: HL Hierarchical Level
Usage: Mandatory
Max Use: 1
Purpose: To identify dependencies
and the content of hierarchically related groups of segments
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
HL01 |
628 |
Hierarchical ID Number A unique number
assigned by the sender to identify this segment in the hierarchical structure 1 for this shipment level
HL segment |
M |
AN |
1/12 |
|
HL02 |
734 |
Hierarchical Parent ID
Number Identification number
of the next higher hierarchical segment for which the segment being described
is subordinate |
M |
AN |
1/12 |
|
HL03 |
735 |
Hierarchical Level Code Code defining the
characteristic of a level in a hierarchical structure S Shipment |
M |
ID |
1/2 |
RXEQPORTING DATE/ACTION Segment: TD1 Carrier Details (Quantity
and Weight)
Usage: Mandatory
Max Use: 1
Purpose: To specify weight and
quantity
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
TD101 |
103 |
Packaging Code Code identifying the
type of packaging; Part 1: Packaging Form, Part 2: Packaging Material CTN25 corrugated cartons |
M |
AN |
5/5 |
|
TD102 |
80 |
Lading Quantity Number of cartons |
M |
N0 |
1/7 |
|
TD106 |
187 |
Weight Qualifier Code defining the weight type G Gross Weight |
M |
ID |
1/1 |
|
TD107 |
81 |
Weight Numeric non-decimal value of weight |
M |
N0 |
1/10 |
|
TD108 |
355 |
Unit or Basis for
Measurement Code Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken LB Pounds |
M |
ID |
2/2 |
RXEQPORTING DATE/ACTION Segment: TD5 Carrier Details (Routing
Sequence/Transit Time)
Usage: Mandatory
Max Use: 1
Purpose: To specify routing
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
TD502 |
66 |
Identification Code
Qualifier Code designating the
system/method of code structure used for Identification Code (67) 2 SCAC |
M |
ID |
1/1 |
|
TD503 |
67 |
Identification Code SCAC identifying the
carrier |
M |
AN |
3/4 |
|
TD504 |
91 |
Transportation
Method/Type Code SCAC identifying the
carrier |
M |
ID |
1/2 |
|
TD505 |
387 |
Routing Free-form description
of the routing |
M |
AN |
1/35 |
|
TD506 |
368 |
Shipment/Order Status
Code Code indicating the
status of an order or shipment or the disposition of any difference between the quantity
ordered and the quantity shipped for a line item or transaction CC Ship Complete PR Partial Shipment |
M |
ID |
2/2 |
RNE9FERENCE IDENTIFICATION Segment: REF Reference Identification
Usage: Mandatory
Max Use: 1
Purpose: To specify identifying
information
Notes: Bill of Lading Number must be unique for each
shipment. Receipt of duplicate Bill of
Lading numbers will be rejected unless the BSN01 is ‘07’ (re-transmission).
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
REF01 |
128 |
Reference
Identification Qualifier Code qualifying the
Reference Identification BM Bill of Lading number
|
M |
ID |
2/2 |
|
REF02 |
127 |
Reference
Identification Bill of Lading number |
C |
AN |
17/17 |
RXEQPORTING DATE/ACTION Segment: DTM Date/Time Reference
Usage: Mandatory
Max Use: 2
Purpose: To specify pertinent
dates and times
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
DTM01 |
374 |
Date/Time Qualifier Code specifying type of
date 011 Ship Date |
M |
ID |
3/3 |
|
DTM02 |
373 |
Date Date expressed as
CCYYMMDD, ship date |
C |
DT |
8/8 |
RNE9FERENCE IDENTIFICATION Segment: FOB F.O.B Related
Instructions
Usage: Optional
Max Use: 1
Purpose: To specify transportation
instructions relating to shipment
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
FOB01 |
146 |
Shipment Method of
Payment Code identifying
payment terms for transportation charges CC Collect PP Prepaid by Vendor |
M |
ID |
2/2 |
RXEQPORTING DATE/ACTION Segment: N1 Name
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by
type of organization, name, and code
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N101 |
98 |
Entity Identifier Code Code identifying an
organizational entity, a physical location, property or an individual ST Ship to, SF Ship from |
M |
ID |
2/3 |
|
N102 |
93 |
Name Free-form name |
O |
AN |
3/3 |
|
N103 |
66 |
Identification Code
Qualifier Code designating the
system/method of code structure used for Identification Code (67) 92 Assigned by Buyer, when
N101 is ST, or 1 DUNS#, when N101 is SF |
M |
ID |
2/2 |
|
N104 |
67 |
Identification Code Code identifying a
party or other code 050 Bealls DC ID when N101 is ST and goods shipped to Vendor’s DUNS when N101 is SF |
M |
AN |
3/3 |
RXEQPORTING DATE/ACTION Segment: N2 Additional Name Information
Usage: Optional
Max Use: 1
Purpose: To specify additional
names or those longer than 35 characters in length
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N201 |
93 |
Name |
M |
AN |
1/30 |
|
N202 |
93 |
Name |
O |
AN |
1/30 |
RXEQPORTING DATE/ACTION Segment: N3 Address Information
Usage: Optional
Max Use: 1
Purpose: To specify the location
of the named party
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N301 |
166 |
Address Information |
M |
ID |
1/30 |
|
N302 |
166 |
Address Information |
O |
ID |
1/30 |
RXEQPORTING DATE/ACTION Segment: N4 Name
Usage: Mandatory (N101 is SF)
Max Use: 1
Purpose: To specify the geographic
place of the named party
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N401 |
19 |
City Name |
O |
AN |
2/30 |
|
N402 |
156 |
State or Province Code |
O |
ID |
2/2 |
|
N403 |
116 |
Postal Code |
O |
ID |
3/15 |
|
N404 |
26 |
Country Code |
M |
ID |
2/3 |
RNE9FERENCE IDENTIFICATION Segment: HL Hierarchical Level
Usage: Mandatory
Max Use: 1
Purpose: To identify dependencies
and the content of hierarchically related groups of segments
Notes: a new order level must be provided for each PO/store
occurrence within the Bill of Lading/Shipment.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
HL01 |
628 |
Hierarchical ID Number A unique number
assigned by the sender to identify this segment in the hierarchical structure |
M |
AN |
1/12 |
|
HL02 |
734 |
Hierarchical Parent ID
Number Identification number
of the next higher hierarchical segment for which the segment being described
is subordinate |
M |
AN |
1/12 |
|
HL03 |
735 |
Hierarchical Level Code Code defining the
characteristic of a level in a hierarchical structure O Order |
M |
ID |
1/2 |
RNE9FERENCE IDENTIFICATION Segment: PRF Purchase Order Reference
Usage: Mandatory
Max Use: 1
Purpose: To provide reference to a
specific purchase order
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
PRF01 |
324 |
Purchase Order Number Bealls assigned Purchase
Order Number |
M |
AN |
7/7 |
|
PRF04 |
373 |
Date Bealls assigned Purchase
Order Date |
M |
AN |
8/8 |
RNE9FERENCE IDENTIFICATION Segment: PID Product/Item Description
Usage: Mandatory
Max Use: 1
Purpose: To describe a product or
process in coded or free-form format
Notes: Beall’s requires vendors to indicate compliance with the
Fair Labor Standards Act in the PID segment.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
PID01 |
349 |
Item Description Type Code indicating the
format of a description S Structured |
M |
ID |
2/2 |
|
PID03 |
559 |
Agency Qualifier Code Code identifying the
agency assigning the code values VI VICS |
M |
ID |
2/2 |
|
PID04 |
751 |
Product Description
Code A code from an industry
code list which provides specific data about a product characteristic FL Compliant with Fair
Labor Standards Act |
M |
AN |
17/17 |
RXEQPORTING DATE/ACTION Segment: TD1 Carrier Details (Quantity
and Weight)
Usage: Mandatory
Max Use: 1
Purpose: To specify weight and
quantity
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
TD101 |
103 |
Packaging Code Code identifying the
type of packaging; Part 1: Packaging Form, Part 2: Packaging Material CTN25 corrugated cartons |
M |
AN |
5/5 |
|
TD102 |
80 |
Lading Quantity Number of cartons for the PO/Store |
M |
N0 |
1/7 |
RNE9FERENCE IDENTIFICATION Segment: REF Reference Identification
Usage: Mandatory (for Bealls
Department Number)
Max Use: 2
Purpose: To specify identifying
information
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
REF01 |
128 |
Reference
Identification Qualifier Code qualifying the
Reference Identification IV Vendor’s Invoice Number DP Bealls Department
Number |
M |
ID |
2/2 |
|
REF02 |
127 |
Reference
Identification Invoice number when
REF01 is IV Bealls Department
Number when REF01 is DP |
C |
AN |
10/10 |
RXEQPORTING DATE/ACTION Segment: N1 Name
Usage: Mandatory
Max Use: 1
Purpose: To identify a party by
type of organization, name, and code
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
N101 |
98 |
Entity Identifier Code Code identifying an
organizational entity, a physical location, property or an individual BY Bealls Store Number |
M |
ID |
2/3 |
|
N102 |
93 |
Name Free-form name |
O |
AN |
3/3 |
|
N103 |
66 |
Identification Code
Qualifier Code designating the
system/method of code structure used for Identification Code (67) 92 Assigned by Buyer |
M |
ID |
2/2 |
|
N104 |
67 |
Identification Code Code identifying a
party or other code Bealls 3-character
Store Number |
M |
AN |
3/3 |
RNE9FERENCE IDENTIFICATION Segment: HL Hierarchical Level
Usage: Mandatory
Max Use: 1
Purpose: To identify dependencies
and the content of hierarchically related groups of segments
Notes: a new pack level must be provided for each carton within
the PO/store occurrence.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
HL01 |
628 |
Hierarchical ID Number A unique number
assigned by the sender to identify this segment in the hierarchical structure |
M |
AN |
1/12 |
|
HL02 |
734 |
Hierarchical Parent ID
Number Identification number
of the next higher hierarchical segment for which the segment being described
is subordinate |
M |
AN |
1/12 |
|
HL03 |
735 |
Hierarchical Level Code Code defining the
characteristic of a level in a hierarchical structure P Pack |
M |
ID |
1/2 |
RNE9FERENCE IDENTIFICATION Segment: MAN Marks and Numbers
Usage: Mandatory
Max Use: 1
Purpose: To indicate identifying
marks and numbers for shipping containers
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
MAN01 |
88 |
Marks and Numbers
Qualifier Code specifying the
application or source of Marks and Numbers (87) GM SSCC-18 and Application
Identifier |
M |
ID |
2/2 |
|
MAN02 |
87 |
Marks and Numbers Marks and numbers used
to identify a shipment or parts of a shipment |
C |
AN |
10/10 |
RNE9FERENCE IDENTIFICATION Segment: HL Hierarchical Level
Usage: Mandatory
Max Use: 1
Purpose: To identify dependencies
and the content of hierarchically related groups of segments
Notes: a new item level must be provided for each UPC within the
pack occurrence.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
HL01 |
628 |
Hierarchical ID Number A unique number
assigned by the sender to identify this segment in the hierarchical structure |
M |
AN |
1/12 |
|
HL02 |
734 |
Hierarchical Parent ID
Number Identification number
of the next higher hierarchical segment for which the segment being described
is subordinate |
M |
AN |
1/12 |
|
HL03 |
735 |
Hierarchical Level Code Code defining the
characteristic of a level in a hierarchical structure I Item |
M |
ID |
1/2 |
ILTINEM IDENTIFICATION Segment: LIN Item Identification
Usage: Mandatory
Purpose: To specify basic item identification
data
105 Notes: Items must appear
in eaches by UPC.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
LIN02 |
235 |
Product/Service ID
Qualifier Code identifying the
type/source of the descriptive number used in Product/Service ID (234) UP UPC (1-5-5-1) |
C |
ID |
2/2 |
|
LIN03 |
234 |
Product/Service ID UPC |
C |
AN |
1/12 |
ILTINEM IDENTIFICATION Segment: SN1 Item Detail
Usage: Mandatory
Purpose: To specify the quantities
associated with the item identified in the LIN at the item level.
105 Notes: Quantity must be a
whole number, not a decimal value.
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SN102 |
382 |
Number of Units Shipped Numeric value of units
shipped by UPC as a whole number only, decimal values are not posted |
M |
N0 |
1/15 |
|
SN103 |
355 |
Unit or Basis for
Measurement Code Code specifying the
units in which a value is being expressed, or manner in which a measurement
has been taken EA Each |
M |
ID |
2/2 |
RXEQPORTING DATE/ACTION Segment: CTT Transaction Totals
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total
for a specific element in the transaction set
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
CTT01 |
354 |
Number of Line Items Total number of line
items in the transaction set The number of HL segments present in the
transaction set |
M |
ID |
1/1 |
STERANSACTION SET TRAILER Segment: SE Transaction Set Trailer
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of
the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments)
Data Element Summary
|
REF. DES. |
DATA ELEMENT |
NAME |
ATTRIBUTES |
||
|
SE01 |
96 |
Number of Included
Segments Total number of
segments included in a transaction set including ST and SE segments |
M |
N0 |
1/10 |
|
SE02 |
329 |
Transaction Set Control
Number Identifying control
number that must be unique within the transaction set functional group
assigned by the originator for a transaction set 9 This will be the same
number as is in the ST segment (ST02) for the transaction set. |
M |
AN |
4/9 |

Required Information
by Zone:
A.
From Name and
Address
B.
Ship to DC
Name and Address
C.
Ship to Postal
Code
D.
Carrier
Information (Bill of Lading & PRO# if available)
E.
6 Digit
Purchase Order Number
F.
3 Digit Dept.
Number
G.
Bar-Code of
Mark/for Store Number
H.
Mark/for Store
Number and Name
I. Serial Shipping Container Code (Bar-Code & Human readable)

From: ABC Company
To: Beall’s Department Stores
Warehouse #50
Department #: 140
Case Pack Qty: 24
Case Pack Asst.: A
Carton ID:
A1of 2
Total Cartons: 96
|
Error Code |
Error Description |
Expense Offset |
|||
|
150 |
ASN (EDI 856, for
approved vendors) |
|
|||
|
151 |
No/Unusable/Late Advanced Ship
Notice |
$5 per carton |
|||
|
200 |
TRANSPORTATION |
|
|||
|
201 |
Shipping on a carrier not
authorized in our Vendor Partnership Guide – Transportation and Routing Guide
section for your shipping point and / or purchase order type. Shipments under 151 lbs are not shipped UPS
Freight LTL collect |
$275 plus inbound freight |
|||
|
202 |
Improperly sealing truckload
shipment, or failure to supply accurate information regarding
truckload/volume shipments within specified time frame or truck not being
properly loaded. |
$275 plus inbound freight |
|||
|
204 |
Shipping collect air
freight without negotiating with the buying office and without contacting the
Beall’s Traffic Office for air freight routing. |
$275 plus inbound freight |
|||
|
206 |
Shipping prepaid / adding
freight to the merchandise invoice or failure to ship 3rd party billing as
instructed. |
$275 plus full freight |
|||
|
209 |
Merchandise shipped to
wrong receiving facility or Direct to Store shipment sent to the |
$275 plus inbound freight,
plus store delivery freight |
|||
|
210 |
Multiple Shipments made on
the same or consecutive days from the same facility (less than truckload) |
$275 plus full freight on
the smaller or secondary order(s). |
|||
|
211 |
More than one shipment per
Purchase Order |
$275 plus full freight on
the smaller or secondary order(s). |
|||
|
212 |
FOB shipping point mismatch
– vendor pickup city and state incorrect |
$275 plus full freight |
|||
|
250 |
PURCHASE ORDER
COMPLIANCE |
|
|||
|
251 |
Advertised merchandise
shipped past cancel which necessitates abnormal means of transportation to
our stores to meet the ad deadline. |
$500 plus full freight to
Stores plus late ship discount below |
|||
|
252 |
Merchandise shipped in
violation of purchase order shipping window or against a canceled P.O. |
Days late |
Disc |
Days early |
Disc |
|
|
1-6 |
20% |
1-13 |
10% |
|
|
|
7-13 |
30% |
14-30 |
20% |
|
|
|
14 + |
40% |
31 + |
30% |
|
|
253 |
Substitution for
merchandise ordered or any variation from the ordered styles, colors, sizes,
quantities, prices or terms. |
$275 plus all freight cost
and 10% of item cost per unit or $100, whichever is greater. Effective 2/1/09:
|
|||
|
255 |
Advertised merchandise not
shipped by seller at 28 days prior to the ad date must be shipped via Air
Freight to Beall’s DC. |
Vendor to pay 100% of Air freight charges |
|||
|
256 |
Advertised merchandise that
will not be shipped by seller at 14 days prior to the Ad date must be shipped
via Air freight direct to each store. |
Vendor to pay 100% of Air freight charges to each
store |
|||
|
Error Code |
Error Description |
Expense Offset |
|
270 |
BILL OF LADING |
|
|
271 |
No BOL or Inaccurate /
insufficient detail in BOL, original invoice or UPS pickup record. Not using VICS BOL when shipping from
outside of the FOB zone. Missing or
incorrect information on BOL errors may include:
|
$275 plus full
transportation cost |
|
300 |
UCC-128 (for
approved vendors) |
|
|
301 |
Missing UCC-128 Label
and/or 128 pack data in 856 |
$5 per carton |
|
302 |
Poor quality UCC-128 label |
$5 per carton |
|
303 |
UCC-128 Bar-code located
incorrectly on cartons |
$5 per carton |
|
304 |
UCC-128 format not correct |
$5 per carton |
|
305 |
Duplicate 128 numbers |
$5 per carton |
|
306 |
Multiple, conflicting
UCC-128 labels |
$5 per carton |
|
350 |
CARTON
IDENTIFICATION |
|
|
351 |
Failure to mark outside of
carton as required for your purchase order type. |
$275 Handling Charge |
|
400 |
PACKING |
|
|
401 |
Failure to separate and
pack merchandise as required for your |
$275 Handling Charge |
|
402 |
Shipping cartons over the
50 lb. Weight limit or shipping banded cartons |
$275 Handling Charge |
|
403 |
Shipped multiple purchase
orders or stores per carton |
$275 Handling Charge |
|
404 |
Failure to provide packing
list information to the style, color, size level. |
$275 Handling Charge |
|
405 |
Improper sealing of full
truckload or failure to properly document trailer and seal number (s). |
$275 plus full
transportation cost |
|
406 |
Unnecessary packing
materials |
$25 per receipt and .25 per
unit |
|
600 |
UPC TICKETING /
FLOOR READY MERCHANDISE |
|
|
601 |
Merchandise not UPC marked |
$25 per receipt, plus $.50
/ unit |
|
603 |
Merchandise is mis-marked |
$25 per receipt, plus $.50
/ unit |
|
605 |
Poor Quality Vendor
Supplied Bar-code |
$25 per receipt, plus $.50
/ unit |
|
607 |
No / wrong retail on UPC
tickets (where req.) |
$25 per receipt, plus $.50
/ unit |
|
609 |
UPC missing human readable
data |
$25 per receipt, plus $.50
/ unit |
|
611 |
Merchandise is not ticketed
with Beall’s UPCA. |
$25 per receipt, plus $.50
/ unit |
|
613 |
Merchandise with Beall’s
UPCA is mis-marked |
$25 per receipt, plus $.50
/ unit |
|
620 |
No Hanger |
$25 per receipt, plus $.50
/ unit |
|
621 |
Wrong Hanger |
$25 per receipt, plus $.50
/ unit |
|
622 |
Hanger in carton, not on
garment |
$25 per receipt, plus $.50
/ unit |
|
623 |
Wrong hanger and hanger in
carton, not on garmernt |
$25 per receipt, plus $.50
/ unit |
|
624 |
Size indicator omitted |
$25 per receipt, plus $.50
/ unit |
|
625 |
Size indicator incorrect |
$25 per receipt, plus $.50
/ unit |
|
626 |
Size indicator not approved |
$25 per receipt, plus $.50
/ unit |
|
630 |
Not folded as required |
$25 per receipt, plus $.50
/ unit |
|
Error Code |
Error Description |
Expense Offset |
|
600 |
UPC TICKETING /
FLOOR READY MERCHANDISE |
|
|
631 |
No size tape/circle sticker |
$25 per receipt, plus $.50
/ unit |
|
632 |
No ticket |
$25 per receipt, plus $.50
/ unit |
|
700 |
SHIPMENT ACCURACY |
|
|
701 |
Removed from “Cross-dock”
and moved to traditional processing |
$50 per receipt plus $1 per
unit |
|
702 |
Failed Inspection and
required 100% audit |
$50 per receipt plus $1 per
unit |
|
703 |
Shipment and ASN does not
match |
$50 per receipt plus $1 per
unit |
|
800 |
INVOICE (EDI 810,
for approved vendors) |
|
|
801 |
Invalid Bealls-assigned |
$10 per invoice |
|
802 |
Invoice amount out of
balance: line item costs + freight – discounts differs from the total invoice
amount |
$10 per invoice |
|
803 |
Invalid DUNS number |
$10 per invoice |
|
804 |
Invalid invoice number:
invoice number is blank or has more than 10 non-blank characters |
$10 per invoice |
|
805 |
Invalid invoice date:
invoice date is zeroes or blank or is not a valid date |
$10 per invoice |
|
806 |
Duplicate invoice number: |
$10 per invoice |
|
807 |
Invalid store number: store
number is blank or zeroes or does not match store number in |
$10 per invoice |
|
808 |
Invoice amount over max:
invoice amount exceeds 10% of the amount ordered |
$10 per invoice |
|
809 |
Invalid UPC |
$10 per invoice |
|
900 |
TMS |
|
|
910 |
Incorrect entry of weight,
cube, carton count and/or shipment origin resulting in a TMS planned routing
to be incorrect or unachievable |
$275 |
|
920 |
Shipment routed on a
carrier other than the one specified |
$275 plus full freight |
|
930 |
Freight not ready at pickup
date and time requested through Webforms or excessive loading time impacting
subsequent pickups |
$275 plus full freight |
Correspondence on any Expense Offset violations must
be initiated within 6 months of the expense offset check date. We are unable to research requests older than
6 months from issue date.
All Penalties are subject to collection by Beall’s
Department Stores and its Subsidiaries or Affiliates