Oracle® Retail Store Inventory

Management

Item Configuration
Release 13.2.4

April 2013
Note: The following is intended to outline our general
product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not
a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
 Contents
Item Configuration ............................................................................................................ 1
Item Transaction Levels .........................................................................................................1
UPC European Article Numbers ...................................................................................2
Trading Unit Code Barcodes ..........................................................................................3
Item Long Description ............................................................................................................3
Algorithm for Handheld Display ..................................................................................4
Reports .............................................................................................................................. 8
Pack Size ...................................................................................................................................8
Changing the Pack Size ...................................................................................................8
Pack Size RIB Integration ................................................................................................ 9
Standard Unit of Measure .................................................................................................... 10
Unit of Measure Rules ................................................................................................... 10
Standard Unit of Measure Conversion .............................................................................. 11
Master Data Setup Flow ................................................................................................ 11
Pack Items .............................................................................................................................. 14
Pack Item Types ............................................................................................................. 15
Pack Item RIB Integration ............................................................................................. 16
Simple Pack Conversion Items (Notional Packs).............................................................. 16
Item Master ..................................................................................................................... 17
All Inventory Transaction Dialogues .......................................................................... 17
Pack Item Stock-on-hand Indicator ............................................................................. 19
Backend Processing in SIM ........................................................................................... 19
Integration....................................................................................................................... 20
In Summary .................................................................................................................... 20
Use Case .......................................................................................................................... 21
Ranging Items ........................................................................................................................ 21
Adding Non-Ranged Items .......................................................................................... 22
Item Status ............................................................................................................................. 28
Active ............................................................................................................................... 28
Temporary (Q-status) .................................................................................................... 28
Discontinued .................................................................................................................. 28
Inactive ............................................................................................................................ 29
Deleted ............................................................................................................................ 29
Non-Sellable Items ................................................................................................................ 34
Pack Item ......................................................................................................................... 34
Type-2 Item Recognition ...................................................................................................... 35
Barcode Algorithms ....................................................................................................... 35
Barcode Algorithm Splicing ......................................................................................... 36
Weight Calculations ...................................................................................................... 38
Weight Application ....................................................................................................... 38
 Error Messages ............................................................................................................... 39
Non-Ranged Items ......................................................................................................... 40
Type-2 Item Integration ................................................................................................ 40
UPC-E Barcodes .................................................................................................................... 40
Converting UPC-E Barcodes to UPC-A Format ........................................................ 41
Generic Barcode Algorithm Splicing Process ............................................................ 41
Impacted Dialogues ....................................................................................................... 42
Error Messages ............................................................................................................... 42
Catch Weight Items – Definitions ................................................................................ 43
Catch Weight Items – Support ..................................................................................... 44
Non-Inventory Items ............................................................................................................ 44
Data Seeding ................................................................................................................... 45
Consignment and Concession Items .................................................................................. 45
Preventing Inventory Changes .................................................................................... 46
Exceptions – Allowing Consignment and Concession Items .................................. 47
Quick Response Codes ......................................................................................................... 48
SIM Usage of QR Codes ................................................................................................ 48
Quick Response Codes Store Parameters ................................................................... 49
Generating QR Tickets and Labels Information ........................................................ 49
Receiving QR Tickets and Labels Information .......................................................... 50
ItemTicket Batch Requirements ................................................................................... 50
Assumptions ................................................................................................................... 51

iii
 Item Configuration
There is functionality within the Store Inventory Management system related to item
configuration that spans across multiple functional areas or concepts that apply to the
application as a whole rather than to a specific functional area. This white paper covers
numerous topics around item configuration including:
 Item Transaction Levels
 Item Long Description
 Pack Size
 Standard Unit of Measure
 Standard Unit of Measure Conversion
 Pack Items
 Simple Pack Conversion Items (Notional Packs)
 Ranging Items
 Item Status
 Non-Sellable Items
 Type-2 Item Recognition
 UPC-E Barcodes
 Non-Inventory Items
 Consignment and Concession Items
 Quick Response Codes

Item Transaction Levels

Items are set up in Oracle Retail Merchandising System (RMS) and are assigned item
levels (1-3) based on how specific or general the Item ID is, with item level 1 being the
most general, and item level 3 being the most specific. For example:
 Strawberry Yogurt – Item Level 1
 Sugar-free Strawberry Yogurt – Item Level 2
 Sugar-free Strawberry Yogurt UPC – Item Level 3
The Transaction Level is the level at which inventory is tracked, and financial
transactions are made. This is also the level against which inventory transactions are
recorded. The transaction level is associated to one of the item levels of the item, usually
level 1 or level 2. For example:
Sugar-free Strawberry Yogurt is the transaction level item. Therefore, the transaction
level is 2. Since there can only be one transaction level per grouping, item level 1 and
item level 3 items would also have a transaction level of 2:
 When a reference is made to the transaction level item, this means that the
transaction level equals the item level.
 If you enter an item below the transaction level (for example, a UPC is entered), the
item is rolled up to the transaction-level item.
 If you enter an item above the transaction level (for example, a Grandparent item is
entered), the item is considered invalid.

Item Configuration 1
Item Transaction Levels

UPC European Article Numbers

UPC European Article Numbers (EAN) are most commonly set up one level below the
transaction level. For example, item level 3 is below item level 2. In the previous
examples, the transaction level is 2, and any barcodes for the transaction level item
(Sugar-free Strawberry Yogurt) would be set up as item level 3, transaction level 2. In
SIM, when an item is scanned that is a lower item level than the transaction level, for
example, a barcode, SIM rolls the item up to the transaction level item and displays that
in the item field.

Note: None of the barcode information is displayed to the

user. Only the transaction-level item information is
displayed.

If the user scans Item 300 EAN Sugar-free Strawberry Yogurt, Item 200 Sugar-free
Strawberry Yogurt would be displayed. Therefore, Item 200 would be the item that is
used for processing (transfers, receipts, and so forth). For example, for a Parent item with
Child, where Child has a UPC barcode:
 100 (Parent) – If the user enters Item 100, the system displays the message Invalid
Item.
 200 (Child) – If the user enters Item 200, the item is accepted. This is the transaction
level for all processing.
 300 (UPC) – If the user enters Item 300, the item is rolled up to item 200.

Item Description Item Level Transaction Level

100 Strawberry Yogurt 1 2

200 Sugar-free Strawberry 2 2
Yogurt
300 Sugar-free Strawberry 3 2
Yogurt UPC

Example 2, with a Grandparent, Parent, and Child/Grandchild:

 100 (Grandparent) – If the user enters Item 100, the system displays the message
Invalid Item.
 200 (Parent) – If the user enters Item 200, the system displays the message Invalid
Item.
 300 (Child/Grandchild) – If the user enters Item 300, the item is accepted. This is the
transaction level for all processing.

Item Description Item Level Transaction Level

100 Coke 1 3
200 Diet Coke 2 3
300 Christmas Coke 3 3

2 Oracle Retail Store Inventory Management

 Item Long Description

Trading Unit Code Barcodes

Trading Unit Code (TUC) barcodes are set up similar to UPC barcodes. In most cases,
they are set up one level below the transaction level. In the following example, since the
transaction level is level 1, the TUC barcode has an item level of 2. As with EAN
barcodes, SIM rolls up TUC barcodes to the transaction level item and displays the
transaction level item in the item field.

Note: None of the barcode information is displayed to the

user. Only the transaction level item information is
displayed.

Scan Item 500 TUC Six-pack Strawberry Yogurt. The user would see Item 400 Six-pack
Strawberry Yogurt. Therefore, Item 400 would be the item that is used for processing
(transfers, receipts, and so forth).

Note: Item 400 is a Parent to Item 500.

Item Description Item Level Transaction Level

400 Six-pack Strawberry 1 1

Yogurt
500 TUC Six-pack 2 1
Strawberry Yogurt

Item Long Description

When an item is created in RMS, it has two descriptions associated with it, a long
description and a short description.
The short description of an item is a product of the first twenty characters of the long
description. It is often used for Point-of-Service receipt printing, but does not always
offer enough detail to a user in helping to identify the item.
The long description is often used for display purposes in SIM since it can contain more
information. RMS concatenates the differentiator descriptions with the long item
description. The user is able to view all differentiator information in the long item
description display if the length parameter setting allows for it.
SIM allows the customer to choose between displaying the long item description and the
short item description on the PC and handheld.
The value of the description is determined by the system administration parameter
Display Item Description. If the parameter is set to Short Item Description, SIM
displays the Short Desc. field from RMS. This is often an abbreviated version of the RMS
long description and has a maximum value of twenty characters. If the parameter is set to
Long Item Description, SIM displays the long item description from RMS with a
maximum of 100 characters.
The user is able to scroll within each table on the PC to view the full description of the
item, whether the parameter is set to the short description or long description.
The item ID that appears preceding the item description field in Item Lookup always
displays the full item number.
The handheld screen has two lines dedicated to the item description field wherever item
ID and item description appear in the SIM application. The first line is reserved for the
RMS item description. Based on the Display Item Description parameter, either the
short description or long description is displayed.

Item Configuration 3
Item Long Description

The second line displays the differentiators associated with the item, and the length of
each differentiator description is determined by the Display HH Length: Diff x
parameter. The item description might wrap down to this line if there is space available
after the defined length of the differentiators are displayed.
There are two instances where a differentiator does not appear on the handheld. If there
are no differentiator values in RMS for the specified item, the differentiator field is blank.
If the Display HH Length: Diff x parameter is set to 0, the differentiator field is blank
and the space is freed up to display more of the item description.
If the item description wraps down to the second line where the differentiators are
located, a semi-colon ( ; ) separates the item description from the differentiator
descriptions. A single space separates each of the differentiators on the second line, for
example, Women’s Sweater;Red Medium Striped. The space is not included as part of the
character length defined in the system parameter.

Note: The space does not apply for differentiators displayed

as part of the long item description. These are separated by a
colon ( : ) as defined in RMS.

Where possible, a blank line separates the second line of the description field from the
next line containing data. Due to limited space, the Item Lookup screen does not allow
for a blank line separation. This results in a more crowded screen appearance, but allows
SIM to display all the necessary information on one page, rather than forcing the user to
navigate to a second screen to view additional information.

Algorithm for Handheld Display

The display of the description and differentiators on the handheld is calculated
dynamically to determine the best display option.
SIM sets the available space for each description based on the length defined in the
system administration parameter for the differentiator description lengths.
SIM allocates space to the item description on the first line. The first line is reserved only
for the item description, whether the user chooses to display the short description or the
long description. If the item description does not use all 21 characters on the first line, the
remaining available space is not allocated to the differentiator descriptions.
SIM then sets space for the differentiator descriptions based on the defined length in the
system administration parameter. Differentiator descriptions appear on the second line
only and are separated by a single space. The space is not included as part of the
character length defined in the system administration parameter.
If the Diff1 description is shorter than the defined length set in the system administration
parameter, the remaining space is given to the Diff2 description. Further remaining space
is then allocated to Diff3 and then Diff4.

Note: Diff1 will not be enlarged nor will it be possible to

allocate more screen space than the total sum of all the
system option differentiator lengths.

SIM allocates the remaining space to the item description. The differentiator descriptions
are right-justified on the second line so the item description can wrap down and use the
remaining available space.

4 Oracle Retail Store Inventory Management

 Item Long Description

If a user prefers to view the long item description instead of viewing the differentiator
descriptions, the user can set the differentiator parameter to 0. In this case, no
differentiator description is displayed, and the space is given to the long item
description.
RMS has differentiators integrated into its item description, so there could be a case
where the differentiators are displayed twice on the handheld. The differentiators are
concatenated to the end of the long item description. If the item has a very short
description assigned in RMS, the differentiator description could appear twice. For
example, Item Description = T-shirt. The associated differentiators are Red, Med, and
Solid. The differentiators are automatically added on to the end of the item description,
and because T-shirt is only seven characters long, the differentiators would appear as
part of the long description on the first line:
T-shirt:Red:Med:Solid
This long item description is short enough to fit on one line on the handheld. The second
line would then display the differentiator descriptions.
In the following example, the fourth differentiator does not display at all since the
parameter length is set to 0. The saved space on the first differentiator frees up space for
Diff2 and then Diff3. Based on the parameter settings, the differentiator descriptions use
a total of 15 characters, so the remaining available space is then given to the item
description.

