WIXLIB

Improved Process for Oracle Retail Documentation CorrectionsTo more quickly address critical corrections to Oracle Retail documentation content,Oracle Retail documentation may be republished whenever a critical correction isneeded. For critical corrections, the republication of an Oracle Retail document may attimes not be attached to a numbered software release; instead, the Oracle Retaildocument will simply be replaced on the Oracle Technology Network Web site, or, inthe case of Data Models, to the applicable My Oracle Support Documentationcontainer where they reside.This process will prevent delays in making critical corrections available to customers.For the customer, it means that before you begin installation, you must verify that youhave the most recent version of the Oracle Retail documentation set. Oracle Retaildocumentation is available on the Oracle Technology Network at the following n/oracle-retail-100266.htmlAn updated version of the applicable Oracle Retail document is indicated by Oraclepart number, as well as print date (month and year). An updated version uses thesame part number, with a higher-numbered suffix. For example, part numberE123456-02 is an updated version of a document with part number E123456-01.If a more recent version of a document is available, that version supersedes allprevious versions.Oracle Retail Documentation on the Oracle Technology NetworkOracle Retail product documentation is available on the following web on/oracle-retail-100266.html(Data Model documents are not available through Oracle Technology Network. Youcan obtain these documents through My Oracle Support.)ConventionsThe following text conventions are used in this document:xConventionMeaningboldfaceBoldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.italicItalic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.monospaceMonospace type indicates commands within a paragraph, URLs, codein examples, text that appears on the screen, or text that you enter.

1Overview1Oracle Retail Pricing is a configurable and flexible pricing solution designed to meetthe varied needs of the retail industry. Pricing empowers retailers to streamline pricingstrategies across the organization, yielding a more predictable and profitable outcome.It provides decision support through pricing-focused business information to validateand approve new retails and markdowns.Pricing supports the creation and management of price changes, clearances andpromotions, integrating with the pricing execution systems, such as the POS in thestore and e-commerce systems, to provide details on these events when approved. Itsfunctionality includes the definition, maintenance, and review of price changes,clearances, and promotions, with capabilities that range from simple item pricechanges at a single location to complex promotional offers across zones. Pricing eventsare defined against the zone structure, which represents a group of locations organizedto support a retailer's pricing strategy. It also allows the user to break out of the zonestructure and create location-level events as needed.Pricing has three primary functions to create and maintain regular price changes,clearances, and promotions. Although each of the three pricing activities is unique, thesystem displays these using a common look and feel to the user creating events. Thesolution also supports dashboards to support management by exception, andleverages the notification framework to alert users to conflicting pricing events.Beta DraftOverview 1-1

1-2 Oracle Retail Pricing Cloud Service/Pricing Implementation GuideBeta Draft

2Getting Started2System OptionsSystem options are used to control behavior in Pricing, configure the duration thathistorical price events will be retained, and provide some defaulting for new events.The first time that pricing is opened after provisioning, these options should beconfigured in order to ensure that all pricing foundation and events created follow thedesired behavior.Getting Started 2-1

Price EventsPrice EventsRe-configurationRestricted?Default ValueDescriptionPrice Event Processing NoDaysNo1Represents the minimum number of days requiredbetween the create date and the effective date for allprice events. This system option also defines whenpromotions are communicated to external systems.Unlike price changes and clearances that arecommunicated on approval, promotions wait untilcloser to the effective date since there tend to bemore last-minute changes to promotions than othertypes of events. Price events that are created with aneffective date closer than this number of days fromthe current date are considered "emergency"changes. Valid values are 1-999.Single UOM Used forAll ItemsConditionalSystem OptionOptional?YesIndicates that all prices in your business will be interms of the same selling unit of measure (UOM). Itis recommended that a value always be set for thissystem option unless you do have varying sellingunits of measure for your business, as this will saveusers a step of having to enter a unit of measure andprevent potential errors. Valid values for this systemoption are pulled from the Merchandising units ofmeasure.Note: once a value is initialized, the system optionwill be disabled and cannot be updated.Offer End DateRequiredNoNoUncheckedIndicates whether an end date on a promotionaloffer is required. Valid values are checked (1) orunchecked (0). If checked, then all promotionaloffers will require an end date before they can beapproved.Allow Reward ListExclusions onTransaction OffersNoNoCheckedDetermines whether or not exclusions can bedefined for transaction level offers. The reward listexclusion allows you to indicate whether or notthere are certain items that should not have thediscount applied, if on the customer's transaction. Ifthis is checked (1), then users will be allowed to addexclusions to the rewarded items on a transactionoffer. If unchecked (0), then the option to addexclusions will be hidden.1Getting Started2-2

