Mirror of Oracle documentation

Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.

5 Dimensions and Attributes

Retail Insights dimensions and attributes represent the structure and activities of a retail organization and make measurement possible. Data is stored at low levels to allow maximum flexibility in reporting. Dimensions and their attributes allow you to summarize this information at higher levels where it is needed to support business decision-making. For example, the Sales fact table holds data at the location, item, and day level. The time, product, and organization dimensions allow you to summarize this data at any level at which it is needed.

Note

This chapter contains selective lists of dimensions and attributes. See Reporting on Oracle Analytics Repository Objects for information about producing comprehensive listings of Oracle Analytics repository objects.

Business Calendar

The business calendar (fiscal calendar) is a dimension based on a retailer’s calendar and is not aligned with the Gregorian/solar calendar. It is used in place of the Gregorian calendar to eliminate discrepancies in the number of days per month, as well as number of weekend days per month. The business calendar is sometimes just called the time calendar.

The business calendar can be based on a variation of the 4-5-4 calendar or the 13-period calendar. Both of these types of calendars allocate exactly seven days to every week, unlike the Gregorian calendar. Most facts are qualified by a calendar attribute.

The following is the hierarchy of the Business Calendar dimension.

Table 5-2 (Cont.) Gregorian Calendar Dimension Attributes

AttributeDefinition
Gregorian Month Start DateThis is the start date of the gregorian month.
Gregorian Month End DateThis is the end date of the gregorian month.
Gregorian WeekThis is the Gregorian Week
Gregorian Week Start DateThis is the Gregorian Week Start Date
Gregorian Week End DateThis is the Gregorian Week End Date

The Gregorian calendar attributes within the Business Calendar allow for reporting against thisyear and last-year historical data for Gregorian periods, making use of the LY mapping for Gregorian calendar to determine how each period aligns with it’s last-year equivalent. For more information on loading the TY-to-LY mappings, refer to the Oracle Retail Insights Operations and Interface Guide .

If you plan to shift your LY calendar to align to a different timeframe year-over-year (for example, to align the week-ending days rather than align the individual days in the year) then there is also a set of Gregorian Unshifted Sales metrics which will not use the shifted LY mappings. These metrics use the abbreviation “GLY” to denote Gregorian LY behaviors.

For example, you may change the Gregorian LY mappings to align Sunday this year to the equivalent Sunday in last year. When using the standard set of LY metrics in RI, they will roll up for those shifted dates (LY YTD may start from January 3rd instead of January 1st in this case). The associated metric for GLY YTD will still roll up from January 1st, no matter what LY mapping you have specified. This allows you to perform life-for-like analyses (where the same weeks are compared YoY) as well as calendar-based analyses (where you compare the same month or year timeframe even if the days are different) without having to switch your calendar back and forth.

Note that at this time, only sales metrics have GLY equivalents. If you want to shift your LY calendar and there is no GLY equivalent metric to get the unshifted view of your data, you can easily create the formula yourself using the built-in AGO() function in OAS.

Gregorian Flexible Attributes

The Gregorian calendar also supports a number of flexible attributes that may be defined by the retailer at the time of implementation. These flex attributes work on the same principle as RMFCS’s Custom Flex Attribute system (CFAS) in that the table structure for the data has an identical set of common datatypes and columns. These calendar at-tributes can be used for any number of business reasons, such as reporting on holidays, high-selling periods, alternate definitions of seasons or planning periods, or any other custom timeframe.

Table 5-3 Gregorian Flexible Dimension Attributes

AttributeDefinition
Date Flex Attr 1-10 CharDate level character-based flex attribute.
Date Flex Attr 11-20 NumberDate level numerical flex attribute.
Date Flex Attr 21-25 DateDate level date-based flex attribute.

RI can be configured to create employee records during the nightly batch process, such that employee IDs included on a transaction (such as the cashier and salesperson) will be usable in reports even when the employee master data file is not provided separately. In this case, reporting on sales by Cashier or Salesperson ID is possible, but the other information like names will not be available.

The primary ways to use the employee attributes for sales reports are:

  • Employee Number along with Sales metrics, to report on employee discounts for employee-purchased items

  • Cashier Number along with Sales metrics, to report on sales by cashier that was logged into the POS

  • Salesperson Number along with Sales metrics, to report on sales by salesperson who was given credit for the sale (or line-item on the sale if multiple salespersons are credited).

Table 5-5 lists the attributes of the Employee dimension.

Table 5-5 Employee Dimension Attributes

AttributeDefinition
Cashier FlagIndicator of whether if the employee is a cashier, with values of “Y” for
yes and “N” for no. An employee can be both a cashier and a
salesperson at the same time.
Sales Rep FlagIndicator of whether the employee is a salesperson, with values of “Y”
for yes and “N” for no. An employee can be both a cashier and a sales
person at the same time.
Employee NameName of the employee.
Employee NumberNumber assigned to the employee.
CashierName of the cashier.
Cashier NumberNumber assigned to the cashier.
SalespersonName of the salesperson.
Salesperson NumberNumber assigned to the salesperson.
Employee Alternate NumberOld employee ID from a legacy system or other systems still in use
such as Payroll.
Employee Supervisor NumberSource system ID generated by organization/system for the
employee’s supervisor or manager.
Employee Supervisor NameName from the source system for the employee’s supervisor or
manager.
Employee Job TitleThe job title associated with the primary position held by the employee.
Employee Active FlagIndicates if the employee is still active in records.
Employee Auth AmountIdentifies the amount this employee is authorized to approve for any
purposes related to the business of the organization.
Employee Auth Curr CodeThe currency code for the authorization amount assigned to the
employee.
Employee Auth Cat CodeThe category code for the authorization amount assigned to the
employee.
Cashier Alternate NumberOld cashier ID from a legacy system or other systems still in use such
as Payroll.
Cashier Supervisor NumberSource system ID generated by organization/system for the cashier’s
supervisor or manager.

Table 5-5 (Cont.) Employee Dimension Attributes

AttributeDefinition
Cashier Supervisor NameName from the source system for the cashier’s supervisor or manager.
Cashier Job TitleThe job title associated with the primary position held by the cashier.
Cashier Active FlagIndicates if the cashier is still active in records.
Cashier Auth AmountIdentifies the amount this cashier is authorized to approve for any
purposes related to the business of the organization.
Cashier Auth Curr CodeThe currency code for the authorization amount assigned to the
cashier.
Cashier Auth Cat CodeThe category code for the authorization amount assigned to the
cashier.
Salesperson Alternate NumberOld salesperson ID from a legacy system or other systems still in use
such as Payroll.
Salesperson Supervisor
Number
Source system ID generated by organization/system for the
salesperson’s supervisor or manager.
Salesperson Supervisor NameName from the source system for the salesperson’s supervisor or
manager.
Salesperson Job TitleThe job title associated with the primary position held by the
salesperson.
Salesperson Active FlagIndicates if the salesperson is still active in records.
Salesperson Auth AmountIdentifies the amount this salesperson is authorized to approve for any
purposes related to the business of the organization.
Salesperson Auth Curr CodeThe currency code for the authorization amount assigned to the
salesperson.
Salesperson Auth Cat CodeThe category code for the authorization amount assigned to the
salesperson.

Cluster

Understanding consumer shopping behavior is important to help retailers when planning assortment, pricing, promotions and other key merchandising decisions.

This includes understanding:

  • Who shops (or is expected to shop) the merchandise area (Department or Class)

  • How they would shop the merchandise area as well as other merchandise areas when in the store

This information helps retailers develop strategies and tactical execution plans that are tailored to meet specific customers’ needs, thus maximizing customer satisfaction while meeting retailers overall business objectives around increased profitability and growth.

Understanding the makeup of the local consumers shopping each individual store is important in developing assortment, pricing and promotion strategies that are tailored to the local consumer needs. However, given the number of stores at a typical retailer, it is not possible to manually plan these at the individual store level. Hence the need for the intelligent grouping of similar stores into clusters.

Clustering stores enables retailers to manage large chains (that is, greater than 500 locations) in an efficient manner. Effective clustering should involve a small number of clusters providing

Table 5-6 (Cont.) Cluster Attribute Dimensions

AttributeDefinition
Primary EthnicityPrimary ethnicity is the most prominent ethnicity within a cluster - since
clusters can be made up of multiple customer segments - there can be
more than one ethnicity present. Hence this attribute being the primary
or most prominent ethnicity attribute value.
Primary Education LevelPrimary education level is the most prominent education level within a
cluster - since clusters can be made up of multiple customer segments
- there can be more than one education level present. Hence this
attribute being the primary or most prominent education level attribute
value.
Primary Typical LifestylePrimary typical lifestyle is the most prominent typical lifestyle within a
cluster - since clusters can be made up of multiple customer segments
- there can be more than one typical lifestyle present. Hence this
attribute being the primary or most prominent typical lifestyle attribute
value.
Primary Income LevelPrimary income level is the most prominent income level within a
cluster - since clusters can be made up of multiple customer segments
- there can be more than one income level present. Hence this attribute
being the primary or most prominent income level attribute value.
Primary Dwelling TypePrimary dwelling type is the most prominent dwelling type within a
cluster - since clusters can be made up of multiple customer segments
- there can be more than one dwelling type present. Hence this
attribute being the primary or most prominent dwelling type attribute
value.
Primary Age ClassPrimary age class is the most prominent age class within a cluster -
since clusters can be made up of multiple customer segments - there
can be more than one age class present. Hence this attribute being the
primary or most prominent age class attribute value.

Price Zones

Price zones are a way of grouping stores together for use in pricing decisions. They appear functionally similar to Clusters. Price zones are typically created in a retailer’s pricing management solution (such as Pricing Cloud Service or RMFCS). Oracle Retail Insights supports loading price zones into the Cluster interfaces using RDE, or through externally interfaced data files. This data will make use of the same attributes outlined above, as well as following the same data structures and formats.

Consumer Attributes

Growing retailers need to attract new customers, and the key to attracting customers is understanding them. Oracle Retail Insights offers a means for retailers to understand and attract new customers and in so doing grow their businesses, through the use of consumer data from Oracle Data Cloud.

Retailers can use Oracle Retail Insights’ Consumer analysis to develop a deep understanding of consumers (that is, those shoppers who are their potential customers). It helps retailers understand the types of purchases each consumer segment makes, where the most desirable consumers live and shop, and in which product categories they should be competing for consumers. Building on that knowledge, retailers can build effective strategies to induce

consumers to buy their products, and convert them from out-of-reach, obscure consumers to familiar, loyal, and revenue-producing customers.

Getting Consumer Data

The process starts by identifying and segmenting your best customers in order to make requests to ODC for consumer data. The Customer Segmentation module of the AI Foundation Cloud Services can be used to create these customer groups. Once a request is made to ODC for a given list of customers (represented with Oracle Person IDs), they will return a group of consumers who best align to the characteristics of those individuals and represent ideal targets for consumer conversion. This consumer data is loaded into RI (using the W_RTL_CONSUMER_DS interface) for analysis, using a set of flexible attributes which can be relabeled to match the data you get back on the ODC responses.

RI also provides an optional Consumer Segment interface (W_RTL_CONSUMERSEG_DS) for directly loading details you may want to add to an ODC consumer group after creating it, such as a name or description for future reference. Lastly, the interfaces

W_RTL_CONS_METADATA_GS and W_RTL_CONS_DOMAIN_LKP_DS are used during implementation to configure which ODC attributes you have requested, so that RI can appropriately display the translatable text strings for them in reporting.

The following table summarizes the available Consumer attributes in RI:

Table 5-7 Consumer Dimension Attributes

AttributeDefinition
Consumer Segment Attributes
Consumer Segment IDUnique identifier of a consumer segment, as provided from the source
system for consumer data.
Consumer Segment NameShort name or description of a consumer segment, to be provided
manually for use in reporting.
Consumer Segment TypeThe type of consumer segment, such as one sourced from ODC or
another external system.
Consumer Segment DescDetailed description or supplemental details about a consumer
segment, such as the purpose of the segment or the actions taken on
it.
Consumer Segment Created
Date
System date when a consumer segment record was first established.
Consumer Segment Updated
Date
System date when a consumer segment record was last updated.
Consumer Segment RankThe ranked position of a consumer within a given segment. A value of
1 means that the consumer record was identified as the best fit for a
segment.
Consumer Segment SizeThe number of consumers belonging to a consumer segment at the
time the segment was processed.
Consumer Attributes
Consumer IDUnique identifier of a consumer.
Consumer UDA 1 to 100Consumer attribute value as provided by the source system. The
specific attributes in these fields will vary by implementation.
Consumer UDA 1 to 100 DescConsumer attribute description which can be translated or updated
over time for the same attribute value.
Consumer Create DateThe date a consumer record was first established in this system.

Table 5-8 (Cont.) Wholesale Customer Dimension Attributes

AttributeDefinition
Prospect FlagThis attribute indicates the organization is a prospect.
Supplier FlagThis attribute indicates the organization is a supplier.
Sales Account FlagThis attribute indicates the organization has a sales account with the
retailer.
Sales Ref FlagThis attribute indicates that sales exist for this organization.
Existing Sales Account FlagThis attribute indicates the organization has an existing sales account.
Sales Account Type CodeThis field indicates the type of sales account.
Internet home pageThis is the URL for the organization’s home page.
Customer Since DateThis is the date the organization became a customer.
Customer End DateThis is the date the organization’s customer relationship ended. It
could be something like the end of the latest sales contract that was
not renewed.
Customer Category CodeThis field indicates to which category the customer belongs.
Line of BusinessLine of business.
SIC CodeThis is the Standard Industry Classification code, a four-digit code
used by the US government for classifying industries.
SIC NameStandard Industry Classification name.
Govt ID TypeGovernment ID Type
Govt ID ValueGovernment ID Value
Service Provider FlagThis attribute indicates the organization is a service provider.
Potential Sales VolumeThis is the potential sales volume of the organization. This should be a
range of volume amounts. For example [0-500,000],
[500,000-1,000,000] and [1,000,000+].
Annual RevenueThis is the organization’s annual revenue amount.
Supplier IDThis is the supplier ID if the organization is a supplier.
Customer NumberThis is the internal customer number assigned to the organization.
Primary Contact NameThis is the primary contact name for the organization.
Primary Contact Phone
Number
This is the primary phone number for the organization.
Base Currency CodeThis is the base currency code of the organization.

Stockholding Franchise Locations

Franchising is the sales and distribution of products to customers who license a retailer’s trade name or services, or both, for a fee. Example services provided could include assortment planning, ordering, and store inventory management. A franchise leases the name of the operating retailer but is not owned by them; however in many situations a retailer manages its franchise stores very similarly to how it manages its own corporate stores, including managing its inventory. In such a situation retailers should create stockholding franchise locations as a way to manage their inventory. Because stockholding franchise locations and corporate locations function similarly, Oracle Retail Insights enables retailers to analyze them similarly while retaining the ability to segregate sales at franchise locations from sales at corporate locations.

Non-Stockholding Franchise Locations

If a retailer does not wish to manage the inventory of its franchise locations, those locations can be set up as non-stockholding franchise locations and analyzed accordingly. The retailer will retain the ability to analyze franchise sales separately from sales at corporate locations.

New/Remodeled Stores

New or recently remodeled stores tend to be more volatile and can have a skewing effect on business performance indicators. Sales and profits from new or recently modeled stores are not really comparable in business analysis and a retailer may decide to exclude them for analysis.

A store may be flagged as a New or Remodeled store in the Organization dimension. The flag can either be received from the merchandising source system or in case the retailer does not have the capability in the merchandising system to calculate the flag, RI can flag the stores as New or Remodeled through an RI driven logic. The flags can be set to ‘Y’ or ‘N’ by utilizing the variable RA_NEW_STORE_DT and RA_REMODEL_ STORE_DT in C_ODI_PARAM and the RI existing attributes - remodeled store date (W_INT_ORG_ATTR_D. ORG_ATTR1_DATE) and new store date (W_INT_ORG_ATTR_D. ORG_ ATTR2_DATE).

When supplying new/remodeled store dates directly (as well as store close dates on ORG_ATTR3_DATE), these first three date columns on W_INT_ORG_ATTR_D must be used, as all RI attributes used in reporting on these dates will only source data from these columns.

Organization Attributes

Table 5-9 lists the attributes of the Organization dimension.

Table 5-9 Organization Dimension Attributes

AttributeDefinition
CompanyName of a company. Company is the highest attribute within the
Organization hierarchy. A company consists of one or more chains.
Company NumberUnique ID from the source system that identifies a company.
ChainName of a chain. A chain consists of one or more areas.
Chain NumberUnique ID from the source system that identifies a chain.
Chain MgrName of a chain manager.
AreaName of an area. An area consists of one or more regions.
Area NumberUnique ID from the source system that identifies an area.
Area MgrName of an area manager.
RegionName of a region.
Region NumberUnique ID from the source system that identifies a region.
Region MgrName of a region manager.
DistrictName of a district. A district consists of one or more locations.
District NumberUnique ID from the source system that identifies a district.
District MgrName of a district manager.

Table 5-9 (Cont.) Organization Dimension Attributes

AttributeDefinition
LocLowest attribute within the organization hierarchy. It identifies a
warehouse, store, or partner within the company.
Loc NumberUnique ID from the source system that identifies a location.
Loc ListName of a location list. A location list is an intentional grouping of
locations for reporting purposes.
Loc List IDUnique ID from the source system that identifies a location list. A
location list is an intentional grouping of locations for reporting
purposes.
Loc TraitName of a location trait. A location trait is an attribute of a location that
is used to group locations with similar characteristics.
Loc Trait IDUnique ID from the source system that identifies a location trait. A
location trait is an attribute of a location that is used to group locations
with similar characteristics.
Tsf Entity IDUnique ID from the source system that identifies a transfer entity. A
transfer entity is a group of locations that share legal requirements
around product management. A location can belong to only one
transfer entity, and a transfer entity can belong to multiple organization
units.
Org Unit IDUnique ID from the source system that identifies a financial
organization unit. An organization unit can belong to only one set of
books.
SOB IDUnique ID from the source system that identifies a financial set of
books. A set of books represents an organizational structure that
groups locations based on how they are reported from an accounting
perspective.
Tsf Entity DescDetailed description of a transfer entity. A transfer entity is a group of
locations that share legal requirements around product management.
A location can be associated with only one transfer entity, and a
transfer entity can be associated with multiple organization units.
Comp FlagIndicator of whether a location has been opened for configurable time,
with values of “Y” for yes and “N” for no. Generally, comparable stores
are locations that are in operation for at least 53 weeks.
Comp Anchor YearWhen using the “same stores” method of comp store analysis, the
anchor year specifies which year of comp flag statuses should be
applied across previous years. This attribute is required in analyses
which use that method of comp reporting, and is generally set to the
current fiscal year.
New Store FlagIndicator of whether a location has been opened newly, with values of
”Y” for yes and “N” for no.
Remodeled Store FlagIndicator of whether a location has been remodeled recently, with
values of “Y” for yes and “N” for no.
Store TypeIndicator of the type of store, with values of “Company,” “Wholesale,“
and “Franchise.”