System Administration Parameter Settings RMS Descriptions

 Display Item Description = Long  Long Item Description = Women’s

Description Cashmere Turtleneck
 Display Length: Diff1 = 5 Sweater:Red:Medium:Striped:Cashmere
 Display Length: Diff2 = 5  Diff1 = Red
 Display Length: Diff3 = 5  Diff2 = Medium
 Display Length: Diff4 = 0  Diff3 = Striped
 Diff4 = Cashmere

Handheld Screen Display

Item Lookup
100025176
Women’s Cashmere Turt
len;Red Medium Stripe
Subclass: Women’s
Price: 24.99
Inventory: 10 units
Pack Size: 1
On Order: 5 units
In Transit: 0 units
Rcv Today: 0 units
Promo Type:

1-Price History
2-Allocations
3-Related Items

Item Configuration 5
Item Long Description

In the following example, the user has set Diff3 and Diff4 to a length of 0. The user has
limited the number of characters to four each for Diff1 and Diff2. SIM only displays eight
characters total for the Diff1 and Diff2 descriptions.

System Administration Parameter Settings RMS Descriptions

 Display Item Description = Short  Short Item Description = Women’s Angora

Description Sweater
 Display Length: Diff1 = 4  Diff1 = Red
 Display Length: Diff2 = 4  Diff2 = Polka dot
 Display Length: Diff3 = 0  Diff3 = blank
 Display Length: Diff4 = 0  Diff4 = blank

Handheld Screen Display

Item Lookup
100025184
Women’s Angora Sweate
Red Polka
Subclass: Women’s
Price: 24.99
Inventory: 10 units
Pack Size: 1
On Order: 5 units
In Transit: 0 units
Rcv Today: 0 units
Promo Type:

1-Price History
2-Allocations
3-Related Items

In the following example, all differentiator parameters are set to 0. SIM maximizes the
available space by displaying the entire long description using both lines.

System Administration Parameter Settings RMS Descriptions

 Display Item Description = Long  Long Item Description = Women’s Angora

Description Sweater set:Red:Polka dot
 Display Length: Diff1 = 0  Diff1 = Red
 Display Length: Diff2 = 0  Diff2 = Polka dot
 Display Length: Diff3 = 0  Diff3 = blank
 Display Length: Diff4 = 0  Diff4 = blank

6 Oracle Retail Store Inventory Management

 Item Long Description

Handheld Screen Display

Receive Item

Order: 1234
2345670000 David Fash

100025184
Women’s Angora Sweater
Set:Red:Polka dot

Unit Cost: 1.00

Rec Qty: 1 units

In the following example, the long item description is being used. There are three
associated differentiators. The long item description is only 20 characters long, so the
entire description fits on the first line. The differentiators displays on the second line
(second line is only line for differentiators) based on the differentiator length parameter
settings.

System Administration Parameter Settings RMS Descriptions

 Display Item Description = Long  Long Item Description = T-

Description shirt:Red:Med:Crew
 Display Length: Diff1 = 5  Diff1 = Red
 Display Length: Diff2 = 5  Diff2 = Med
 Display Length: Diff3 = 5  Diff3 = Crew
 Display Length: Diff4 = 5  Diff4 = blank

Handheld Screen Display

Receive Item

Order: 1234
2345670000 David Fash

100025184
T-shirt:Red:Med:Crew
Red Med Crew

Unit Cost: 1.00

Rec Qty: 1 units

Item Configuration 7
Pack Size

Reports
All SIM reports default to display the short item description. The report view in the SIM
database includes both a long item description and a short item description field for all
reports. This allows the customer to customize the reports to display the long description
or short description.
When printing item tickets, the short description always displays. Items tickets was not
modified to include a long item description due to the limited space available on the
ticket or label.

Pack Size
The Pack Size represents the number of that item within a Case. The Pack Size is set up in
RMS when adding the supplier to the item. RMS terminology is Case Size. Case Size in
RMS is the same as Pack Size in SIM. Within SIM, the Pack Size for the primary supplier
is used if the supplier is unknown. Otherwise, SIM uses the pack size for the supplier
that is being used (Returns/DSD/Store Orders).

Note: When referring to the Default Case Size, this is the

Case Size defined on the item master, which is the item’s
primary supplier Pack Size.
Note: The Pack Size is not the number of component items
within a Pack Item, but rather the number of items within a
case (box). Pack Size is used for all types of items and packs.
If SIM is configured to allow it, the user can override the
pack size for all items and packs.

Many screens in SIM allow the user to enter an item quantity in both units and cases.
When entering an item quantity in cases, the user has the option of changing the default
Pack Size of the case. The Pack Size field is available when receiving Direct Store
Deliveries, creating transfers, creating returns, and performing inventory adjustments.
This feature allows the customer to disable the Pack Size column on the screens and
make the fields View Only.
A system administration parameter, Disable Pack Size, is used to disable and enable the
Pack Size throughout the SIM application on both the handheld and the PC.
 If the Disable Pack Size flag is enabled, the system allows the user to enter values
into the Pack Size fields throughout SIM.
 If the Disable Pack Size flag is disabled, the system does not allow the user to enter
values into the Pack Size fields throughout SIM. The Pack Size column does still
appear on the screens, but the user is not able to access the field (View Only).

Changing the Pack Size

When changing the pack size for a transaction, the expected result for the Quantity field
depends on when you change the Quantity field and the Pack Size field. For example, set
the Unit of Measure (UOM) system parameter to Cases:
1. Access a saved return with a return quantity of 10 for Item A, with a pack size of 1.

Note: The UOM is Cases. If you switch to Units, the return

quantity is also 10.

2. Switch to Cases.
3. Change the pack size to 2.

8 Oracle Retail Store Inventory Management

 Pack Size

Note: The quantity field has changed to 5. SIM calculates the

new quantity for Cases based on the new pack size of 2.

4. Switch to Units. The quantity is still 10 when displayed in units. The total quantity
for units does not change since only the pack size is changed.
5. Switch to Cases and change the quantity of cases from 5 to 10 (the pack size is still 2).
6. Switch to Units and the quantity is 20. The Units quantity was recalculated based on
the new Cases quantity with a pack size of 2.
Changing the pack size field only does not change the quantity of units. Changing the
quantity of cases does change the quantity of Units if the pack size is greater than 1.
The following PC screens currently display the Pack Size field, and are affected by the
configuration setting:
 Transfer Detail
 Direct Delivery Detail
 Return Detail
 Inventory Adjustment Detail
 Item Request Detail
 Store Order Detail

Note: Warehouse deliveries are an exception and the pack

size is not editable, as it is the Pack Size from the ASN.
Pack size is displayed on the Count/Recount Detail screen
but is not editable.

The following handheld screens currently display the Pack Size field, and are affected by
the configuration setting:
 Create Transfer Requests
 Edit Transfer Request
 Create Transfers
 Edit Transfer
 Receive Transfer
 Direct Delivery
 Returns
 Inventory Adjustment
 Item Requests

Pack Size RIB Integration

SIM receives all information coming from the RIB at the Each level. The pack size
displayed to the user is handled through the user interface in SIM, not at the database or
message level.

Item Configuration 9
Standard Unit of Measure

Standard Unit of Measure

The Standard Unit of Measure (SUOM) is the unit of measure by which stock is tracked
at the corporate level and for store inventory. The system administration parameter
Default UOM has values of Standard UOM or Cases (default cases). The Default UOM
parameter allows the store to select the UOM with which the store normally works. The
selected option defaults in the majority of the functional areas throughout the
application, with the exception of stock counts and Item Basket. Stock counts always
defaults to the standard unit of measure since most counts are performed in the SUOM.
The user is still has the ability to switch to Cases. Item Basket always defaults to the
selling UOM and the user is not able to switch to Cases.
 If the setting is SUOM, the system displays the quantities in the SUOM when initially
entering the affected screens throughout the SIM product. The user still has the
ability to switch the field and change the displayed UOM, if desired.
 If the setting is Cases, the system displays the quantities in Cases when an item is
entered on the affected screens throughout the SIM product. The default value of
Cases does not populate until an item is entered in the item field. The user still has
the ability to toggle the field and change the displayed UOM if desired.
If the user chooses to switch between Cases and SUOM in the UOM field, SIM saves
based on the Default UOM set in System Administration. For example, if the Default
UOM parameter is set to Cases and the user switches to Eaches within a transaction and
saves the transaction, SIM reverts back to Cases when accessing the transaction again.

Note: In older versions of SIM, if displaying cases resulted

in a decimal for the quantity, SIM displayed in SUOM
regardless of how the Default UOM parameter was set. This
is no longer the case as of SIM 13.2. SIM always displays
based on the system parameter, with the exception of stock
counts and Item Basket.

When switching between Cases and SUOM in a functional area that has an Old Qty field
and a New Qty field, both fields switch together so that both display Cases, or both
display the SUOM for the item.

Unit of Measure Rules

Consider the following rules for Units of Measure:
 If the SUOM is Eaches, the user has the option to choose Units or Cases from the
UOM drop down.
 If the SUOM is Eaches, the user is only able to enter a quantity in positive whole
numbers. It should not display in decimals. For example, 4 units, not 4.0 units. The
UOM also displays as units, not Eaches.
 Inventory can only be stored as whole units for Eaches.
 If the SUOM is different than Eaches, the options available in the UOM field should
be UOM and Cases.
 If the SUOM is different than Eaches, then depending on the UOM, the user is
allowed to enter a decimal value for the quantity. The quantity is restricted to a total
of four digits and three decimal places if decimals are allowed for that specific UOM.
 The SUOM should be displayed as the abbreviation as it is held on the table.
 The inventory is allowed to hold decimal values for those items that have a SUOM
other than units that allow for decimals.

10 Oracle Retail Store Inventory Management

 Standard Unit of Measure Conversion

 If switched to Cases, the Pack Size is displayed and the user is allowed to change it to
a whole value, even if the SUOM is different than Eaches.
 The Pack Size needs to be less than or equal to 9999. It is rounded to three decimals if
more than three decimal places are entered.
 The pack size cannot be changed from 1 if the UOM is set to the SUOM.

Example 1 – UOM as kg
An item has a UOM as kg, and has a case size of 15:
 If the UOM is set to kg, the quantity can have a decimal (15.5 kg), but the pack size
can only be 1 (1 kg).
 If the UOM is set to case, and the SUOM is set to kg, the pack size can only be set to a
whole value. The conversion to pack size can be decimal, but any updates made will
be as a whole number.

Example 2 – UOM as Eaches

An item has a UOM as Eaches, and has a pack size of 12:
 If the UOM is set to Eaches, the quantity can be 18 units and the pack size can only
be 1 (1 Each).
 If the UOM is set to Case, a quantity of 1.5 cases is displayed with a case size of 12.
However, the user is only able to change the pack size to a whole number, and the
quantity can only be updated to a whole number, for example, 18 units pack size
with a quantity of 1 or 2.

Standard Unit of Measure Conversion

SIM conducts all transactions in the Standard Unit of Measure (SUOM). The
merchandising system tracks various units of measure for each item like the Unit of
Purchase (UOP), that is, the unit of measure by which an item is purchased, or the selling
Unit of Measure, that is, the unit of measure by which an item is sold.
When SIM interacts or interfaces with external systems there is a need to convert from
one UOM to another. The following areas require conversion between units of measure:
 Direct Updates Point-of-Service Sales Posting
When sales are posted using ReSA, the sales audit system converts the units sold into
the SUOM. When sales are posted using the direct update interfaces directly from
Point-of-Service to SIM, SIM needs to convert between the selling unit of measure
and the SUOM, if the selling unit of measure is different from the SUOM.
 Customer Order
If customer orders are interfaced to SIM for reservation of inventory, the SUOM
might need to be converted since the information is likely provided in a selling unit
of measure.
 Point-of-Service Inventory Inquiry
Point-of-Service currently has the ability to query SIM to get the current inventory
position. SIM should convert the information returned to Point-of-Service to the
selling unit of measure.