Price EventsSystem OptionOptional?Re-configurationRestricted?Default ValueDescriptionAllow Clearance andPromotion OverlapNoConditionalUncheckedIndicates whether or not promotional offers will beallowed to apply to items on clearance. If this is setto checked (1), then promotions can be applied toclearance items. If this is set to unchecked (0), thenthe "Apply To" option when creating promotionaloffers will default to "Regular" and be hidden.Note: if this value is changed from unchecked tochecked, then after saving the update the option willbe disabled and cannot be updated.Reset Clearance withPrice ChangeNoConditionalUncheckedIndicates whether or not a price change will be ableto be created for an item/location currently onclearance or that will be on clearance on the pricechange effective date. If this option is not checked(0), then a reset will need to be created andapproved first before any new price changes can becreated. If it is checked (1), then you will be able tocreate a price change for an item/location that iscurrently or will be on clearance, resetting it toregular price and changing the regular selling pricein one update.This option has a dependency on the Zone/ParentRanging system option. If that option is set tounchecked (0), then this parameter must have avalue of checked. Similarly, if this option is set tounchecked, the Zone/Parent Ranging parametermust be checked (1).Note: after this value is initialized, the option will bedisabled and cannot be updated.Markdown ValueRequired onClearancesNoNoUncheckedDetermines whether or not it is required that amarkdown value (e.g. First, Second, etc.) is definedfor clearance markdowns and resets. If this option isset to checked (1), then the markdown value must bedefined when creating a new markdown. If this isset to unchecked (0), then it is not required.Allow Multi UnitPricingNoNoUncheckedDetermines whether multi-unit pricing functionalitywill be used in both Merchandising and Pricing.Valid values are unchecked (0) or checked (1).Getting Started2-3

Conflict CheckingSystem OptionOptional?Re-configurationRestricted?Default ValueDescriptionAllow Supplier Siteand Brand for OfferItem SelectionNoNoUncheckedDefines whether the supplier/brand merchandiselevel are enabled when creating offers. Valid valuesare: unchecked (0) or checked (1). This value shouldbe set based on what your selling solutions cansupport. If integrating with Xstore POS, this shouldbe set to unchecked.1If implementing with Xstore POS, this should be set to unchecked, as Xstore does not support exclusions to transaction level offer reward lists.Conflict CheckingSystem OptionOptional?Re-configurationRestricted?Default ValueDescriptionClearance Retail mustbe less than or equalto Regular RetailNoNoCheckedDetermines whether or not the initial clearancemarkdown can increase the price of anitem/location from its current regular price. This istypically only required for cases where there isconcern over user error resulting in a price changebeing created rather than a clearance for the firstmarkdown. Valid values are checked (1) andunchecked (0).Clearance Retail mustbe less than PreviousMarkdownNoNoCheckedDetermines whether or not subsequent markdownsfor item/locations can increase the price from itscurrent clearance price. This is typically onlyrequired for cases where there is concern over usererrors. Valid values are checked (1) and unchecked(0).Run for SubmitNoNoCheckedDetermines whether or not conflict checking will berun for price changes and clearances when an eventis submitted. If unchecked (0), then conflict checkingwill only apply when attempting to approve a priceevent or updating an approved event. Whenchecked (1), it will apply both when submitting andapproving.Getting Started2-4