Table 5-9 (Cont.) Organization Dimension Attributes

AttributeDefinition
Address TypeType of address. Values are as follows:

01 – Business

02 – Postal

03 – Returns

04 – Order

05 – Invoice

06 – Remittance
Loc Name3Three-character abbreviation of a location name.
Loc Name10Ten-character abbreviation of a location name.
Loc Name SecondarySecondary name of a location.
Address Line 1First line of street address.
Address Line 2Second line of street address.
Address Line 3Third line of street address.
CityCity of a location.
Postal CodePostal code of a location.
Phone NumberPrimary phone number of a location.
Loc TypeType of location, with values of “Store,” “Warehouse,” and “External
Finisher.”
Linear DistanceTotal merchandisable space of a location. Feet is the unit of measure.
VAT Region IDUnique ID from the source system that identifies the Value Added Tax
(VAT) region in which a store is located.
VAT Included FlagIndicator of whether Value Added Tax (VAT) is included in the retail
price, with values of “Y” for yes and “N” for no.
Currency CodeBase currency code of the organization.
Break Pack FlagIndicator of whether a warehouse is capable of distributing less than
the supplier’s case quantity, with values of “Y” for yes and “N” for no.
Stockholding FlagIndicator of whether a location can hold stock, with values of “Y” for yes
and “N” for no. In a non-multichannel environment, the value is always
”Y”.
Loc MgrName of the manager of the organization.
MallName of the mall in which a store is located.
Loc Open DateOpen date of a location.
Loc Close DateClose date of a location.
Selling AreaTotal square footage of a store’s selling area.
Remodel DateDate that a location was last remodeled.
Tsf Zone IDUnique ID from the source system that identifies a transfer zone. A
transfer zone is an intentional grouping of locations for transferring
owned inventory from one location to another. A location can belong to
only one transfer zone.
Promo Zone IDUnique ID from the source system that identifies a promotion zone. A
promotion zone is an intentional grouping of locations for promotion
activity. A location can belong to only one promotion zone.
Total AreaTotal square footage of a location.

Table 5-9 (Cont.) Organization Dimension Attributes

AttributeDefinition
Default WH IDWarehouse that can be used as the default for creating cross-dock
masks. This determines which stores may be sourced by a warehouse,
and it only contains virtual warehouses in a multichannel environment.
Store Format DescDescription of a store format. Examples are Conventional Store,
Supermarket, Virtual Store, Catalog Store, and Hard Discount.
Store Format IDUnique ID from the source system that identifies a store format.
StateState name of a location.
CountryCountry name of a location.
Banner IDUnique ID from the source system that identifies a banner. A banner is
the name of a retailer’s subsidiary.
BannerName of a banner. A banner is the name of a retailer’s subsidiary.
ChannelName of a channel. A channel is a method for a retailer to interact with
a customer, and it is an outlet for sale and delivery of goods and
services to the customer. A retailer can have multiple outlets, such as
brick-and-mortar stores, Web sites, and catalogs.
Channel IDUnique identifier associated with a channel.
Channel TypeType of channel to interact with a customer. The values are “Brick and
Mortar,” “Webstore,” and “Catalog.”
Virtual WH FlagIndicator of whether a location is a virtual warehouse, with values of
“Y” for yes and “N” for no.
Physical WH IDUnique ID from the source system that identifies a physical warehouse
that is assigned to a virtual warehouse.
State CodeCode that identifies the state of the location.
Sister Store IDLocation that will be used to relate a current store to the historical data
of an existing store.
Store ClassType of store class, which retailers can use to group their stores. The
best stores are typically considered “A” stores, the next-best “B” stores,
and so on. Values can be “A,” “B,” “C,” “D,""E,” and “X”.
WH Delivery PolicyContains the delivery policy of the warehouse.
WH Redistribution IndicatorIndicates that the warehouse is a re-distribution warehouse. Used as a
location on Purchase Orders in place of actual locations that are
unknown at the time of Purchase Order creation and approval. Valid
values are Y or N.
WH Replenishment IndicatorThis indicator determines if a warehouse is replenishable.
WH Finisher IndicatorIndicates if this virtual warehouse is an internal finisher.
Virtual WH TypeIndicates the type of virtual warehouse. Codes vary by retailer and are
specified in the source system.
WH Inbound Handling DaysWarehouse inbound handling days are defined as the number of days
that the warehouse requires to receive any item and get it to the shelf
so that it is ready to pick.
Duns LocationHolds the location associated with the DUNS number.
DUNS NumberHolds the Dun and Bradstreet number to identify the company.
Loc Customer Order FlagIndicates whether the location is customer order location or not.
Loc Customer Order Ship FlagIndicates whether the location is able to ship customer orders or not.

Table 5-9 (Cont.) Organization Dimension Attributes

AttributeDefinition
Loc Email AddressContains the email address for the store or warehouse.
Loc Fax NumberContains the fax number for the location.
Loc Gift Wrapping FlagIndicates whether the location supports gift wrapping or not.
Store Acquired DateContains the date on which the store was acquired.
Store Language ISO CodeHolds the ISO code associated with the given store language.
Total Selling AreaTotal store selling area as a summable metric for reporting at higher
levels of the hierarchy.

Comparable Store

Comp stores are really established stores as opposed to new or closed stores. Comp store measurements are important to an analyst because profits and sales from the more established stores provide stable indicators of business performance. New or closed stores tend to be more volatile and can have a skewing effect on business performance indicators. Sales and profits from new or closed stores are not really comparable in business analysis, and as a result, they are not included in the comp store measurements.

The Comparable Store Flag can be sent from the retailer’s non-Oracle merchandising source system or manually derived and loaded into the RI interface for W_RTL_LOC_COMP_MTX_DS. Note that RI does not load comp flag information from RMFCS in either case; it is either sourced externally and interfaced to RI, or derived by hand and uploaded as-needed. In both cases, the data should consist of a pipeline delimited flat file containing Store ID, Comp Store Flag, Effective From Date, which will form the interface file that must be loaded to W_ RTL_LOC_COMP_MTX_DS table. This file can contain flag values in (N, Y, C), representing non-comparable, comparable, and closed stores respectively.

RI provides multiple methods for reporting on comparable stores, depending on the retailer’s business needs. In the “Same Store” method of comparison, the stores designated as comp/ non-comp/closed in a reporting period have their history grouped under the same statuses for previous years as well, allowing the retailer to always be comparing the same stores this year versus last year in comp reporting. This option is enabled using the SAME_STORES variable in C_ODI_PARAM. If set to ‘Y’ then this method is enabled for both As-Is and As-Was reporting. The number of years of history to “duplicate” the comp statuses across is configured with the ANCHOR_TO_YEARS variable, which defaults to 2 years (this year and last year).

If Same Stores comp reporting is disabled, then both subject areas instead use As-Was comp reporting (also known as Group Comp). This method will consider the historical values of the Comp Flag and directly report a store’s history based on its comp status at that point in time. This type of reporting may split a store’s history across different comp statuses within the same analysis.

Product

The Product dimension represents the product lines that the company sells. The Product dimension is essential to the department manager who needs to know which items turn the highest profit, or how an item performs within the market as a whole. Because of its importance for analysis in the retail environment, attributes from the Product dimension are present in nearly every data mart in Retail Insights. In most cases, data is kept at the lowest level in the hierarchy (item), to allow maximum flexibility and detail in reporting.

Style/Color configuration of a fashion retailer, this is the same as the Color level of reporting, but it has the flexibility to support whatever combination of diffs are used in RMFCS.

The following attributes allow for building reports at the Item Diff Aggregate level:

  • Item Diff Agg ID

  • Item Diff Agg Desc

They are arranged in the following hierarchy: Item Level 1 > Item Diff Agg > Item.

Product Attributes

Table 5-10 lists the attributes of the Product dimension:

Table 5-10 Product Dimension Attributes

Attribute
Company Number
Definition
Unique ID from the source system that identifies a company.
CompanyName of a company. A company consists of one or more divisions.
Division NumberUnique ID from the source system that identifies a division.
DivisionName of a division. A division is the highest category of merchandise
within an organization. Typically a division is used to signify the overall
category of merchandise, such as hardlines or apparel.
Division Buyer NumberUnique ID from the source system that identifies a division buyer.
Division BuyerName of a division buyer, an executive responsible for purchasing
merchandise to be sold in a store or retail channel for a particular
division.
Division Merchant NumberUnique ID from the source system that identifies a division merchant.
Division MerchantName of a division merchant.
Group NumberUnique ID from the source system that identifies a group.
GroupName of a group. A group is the next level of merchandise in a
hierarchy below division. A group consists of one or more departments.
A group can belong to only one division.
Group Buyer NumberUnique ID from the source system that identifies a group buyer.
Group BuyerName of a group buyer. A group buyer is an executive responsible for
purchasing merchandise to be sold in a store or retail channel for a
particular group.
Group Merchant NumberUnique ID from the source system that identifies a group merchant.
Group MerchantName of a group merchant.
Department NumberUnique ID from the source system that identifies a department.
DepartmentName of a department. A department is the next level below group in
the merchandise hierarchy. A group can have multiple departments.
Key information about how inventory is tracked and reported is stored
at the department level.
Department Buyer NumberUnique ID from the source system that identifies a department buyer.
Department BuyerName of a department buyer, an executive responsible for purchasing
merchandise to be sold in a store or retail channel for a particular
department.
Department Merchant NumberUnique ID from the source system that identifies a department
merchant.

Table 5-10 (Cont.) Product Dimension Attributes

AttributeDefinition
Department MerchantName of a department merchant.
Profit Calc TypeIndicator of the profit calculation type, with values of “Direct Cost” and
“Retail Inventory”.
Purchase TypeIndicator of the purchase type of merchandise, with values of “Owned”,
“Consignment”, and “Concession.”
OTB Calc TypeIndicator of the open–to-buy calculation type, with values of “Cost” and
“Retail.”
Class NumberID within a department that uniquely identifies a class.
ClassName of a class. A class is the next level below department in the
merchandise hierarchy. A department can have multiple classes. A
class provides the means to group products within a department. A
class consists of one or more subclasses.
Class Buyer NumberUnique ID from the source system that identifies a class buyer.
Class BuyerName of a class buyer, an executive responsible for purchasing
merchandise to be sold in a store or retail channel for a particular
class.
Class Merchant NumberUnique ID from the source system that identifies a class merchant.
Class MerchantName of a class merchant.
Subclass NumberID within a department number and class number that uniquely
identifies a subclass. A class can have multiple subclasses.
SubclassName of a subclass. A subclass defines the type of merchandise sold
in a department and class.
Subclass Buyer NumberUnique ID from the source system that identifies a subclass buyer.
Subclass BuyerName of a subclass buyer, an executive responsible for purchasing
merchandise to be sold in a store or retail channel for a particular
subclass.
Subclass Merchant NumberUnique ID from the source system that identifies a subclass merchant.
Subclass MerchantName of a subclass merchant.
Item NumberUnique ID from the source system that identifies an item.
ItemDetailed description of an item. Item is the lowest-level attribute within
a product hierarchy. Sales and inventory facts are tracked at one of the
predetermined levels within the Item attribute.
Pack FlagIndicator of whether an item is a pack. A pack item is a collection of
items that can be ordered or sold as a single unit.
Package SizeSize of the product printed on packaging.
Package UOMUnit of measurement in which a package size is measured.
Item LevelIndicator of the level within an item family, with values of 1, 2, and 3.
Transaction LevelIndicator of the level within an item family that inventory is tracked, with
values of 1, 2, and 3.
Item Level 1 NumberItem number of the highest level in an item family.
Item Level 1 DescItem description of the highest level in an item family.
Item Level 2 NumberItem number of the second level in an item family.
Item Level 2 DescItem description of the second level in an item family.

Table 5-10 (Cont.) Product Dimension Attributes

AttributeDefinition
Item Level 3 NumberItem number of the lowest level in an item family.
Item Level 3 DescItem description of the lowest level in an item family.
Item Diff Agg IDCombination of item differentiators used to define the aggregate
reporting level between Level 1 and Level 2.
Item Diff Agg DescDescription of item differentiators used to define the aggregate
reporting level between Level 1 and Level 2.
Color Item Diff AggThe color of an item, when used as an item diff aggregate.
Size Item Diff AggThe size of an item, when used as an item diff aggregate.
Flavor Item Diff AggThe flavor of an item, when used as an item diff aggregate.
Brand Item Diff AggThe brand of an item, when used as an item diff aggregate.
Style Item Diff AggThe style of an item, when used as an item diff aggregate.
Fabric Item Diff AggThe fabric of an item, when used as an item diff aggregate.
Scent Item Diff AggThe scent of an item, when used as an item diff aggregate.
Original RetailOriginal retail price of an item per unit and is stored in the primary
currency.
Mfg Recommended RetailRecommended manufacturer’s retail price of an item per unit, stored in
the primary currency.
Pack NumberItem number where PACK_FLG = Y. A pack item is a collection of items
that can be ordered or sold as a single unit.
Pack Item QuantityQuantity of a pack component item units that make up a pack.
Pack DescItem description where PACK_FLG = Y. A pack item is a collection of
items that can be ordered or sold as a single unit.
Pack UOMStandard unit of measurement for a pack item.
Item List IDUnique ID from the source system that identifies an item list. An item
list is an intentional grouping of items for operational purposes.
Item List DescDetailed description of an item list. An item list is an intentional
grouping of items for operational purposes.
UDA Head IDUnique ID from the source system that identifies a user-defined
attribute of an item. A UDA head is a parent of a UDA detail.
UDA Head DescDetailed description of a user-defined attribute of an item. A UDA head
is a parent of a UDA detail.
UDA Detail IDUnique ID from the source system that identifies a user-defined
attribute detail of an item. A UDA detail can be a child of only one UDA
parent.
UDA Detail DescDetailed description of a user-defined attribute detail of an item. A UDA
detail can be a child of only one UDA parent.
Diff TypeIndicator of the differentiator type, with example values of “Size,“
“Color,” “Flavor,” “Scent,” and “Pattern.” A differentiator type is a parent
of a differentiator.
Diff IDUnique ID from the source system that identifies an item differentiator.
Differentiators define the characteristics of an item. A differentiator can
be a child of only one differentiator type.
Diff DescDescription of an item differentiator. A differentiator can be a child of
only one differentiator type.

Table 5-10 (Cont.) Product Dimension Attributes

AttributeDefinition
UOMStandard unit of measurement for an item.
Item Number Type CodeIndicator of the type of numbering system used to identify an item.
Values are as follows:

Oracle Retail Item Number

UCC12

UCC12 with Supplement

UCC8

UCC8 with Supplement

EAN/UCC-8

EAN/UCC-13

EAN/UCC-13 with Supplement

ISBN-10

ISBN-13

NDC/NHRIC – National Drug Code

PLU

Variable Weight PLU

SSCC Shipper Carton

EAN/UCC-14

Manual

Custom Item Type
Item Input FlagIndicator of whether an item holds inventory for an item transformation,
with values of “Y” for yes and “N” for no.
Merchandise FlagIndicator of whether an item is merchandise, with values of “Y” for yes
and “N” for no.
Pack Retail FlagIndicator of whether a pack has its own unique retail price, or if a pack
retail price is the sum of its components’ retail prices, with values of “Y”
for yes and “N” for no.
Class AlternateAlternate version of the Class attribute which operates only on the
description of the class, allowing for grouping of same-named classes
onto the same result row in an analysis.
Subclass AlternateAlternate version of the Subclass attribute which operates only on the
description of the subclass, allowing for grouping of same-named
subclasses onto the same result row in an analysis.
Item DescDescriptive text for the transaction-level item from the merchandising
system, without any appended values such as item numbers.
Item UDA ID 1 - 50
Item UDA Desc 1 - 50
User-defined attributes which have been “pivoted” into a column-based
structure, allowing for side-by-side usage in reporting. Content of the
attributes is determined by populating the
W_RTL_UDA_METADATA_G interface.
Item Diff ID 1 - 8
Item Diff Desc 1 - 8
User-defined differentiators which have been “pivoted” into a column-
based structure, allowing for side-by-side usage in reporting. Content
of the attributes is determined by populating the
W_RTL_UDA_METADATA_G interface.
Item Supplier LabelThe descriptive label for an item as provided by the supplier to the
merchandising system.
Item Supplier VPNThe vendor product number as provided by the supplier to the
merchandising system.

Table 5-10 (Cont.) Product Dimension Attributes