Master Data Setup Flow

UOM conversion requires master data to flow down from RMS to enable the process
changes.

Item Configuration 11
Standard Unit of Measure Conversion

Updates to Item Master Data to Enable Conversion between Different Units of Measure
(UOM)

RMS UOM Conversion RIB UOM Conversion SIM

UOM Conversion
If the UOM on the transaction is not the same as the SUOM, the quantity is transformed
into the SUOM.
The conversion of quantity from one UOM to another is dependent on the UOM class.
If the UOM class of the selling UOM is the same as the UOM class of the SUOM, SIM
uses within-class conversion. The conversion factor for within-class conversion can be
obtained from the UOM transaction conversion table.
In the case of some items, for example, eggs, the SUOM would be Eaches, whereas the
selling UOM would be Dozen. Since both units of measure are quantity measures, the
conversion would be available in the UOM conversion table. For example:

Selling UOM = DOZ (Dozen) and Standard UOM = EA

Conversion factor = 1 Dozen = 12 Eaches
SOH before posting sale = 144 Eggs
Sale quantity = 1

After the sale quantity is updated, the stock-on-hand would be 132 eggs (144 – 12).
If the UOM class of the selling UOM is different from the UOM class of the SUOM, SIM
uses the between-class conversion. The conversion factor between-class conversion can
be obtained from the UOM transaction conversion table.
For items such as oil, the SUOM would be Barrels, but the selling UOM could be Liters.
Barrel is a pack measure and Liters is a measure of volume. The conversion needs to be
explicitly defined, and 1 Barrel could be defined to hold 55 liters. For example:

Selling UOM = Liters and Standard UOM = Barrels

Conversion factor = 1 Barrel = 55 Liters
SOH before posting sale = 2 Barrels
Sale quantity = 11 liters

After the sale quantity is updated, the stock-on-hand would be 2 – (11/55) Barrels, or 1.8
Barrels.
The exception is in case the UOM class is miscellaneous. In case of a miscellaneous UOM
class, the conversion factor can be obtained from the Item Supplier UOM table.
Miscellaneous classes are used to define conversions specific to an item or supplier. For
example, gift baskets are sold as Baskets of items, but are inventoried as Containers of 15
baskets. For example:

Selling UOM = Basket and Standard UOM = Container

Conversion factor = 1 container = 15 Baskets
SOH before posting sale = 2 Containers
Sale quantity =6 Baskets

After the sale quantity is updated, the stock-on-hand would be 2 – (6/15) Containers, or
1.6 Containers.

12 Oracle Retail Store Inventory Management

 Standard Unit of Measure Conversion

Note: This UOM conversion is based on the conversion used

in RMS 12.0. The conversion calculation needs to reflect the
current calculations used in ReSA and RMS to prevent
systematic variations due to rounding errors.

Validation Requirements
Consider the following validation requirements for Units of Measure:
 Conversion between a UOM class of quantity to a UOM class of dimension, area or
volume requires the UOM of length/width/height be defined for the item.
 Conversion between a UOM class of dimension, area or volume to a UOM of
quantity requires the UOM of length/width/height be defined for the item.
 Conversion from a measure of quantity to a measure of mass requires the UOM of
weight be defined for the item.
 Conversion from a measure of mass to a measure of quantity requires the UOM of
weight be defined for the item.
 Conversion from a measure of quantity to a measure of liquid volume requires the
UOM of liquid volume be defined for the item.

Integration Requirements
The UOM conversion process requires the integration between RMS and SIM to include
interfaces, which communicate the master data required to carry out the UOM
conversion.
SIM undertakes a UOM conversion for transactions involving Point-of-Service. Point-of-
Service records all transactions in the selling UOM, while SIM maintains all stock
positions in the SUOM. In case the selling UOM and the SUOM are different, SIM needs
to convert between the two units of measure before any inventory can be impacted.
The following attributes are required to effect conversion between the different units of
measure:
 Type of unit of measure (also class of unit of measure).
 Conversion factor required to convert from a given UOM to a target UOM for in-
class conversions.
 Conversion factor required to convert from a given UOM to a target UOM for across-
class conversions.
 Item supplier units of measure, required to convert units of measure of the
miscellaneous class.
 Item supplier dimensions, including units of measure for length, width, height,
weight and volume. SIM subscribes to the ISCDim feed which is part of the current
item feeds published by RMS.

Example 1 – Selling Versus Standard UOM

A watermelon is purchased and tracked by the kilogram, but sold by the Eaches.
Consider that 0.25 kg is the equivalent of 1 Each, as defined on a per-item basis in RMS.
Store A currently has 250 kg of watermelon in inventory. If 45 watermelons are sold on a
given day at Store A, the inventory would be reduced to 238.75 kg:

45 Eaches * .25 kg = 11.25 kg

250 kg – 11.25 kg = 238.75 kg

Item Configuration 13
Pack Items

The conversion from 45 Eaches to 11.25 kg would take place in ReSA, so the sales file
processed by SIM would contain the 11.25 kg.

Example 2 – Case Ordering

Carpet is sold and inventoried by the meter, but purchased in 30 meter rolls. The SUOM,
as defined at the item level in RMS, would be Meter. A supplier’s Pack Size, or Case Size,
can be defined at the item/supplier/country level in RMS. Rolls of carpet would be set
up with a Pack Size of 30. When ordered, carpet could be ordered using this pack size
(30), and then received into inventory by individual meter. Sales would decrement the
total inventory by meter since carpet is being both sold and inventoried at the meter
level.

Example 3 – Simple Pack

Tiles are usually sold in a pack of 10, but in exceptional circumstances can be broken up
to allow a customer to purchase two individual tiles. In this instance, the individual tile
would be set up as an Eaches item in RMS, and the pack of 10 tiles would be set up as a
Simple Sellable Pack. Inventory is held against the individual tile in RMS, and ISO allows
the scanning and capture of stock quantities at the simple pack level.

Pack Items
A Pack is an item that contains component items. Simple Packs contain only one
component item. Complex Packs contain multiple different items. When these packs are
set up, the component items are specified, along with the number of component items
contained in the pack.
Simple Pack:

Pack Pack Description Component Item Component Qty

700 Six-pack Coke 100 – Single Coke 6

In the simple pack:

 Ordering 1 unit of Pack 700 would mean the user is ordering one Six-pack which
contains six units of 100 – Single Coke.
 Ordering 5 units of Pack 700 would mean the user is ordering five Six-packs for a
total of 30 units of 100 – Single Coke.
 Ordering 1 case (pack size 10) of Pack 700 would mean the user is ordering one case
that contains 10 of Pack 700, which would be 10 Packs, or 60 units, of 100 – Single
Coke.
 Ordering 5 cases of Pack 700 would mean the user is ordering five cases that each
contain 10 of Pack 700, which would be 50 Packs, or 300 units, of 100 – Single Coke.
Complex Pack:

Pack Pack Description Component Item Component Qty

900 Hair Multi Pack 200 –Shampoo 1

300 – Conditioner 1

14 Oracle Retail Store Inventory Management

 Pack Items

Pack Item Types

Transactions in SIM that require an item entry have the following rules:
 Non-Sellable Simple Packs – Inventory is tracked at the component level. Inventory
is not tracked for the pack item.
For example, if a return transaction contains Pack A with a return quantity of 2, and
Pack A is made up of 3 units of Item B, then when the return is dispatched, the stock-
on-hand at the sending store for Item B is decremented by 6 (2 packs of A, multiplied
by 3 units of B).
 Non-Sellable Complex Packs –Inventory is tracked at the component level.
Inventory is not tracked for the pack item.
For example, if a return transaction contains Pack A with a return quantity of 2, and
Pack A is made up of Item B and Item C, then when the return is dispatched, the
stock-on-hand at the sending store for Item B is decremented by 2 (2 packs of A,
multiplied by 1 unit of B), and Item C is also decremented by 2.
 Sellable Simple Packs – The user is allowed to enter this type of pack on inventory
transactions. Sellable packs can be treated like other sellable items. Inventory is
tracked at the pack level.
For example, if Pack A is a sellable pack, and a return is dispatched with a return
quantity of 5, then the stock-on-hand at the sending store for Pack A is decremented
by 5.
 Sellable Complex Packs – The user is allowed to enter this type of pack on an
inventory transaction. Sellable packs can be treated like other sellable items.
Inventory is tracked at the pack level. Sellable complex packs should have the same
stock movement as the sellable simple pack.
 Notional Packs – All inventory is held at the component level for both sellable and
non-sellable notional packs. See Simple Pack Conversion Items (Notional Packs) for
backend processing details.
 Since a pack always has a UOM as each, all packs (complex or simple, sellable or
non-sellable) should be able to adjust the Pack Size if the dialogue allows it. For more
information see Pack Size. The Pack Size is the number of Packs within a Case.
For example, Pack A contains 1 Shampoo and 1 Conditioner. The Pack Size is 100.
The Pack Size means that there are 100 of Pack A in a Case (100 Shampoo and 100
Conditioner).

Example in Transfers
 Scan item 100 – Single Coke. The display indicates Item 100, Pack Size of 96.
 Scan item 200 – EAN Christmas Coke. The display indicates Item 100, Pack Size of 96.
Because Item 200 is a barcode and not a transaction level, it rolls up to Item 100. Pack
Size of 96 represents 96 single Cokes in a case.
 Scan item 700 – Six-pack Coke. The display indicates Item 700, Pack Size of 24. Pack
Size 24 represents the number of 700 – Six-pack Cokes in a case.

Note: Pack Size of 24 displays based on the Pack, not on the

Pack Size of 96, which is the component.

 Scan item 800 – TUC Six-pack Christmas Coke. The display indicates Item 700, Pack
Size of 24. Because Item 800 is a TUC barcode and not a transaction level, it rolls up
to Item 700. Pack Size of 24 represents the number of 700 – Six-pack Cokes in a case.

Item Configuration 15
Simple Pack Conversion Items (Notional Packs)

Note: Pack Size of 24 displays based on the Pack, not on the

Pack Size of 96, which is based on the component.

Component Item:

Item Description Item Level Transaction Level Pack Size

100 Single Coke 1 1 96

200 EAN Christmas 2 1
Coke
Pack Item:

Item Description Item Level Transaction Level Pack Size

700 Six-pack Coke 1 1 24

800 TUC Six-pack 2 1
Christmas Coke

Pack Item RIB Integration

RMS publishes pack items to SIM, and subscribes to transactions with pack items coming
from SIM.
RMS subscribes directly to the pack item being communicated in the message and
handles this information as required:
 Transfer Dispatch (ASN Out)
 Receipt of Direct Delivery, existing PO (Receipt)
 Receipt of Direct Delivery, new PO (DSD Receipt)
 Receipt of Warehouse Delivery (Receipt)
 Receipt of Transfer (Receipt)
 Return to Vendor (RTV)
 Return to Warehouse (ASN Out)
 Inventory Adjustments (InvAdj)
SIM publishes the pack item, and RMS handles this information to its components so
other external systems do not have to handle this complex logic.
When SIM updates the inventory after receiving a pack item, SIM checks to see if the
item is orderable only, not sellable. If it is, then it is broken down to its components, and
the stock-on-hand is updated for each component. Sellable items are stored in SIM at the
Pack Item level.

Simple Pack Conversion Items (Notional Packs)

Some customers have several items within a product assortment, where different retail
prices are offered to the customer depending on the UOM purchased. For example, an
item can be sold in Eaches, Packs or in mass quantities:
 Rebar iron – can be purchased as a Ton, and sold either as an Each, a Bundle or a
Ton.
 Carpet – can be purchased as a Roll, and sold by the square meter, with a cost per
meter.

16 Oracle Retail Store Inventory Management

 Simple Pack Conversion Items (Notional Packs)

 Chain – can be purchased as a Spool, and sold by the length, with a cost per meter.
 Wire – can be purchased as a Spool, and sold by the length, with a cost per meter.
 Nails – can be purchased by weight, and sold by the Box (kg) or individual piece.
 Screws – can be purchased by weight, and sold by the Box (kg) or individual piece.
