Store Inventory Management Barcode Labeling
Store Inventory Management Barcode Labeling
Management
Barcode Labeling
June 2009
Contents
Overview ...................................................................................................................................3
Prerequisite ..............................................................................................................................3
Related Documents .................................................................................................................3
Labeling Overview ...................................................................................................................4
Oracle Retail Store Inventory Management Labeling ..........................................................4
Label Design ...................................................................................................................................... 5
Configuring Labels for Oracle Retail SIM ..................................................................................... 5
Shipping UCC-128 SSCC Label.................................................................................................... 6
Returns UCC-128 SSCC Label...................................................................................................... 8
Shelf UCC-128 SSCC Label........................................................................................................... 9
Label Configuring Summary ........................................................................................................ 10
Oracle SIM Reporting Framework ........................................................................................11
Solution Diagram ...................................................................................................................12
ZebraLink Enterprise Connector .................................................................................................. 12
Assumptions ..........................................................................................................................13
Printer Configuration In SIM .................................................................................................14
Oracle BI Publisher Setup.....................................................................................................14
Setting up the Label printer in BI Publisher........................................................................15
Disclaimers .............................................................................................................................16
Conclusion..............................................................................................................................16
Overview
Oracle Retail Store Inventory Management (SIM) Barcode Label means meeting or
complying with the labeling guidelines set down by your customer. The customer, whether
it is a retail firm, shipper, or manufacturer, has created their own labeling specifications to
fulfill their label requirement needs. It is up to the supplier to meet those guidelines. Failure
to do so could result in return of product, penalties, or contract termination.
Organizations like the Uniform Code Council (UCC), the Automotive Industry Action
Group (AIAG) and Health Industry Business Communications Council (HIBCC) have
developed specific industry labeling standards. Their guidelines minimize problems
between trading partners by creating a basic structure that all suppliers and customers can
agree upon.
Oracle Retail Store Inventory Management provides a flexible label-printing architecture
through Oracle Business Intelligence, which enables you to comply with your customerlabeling requirements. This white paper elaborates on the configuration of Oracle Retail
Returns and Shelf labeling standards using Zebra Technologies barcode printer products.
Prerequisite
This document is a supplement that describes the report elements of barcode labels for
Oracle Retail using Zebra Technologies barcode printer products with Oracle Business
Intelligence Publisher.
Related Documents
For detailed information on implementation and configuration, refer to the following
documents:
Oracle Retail Store Inventory Management User Guide
Oracle Business Intelligence Publisher User Guide
ZebraDesigner for XML User Guide
ZebraLink Enterprise Connector for Oracle BI Publisher User Guide
ZebraDesigner for XML Font and Graphics Downloader User Guide
ZebraNet Bridge Enterprise User Guide
Zebra Enterprise Connector Solution Flyer
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 3
Labeling Overview
Oracle Retail Store Inventory Management allows store personnel to quickly and easily
perform an array of in-store operations to receive merchandise, manage physical inventories,
conduct stock counts, order or transfer stock, ship and receive, handle Direct Store Delivery,
and pricing and printing of labels and tickets. Store Inventory Management provides store
employees with the information and flexible capabilities that are needed to convert shoppers
into buyers and maintain optimal inventory levels. Store Inventory Management enables
floor-based inventory management through the use of mobile devices and store PCs. The
handheld mobile device enables the user to bring powerful software that normally runs in
the back office to the shop floor and backroom increasing efficiency and enabling retail best
practices. The handheld is used for capturing and validating data. The data can then be sent
to external systems, including the corporate level merchandising or warehousing system.
Oracle Retail Store Inventory Management is integrated with Oracle Business Intelligence to
produce xml files as part of a transaction or a business event, such as a purchase order
receipt, returns confirmation, shipping completion, or shelf label report generation. Often,
the types of labels that might be required during certain transactions, and the source of the
data for those labels, are identical for several different transactions.
Oracle XML reports can be associated with label types. The type of data that is included in
each label differentiates the label types. For instance, the Returns label type includes all the
attributes about a record, such as item description, part numbers and customer, while a shelf
label includes item details about the product.
While the Oracle XML report type identifies the type of data that is available to each label, a
label format identifies the exact fields that are included in each label, as well as the name to
assign to each of those fields that the ZebraLink Enterprise Connector software identifies.
The Oracle Retail Store Inventory Management barcode printing solution is used in
conjunction with Zebra Technologies barcode printing software and hardware offerings. The
Zebra enterprise label integration software monitors and manages label directory and the
delivery of data to respective Zebra barcode and RFID printers.
This document outlines the Oracle Retail Store Inventory Management barcode printing
solution.
Carton Labeling: Once a container or carton has been packed with a quantity of
products sharing a common/different UPC or part number, the carton or pallet is
then labeled to identify the contents. This label can be mapped to Oracle XML report
label type <RETURNS>.
There are two possibilities:
Shelf Product Labeling: Most common data fields in individual shelf labeling are
Manufacturer Code, Item Code, Serial Number, Production Date and Expiry Date.
These types of labels do not include any shipping information. They can be mapped
to the Oracle XML report label type <SHELF>.
Label Design
Oracle Retail SIM labels must be designed using the Zebra Designer for XML barcode
labeling software. Pre-design content is provided by Oracle Retail SIM. The root node of the
XML report for each label identifies the label names.
Once you have decided on the label format to be generated, and have examined the label
fields required in the label, look at the XML report generated by Oracle Business Intelligence
Publisher and map the required labels to the XML tag as variable fields in the Zebra label
design tool. The following steps outline this approach:
The XML Tags must match the Variable fields on the Label, for example:
<ORGANIZATION> in the XML report will be represented as
$$ORGANIZATION$$ in the label design.
Follow the instructions in ZebraDesigner for XML in the ZebraLink Enterprise
Connector for Oracle BI Publisher User Guide to construct your label design.
After constructing the label format, you need to define label rules in the Zebra Enterprise
Connector to print these labels. Modify the ReportsInfo.ini file in the \zebra_ec\bin
directory where the Enterprise Connector is installed. Follow the instructions in ZEC
Installation and Operation in the ZebraLink Enterprise Connector for Oracle BI Publisher User
Guide.
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 5
This is a shipping label, which needs to be printed and attached to the container. The fields
in the above label can be mapped using the XML report from Oracle BI Publisher.
The following is a sample Oracle BI Publisher report:
<SHIPPING>
<SHIP_LINE>
<ORGANIZATION>O123</ORGANIZATION>
<SUPPLIER>Zebra</SUPPLIER>
<SHIP_FROM_ADDRESS1/>
<SHIP_FROM_ADDRESS2/>
<SHIP_FROM_CITY/>
<SHIP_FROM_STATE/>
<SHIP_FROM_ZIP/>
<LPN>1</LPN>
<PART_NUMBER>117-000-2050</PART_NUMBER>
<ITEM_DESC>110 XiIII PLUS</ITEM_DESC>
<SERIAL_NUMBER>ser1</SERIAL_NUMBER>
<QUANTITY>1</QUANTITY>
<SHIP_TO_CUSTOMER>Bills House of Patios</SHIP_TO_CUSTOMER>
<SHIP_TO_ADDRESS1>21 Wacker</SHIP_TO_ADDRESS1>
<SHIP_TO_ADDRESS_2/>
<SHIP_TO_CITY>Chicago</SHIP_TO_CITY>
<SHIP_TO_STATE>IL</SHIP_TO_STATE>
<SHIP_TO_ZIP>60001</SHIP_TO_ZIP>
<CUSTOMER>Bills House of Patios</CUSTOMER>
<SUPPLIER>Zebra</SUPPLIER>
<UOM>EA</UOM>
</SHIP_LINE>
</SHIPPING>
Label Field
Label Field
Seeded
XML Report
Nodes
in the Label
<SHIPPING>
$$ORGANIZATION$$
ORGANIZATION
Yes
<ORGANIZATION>
<SHIP_LINE>
$$SUPPLIER$$
SUPPLIER
Yes
<SUPPLIER>
$$SHIP_FROM_ADDRESS1$$
SHIP_FROM_ADDRESS1
Yes
<SHIP_FROM_ADDRESS1>
$$SHIP_FROM_ADDRESS2$$
SHIP_FROM_ADDRESS2
Yes
<SHIP_FROM_ADDRESS2>
$$SHIP_FROM_CITY$$
SHIP_FROM_CITY
Yes
<SHIP_FROM_CITY>
$$SHIP_FROM_STATE$$
SHIP_FROM_STATE
Yes
<SHIP_FROM_STATE>
$$SHIP_FROM_ZIP$$
SHIP_FROM_ZIP
Yes
<SHIP_FROM_ZIP>
$$LPN$$
LPN
Yes
<LPN>
$$PART_NUMBER$$
PART_NUMBER
Yes
<PART_NUMBER>
$$ITEM_DESC$$
ITEM_DESC
Yes
<ITEM_DESC>
$$SERIAL_NUMBER$$
SERIAL_NUMBER
Yes
<SERIAL_NUMBER>
$$QUANTITY$$
QUANTITY
Yes
<QUANTITY>
$$SHIP_TO_CUSTOMER$$
SHIP_TO_CUSTOMER
Yes
<SHIP_TO_CUSTOMER>
$$SHIP_TO_ADDRESS1$$
SHIP_TO_ADDRESS1
Yes
<SHIP_TO_ADDRESS1>
$$SHIP_TO_ADDRESS_2$$
SHIP_TO_ADDRESS_2
Yes
<SHIP_TO_ADDRESS_2>
$$SHIP_TO_CITY$$
SHIP_TO_CITY
Yes
<SHIP_TO_CITY>
$$SHIP_TO_STATE$$
SHIP_TO_STATE
Yes
<SHIP_TO_STATE>
$$SHIP_TO_ZIP$$
SHIP_TO_ZIP
Yes
<SHIP_TO_ZIP>
$$CUSTOMER$$
CUSTOMER
Yes
<CUSTOMER>
$$SUPPLIER$$
SUPPLIER
Yes
<SUPPLIER>
$$UOM$$
UOM
Yes
<UOM>
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 7
You can map all the fields in the label to the variable fields from the Returns XML Report in
Oracle BI Publisher.
The following is a sample XML report:
<RETURNS>
<RETURN_LINE>
<TRANS_ID>1</TRANS_ID>
<RET_AUTH>1</RET_AUTH>
<TO_NAME>Solihull</TO_NAME>
<TO_ADD1>950 Nicollet Mall</TO_ADD1>
<TO_ADD2/>
<TO_CITY>Minneapolis</TO_CITY>
<TO_STATE>MN</TO_STATE>
<TO_POSTAL>55403</TO_POSTAL>
<FROM_NAME>Solihull</FROM_NAME>
<FROM_ADD1>950 Nicollet Mall</FROM_ADD1>
<FROM_ADD2/>
<FROM_CITY>Minneapolis</FROM_CITY>
<FROM_STATE>MN</FROM_STATE>
<FROM_POSTAL>55403</FROM_POSTAL>
</RETURN_LINE>
</RETURNS>
Label Field
Label Field
Seeded
XML Report
Nodes
in the Label
Name in Oracle
Retail
<RETURN>
$$TRANS_ID$$
TRANS_ID
Yes
<TRANS_ID>
<RETURN_LINE>
$$RET_AUTH$$
RET_AUTH
Yes
<RET_AUTH>
$$TO_NAME$$
TO_NAME
Yes
<TO_NAME>
$$TO_ADD1$$
TO_ADD1
Yes
<TO_ADD1>
$$TO_ADD2$$
TO_ADD2
Yes
<TO_ADD2>
$$TO_CITY$$
TO_CITY
Yes
<TO_CITY>
$$TO_STATE$$
TO_STATE
Yes
<TO_STATE>
$$TO_POSTAL$$
TO_POSTAL
Yes
<TO_POSTAL>
$$FROM_NAME$$
FROM_NAME
Yes
<FROM_NAME>
$$FROM_ADD1$$
FROM_ADD1
Yes
<FROM_ADD1>
$$FROM_ADD2$$
FROM_ADD2
Yes
<FROM_ADD2>
$$FROM_CITY$$
FROM_CITY
Yes
<FROM_CITY>
$$FROM_STATE$$
FROM_STATE
Yes
<FROM_STATE>
$$FROM_POSTAL$$
FROM_POSTAL
Yes
<FROM_POSTAL>
You can easily map all the fields in the label to the variable fields from the Returns XML
Report in Oracle BI Publisher.
The following is a sample XML report:
<SHELFLABEL>
<LABEL>
<ITEM_TICKET_ID>1</ITEM_TICKET_ID>
<LONG_DESCRIPTION>z parent:Brown:Cherry:Medium:Cinnamon</LONG_DESCRIPTION>
<CASE_SIZE>2</CASE_SIZE>
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 9
<SKU>100017328</SKU>
<ORDERABLE>Y</ORDERABLE>
<SELLABLE_UOM>EA</SELLABLE_UOM>
<UNIT_PRICE>1020</UNIT_PRICE>
<UNIT_PRICE_CURRENCY_CODE>USD</UNIT_PRICE_CURRENCY_CODE>
<COUNTRY_OF_MANUFACTURE>US</COUNTRY_OF_MANUFACTURE>
<UOM_PRICE>1020</UOM_PRICE>
<UOM_PRICE_CURRENCY_CODE>USD</UOM_PRICE_CURRENCY_CODE>
</LABEL>
</SHELFLABEL>
Label Field
Label Field
Seeded
XML Report
Nodes
in the Label
Name in Oracle
Retail
<SHELFLABEL>
$$ITEM_TICKET_ID$$
ITEM_TICKET_ID
Yes
<ITEM_TICKET_ID>
<LABEL>
$$LONG_DESCRIPTION$$
LONG_DESCRIPTION
Yes
<LONG_DESCRIPTION
>
$$CASE_SIZE$$
CASE_SIZE
Yes
<CASE_SIZE>
$$SKU$$
SKU
Yes
<SKU>
$$ORDERABLE$$
ORDERABLE
Yes
<ORDERABLE>
$$SELLABLE$$
SELLABLE
Yes
<SELLABLE>
$$UNIT_PRICE$$
UNIT_PRICE
Yes
<UNIT_PRICE>
$$UNIT_PRICE_CURREN
CY_CODE$$
UNIT_PRICE_CURRENC
Y_CODE
Yes
<UNIT_PRICE_CURREN
CY_CODE>
$$COUNTRY_OF_MANUF
ACTURE$$
COUNTRY_OF_MANUF
ACTURE
Yes
<COUNTRY_OF_MANU
FACTURE>
$$UOM_PRICE$$
UOM_PRICE
Yes
<UOM_PRICE>
$$UOM_PRICE_CURREN
CY_CODE$$
UOM_PRICE_CURRENC
Y_CODE
Yes
<UOM_PRICE_CURREN
CY_CODE>
A Zebra Printer Language (ZPL) template appropriate to the Oracle XML report
must be created and uploaded to the ZebraLink Enterprise Connector (ZEC)
zplrepository directory.
The ReportInfo.ini file must be configured appropriately.
Always refer to the ZebraLink Enterprise Connector for Oracle BI Publisher User Guide for
detailed explanations.
The user presses the Print button on the SIM interface (PC or wireless).
2.
SIM gets the printer selection from the user, if it is the first print request in the session.
For subsequent print requests, the printer defaults to the last-selected printer.
3.
SIM builds a report request comprising standard parameters such as logical name of the
report, selected printer name, locale and store ID in addition to any other report-specific
parameters, such as Stock Count ID.
4.
Using these request parameters, SIM constructs a report request and routes the request
using http to the pre-configured Reporting Tool Request URL (which points to the BI
Publisher installation URL).
5.
BI Publisher identifies the report, queries the database to get the data needed for the
report, formats the data, and sends the report to a destination (in this case, a logical
name of a printer that is pre-configured on BI Publisher).
6.
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 11
Solution Diagram
The ZebraLink Enterprise Connector Printing Solution has the ability to interpret and parse
XML. This translates into major time and cost savings for barcode label printing. Label
formats supporting various applications can be loaded into the Zebra Enterprise Connectors
ZPL repository, facilitating XML printing from Oracle BI Publisher.
The ZebraLink Enterprise Connector Printing Solution enables convenient, accurate barcode
and radio frequency identification label printing. Existing and new Oracle and Zebra
customers using Oracle Retail SIM now have the ability to move from their legacy barcode
label printing solutions by using the Zebra Enterprise Connector for all their barcode label
needs with Oracle Retail SIM.
Assumptions
The following must be completed:
ZebraLink Enterprise Connector for Oracle BI Publisher is installed and running on
the same host as Oracle BI Publisher. Refer to ZebraLink Enterprise Connector
documentation for installation and system requirements.
Zebra printer has been configured using CUPS on the host:
ZPL label template has been created. Zebra Designer for XML can be used to design
ZPL template files. Exported templates are uploaded to the ZebraLink Enterprise
Connectors ZPL Repository for processing during printing. ZebraLink Enterprise
Connector applies the ZPL template to an XML data stream to create the raw output
for the Zebra printer. So when creating a ZPL template, the dynamic variable names
should match the element names in the XML data. For example, variable
$$RETURN_ID$$ in the template should match <RETURN_ID> in the xml data. See
Zebra Designer for XML in ZebraLink Enterprise Connector for Oracle BI Publisher
User Guide.
The ReportInfo.ini configuration file in ZebraLink Enterprise Connector has been
configured for the ZPL template. This file is used to associate an XML root node to a
ZPL template; this tells ZebraLink Enterprise Connector which ZPL template to
apply for which XML root node. It also indicates the repeat node in the XML stream.
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 13
The repeat node is a repeating node in the XML stream that indicates to ZebraLink
Enterprise Connector the number of labels to print. An XSL might also be specified
here to transform the incoming XML stream before applying the ZPL template. See
ZebraLink Enterprise Connector for Oracle BI Publisher User Guide for configuration
details.
Where:
<store_id> is the id_str_rtl
rk_retail_store_printer_seq.nextval is the id_printer
2 is the printer_type
Zebra label printer is the printer_description
<printer_server_name_in_BIP> is the printer_network_address
Choose Data Template as type. Do not choose SQL Query. If SQL Query is chosen, the
output xml data will not be customized, it will be of the form:
<ROWSET><ROW><COLUMN1><COLUMN2>
2.
Use the data template to customize the xml to the form expected by ZPL label template
(ZPL template is the template for the label that will be created in ZebraDesigner):
2.
The server name should match the printer_network_address that was set up in SIM (see
Printer Configuration In SIM).
3.
Configure the custom filter for ZebraLink Enterprise Connector (see Configuring and
using Oracle BI Publisher in ZebraLink Enterprise Connector for Oracle BI Publisher User
Guide).
Using Oracle Virtual Directory to Authenticate Oracle Retail Store Inventory Management 15
Disclaimers
It is your responsibility to check and validate the details specified in this document before
implementing. You must verify the label content and check with your implementation
partner about the feasibility of the XML mapping outlined in this document. The details in
this white paper should be considered guidelines only and neither Zebra nor Oracle are
responsible for the correctness of the label or the mapping details. Neither Zebra nor Oracle
are liable for any losses or damage whatsoever you might have incurred by implementing
the mapping suggested in this document.
Conclusion
Missing label fields in the labels often call for costly customizations and longer
implementation life cycles. Custom label fields give you a powerful tool to model any
compliant label, there by eliminating the need for any customization.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright 2009, Oracle. All rights reserved.
This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.