AttributeDefinition
Item Supplier Origin CountryThe origin country as provided by the supplier to the merchandising
system.
Item Supplier Pickup Lead
Time
The pickup leadtime as provided by the supplier to the merchandising
system.
Item Supplier Inner Pack SizeThe inner pack size of an item as provided by the supplier to the
merchandising system.
Item Secondary DescThe secondary item description optionally provided in the
merchandising system.
Item Primary Part NumberThe primary part number associated with a transaction item, such as a
UPC or EAN number.
Item Primary Part DescThe primary part description associated with a transaction item, such
as a UPC or EAN description.
Pack Comp QtyPack component item units contained within a pack item.
Color GroupDescription of the differentiator group used to setup items having a
Color attribute in the merchandising system.
Color Group IDIdentifies the differentiator group used to setup items having a Color
attribute in the merchandising system.
Container ItemThis field holds the container item number for a contents item.
Diff GroupDescription of the differentiator group used to setup items in the
merchandising system.
Diff Group IDDifferentiator group used to setup items in the merchandising system.
Item Case TypeThis field determines which case sizes to extract against an item for
inventory planning applications
Item Catch Weight FlagIndicates whether the item should be weighed when it arrives at a
location.
Item Catch Weight Order TypeThis field determines how catch weight items are ordered.
Item Catch Weight Sale TypeThis field indicates the method of how catch weight items are sold in
store locations.
Item Catch Weight UOMUnit of measure for catch weight items.
Item Cost Zone GroupCost zone group associated with the item.
Item Default Waste PercentDefault daily wastage percent for spoilage type wastage items.
Item Deposit Price Per UOMThis field indicates if the deposit amount is included in the price per
UOM calculation for a contents item ticket.
Item Deposit TypeThis field is the deposit item component type. A NULL value in this field
indicates that this item is not part of a deposit item relationship.
Item Forecastable FlagIndicates if this item will be interfaced to an external forecasting system
(Y, N).
Item Gift Wrap FlagThis field will contain a value of Y if the item is eligible to be gift
wrapped.
Item Handling SensitivityHolds the sensitivity information associated with the item.
Item Handling TempHolds the temperature information associated with the item.
Item Retail Label TypeThis field indicates any special label type associated with an item (i.e.
pre-priced or cents off).

Table 5-10 (Cont.) Product Dimension Attributes

AttributeDefinition
Item Retail Label ValueThis field represents the value associated with the retail label type.
Item Service LevelHolds a value that restricts the type of shipment methods that RCOM
can select for an item.
Item Ship Alone FlagThis field will contain a value of Y if the item should be shipped to the
customer is a separate package versus being grouped together in a
box.
Item Short DescShortened description of the item.
Item Store Order MultipleMerchandise shipped from the warehouses to the stores must be
specified in this unit type or multiple.
Item UOM Conversion FactorConversion factor between an Each and the STANDARD_UOM when
the STANDARD_UOM is not in the quantity class.
Item Waste PercentAverage percent of wastage for the item over its shelf life.
Item Waste TypeIdentifies the wastage type as either Sales Wastage or Spoilage
Wastage.
Pack Orderable CodeCode identifying the type of orderable pack. An orderable pack is a
collection of items that is ordered as a single unit. Values include V
(vendor pack), B (buyer pack) and N (not orderable).
Pack Sellable CodeCode identifying the type of sellable pack. A sellable pack is a
collection of items that is sold as a single unit. Values include S
(sellable) and N (not sellable).
Pack Type CodeCode identifying the type of pack. A pack is a collection of one or more
items with varying quantities. Values include S (simple pack) and C
(complex pack).
Perishable Item FlagA grocery item attribute used to indicate whether an item is perishable
or not.
Simple Pack Comp NumberThe component item number contained in a simple pack. Use this
attribute to display the component of a sellable simple pack in-line with
other data. If the item is not a simple pack, it will just repeat the selling
item number.
Simple Pack Comp QtyThe component item quantity contained in a simple pack. Use this
attribute to display the number of units in a sellable simple pack in-line
with other data. If the item is not a simple pack, it will display a quantity
of 1.
Size GroupDescription of the differentiator group used to setup items having a
Size attribute in the merchandising system.
Size Group IDIdentifies the differentiator group used to setup items having a Size
attribute in the merchandising system.
Item Orderable FlagIndicates if the item is orderable in the merchandising system.

Table 5-11 Product Split Dimension Attributes

AttributeDefinition
StyleThis attribute displays the style of an item.
ColorThis attribute displays the color of an item.
SizeThis attribute displays the size of an item.

Table 5-11 (Cont.) Product Split Dimension Attributes

AttributeDefinition
FabricThis attribute displays the fabric of an item.
FlavorThis attribute displays the flavor of an item.
ScentThis attribute displays the scent of an item.
Color AlternateThis attribute displays the description of a color in primary language,
for use in grouping report results by the color label.
Size AlternateThis attribute displays the description of a size in primary language, for
use in grouping report results by the size label.
Season AlternateThis attribute displays the description of a season in primary language,
for use in grouping report results by the season label. This has been
copied over from the Season Phase dimension for use in item/season
based reports.
Phase AlternateThis attribute displays the description of a season phase in primary
language, for use in grouping report results by the phase label. This
has been copied over from the Season Phase dimension for use in
item/season based reports.
Item Part DescDescription of the code associated with a product that is typically
printed on the physical item, such as a UPC, EAN, or PLU. A single
SKU may have multiple part numbers associated with it.
Item Part NumberA code associated with a product that is typically printed on the
physical item, such as a UPC, EAN, or PLU. A single SKU may have
multiple part numbers associated with it.

Product Images

RI is capable of displaying item images that have been configured for use in RMFCS. RI directly captures the URLs which have been assigned to items and exposes them to OAS as string attributes. The URLs can be displayed as images by changing the column’s Data Format option to either Image URL or HTML. The Image URL format will directly perform a GET browser request on the URL and return the image exactly as it is formatted on the host system. The HTML format allows you to enter custom HTML tags to change the format of the image, such as the width or height. All URLs must use the HTTPS protocol, image URLs using HTTP will not be rendered in RI. The image URLs are a concatenation of the file path and file name from RMFCS, without any manipulation. Ensure that this concatenation results in a valid URL before using it in RI.

An example column formula that can be used in conjunction with the HTML data format is provided below:

'<img src='||"Item As Is"."Item Image"||' width=100 height=100 />'

This formula will display the image at a forced 100x100 pixel size, which is a typical viewing size in reports where the image is just a reference (e.g. to see the color or silhouette) rather than the focus of the analysis.

Table 5-12 lists the attributes for item images.

Table 5-12 Product Image Attributes

AttributeDefinition
Item ImageImage representing a transaction item.
Style ImageImage representing a style or parent-item.
Subclass ImageImage representing a subclass.
Class ImageImage representing a class.
Department ImageImage representing a department.
Group ImageImage representing a group.
Division ImageImage representing a division.
Company ImageImage representing a company.
Item Attribute ImageImage representing an item attribute.
Default Item Attribute ImageThis is the default Item Attribute image.
Second Half Item ImageThis attribute displays the description of the Item image used in the
item similarity comparison.

Table 5-13 lists the attributes of the Related Items dimension. These values are sourced from the related item data in RMFCS. Related item attributes are currently supported with the Sales and Inventory Position facts. Related items should be viewed along with the Item dimension to see the full relationship.

Table 5-13 Product Org Dimension Attributes

AttributeDefinition
Item Relationship IDUnique identifier for the relationship with a related item.
Item Relationship NameName given to the relationship with a related item.
Item Relationship TypeDescribes the type of relationship for a related item. Values are
configured in code_detail table under code_type IREL. Valid values:
CRSL, SUBS.
Related Item DescDescription of the related item.
Related Item End DateIndicates the date till the related items can be used for transactions. A
null value means it’s effective indefinitely.
Related Item NumberUnique identifier of the related item.
Related Item PriorityRelative priority of a related item when multiple items are assigned.
Applicable only in case of relationship type SUBS.
Related Item Start DateIndicates the date when the related items can be used for transactions.

Substitute Items

Table 5-14 lists the attributes of the Substitute Items dimension. These values are sourced from the substitute item data in RMFCS. Substitute item attributes are currently supported with the Sales and Inventory Position facts. Substitute items should be viewed along with the Item and Organization dimensions to see the full relationship.

Table 5-14 Substitute Items Dimension Attributes

AttributeDefinition
Substitute End DateIndicates the date when the substitution will end for the main item
Substitute Item DescDescription for the substitute item.
Substitute Item Fill PriorityContains the fill priority for the main item relative to a substitute item
and is NULL if LOC_TYPE is not W (Warehouse). Valid values for this
field are: M (main), S (substitute)
Substitute Item NumberUnique identifier for the substitute item.
Substitute Item Pick PriorityContains the pick priority for the substitute item. If there are multiple
substitute items for a main item, then the pick priority will determine the
order the item is picked.
Substitute ReasonReason for substituting the item.
Substitute Replenishment PackContains the replenishment pack, if any, that will be used to fulfill the
demand of the associated item.
Substitute Start DateIndicates the date when the substitution will start for the main item.

Product Org Attributes

Table 5-15 lists the attributes of the Product Org Attributes dimension. These values are sourced from the item/loc traits and replenishment item loc table data in RMFCS

Table 5-15 Product Org Dimension Attributes

AttributeDefinition
Backorder IndicatorContains a value of Y to indicate the item is backorderable.
Electronic Marketing ClubCode representing the electronic marketing club the item belongs to at
the location.
Food Stamp IndicatorContains a value of Y when the item is eligible for food stamps.
In Store Market BasketContains the in store market basket code for the item/location.
Manual Price EntryContains a value of Y when the item is expected to have manual price
entries at the POS for a location.
National Brand Comparison
Item
Nationally branded item to which you would like to compare the current
item.
Refundable IndicatorContains a value of Y to indicate the item is refundable at that location.
Returnable IndicatorContains a value of Y to indicate the item is returnable to that location.
Reward Club Eligible IndicatorWhether the item is valid for various types of bonus point or award
programs at the location.
Store Reorderable IndicatorContains a value of Y to indicate the item is reorderable to that
location.
WIC IndicatorContains a value of Y to indicate the item is eligible for the Women,
Infants, and Children (WIC) program.
Item Loc StatusCurrent status of item at the store
Item Loc Previous StatusPrevious status of item at the store
Item Loc Status Update DateDate on which the status for item at the store was most recently
changed.

Table 5-15 (Cont.) Product Org Dimension Attributes

AttributeDefinition
Item Loc Ranged FlagContains a value of Y to indicate the item location ranging.
Item Loc Clearance FlagContains a value of Y to indicate the item is on clearance at the store.
Item Loc Taxable FlagContains a value of Y to indicate the item is taxable at the store.
Item Loc Local DescContains the local description of the item at a specific location.
Item Loc Local Short DescContains the local short description of the item at a specific location.
Item Loc Pallet Tier UnitsContains the number of shipping units (cases) that make up one tier of
a pallet. Multiply TIER x HEIGHT to get total number of cases for a
pallet.
Item Loc Pallet HeightContains the number of tiers that make up a complete pallet (height).
Multiply TIER x HEIGHT to get total number of cases for a pallet.
Item Loc Store Order MultiplesContains the multiple in which the item needs to be shipped from a
warehouse to the location.
Item Loc Daily Waste PercentContains the average percentage lost from inventory on a daily basis
due to natural wastage.
Item Loc Size of EachContains the size of an each in terms of the uom_of_price.
Item Loc Ticket SizeContains the size to be used on the ticket in terms of the
uom_of_price.
Item Loc Ticket UOMContains the unit of measure that will be used on the ticket for this
item.
Item Loc Primary VariantAddress sales of PLUs (i.e. above transaction level items) when
inventory is tracked at a lower level (i.e. UPC).
Item Loc Primary Cost PackContains an item number that is a simple pack containing the
Item Loc Primary Supplieritem in the item column for this record.
Item Loc Primary CountryContains the numeric identifier of the supplier who will be considered
the primary supplier for the specified item/loc.
Item Loc Inbound Handling
Days
Contains the identifier of the origin country which will be considered
the primary country for the specified item/location.
Contains the number of inbound handling days for an item at a
warehouse type location.
Item Loc Source MethodSpecifies how the ad-hoc PO/TSF creation process should source the
item/stores request.
Item Loc Source WarehouseUsed by the ad-hoc PO/Transfer creation process to determine which
warehouse to fill the stores request from.
Item Loc UIN TypeContains the unique identification number (UIN) used to identify the
instances of the item at the location.
Item Loc UIN LabelContains the label for the UIN when displayed in SIM.
Item Loc UIN Capture TimeIndicates when the UIN should be captured for an item during
transaction processing.
Item Loc UIN Generation FlagContains a value of Y to indicate the UIN is being generated in the
external system.
Item Loc Franchise Costing
Loc ID
Indicates if the costing location of the franchise store is a store or a
warehouse.
Item Loc Franchise Costing
Loc Type
Contains the type of costing location in the costing location field.

Table 5-15 (Cont.) Product Org Dimension Attributes

AttributeDefinition
Replenishment Order MethodDetermines if the replenishment process will create an actual order/
transfer line item for the item location if there is a need for it or if only a
record is written to the Replenishment Results table. Valid values are
Manual, Semi-Automatic, Automatic, or Buyer Worksheet.
Replenishment MethodContains the character code for the algorithm that will be used to
calculate the recommended order quantity for the item location. Valid
values include Constant, Min/Max, Floating point, Time Supply,
Dynamic, SO Store Orders. Replenishment Increment Percent
Replenishment Increment
Percent
Contains the percentage by which the min and max stock levels will be
multiplied when calculating the recommended order quantity.
Replenishment Supply Min
Days
Contains the minimum number of days of supply of stock to maintain.
Replenishment Supply Max
Days
Contains the maximum number of days of supply of stock to maintain.
Replenishment Time Supply
Horizon
Contains the number of days over which an average sales rate is
calculated to be used in the Time Supply replenishment method
algorithm.
Replenishment Inventory
Selling Days
Contains the number of required days of on hand inventory to satisfy
demand.
Replenishment Reject Orders
Flag
Contains a value of Y to indicate if uploaded store orders with needs
date on or after the NEXT_DELIVERY_DATE are valid.
Replenishment Lost Sales
Factor
Contains the percentage of sales that could have occurred if inventory
had been available through the order lead time.
Replenishment Scaling Exempt
Flag
Contains a value of Y to indicate if the item/location should be exempt
from scaling during the order scaling process during the replenishment
process
Replenishment Order Scale
Max Value
Contains the limit up to which order scaling can increase the order
quantity for the item/location during the replenishment process.
Replenishment Terminal Stock
Qty
Contains the desired stock on hand for the item location when the end
of season is reached.
Replenishment Season IDContains the numeric identifier of the season for which this item
location is being replenished.
Replenishment Phase IDContains the numeric identifier of the phase within the season for
which this item location is being replenished.
Replenishment Last Review
Date
Contains the date on which the item location was last reviewed.
Replenishment Next Review
Date
Contains the date on which the item location will be reviewed next.
Replenishment Order Unit
Tolerance
Contains the allowable unit change to order quantities generated from
replenishment.
Replenishment Order Percent
Tolerance
Contains the allowable percent change to order quantities generated
from replenishment.
Replenishment Tolerance FlagContains a value of Y to indicate unit and percent tolerances will be
used.
Replenishment Last Delivery
Date
Contains the last delivery date that replenishment was run for.

Table 5-15 (Cont.) Product Org Dimension Attributes

AttributeDefinition
Replenishment Next Delivery
Date
Contains the next delivery date calculated for the next review cycle.
Replenishment MBR Order QtyPopulated if the item on replenishment is using the Warehouse
Stocked/Cross-Docked stock category.
Replenishment MBR Pickup
Lead Time
Contains the pickup lead time for MBR cross-link line items after reqext
processes them.
Replenishment MBR Supplier
Lead Time
Contains the supplier lead time for MBR cross-link line items after
reqext processes them.
Replenishment Transfer PO
Link
Contains a reference number to link the item on the transfer to any
purchase orders that have been created to allow the from location (i.e.
warehouse) on the transfer to fulfill the transfer quantity to the to
location (i.e store) on the transfer.
Replenishment Last ROQContains the last recommended order quantity created by Vendor
Replenishment Extraction (rplext.pc).
Replenishment Pack Size LevelContains the pack size level (Case, Inner, Each) at which the item is
shipped between warehouses and stores.
Replenishment Unit CostContains the unit cost for the item for the replenishment supplier/
country.
Replenishment Supplier Lead
Time
Contains the number of days that will elapse between the date an
order is written and the delivery to the store or warehouse from the
supplier.
Replenishment Inner Pack SizeContains the break pack size for the item for the supplier.
Replenishment Pack SizeContains the quantity that orders must be placed in multiples of for the
supplier of the item.
Replenishment Pallet Tier
Units
Contains the number of shipping units (cases) that make up one tier of
a pallet. Multiply TIER x HEIGHT to get total number of units (cases)
for a pallet.
Replenishment Pallet HeightContains the number of tiers that make up a complete pallet (height).
Replenishment Rounding LevelThis field determines how order quantities will be rounded to Case,
Layer and Pallet.
Replenishment Inner Rounding
Threshold
Contains the Inner Rounding Threshold value.
Replenishment Case Rounding
Threshold
Contains the Case Rounding Threshold value.
Replenishment Layer
Rounding Threshold
Contains the Layer Rounding Threshold value.
Replenishment Pallet
Rounding Threshold
Contains the Pallet Rounding Threshold value.
Replenishment Service Level
Type
Contains the Service Level Type (Simple Sales or Standard) that will
drive the safety stock calculation algorithm.
Replenishment Zero SOH
Transfer Flag
Contains a value of N to indicate a transfer should be created even
though the warehouse does not have enough stock on hand.
Replenishment Multiple Per
Day Flag
Contains a value of N to indicate if an item can be replenished multiple
times per day at the location.
Replenishment Supplier Lead
Time Flag
Indicates if the supplier lead time will be considered in the calculation
of time supply order points and order up to point.

Table 5-15 (Cont.) Product Org Dimension Attributes