SIM holds the inventory at the component level so each inventory transaction impacts the
component stock-on-hand, regardless of which item is used for the transaction.

Note: SIM is integrated with RMS to obtain the indicator that

is held at the Item Master level in RMS. The indicator name
in RMS is Notional Pack.

Item Master
To understand which simple packs need to be broken down, SIM has an item-level
indicator that comes from RMS with the other item attributes.

All Inventory Transaction Dialogues

The user is able to scan in the simple pack item, but when the transaction is confirmed,
SIM updates the stock-on-hand of the component only. The transaction is published to
RMS and RWMS at the pack level that was scanned.
This functionality works very similar to orderable-only items. When an orderable-only
pack is received in SIM, it is automatically broken down to its components.
The affected dialogues are:
 Inventory Adjustments
 Stock Counts
 Transfers
 Warehouse Deliveries
 Returns
 DSD
 Receiver Unit Adjustments
This functionality fits the grocery requirement of breaking down simple packs in the
store by a customer. For example, cigarette cartons, 12-packs of Coke, and so forth all fit
this model.
The Simple Pack Conversion indicator is displayed on the Item Lookup Detail screen and
controls whether or not a simple pack item is broken down to its component items for all
inventory transactions. If the indicator is selected, SIM breaks the item down to the
components, and all inventories are held at the component level. If the indicator is not
selected, inventory is held at the pack level and the pack is not broken down.
Simple packs, or any item which is not orderable, should not be able to be added to DSDs
or Store Orders for suppliers.
The user is prompted with a message that the item is being substituted with the pack
item’s component item when entering these simple packs in Sequencing, Stock Counts
and Product Groups.

Item Configuration 17
Simple Pack Conversion Items (Notional Packs)

Process Flow

Subscribe to Multi
Unit Price indicator
in RMS

Display new
indicator on Item
Lookup Detail
screen in SIM

Is the indicator
Yes checked? No

SIM breaks pack

down.
All inventory All inventory
movement occurs movement occurs
at component level at pack level.
(backend
process).

PC Flow

Main Menu

Lookups Item Lookup Search for item

Item Detail screen

Display Simple
Pack Conversion
checkbox

18 Oracle Retail Store Inventory Management

 Simple Pack Conversion Items (Notional Packs)

Pack Item Stock-on-hand Indicator

Although the items are tracked at their component levels, in some cases the retailer may
want to see the calculated value of packs that is possible with the components on hand.
SIM is integrated with RMS to obtain an indicator that controls whether or not the pack
item-calculated stock-on-hand displays in Item Lookup and can be used for Inventory
Inquiries/Web service for notional packs.
The name of the RMS indicator is SOH Inquiry at Notional Pack Level:
 If the indicator is not set in RMS, the inventory fields display as Null for the pack.
 If the stock-on-hand indicator is set in RMS and the Simple Pack Conversion
indicator is selected, then when the user looks up the pack item in Item Lookup, SIM
displays the rolled up simple pack quantity based on the component item’s stock-on-
hand.
This is a calculated value based on the number of components that make up the pack. In
the Web service message for the inventory inquiry, a message indicates the stock-on-
hand for the pack item is a calculated value. In Item Lookup, a tilde character (~) displays
next to each applicable inventory bucket to indicate it is a calculated value based on the
component item’s stock-on-hand. For example:
 Simple Pack Conversion indictor is selected.
 RMS indicator is set to display calculated pack item stock-on-hand.
 Component SOH = 1200 units
 Simple Pack = 12 components per pack
If the user looks up the pack item in Item Lookup, SIM displays SOH = ~100 for the pack
item. The component Stock-on-hand (1200) is divided by the number of components for
the pack (12):

1200÷12 = 100

If an inventory inquiry is sent from the Web service, SIM converts the component item’s
stock-on-hand by dividing it by the number of units in the pack item to get a calculated
value for the pack item’s stock-on-hand.

Backend Processing in SIM

If the indicator is set to allow the breakdown of the simple pack, SIM breaks the simple
pack down to the component level item and update the stock-on-hand only for the
component item.
Wherever the user is able to enter or add an item in the SIM application, the user is able
to enter at the pack item level. SIM breaks the item down to the component level on the
back end.
 Backend processing converts the pack item to the component level by taking the
transaction quantity and multiplying it by the number of component items that make
up the pack.
 Depending on the type of transaction, the stock-on-hand is updated with the increase
or decrease.
For example, Item 1000 Bottle of Coke. Component item 1000 can be sold individually as
an Each or as part of a simple pack:
 Item 1001 Pallet of Coke – orderable-only simple pack (pallet = 1000 component
UOM)
 Item 1002 24-pack Coke – simple sellable pack

Item Configuration 19
Simple Pack Conversion Items (Notional Packs)

 Item 1003 12-pack Coke – simple sellable pack

 Item 1004 Six-pack Coke – simple sellable pack
When a transaction occurs for the pack item, SIM multiplies the transaction quantity by
the number of component items that make up the pack and decrement or increment the
component item’s stock-on-hand by that quantity.
When a Return to Warehouse occurs for 10 units of component Item 1002 24-pack Coke,
the stock-on-hand of the component item at the store decreases by 240 Eaches (24 x 10).
When a sale occurs for 10 units of component Item 1000 Bottle of Coke, SIM updates the
stock-on-hand of the component item, which is decreased by10.

Transaction Transaction Transaction Component Component Component

Type Item Quantity Item Quantity Stock-on-
hand

Sale Item 1000 10 Item 1000 10 decreases

Bottle of Coke
Receive Item 1001 10 Item 1000 10,000 increases
Pallet of Coke
Return to Item 1002 24- 10 Item 1000 240 decreases
Warehouse pack Coke
Transfer Ship Item 1003 12- 10 Item 1000 120 decreases
pack Coke
Transfer Item 1003 12- 10 Item 1000 120 increases
Receive pack Coke
Direct Item 1004 Six- 10 Item 1000 60 increases
Delivery pack Coke

Integration
All outbound integration messages are sent at the same level at which the transaction
was saved.
Inbound messages in general are kept at the item level they are interfaced with the
exception of sales. The SIM sales file parser breaks inventory down to its components
after receiving the item from ReSA.
For Point-of-Service, the Item Inquiry Web service indicates which values are calculated
approximations, and which quantities are not. When the user looks up the pack item in
Item Lookup, SIM displays the rolled up simple pack quantity based on the component
item’s stock-on-hand if the Simple Pack Conversion indicator is selected. With the
Inventory Inquiry Web service, SIM calculates the approximate value of the stock-on-
hand, available quantity, shop floor, back room and unavailable quantity. The Web
service should indicate if the value is a calculated value or a real value.

In Summary
Consider the following assumptions about pack items:
 Only simple packs are broken down automatically based on the RMS item setting.
This functionality does not apply to complex packs.
 SIM does not aggregate up the available stock-on-hand to the simple pack when
viewing the higher level simple pack information.
 When integrating SIM over a Web service for a simple pack that is broken down, SIM
returns a stock-on-hand of Null.

20 Oracle Retail Store Inventory Management

 Ranging Items

 Pack items can be set up in sequencing and be extracted for stock counts, but they do
not have any inventory.
 The SIM sales file parser breaks down the simple pack, as this is not performed by
ReSA.
 For Pick Lists, assume that the item is always replenished at the component level,
which is turned into simple packs in RMS.
 For inventory inquiries, no conversion is done for the simple pack to calculate an
approximate pack quantity.

Use Case
Consider the following use cases for pack items:
 Item 123 – Rebar, single piece (can be sold as Eaches).
 SUOM = EA
 One item = 10 kg
 Assumes stock-on-hand of the item is stored in fractional quantities
 Has its own retail
 Orderable Pack 456 – Orderable only, and represents the normal purchasing quantity
(1 Ton). When received, SIM and RMS hold the inventory in terms of the component
item (single piece of rebar).
 Item 123
 Component quantity = 100 EA
 Sellable Pack ABC (sold as a bundle of 10 Eaches) – Can have as many of these as
needed to support individually priced bundles.
 Item 123
 Component quantity = 10 EA
 Has its own retail
 Sellable Pack XYZ (sold as weight) – This is a pack where the component item is a
fractional quantity of the base item.
 Item 123
 Component quantity = 0.1 EA (1 kg)
 Has its own retail
 Orderable Pack 456 gets broken down to components in SIM (Item 123).
 ReSA needs to take sellable packs to component level MOD.
 Item 123 can be sold as individual pieces at its own price (selling UOM = EA).
 Item ABC can be sold as a pack with its own price (selling UOM = EA).
 Item XYZ can be sold by weight (for example, 1,350 kg), which decrements the
quantity of Item 123 by 135 pieces.

Ranging Items
A ranged item is an item that has an item/location relationship. Before an item can be
used by a store in SIM, the item must be ranged. SIM allows the user to enter non-ranged
items. A non-ranged item is an item that does not have an item/location relationship for
the store. Ranging an item depends on two factors: the item host system (for example,
RMS), and whether SIM allows for the ranging of items.

Item Configuration 21
Ranging Items

Once an item is ranged, SIM can allow the user to use these items in a functional area
depending on the status:
 Stores need the ability to move items out of the store that are not ranged to the store.
 Stores need the ability to receive non-ranged items into the store.
 Stores need to be able to look up items that are non-ranged.
 The non-ranged functionality exists in functional areas where an item is added and
the transaction is being sent out of the store.
An item is ranged in SIM when RMS sends the item/location relationship. If this
relationship does not exist, then it is not possible to use this item for any inventory
actions, such as receiving, transfers, returns, stock counts, or inventory adjustments.

Note: It is possible to use a non-ranged item to perform a

lookup or to print price labels.

The Item Lookup screen includes a checkbox to include non-ranged items when
searching for items.
A system parameter called Allow Non-Range Item determines whether an item can be
ranged in SIM. This system parameter gives stores the ability to add non-ranged items to
functional areas in the application. If this system option is set to No, then ranging is not
allowed and can only be done through the host system (RMS).
If the system parameter is set to Yes, then SIM allows the temporary ranging of an item.
This provisional ranged item has the same functionality as a ranged item with an Active
status, with the exception of Price Changes, Store Orders and Item Requests. These areas
do not allow for the ranging of items regardless of how the Allow Non-Range Item
parameter is set. SIM can only provisionally range items since an official response needs
to come back from the host system with all the pertinent item details. The default setting
for this parameter is Yes.

Adding Non-Ranged Items

If the user attempts to add a non-ranged item to a transaction, the following error
message is displayed:

The item is not ranged at this location, would you like to range the item?

Click Yes to create an item/location record with a status of Q (temporary). Click No to

clear out the item. No relationship is created.
If the system parameter Allow Non-Range Item is set to Yes and the user selects to add
the non-ranged item, SIM temporarily ranges the item. However, the item is not officially
ranged until RMS ranges the item.
If the user attempts to add this same item again at a later time, the user is not asked again
if they want to add the non-ranged item. The item is already in Q (temporary) status and
is considered to be ranged, and therefore the message prompt is not displayed. SIM
allows the item to be added immediately.
Price Changes, Item Requests and Stores Orders do not allow non-ranged or Q
(temporary) status items to be added under any circumstance due to corporate control. A
hard prompt is displayed if the user attempts to add the item in these functional areas.

22 Oracle Retail Store Inventory Management

 Ranging Items

SIM PC Non-Ranged Item Areas

Area Process Action Result

Direct Delivery: Add Item User adds a non-ranged item. Yes – Add item and
Direct Delivery Detail Button Soft Warning: create the
The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Warehouse Delivery: Add Item User adds a non-ranged item. Yes – Add item and
Receive Case Button Soft Warning: create the
The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Transfer In: Receive Add Item User adds a non-ranged item. Yes – Add item and
Transfer Button Soft Warning: create the
The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Transfer Out: Create Add Item User adds a non-ranged item. Yes – Add item and
Transfer SIM checks whether the item create the
is ranged at both locations. If item/location record in
the sending location is non- Q status.
ranged, a Soft Warning: No – Clear out the item
The item is not ranged and do not create the
at the sending location, relationship.
would you like to range
the item?
If the receiving location is
non-ranged, a Soft Warning:
The item is not ranged
at the receiving
location, would you like
to range the item?
If not ranged at both sending
and receiving locations,
prompt first with a message
for sending store and then
receiving store.

