| Oracle® Retail Merchandising System Operations Guide, Volume 1 - Batch Overviews and Designs 16.0.024 E89599-02 |
|
 Previous |
 Next |
| Oracle® Retail Merchandising System Operations Guide, Volume 1 - Batch Overviews and Designs 16.0.024 E89599-02 |
|
Previous |
Next |
The RMS competitive pricing functionality extracts a competitor's price for an item. RMS masters competitor price information. Oracle Retail Price Management (RPM) uses this information to determine if a price review should be performed.
The batch programs in this chapter only need to be run if the retailer uses competitive shopping to track prices at other retailers and wishes to use this information to drive pricing decisions in RPM.
The following batch designs are included in this functional area:
cmpupld.pc (Upload Competitor's Prices)
cmpprg.pc (Purge Aged Competitive Pricing Data)
| Module Name | cmpupld.pc |
| Description | Upload Competitor's Prices |
| Functional Area | Competitive Pricing |
| Module Type | Integration |
| Module Technology | ProC |
| Catalog ID | RMS61 |
| Runtime Parameters | NA |
This program is used to upload and process competitor item prices from an external source. The flat file uploaded by cmpupld.pc can contain pricing data for a completed shopping list or data for a new list of items to be shopped. The module processes data for both features.
Table 22-1 Scheduling Constraints
| Schedule Information | Description |
|---|---|
|
Frequency |
Daily |
|
Scheduling Considerations |
This upload program should be scheduled to run before any of the Retail Pricing Management (RPM) batch modules |
|
Pre-Processing |
NA |
|
Post-Processing |
NA |
|
Threading Scheme |
The number of threads will be based on the number of input files |
This is a file based upload, and file based restart/recovery logic is applied. The commit_max_ctr field should be set to prevent excessive rollback space usage and to reduce the overhead of file I/O. The recommended commit counter setting is 10000 records (subject to change based on experimentation).
| Integration Type | Upload to RMS |
| File Name | Determined by runtime parameter |
| Integration Contract | IntCon000007 |
Table 22-3 Input File Layout
| Record Name | Field Name | Field Type | Default Value | Description |
|---|---|---|---|---|
|
File Header |
File Type Record Descriptor |
CHAR (5) |
FHEAD |
Value that identifies the record type. |
|
File Line Identifier |
NUMBER (10) |
0000000001 |
Sequential file line number. |
|
|
File Type Definition |
CHAR(4) |
CMPU |
Value that identifies the file as that for this program. |
|
|
File Create Date |
CHAR (14) |
NA |
Date when the file was written by the external system. It should be in the YYYYMMDDHH24MISS format. |
|
|
File Detail |
File Type Record Descriptor |
CHAR (5) |
FDETL |
Value that identifies the record type. |
|
File Line Identifier |
NUMBER (10) |
Sequential file line number. |
||
|
Shopper ID |
NUMBER (4) |
Numeric value that uniquely identifies the shopper to which the competitive shopping list is assigned. |
||
|
Shop Date |
CHAR (14) |
Date when the competitive shop was performed. It should be in the YYYYMMDDHH24MISS format. |
||
|
Item |
CHAR (25) |
Alphanumeric value that uniquely identifies the transaction level or below transaction level item that was competitively shopped. |
||
|
Competitor ID |
NUMBER(10) |
Numeric value that uniquely identifies a competitor. |
||
|
Competitor Store ID |
NUMBER(10) |
Numeric value that uniquely identifies a competitor's store. |
||
|
Recorded Date |
CHAR (14) |
Date when the item's retail price was recorded at the competitor's store. It should be in the YYYYMMDD24MISS format. |
||
|
Competitive Retail Price |
NUMBER(20,4) |
Numeric value that represents the retail price at the competitor's store. Format for this value should include four implied decimal places. |
||
|
Competitive Retail Type |
CHAR(6) |
R, P, C |
Value that represents the retail type ('R' is for regular; 'P', promotional; and 'C', clearance) that was recorded. |
|
|
Promotion Start Date |
CHAR (14) |
Effective start date of the competitor's price. It should be in the YYYYMMDDHH24MISS format. |
||
|
Promotion End Date |
CHAR (14) |
Effective end date of the competitor's price. It should be in the YYYYMMDDHH24MISS format. |
||
|
Offer Type Code |
CHAR(6) |
Alphanumeric value that corresponds to a valid offer type (such as,. Coupon, Bonus Card, Pre-priced). Valid values are defined on CODE_DETAIL table with CODE_TYPE 'OFTP'. |
||
|
Multi-Units |
NUMBER(12,4) |
Numeric value that represents the number of units that must be purchased to qualify for a multi-unit price. An example of a multi-unit price would be 2 for $3.00. There are four implied decimal places. |
||
|
Multi-Units Retail |
NUMBER(20,4) |
Numeric value that represents the price for a multi-unit item that was competitively shopped. There should be four implied decimal places. |
||
|
File Trailer |
File Type Record Descriptor |
CHAR(5) |
FTAIL |
Value that identifies the record type. |
|
File Line Identifier |
NUMBER (10) |
NA |
Sequential file line number. |
|
|
File Record Counter |
NUMBER (10) |
NA |
Numeric value that represents the number of FDETL records in the file. |
| Module Name | cmpprg.pc |
| Description | Purge Aged Competitive Pricing Data |
| Functional Area | Competitive Pricing |
| Module Type | Admin |
| Module Technology | ProC |
| Catalog ID | RMS198 |
| Runtime Parameters | NA |
This program deletes from the competitive price history (COMP_PRICE_HIST) table and the competitive shopping list (COMP_SHIP_LIST) table based purge criteria based on system parameter settings. The Competitive Pricing Months parameter (comp_price_months) will determine how many months competitive price history should be maintained before deletion. The Competitive Pricing List Days (comp_list_days) parameter will determine how long a requested shopping list should remain on the shopping list table if it is not complete by the requested shop date.