AttributeDefinition
Replenishment Supplier NumContains the numeric identifier of the supplier from which the specified
location will source the replenishment demand for the specified item
location.
Replenishment Country CodeContains the country code of the supplier country that will be used to
supply the replenishment demand for the specified item location.
Replenishment Review CycleContains the number representing when the specified item location will
be reviewed for replenishment. Valid values are 0-14. A 0 represents a
weekly review cycle, a 1 represents a daily review cycle, a 2 represents
a review cycle of every 2 weeks, a 3 represents a review cycle of every
3 weeks, etc.
Replenishment Stock CategoryContains the sourcing strategy for the item/location relationship.
Replenishment Source WHContains the numeric identifier of the warehouse through which the
specified item will be sourced, or will crossdock to the specified store.
Replenishment Activate DateContains the date on which the item location will start to be reviewed
for replenishment.
Replenishment Deactivate
Date
Contains the date at which time the item location will no longer be
reviewed for replenishment.
Replenishment Pres StockContains the minimum amount of stock that needs to be on store
shelves.
Replenishment Demo StockContains the amount of stock that cannot be sold as new and is not
counted as part of inventory in the replenishment calculations.
Replenishment Min StockContains the required minimum number of units available for sale.
Replenishment Max StockContains the required maximum number of units available for sale.
Replenishment Service LevelContains the required measure of the probability that demand is
satisfied from on hand inventory.
Replenishment Pickup
Leadtime
Contains the expected number of days required to ship the item from
the supplier to the initial receiving location.
Replenishment WH LeadtimeContains the expected number of days required to move the item from
the warehouse to the store defined on this record.
Item Loc Deposit Code FlagIndicates whether a deposit is associated with this item at the location.
Item Loc Proportional Tare PctContains the value associated of the packaging in items sold by weight
at the location.
Item Loc Fixed Tare ValueContains the value associated of the packaging in items sold by weight
at the location.
Item Loc Fixed Tare UOMContains the unit of measure value associated with the tare value.
Item Loc Return PolicyContains the return policy for the item at the location.
Item Loc Stop Sale FlagIndicates that sale of the item should be stopped immediately at the
location
Item Loc Report CodeContains the code to determine the reports the location should run.
Item Loc Flex Attr 1 - 25Item Location level custom flex attributes matching standard CFA
datatypes and formatting

Promotion

A promotion is an attempt to stimulate the sale of particular merchandise. This can be accomplished by temporarily reducing its price, advertising it, or linking its sale to offers of other merchandise at reduced prices or free. A promotion can take place for many different reasons, such as the desire to attract a certain type of customer, increase sales of a particular class of merchandise, introduce new items, or gain competitive advantage. Tracking of sales and demand by promotion allows retailers to assess the success in attracting customers to purchase items that are placed on promotion.

A single promotion can be part of a larger effort or event. Several promotions can be associated with an event. For example, a summer sale event might consist of multiple promotions.

There are a number of formats in which a promotion can be offered. Some common examples of these formats are as follows:

  • Get a specific percent off the price of an item

  • Buy a certain quantity of an item and get a certain amount off the total purchase value

  • Buy a certain item and get a discount on another item

  • Get free shipping and handling

Typically, a promotion on an item is not applied universally. It might be triggered only for certain stores, for certain media, for certain customer types, or for certain offer coupons. The type of circumstance that triggers a promotion is called the promotion trigger type. In a brick-andmortal market, a promotion is always triggered by the store. In a direct-to-consumer market, there can be different trigger types such as Source Code, Media Code, Selling Item Code, or Customer Type. One promotion can be triggered by only one promotion trigger type.

It is also possible that the retailer has multiple sources of promotions both internal and external to their Oracle applications. RI has the ability to source promotions directly from the RPM and Customer Engagement applications. It can also accept external promotions through a separate interface. Regardless of the source of the promotion data, it is assumed that the retailer will ensure uniqueness of the promotions across all source systems, such that the sales transactions occurring under a specific promotion can be correctly identified and reported on.

Table 5-16 lists the attributes of the Promotion dimension.

Table 5-16 Promotion Dimension Attributes

AttributeDefinition
Promo SourceIdentifier for the source system of the promotion data, in cases where
multiple source systems are generating promotions (such as RPM, CE,
and OMS).
Promo IDUnique ID from the source system that identifies a promotion. A
promotion is an intentional grouping of promotion offers. A promotion
can only be a child of a single promotion event. Multiple promotions
within a promotion event can have overlapping timeframes within the
event.
Promo NameName of a promotion. A promotion is an intentional grouping of
promotion offers. A promotion can only be a child of a single promotion
event. Multiple promotions within a promotion event can have
overlapping timeframes within the event.

Table 5-16 (Cont.) Promotion Dimension Attributes

AttributeDefinition
Promo DescriptionDescription of a promotion. A promotion is an intentional grouping of
promotion offers. A promotion can only be a child of a single promotion
event. Multiple promotions within a promotion event can have
overlapping timeframes within the event.
Promo Start DateThis represents the start date of a promotion. This value is determined
by the timeframes of the promotion offers within a promotion.
Promo End DateThis represents the end date of a promotion. This value is determined
by the timeframes of the promotion offers within a promotion.
Promo Offer IDUnique ID from the source system that identifies a promotion offer. A
promotion offer is an intentional grouping of promotion details within a
promotion. A promotion offer is always a child of a single promotion,
which is a child of a single promotion event. Multiple offers within a
promotion can have overlapping timeframes within the promotion.
Promo Offer NameName of a promotion offer. A promotion offer is an intentional grouping
of promotion details within a promotion. A promotion offer is always a
child of a single promotion, which is a child of a single promotion event.
Multiple offers within a promotion can have overlapping timeframes
within the promotion.
Promo Offer Start DateThis represents the start date of a promotion offer. Individual offers
may have overlapping timeframes within a promotion.
Promo Offer End DateThis represents the end date of a promotion offer. Individual offers may
have overlapping timeframes within a promotion.
Promo Offer TypePromotion offer type that is applied to a promotion offer, with values
such as 0 (simple item offer), 1 (simple transaction offer), and 2
(buy/get transaction offer). A promotion offer type is the method to
implement a price discount, reward, or credit/financing.
Coupon CodeA static number or code used to identify a set of coupons associated
with an offer. May be used to generate serialized coupon numbers that
will be issued to customers or redeemed at the point of sale.
Target NameDescribes the customer segment that is targeted for a particular
promotion. The promotion offers may only be delivered to the
customers in the specified segments.
Promo Detail IDIdentifier of a detail of a promotion offer, usually either a condition or
reward attached to the offer, but may include other details such as
rules, constraints, or limits on the offer.
Promo Detail TypeIdentifies the type of detail record associated with an offer, with values
such as “C” for condition or “R” for reward. The available types will vary
depending on the source of promotion data.
Promo Condition/Reward TypeIdentifies the type of condition or reward rule, such as Buy/Spend X or
Give Percent Off.
Promo Condition/Reward
Amount
Identifies the amount associated with a condition or reward, such as
the price change amount or percent off.
Promo Condition/Reward
Quantity
Identifies the number of units associated with the condition or reward,
such as the quantity to buy before getting the reward, or the quantity
eligible for discount.
Promo Condition/Reward UOMThe unit of measure for the condition or reward quantity.

Customer addresses and personal information will be sourced from an external customer management system or from Oracle Retail Customer Engagement (ORCE). Oracle Retail Insights will provide Source Independent Load interfaces (W_PARTY_PER_DS and W_RTL_PARTY_PER_ATTR_DS) to feed customer master data, addresses, and other customer attributes from the Oracle Retail Insights staging tables to the customer dimension. Some or all of this data could be loaded into the CRM system by Oracle Data Cloud, and then passed down from there to RI.

If detailed customer data is not available, it is also possible to seed customer numbers directly from sales transactions (if the POS system is capable of providing such identifiers). This allows for a simple form of customer analysis that uses just the unique identifiers from the point of sale to analyze your data.

Customer addresses and personal information will be sourced from an external customer management system or from Oracle Retail Customer Engagement (ORCE). Oracle Retail Insights will provide Source Independent Load interfaces (W_PARTY_PER_DS and W_RTL_PARTY_PER_ATTR_DS) to feed customer master data, addresses, and other customer attributes from the Oracle Retail Insights staging tables to the customer dimension. Some or all of this data could be loaded into the CRM system by Oracle Data Cloud, and then passed down from there to RI.

Table 5-17 lists the attributes of the Customer dimension.

Table 5-17 Customer Dimension Attributes

AttributeDefinition
Customer Individual Gender
Code
Code for an individual’s gender.
Customer Individual GenderAn individual’s gender, for example: male, female, not declared.
Customer Individual Marital
State Code
Code for an individual’s marital state (marital status).
Customer Individual Marital
State
An individual’s marital state (marital status), for example: single,
married, divorced, widowed.
Annual IncomeCustomer’s annual income.
Education Background CodeCode for the education background code of the customer.
Recency CategoryRecency category of the customer.
Customer Primary CityCustomer primary city of residence.
Customer Primary State CodeCode for customer primary state.
Customer Primary StateCustomer primary state.
Customer Primary Postal CodeCustomer primary postal code.
Customer Primary CountryCustomer primary country.
Address IDCustomer address ID.
Churn ScoreScore indicating the likelihood of customer retention.
Customer Status CodeStatus code for a customer.
Customer Status Code
Description
Status of a customer, for example: potential, first-time, regular.
Education BackgroundEducation background of a customer, for example: bachelor’s degree,
master’s degree).
Ethnicity CodeCode for the ethnicity of the customer, for example: H = Hispanic, G =
German, U = Unknown.

Table 5-17 (Cont.) Customer Dimension Attributes

AttributeDefinition
Nationality CodeCode for the nationality of the customer.
Customer TypeType of customer
NationalityNationality of the customer.
Occupation CodeCode for the occupation of the customer.
OccupationOccupation of the customer.
Prospect FlagFlag to indicate someone who has visited or shopped online, but has
not purchased. The retailer may have some information about such
prospect customers.
Recency Category CodeCode indicating how recently the customer purchased.
Recency CategoryScore indicating how recently the customer purchased.
Frequency Category CodeCode indicating how often a customer purchases.
Frequency CategoryScore indicating how often a customer purchases.
Monetary Category CodeCode indicating the monetary value of a customer’s purchase.
Monetary CategoryScore indicating the monetary value of customer’s purchase.
RFM Categories CodeCode indicating the customer’s total RFM Score.
RFM CategoriesScore indicating the combined recency, frequency, and monetary value
of a customer.
Churn Score Range SortSort range for churn score.
Churn Score RangeRange of churn score.
Customer Address Type CodeCode for the type of customer address.
Customer Address TypeType of address, for example: billing address, delivery address.
Years at AddressNumber of years for which the specific address has been in use.
Customer Address Class CodeCode indicating the class of the address.
Customer Address ClassClass of address, for example: residential address, commercial
address.
Primary Address FlagFlag that indicates if the address can be used for all customer
communication and reporting purposes.
CityIndicates the City.
State CodeState code.
StateState.
Postal CodePostal code.
CountryIndicates the Country.
Opt Out FlagFlag indicating if the address or e-mail address may or may not be
marketable.
Customer Birth MonthCustomer month of birth.
Customer Birth YearCustomer year of birth.
AgeIndicates the age of customer based on year and month of birth.
Age RangeThis demographic attribute for customer represent the range in which
his age lies. This attribute will be typically configured by user based on
their business needs.

Table 5-17 (Cont.) Customer Dimension Attributes

AttributeDefinition
Customer Income BandRange in which customer’s income falls.
Ethnicity NameEthnicity of the customer, for example: H = Hispanic, G = German, U =
Unknown.
Dwelling StatusThe dwelling status classifies all dwellings according to whether they
are occupied, unoccupied, or under construction during the time period
of the data collection.
Dwelling SizeThis attribute lists the floor area for a dwelling unit expressed in the
standard unit of measure.
Dwelling TypeThis attribute lists the dwelling unit occupied by, or intended for
occupancy by, one household. Examples include: detached house, flat,
apartment, tenement, trailer park, etc.
Dwelling TenureThe dwelling tenure attribute refers to the period of the occupancy of a
private household in a dwelling. It is expressed in number of years.
ReligionThis attribute identifies a customer’s religion.
Religion CodeThis attribute is the code for a customer’s religion.
Social ClassStatus hierarchy by which customers are classified on the basis of
esteem and prestige. Values - Upper Class, Upper Middle class, Lower
middle class, Upper lower class, lower class.
Social Class CodeCode indicating the status hierarchy by which customer are classified
on the basis of esteem and prestige.
Family LifecycleIndicates the family lifecycle of the customer, Examples include:
bachelor, married with no children (DINKS: Double Income, No Kids),
full-nest, empty-nest, or solitary survivor.
Family Lifecycle CodeCode indicating the family lifecycle of the customer.
Metro Area SizeSize of population in the metro area where the customer lives.
ActivityActivity based on AIO survey.
Activity CodeActivity code based on AIO survey.
AttitudeThis attribute indicates the customer’s attitude.
Attitude CodeCode indicating customer’s attitude.
Benefit SoughtThe main benefits the customer looks for in a product. For example,
health, taste, and so on.
Benefit Sought CodeCode based on benefits sought.
ClimateThis indicates the weather patterns for the customer’s area.
Climate CodeThe code indicates the weather patterns.
Customer Lifetime ValueThis attribute is a forecast of customer profitability.
Customer Lifetime Value CodeThis is the code for customer lifetime value.
Customer Lifetime Value
Range
This is the range in which the customer’s value falls, for example, Very
High/High/Medium/Low
Customer Profitability CodeThis is the code for customer profitability.
Customer ProfitabilityThis attribute is a historical analysis of customer profitability, for
example, High/Medium/Low.
InterestThis attribute indicates interest based on AIO survey.
Interest CodeCode indicating customer’s interests.

Table 5-17 (Cont.) Customer Dimension Attributes

AttributeDefinition
OccasionThis attribute indicates when a customer tends to purchase or
consume the product. It can be holidays and events that stimulate
purchases
Occasion CodeCode indicating when customer tends to purchase or consume the
product.
OpinionThis attribute indicates (but is not limited to) customer’s political
opinions, environmental awareness, sports, arts and cultural issues.
Opinion CodeCode indicating customer opinions.
Readiness to BuyThis attribute indicates customer buying mindset.
Readiness to Buy CodeCode indicating the customer buying mindset.
Hours WorkedThe number of hours the customer works.
Age of KidsThis attribute will contain predefined ranges for a customer. The
generic range of values will be Range - 0-3, 3-6, 6-10, 11-18, 0-16.
Population DensityPopulation density of the customer’s area. Possible values can be
urban, suburban, or rural.
No of TeensThis attribute is the number of teens in the customer’s household.
Usage RateThis indicates light, medium and heavy product usage by the customer.
Years Primary StoreThis attribute is the number of years the customer has shopped at their
primary grocery store.
Customer Active FlagFlag indicating if the customer is active.
CitizenshipThis indicates the citizenship status of the customer.
Citizenship CodeCode indicating the citizenship status of the customer.
Customer Address Effective
Date
The date a customer’s primary address is effective from.
Annual RevenueA customer’s annual revenue or net worth.
Call FlagFlag indicating if this customer can be called.
Contact Active FlagFlag indicating if this contact is active.
Contact Business NameName of the business or organization associated with this customer.
Contact Formed DateThe date that this customer’s information was first recorded.
Customer End DateThe effective end date for the customer.
Customer Since DateThe effective start date for the customer.
Customer Birth DateThe birth date of the customer.
Customer Email AddressThe primary email address of the customer.
Customer Phone NumberThe primary phone number of the customer.
Customer End DateThe effective end date for the customer.
Customer First NameThe first name or given name of a customer.
Customer Middle NameThe middle name of a customer.
Customer Last NameThe last name or surname of a customer.
Customer Name PrefixThe prefix on a customer name.
Customer Name SuffixThe suffix on a customer name.

Table 5-17 (Cont.) Customer Dimension Attributes

AttributeDefinition
Customer NicknameThe nickname of a customer.
Customer Full NameThe full name of the customer.
Customer Home LocationThe name or number of the customer’s chosen home or preferred retail
location.
Customer Signup LocationThe name or number of the location where the customer signed up or
had their data entered into the system.
Last Transaction DateThe last recorded transaction date for the customer, as registered in
source system for the customer data.
First Transaction DateThe first recorded transaction date for the customer, as registered in
source system for the customer data.
Enterprise FlagFlag indicating if this customer is an individual or an organization.
Suppress Call FlagFlag indicating if this customer should not be contacted by phone.
Suppress Email FlagFlag indicating if this customer should not be contacted by email.
Suppress Fax FlagFlag indicating if this customer should not be contacted by fax.
Suppress Mail FlagFlag indicating if this customer should not be contacted by mail.
Customer Oracle IDThe identifier assigned by Oracle Data Cloud to track the data for a
known individual across systems.
Customer Oracle Address IDThe identifier assigned by Oracle Data Cloud to track the data for a
known household across systems.

Customer Segmentation

Customer segmentation is the process of identifying and classifying customers according to their current and future value to your business. Segmentation identifies your most and least valuable customers based on how frequently and recently customers have purchased, and the monetary value and profitability of their business. You can use this information to establish programs and policies that protect your most valued customers against defecting to a competitor. In addition, segmentation assists the marketing analyst in identifying customers whose purchasing history indicates the potential to become more profitable, as well as those who contribute little value to your business.

Your best customers are those who:

  • Have purchased goods or services from you recently

  • Purchase from you frequently

  • Spend a large amount of money

Table 5-18 lists the attributes of the Customer Segment dimension.

Table 5-18 Customer Segment Dimension Attributes

AttributeDefinition
Customer Segment NameName of the customer segment.
Customer Segment TypeIndicates the type of customer segment.

Table 5-18 (Cont.) Customer Segment Dimension Attributes

AttributeDefinition
Customer Segment Age RangeThis attributes indicates the age group for customer segment. This
attribute can be used by marketers devise, and endorse items
specifically for the needs and perceptions of age groups.
Customer Segment Gender
Code
The code indicating gender of customer segment.
Customer Segment GenderThis attributes defines the gender of customer segment. Gender drives
marketing decisions for categories like clothing, hairdressing,
magazines and toiletries and cosmetics, and so on.
Customer Segment Family
Size
Indicates the Family Size for a demographics based segment.
Customer Segment Generation
Code
Generation code for creating demographic segments.
Customer Segment GenerationGeneration for creating demographic segments. Possible value can be
Baby-boomers, Generation X ans so on.
Customer Segment Annual
Income Range
The attribute defines target customer segment income range. Retailers
will use this attribute to potentially target affluent customers with luxury
goods and convenience services. Low Income range customers may
be targeted with every day value or discounted items and services.
Customer Segment
Occupation Code
Occupation code to classify customer into occupational categories.
Customer Segment
Occupation
Occupation for purposes of segmenting into occupational categories.
Customer Segment Education
Background Code
Educational background code to classify customer into different
education categories.
Customer Segment Education
Background
Educational background to classify customer into different education
categories.
Customer Segment Ethnicity
Code
The code to identify ethnic groups to find customers with special
interests.
Customer Segment EthnicityThis attribute identifies ethnic groups to find customers with special
interests.
Customer Segment Nationality
Code
Nationality code for the purpose of demographics based segmentation.
Customer Segment NationalityThis attribute identifies nationality to find customers with special
interests.
Customer Segment Religion
Code
Religious code for the purpose of demographics based segmentation.
Customer Segment ReligionThis attribute identifies religious groups to find customers with special
interests.
Customer Segment Social
Class Code
Code indicating the status hierarchy by which customer are classified
on the basis of esteem and prestige.
Customer Segment Social
Class
Status hierarchy by which customer are classified on the basis of
esteem and prestige. Values - Upper Class, Upper Middle class, Lower
middle class, Upper lower class, lower class.
Customer Segment Family
Lifecycle Code
Code indicating the family lifecycle of the segment.