Item Configuration 23
Ranging Items

Area Process Action Result

Transfer Requests: Add Item User adds a non-ranged item. Yes – Add item and
Transfer Request SIM checks whether the item create the
Detail is ranged at both locations. If item/location record in
the sending location is non- Q status.
ranged, a Soft Warning: No – Clear out the item
The item is not ranged and do not create the
at the sending location, relationship.
would you like to range
the item?
If the receiving location is
non-ranged, a Soft Warning:
The item is not ranged
at the receiving
location, would you like
to range the item?
If not ranged at both sending
and receiving locations,
prompt first with a message
for sending store and then
receiving store.
Returns: Return Add Item User adds a non-ranged item. Yes – Add item and
Detail Soft Warning: create the
The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Inventory Add Item User adds a non-ranged item. Yes – Add item and
Adjustment: Inv Adj Soft Warning: create the
Detail The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Stock Counts: Add to Group User adds a non-ranged item. Yes –The item/loc
Counting Group for Item level. Soft Warning: relationship is NOT
Detail for all Types of The item is not ranged created. The user must
Groups at this location, would then select Add to
you still like to use Group button to
the item? actually add the item.
For all store Groups or No – Clear out the
individual store Groups, the item.
user is able to add any item to
the group.
Item Requests Add item User adds a non-range/Q User clicks OK. The
status item. Item is not item location
ranged and cannot be added. relationship is not
created.
Store Orders Add item User adds a non-range/Q User clicks OK. The
status item. Item is not item location
ranged and cannot be added. relationship is not
created.

24 Oracle Retail Store Inventory Management

 Ranging Items

Area Process Action Result

Sequencing Sequence Item User sequences a non-ranged Yes – Add item and
item. create the
The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Price Changes Enter Item User enters a non-ranged User clicks OK. The
item. item location
The item is not ranged relationship is not
at this store and cannot created.
have its price changed.
Item Tickets: Item Enter Item User enters a non-ranged Yes – Add item and
Ticket Detail item. create the
The item is not ranged item/location record in
at this location, would Q status.
you like to range the No – Clear out the item
item? and do not create the
relationship.
Filter Screens Filter Item Do not prompt with any error
message.

Item Lookup: Enter Barcode User enters non-ranged or SIM looks up that item.
of Item. ranged item. User is allowed to look
up non-ranged items.

Item Location Status and Stock Count Extraction – Stock Count Non-Ranged Matrix
Stock Count Active Q Status Non- Action
Type (ranged) (pseudo- Ranged
ranged)

Unit Only Y Y N User is allowed to add non-ranged and

Q-status items to the Product Group.
Batch should only break those items
down that match the Item Status and
SOH criteria set up on the Product
Group Detail screen.
Unit & Y Y N Unit & Amount can only add
Amount hierarchies to groups.
Batch should only break those items
down that are Active, Discontinued, or
Temporary ranged for the scheduled
stores, or that have inventory different
than 0 for Inactive or Deleted.
Allowed to scan non-ranged items that
were not extracted, and add them to
the Unit & Amount count.

Item Configuration 25
Ranging Items

Stock Count Active Q Status Non- Action

Type (ranged) (pseudo- Ranged
ranged)

Ad hoc Y Y Y Allowed to enter any item. Non-

ranged/Q status message:
The item is not ranged at this
location, would you like to add
it to the stock count?
User can click Yes or No.
Problem Line Y Y N User is allowed to add non-ranged and
Q-status items to the Product Group.
Batch looks for those items on problem
line product group that are
problematic and put them on the stock
count.
Note: Non-ranged items are not on the
stock count, because they are never
problematic.

SIM Handheld Non-Ranged Item Areas

Area Process Action Result

Returns: Item Entry: User enters a non-ranged Yes – Add the item and
 Create Return Scan Barcode item. Soft Warning: create the
of Item The item is not ranged, item/location record in
 Add/Edit Return
would you like to range Q status.
the item to this store? No – Return user to
item entry screen.
Transfer In: Receive Item Entry: User enters a non-ranged Yes – Add the item and
Transfer Scan Barcode item. Soft Warning: create the
The item is not ranged, item/location record in
would you like to range Q status.
the item to this store? No – Return user to
item entry screen.
Transfer Out: Item Entry: User adds a non-ranged item. Yes – Add the item and
 Create Transfer Scan Barcode SIM checks whether the item create the
of Item is ranged at both locations. If item/location record in
 Edit Transfer
either location is non-ranged, Q status.
a Soft Warning: No – Return user to
The item is not ranged, item entry screen.
would you like to range
the item to this store?
Transfer Requests: Item Entry: User adds a non-ranged item. Yes – Add the item and
 Create Transfer Scan Barcode SIM checks whether the item create the
Request is ranged at both locations. If item/location record in
either location is non-ranged, Q status.
 Edit Transfer
a Soft Warning: No – Return user to
Request
The item is not ranged, item entry screen.
would you like to range
the item to this store?

26 Oracle Retail Store Inventory Management

 Ranging Items

Area Process Action Result

Item Lookup Scan Barcode User scans in a non-ranged or SIM looks up that item.
of Item. ranged item. User is allowed to look
up non-ranged items.

Warehouse Delivery: Receive Case: User enters a non-ranged Yes – Add the item and
Receive Case Item Entry – item. Soft Warning: create the
Scan Barcode The item is not ranged, item/location record in
would you like to range Q status.
the item to this store? No – Return user to
item entry screen.
Direct Delivery Item Entry: User enters a non-ranged Yes – Add the item and
Scan Barcode item. Soft Warning: create the
The item is not ranged, item/location record in
would you like to range Q status.
the item to this store? No – Return user to
item entry screen.
Inventory Item Entry: User enters a non-ranged Yes – Add the item and
Adjustment Scan Barcode item. Soft Warning: create the
The item is not ranged, item/location record in
would you like to range Q status.
the item to this store? No – Return user to
item entry screen.
Item Requests Add item User adds a non-ranged/Q- User presses Enter. The
status item. Item is not item location
ranged and cannot be added. relationship is not
created.
Item Tickets: Item Enter Item User enters a non-ranged Yes – Add the item and
Ticket Detail item. Soft Warning: create the
The item is not ranged at item/location record in
this location, would you Q status.
like to range the item? No – Clear out the item
and do not create the
relationship.
Item Basket Scan Item User enters a non-ranged Yes – Add the item and
item. Soft Warning: create the
The item is not ranged at item/location record in
this location, would you Q status.
like to range the item? No – Clear out the item
and do not create the
relationship.
Sequencing Sequence Item User sequences a non-ranged Yes – Add the item and
item. Soft Warning: create the
The item is not ranged at item/location record in
this location, would you Q status.
like to range the item? No – Clear out the item
and do not create the
relationship.

Item Configuration 27
Item Status

Item Status
Each ranged item has a status for the location it is ranged to. Different rules apply in
different transactions, based on the state of the item.
For example, SIM prompts the user when receiving an item if the item is in Discontinued,
Inactive or Deleted status.
If an item location has a status of Discontinued, Inactive or Deleted and the user is trying
to receive the item (unexpected or not), the user is prompted with the following message:

The item is <status>, are you sure you want to use the item?

The message indicates the user can select Yes or No. If the user selects Yes, the item is
added. If the user selects No, the item is not added to the transaction and the item is not
received.
SIM checks the status upon receiving to account for items that were active upon
shipping, but that have been inactivated or deleted after the order was shipped, before
the items were received at the store.
Inactive and Deleted status items can always be transferred out of a store as long as the
item is not Inactive or Deleted at the destination store. Discontinued items can always be
transferred out of a store. It is common for retailers to transfer discontinued items to
stores where they might sell faster.
 If an item is inactive at the destination store, the user is prompted with a message
that the item is inactive at the destination store and cannot be added.
 If an item is deleted at the destination store, the user is prompted with a message that
the item is deleted at the destination store and cannot be added.
Discontinued, Inactive or Deleted items can be added to Returns. SIM must allow the
retailer to return these items to the vendor/supplier or warehouse.

Note: A soft prompt is not needed for RTW/RTV when

returning Discontinued, Inactive or Deleted items.

Active
No functional restrictions exist for the item. Every function in SIM can be performed with
this item, including receiving, transfers, returns, stock counts, orders, and so forth.

Note: Stock counts are assumed to be all types of Unit and

Amount, Unit Count, Ad Hoc and Problem Line.

Temporary (Q-status)
When SIM ranges an item, the item is assigned the status of Q. This status is equivalent to
Active, meaning SIM treats the item as though it is an active item. An item can move to
this status in most functional areas in SIM with the exception of Price Changes, Item
Request and Store Orders.

Discontinued
Discontinued items cannot be ordered from the supplier, but they can be transferred in
from a warehouse or store. Discontinued items can appear on stock counts. It is possible
to ship discontinued items to a finisher.
There are no restrictions with the exception of creating a PO.

28 Oracle Retail Store Inventory Management

 Item Status

Inactive
An inactive item cannot be ordered from a supplier, for example, through an Item
Request or a Store Order. An inactive item cannot be transferred in from a warehouse or
store if the receiving location is inactive or deleted for the item. All other transfers are
acceptable.
Inactive and Deleted items are not allowed for finishers.
If the item is part of a delivery (DSD/Warehouse Delivery), the user is able to receive the
item or add the item if it was not on the transaction. The user is prompted with a
message saying that the item is inactive. The user is allowed to receive inactive or deleted
items on a transfer, but cannot transfer out items that are inactive at the destination store.
Returns (RTW/RTV/return to supplier) are possible.
It is not possible to order an inactive item or create an item request for an inactive item.
It is possible to create price changes and promotions for these items.

Note: Inactive items have almost the same functionality as

deleted items. This is because an inactive item is severely
restricted. The difference is that inactive items can have
permanent price changes and promotions. A deleted item
cannot have permanent price changes and promotions.

Deleted
A deleted item cannot be ordered from a supplier. Deleted items are prohibited on Item
Requests and cannot be transferred out from a warehouse or store if the receiving
location is in Delete status. All other transfers are acceptable.
If the deleted item is part of a delivery (DSD/Warehouse Delivery), the user is able to
receive the item or add the item if it was not on the transaction. The user is prompted
with a message saying that the item is deleted. A user is allowed to receive deleted items
on a transfer, but cannot transfer out items that are inactive or deleted at the destination
store. Returns (RTW/RTV/return to supplier) are still possible.
It is not possible to create price changes, clearances or promotions for deleted items.
Items are deleted in SIM when they are not on any transactions in SIM. This means that
they can remain in a Deleted status for some time despite the fact they are deleted in
RMS.

Note: SIM allows processing of the delete item/loc

relationship because it is more prudent to receive the goods
then to reject and potentially have them disappear.

Item Configuration 29
Item Status

SIM PC Areas – Message Prompt for Inactive/Deleted/Discontinued Status Items

Area Process Action Result

Direct Delivery: Add Item User adds an Yes – Add the item.
Direct Delivery Button Inactive/Deleted/Discontinued item. No – Clear out the
Detail Soft Warning: item and do not
The item is inactive, are you receive.
sure you want to use this item?

The item is deleted, are you

sure you want to use this item?

The item is discontinued, are

you sure you want to use this
item?
Direct Delivery Receive All User presses Receive All when Yes – Receives all.
ASN: Direct receiving against an ASN. Soft No – Returns user
Delivery Detail warning: to the Direct
when receiving One or more items are inactive, Delivery Detail
against an discontinued or deleted, are screen without
existing purchase you sure you want to receive receiving.
order (ASN) all?
Warehouse Add Item User adds an Yes – Add the item.
Delivery: Receive Button Inactive/Deleted/Discontinued item. No – Clear out the
Case Soft Warning: item and do not
The item is inactive, are you receive.
sure you want to use this item?

The item is deleted, are you

sure you want to use this item?

The item is discontinued, are