ZonesZonesSystem OptionOptional?Zone/Parent Ranging NoRe-configurationRestricted?Default ValueDescriptionConditionalCheckedDefines whether or not transaction levelitem/location ranging is required when creatingprice events, including regular price changes orclearance, at higher levels. For example, whensetting up price changes at zone and parent level, itchecks that at least one store or warehouse in thezone has an item/location relationship defined for atleast one transaction item in the parent to ensurethat price changes are not set up on items wherenothing is sold.If this system option is checked (1), when a usercreates a price change or clearance at a level higherthan transaction item/location level, there must beat least one item/location ranged on the event. Ifnot, then there will be an error raised when theevent is created. If this system option is not checked(0), then ranging validation will only be performedon price events created at the transaction/locationlevel and ranging checks will not be performed onevents created at any other higher level.This system option has a dependency on the ResetClearance with Price Change option. If theZone/Parent Ranging option is unchecked, then theReset Clearance with Price Change option must bechecked. Similarly, if the Reset Clearance with PriceChange option is unchecked, then the Zone/ParentRanging option must be checked.Note: after this value is initialized, the option will bedisabled and cannot be updated.RecognizeWarehouses asLocationsNoConditionalUncheckedControls whether or not warehouses can be added tozones, or be added to price changes and clearances.If unchecked (0), then price for your warehouseswill not be impacted by price changes andclearances. If checked (1), then price will bemanaged at warehouses and warehouses can also beindividually added to events.Note: if this value is changed from unchecked tochecked, then after saving the update the option willbe disabled and cannot be updated.Getting Started2-5

Data FilteringData RetentionSystem OptionOptional?Re-configurationRestricted?Default ValueDescriptionExecuted PriceChanges MonthsNoNo2Defines how many months executed price changeswill be retained. Valid values are 1-24 months. Note:when the process runs to remove executed pricechanges, it will remove a whole month at a time. So,some events may be retained slightly longer than thenumber of months defined here.Executed ClearancesMonthsNoNo2Defines how many months executed clearances willbe retained. Valid values are 1-24 months. Note:when the process runs to remove executedmarkdowns and resets, it will remove a wholemonth at a time. So, some events may be retainedslightly longer than the number of months definedhere.Expired Price Changeand Clearance DaysNoNo3Defines how many days that expired price changes,markdown, and resets will be retained. An expiredevent is defined as an event that has passed itseffective date and is still in Worksheet, Submitted, orRejected status. Valid values are 1-999 days.Data FilteringThis section of system options is only displayed if the Merchandising system option Data Level Filtering Enabled ischecked (Y).System OptionOptional?Re-configurationRestricted?Default ValueDescriptionClearance CadenceTemplates MerchandiseHierarchy LevelYesYesNULLHolds the merchandise hierarchy level used forfiltering of cadence templates. Valid values aredivision (D), group (G), department (P), class (C) orsubclass (S). If null, then data filtering bymerchandise hierarchy is not applied for this entity.Getting Started2-6

System DefaultsSystem OptionOptional?Re-configurationRestricted?Default ValueDescriptionClearance CadenceTemplates OrganizationalHierarchy LevelYesYesNULLHolds the organizational hierarchy level used forfiltering of cadence templates. Valid values are chain(C), area (A), region (R), or district (D). If null, thendata filtering by organizational hierarchy is notapplied for this entity.System DefaultsSystem defaults allow you to set up certain defaults for each price event type that will be used by default when newevents are created. Users will be able to override them on a particular event, but adding defaults can help cut down onerrors if you want your users to always enter price events in a particular way.Price ChangeSystem OptionOptional?

Oracle Retail Pricing Cloud Service/Pricing Implementation Guide Release 19.0 F25743-01 January 2020