Table 5-18 (Cont.) Customer Segment Dimension Attributes

AttributeDefinition
Customer Segment Family
Lifecycle
Indicates the family lifecycle of the segment, Examples include:
bachelor, married with no children (DINKS: Double Income, No Kids),
full-nest, empty-nest, or solitary survivor.
Customer Segment Region
Code
Region code for the purpose of geographic based segmentation.
Possible value can be continent, country, state, or even neighborhood.
Customer Segment RegionRegion value for the purpose of geographic based segmentation.
Possible value can be continent, country, state, or even neighborhood.
Customer Segment Metro Area
Size
Size of population for creating geographic based customer segments.
Customer Segment Population
Density
Population density for creating geographic customer segments,
Possible values can be urban, suburban, or rural.
Customer Segment Climate
Code
The code indicates the weather patterns.
Customer Segment ClimateThis indicates the weather patterns for the purpose of geographic
based segmentation.
Customer Segment Benefit
Sought Code
Benefits sought code for purposes of segmentation based on benefits
sought.
Customer Segment Benefit
Sought
The main benefits consumers look for in a product. For example,
health, taste, and so on.
Customer Segment Usage
Rate
This indicates light, medium and heavy product usage segments.
Customer Segment Readiness
To Buy Code
Code indicating the customer segment’s buying mindset.
Customer Segment Readiness
To Buy
This attribute indicates customer segment’s buying mindset.
Customer Segment Occasion
Code
Code indicating when segment tends to purchase or consume the
product.
Customer Segment OccasionThis attribute indicates when segment tends to purchase or consume
the product. It can be holidays and events that stimulate purchases
Customer Segment Activity
Code
Activity code based on AIO survey.
Customer Segment ActivityActivity based on AIO survey. This attribute can be used to create
Psychographic segments.
Customer Segment Interest
Code
Code indicating customer segment’s interests.
Customer Segment InterestIndicates interest based on AIO survey. This attribute can be used to
create Psychographic segments.
Customer Segment Opinion
Code
Code indicating customer segment’s opinions.
Customer Segment OpinionThis attribute indicates (but is not limited to) customer segments
political opinions, environmental awareness, sports, arts and cultural
issues.
Customer Segment Attitude
Code
Code indicating customer segment’s attitude.
Customer Segment AttitudeThis attribute indicates the customer segment’s attitude. This can be
used to create Psychographic segments.

Table 5-18 (Cont.) Customer Segment Dimension Attributes

AttributeDefinition
Customer Segment Value
Code
Code indicating customer segment’s value.
Customer Segment ValueThis attribute indicates the customer segment’s value. This can be
used to create Psychographic segments.
Customer Segment Source
Type
This attribute indicates whether the customer segment was based on
customers or households.

Customer Segment Allocation

The customer segment allocation folder under Customer Insights in Oracle Retail Insights enables analysis of the association of a retailer’s customer segments to its merchandise and organization hierarchies. That association enables the targeting of specific customer segments with promotions by indicating in what locations and what products a customer segment is most likely to purchase. Note that this is purely for dimensional reporting.

For example, if a merchant sees a strong association between customer segment: farmer; subclass: plows; locations: Midwest Region, she will want to ensure that she has an extended assortment of the plows subclass for that Region. That way she is driving sales as well as meeting or exceeding customer expectations.

The Customer Segment Allocation association itself is done by external systems and interfaced to Oracle Retail Insights. The association level needs to be predefined in the configuration file to determine at what level of the merchandise and organization hierarchy customer segment allocation should be tracked. For example, a retailer could configure association at subclass and store level, or department and region level, or whatever levels are appropriate for their organization. Regardless of what level is chosen during configuration, it is not recommended to drill up or down on those merchandise or organization hierarchy levels during reporting, as that will provide incorrect results.

Customer Behavior

Retail Insights exposes a set of metrics describing customer behavior, which are calculated using the Retail AI Foundation Cloud Services. These metrics are calculated using customerlinked transaction data. In addition to helping understand how customers have behaved in past, these metrics can also help predict future behavior.

Table 5-19 Customer Behavior Metrics

AttributeDefinition
Customer LatencyThe number of days between each of a customer’s transactions sales
or return.
Customer LifespanThe time between a customer’s first and last purchase.
Customer RFMThe RFM (recency, frequency, monetary) score determines
quantitatively which customers are the best ones by examining how
recently a customer has purchased (recency), how often the customer
purchases (frequency), and how much the customer spends
(monetary).
Customer Projected Next
Purchase Date
Prediction of the next likely customer purchase date.

Table 5-19 (Cont.) Customer Behavior Metrics

AttributeDefinition
Customer Location LoyaltyHow loyal are customers to a specific location? A value of 100%
indicates that they always shop at a particular location.
Customer Style LoyaltyHow loyal are customers to a particular style? A value of 100%
indicates that they always prefer one specific style.
Customer Color LoyaltyHow loyal are customers to a particular color? A value of 100%
indicates that they always prefer one specific color.
Customer Brand LoyaltyHow loyal are customers to a particular brand? A value of 100%
indicates that they always prefer one specific brand.
Customer Price Efficiency
Loyalty
How efficient are customers in getting a promotion price? A value of
100% indicates that the customer always buys items on promotions or
is very efficient in obtaining a good price.
Customer Projected Lifetime
Value
The projected total lifetime value of a customer, which is modeled by
predicting the number/value of future purchases a customer will make
and combining that with their purchase history.

Customer Loyalty Scores

Loyal customers are among the retailer’s most precious assets. A loyal customer contributes to your business on a regular basis over an extended period of time and almost always ranks as one of your best customers.

When used in conjunction with RFM analysis, these metrics allow you to assess the importance of various items to your best customers.

In Retail Insights, customer’s loyalty scores are tracked at individual customer as well as customer segment level for various grains of promotion, calendar, style, brand and merchandising hierarchy.

Loyalty score attributes indicate the likelihood of purchase of merchandise by a given customer or customer segment for the supported attributes.

Table 5-20 lists the attributes of the Customer Loyalty dimension.

Table 5-20 Customer Loyalty Score Dimension Attributes

AttributeDefinition
Seg Dept Loyalty ScoreCustomer Segment’s loyalty scores for Department, Location and Day.
This score is an indication of customer segment’s experience of
purchase of products or services.
Seg Dept Loyalty Score by
Promo
Customer segment‘s loyalty score for Department, Location and Day
by Promotion Component Type. This score is an indication of customer
segment’s experience of purchase of products or services.
Seg Class Loyalty ScoreCustomer segment‘s loyalty score for Class, Location and Day. This
score is an indication of customer segment’s experience of purchase of
products or services.
Seg Class Loyalty Score by
Promo
Customer segment‘s loyalty score for Class, Location and Day by
Promotion Component Type. This score is an indication of customer
segment’s experience of purchase of products or services.

Table 5-20 (Cont.) Customer Loyalty Score Dimension Attributes

AttributeDefinition
Seg Subclass Loyalty ScoreCustomer segment ‘s loyalty score for Subclass, Location and Day.
This score is an indication of customer segment’s experience of
purchase of products or services.
Seg Subclass Loyalty Score by
Promo
Customer segment‘s loyalty score for Subclass, Location and Day by
Promotion Component Type. This score is an indication of customer
segment’s experience of purchase of products or services.
Seg Style Brand Loyalty ScoreCustomer segment‘s loyalty score for Style, Brand, Location and Day.
This score is an indication of customer segment’s experience of
purchase of products or services.
Seg Style Brand Loyalty Score
by Promo
Customer segment‘s loyalty score for Style, Brand, Location and Day
by Promotion Component Type. This score is an indication of customer
segment’s experience of purchase of products or services.
Cust Dept Business Month
Loyalty Score
Customer’s loyalty score for Department, Location and Business
Month. This score is an indication of customer’s experience of
purchase of products or services.
Cust Dept Business Month
Loyalty Score by Promo
Customer’s loyalty score for Department, Location and Business Month
by Promotion Component Type. This score is an indication of
customer’s experience of purchase of products or services.
Cust Class Business Month
Loyalty Score
Customer’s loyalty score for Class, Location and Business Month. This
score is an indication of customer’s experience of purchase of products
or services.
Cust Class Business Month
Loyalty Score by Promo
Customer’s loyalty score for Class, Location and Business Month by
Promotion Component Type. This score is an indication of customer’s
experience of purchase of products or services.
Cust Style Business Month
Brand Loyalty Score
Customer’s loyalty score for Style, Brand, Location and Business
Month. This score is an indication of customer’s experience of
purchase of products or services.
Cust Style Business Month
Brand Loyalty Score by Promo
Customer’s loyalty score for Style, Brand, Location and Business
Month by Promotion Component Type. This score is an indication of
customer’s experience of purchase of products or services.
Cust Dept Greg Month Loyalty
Score
Customer’s loyalty score for Department, Location and Gregorian
Month. This score is an indication of customer’s experience of
purchase of products or services.
Cust Dept Greg Month Loyalty
Score by Promo
Customer’s loyalty score for Department, Location and Gregorian
Month by Promotion Component Type. This score is an indication of
customer’s experience of purchase of products or services.
Cust Class Greg Month Loyalty
Score
Customer’s loyalty score for Class, Location and Gregorian Month.
This score is an indication of customer’s experience of purchase of
products or services.
Cust Class Greg Month Loyalty
Score by Promo
Customer’s loyalty score for Class, Location and Gregorian Month by
Promotion Component Type. This score is an indication of customer’s
experience of purchase of products or services.
Cust Style Greg Month Brand
Loyalty Score
Customer’s loyalty score for Style, Brand, Location and Gregorian
Month. This score is an indication of customer’s experience of
purchase of products or services.
Cust Style Greg Month Brand
Loyalty Score by Promo
Customer’s loyalty score for Style, Brand, Location and Gregorian
Month by Promotion Component Type. This score is an indication of
customer’s experience of purchase of products or services.

Table 5-22 (Cont.) Supplier Dimension Attributes

AttributeDefinition
Supplier ParentSupplier level. For a supplier site, this value contains the parent
supplier number. Sites represent physical locations from which
suppliers ship. A null value indicates that this is a supplier.
QC FlagIndicator of whether orders from a supplier require quality control, with
values of “Y” for yes (unless overridden by the user when the order is
created) and “N” for no, indicating that no quality control is required for
this supplier unless indicated by the user during order creation. Quality
control for suppliers involves checking the quality of the merchandise
received (for example, damaged or over-ripened) and whether received
shipments contain the quantity on the receiving label.
VMI StatusStatus with which vendor-managed inventory (VMI) purchase orders
are created, with values of “A” for approved and “W” for worksheet. A
null value indicates that the supplier is not a VMI supplier. A VMI
supplier does inventory planning for the retailer. A VMI supplier is also
responsible for replenishing and reordering the retailer’s supply.
Pre Mark FlagIndicator of whether a supplier’s premarked inventory is in separate
containers for cross-dock shipping to stores, with values of “Y” for yes
and “N” for no.
EDI FlagIndicator of whether a supplier electronically sends advance shipping
notices (ASN), with values of “Y” for yes and “N” for no.
Intl Currency FlagIndicator of whether a supplier operates in the same currency as the
retailer’s primary currency, with values of “Y” for yes and “N” for no.
Currency CodeCode of the currency that a supplier uses for business transactions.
Supplier StatusIndicator of whether supplier is currently active, with values of “A” for
active and “I” for inactive.
Supplier Start DateDate the supplier record was first inserted into the data warehouse.
Supplier End DateDate the supplier was deleted from the source system.
Currency DescriptionDescription of the currency that a supplier uses for business
transactions.
Supplier Name 2Secondary name of a supplier.
Primary FlagIndicator of whether the supplier is the primary supplier for the item,
with values of “Y” for yes and “N” for no. Each item has only one
primary supplier. This field does not apply to sub-transaction-level
items.
Pack SizeNumber of items in a pack. Orders for the item must be placed in
multiples of this quantity.
In Order QtyMinimum quantity of the item that can be ordered at one time.
Max Order QtyMaximum quantity of the item that can be ordered at one time.
Lead TimeNumber of days needed between the date an order for an item is
written and the delivery from the supplier to the store or warehouse.
Pickup Lead TimeNumber of days needed between the date an item leaves a supplier
and the delivery to an initial receiving location.
Inner Pack SizeBreak pack size for an item. A break pack is a pack within a larger
container.
Supplier Trait IDUnique ID from the source system that identifies a supplier trait. A
supplier trait is an attribute of a supplier, used to group suppliers with
similar characteristics.

Table 5-22 (Cont.) Supplier Dimension Attributes

AttributeDefinition
Supplier Trait DescDescription of a supplier trait. A supplier trait is an attribute of a
supplier, used to group suppliers with similar characteristics.
Supplier Backorder IndIndicates if backorders or partial shipments will be accepted.
Supplier Default Lead TimeHolds the default lead time for the supplier. The lead time is the time
the supplier needs between receiving an order and having the order
ready to ship.
Supplier Delivery PolicyContains the delivery policy of the supplier.
Supplier Final Destination IndIndicates if the supplier can ship to final destinations as per allocation
or not.
Supplier Return Allowed IndIndicate if the supplier or supplier site accepts returns for the items
associated with them.

Retail Type

The Retail Type attribute represents the price type at which items were sold or held as inventory. There are seven values for Retail Type:

  • Regular

  • Promotional

  • Clearance

  • Employee

  • Intercompany

  • Book Transfer

  • Normal Transfer

This attribute segments a number of business measurements by price type, including sales and profit, stock position and value, markdowns, markups, transfers and competitor pricing. This information is valuable when determining a pricing strategy, analyzing inventory value, or evaluating a competitor.

It is important to note that inventory data is not held for all values of Retail Type. In RMFCS, stock on hand is considered to be in clearance or non-clearance status. In Retail Insights, nonclearance inventory is associated with the Regular value of Retail Type, while clearance inventory is associated with the Clearance value. Similarly, transfers can only be classified using one of the (I, B, N) values.

Table 5-23 describes the Retail Type attribute.

Table 5-23 Retail Type Attribute

AttributeDefinition
Retail TypePrice type of an item. Values are as follows:

R - Regular

P - Promotion

C - Clearance

E - Employee

I - Intercompany

B - Book

N - Normal
If an item is on promotion and clearance at the same time, the retail
type is “C”.

Product Season

Product season functionality allows you to categorize each item according to different seasons, and phases within seasons. For example, you can assign a season of “Spring” to a group of items, according to the supplier’s deliveries of fashion items. Those relationships can be further broken down into the phases, such as “Spring I” and “Spring II.” These item-phase-season relationships are then loaded into Retail Insights. You can query sales and inventory data, for example, based on all items in the spring season, or just items in the Spring II phase.

Note

On a given day, an item can belong to more than one season and more than one phase within a season. Seasonality is designed to group by item/location/day to avoid double-counting.

Retail Insights provides two versions of Season Phase attributes to support different business practices. The first version is called Season Phase Operational attributes. These attributes should be used when your merchandising system is managed to align buying and selling activities to fixed periods of time, such as a set of items being sold only during the Spring 2017 season. When using these attributes in reports, the start and end dates of the seasons and phases will be used to limit the data returned, similar to using calendar attributes. For example, if you want to see the net sales and profit for the Spring 2017 season, you could use the operational Season ID attribute to limit results to the effective dates of that season (without worrying about what those dates are).

The second set of attributes is called Season Phase Planning. These attributes should be used when a season or phase is used informationally, such as to describe when the item will first be received into stores, but not necessarily the window of time the item is selling for. Using these attributes will not limit reports to the start and end dates, it is more similar to using item or location attributes.

The following is the hierarchy of the Product Season dimension.

Product Season

based on census blocks in the U.S. The trade area provides a mechanism to map market area data to a specific store because the census blocks (or other method used to store market area data) do not correlate directly to the geographic area served by a store. Examples of ways to define a trade area include using traffic flow studies, a retail gravity model, a zip code method, or commuting data.

Table 5-25 Trade Area Dimension Attributes

AttributeDefinition
Trade Area NameIndicates the name of the trade area
Trade Area DescriptionThis attribute provides a description of the trade area.
Trade Area TypeThis attribute describes the type of trade area. Valid values could
include Urban, Suburban, Rural, and others.
Pull factorPull factors are ratios that estimate the proportion of local sales that
occurs in a town.
Commuter populationNumber of people who commute in this trade area.
Peak Season PopulationThe number of people in the Trade Area during peak ‘population’
season. This is common in Trade Areas with high tourist population
ebb and flow.
Tourist PopulationThe number of people that are tourists in a Trade Area.
State PopulationThe number of people in the state that the Trade Area resides.
Number of HouseholdsThe number of households within a trade area.
Average Family SizeThe average number of people within a household that reside in a
trade area.
Per Capita IncomeThe income divided by the total population of a Trade Area.
Avg Num of VehiclesAverage number of vehicles per household in this trade area.
Average Drive TimeThis attribute indicates the average time in minutes consumers must
drive from their homes to shop.

Reclassification

Reclassification occurs when any entity in a dimension changes its place in the dimension hierarchy, or when one or more attributes of an entity are changed. Reclassification affects Retail Insights reporting, whether you are using as-is, as-was, or point in time analysis. See “Analysis Methods” in Creating and Modifying Reports for more information.

Major Reclassification and Lower-Level Dimensions

A major change occurs whenever an entity changes its place in the product hierarchy (group, department, and item can be reclassified) or in the organization hierarchy (area, region, district, and location can be reclassified). This type of reclassification alters the relationship among entities in a hierarchy.

For example, a single item (white shirt) might be reclassified from the Dress to the Casual subclass.