you sure you want to use this
item?
Warehouse Receive User presses Receive with no Yes – Receives all
Delivery: containers highlighted and an containers.
Delivery Detail Inactive/Deleted item on the No – Returns user
delivery. Soft Warning: to the Detail screen
One or more items are inactive, without receiving.
discontinued or deleted, are
you sure you want to receive
all?
Warehouse Receive User presses Receive with one or Yes – Receives all
Delivery: more containers highlighted and an highlighted
Delivery Detail Inactive/Deleted item on the containers.
delivery. Soft Warning: No – Returns user
One or more items are inactive, to the Detail screen
discontinued or deleted, are without receiving.
you sure you want to receive
all selected containers?

30 Oracle Retail Store Inventory Management

 Item Status

Area Process Action Result

Transfer Out: Add Item User adds an Inactive/Deleted item. OK – Item is not
Create Transfer SIM checks whether the item is added.
inactive at destination store. If the Yes – Item is added.
receiving location is inactive or
No – Item is not
deleted:
added.
The item is <inactive or
deleted> at the destination
store and cannot be added.
If the item is discontinued:
The item is discontinued, are
you sure you want to use the
item?
Transfer Add Item User adds an Inactive/Deleted item. OK – Item is not be
Requests: SIM checks whether the item is added.
Transfer Request inactive or deleted at destination Yes – Item is added.
Detail store. If the receiving location is
No – Item is not
inactive or deleted:
added.
The item is inactive or deleted
at the destination store and
cannot be added.
If the item is discontinued:
The item is discontinued, are
you sure you want to use the
item?
Transfer In: Add Item User adds an Yes – Add the item.
Receive Transfer Button Inactive/Deleted/Discontinued item. No – Clear out the
Soft Warning: item and do not
The item is inactive, are you receive.
sure you want to use this item?

The item is deleted, are you

sure you want to use this item?

The item is discontinued, are

you sure you want to use this
item?
Transfer In: Receive All User presses Receive All, and an Yes – Receives all.
Receive Transfer Button Inactive/Deleted item is on the No – Returns user
transfer. Warning: to the Receive
One or more items are inactive, Transfer screen
discontinued or deleted, are without receiving.
you sure you want to receive
all?
Item Requests Add item User adds an Inactive/Deleted status OK – Item is not
item. added.
The item is <inactive or Yes – Item is added.
deleted> and cannot be added. No – Item is not
If the item is discontinued: added.
The item is discontinued, are
you sure you want to use the
item?

Item Configuration 31
Item Status

Area Process Action Result

Filter Screens Filter Item Do not prompt with any error

message.

Returns: Add Item Inactive/Deleted items are not Yes – Add the item.
Finishers allowed to be shipped to Finishers. No – Does not add
User adds an Inactive/Deleted status the item.
item.
The item is <inactive or
deleted> and cannot be added.
If the item is discontinued:
The item is discontinued, are
you sure you want to use the
item?

SIM Handheld Areas – Message Prompt for Inactive/Deleted/Discontinued Status Items

Area Process Action Result

Direct Delivery Item Entry: User adds an Yes – Receive the

Scan Barcode Inactive/Deleted/Discontinued item.
item. Soft Warning: No – User is
The item is inactive, are you returned to the
sure you want to use this item? Item Entry screen.

The item is deleted, are you

sure you want to use this item?

The item is discontinued, are

you sure you want to use this
item?
Direct Delivery Receive All User presses Receive All when Yes – Receives all.
ASN: Receiving receiving against an ASN. Soft No –User is
against an warning: returned to the
existing purchase One or more items are inactive, Direct Delivery
order (ASN) discontinued or deleted, are Detail screen
you sure you want to receive without receiving.
all?
Warehouse Receive User adds an Yes – Receive the
Delivery: Receive Case- Item Inactive/Deleted/Discontinued item.
Case Entry – Scan item. Soft Warning: No – User is
Barcode The item is inactive, are you returned to the
sure you want to use this item? Item Entry screen.

The item is deleted, are you

sure you want to use this item?

The item is discontinued, are

you sure you want to use this
item?

32 Oracle Retail Store Inventory Management

 Item Status

Area Process Action Result

Warehouse Receive All User presses Receive All, and an Yes –All containers
Delivery: Inactive/Deleted item exists on the are received. User
Delivery delivery. Soft Warning: is returned to the
Information One or more items are inactive, delivery summary
discontinued or deleted, are screen where
you sure you want to receive delivery can be
all? confirmed.
No – User is
returned to the
Detail screen
without receiving.
Warehouse Receive User presses Receive Container, and Yes – Container is
Delivery: Container Inactive/Deleted item exists on the received.
Container delivery. Soft Warning: No – User is
Summary One or more items are inactive, returned to the
discontinued or deleted, are Container
you sure you want to receive Summary screen
the container? without receiving.
Warehouse Scan barcode User scans container to receive, and Yes – Container is
Quick Receiving: of container an Inactive/Deleted item exists on received.
Quick Receiving to receive the delivery. Soft Warning: No – User is
One or more items are inactive, returned to the
discontinued or deleted, are Quick Receiving
you sure you want to receive screen where user
the container? can scan another
container.
Transfer Out: Item Entry: User enters an Inactive/Deleted OK – User is
 Create Scan Barcode status item. SIM checks whether the returned to the
Transfer of Item item is inactive or deleted at Item Entry screen.
destination location. If the Yes – Item is
 Edit Transfer
destination location is inactive or added.
deleted:
No – Item is not
The item is <inactive or added.
deleted> at destination store
and cannot be added.
If the item is discontinued:
The item is discontinued, are
you sure you want to use the
item?
Transfer Item Entry: User enters an Inactive/Deleted OK – User is
Requests: Scan Barcode status item. SIM checks whether the returned to the
 Create item is inactive or deleted at Item Entry screen.
Transfer receiving location. If the receiving Yes – Item is
Request location is inactive or deleted: added.
 Edit Transfer The item is <status> at No – Item is not
Request destination store and cannot be added.
added.
If the item is discontinued:
The item is discontinued, are
you sure you want to use the
item?

Item Configuration 33
Non-Sellable Items

Area Process Action Result

Transfer In: Item Entry: User enters an Yes – Receive the

Receive Item Scan Barcode Inactive/Deleted/Discontinued item.
status item. Soft Warning: No – User is
The item is discontinued, returned to the
inactive or deleted, are you Item Entry screen.
sure you want to use the item?
Transfer In: Receive All User presses Receive All, and Yes – Receives all.
Receive All Inactive/Deleted items are on the No – User is
transfer. Warning: returned to the
One or more items are inactive, Receive Transfer
discontinued or deleted, are screen without
you sure you want to receive receiving.
all?
Item Requests Add item User adds an Inactive/Deleted status User presses Enter.
item: The item is not
The item is <status> and cannot added.
be added. Yes – Item is
If the item is discontinued: added.
The item is discontinued, are No – Item is not
you sure you want to use the added.
item?
Returns: Add Item Inactive/Deleted items are not Yes – Item is
Finishers allowed to be shipped to Finishers. added.
User adds an Inactive/Deleted status No – Item is not
item: added.
The item is <inactive or
deleted> and cannot be added.
If the item is discontinued:
The item is discontinued, are
you sure you want to use the
item?

Non-Sellable Items
If a regular item is non-sellable yet orderable, SIM should be able to perform all
inventory transactions against the item.
Any inventory increases or decreases for these items are displayed on the item detail
screen.
SIM does not relieve inventory when sales come through since the sale is for a different
item type, and SIM does not know the relationship between the sellable and orderable
item.

Pack Item
If a pack item is non-sellable yet orderable, SIM should be able to perform all inventory
transactions against the item.
The pack item has no inventory recorded to it with the exception of in-transit and on-
order. All inventory adjustments (including receipts) are made to the components of the
pack.

Note: See Simple Pack Conversion Items (Notional Packs)

for tracking inventory on breakable packs.

34 Oracle Retail Store Inventory Management

 Type-2 Item Recognition

Type-2 Item Recognition

Barcode Algorithms
SIM supports a variety of different algorithms to support advanced barcodes.
 Type-2 barcodes can contain a price or weight, and SIM extracts from these barcodes
a SKU/UPC number as well as a quantity.
 Type-E barcodes are condensed barcodes that need to be reformatted into their
original size to be understood.
Whether a barcode is type-2 or type-E, SIM follows a standard process: The barcode
scanned by the handheld, or entered by the user, goes through a set process to find the
correct item number:
1. The scanned barcode is checked to see if it is a valid item.
2. If the exact scanned or entered item number is found in the item master file, SIM
assumes that that item should be used for the transaction.
3. If the exact match is not found, then the parsing logic is started.
The SIM architecture is designed to have a customer add their own barcodes if needed, as
long as the barcodes are a valid SKU, or contain a SKU and weight. It is also possible to
turn on or turn off specific barcodes to ensure processing is only performed for barcodes
that are actually used by the retailer.

System Process Flow

N Populate Item

Screen
Extract
Item scan requires
algorithm
quantity?

Calculate Update quantity

Extract UPC weight by with derived
using price quantity

If price is 0, use qty = 0

If not variable, use qty = 1

Item Configuration 35
Type-2 Item Recognition

The user begins by scanning an item. This barcode scan must go through an algorithm to
identify the UPC and the price. If the scan is called from a screen which expects an
automatic quantity increase, the system calculates the quantity of the item based on the
price of the barcode and the current price on file. The quantity for the item is then
incremented by this calculated quantity.

Note: SIM does not have algorithms supporting barcodes

with embedded quantity. Only embedded price is
supported. It is possible to extend SIM to support quantity-
based barcodes by adding a custom quantity-specific
barcode.

Barcode Algorithm Splicing

Validate that the scan is of a valid barcode. Use the Studio/Edge application. If the
scanned barcode is not a valid item, then start the parsing logic. Parsing is based on the
following values:
 Number of barcode characters
 Number of prefix characters
 Initial item digit position
 Initial price digit position
 Check digit position
 Prefix (this field is optional. If filled out, it might increase performance)
For performance reasons, also indicate which barcodes is used.
Supported formats are based on the existing RMS barcode formats, all of which are active
from the start:

Format Description Number of Initial Initial Check Prefix Number of

Prefix Item Price Digit Barcode
Characters Digit Digit Position Characters
Position Position

A 1-4-6-1 1 2 6 0 12
B 1-5-5-1 1 2 7 0 12
C 1-4-6-1 1 2 7 6 12
D 1-5-5-1 1 2 8 7 12
E 2-4-5-1 2 3 8 7 12
F 2-4-5-1 2 3 7 0 12
G 2-5-4-1 2 3 8 0 12
H 2-5-5-1 2 3 8 0 13
I 2-4-6-1 2 3 7 0 13
J 2-4-6-1 2 3 8 0 13
K 2-5-5-1 2 3 9 8 13

Each type has a hardcoded algorithm. Each column is the start of the position in the
string (0 means there is no position for it). The description explains the length of the
value. For example, look at C 1-4-6-1 for item number 123456789012:
 The prefix is in position 1, with a length of one character (1).

36 Oracle Retail Store Inventory Management

 Type-2 Item Recognition

 The initial item digit is in position 2. The item number has a length of four characters
(2345).
 The check digit is in position 6, with a length of one character (6).
 The initial price digit is in position 7. The price has a length of six characters (789012,
or 7890.12).
After checking length, the check digit should be validated.
If a prefix value is filled in on the table, SIM identifies and checks the parsing algorithm
routine if the prefix matches that which was retrieved before going to the database. This
allows faster processing and helps eliminate certain invalid options.
A successful lookup of the item on item master should include the following item
elements, derived from the previous table:
 Item ID
 Item Format
 Prefix
Leading 0s for the Item ID must be supported. For example, for Item 250010001500:
 Rule 1 – Check item master/item location for validity of the entire item number.
 Rule 2 – Parse valid values: 12-character length, only options A-G are left valid.
 Rule 3 – Parse check digit, only formats A, B, F and G are left valid.
 Rule 4 – Parse prefix, if prefix filled in validate prefix, in this case, which is not done
since the table does not contain any by default.
 Rule 5 – Go to the database with the following information:
 Format A, prefix 2, item 5001
 Format B, prefix 2, item 50010
 Format F, prefix 25, item 0010
 Format G, prefix 25, item 00101
