This chapter contains the following topics:
The UCC in the United States, the Electronic Commerce Council of Canada (ECCC), and the International Article Numbering Association (EAN) have established standard identification and information transmission procedures. These standards, known as UCC 128 compliance, facilitate uniform product identification and the exchange of shipment information between suppliers and customers (retailers).
To adopt UCC 128 compliance practices, suppliers and retailers adopt these standards:
A defined structure for each code.
Bar code labels.
Fixed or variable codes that encode information for a single product unit, a consumer pack, or a collection or packages for shipment.
Labels that follow the specific standard of the UCC Common Label. This standard sets up specific label segments and the information that is contained in each segment.
Electronic Data Interchange (EDI).
The electronic exchange of structured computer-readable information.
For large retailers, the benefits of being UCC 128 compliant are:
By reducing warehouse cycle time, retailers can get their products on the shelf more quickly. A retailer can increase the sell-through revenue by moving the product to the customer faster.
Reduced safety stock
By receiving information about shipments before their arrival, companies can react more quickly to shortages and maintain less safety stock in inventory.
Increased forecasting accuracy
Retailers are able to more accurately measure lead time of shipments. This can reduce safety stock.
Reduced receiving costs
By scanning shipping labels, the retailer can collect bar-coded data faster than by manually entering data. Scanning shipping labels is less labor-intensive and results in fewer errors and omissions of data.
Improved warehouse management
Retailers can gather better shipping statistics, reduce warehouse cycle time, and more efficiently plan floor space and labor schedules.
For suppliers, the benefits of being UCC 128 compliant are:
Improved cash flow
By reducing the payment cycle times with retailers, suppliers can reduce borrowing requirements and improve cash flow.
Retailers penalize suppliers that cannot adopt UCC 128 compliance procedures. Typically, this penalty is per transaction. If the supplier cannot adopt UCC 128 compliance practices within a given time frame, the supplier can lose business with the retailer.
Each company can assign product identification codes. The UCC, the ECCC, and the EAN (outside of Canada and the United States) assign member companies the company identification. In the company identification codes, the first digit is the region code. For North America, the region code is 0. Therefore, the company identification can be seven digits if the first digit as zero. Because each UCC code contains the company number, all numbers are unique.
Each company can assign the Universal Product Code (identified as UPC in North America and EAN-13 outside of North America) to both a consumer unit and the lowest saleable unit for a specific product. For example, a can of soda would have the UPC identification on the can because it can be sold individually. The UPC code is a fixed code that identifies one unit of a specific product.
This example illustrates the structure of a UPC code:
The UPC code consists of a:
Seven-digit company (or manufacturer) ID that is assigned by the UCC or the EAN.
For North American companies, only six characters represent the company ID because the leading seventh digit is always zero and can be left off the code.
Five-digit product ID that is assigned by the company.
Single-digit check character.
Typically, a company maintains its own product identification codes for internal use but cross-references the internal product identification codes to the UPC code.
Companies assign the Shipping Container Code (identified as the SCC-14 in North America and EAN-14 outside of North America) to an intermediate pack for a specific product. For example, cans of soda are sold in various configurations. One possible configuration is four 6-packs in each case. Therefore, the case would have an intermediate pack identifier (SCC-14) on it.
The SCC, similar to the UPC, is a fixed code that identifies the specific number of consumer packs of a specific product. The SCC code on the case of soda represents four consumer packs, each with six sodas or a total of 24 sodas.
The SCC-14 code consists of:
A single-digit packaging indicator that identifies the packaging.
This identifier is assigned by the company and may vary from product to product. This identifier is fixed and has these values:
Zero indicates that the product ID on the SCC is different than the product identification on the UPC codes that are contained within the package.
Codes 1 though 8 indicate company-defined packaging. For example, a 1 might mean a case containing six packs and a 2 might mean a case containing 12-pack boxes.
Code 9 indicates that the amount of product inside the package varies from package to package even though the same product identification is in the UPC codes of the consumer pack that is contained within the package.
A seven-digit company (or manufacturer) ID that is assigned by the UCC or the EAN.
A five-digit product ID that is assigned by the company.
A single-digit check character.
In the system, an SCC code is equivalent to an item code for a specific unit of measure. For any item, one UPC code exists, but several SCC codes exist.
The SSCC is a variable code that can be a hierarchical structure of SCCs and UPCs. The code is a key to a database record. For example, an SSCC can be put on a pallet that has 10 cases of soda and 10 cases of juice.
This example illustrates the structure of an SSCC-18 code:
The SSCC-18 code consists of:
A single-digit packaging type. This identifier is fixed and has these values:
Zero indicates that the shipping container is a case or carton.
Code 2 indicates that the shipping container is a pallet (larger than a case).
Code 3 indicates that the shipping container is undefined.
Code 4 indicates the shipping container that you use internally for intracompany use.
Codes 5 though 9 are reserved for future use.
A seven-digit company (or manufacturer) ID that is assigned by the UCC or the EAN.
A nine-digit serial number that identifies the shipping method that is assigned by the company.
A single-digit check character.
The UPC symbology has different formats, depending on business needs:
UPC-A: A format that displays all 12 or 13 digits.
UPC-E: A format that compresses the 12-digit or 13-digit numbers to eight digits by removing zeroes from the number.
Although the UPC-E version displays only eight digits, when the code is scanned and decoded by the bar reader, the transmission includes all digits to the computer.
The SCC has different formats, depending on where you print the label and the information to include. For example, you can use the Interleaved 2-of-5 (ITF) format if you print the bar codes on corrugated cartons. You might want to use the UPC/EAN-128 if you encode an Application Identifier (AI) prefix. An AI prefix is important when you are scanning multiple bar codes on a shipping label because they enable the scanner to identify what the encoded number represents.
The ITF format encodes the 14 digits and is often used on corrugated cartons because it can be printed more reliably than UPC/EAN-128.
This example illustrates the structure of an SCC14/EAN-14 label:
The UPC/EAN 128 format encodes the 14 digits of the SCC and an AI prefix.
This example illustrates the structure of a UPC/EAN 128 label:
The SSCC is encoded with the UPC/EAN-128 standard. This standard encodes both the 18 digits of SSCC-18 code and an AI prefix. The AI identifies the type of information that is encoded. An AI of 00 identifies the bar code as an SSCC-18.
The SSCC is the label that is affixed to the shipment, the pallet, or a container. It might be applied as the shipment is being assembled or at the dock as the shipment is being loaded for transport to the customer.
This example illustrates the structure of a SSCC-18 label:
When you transmit order information, you can establish a format that relays the information about the shipment, the orders within the shipment, and the items within the order. You define hierarchical configurations to transmit information that meets the customers' needs.
You can set up any structure based on the business needs. This table illustrates examples of hierarchical structures:
|Pick and Pack||This is the most flexible configuration because you can combine products at the tare and pack levels.|
|Standard Carton Pack||Within this configuration, only one UPC can be present in subordinate tare and pack levels.|
Within the configurations, you can define hierarchies based on the customer preferences. This table provides examples of configuration levels:
|Shipment (S)||Only one shipment level can be in each transaction set that is transmitted. This contains information such as the bill of lading number, ship to, and sold from information.|
|Order (O)||The order level contains information that is related to the supplier's sales order and the customer's purchase order.|
|Tare (T)||The optional tare level contains information that is related to pallets and other large product collections.|
|Pack (P)||The optional pack level contains information that is related to intermediate packs.|
|Item (I)||The item level contains information about the product that is shipped, such as UPC number and quantity.|
One customer might need shipment, order, and item information in their orders, while another might prefer shipment, order, tare, pack, and item information, in that order. You define hierarchical configurations to transmit information that meets the customers' needs for their advanced shipment notice (ASN).
|Form Name||Form ID||Navigation||Usage|
|Hierarchical Configuration Definition Revisions||W47HLD||Shipping Notice (G47215), Hierarchical Configuration Definition
Click Add on the Work With Hierarchical Configuration Definition form.
|Set up hierarchical configurations.
Define hierarchical configurations to transmit information that meets the customers' needs.
Enter a number that identifies an entry in the address book, such as employee, applicant, participant, customer, supplier, tenant, or location.
Enter the EDI 856 transaction set-hierarchy configuration-codes that specify the levels that are present in the Ship Notice/Manifest. This field is made up of a combination of two-character hierarchical level codes (values from the X12 specification for data element 735 - Hierarchical Level Code). Up to nine combinations of HLC codes can be in this field.
Enter a code indicating the hierarchical application structure of an EDI transaction set that uses the HL segment to define the structure of the transaction set.
Enter a number to organize the table into a logical group for online viewing and reporting.
Enter a data dictionary item name. Examples include F#MMCO or F#CO for company, F#MMCU or F#MCU for business unit, and F#RP01-30 for business unit category codes 01 through 30.
With the exception of #, @, and $, the system does not allow special characters as part of the data item name.
To create protected data names that software updates do not overwrite, use $xxx and @xxx, where xxx is user-defined.
Note:For report writer, on the Processing Options Setup form, the system uses the field name during data entry to edit the field size and other field attributes.
Enter a code to designate sorting sequence as ascending or descending. Values are:
Note:This field is for use within the OPNQRYF command to designate the UNIQUEKEY parameter. The number of key sequence fields that you specify with the proceeding codes represent the number that is assigned to the UNIQUEKEY parameter. This parameter eliminates duplicate records for the specified keys.
Enter a level break. You might specify the level of totaling to place on this field. The system allows up to nine levels of totals. If you do not specify levels of totals in an order that is consistent with the sequence parameters, unpredictable results might occur, for example:
Level 01 - Department Totals - Sort Sequence 03
Level 02 - Branch Totals - Sort Sequence 02
Level 03 - Division Totals - Sort Sequence 01
Level 10 - Grand Totals
If you specify the same totaling level on multiple data fields, you must enter a 1 in the first position of total level for all secondary fields, for example:
Level 01 - Business Unit (description comes from here).
Level 11 - Object (description ignored).
Level 11 - Subsidiary (description ignored).
Do not confuse this with account master or business unit master level-of-detail concept.
This section provides an overview of shipping labels and discusses how to set up shipping information.
This example illustrates a shipping label:
This table lists the segments within the previous example and the information that is contained in each:
|Zone A - Ship From||Ship From name and address.||Conditional for full trailer shipments, mandatory for other shipments.|
|Zone B - Ship To||Ship To name and address.||Conditional for full trailer shipments, mandatory for other shipments.|
|Zone C - Carrier Routing Bar Code||Ship To postal code or PRO Number bar code.||Conditional.|
|Zone D - Carrier||Carrier Name, SCAC Bill of Lading Number, PRO Number Carrier Assigned Packaged ID, Carrier Assigned Shipper ID.||Conditional.|
|Zone E - Trading Partner Data||The agreed-upon data for the trading partners. Both bar code and text data can appear in this zone. For example, you can enter purchase order numbers, serial numbers, and product numbers.||Optional.|
|Zone F - Trading Partner Data||This is the agreed-upon data for the trading partners. This data is supplemental to the data that is in Zone E.||Optional.|
|Zone G - Final Destination Code||Can be large human-readable location number or bar code. For example, you can use this zone for the Mark-For number.||Conditional.|
|Zone H - Final Destination Code||The Final Destination ID, Mark-For name and address.||Conditional.|
|Zone I - SSCC-18 Bar Code||The Serial Shipping Container Code.||Mandatory.|
|Form Name||Form ID||Navigation||Usage|
|Customer Master Revision||W03013B||Sales Order Management Setup (G4241), Customer Billing Instructions
Select a customer, and then click Select on the Work With Customer Master form.
|Set up shipping information.
Set up customer specifications for UCC 128 Compliance. These specifications might include the customer-specific format for transmitted information and additional UCC 128 processing information, such as transportation equipment, routing, and reference numbers.
Enter the name of the program that the system uses to print shipping labels for a customer.
Enter the default pick and pack configuration that the customer requires.
Enter the default standard carton-pack configuration that the customer requires.
Enter the DREAM Writer version that the system uses for printing shipping labels for a customer.
Enter the default configuration that the customer requires. Values are:
Blank: Processing is not performed for this customer.
1: Pick and pack configuration is the default value.
2: Standard carton configuration is the default value.
Select to indicate that a packaging code is required for this customer.
Select to indicate that a transportation method is required for this customer.
Select to indicate that an equipment code is required for this customer.
Select to indicate whether identification codes 1 and 2 are required for this customer.
Select to indicate whether reference numbers 1 and 2 are required for this customer.
Select to indicate that a weight code is required for this customer.
Select to indicate that a routing description is required for this customer.
This section provides an overview of item information for UCC 128, lists prerequisites, and discusses how to set up item information for UCC 128.
For UCC 128 processing, the item identifiers can be the UPC or SCC codes that you assign to the product unit and intermediate packs.
Zero indicates that the product ID on the SCC is different than the product identification on the UPC that is contained within the package.
You can use this product identifier for kits.
Codes 1 through 8 indicate company-defined packaging.
For example, a 1 might mean a case containing six packs and a 2 might mean a case containing 12-pack boxes.
Code 9 indicates that the amount of product inside the package varies from package to package, even though the same product identification is in the UPC of the consumer pack that is contained within the package.
The system does not support variable units of measure.
You can set up aggregate SCCs to represent kits with non-inventory components. A kit is a collection of inventory items, called components, that are associated with a description name, called a parent item. The aggregate SCC represents the parent item. You can access the Item Cross-Reference Revisions form to assign component UPCs to the aggregate SCC for the kit. You enter cross-reference information only for non-inventory items. For example, you do not stock bandages, an item for which you do not record inventory or UPCs. You do sell first aid kits, which include bandages. Depending on the customer requirements, you can enter the aggregate SCC for the first aid kit and item cross-reference information for the components, such as bandages, that constitute the first aid kit.
If the components are inventory items, you do not have to enter cross-references. When you enter an order for a kit, the system retrieves the kit information, which includes the component UPCs, from the Item Master table.
To set up identification for kits with non-inventory items, you can set up an SCC with a product identifier equal to 0 (zero), which indicates that the SCC is different than the product identification on the UPC that it contains. To assign the UPC to the aggregate, you can enter information in the Item Cross-Reference field.
On Item Cross Reference, you must enter the cross-reference type, UP, to indicate UPC. The cross-reference item number is the UPC code and the cross-reference description is the unit of measure.
Set up the UCC-assigned vendor number in user-defined code (UDC) 41/UC.
Verify that you have set up the shipping document types in UDC 49/SD.
|Form Name||Form ID||Navigation||Usage|
|Storage/Shipping||W4101D||Inventory Master/Transactions (G4111), Item Master
Select an item and then select Storage/Shipping from the Row menu on the Work With Item Master Browse form.
|Set up item information for UCC 128.
Assign UPC or SCC codes to product unit and intermediate packs as item identifiers.
|Item Cross Reference Revisions By Item||W4104C||Select Item Cross Ref. from the Form menu on the Storage/Shipping form.||Assign UPCs for non-inventory components to the aggregate SCC.|
Enter the UOM at the UPC level.
Enter the universal product code number that must conform to the UCC structure for UPC numbers.
Enter the unit of measure that is associated with an SCC pack that has a packaging indicator of 1.
Enter the unit of measure code to use for each universal product code quantity that is contained in the aggregate service class code pack.
Enter the unit of measure that is associated with an SCC pack that has a packaging indicator of zero.
Note:In the system, an SCC is equivalent to an item code at a specific unit of measure. For any item, one UPC exists, but several SCCs exist.
You can enter UPCs and SCCs with product identifiers 1 through 8.
To set up item information for a kit, complete only the Default Aggregate UPC UOM and SCC (PI=0) fields.