This type of change does not alter the relationship of a subclass to any other level of the hierarchy above or below it. The record is simply updated to reflect the description change; a new surrogate key does not need to be inserted. Minor change dimension processing in Retail Insights is less complex than major change processing.

Customer Order

Oracle Retail Insights’ customer order functionality allows retailers to analyze transactions that cross multiple channels, and enables analysis of Oracle’s Commerce Anywhere capabilities. It has two dimensions: customer order demand and customer order fulfillment.

For most retailers, effective customer order management has become critical as customers no longer shop only in brick and mortar stores, but expect the ability to interact with retailers across a variety of channels. A customer order is an agreement between the retailer and the customer in which the customer pays for an item and the retailer agrees to make the item available for pickup or delivery at a later date. It consists of two parts, demand and fulfillment. Demand involves facilitating the capturing of customer orders via an e-commerce site, a mobile device, an in-store kiosk or any other similar method. The order fulfillment process, in which the customer takes possession of the product, must be properly managed across those channels to avoid jeopardizing relationships with valued customers who want a seamless experience. An order management system, such as DOO (Distributed Order Orchestration) and GOP (Global Order Promising), is used to manage the order throughout its lifecycle. When an order is initially taken, this application will determine where the order should be sourced based on customer preferences and rules related to fulfillment options set by a retailer (e.g. cost, lead times). Oracle Retail Insights provides a comprehensive set of metrics to help retailers achieve customer satisfaction. Included are key performance measurements for customer order demand and customer order fulfillment.

Oracle Retail Insights’ customer order dimension supports a number of different attributes of a customer order to allow performance analysis of retailer’s business across all channels. A complete list of these attributes and their descriptions is in the following sections. These attributes allow a user to slice and dice customer order data for analyses by order delivery information, order status, and other customer order details.

For example, if an item in an order line is sold as a substitute for another item (perhaps the original item is unavailable), then both the original item and the substitute item will be identified as such. These attributes can be used to analyze the demand for the original item the customer wanted and the alternative items that were actually ordered and delivered.

Order status is also captured so that retailers can track the order lifecycle and analyze orders based on whether they are backordered, complete, canceled, etc. to discover potential issues involved with customer satisfaction that excessive backorders or cancellations might indicate. A large amount of canceled orders, for instance, could mean there is a group of upset customers who are returning items with which they are unsatisfied or for which delivery time was too late to be acceptable.

Finally, a retailer can identify how an order was shipped, through the requested shipment type and requested shipment method attributes, which identify the carrier and the service type being used to fulfill the order. This could be used in conjunction with the order status analysis to determine if customer dissatisfaction correlates to a specific shipment type or method.

Note

When using Customer Order Promotion Transaction, Customer Order Transaction, Customer Order Status, and Customer Order Fulfillment dimensions, Salesperson and/or Cashier attributes should be used to represent an employee. Employee Name should not be used with these facts.

Table 5-26 Customer Order Demand Attributes

AttributeDefinition
CO Header Demand StatusThis attribute provides the status of the customer order header, which
could be unique to the retailer’s order management system.
Using this attribute a user can identify the status of customer order.
Some of the statuses could be “Order Initiate”, “Back-ordered”, “Partial
Picked”, “Picked”, “Partial Shipped”, “Shipped”, “Completed” and
”Cancelled”.
CO Line Demand StatusThis attribute provides the status of the customer order line, which
could be unique to the retailer’s order management system.
Sales PersonThis attribute lists the retailer’s sales person who was responsible for
the transaction and was credited with originating the sale.
CashierThis attribute lists the employee who processed the sales transaction
by receiving the tender from customer.
Customer Service
Representative
This attribute lists the employee who helped the customer with any
questions or sold them value-added services (re-packaging, gift
packing, gift cards, etc).
Origin Demand ChannelThis attribute lists the location deemed the point of origin for the
customer order.
There are several channels, such as call center, website, SMS
advertisement, store cashier, and sales person that could be
considered the Origin Demand Channel.
Submit Demand ChannelThe location deemed the generation of demand or point of submission
for the customer order.
There are several channels, such as customer service center, website,
kiosk at store, and store POS system that could be considered the
submit demand channel.
The origin demand channel and submit demand channel may or may
not be the same for a customer order.
CO Header NumberEach customer order has header information that is primarily
customer-related, pertains to the entire order, and is uniquely identified
by a Customer Order header number.
Header information also contains information about the conditions that
affect how the system processes an order, such as fulfillment type,
fulfillment method and delivery dates. Most of the remaining header
information consists of default values from the Address Book,
Customer Billing Instructions, and Customer Master, such as tax code
and area, and shipping address information.
CO Line NumberThe customer order line number is used to uniquely identify the
customer order line information, which includes detailed information
about the items on the order, such as quantities, prices, status, and
shipped quantities. It also contains the customer order header number
to identify the order to which the line belongs.

Table 5-26 (Cont.) Customer Order Demand Attributes

AttributeDefinition
Requested Shipment TypeThis attribute provides the type of requested shipment for the customer
order line.
Some shipment types could be “Direct Ship to Customer”, “Store
Pickup”, etc.
Requested Shipment MethodRequested Shipment Method is more granular information about the
Requested Shipment Type attribute. It defines the method of shipping
to the customer.
If the shipment type is “direct ship to cust” the method might be
”overnight” or “ground”.
If the shipment type is “Store Pickup” the method would refer to how
the goods were made available at the store, such as “WH-to-Store
transfer”, or “Stock from Store”, etc.
CO Line Original ItemIf an item is not available it may be replaced with a substitute item. In
that case Oracle Retail Insights stores the original item as the CO Line
Original Item attribute.
CO Line Substitute ItemIf a customer orders an item that is not available, a retailer may decide
to substitute a similar item that is available to be shipped immediately.
This attribute displays the substitute item.
CO Retail TypeThis attribute displays the price type that was recorded for the line
item. The possible values could be R-Regular, P-Promotion, and C-
Clearance.
CO Cancel ReasonThis attribute is the reason given by the customer for canceling an
order. Examples could be “Backorder Abandon,” “Late Delivery,” etc.

Table 5-27 Customer Order Fulfillment Organization Dimension Attributes

AttributeDefinition
Fulfillment Company NumberThis attribute displays the unique ID from the source system that
identifies a fulfillment company.
Fulfillment CompanyName of a fulfillment company. Fulfillment Company is the highest
attribute within the fulfillment Organization hierarchy. A fulfillment
company consists of one or more fulfillment chains.
Fulfillment Chain NumberThis attribute displays the unique ID from the source system that
identifies a fulfillment chain.
Fulfillment ChainThis attribute displays the name of a fulfillment chain. A fulfillment
chain consists of one or more areas.
Fulfillment Area NumberThis attribute displays the unique ID from the source system that
identifies a fulfillment area.
Fulfillment AreaThis attribute displays the name of a fulfillment area. A fulfillment area
consists of one or more regions.
Fulfillment Region NumberThis attribute displays the unique ID from the source system that
identifies a fulfillment region.
Fulfillment RegionThis attribute displays the name of a fulfillment region. A fulfillment
region consists of one or more districts.
Fulfillment District NumberThis attribute displays the name of the unique ID from the source
system that identifies a fulfillment district.

Table 5-27 (Cont.) Customer Order Fulfillment Organization Dimension Attributes

AttributeDefinition
Fulfillment DistrictThis attribute displays the name of a fulfillment district. A fulfillment
district consists of one or more locations.
Fulfillment Location NumberThis attribute displays the unique ID from the source system that
identifies a fulfillment location.
Fulfillment LocationThis attribute displays the lowest level within the fulfillment organization
hierarchy. It identifies a fulfillment warehouse, fulfillment store, or
partner within the fulfillment company.
Fulfillment Channel IDThe ID of channel in which a customer order is fulfilled.
Fulfillment ChannelThe channel in which a customer order is fulfilled.

Table 5-28 Customer Order Tender Attributes

AttributeDefinition
Sales Transaction NumberThis attribute displays a unique number through which the sales
transaction can be identified. The transaction number is used to add
detailed information about the item sales on the transaction, such as
quantities, prices, discounts and tender amounts.
Tender TypeThe form of payment made for a customer order sales transaction.
Examples of tender types include cash, credit card, or gift card.
Transaction TypeThis attribute differentiates cross channel liability transactions from
normal sales, return transactions, and wholesale sales and return
transactions. This is an internally generated attribute used by Oracle
Retail Insights.

Reason

The Reason dimension makes it possible to track why a particular action was taken in the areas of inventory adjustment and sales. Return reasons such as “wrong item shipped” or “defective” are tracked by Return Reason. Inventory adjustments are tracked by Inv Adjustment Reason. The Reason attributes do not form a drillable hierarchy.

Both sets of reason codes exist within the same attributes, but only the codes associated with a specific metric will display in a given analysis. For example, Reason Code and Return Amt will show the return reason codes. Reason Code and Adjustment Units will show the inventory adjustment reason codes. Status Codes will behave similarly for Unavailable Inventory and Customer Order facts.

Table 5-29 Reason Attributes

AttributeDefinition
Reason CodeTo identify the reason why a particular action had performed depending
on the subject area used (For example: Inv Adjustments, Return to
Vendor, cost change, price change etc.)
Reason DescriptionA detailed description of the reason why a particular action had
performed depending on the subject area used (For example: Inv
Adjustments, Return to Vendor, cost change, price change etc.)

Table 5-29 (Cont.) Reason Attributes

AttributeDefinition
Status CodeTo identify the status of the element depending on the subject area
used. (For example: Inv Status, Customer order status etc.)
Status DescriptionA detailed description of the status depending on the subject area
used. (For example: Inv Status, Customer order status etc.)
Status ClassThis Attribute can be used to identify the different functional areas that
status is used for. (For example: Inv Status, Customer order status
etc.)
Reason CategoryThis attribute gives the category of reason for different functionalities
(For example: Inventory Adjustment, RTV etc.)

Inventory Transfer

Inventory Transfers are stock movements between a retailer’s locations. Inventory Transfers analysis will enable retailers to improve sales and avoid out of stocks by moving stock to locations where it is most needed. Depending on the transaction codes used in creating Inventory Transfers the transfer type is captured in Retail Insights as Normal, Book and Inter Company transfer types. Retail Insights will not support Transfers functionality for Transformable items. Retail Insights holds the inventory Transfers at item, to location, from location, transfer type and day level.

Table 5-30 Inventory Transfer Attributes

AttributeDefinition
Transfer Type CodeIndicates the code for Transfer Type. This is based on the origin of the
transfer request and determines how transfer behaves.
Transfer Type DescriptionIndicates the description for Transfer Type. This is based on the origin
of the transfer request and determines how transfer behaves. Different
Transfer Types that are supported are - Normal Transfer, Book Transfer,
Inter Company.
Tsf Zone IDUnique ID from the source system that identifies a transfer zone. A
transfer zone is an intentional grouping of locations for transferring
owned inventory from one location to another. A location can belong to
only one transfer zone.
Tsf Zone DescDetailed description of a transfer zone. A transfer zone is an intentional
grouping of locations for transferring owned inventory from one location
to another. A location can belong to only one transfer zone.
Tsf Entity IDUnique ID from the source system that identifies a transfer entity. A
transfer entity is a group of locations that share legal requirements
around product management. A location can belong to only one
transfer entity, and a transfer entity can belong to multiple organization
units.
Tsf Entity DescDetailed description of a transfer entity. A transfer entity is a group of
locations that share legal requirements around product management.
A location can belong to only one transfer entity, and a transfer entity
can belong to multiple organization units.

Transfer from Organization

The Transfer from Organization dimension allows tracking of inventory transfers from a location or other organizational attribute. This permits analysis of the number of units transferred and the retail and cost value of the transfer in the organization.

Table 5-31 Transfer From Organization Attributes

AttributeDefinition
From Chain NumberChain in the company from which a transfer originates
From ChainName of the chain from where the transfer originated.
From Area NumberArea in the chain from which a transfer originates.
From AreaName of the Area under the chain from which a transfer originates.
From Region NumberRegion in the area from which a transfer originates.
From RegionName of the Region under the area from which a transfer originates.
From District NumberDistrict Number from which a transfer originates.
From DistrictName of the District under the region from which a transfer originates.
From Loc NumberWarehouse, store, or partner location number from which a transfer
originates.
From LocWarehouse, store, or partner location name from which a transfer
originates.
From Tsf Entity IDTransfer entity ID from which a transfer originates.
From Tsf Entity DescTransfer entity description from which a transfer originates.
From Tsf Zone IDTransfer Zone ID from which a transfer originates.
From Tsf Zone DescTransfer Zone description from which a transfer originates.

Transfer Status

Separately from the dimensions listed above, RI also maintains the current status of each individual transfer created in the merchandising system. This is equivalent to the RMFCS table for TSFHEAD, and captures all of the up-to-date attributes and status codes for every transfer action. Having this data in RI allows allocators and buyers to analyze transfer activity across the business and quickly identify problem areas using a variety of criteria, such as getting daily reports for cancelled or rejected transfers, transfers which have been open past a certain number of days, or transfers which have specific context types.

Table 5-32 Transfer Status Dimension Attributes

AttributeDefinition
Transfer NumberUnique number to identify the transfer within the system.
Parent Transfer NumberIdentifies the transfer at the level above the transfer and only used for
the transfer with finishing activity.
Transfer From Loc TypeContains the location type of the from location of the transfer. Valid
values: S-Store; W - Warehouse; E - External Finisher

Table 5-32 (Cont.) Transfer Status Dimension Attributes

AttributeDefinition
Transfer From LocContains the location number of the transfer from location. This field
will contain a store, warehouse or external finisher number based upon
the FROM_LOC_TYPE field.
Transfer Expected DC DateIt is the date that the transfer is expected to be shipped from a
warehouse and communicated to WMS.
Transfer Inventory TypeIndicates whether the transfer is for Available or Unavailable inventory
(not combination of both). Valid values: A - Available, U - Unavailable
Transfer TypeIdentifies the type or reason for the transfer.
Transfer StatusContains the status of the transfer. Valid value: I - Input, B - Submitted,
A - Approved, S - Shipped, C - Closed, D - Deleted (will be deleted
during batch), X - Transfer is being externally closed, P - Picked, L -
Selected.
Transfer Freight CodeDetermines the priority for this transfer. Valid values: N - Normal, E -
Expedite, H - Hold
Transfer Routing CodeIndicates the type of freight to use on the transfer.
Transfer Create IDContains the user ID of the user that created the transfer.
Transfer Approval DateContains the date the transfer was approved.
Transfer Approval IDContains the user ID of the user that approved the transfer.
Transfer Delivery DateIndicates the earliest date that the transfer can be delivered to the
store.
Transfer Close DateContains the date the transfer was closed.
Transfer External Ref NumberContains audit trail reference to external system when an external
transaction initiates master record creation in the Oracle Retail system.
Transfer Repl Approve FlagContains the indicator used to determine if the transfer should be
approved during the replenishment process. Valid values: Y, N.
Transfer CommentsContains any miscellaneous comments associated with the transfer
entered by the user.
Transfer EOW DateContains the end of week date for the exp_dc_date column. It is used
for OTB extracts for Intercompany transfers.
Transfer Mass Return NumberContains the Mass Return Transfer Number with with this transfer is
associated.
Transfer Not After DateContains the last day upon which a store can ship the requested
merchandise to the warehouse.
Transfer Context Type CodeThis field holds the reason code related to which a transfer is made.
Transfer Context Type DescThe descriptive value for the transfer context type code.
Transfer Context ValueContains the value relating to the context type, for example Promotion
Number.
Transfer Restock Cost PercentContains the percentage of cost charged by the receiving location for
re-stocking.
Transfer Franchise Order Need
Date
Contains the need date of franchise Order. This column is populated
only for Franchise Order transfers.
Transfer Delivery SlotIndicates the delivery slot that will be used for the transfer.
Transfer Franchise Order
Number
Contains the franchise order number this transfer is linked to.

Table 5-32 (Cont.) Transfer Status Dimension Attributes

AttributeDefinition
Transfer Franchise Return
Number
Contains the franchise return number this transfer is linked to.

Market Item

One of the critical components available with Oracle Retail Insights reporting is the ability for a retailer to compare its own performance to that of the market. Market Item attributes allow the retailer to make assortment, promotional and space allocation decisions within a wider context. By comparing its own trends to that of the market it is possible to identify and respond to opportunities and problems quickly and effectively.

Table 5-33 Market Item Dimension Attributes

AttributeDefinition
All StoreRepresents the highest level of Market Item hierarchy.
Market DeptIndicates the second level of Market Item hierarchy.
Market CategoryThe range of products purchased by a business organization or sold by
a retailer is broken down into discrete groups of similar or related
products; these groups are known as product categories (examples of
grocery categories might be: tinned fish, washing detergent,
toothpastes).
Market SubcategoryEach market category divides into sub-categories. A pre requisite to
defining the sub-categories is that trends behind the categories are
known. Subcategory is defined as grouping of common differentiating
characteristics within a larger category.
Market SegmentThe next level below Market subcategory. Key information about how
inventory is tracked and reported is stored at the Market Segment
level.
Market Sub-segmentThe next level below Market Segment. This is equivalent to Subclass
level of Retailer’s merchandising hierarchy.
Market Item DescriptionDescription of the item including characteristics of the market item.
Market Item BrandDisplays the brand associated with the market item. This is level 10 of
Market Item hierarchy.
Market Sub BrandA subcomponent of a brand. For example, if a brand were “Super
Cola”, the subbrand might be “Super Cola Light”.
Market Brand OwnerBrand owner for the Item.
Market Brand Owner NumberBrand owner for the Item.
Market Item FlavorIndicates the flavor of Market Item.
Market Item PatternIndicates the pattern of Market Item.
Market Item ScentIndicates the scent of Market Item.
Market Item SizeIndicates the size of market item.
Market Package TypeThe package type defines as the packaging method chosen by the
market item. After choosing the packaging type, retailer should specify
the dimensions of the item. The following types of packaging types are
available Case Pallet Each.

Table 5-33 (Cont.) Market Item Dimension Attributes