SIM only selects one valid item. If two values are valid, SIM raises an Invalid Item
error.

Note: The price is defined as 000150 or 0001500, depending

on the format. Two decimals are implied, so the price can
vary from $1.50 to $15.00, depending on the correct format
type.

Note: The reason for looking up the format and prefix match
is so the algorithm can return two different formats, and
each can be a valid item ID:
– x1234zzzzzzY (prefix 2)
– xx2345zzzzzY (prefix 21)
Both Item IDs can be valid, but only one is accurate. The
type and prefix narrows the calculation down to a unique
ID.

Item Configuration 37
Type-2 Item Recognition

Weight Calculations
Consider the following weight calculations:
 The weight is calculated by using the price from the label and dividing it by the
current active price on file.
 Two decimals are implied in the retrieved value from the barcode.
 The currency for the price on the barcode is the currency of the store.
 This price can be regular, promotion or clearance.
 The item’s SUOM of the weight is implied.
 Standard rounding is applied up to a maximum of four decimals.
For example, Item 250010001500 was defined as format A. This means that the price was
000150 = $1.50.
 The price on file for this item is $3.00.
 The quantity is calculated as follows:

1.5/3 = 0.5

 The item’s SUOM is kg, so the weight of the item is 0.5 kg.

Weight Application
The quantity field is increased by the value calculated from the barcode.
 The increase can be 0 or greater. The increase cannot be less than 0.
 If the item is a regular item defined as an item without embedded price, continue to
increase the quantity field with 1.
 The first time an item is scanned should equal the weight of the item.
The PC screens are not be impacted by the weight calculation.
If the screen is in case mode and the item scanned is an item with a variable weight
attached to it, the system calculates the case value back to the SUOM, add the weight
from the barcode, and calculate back to case value.
 The UOM format (case or SUOM) stays the same when scanning the variable weight
item. For example, where a case is 10 pounds:
– The quantity for item on receipt up to this point is 18 pounds.
– The handheld in case mode would display 1.8 cases.
– The user scans a variable weight item with a weight of 4 pounds.
– The display on the handheld goes to 2.2 cases.
 In case the item is already in SUOM when scanning, the quantity of the barcode is
added.
 The user is able to continue typing in quantities for both the case and the SUOM.
 If the user types in case mode, for example 25, then this would mean 25x10 pounds,
or 250 pounds at the SUOM level.
The following screens on the handheld allow the quantity value to be increased by the
calculated value from the barcode:

Dialogue Quantity Comment

Update

Direct Delivery Item Yes

Input

38 Oracle Retail Store Inventory Management

 Type-2 Item Recognition

Dialogue Quantity Comment

Update

Direct Delivery Record Yes

Damages
Inventory Adjustment Yes
Item
Stock Counts Item New Yes / No Unguided stock counts require the quantity to be
summarized.
Guided stock counts on the other hand require the user
to enter the total quantity and subsequently confirm it
by scanning the item. As such no quantity of the
barcode needs to be added.
Stock Return Item New Yes
Transfer In Item Input Yes
Transfer Out Item New Yes
(add)
Transfer Request Item Yes
New
Warehouse Delivery Yes
Input Qty
Warehouse Delivery Yes
Damages
Warehouse Delivery Yes
Discrepancies
Item Basket Yes

Error Messages
Errors can be caused by several events:
 The price has alphanumeric values:
 The value entered is not a valid UOM.
 Applicable to the handheld and the PC.
 The UOM is an each or other UOM that cannot have decimals for the item:
 Raise a standard Invalid Item error.
 Applicable to the handheld and the PC.
 The algorithm engine fails:
 Raise a standard technical error.
 Applicable to the handheld and the PC.
 The item cannot be found (regular item, or extracted item from the barcode):
 Raise a standard Invalid Item error.
 Applicable to the handheld and the PC.
 SIM finds two possible items:
 Raise a standard Invalid Item error.
 Applicable to the handheld and the PC.

Item Configuration 39
UPC-E Barcodes

Note: A standard Invalid Item error is defined as the current

Invalid Item message.

Non-Ranged Items
Non-ranged items have a quantity of 0 if the item is a VPLU (variable barcode).

Type-2 Item Integration

SIM subscribes to the following information:
 Subscribe to and store the prefix from the item header RIB message.
The value should be held on the as_itm table.
 Subscribe to and store the format ID from the item header RIB message.
The value should be held on the as_itm table.

UPC-E Barcodes
UPC-E items compress a normal 12-digit UPC-A item into six digits. SIM has the ability
to decompress UPC-E barcodes to UPC-A. A seventh digit acts as a check digit for the
UPC-E number. When the user scans the UPC-E barcode, SIM finds the UPC-A barcode
and display the item ID associated with it.
UPC-E is also called zero-suppressed UPC because UPC-E compresses a normal 12-digit
UPC-A number into a six-digit code by suppressing the number system digit, trailing
zeros in the manufacturers code and leading zeros in the product identification part of
the barcode message. A seventh check digit is encoded into a parity pattern for the six
main digits. UPC-E can be uncompressed back into a standard UPC-A 12-digit number.

Note: Most barcode readers can be configured to

automatically convert six-digit UPC-E numbers to 12-digit
UPC-A numbers before they are transmitted to a host
computer.

The main difference between a UPC-A symbol and a UPC-E symbol is the size. The
following image presents a UPC-A bar code (left) and the same data encoded as a UPC-E
bar code (right):
UPC-A and UPC-E Differences

40 Oracle Retail Store Inventory Management

 UPC-E Barcodes

Converting UPC-E Barcodes to UPC-A Format

The following is the process for converting a UPC-E barcode to UPC-A format:
1. The user starts the process by scanning an item. This barcode scan is sent through an
algorithm to identify the UPC.
2. If the scan is for a UPC-E barcode, SIM extracts the algorithm and decompress to the
UPC-A. SIM then displays the associated item ID.
3. The UPC-E barcode is eight digits, with six main digits and a seventh check digit.

Business Process Flow

The following diagram describes the flow for converting UPC-E barcodes to UPC-A
format:

Extract
Scan UPC-E
algorithm

Convert to UPC-A
and display item
ID

Scan UPC-E, Display UPC-A

Generic Barcode Algorithm Splicing Process

After a barcode is scanned, SIM performs the following process for a UPC-E barcode:
1. SIM parses the barcode. Parsing is based on the following values:
 Total length of digits in the barcode
 Prefix length (prefix code is -1 for UPC-E)
 Begin Item digit position
 Check digit position
 Prefix (this is an optional field, but if filled in might increase performance)
2. If a prefix value is filled in on the table, SIM identifies and checks in the parsing
algorithm routine if the prefix matches with what was retrieved before going to the
database. This allows faster processing and helps eliminate certain invalid options.
A successful lookup of the item on item master should include the following item
elements:
 After the barcode splicing, SIM looks up the found item number on the item
master table to find the transaction level items.
 If an item is still not found, SIM continues with checking the item number
against the repository of UINs in SIM.
– Finding the UIN is across all stores.
– If a UIN is found, SIM next finds the transaction level items and returns them
to the client.

Item Configuration 41
UPC-E Barcodes

– It is important to understand that SIM could find multiple hits for barcodes
or for UINs, but it is also important to understand that SIM may not find a
UIN if a serial number matches a potential barcode algorithm that results in
an item find.

Note: Leading 0s for the item ID must be supported.

In the following table, the number 0 and each of the letters (a, b, c, d and e) represent
individual digits in the bar code message. The letter X represents the UPC check digit.

UPC-A Number Equivalent UPC-E Notes

0ab00000cdeX abcde0X Manufacturer code must have two leading digits

with three trailing zeros. The item number is
limited to three digits (000 to 999).
0ab10000cdeX abcde1X Manufacturer code must have three leading
digits ending with 1 and two trailing zeros. The
item number is limited to three digits.
0ab20000cdeX abcde2X Manufacturer code must have three leading
digits ending with 2 and two trailing zeros. The
item number is limited to three digits.
0abc00000deX abcde3X Manufacturer code must have three leading
digits and two trailing zeros. The item number is
limited to two digits (00 to 99).
0abcd00000eX abcde4X Manufacturer code must have four leading digits
with one trailing zero. The item number is
limited to one digit (0 to 9).
0abcde00005X abcde5X Manufacturer code has all five digits. The item
0abcde00006X abcde6X number is limited to a single digit consisting of 5,
6, 7, 8 or 9.
0abcde00007X abcde7X
0abcde00008X abcde8X
0abcde00009X abcde9X

Impacted Dialogues
Any screen where an item can be scanned or entered allows UPC-E to convert to UPC-A.

Error Messages
Errors can be caused because of several events:
 The algorithm engine fails:
 Standard technical error.
 Applicable to the handheld and the PC.
 The item cannot be found (regular item, or extracted item from the barcode):
 Raise standard Invalid Item error.
 Applicable to the handheld and the PC.
 SIM finds two possible hits:
 Display existing Item Select screen so the user can choose an item.
 Applicable to the handheld and the PC.

42 Oracle Retail Store Inventory Management

 UPC-E Barcodes

Note: Standard Invalid Item error is defined as the current

Invalid Item message.

Catch Weight Items – Definitions

The following are definitions for catch weight items:
 Type 1 – Purchase in fixed-weight simple packs. Sell by variable weight:
For example, bananas. If purchased as a simple pack, the cost charged by the
supplier is an agreed amount for an assumed fixed weight simple pack size.
Therefore, the simple pack is ordered at an assumed fixed weight.
If purchased as the component item, the cost charged by the supplier is dependent
upon the actual weight of the component item received. The retail price charged to
the customer is dependent on the weight of the component item. Inventory is
recorded for the simple pack in eaches, and for the component item, in mass (weight)
UOM.
 Type 2 – Purchase in variable-weight simple packs. Sell by variable weight:
For example, meat sold at a delicatessen counter. Costs and retail prices of both the
simple pack and component item are held per mass UOM, that is, when the item is
purchased, the cost charged by the supplier depends upon the weight of the simple
pack accepted at the receiving location. Therefore, the simple pack is ordered at
different costs depending on the weight of the simple pack.
If purchased as the component item, the cost charged by the supplier is dependent
upon the actual weight of the component item received. The retail price charged to
the customer is dependent on the weight of the item. Inventory is recorded for the
simple pack in eaches, and for the component item, in mass (weight) UOM.
 Type 3 – Purchase in fixed-weight simple packs containing a fixed number of eaches.
Sell by variable weight eaches:
For example, prepackaged cheese. If purchased as a simple pack, the cost charged by
the supplier is an agreed amount for an assumed fixed weight simple pack size.
Therefore, the simple pack is ordered at an assumed fixed weight.
If purchased as the component item, the cost charged by the supplier is dependent
upon the actual weight of the component item received. The retail price charged to
the customer is dependent on the weight of the item. Inventory is recorded for the
simple pack in eaches, and for the component item, in eaches.
 Type 4 – Purchase in variable-weight simple packs containing a fixed number of
eaches. Sell by variable weight eaches:
For example, pre-packaged sirloin steak. Costs and retail prices of the simple pack
are held per mass UOM, that is, when the item is purchased as a simple pack, the
cost charged by the supplier depends upon the weight of the simple pack accepted at
the receiving location. Therefore, the simple pack is ordered at different costs
depending on the weight of the simple pack.
If purchased as the component item, the cost charged by the supplier is dependent
upon the actual weight of the component item received. The retail price charged to
the customer is dependent on the weight of the item. Inventory is recorded for the
simple pack in eaches, and for the component item, in eaches.

Item Configuration 43
Non-Inventory Items

Catch Weight Items – Support

SIM supports the following catch weight items:
 Items received as weight and then sold as weight.
 Items received as kg and then sold as grams.
 Catch weight type 1 and 3 are all supported, if a nominal weight is provided by RMS.

Note: SIM does not have the ability to capture weight for
types 2 and 4, so the RMS nominal weight is used in this
case.

Item Types that are Not Supported

SIM does not support the following catch weight items:
 Item transformation is not supported in SIM. For example, a carcass of beef sold as
steak and hamburger is not supported.
 An item received as a unit and then sold as weight is not supported.

Non-Inventory Items
Non-inventory items are items that have no inventory, but can be sold in the store, for
example, warranty plans, gift cards:
 SIM flags the item as a non-inventory item when subscribing.
 ReSAFileParser and the Sales web service do not update stock-on-hand for these
items, and does not put them in the error log.
 SIM does not allow inventory changes to this item type in any of its dialogues.
Due to business processes, some functional areas are allowed to accept and use non-
inventory items:
 Sequencing does allow non-inventory items so the retailer can know the relative
location of the item in the store.
 Pricing – Retailers are able to control the pricing of non-inventory items in RPM, and
therefore SIM allows price changes for non-inventory items.
 Ticketing – Retailers have the ability to print tickets for non-inventory items in order
to reflect any price changes.
 Item Lookup – SIM allows the user to look up non-inventory items as an indication
that the item is indeed carried at the store. However, Item Lookup does not display
any stock-on-hand information.
 Item Baskets – Non-inventory items are allowed on item baskets.

44 Oracle Retail Store Inventory Management

 Consignment and Concession Items

Because non-inventory items are very similar to consignment or concession items from
an inventory perspective, SIM subscribes to these records but not allow any inventory
adjustments to be made against them.
Non-Inventory Items

Point-of-Service RMS updates

ReSA processes
sells non-inventory stock ledger, not
RTLOG
item stock-on-hand

SIM ignores sales

record and does
not update stock-
on-hand

Subscribing to the non-inventory items allows SIM to identify the items as non-inventory
and flag them on the Item Lookup Detail screen.

Data Seeding
Data seeding captures the non-inventory indicator when seeding data from RMS. These
items should not exist on POs, transfers, pending inventory adjustments or returns.

Consignment and Concession Items

A consignment item is an item that is owned by the supplier, but the physical aspect of
the merchandise is controlled by the retailer. The supplier bears all costs of the item until
the item is sold. Once the item is sold, the retailer pays the supplier for the item. The
benefit to the retailer is that no backroom inventory expenses are incurred. The only
impact is to shelf space. This is very beneficial for high risk items that might not sell in
expected quantities. Instead of bearing the cost of high inventory levels due to poor sales,
the retailer can send the items back to the supplier at no cost. Ownership is only
transferred to the retailer once the item is sold.
 Consignment items are excluded from SIM so that the user is unable to add or use a
consignment item when attempting to make a change to inventory.
 ReSAFileParser does not upload the sale, to prevent it being added to the error log.
Similar to consignment items, SIM subscribes to concession items. A concession item is
similar to a consignment item in that the retailer does not own the inventory being sold.
However, the ownership is not transferred when the items are sold. A retailer rents floor
space to a supplier, and a record of the concession sale is recorded. The retailer then bills
the supplier using an approved method. Because concession items and consignment
items are very similar (with the exception of how the retailer receives revenue), SIM
subscribes to these records but does not allow any inventory adjustments to be made
against them. In SIM, concession items are handled in the same way as consignment
items.

Item Configuration 45
Consignment and Concession Items

Consignment items are usually items such as magazines at a grocery store, where the
vendor stocks the shelves, but the retailer does not actually purchase the items until they
are sold. Upon sale, which is managed by a daily batch process, a PO and invoice are
created. The invoice is matched to the PO and paid through ReIM. RMS never does any
receiving on consignment items, and they are never in stock. The PO cost is based on the
retail price the item was sold at, and a Consignment Rate that is maintained in RMS for
the item. Consignment designation is made at the department level, so all items in a
consignment department are consignment items and treated similarly. The consignment
rate can vary by item within a department. Sales are actually recorded in the stock ledger
for consignment items.
Concession items in RMS use a model similar to that of a Starbucks that is located in a
Target store. Starbucks is charged a fee for having their business in the Target store. In
current functionality, a fee is charged to the concession business based on a percentage of
their sales. The sales are not actually recorded as part of the retailer’s business in the RMS
stock ledger, but instead the sales are written to a special table that is used by a separate
process to invoice the concession business. Again, like consignment items, there is no
inventory for these items. The designation of concession is made at the department level:
 SIM subscribes to and records consignment and concession items.
 The flag is stored at the item/loc level in RMS, and the consignment rate is recorded
at the item/supplier level.
 SIM has an indicator in Item Lookup to flag an item as consignment or concession.
 SIM validates whether the item is a consignment or concession item. If the item is a
consignment or concession item, SIM does not update the inventory.
 ReSAFileParser does not update the stock on hand or perform the late sales logic.
The batch does not add the item to the error log.

Preventing Inventory Changes

When attempting to use an item that is flagged as consignment or concession for the
purpose of making an inventory change, SIM validates that the item is a consignment or
concession item, and then prompt the user with the following error message:

This is a consignment item and cannot be used. Please select another item.

SIM prevents the use of consignment and concession items on Store Orders, Transfers,
Receipts, Item Request, Pick List, Product Group, Stock Counts, Returns, Problem Line,
Wastage, and Inventory Adjustments. When attempting to use a consignment or
concession item, the user is prompted with the following message:

This is a consignment item and cannot be used. Please select another item.

There are exceptions where consignment and concession items are allowed in SIM. The
user is allowed to enter consignment or concession items in Sequencing, Pricing,
Ticketing, Item Baskets and Item Lookup.

46 Oracle Retail Store Inventory Management

 Consignment and Concession Items

Exceptions – Allowing Consignment and Concession Items

SIM allows the user to look up consignment and concession items in Item Lookup on
both the handheld and the PC.
The Item Lookup screen on the PC includes a section called Item Type. This section
provides the user with information on what type of item is currently being viewed. SIM
looks to the SIM database to determine if consignment or concession check boxes are
flagged for the item being viewed.
Stock-on-hand, and any reference to inventory, is not available for consignment items as
the item is not owned by the retailer until after the sale. Stock-on-hand and inventory
information is not available for concession items. Stock-on-hand fields are null in Item
Lookup on both the PC and the handheld. The purpose of including consignment and
concession items in Item Lookup is to verify that the retailer does carry the item despite
the fact that inventory is not tracked.
Stock Locator – Consignment and concession items do not have any stock-on-hand
information. However, the user is able to access the Stock Locator to view locations at
which the item is carried. Stock-on-hand fields Available SOH and Received Today is
null.
Price Information – The user is able to view price information for consignment and
concession items.
Item Basket – The user is allowed to add consignment and concessions items to an item
basket.

Item Configuration 47
Quick Response Codes

Quick Response Codes

Quick Response (QR) Codes are two-dimensional barcodes that can be generated to
represent any text, most often a custom URL. They can be read by a number of mobile
applications using a cell phone’s camera, and provide a way to hyperlink the physical
world. QR codes can be placed next to products to provide further information or digital
coupons, even if the QR code is on a billboard or store signage. Applications such as
RedLaser provide customers ways to comparison shop in the store. QR codes and the
associated Web sites are controlled by the retailer, allowing them to recapture control of
product research in their store, as well as provide value-added information and digital
coupons.
Potential benefits for retailers, if supported, include:
 Quick, controlled, and convenient delivery of product information and promotion.
The retailer’s item Web page is a gateway to listing related products and accessories,
service offers and warranty information (avoiding the Best Buy scenario where, if
someone asks for warranty information, the retailer must open the package and then
must discount the item).
 Flexibility for the retailers to use QR codes for different purposes, including brand
and department-level marketing.
 Retailers can dynamically change the content of QR code Websites based on a drop
in outstanding stock, overcapacity, vendor specials, and promotions. Retailers can
also target specific regions and stores with their own Websites, and if using a retailer-
controlled QR reader, can also target specific customer segments, or potentially even
individual customers.

SIM Usage of QR Codes

The following applies to the SIM usage of QR codes:
 Track image reference to QR codes at the item, location, image type, and time level.
 Generate tickets and labels by location when QR codes change based on time or
entry, using the existing ticket and label dialogues.
 Allow customers to configure the generation of tickets and labels automatically.
 Print tickets and labels with QR codes.
 Allow external systems to integrate QR references within SIM.
Tickets and labels are generated ad hoc or based on system event changes, such as
description or price. These ticket and labels can be printed in batch by a user, or
individually.
QR codes are added to enhance the information a customer can look up.

48 Oracle Retail Store Inventory Management

 Quick Response Codes

Business Process Flow

Image server
Information is sent
sets up QR Code
to SIM
image

SIM generates
ticket/labels

User selects
tickets/labels from
available ticket list
to print

Quick Response Codes Store Parameters

The following table lists the store administration options related to QR codes:

Store Topic Valid Default Description

Administration Values Value
Option

Send Item Tickets Ticketing Yes, No No Indicates SIM generates a

to Ticketing for new ticket if the QR code
QR Code Change changes based on the optional
time/date. If no time/date is
defined, it is generated
immediately. If a time/date
exists, it is generated by a
batch program.
Send Shelf Edge Ticketing Yes, No No Indicates SIM generates a
Labels to Ticketing new label if the QR code
for QR Code changes based on the optional
Change time/date. If no time/date is
defined, it is generated
immediately. If a time/date
exists, it is generated by a
batch program.

Generating QR Tickets and Labels Information

Information is received – QR code tickets are generated if the Send Item Tickets to
Ticketing for QR Code Change parameter is set to Yes:
 A QR code type image is integrated for specified locations with an empty date field
(generates a ticket for the specified location with stock-on-hand quantity).

Item Configuration 49
Quick Response Codes

 A QR code type image is integrated with neither a location nor a date specified
(generates a ticket for all locations that have that item ranged with stock-on-hand
quantity).
In both cases, the ticket has an indicator to print the QR code.
User runs batch – QR code labels are generated if the Send Shelf Edge Labels to Ticketing
for QR Code Change parameter is set to Yes.
 A QR code type image is integrated for specified locations with an empty date field
(generate a label for the specified location with stock-on-hand quantity).
 A QR code type image is integrated with neither a location nor a date specified
(generate a label for all locations that have that item ranged with label quantity from
sequencing).
In both cases, the ticket has an indicator to print the QR code.

Receiving QR Tickets and Labels Information

Standard interface messages (item image subscriber) receive the new attributes to trigger
certain functionality. This information might be sent from RMS:
 Type:
 QR Code (QR code image)
 Standard (Standard image)
 Required (if empty, assume standard QR code)
 Start Date:
 Date QR image goes into effect
 Optional information
 End Date:
 Date QR image goes out of effect
 Optional information
 Location:
 Locations this QR code applies to
 Optional information

ItemTicket Batch Requirements

The ItemTicket batch reviews the item image table for any QR type item that has a date
equal to the date for which the batch is running. Without a parameter input, this is the
moment after midnight, similar to every other batch. With a date, this is the date defined
in the batch. Based on this date and time of the item image, and the Quick Response
codes store parameters, SIM creates a ticket or label entry in the Ticketing screen
following the standard pattern of ticketing and labeling.
This batch takes into account time zone information if a location has been provided:
User runs batch – QR Code tickets are extracted if the Send Item Tickets to Ticketing for
QR Code Change parameter is set to Yes:
 A QR code type image is found for the specified location with a start date equal to
the date for which the batch is run (generate a ticket for the specified location with
stock-on-hand quantity).
 A QR code type image is found with a start date equal to today, but no location is
specified (generate a ticket for all locations that have that item ranged with stock-on-
hand quantity).

50 Oracle Retail Store Inventory Management

 Quick Response Codes

User runs batch – QR code labels are extracted if the Send Shelf Edge Labels to
Ticketing for QR Code Change parameter is set to Yes:
 A QR code type image is found for the specified location with a start date equal to
the date for which the batch is run (generate a label for the specified location with
stock-on-hand quantity).
 A QR code type image is found with a start date equal to today, but no location is
specified (generate a label for all locations that have that item ranged with label
quantity from sequencing).
The batch sets the QR code indicator to Off for the ticket and label, and generates a new
one if the same condition applies, but instead of the start date, the end date is reached for
the batch run.

Assumptions
The same default tickets and labels are printed as defined for regular ticket and label
printing.

Item Configuration 51
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 © 2013, Oracle and/or its affiliates. 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.