AttributeDefinition
Market Parent CompanyThe next level below Market Sub-segment. It Indicate the parent
company for the given market item hierarchy.
Vendor NameThe name of the vendor who supplies the market item.
Multi PackThe multi-pack is defined as package of several individual pack items
sold as a unit. This can be broken into multiple pack items.
Universal Product CodeTwelve-digit barcode printed or affixed on virtually everything sold in
supermarkets or retail stores, including books, magazines, candy, etc.,
for automatic checking-out at the cashier counter. UPC not only
identifies an item, it also provides real time information on quantity
sold, and inventory and ordering information.

Competitor Pricing

A competitor is a retailer with a product range and customer base similar to those for the organization business unit [Store location in RI] and its channels. The competitor entity holds information about each competitor store and associates it with a location in the organization. Competitor pricing details can be associated with a specific competitor location and mapped to an item in the product hierarchy. This structure provides the means to compare competitor prices for similar or identical items, at a direct competitor location. With this type of timely information, promotion and pricing strategies can be implemented by retailers to prevent potentially costly customer defections.

Sample questions that Competitor Pricing Analysis can help answer:

  • How do my prices compare, for specific items, against nearby competitor locations? Against average competitor prices across all competitor locations?

  • How do my prices vary for an Item at the competition, when that Item has regular price, or when it’s on promotion, or on clearance at the competitor?

One of the critical components available with Oracle Retail Insights reporting is the ability for a retailer to compare its own performance to that of the market. Market Item attributes allow the retailer to make assortment, promotional and space allocation decisions within a wider context. By comparing its own trends to that of the market it is possible to identify and respond to opportunities and problems quickly and effectively.

Buyer

The Buyer dimension stores data about buyers who are responsible for raising purchase orders. The buyer dimension is attached to the Purchase order transactions and is used to report on order quantity, received quantity, cancelled qty against purchase orders created by the given buyer.

Table 5-34 lists the attributes of the Buyer dimension.

Table 5-34 Buyer Attributes

AttributeDefinition
Buyer NameThe name of the person authorized to create purchase order.

Table 5-34 (Cont.) Buyer Attributes

AttributeDefinition
Buyer PhoneThe current telephone number of the buyer.
Buyer FaxThe current Fax number of the buyer.

Purchase Order

A Purchase order (PO) is a request issued by a Retailer to a supplier, indicating types, quantities, and agreed prices for products. Sending a purchase order to a supplier constitutes a legal offer to buy products or services.

The purchase order dimension stores key details of the purchase orders such as Supplier, Buyer, Order Type, import order indicator etc for orders that have been approved at least once are stored in the dimension.

The purchase order dimension is used with Buyer, Supplier, Item, Organization, Calendar dimensions to report on cost and quantity of ordered, cancelled, received purchase orders against a supplier/Buyer/Item/Location/Time period. The dimension can also be used with the Sales fact, if there are matching customer order numbers on both the PO header record and a sales transaction record.

Table 5-35 lists the attributes of the Purchase Order dimension.

Table 5-35 Purchase Order Attributes

AttributeDefinition
Appointment Date TimeThis column will hold the date and time of the receiving appointment at
the warehouse.
Backhaul AllowanceContains the type of backhaul allowance that will be applied to the
order. Some examples are Calculated or Flat rate
Backhaul TypeThis field contains the type of backhaul allowance that will be applied
to the order. Some examples are Calculated or Flat rate
Close DateThis contains the date when the order is closed.
Contract NumberThis contains the contract number associated with this order.
Currency CodeThis contains the currency code for the order.
Customer Order NumberThe customer order identifier associated with a purchase order,
typically used for drop shipments where the PO is placed to fulfill the
customer order.
Delivery SupplierThis field holds the supplier/supplier site from where the goods are
delivered.
Earliest Ship DateThe date before which the items on the purchase order cannot be
shipped by the supplier. Represents the earliest ship date of all the
items on the order
EDI PO IndicatorThis indicates whether or not the order will be transmitted to the
supplier via an Electronic Data Exchange transaction.
Import Country IDThe identifier of the country into which the items on the order are being
imported.

Table 5-35 (Cont.) Purchase Order Attributes

AttributeDefinition
Import Order NumberThis indicates if the purchase order is an import order.
Valid values are Y (Yes) and N (No).
Latest Ship DateThe date after which the items on the purchase order cannot be
shipped by the supplier. Represents the greatest latest ship date of all
the items on the order
Not After DateThis contains the last date on which the delivery of goods in purchase
order will be accepted.
Not Before DateThis contains the first date on which the delivery of goods in purchase
order will be accepted.
Order NumberThis is the purchase order number that uniquely identifies an order
within source system.
Order TypeIndicates the type of order and which Open To Buy bucket will be
updated. Valid values include: N/B - Non Basic ARB - Automatic
Reorder of Basic BRB - Buyer Reorder of Basic.
Original Approval DateThis contains the date that the order was originally approved.
Originated IndicatorIndicates where the order originated.
Valid values include:
0 - Current system generated (used by automatic replenishment)
2 - Manual
3- Buyer Worksheet
4 - Consignment
5 - Vendor Generated
Payment MethodIndicates how the purchase order will be paid.
Valid options are LC (Letter of Credit), WT (Wire Transfer), OA (Open
Account).
Pickup DateContains the date when the order can be picked up from the Supplier.
This field is only required if the Purchase Type of the order is Pickup.
Pickup LocationContains the location at which the order will be picked up, if the order is
a Pickup order.
Pickup NumberThis contains the reference number of the Pickup order.
PO TypeThis contains the value associated with the PO_TYPE for the order.
Purchase TypeIndicates what’s included in the suppliers cost of the item. Valid values
include C (Cost), CI (Cost and Insurance), CIF (Cost, Insurance and
Freight), FOB (Free on Board).
QC IndicatorThis indicator determines whether or not quality control checking is
required when items for this order are received. Valid values are Y and
N.
Reject CodeThis contains a code for the reason why the order was rejected during
the automatic replenishment approval process.
Valid values include: VM (Vendor minimum not met), NC (Negative
cost calculated on an item), UOM (UOM convert error due to
incomplete data).

Table 5-35 (Cont.) Purchase Order Attributes

AttributeDefinition
Ship MethodThe method used to ship the items on the purchase order from the
country of origin to the country of import.
Valid values include 10 (Vessel, Non container), 11 (Vessel,
Container), 12 (Border Water-borne (Only Mexico and Canada)), 20
(Rail, Non-container), 21 (Rail, Container), 30 (Truck, Non container),
31 (Truck, Container), 32 (Auto), 33 (Pedestrian), 34 (Road, Other,
includes foot and animal borne), 40 (Air, Non-container), 41 (Air,
Container), 50 (Mail), 60 (Passenger, Hand carried), 70 (Fixed
Transportation Installation), 80 (Not used at this time).
Ship Pay MethodCode indicating the payment terms for freight charges associated with
the order.
Valid values include: CC - Collect, CF - Collect Freight Credited Back
to Customer, DF - Defined by Buyer and Seller, MX - Mixed, PC -
Prepaid but Charged to Customer, PO - Prepaid Only,
PP - Prepaid by Seller
Split Reference Order NumberThis column will store the original order number from which the split
orders were generated from. It will be for references purposes only.
The purpose is to allow users a means of grouping orders that were
split from an original super order. The original order, once split, will
however be removed from the system.
StatusIndicates the status of the purchase order. Dimension only holds POs
with the following status:
A - Approved
C - Cancelled
Vendor Order NumberThis contains the vendor’s unique identifying number for an order.
These orders may have originated by the vendor through the EDI
process or this number can be associated to an Oracle Retail order
when the order is created on-line.
Revision DateThe date that an existing purchase order was revised. A revision could
include major changes such as a cancellation of ordered units, or a
minor change such as a modification to the unit cost amount.

Allocation

An allocation helps allocate merchandise against each store or warehouse after determining the inventory requirements for the given item, location, and week using real time inventory information. An allocation can either be done in advance of the order’s arrival or at the last minute to leverage real-time sales and inventory information. Pre-distribution of product quantities on a purchase order can be done to support faster delivery of goods from a warehouse location to stores. This is tracked via allocations against a given purchase order. Multiple allocations can be raised against a given PO that help distribute the ordered quantity among the stores sourcing from the warehouse.

The Allocation dimension holds details of a given allocation such as the order number against which the allocation was done, the status etc. The Allocation dimension is linked to the Purchase order dimension to report allocations and the allocated quantities against a purchase order.

Table 5-36 lists the attributes of the Allocation dimension.

Table 5-36 Allocation Attributes

AttributeDefinition
Alloc NumberContains the unique identifier for the allocation
Order NumberThe purchase order number against which the allocation has been
raised. This is a common attribute between the Purchase Order Dim
and the Allocation Dim.
StatusStatus of the allocation.
Valid Values:
‘R’ = Reserved
’A’ = Approved
’C’ = Closed
PO TypeThe PO_Type of the order associated with the allocation
Alloc MethodContains the preferred allocation method, which is used to distribute
goods when the stock received at a warehouse cannot immediately fill
all requested allocations to stores.
Valid values for this field are:
A - Allocation quantity based
P - Prorate method
C - Custom
Release DateContains the date on which the allocation should be released from the
warehouse for delivery to the store locations.
DOCThe ASN or BOL number for an ASN or BOL sourced allocation.
DOC TypeThe source of the Allocation.
Valid Values: PO, TSF, ALLOC, ASN, BOL

Tender Type

The tender type dimension holds the various tender types that may be utilized during sales transactions.

Table 5-37 Tender Type Dimension Attributes

AttributeDefinition
Tender TypeRepresents the tender type code.
Tender Type GroupRepresents the tender type group to which the tender type ID belongs
to.
Tender Card NumberRepresents the identifier of a gift card or voucher that was purchased
(such as for gift card sales) or used as tender (such as gift card
redemption). Does not include other tender types such as credit cards.

Coupon

A coupon is a voucher entitling the holder to a discount for a particular product.

Coupons are important vehicles for targeted offers and for driving sales of a desired category. An analysis of coupon use can help retailers understand if the cost of producing and distributing coupons is worthwhile.

Table 5-38 Coupon Dimension Attributes

AttributeDefinition
Coupon DescriptionContains the description of the coupon associated with the coupon
number.
Coupon Reference NumberHolds the coupon barcode - only an EAN13 or free text can be
entered.
Coupon Maximum Discount
Amt
Contains the Maximum Discount value that can be gained from the
coupon.
Coupon AmtContains the percent or dollar value of the coupon.
Percent IndSpecifies whether the coupon amount is a percent or a dollar value.
PromotionHolds the promotion ID. Any open promotion can be selected to be
associated with coupons
Promotion Component IDPromotion Component ID field required for RPM. Will be required if a
promotion has been selected.
Transaction Level IndIndicates if this is a transaction level coupon.
Coupon Effective DateThe effective from-date of the coupon.
Coupon Expiration DateThe date the coupon expires.

Transaction Code

The Transaction Code attribute represents the codes used in merchandising systems to differentiate different types of transactions which occur during daily operations. In Retail Insights, these codes are also used to separate Inventory Receipts based on their associated transaction type.

There are three values for Transaction Code which are used in conjunction with Inventory Receipts:

  • Purchases (20)

  • Allocation Transfer Receipts (44~A)

  • Transfer Receipts (44~T)

Table 5-39 Transaction Code Dimension Attributes

AttributeDefinition
Transaction CodeCode which describes the transaction type that generated the
inventory receipts.
Transaction DescriptionDescription of the transaction type that generated the inventory
receipts.

Customer Loyalty Program

Loyalty Programs define the rules used for tracking the purchases of Customers belonging to location loyalty programs, usually through a system of “points”. These points can then be redeemed for discounts of a fixed amount (though the points alone have no intrinsic value). The discounts can be distributed through the mail as paper coupons, or made available to

customers as an E-Award coupon or Entitlement coupon associated with an Award Program. Loyalty program data can be extracted from Oracle Retail Customer Engagement.

Table 5-40 Loyalty Program Dimension Attributes

AttributeDefinition
Loyalty Program NumberThe number associated with the customer loyalty program.
Loyalty Program DescriptionThe name of the customer loyalty program.
Loyalty Points DescriptionThe name of the points used in a point-based loyalty program.
Loyalty Points Currency ValueThe currency amount required to earn a point in a point-based loyalty
program.
Loyalty Program Active FlagA flag indicating if a loyalty program is currently active.
Loyalty Program Start DateThe effective start date for the loyalty program.
Loyalty Program End DateThe effective end date for the loyalty program.
Loyalty Program Level NumberThe number associated with a level in a customer loyalty program.
Loyalty Program Level
Description
The name of a level in a customer loyalty program.
Loyalty Program Level Active
Flag
A flag indicating if a loyalty program level is currently active.
Loyalty Program Level Default
Flag
A flag indicating if a loyalty program level is the default level a member
of the program will start at.
Loyalty Program CurrencyThe primary currency used for the loyalty program.

Customer Loyalty Account

Loyalty Accounts are used to assign customers to one or more Loyalty Programs. A loyalty account may contain details about the customer’s use of the program, such as their points balance, program level, and account open and expiration dates. A customer must have a loyalty account in order to take advantage of the benefits of a loyalty program. Loyalty account data can be extracted from Oracle Retail Customer Engagement.

Table 5-41 Loyalty Account Dimension Attributes

AttributeDefinition
Loyalty Account NumberThe number associated with the customer loyalty account.
Loyalty Account Card Serial
Number
The sixteen-digit number embossed on a loyalty account card.
Loyalty Account From DateThe date that a loyalty account became active at a loyalty program
level.
Loyalty Account To DateThe date that a loyalty account was no longer active at a loyalty
program level.
Loyalty Account Active FlagA flag indicating if the loyalty account is active in the source system.
Loyalty Account Expiry FlagA flag indicating if the loyalty account has expired, such as due to
inactivity or account closure.
Loyalty Account Points BalanceThe number of points available on a loyalty account.
Loyalty Account Escrow
Balance
The number of points in escrow to a loyalty account.

Table 5-41 (Cont.) Loyalty Account Dimension Attributes

AttributeDefinition
Last Award Processed DateThe last time an award was processed against a loyalty account.
Last Accrual DateThe last time points were accrued against a loyalty account.
Last Program Level Change
Date
The last time the loyalty account moved to a different program level.
Last Transaction DateThe last time a transaction was recorded against the primary customer
on a loyalty account

Stock Counts

A stock count (or cycle count) is an inventory auditing procedure, which falls under inventory management, where a subset of inventory, in a specific location, is counted on a specified day. Stock counts may be performed once or multiple times per fiscal year, and different locations may undergo a count at different times. The primary purpose of stock counting is to capture an accurate count of all stock on hand and compare it to the inventory management system’s records for inaccuracies and losses. Major differences between the stock count and inventory records would be a cause for concern and require further investigation by the retailer, as these differences could be due to theft or poor inventory management practices by the store.

Reporting on stock counts involves collecting sales and inventory data for the range of dates between the prior count and the current one. This information can be compared to the manual counts and metrics like shrinkage can be calculated at various levels of the merchandise or organization hierarchies. Due to the dynamic nature of stock counts (in terms of when they occur and which locations have undergone them at any point in time), aggregating the sales and inventory data is not as simple as rolling up to a specific fiscal period. The reporting system will need to understand the stock count dates that occur at each retail location, and return aggregate data which is rolled up from each store’s individual date ranges.

RI provides a Stock Count dimension for capturing and reporting on stock count activities as well as two Stock Count facts covered in the next chapter. The dimension consists of a list of locations associated with a stock count, as well as the window of time to analyze historical data for the count. The data for this dimension needs to be provided to RI by the retailer from an inventory system such as SIM that manages the stock count activities.

Only when the dimension is provided daily can the stock count facts be populated with data.

Note

When reporting on factual data, such as sales and inventory for a stock count activity, the following OAS filter can be used to limit the results to the stock count period:

“Business Calendar”.”Fiscal Date” between “Stock Count”.”Stock Count From Date” and “Stock Count”.”Stock Count To Date”

This filter can be added by creating a new filter, selecting the box for “Convert this filter to SQL” in the popup, and clicking OK. Copy the text above into the text box that appears. Then click OK again.

Table 5-42 Stock Count Dimension Attributes

AttributeDefinition
Stock Count IDNumber which uniquely identifies the stock or cycle count in the source
system.
Stock Count DescDescription of the cycle or stock count. This value can be used to
group together stock count activities across multiple locations for
reporting purposes.
Stock Count TypeIndicates the type of stock count, such as B (both unit and amount) or
U (unit only).
Stock Count StatusIndicates the status of a stock count, such as whether it is scheduled
but not yet executed, or already finalized and approved.
Stock Count Start DateContains the starting date from which data should be included for the
current stock or cycle count, such as the day after the prior count
occurred.
Stock Count End DateContains the date on which the stock or cycle count event will take
place.

Discount Type

Discount types are codes defined in the point of sale system to classify a price change applied to a sale, such as manufacturer coupons, employee discounts, or manager price overrides. Discount types would be populated in the sales audit system in order to capture which discounts have been applied to a transaction, which is then loaded to RI along with the Sales Discount fact.

Table 5-43 Discount Type Dimension Attributes

AttributeDefinition
Discount Type CodeNumber which uniquely identifies the discount code in the point of sale
and auditing systems.
Discount DescriptionDescription of the discount code, such as Employee Discount.

Selling Organization

It is possible for return transactions to be tagged with the original selling location and original transaction ID associated with the sale of the returned item. This information can be passed from the point of sale system, and then RI will link the selling location to the organization hierarchy for reporting. This functionality enables detailed returns analysis following the sale and return of an item, such as identifying items which are bought online and returned in store.

Table 5-44 Selling Organization Dimension Attributes

AttributeDefinition
Selling Company NumberThis attribute displays the unique ID from the source system that
identifies original selling company.
Selling CompanyName of the original selling company.

Table 5-44 (Cont.) Selling Organization Dimension Attributes

AttributeDefinition
Selling Chain NumberThis attribute displays the unique ID from the source system that
identifies original selling chain.
Selling ChainThis attribute displays the name of original selling chain.
Selling Area NumberThis attribute displays the unique ID from the source system that
identifies original selling area.
Selling AreaThis attribute displays the name of original selling area.
Selling Region NumberThis attribute displays the unique ID from the source system that
identifies original selling region.
Selling RegionThis attribute displays the name of original selling region.
Selling District NumberThis attribute displays the name of the unique ID from the source
system that identifies original selling district.
Selling DistrictThis attribute displays the name of original selling district.
Selling LocNumberThis attribute displays the unique ID from the source system that
identifies original selling location.
Selling LocThis attribute displays the name of the original selling location.
Selling Channel IdThis attribute displays the unique ID from the source system that
identifies original selling channel.
Selling ChannelThis attribute displays the name of the original selling channel.

Clearances

Clearance events which are managed through a pricing solution such as RPM will be loaded into RI for detailed clearance reporting. The clearance events will be captured for the items and locations included in the event, for the range of effective dates the clearance is active for. An item-location may only be under the effects of a single clearance event at a time, but may undergo multiple clearances across the entire item lifecycle. RI will automatically manage the effective dates and eligibility of items on clearance as new clearance events are generated in the source system.

Retail Insights will maintain the full history of clearance events applied to items, allowing for indepth analysis of sales, inventory, and similar facts grouped by individual clearances, or aggregated by the clearance groups or markdown numbers associated with multiple events. Some facts are not supported with the Clearances dimension as the fact data would not typically be used at this level, such as Base/Net Supplier Costs, Customer Orders, Purchase Orders, and Sales Promotions. Certain combinations of dimensions would also prevent Clearance analysis, such as looking at Transfers based on the From/To Locations where you could be transferring between clearance and non-clearance locations.

Table 5-45 Clearances Dimension Attributes

AttributeDefinition
Clearance IDThe display ID of a clearance event
Clearance Group IDThe group ID of a clearance event.
Clearance Group DescThe description of a clearance group assigned to a clearance.

Table 5-45 (Cont.) Clearances Dimension Attributes

AttributeDefinition
Clearance Markdown IDThe unique identifier of the markdown number assigned to a clearance
event.
Clearance Markdown NumberThe markdown number assigned to a clearance event, generally
designating the sequence of the event across multiple clearances
(such as first, second, final).
Clearance OOS DateContains the date when the item/location on clearance is expected to
be out of stock. Does not mean the item will actually become out of
stock on this date.
Clearance ReasonThe user-provided reason for initiating the clearance event.
Clearance Change TypeThe type of price change being applied, such as Amount Off, Percent
Off, Fixed Price, or Exclude.
Clearance Change AmtThe amount of a price change or fixed price override on a clearance
event. This value shows the item price after the change has been
applied.
Clearance Change UOMThe unit of measurement for the price change on a clearance event.
Clearance Change CurrencyThe currency code for the price change on a clearance event.

Custom Flex Attributes

The custom flex attribute solution (CFAS) for RMFCS is a metadata driven framework that enables you to set up additional attributes on the pre-enabled RMFCS entities without having to change the existing screens or make any changes in the application code. Retail Insights has the ability to consume certain sets of commonly used CFAS attributes created using the out-of-box RMFCS framework, including Item, Location, and Item-Location attributes. RI currently supports the standard configuration of these tables using a single group-set per dimension.

Each CFAS interface is loaded from RMFCS as an extension of the associated dimension in RI. RI currently supports the following interfaces.

  • Item attributes are loaded from the RMFCS table ITEM_MASTER_CFA_EXT and are exposed in OAS as a new set of Item dimension attributes.

  • Location attributes are loaded from a combination of STORE/WH/PARTNER CFA tables and are exposed in OAS as a new set of Organization dimension attributes.

  • Item-Location attributes are loaded from the ITEM_LOC_CFA_EXT table and are exposed in OAS as a new set of Product Org attributes.

  • Supplier attributes are loaded from RMFCS table SUPS_CFA_EXT table and are exposed in OAS as a new set of Supplier attributes.

  • Merchandise hierarchy attributes are loaded from a combination of DEPS/CLASS/ SUBCLASS CFA tables in RMFCS and are exposed in OAS as a set of Item dimension attributes.

The RI attribute names for CFAS attributes are intentionally generic, and it is expected that the retailer will relabel them during implementation of RI. The naming scheme follows a standard pattern of Flex Attr . For example, Item attributes will have names such as Item Flex Attr 22 Date or Item Flex Attr 11 Number. These should be relabeled to show names that will be meaningful to RI users when building reports. Once they have been

loaded and labeled appropriately, the attributes should function in the same manner as any other RMFCS-sourced attribute.

Deals

A deal is a set of one or more agreements that take place between the retailer and a vendor. A vendor can be a supplier, wholesaler, distributor or manufacturer, and from the vendor, the retailer is entitled to receive discounts or rebates for goods that are either purchased or sold. A deal consists of a set of discounts and/or rebates that are negotiated with the vendor and share a common start date. Retail Insights includes a standalone Deals dimension with attributes that define the deal details. The deal ID is the primary key for the dimension and a deal will have only one row in the data. When new data comes to the system for an existing deal, the attribute values are updated to reflect the latest data. History is not retained for old versions of deal data. Deal attributes may be used with the Deal Income fact for reporting.

Table 5-46 Deals Dimension Attributes

AttributeDefinition
Deal Active DateDate the deal will become active. This date will determine when
deal components begin to be factored into item costs.
Deal Actual Earned TDThe total monies earned for the deal to date.
Deal Add Reporting DaysThis column will give the number of extra reporting days that
should be added to the Deal_actuals_forecast table to cater to the
late postings of the transactions after the deal close date.
Deal Apply TimingIndicates when the deal component should be applied - at PO
approval or time of receiving. Valid values are O for PO approval,
R for receiving.
Deal Approval DateDate the deal was approved.
Deal Bill Back MethodThis will determine the bill back method. It will be required for
bill back deals only. Valid values are Credit note or Debit note.
Deal Bill Back PeriodCode that identifes the bill-back period for the deal component.
This feld will only be populated for billing types of BB. Valid
values are W for week, M for month or Q for Quarter and A for
Annual.
Deal Billing Partner IDThis indicates the partner that will included on the invoice
information.
Deal Billing Partner TypeType of the partner the deal applies to. Valid values are S1 for
supplier hierarchy level 1 (manufacturer), S2 for supplier
hierarchy level 2 (distributor) and S3 for supplier hierarchy level
3 (wholesaler).
Deal Billing Supplier IDThis indicates the supplier that will included on the invoice
information.
Deal Billing TypeBilling type of the deal component. Valid values are OI for off-
invoice and BB for bill-back.
Deal Close DateDate the deal will/did end. This date determines when deal
components are no longer factored into item costs. It is optional
for annual deals, required for promotional deals. It will be left
null for PO-specifc deals.
Deal CommentsFree-form comments entered with the deal.

Table 5-46 (Cont.) Deals Dimension Attributes

AttributeDefinition
Deal Comp TypeType of the deal component, user-defned and confgurable. In the
case of multiple components, will only get one of the values for
this record.
Deal Comp Type DescDescription of the deal component. In the case of multiple
components, will only get one of the values for this record.
Deal Create DateDate of when the record was created. This value should only be
populated once on insert, it should never be updated in the
source.
Deal CurrencyCurrency code of the deals currency. All costs on the deal will be
held in this currency.
Deal External Ref NoAny given external reference number associated with the deal.
Deal Growth Rate TDThe budget growth rate percentage for the deal to date.
Deal Hist Comp End DateThe last date of the historical period against which growth will be
measured in this growth rebate.
Deal Hist Comp Start DateThe frst date of the historical period against which growth will be
measured in this growth rebate.
Deal Income MethodThis will determine how the income will be calculated. Valid
values are Actuals earned to date or Pro-rated using forecast.
Deal Invoice LogicThis will determine if the credit notes or debit notes created
should be created manually or require manual intervention and
also if negative amounts should be included. Valid values are AA
for Automatic All values, MA for Manual All Values, AP Automatic
Positive values only, MA Manual Positive values only, NO - no
invoice processing.
Deal Last Invoice DateThis is the last time an invoice was raised for the deal.
Deal Next Invoice DateThis is the estimated next invoice date for the deal.
Deal NumberUnique deal number, generated from a sequence.
Deal Order NumberOrder the deal applies to, if the deal is PO-specifc.
Deal Pack Level FlagUsed to indicate whether the packs are to be tracked at pack level
or not.
Deal Partner DescName of the partner assigned to this deal.
Deal Partner IDLevel of supplier hierarchy (such as manufacturer, distributor or
wholesaler) set up as a partner, used for assigning rebates by a
level other than supplier.
Deal Partner TypeType of the partner the deal applies to. Valid values are S1 for
supplier hierarchy level 1 (manufacturer), S2 for supplier
hierarchy level 2 (distributor) and S3 for supplier hierarchy level
3 (wholesaler).
Deal Rebate Calc TypeIndicates if the rebate should be calculated using linear or scalar
calculation methods. Valid values are L for linear or S for scalar.
Deal Rebate FlagIndicates if the deal component is a rebate. Deal components can
only be rebates for bill-back billing types. Valid values are Y for
yes or N for no.
Deal Rebate Growth FlagIndicates if the rebate is a growth rebate, meaning it is calculated
and applied based on an increase in purchases or sales over a
specifed period of time. Valid values are Y for yes or N for no.

Table 5-46 (Cont.) Deals Dimension Attributes

AttributeDefinition
Deal Rebate Income TypeIndicates if the rebate should be applied to purchases or sales.
Valid values are P for purchases or S for sales. It will be required
if the rebate indicator is Y.
Deal Recalc Orders FlagIndicates if approved orders should be recalculated based on this
deal once the deal is approved. Valid values are Y for yes or N for
no.
Deal Reject DateDate the deal was rejected.
Deal Reporting LevelThis will determine periods shown in the deal income screen and
the frequency of the deal income accrual reporting. Valid values
are W for week, M for month or Q for Quarter.
Deal StatusCode for the status of the deal. Valid values are A for approved, R
for rejected and C for closed. Unapproved deals will not be
extracted from the source.
Deal Stock Ledger FlagIndicates if the deal income accrual will also be written to the
RMS stock ledger. Valid values are Y for yes or N for no.
Deal Supplier DescName of the supplier assigned to this deal.
Deal Supplier NumDeal supplier’s number. This supplier can be at any level of
supplier hierarchy.
Deal Threshold TypeIdentifes whether thresholds will be set up as qty values,
currency amount values or percentages (growth rebates only).
Valid values are Q for qty, A for currency amount or P for
percentage.

Non-Merchandise Codes

Non-Merchandise Codes are reference numbers used to categorize types of expenses and allowances linked with the receipt of purchase orders. They typically represent additional costs that are not associated with the cost of the merchandise itself, but need to be tracked in the merchandising system as they do impact the total cost of ownership for the item. This may include freight fees, import fees, shipping costs, or other fees and discounts from the supplier that are linked to the individual purchase order. The non-merchandise codes are also used as a way to summarize and post the added costs to the general ledger for cost and margin calculations. Retail Insights uses the codes as a dimension specifically for reporting on the Inventory Receipt Expenses fact.

Table 5-47 Non-Merchandise Codes Dimension Attributes

AttributeDefinition
Non Merch CodeCode identifying a non-merchandise cost that can be added to an
invoice and used in the general ledger.
Non Merch DescContains the description the non-merchandise code.

Lifecycle Pricing Optimization

If you own the Oracle Retail Lifecycle Pricing Optimization (LPO) solution then you will have the ability to report on some of the results of that application directly in Retail Insights. Retail Insights exposes the optimization run attributes and included product hierarchy nodes as

dimensions and attributes. It also includes the run input and output metrics and calculations as fact measures. You may report on these fact measures by Optimization Run and Run Products, but you can also join the data with the Business Calendar and Clusters dimensions to see the metrics by price zone and fiscal week.

Table 5-48 Price Optimization Run Dimension Attributes

AttributeDefinition
LPO Processing Week IDInternal calendar identifer that corresponds to the last actual
week data was loaded for price optimization purposes.
LPO Run IDUnique identifer for the Price Optimization run.
LPO Run NameName assigned to identify the Price Optimization run.
LPO Run DescDescription assigned to identify the Price Optimization run.
LPO Run Status IDStatus ID of the Price Optimization run.
LPO Run StatusStatus of the Price Optimization run, such as Ready for Review or
Approved.
LPO Last Execution DateThe last time the Price Optimization run was executed.
LPO Batch Run FlagIndicates if the Price Optimization run was triggered from a
batch.
LPO Finalized FlagIndicates if the Price Optimization run has been fnalized.

Table 5-49 Price Optimization Product Dimension Attributes

AttributeDefinition
LPO Product Rec Lvl IDIdentifer for the recommendation level of the LPO product
hierarchy
LPO Product Rec Lvl NameName for the recommendation level of the LPO product hierarchy
LPO Product Lvl 1 IDIdentifer for the top level of the LPO product hierarchy
LPO Product Lvl 1 NameName for the top level of the LPO product hierarchy
LPO Product Lvl 2 IDIdentifer for level 2 of the LPO product hierarchy
LPO Product Lvl 2 NameName for level 2 of the LPO product hierarchy
LPO Product Lvl 3 IDIdentifer for level 3 of the LPO product hierarchy
LPO Product Lvl 3 NameName for level 3 of the LPO product hierarchy
LPO Product Lvl 4 IDIdentifer for level 4 of the LPO product hierarchy
LPO Product Lvl 4 NameName for level 4 of the LPO product hierarchy
LPO Product Lvl 5 IDIdentifer for level 5 of the LPO product hierarchy
LPO Product Lvl 5 NameName for level 5 of the LPO product hierarchy
LPO Product Lvl 6 IDIdentifer for level 6 of the LPO product hierarchy
LPO Product Lvl 6 NameName for level 6 of the LPO product hierarchy
LPO Product Lvl 7 IDIdentifer for level 7 of the LPO product hierarchy
LPO Product Lvl 7 NameName for level 7 of the LPO product hierarchy
LPO Product Lvl 8 IDIdentifer for level 8 of the LPO product hierarchy
LPO Product Lvl 8 NameName for level 8 of the LPO product hierarchy
LPO Product Lvl 9 IDIdentifer for level 9 of the LPO product hierarchy
LPO Product Lvl 9 NameName for level 9 of the LPO product hierarchy

Inventory Planning Optimization

If you own the Oracle Retail Inventory Planning Optimization (IPO) solution then you will have the ability to report on some of the results of that application directly in Retail Insights. Retail Insights exposes the replenishment optimization run attributes, enabling filtered views of other RI facts to show only those item/locations that got IPO results.

Table 5-50 Inventory Replenishment Status Dimension Attributes

AttributeDefinition
IPO Current Run Header IDMost recent inventory optimization run header ID for an item/location.
IPO Current Calculation DateMost recent date when the inventory optimization process updated the
replenishment results for an item/location.
IPO Current Optimized FlagIndicates whether an item/location was processed by an inventory
optimization run.
IPO Current Exportable FlagIndicates whether an item/location is eligible for export to
Merchandising Foundation Cloud Service, based on the most recent
optimization run that included it.
IPO Current Exported FlagIndicates whether an item/location has been exported to
Merchandising Foundation Cloud Service, based on the most recent
optimization run that included it.

Assortment Groups

The Assortment Group dimension defines the combinations of merchandise, stores, and selling periods that make up a specific product assortment. These groups can be integrated directly from the output of the Assortment Planning (AP) application or loaded manually into the input interface. A single assortment group is defined as a level of the merchandise hierarchy (for example, Womenswear Department) combined with a store cluster (for example, Northeast Stores) and a selling period (FY2025 Feb through FY2025 July). Retail Insights will take this information and spread it down to the item/location/week level of detail, and then join it with specific fact data. Assortment groups can currently be used only with Sales and Sales Optimization facts. You may use them to compare and analyze the differences between your historical sales in the data warehouse and the optimized sales produced by AI Foundation, or to aggregate your sales history to the Assortment Group level for summary reporting.

Table 5-51 Assortment Group Dimension Attributes

AttributeDefinition
Assortment Group ClusterUnique identifier for a specific assortment group and store cluster
combination.
Assortment GroupIdentifier representing a set of products grouped together for a period
of time to plan them as a single assortment.
Assortment PeriodIdentifier representing a distinct period of time (such as three months)
that will be used in assortment planning.
Assortment Period DescDescriptive label for a period of time (such as three months) that will
be used in assortment planning.
Assortment ClusterIdentifier for a group of stores that will be planned together during
assortment planning.
Assortment Cluster DescDescriptive label for a group of stores that will be planned together
during assortment planning.

Table 5-51 (Cont.) Assortment Group Dimension Attributes

AttributeDefinition
Assortment Start DateThe start date of the assortment period assigned to an assortment
group.
Assortment End DateThe end date of the assortment period assigned to an assortment
group.

Retail Insights Attribute Metadata

The following chart provides information about Retail Insights attribute metadata. Users please be aware that you cannot mix facts across as-is and as-was subject areas.

Table 5-52 Retail Insights Attribute Metadata

AttributesAs-IsAs-Was
Business CalendarXX
EmployeeXX
ClusterXX
Consumer GroupXX
Consumer Household GroupXX
OrganizationXX
Stockholding FranchiseXX
Non-Stockholding FranchiseXX
ProductXX
PromotionXX
CustomerXX
Customer BehaviorX
Customer SegmentXX
Customer Segment AllocationXX
HouseholdXX
Customer Segment LoyaltyX
SupplierXX
Retail TypeXX
Season PhaseXX
Season Phase PlanningXX
Trade AreaX
Market ItemX
BuyerXX
Purchase OrderXX
AllocationXX
Tender TypeXX
CouponXX

Table 5-52 (Cont.) Retail Insights Attribute Metadata

AttributesAs-IsAs-Was
Competitor PricingXX
Customer OrderXX
Customer Order Origin ChannelXX
Customer Order Submit ChannelXX
Customer Order Tender TypeXX
Fulfillment OrganizationXX
Gregorian CalendarXX
Customer Order FulfillmentXX
Customer Order StatusXX
ReasonXX
Shipment MethodXX
Shipment TypeXX
Tender TypeXX
Time of the dayXX
Return to VendorXX
Inventory AdjustmentsXX
Inventory TransfersXX
Transaction CodeXX
Customer Loyalty ProgramXX
Customer Loyalty AccountXX
Stock CountXX
Discount TypeXX
Selling OrganizationXX
ClearancesXX
Purchase TypeXX
DealsXX
Non-Merchandise CodesXX
Price Optimization RunX
Price Optimization ProductX
Inventory Replenishment StatusX
Assortment GroupsX

In this guide