MRCH Batch Schedule

Oracle Retail Merchandising
Batch Schedule
Release 13.0
April 2008
Oracle Retail Merchandising Batch Schedule, Release 13.0
Copyright 2008, Oracle. All rights reserved.

Primary Author: Rich Olson
The Programs (which include both the software and documentation) contain proprietary
information; they are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright, patent, and other intellectual and industrial
property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the
extent required to obtain interoperability with other independently created software or as specified
by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any
problems in the documentation, please report them to us in writing. This document is not
warranted to be error-free. Except as may be expressly permitted in your license agreement for
these Programs, no part of these Programs may be reproduced or transmitted in any form or by
any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the
Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and
technical data delivered to U.S. Government customers are "commercial computer software" or
"commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the Programs, including documentation and technical data, shall be subject to the
licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent
applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software
Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other
inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate
fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the
Programs are used for such purposes, and we disclaim liability for any damages caused by such
use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation
and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from
third parties. Oracle is not responsible for the availability of, or any content provided on, thirdparty Web sites. You bear all risks associated with the use of such content. If you choose to
purchase any products or services from a third party, the relationship is directly between you and
the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or
(b) fulfilling any of the terms of the agreement with the third party, including delivery of products
or services and warranty obligations related to purchased products or services. Oracle is not
responsible for any loss or damage of any sort that you may incur from dealing with any third
party.
Value-Added Reseller (VAR) Language

(i) the software component known as ACUMATE developed and licensed by Lucent Technologies
Inc. of Murray Hill, New Jersey, to Oracle and imbedded in the Oracle Retail Predictive
Application Server Enterprise Engine, Oracle Retail Category Management, Oracle Retail Item
Planning, Oracle Retail Merchandise Financial Planning, Oracle Retail Advanced Inventory
Planning and Oracle Retail Demand Forecasting applications.
(ii) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation
(MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail
Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.
(iii) the SeeBeyond component developed and licensed by Sun MicroSystems, Inc. (Sun) of Santa
Clara, California, to Oracle and imbedded in the Oracle Retail Integration Bus application.
(iv) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of
Kirkland, Washington, to Oracle and imbedded in Oracle Retail Store Inventory Management.
(v) the software component known as Crystal Enterprise Professional and/or Crystal Reports
Professional licensed by Business Objects Software Limited (Business Objects) and imbedded in
Oracle Retail Store Inventory Management.
(vi) the software component known as Access Via licensed by Access Via of Seattle, Washington,
and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.
(vii) the software component known as Adobe Flex licensed by Adobe Systems Incorporated of
San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization
application.
(viii) the software component known as Style Report developed and licensed by InetSoft
Technology Corp. of Piscataway, New Jersey, to Oracle and imbedded in the Oracle Retail Value
Chain Collaboration application.
(ix) the software component known as WebLogic developed and licensed by BEA Systems, Inc.
of San Jose, California, to Oracle and imbedded in the Oracle Retail Value Chain Collaboration
application.
(x) the software component known as DataBeacon developed and licensed by Cognos
Incorporated of Ottawa, Ontario, Canada, to Oracle and imbedded in the Oracle Retail Value Chain
Collaboration application.
iii
Contents
Preface ............................................................................................................................. vii
Audience ............................................................................................................................... vii
Related Documents.............................................................................................................. vii
Customer Support...............................................................................................................viii
Conventions.........................................................................................................................viii
1 Introduction to Merchandising Batch Processing ................................................... 1
Batch Processing......................................................................................................................1
Types of Batch Programs ................................................................................................1
Batch Window ..................................................................................................................2
Batch Schedule and Phases.............................................................................................2
Integrated Merchandising Batch Schedule..........................................................................3
Program List ............................................................................................................................3
Batch Schedule Diagram ........................................................................................................5
RMS, ReIM, RTM Section ...............................................................................................5
ReSA Section.....................................................................................................................6
RPM Section......................................................................................................................6
Notations in the Batch Schedule Diagram....................................................................7
prepost Program ..............................................................................................................8
Modifications to the Batch Schedule ....................................................................................9
2 Program List............................................................................................................... 11
3 Batch Schedule Diagram .......................................................................................... 17
4 Interface Diagrams for RMS and RPAS ................................................................... 19
RMS Pre/Post Extract Diagrams .................................................................................20
RMS Foundation Data Extract Diagrams ...................................................................21
RMS Fact Data Extract Diagrams.................................................................................23
RPAS-RMS Fact Load Diagram ...................................................................................24
5 Interface Diagrams for RMS and RDW..................................................................... 25
6 Interface Diagram for RPM and RDW....................................................................... 37
7 Interface Diagram for ReIM and RDW ...................................................................... 39
Preface
This batch schedule document details the integrated cyclical processing schedules for the
Oracle Retail Merchandising applications:
Oracle Retail Merchandising System (RMS)
Oracle Retail Invoice Matching (ReIM)
Oracle Retail Price Management (RPM)
Oracle Retail Sales Audit (ReSA)
Oracle Retail Trade Management (RTM)
Oracle Retail Allocation

Note: Although Oracle Retail Allocation is a Merchandising
application, it is not represented in this batch schedule

because it does not have any batch programs to run. All
Allocation processing is online processing.
This guide describes the periodic and ad hoc phases of batch processing, as well as preand post-processing dependencies.
Audience
The audiences for this guide are as follows:
Systems analysts and system operations personnel who need information about
Merchandising processes, internally or in relation to systems across the enterprise
Integrators and implementation staff who have the overall responsibility for
implementing the Merchandising applications in their enterprise
Related Documents
For more information, see the following documents for the Oracle Retail Merchandising
products:
Oracle Retail Merchandising Implementation Guide
Oracle Retail Merchandising System Operations Guide
Oracle Retail Price Management Operations Guide
Oracle Retail Invoice Matching Operations Guide
Oracle Retail Data Warehouse Operations Guide
Oracle Retail Predictive Application Server documentation
Oracle Retail Demand Forecasting documentation
vii
Customer Support
https://metalink.oracle.com
When contacting Customer Support, please provide the following:
Product version and program/module name
Functional and technical description of the problem (include business impact)
Detailed step-by-step instructions to re-create
Exact error message received
Screen shots of each step you take
Review Patch Documentation

For a base release (".0" release, such as 13.0), Oracle Retail strongly recommends that you
read all patch documentation before you begin installation procedures. Patch
documentation can contain critical information related to the base release, based on new
information and code changes that have been made since the base release.
Oracle Retail Documentation on the Oracle Technology Network

In addition to being packaged with each product release (on the base or patch level), all
Oracle Retail documentation is available on the following Web site:
http://www.oracle.com/technology/documentation/oracle_retail.html
Documentation should be available on this Web site within a month after a product
release. Note that documentation is always available with the packaged code on the
release date.
Conventions
Navigate: This is a navigate statement. It tells you how to get to the start of the procedure
and ends with a screen shot of the starting point and the statement the Window Name
window opens.
Note: This is a note. It is used to call out information that is
important, but not necessarily part of the procedure.

This is a code sample
It is used to display examples of code
A hyperlink appears like this.
viii
1
Introduction to Merchandising Batch
Processing
This chapter is a brief introduction to Oracle Retail batch processing. It defines basic
terms and concepts, describes batch processing phases, and explains how to interpret the
batch schedule diagram and program list.
Batch Processing
Batch processing is the execution of a group of batch programs (jobs). The results are
returned without user intervention. Batch programs are commonly used for the
following reasons:
To process large volumes of transaction data
To interface with external systems
To perform internal maintenance
Batch programs can process very large quantities of data quickly and efficiently. Batch
programs can perform some updates that could be performed through online
transactions, but much more quickly and with less impact on system performance. Batch
processing is usually scheduled for times when systems are idle or least busy.
Batch programs can be run automatically using batch scheduler software. The batch
scheduler allows batch jobs to be set up in a specific order, with restrictions attached to
any program as needed. If an error occurs with a batch program, an administrator must
correct the error and manually rerun the batch program that failed.
Types of Batch Programs

Oracle Retail batch programs are of several types:
Upload programs bring data from external systems into the Oracle Retail database.
For example, the posupld program uploads daily transactions that occur at the point
of sale (POS) for processing by the Oracle Retail Management System (RMS).
Download programs extract data from RMS and format it so it can be used by
external systems. For example, the posdnld program extracts new and changed
information about an item/location for downloading to the point of sale.
System maintenance programs perform tasks such as updating the system date. For
example, the dtesys program increments the system date at the end of each batch
cycle.
Functional maintenance programs process data specific to a functional area. For

example, the storeadd program updates a number of tables to create entries for a new
store.
Batch Schedule 1
Batch Processing
Batch Window
Because of the impact on production systems, it is not always possible to run batch
programs during business hours; however, there is a window of opportunity during each
day or night when online systems are not being used. This time frame is the batch window.
For example, a retailer with stores throughout the continental U.S. might require its
online systems to be available from 8 AM Eastern Standard Time, when its East Coast
offices open, until 9 PM Pacific Standard Time, when its West Coast stores close. This
allows an eight-hour batch window for processing all batch jobs.
Batch Schedule and Phases

Order is critical when running batch programs. Some tasks need to be performed before
others. A batch schedule ensures that every time batch processing is performed, the
correct tasks are performed in the proper order.
The batch schedule is a diagram that represents all batch programs and how they are
sequenced. For each individual user, the schedule is a suggested starting point for the
installation. Some programs are specific to products that may not be installed, so these
programs may not be used at all.
The total batch schedule is divided into phases. Each phase must be completed before the
next phase can begin. Within a phase, there may also be programs that depend on the
completion of another program within that phase, so programs within each phase may
need to be run in a particular order.
2 Oracle Retail Merchandising
Merchandising Batch Schedule
Merchandising Batch Schedule

The integrated Merchandising batch schedule combines the batch schedules of all
Merchandising applications into a single schedule diagram. The diagram (later in this
document) shows the batch dependencies among the Merchandising applications.
The integrated Merchandising batch schedule combines the batch modules for the
following applications:
Oracle Retail Merchandising System (RMS)
Oracle Retail Trade Management (RTM)
Oracle Retail Sales Audit (ReSA)
Oracle Retail Invoice Matching (ReIM)
Oracle Retail Price Management (RPM)

Note: Although Oracle Retail Allocation is a Merchandising
application, it is not represented in this batch schedule

because it does not have any batch programs to run. All
Allocation processing is online processing.
Program List
The columns of the program list provide details about each batch program, as follows:
Column
Description
Program name
Name of the program or script
Functional area
Functional area of the application for which the batch program

is run
Threaded
Whether the program is threaded (Y/N)
Driver
Program driver
Phase
Phase during which the program is run (see the batch schedule
diagram)
Pre-dependency
Programs that must be completed before the program can be

run
Post-dependency
Programs that must be run after the program completes

successfully
Timing
How often the program is run (for example, daily, weekly,

monthly, ad hoc)
Restart/Recovery
Whether the program uses restart/recovery (R=Yes, N=No)
Run Parameters for Program
Command syntax to run the program
Batch Schedule 3
Program List
For example, the following shows the information in the program list about an RMS
phase 3 program named dealday:
Program Name
dealday
Functional Area
Deals
Threaded
Driver
Location
Phase
Pre-dependency
dealinc, dealfinc, prepost dealday pre
Post-dependency
prepost dealday post, salmnth
Timing
Monthly
Restart/Recovery
Usage
dealday userid/passwd
The program list is grouped in the following order:
RMS, RTM, and ReSA programs
RPM programs
ReIM programs
RMS extracts for Retail Predictive Application Server (RPAS)
RMS extracts for Retail Data Warehouse (RDW)
The extracts for RPAS and RDW are programs that are part of the RMS application.
Batch Schedule Diagram

The batch schedule diagram illustrates the program list pre- and post-dependency
details. The layout and notations of the diagram also illustrate required sequences and
other processing details. Executing the Merchandising batch processing in the manner
diagrammed ensures that all critical dependencies are met.
For ease of setting up a schedule at client site, and also based on logical application
dependencies, the diagram is divided into three main sections:
RMS, RTM, ReIM
ReSA
RPM
Later chapters of this document show data flow diagrams for other batch processes:
Chapter 4 shows the Retail Extract, Transform, and Load (RETL) data flows for the
extracts from RMS to RPAS.
Chapter 5 shows the RETL dimension and fact data flows for the extracts from RMS
to Retail Data Warehouse (RDW).
Chapter 6 shows the RETL data flow for the Promotion dimension extract from RPM
to RDW.
Chapter 7 shows the RETL data flow for the Supplier Invoice Cost dimension extract
from ReIM to RDW.
RMS, ReIM, RTM Section

The first section diagrams the RMS, ReIM, and RTM programs and their dependencies.
This section is further divided into phases 0 through 7, ad hoc, and date set batch.
Each phase must be completed before the next phase can begin. Also, a phase may
contain programs that depend on other programs within the phase. Programs within
each phase may need to run in a particular sequence.
The following are brief descriptions of the Merchandising batch processing phases.
Depending on your implementation, some programs and phases may not apply.
Phase
Description
Phase 0
The first phase performs essential table maintenance including:
Daily purges
Updates to currency exchange rates
Updates to value-added tax (VAT) data
Phase 1
This phase prepares the tables for interfacing with external systems in
Phase 2. Among other programs, the stock variance (stkvar) batch
program is run to update stock counts.
Phase 2
During this phase, information is uploaded from external interfaces,

including point of sale (POS) data (posupld batch program).
Phase 3
In this phase, the main RMS processing programs are run for
purchasing, ordering, stock ledger, deals, and replenishment.
Batch Schedule 5
Phase
Description
Phase 4
This phase pushes data to external sources. Changed system

information is rebuilt. Open to buy (OTB) data is updated. Information
is sent to the forecasting system.
Phase 5
This phase consists of ReIM process upload programs.
Phase 6
This phase consists of ReIM process roll-up programs.
Phase 7
This phase consists of ReIM process download programs.
Ad Hoc
Ad hoc batch programs can be run at any time. The ad hoc programs
have no phase dependencies.
Date Set
The Date Set phase increments the system date and updates other
calendar dates.
Note: The date set phase should be the very last phase to run. Even the
ad hoc programs should be run before the date set program.

Read the batch schedule diagram from left to right. In the following example, any of the
programs (ediupavl, ediupack, stkvar,ditinsrt, lifstkup, ReceiverAdjustment,
DiscrepancyPurge) can start at the same time; however, the stkupld program cannot start
until the lifstkup program is successfully completed.
Sequence ---------
Phase 1
ediupavl
ediupack
stkvar
ditinsrt
lifstkup
stkupld
ReceiverAdjustment (ReIM) *
DiscrepancyPurge(ReIM)
ReSA Section
This section diagrams the ReSA programs and their dependencies.
RPM Section
This section diagrams the RPM programs and their dependencies.
Notations in the Batch Schedule Diagram

Pipes
Pipes are vertical bars ( | ) that represent the dependencies within a phase. Reading left
to right, a pipe indicates that one or more programs to the right depend upon completion
of one or more programs to the left.
In the following example, the stkupld module depends on the lifstkup module; that is,
the stkupld module can be run only after successful completion of the lifstkup module.
lifstkup
stukpld
In the following example, both of the modules cntrordb and reqext are dependent on
ociroq. Neither cntrordb nor reqext can be run until the ociroq module has completed
successfully.
cntrordb
ociroq
reqext
In the following example, the ibcalc module is dependent on both ibexpl and cntrprss.
The ibcalc module cannot be run until both ibexpl and cntrprss have completed
successfully.
ibexpl
ibcalc
cntrprss
Abbreviations
In the diagram, abbreviations in parentheses that follow program names have the
following meanings:
Abbreviation
Meaning
(perl)
The module is a Perl script.
(FIF)
The module is related to the Financials application.
(sqlldr)
There is a sqlloader process to load/ftp the output files.
(rebuild all)
There is a rebuild process inside the application.
(IM)
The module is related to Invoice Matching but owned by RMS.
(RMS)
The module belongs to RMS.
(RMS)
(Bold type) The RMS module is executed externally to that phase.
(ReSA)
The module belongs to ReSA.
(ReSA)
(Bold type) The ReSA module is executed externally to that phase.
(ReIM)
The module belongs to ReIM.
(RTM)
The module belongs to RTM.
(Weekly)
The module is executed weekly.
(Monthly)
The module is executed monthly.
(Forms Auditing)
This is an online forms auditing process related to ReSA.
Batch Schedule 7
Footnotes
Footnote symbols (*, **, , ) refer to footnotes that appear below that phase or section of
the diagram.
prepost Program
The prepost program facilitates multi-threading by allowing general system
administration functions (such as table deletions or mass updates) to be completed after
all threads of a particular program have been processed. The prepost program must be
run before, after, or both before and after, programs that require specific processing to
run or complete successfully.
In the batch schedule diagram, the prepost program is indicated by pre and post
entries, as in the following examples.
In the following example, pre-processing is required before running the ociroq program.
pre
ociroq
In the following example, pre-processing is required before running the stkupd program.
Also, post-processing is required after successful completion of the stkupd program.
pre
stkupd
post
In the following example, post-processing is required after successful completion of the

sccext program.
sccext
post
Modifications to the Batch Schedule
Modifications to the Batch Schedule

The integrated Merchandising batch schedule shows the dependencies for all the
programs that could be run by a retailer. Based on many factors, there will always be
some programs that a retailer does not run. Determining which programs, or groups of
programs, are not required is a job that should be performed at implementation time.
One major factor involves the applications that the retailer has purchased and wants to
install:
For example, a retailer may have purchased RMS, but not ReIM; in this case, the
ReIM programs would not be run.
Another example is that a retailer may not want to use some functionality within an
application. Perhaps a retailer purchased RMS but did not purchase the RDW
application. In this case, the retailer may not want to run the programs that extract
RMS data to be used later by the RDW application.
These major configuration choices also affect whether some programs are used:
Whether the Retail Integration Bus (RIB) is used

For more information about configuring the RIB for Merchandising applications, see
Configuring RPM without the RIB in the Backend System Administration and
Configuration chapter of the Retail Price Management Operations Guide.
Whether full-featured or simplified Retail Price Management (RPM) is used

For more information about configuring simplified RPM, see the Backend System
Administration and Configuration chapter in the Retail Price Management
Operations Guide.
Whether full-featured or simplified RTM is used

For more information about configuring simplified RTM, see the Oracle Retail
Trade Management Batch chapter in Volume 1 of the Retail Merchandising System
Operations Guide.
Batch Schedule 9
RMS,RTM,ReSA Program Dependency and Scheduling Details

Program Name
auditprg
auditsys
ccprg
cednld
cmpprg
cmpupld
cntrmain
cntrordb
cntrprss
Functional Area
Audit
Audit
Costing
Trade Management
Pricing
Pricing
Contracting
Contracting
Contracting
Threaded
N
N
N
Y
N
N
N
Y
Y
Driver
N/A
N/A
N/A
Broker
N/A
N/A
N/A
Contract
Dept
Phase
ad hoc
ad hoc
ad hoc
2
ad hoc
ad hoc
0
3
3
costcalc
cremhierdly
Deals
Reclassification
Y
N
Supplier
N/A
2
4
dealact
dealcls
Deals
Deals
Y
N
Deal Id
N/A
3
3
dealday
Deals
Location
dealex
Deals
Deal Id
Pre-dependency
N/A
N/A
N/A
N/A
N/A
N/A
N/A
rpladj
rplext
ditinsrt
precostcalc
N/A
salstage
prepost dealact_nor pre
prepost dealact_po pre
prepost dealact_sales pre
N/A
dealinc
precostcalc
dealinc
dealfct
Deals
Deal Id
dealfinc
Deals
Deal Id
dealinc
dealprg
dealupld
Deals
Deals
Deals
Y
N
Y
Deal Id
N/A
File-based
dfrtbld
discotbapply
distropcpub
Item Maintenance
OTB
Pricing/Transfers/Allocation Publish
Y
Y
Y
Dept
Dept
Store
ditinsrt
dlyprg
docclose
Deals
Maintenance
Receiving
N
N
N
N/A
N/A
N/A
dtesys
dummyctn
edidladd
edidlcon
edidlinv
Calendar
Receiving
Maintenance
Contracting
Invoice Matching
N
N
N
N
Y
N/A
N/A
N/A
N/A
Location
edidlord
edidlprd
ediprg
ediupadd
ediupack
ediupavl
ediupcat
elccostcalc
fcstprg
fcstrbld
fcstrbld_sbc
Ordering
EDI Interface - Sales and Inventory
EDI Interface - Purge
Maintenance
EDI Interface - ordering
EDI Interface - Contracts
EDI Interface - Suppliers
Costing
Forecasting
Forecasting
Forecasting
N
N
N
N
N
N
N
Y
Y
Y
Y
N/A
N/A
N/A
File-based
N/A
File-based
File-based
Supplier
Domain Id
Domain Id
Domain Id
4
4
ad hoc
2
1
1
ad hoc
ad hoc
ad hoc
3
3
fifgldn1
fifgldn2
fifgldn3
ftmednld
gcupld
genpreiss
gradupld
Financial Interface
Financial Interface
Financial Interface
Planing System Interface
Misc Interface - Taxgeocode
Ordering
Forecasting
Y
Y
Y
N
N
Y
N
Dept
Dept
Store/Wh
N/A
N/A
Supplier
File-based
3
3
3
ad hoc
ad hoc
ad hoc
ad hoc
hstbld
hstbld_diff
hstbldmth
hstbldmth_diff
Sales
Sales
Sales
Sales
Y
N
Y
N
Location
N/A
Dept
N/A
3
ad hoc
3
ad hoc
salstage
salmth
N/A
N/A
N/A
N/A
posupld
prepost hstbld pre (for rebuild all)
hstbld
posupld
N/A
hstmthupd
hstprg
hstprg_diff
Sales
Sales
Sales
Y
N
N
Location
N/A
N/A
3
ad hoc
ad hoc
(The program should be run on the last day of

the month).
N/A
N/A
hstwkupd
Sales
Store/Wh
htsupld
Trade Management
File-based
ad hoc
ibcalc
ibexpl
invaprg
invclshp
invprg
lcadnld
lclrbld
lcmdnld
lcup798
lcupld
Investment Buy
Investment Buy
Inventory Adjustments
Invoice Matching
Invoice Matching
Letter of Credit
Maintenance - Location
Letter of Credit
Letter of Credit
Letter of Credit
Y
N
N
N
N
N
N
N
N
N
Dept
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
3
3
ad hoc
2
ad hoc
4
ad hoc
4
2
2
N/A
Hts240_to_2400 (perl script)
Ushts2rms (perl script)
prepost htsupld pre
ibexpl
replext
prepost ibcalc pre
rplext
N/A
N/A
ordprg
N/A
storeadd
N/A
lcmt798 (perl script)
lifstkup
likestore
Stock Ledger
N
Y
File-based
Dept
1
ad hoc
inv_bal_upload.sh (warehouse mgmt program)

storeadd
mrt
mrtprg
Mass Return Transfers

Y
Y
Warehouse
Warehouse
2
ad hoc
N/A
N/A
mrtrtv
Warehouse
mrt
mrtupd
nwppurge

Stock Ledger
Y
N
Warehouse
N/A
2
ad hoc
3
ad hoc
0
3
4
3
1
0
ad hoc
date_set
ad hoc
ad hoc
ad hoc
4
dealact
dealact
prepost dealinc pre
N/A
(This program is the first one in Deals batch)
(This program will likely be run after sales
information is uploaded into Oracle Retail)
orddscnt
PriceEventExecutionBatch(RPM)
N/A
N/A
N/A
sastdycr
(This program should run at the end of
the batch cycle)
N/A
N/A
N/A
N/A
ordrev
(and after replenishment batch)
prepost edidlprd pre
(Towards the end of the batch cycle)
N/A
N/A
N/A
N/A
N/A
prepost fcstprg pre
N/A
prepost fcstrbld post
salstage
mrtrtv
N/A
Post-dependency
N/A
N/A
N/A
N/A
N/A
All RPM batch modules
All Replenishment modules
prepost cntrordb post
rplbld
Timing
daily
daily
monthly
daily
daily
ad hoc
daily
daily
daily
Uses Restart/Recovery
N
N
N
R
N
R
R
R
R
Run Parameters for Programs

auditprg userid/passwd
auditsys userid/passwd
ccprg userid/passwd
cednld userid/passwd broker file_name
cmpprg userid/passwd
cmpupld userid/passwd input_file reject_file
cntrmain userid/passwd
cntrordb userid/passwd
cntrprss userid/passwd
prepost costcalc post

reclsdly
daily
daily
R
R
costcalc userid/passwd supplier (May use the batch_costcalc.ksh for launching this program as it is created based on performance considerations)
cremhierdly userid/passwd
N/A
N/A
prepost dealday post
salmnth
dealinc
reclsdly
daily
daily
R
R
dealact userid/passwd
dealcls userid/passwd
monthly
dealday userid/passwd
daily
dealex userid/passwd
salmth
dealfct
dealday
salmth
daily
dealfct userid/passwd [Y/N - EOM processing ind]
weekly/ad hoc
dealfinc userid/passwd
salmth (if monthly)

N/A
(All other deals programs)
monthly
monthly
daily
R
R
R
dealinc userid/passwd [Y/N -EOM processing ind]

dealprg userid/passwd
dealupld userid/passwd input_file reject_file
(SQL*Load the output file)

N/A
N/A
daily
daily
daily
R
R
R
dfrtbld userid/passwd outfile

discotbapply userid/passwd
distropcpub userid/passwd
costcalc
orddscnt
(All other batch programs)
N/A
daily
daily
daily
R
N
R
ditinsrt userid/passwd (P or S) (supplier/partner).

P or S = program is either run for deals set up by Partner or Supplier.
supplier/partner is selected by appropriate calling script and passed into program. Note:
(May use the batch_ditinsrt.ksh for launching this program as it is created based on performance considerations)
dlyprg userid/passwd
docclose userid/passwd
prepost dtesys post

N/A
N/A
N/A
N/A
daily
daily
ad hoc
ad hoc
daily
N
N
N
N
R
dtesys userid/passwd [indate--YYYYMMDD format]

dummyctn userid/passwd
edidladd userid/passwd ediadd_output ediadd_catalog
edidlcon userid/passwd edidlcon_outfile
edidlinv userid/passwd output_filename
N/A
prepost edidlprd post
N/A
N/A
N/A
N/A
N/A
prepost elccostcalc post
prepost fcstprg post
prepost fcstrbld post
N/A
ad hoc
daily
monthly
daily
ad hoc
daily
daily
ad hoc
daily
weekly
weekly
R
R
R
N
R
R
R
R
N
R
R
edidlord userid/passwd filename

edidlprd userid/passwd filename
ediprg userid/passwd
ediupadd userid/passwd input_file reject_file
ediupack userid/passwd data_file reject_file
ediupavl userid/passwd input_file reject_file
ediupcat userid/passwd edi_data_file error_file
elccostcalc userid/passwd
fcstprg userid/passwd domain
fcstrbld userid/passwd
fcstrbld_sbc userid/passwd
daily
daily
monthly
ad hoc
ad hoc
ad hoc
ad hoc
R
R
R
R
R
R
R
fifgldn1 userid/passwd
ftmednld userid/passwd
gcupld <username/password@environment> <infile> <outfile>
genpreiss userid/passwd
gradupld userid/passwd input_file rej_file
prepost hstbld post

N/A
prepost hstbldmth post
prepost hstbld post
(Run SQL*Loader using the control file
hstmthupd.ctl to load data from the output file
written by HSTMTHUPD.PC for non-existent records
on ITEM_LOC_HIST_MTH)
N/A
N/A
Run SQL*Loader using the control file hstwkupd.ctl
to load data from the output file written by
HSTWKUPD.PC for non-existent records on
ITEM_LOC_HIST
weekly
ad hoc
monthly
ad hoc
R
N
R
N
hstbld userid/passwd level(weekly/rebuild)

hstbld_diff userid/passwd
hstbldmth userid/passwd level(monthly/rebuild)
hstbldmth_diff userid/passwd
monthly
monthly
weekly
R
N
N
hstmthupd userid/passwd (out_file)

hstprg userid/passwd
hstprg_diff userid/passwd
weekly
hstwkupd userid/passwd (out_file)
N/A
ad hoc
htsupld userid/passwd input_file reject_file country_id ; perl hts_240_to_2400 inputfile outputfile ; perl ushts2rms inputfile outputfile rejectfile
rplbld
ibcalc
N/A
N/A
N/A
N/A
N/A
N/A
daily
daily
monthly
daily
monthly
daily
monthly
daily
daily
daily
R
N
N
N
R
R
R
R
R
R
ibcalc userid/passwd
ibexpl userid/passwd
invaprg userid/passwd
invclshp userid/passwd
invprg userid/passwd
lcadnld userid/passwd output_file
lclrbld userid/passwd
lcmdnld userid/passwd output_file.
lcup798 userid/passwd input_file rej_file
lcupld userid/passwd input_file rej_file
stkupld
prepost likestore post
mrtrtv
mrtupd
N/A
mrtupd
daily
daily
N
R
lifstkup userid/passwd input_file output_file

likestore userid/passwd
daily
ad hoc
R
R
mrt userid/passwd
mrtprg userid/passwd
daily
mrtrtv userid/passwd
daily
ad hoc
R
N
mrtupd userid/passwd
nwppurge userid/passwd
prepost fifgldn1 post

salapnd
N/A
N/A
N/A
N/A
N/A
N/A
N/A
salapnd
nwpyearend
Stock Count
Location
ociroq
onictext
onorddnld
onordext
ordautcl
Replenishment
Ordering
N
Y
Y
Y
N
N/A
Transfer
Store/Wh
Order
N/A
3
4
4
4
ad hoc
orddscnt
ordprg
ordrev
Deals
Ordering
Ordering
Y
N
N
Supplier
N/A
N/A
4
ad hoc
4
ordupd
otbdlord
otbdlsal
otbdnld
otbprg
otbupfwd
otbupld
poscdnld
posdnld
posgpdld
posupld
Ordering
OTB
OTB
OTB
OTB
OTB
OTB
Point of Sale Interface
Sales
N
N
N
N
N
Y
Y
N
Y
N
Y
N/A
N/A
N/A
N/A
N/A
File-based
File-based
N/A
Store
N/A
File-based
4
4
4
4
ad hoc
ad hoc
ad hoc
4
ad hoc
4
2
precostcalc
prepost
reclsdly
Deals
Pre/post functionality
Item Maintenance
Y
N
Y
Supplier
N/A
Reclass no
2
all phases
4
repladj
Replenishment
Dept
reqext
Replenishment
Partition (Item)
rilmaint
Replenishment
Location
rplapprv
Replenishment
N/A
run on last day of year

prepost ociroq pre
repladj
onordext
onictext
prepost onordext pre
N/A
ditinsrt
sccext
reclsdly
N/A
orddscnt
sccext
(After RPM pricing change extraction
batch)
ordupd
ordupd
ordupd
N/A
N/A
N/A
posdnld
N/A
reclsdly
saexprms(ReSA)
ditinsrt
prepost precostcalc pre
N/A
cremhierdly
rplatupd
posupld
rplatupd
repladj
prepost ociroq pre
ociroq
prepost reqext pre
storeadd
sccext
rplatupd
rplsplit
supcnstr
prepost rplapprv pre
N/A
yearly
nwpyearend userid/passwd
N/A
onorddnld
N/A
onictext
N/A
daily
weekly
daily
daily
daily
R
R
R
R
N
ociroq userid/passwd
onictext userid/passwd datefile
onorddnld userid/passwd
onordext userid/passwd datefile
ordautcl userid/passwd
daily
monthly
daily
R
N
R
orddscnt userid/passwd
ordprg userid/passwd
ordrev userid/passwd
daily
daily
daily
daily
monthly
daily
daily
daily
daily
daily
daily
N
R
R
R
N
R
R
R
R
R
R
daily
daily
daily
R
N
R
ordupd userid/passwd
otbdlord userid/passwd output_file
otbdlsal userid/passwd output_file
otbdnld userid/passwd output_file
otbprg userid/passwd
userid/passwd input_file reject_file
otbupld userid/passwd input_file reject_file
poscdnld userid/passwd outputfile
posdnld userid/passwd output_filename
posgpdld userid/passwd output_file
posupld userid/passwd infile rejfile vatfile itemfile lockfile
precostcalc userid/passwd supplier (May use the batch_precostcalc.ksh for launching this program as it is created based on performance
considerations)
prepost userid/passwd program pre_or_post
reclsdly userid/passwd process_mode
daily
repladj userid/passwd
discotbapply
invprg
edidlord
otbdnld
otbdlsal
otbdlord
N/A
N/A
N/A
N/A
N/A
N/A
prepost poscdnld post
prepost posdnld post
N/A
prepost posupld post
dealcls
salstage
costcalc
N/A
prepost reclsdly post
reqext
rplext
daily
reqext userid/passwd partition_position (May use the batch_reqext.ksh for launching this program as it is created based on performance
considerations)
prepost rilmaint post

repladj
daily
rilmaint username/password
N/A
daily
rplapprv userid/passwd
daily
rplatupd userid/passwd
daily
rplbld username/password
daily
daily
monthly
daily
daily
monthly
R
N
N
R
R
N
daily
rplext userid/passwd dept (May use the batch_rplext.ksh for launching this program as it is created based on performance considerations)
rplprg userid/passwd
rplprg_month userid/passwd
rplsplit userid/passwd
rpmmovavg userid/passwd business_date(YYYYMMDD) store(optional)
rtvprg userid/passwd
sacrypt userid/passwd infile outfile key_file e/d (Encryption/Decryption indicator)
Note: outfile generated by batch is infile for saimptlog.
prepost reqext post
rplext
prepost rplatupd post

repladj
rplatupd
Replenishment
Location
rplbld
Replenishment
Supplier
prepost rplatupd pre

ibcalc
rplext
cntrprss
rplext
reqext
vrplbld
ibexpl
prepost rpl pre
rplatupd
supcnstr
prepost rplext post
contracting is used,
otherwise run
rilmaint
repladj
reqext
rplext
rplprg
rplprg_month
rplsplit
rpmmovavg
rtvprg
Replenishment
Replenishment
Replenishment
Replenishment
Pricing
RTV
Y
N
N
Y
Y
N
Dept
N/A
N/A
Supplier
Store
N/A
3
ad hoc
ad hoc
3
3
ad hoc
sacrypt
Sales Audit
Store/Day
SA
saescheat
Sales Audit
N/A
SA
saexpach
Sales Audit
N/A
SA
saexpgl
Sales Audit
N/A
SA
saexpim
saexprdw
Sales Audit
Sales Audit
N
Y
N/A
Store
SA
SA
saexprms
Sales Audit
Store
SA
saexpuar
Sales Audit
N/A
SA
sagetref
saimpadj
Sales Audit
Sales Audit
N
N
N/A
N/A
SA
SA
saimptlog
Sales Audit
Store/Day
SA
saimptlogfin
Sales Audit
N/A
SA
salapnd
saldly
saleoh
salins
salmaint
Stock Ledger
Stock Ledger
Stock Ledger
Sales
Stock Ledger
N
Y
Y
N
N
N/A
Store/Wh
Dept
N/A
N/A
3
3
3
0
ad hoc
salmth
salprg
Stock Ledger
Stock Ledger
Y
N
Dept
N/A
3
ad hoc
ibcxpl
ibcalc
rplbld )
N/A
N/A
supcnstr
salstage
N/A
N/A
N/A
rplapprv
N/A
N/A
sagetref
satotals
sarules
satotals
sarules
sapreexp
satotals
sarules
sapreexp
sapreexp
saescheat
sapreexp
satotals
sarules
sapreexp
satotals
sarules
sapreexp
N/A
saexpim
sapurge
N/A
sastdycr
saimptlogfin
sagetref
saprepost saimptlog pre
saimptlog
savouch
salstage
fifgldn1
fifgldn2
salstage
salmth
N/A
N/A
salweek
pre_dwi_extract.ksh(RMS
N/A
cntrprss(if
monthly
saescheat userid/passwd
daily
saexpach userid/passwd
N/A
daily
saexpgl userid/passwd
N/A
resa2rdw(perl script)
daily
daily
R
R
saexpim userid/passwd
saexprdw userid/passwd ; perl resa2rdw inputfile outputfile
saprepost saexprms post
daily
saexprms userid/passwd
N/A
daily
saimptlog
satotals
saprepost saimptlog post
(Use sql Loader to load data into ReSA tables)
daily
daily
R
R
daily
saexpuar userid/passwd
sagetref userid/passwd itemfile wastefile ref_itemfile prim_variantfile varupcfile storedayfile codesfile errorfile ccvalfile storeposfile tendertypefile
merchcodesfile partnerfile supplierfile employeefile bannerfile.
(To prevent a file from being written, place a '-' in its place. Note: Item files must all be written together).
saimpadj userid/passwd input_file rej_file
saimptlog user/pw infile badfile itemfile wastefile refitemfile primvariantfile varupcfile storedayfile promfile codesfile errorfile ccvalfile storeposfile
tendertypefile merchcodefile partnerfile supplierfile employeefile bannerfile
satotals
daily
saimptlogfin userid/passwd store_day_file
N/A
salweek
N/A
N/A
N/A
daily
daily
half yearly
daily
half yearly
R
R
N
R
N
salapnd userid/passwd
saldly userid/passwd
saleoh userid/passwd
salins userid/passwd
salmaint userid/passwd pre_or_post
prepost salmth post

N/A
monthly
daily
R
N
salmth userid/passwd
salprg userid/passwd
saldly
salapnd
salweek
dealfct
rpmmovavg
fifgldn1
fifgldn2
salstage
Stock Ledger
N/A
salweek
sapreexp
saprepost
Stock Ledger
Sales Audit
Sales Audit
Y
N
N
Dept
N/A
N/A
3
SA
SA
sapurge
Sales Audit
Store
SA
sarules
Sales Audit
N/A
SA
sastdycr
satotals
savouch
sccext
schedprg
sitmain
soutdnld
stkdly
stkprg
stkschedxpld
Sales Audit
Sales Audit
Sales Audit
Costing
Organizational Hierarchy
Item Maintenance
Forecasting
Stock Ledger
Stock Ledger
Stock Ledger
N
N
N
Y
N
N
Y
Y
N
Y
N/A
N/A
N/A
Cost change
N/A
N/A
Domain Id
Dept
N/A
Location
stkupd
stkupld
stkvar
Stock Ledger
Stock Ledger
Stock Ledger
Y
Y
Y
Location
Dept
Dept
3
1
1
stkxpld
stlgdnld
Stock Ledger
Stock Ledger
Y
Y
Dept
Dept
3
4
storeadd
supcnstr
supmth
tamperctn
tcktdnld
tifposdn
tranupld
tsfclose
tsfprg
txrposdn
txrtupld
vatdlxpl
Replenishment
Stock Ledger
Receiving
Maintenance
Sales Tax
Trade Management
Transfers
Transfers
Point of Sale Intereface
Sales Tax
Maintenance - VAT
N
N
Y
N
N
N
Y
Y
N
N
N
Y
N/A
N/A
Dept
N/A
N/A
N/A
File-based
Transfer
N/A
N/A
N/A
Vat Region
vendinvc
Deals
Deal Id
N/A
rplbld
N/A
N/A
N/A
txrposdn
N/A
N/A
N/A
N/A
N/A
N/A
dealact
salstage(if daily)
prepost vendinvc pre
vendinvf
vrplbld
Deals
Replenishment
Y
Y
Deal Id
Supplier
3
2
salstage(if daily)
prepost vendinvf pre
ediupack
wasteadj
Stock Ledger
Store
wfcostcalc
wfordcls
wfordprg
wfordupld.ksh
wfrtnprg
whadd
Costing
Ordering
Ordering
Ordering
Ordering
Y
Y
Y
Y
Y
N
Store_Wh
Wholesale Order ID
Wholesale Order ID
CustomerRefID
Wholesale Return ID
N/A
whstrasg
N/A
Program Name
ItemReclassBatch
NewItemLocBatch
LocationMoveScheduleBatch
Functional Area
Future Retail
Future Retail
Zone Structure/Future Retail
Threaded
N
N
Y
Driver
N/A
N/A
Location move
date_set
SA
SA
3
ad hoc
ad hoc
4
3
ad hoc
0
ad hoc
3
3
ad hoc
ad hoc
4
ad hoc
ad hoc
ad hoc
4
4
0
3
2
ad hoc
ad hoc
adhoc
ad hoc
ad hoc
3
posupld
saldly
stkdly
salapnd
prepost salweek pre
dealfct
dealinc
vendinvc
vendinvf
SA audit process
N/A
saprepost sapurge pre
(This program should be run as the last
program in the ReSA batch schedule)
satotals
(It should run before the DTESYS batch program
and before the next store/days transactions are
received)
saimptlogfin
saimptlog (and its SQL Load process)
cstisldex.ksh (RMS to RDW RETL extract)
N/A
lclrbld
N/A
stkvar
N/A
N/A
prepost stkupd pre
stkxpld
lifstkup
N/A
stkschedxpld
wasteadj
N/A
N/A
costcalc
prepost wfcostcalc pre
N/A
wfordcls
N/A
N/A
N/A
(Must be run after all replenishment batch
programs).
daily
salstage userid/passwd
weekly
daily
daily
R
R
N
salweek userid/passwd
sapreexp userid/passwd
saprepost userid/passwd program pre_or_post
daily
sapurge userid/passwd deleted_items_file [optional list of store days to be deleted]
daily
sarules userid/passwd store_no
dtesys
sarules
saimptlogfin
prepost sccext post
N/A
N/A
N/A
salweek
prepost stkprg post
stkxpld
daily
daily
daily
daily
monthly
ad hoc
daily
daily
monthly
daily
R
R
R
R
R
R
R
R
N
R
sastdycr userid/passwd [YYYYMMDD]

satotals userid/passwd store_no
savouch userid/passwd infile rejfile tendertype_file
sccext userid/passwd
schedprg userid/passwd
sitmain userid/passwd
soutdnld userid/passwd
stkdly userid/passwd
stkprg userid/passwd
stkchedxpld userid/passwd
prepost stkupd post

N/A
N/A
daily
daily
daily
R
R
R
stkupd userid/passwd
stkupld userid/passwd input_file reject_file
stkvar userid/passwd [ report_file_name ]
stkupd
N/A
prepost storeadd post
likestore
rplsplit
prepost supmth post
N/A
N/A
prepost tifposdn post
N/A
N/A
N/A
tifposdn
N/A
prepost vatdlxpl post
prepost vendinvc post
salweek(if weekly)
salmth (if monthly)
prepost vendinvf post
salweek(if weekly)
salmth (if monthly)
prepost vrplbld post
daily
weekly
R
R
stkxpld userid/passwd
stlgdnld userid/passwd input_file
daily
daily
monthly
ad hoc
daily
daily
daily
daily
monthly
daily
ad hoc
daily
R
R
R
N
R
R
R
R
R
R
R
R
storeadd userid/passwd
supcnstr userid/passwd
supmth userid/passwd
tamperctn userid/passwd
tcktdnld userid/passwd filename print_online_ind days_in_advance [location]
tifposdn userid/passwd output_file
tranupld userid/passwd infile
tsfclose userid/passwd
tsfprg userid/passwd
txrposdn userid/passwd
txrtupld username/password input_file reject_file
vatdlxpl userid/passwd
daily
vendinvc userid/passwd
daily
daily
R
R
vendinvf userid/passwd
vrplbld userid/passwd
salmth
prepost salweek post
(Before any SA export process)
N/A
saprepost sapurge post

sapreexp
saescheat
daily
wasteadj userid/passwd
prepost wfcostcalc post

wfordprg
N/A
N/A
N/A
prepost whadd post
stkxpld
stkupd
daily
daily
daily
ad hoc
daily
daily
R
R
R
R
R
R
wfcostcalc userid/passwd
wfordcls userid/passwd
wfordprg userid/passwd
wfordupld.ksh userid/passwd input_file_directory output_file_directory number_of_threads
wfrtnprg userid/passwd
whadd userid/passwd
prepost whstrasg post
daily
whstrasg userid/passwd
Post-dependency
NewItemLocBatch
LocationMoveBatch
LocationMoveBatch, PriceEventExecutionBatch
PriceEventExecutionBatch
Timing
daily/ad hoc
daily/ad hoc
daily, adhoc
N
N
N

itemReclassBatch.sh rpm-app-userid password
newItemLocBatch.sh rpm-app-userid password [status [error-commit-count]]
locationMoveScheduleBatch.sh rpm-app-userid password
daily
locationMoveBatch.sh rpm-app-userid password
PriceEventExecutionRMSBatch
daily
priceEventExecutionBatch.sh rpm-app-userid password
PriceEventExecutionDealsBatch
MerchExtractKickOffBatch
daily
daily
daily
daily
N
N
N
N
priceEventExecutionRMSBatch.sh rpm-app-userid password

priceEventExecutionDealsBatch.sh rpm-app-userid password
priceStrategyCalendarBatch.sh rpm-app-userid password
worksheetAutoApproveBatch.sh rpm-app-userid password
Wholesale Item Catalog Report (RMS)

N/A
daily
daily
N
N
merchExtractKickOffBatch.sh rpm-app-userid password

purgeBulkConflictCheckArtifacts.sh rpm-app-userid password
RPM Dependency and Scheduling Details

Phase
N/A
N/A
N/A
LocationMoveBatch
Zone Structure/Future Retail
Location move
N/A
Price Change/Clearance/Promotion
Pricing event
N/A
PriceStrategyCalendarBatch
WorksheetAutoApproveBatch
Price Strategy
Pricing Worksheet
Y
Y
Pricing event
Pricing event
N
Y
Price strategy
N/A
N/A
N/A
N/A
PurgeBulkConflictCheckArtifacts
Pricing Worksheet
Conflict Checking
Y
N
Price strategy
N/A
N/A
N/A
Pre-dependency
reclsdly(RMS)
storeadd(RMS), ItemReclassBatch
NewItemLocBatch
NewItemLocBatch
LocationMoveBatch
salstage (RMS)
RPMtoORPOSPublishBatch.sh
N/A
N/A
N/A
N/A
storeadd (RMS)
wfcostcalc (RMS)
RPMtoORPOSPublishExport.sh
RegularPriceChangePublishBatch
regularPriceChangePublishExport
ClearancePriceChangePublishBatch
ClearancePriceChangePublishExport
PromotionPriceChangePublishBatch
PromotionPriceChangePublishExport
PriceChangeAutoApproveResultsPurgeBatch
PriceChangePurgeBatch
PriceChangePurgeWorkspaceBatch
PromotionPurgeBatch
PurgeExpiredExecutedOrApprovedClearancesBatch
PurgeUnusedAndAbandonedClearancesBatch
PurgeLocationMovesBatch
Regular Price Changes
Regular Price Changes
Clearances
Clearances
Promotions
Promotions
Purge
Purge
Purge
Purge
Purge
Purge
Purge
Y
Y
N
Y
N
Y
N
N
N
N
N
N
N
N
Location
Price event (item/loc)
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
daily
ksh RPMtoORPOSPublishBatch.sh <userid/passwd@sid > <log path> <error path>
N/A
RegularPriceChangePublishExport
daily
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
daily/ad hoc
N
N
N
N
N
N
N
N
N
N
N
N
N
N
ksh RPMtoORPOSPublishExport.sh <userid/passwd@sid > <Numberof slots> <logpath> <error path> <Export path>
regularPriceChangePublishBatch.sh rpm-app-userid password
regularPriceChangePublishExport.sh rpm-db-userid/pwd@database [export-path]
clearancePriceChangePublishBatch.sh rpm-app-userid password
clearancePriceChangePublishExport.sh rpm-db-userid/pwd@database [export-path]
promotionPriceChangePublishBatch.sh rpm-app-userid password
promotionPriceChangePublishExport.sh rpm-db-userid/pwd@database [export-path]
priceChangeAutoApproveResultsPurgeBatch.sh rpm-app-userid password
priceChangePurgeBatch.sh rpm-app-userid password
priceChangePurgeWorkspaceBatch.sh rpm-app-userid password
promotionPurgeBatch.sh rpm-app-userid password
purgeExpiredExecutedOrApprovedClearancesBatch.sh rpm-app-userid password
purgeUnusedAndAbandonedClearancesBatch.sh rpm-app-userid password
purgeLocationMovesBatch.sh rpm-app-userid password
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
ZoneFutureRetailPurgeBatch
ItemLocDeleteBatch
priceChangeAreaDifferentialBatch
InjectorPriceEventBatch
Purge
Purge
Price Change
N
N
Y
Y
N/A
N/A
N/A
Item/Location
Program Name
Functional Area
Threaded
Driver
AutoMatch
BatchPurge
ComplexDealUpload
DiscrepancyPurge
DisputedCreditMemoRollup
EdiInvoiceUpload
EdiInvoiceDownload
FixedDealUpload
ReasonCodeActionRollup
ReceiptWriteoff
Invoice Matching (ReIM)

Y
N
Y
N
N
Y
N
Y
N
N
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
ad hoc
ad hoc
ad hoc
ad hoc
N
N
N
N
zoneFutureRetailPurgeBatch.sh rpm-app-userid password

itemLocDeleteBatch.sh rpm-app-userid password
priceChangeAreaDifferentialBatch rpm-app-userid password
injectorPriceEventBatch.sh rpm-app-userid password [status=<status>] [event_type=<event_type>]
Post-dependency
ResolutionPosting
N/A
AutoMatch
N/A
ResolutionPosting
AutoMatch
N/A
AutoMatch
N/A
ResolutionPosting
Timing
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
R
R
R
R
R
R
R
R
R
R
AutoMatch userid/passwd
BatchPurge userid/passwd
ComplexDealUpload userid/passwd BlockSize PartitionNo
DiscrepancyPurge userid/passwd
DisputedCreditMemoRollup userid/passwd
EdiInvoiceUpload userid/passwd "EDI input file with path" EDI reject file with path
EdiInvoiceDownload userid/passwd
FixedDealUpload userid/passwd BlockSize PartitionNo
ReasonCodeActionRollup userid/passwd
ReceiptWriteoff userid/passwd
daily
ReceiverAdjustment userid/passwd
N/A
AutoMatch
daily
monthly
R
R
ResolutionPosting userid/passwd
TermsRankingService userid/passwd
Post-dependency
N/A
Timing
daily
N

N/A
Refer to RPAS Operations guide

daily
daily
N
N
N/A
N/A

daily
daily
N
N
N/A
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A

daily
daily
N
N
N/A
N/A
daily
N/A

daily
daily
N
N
N/A
rmsl_rpas_forecast.ksh daily or weekly
daily
rmsl_rpas_update_retal_date.ksh CLOSED_ORDER or RECEIVED_QTY
Post-dependency
Refer to RDW operations guide
Timing
daily
daily
daily
daily
daily
daily
N
N
N
N
N
N

N/A
N/A
N/A
N/A
N/A
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A

daily
daily
N
N
N/A
N/A

daily
daily
N
N
N/A
N/A
daily
N/A
daily
N/A
daily
N/A
daily
N/A

daily
daily
N
N
N/A
N/A
ReIM Dependency and Scheduling Details

Phase
Pre-dependency
6
0
5
1
6
5
7
5
6
6
TermsRankingService
N/A
vendinvc(RMS), vendinvf(RMS)
N/A
edidlinv(RMS)
ResolutionPosting
vendinvc(RMS), vendinvf(RMS)
AutoMatch
AutoMatch
EdiInvoiceUpload
ReasonCodeActionRollup,
N/A
ReceiverAdjustment
N/A
ResolutionPosting
TermsRankingService

N
N
N/A
N/A
6
6
RMS to RPAS RETL Extracts Dependency and Scheduling

Details (EXTRACTS_FOR_RPAS)
Program Name
pre_rmse_rpas.ksh
Functional Area
Planning/Forecast System Interface
Threaded
N
Driver
N/A
Phase
N/A
rmse_rpas.ksh
rmse_rpas_attributes.ksh

N
N
N/A
N/A
N/A
N/A
rmse_rpas_daily_sales.ksh
rmse_rpas_domain.ksh

N
N
N/A
N/A
N/A
N/A
rmse_rpas_item_master.ksh
N/A
N/A
rmse_rpas_merchhier.ksh
N/A
N/A
rmse_rpas_orghier.ksh
N/A
N/A
Pre-dependency
N/A. This is a pre setup script
pre_rmse_rpas.ksh. (This is the launch script to
run the extracts)
pre_rmse_rpas.ksh
saldly
pre_rmse_rpas.ksh
pre_rmse_rpas.ksh
sitmain
reclsdly
dlyprg
reclsdly
dlyprg
dlyprg
pre_rmse_rpas.ksh
stkdly
rmse_rpas_stock_on_hand.ksh
N/A
N/A
rmse_rpas_store.ksh
rmse_rpas_suppliers.ksh

N
N
N/A
N/A
N/A
N/A
rmse_rpas_weekly_sales.ksh
N/A
N/A
rmse_rpas_wh.ksh
rmsl_rpas_forecast.ksh

N
N
N/A
N/A
N/A
N/A
rmsl_rpas_update_retl_date.ksh
N/A
N/A
Dimension source:
Program Name
cdedtlex.ksh
cmptrex.ksh
cmptrlmex.ksh
cmptrlocex.ksh
crncycdex.ksh
emplyex.ksh
Functional Area
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
Threaded
N
N
N
N
N
N
pre_rmse_rpas.ksh
storeadd
dlyprg
pre_rmse_rpas.ksh
hstwkupd
salweek
whadd
dlyprg
pre_rmse_rpas.ksh
After all RMS/Planning System Integration RETL
scripts are run
RMS to RDW RETL Extracts Dependency and Scheduling

Details (EXTRACTS_FOR_RDW)
Driver
N/A
N/A
N/A
N/A
N/A
N/A
Phase
N/A
N/A
N/A
N/A
N/A
N/A
orgaraex.ksh
RDW interface
N/A
N/A
orgchanex.ksh
RDW interface
N/A
N/A
orgchnex.ksh
RDW interface
N/A
N/A
orgdisex.ksh
RDW interface
N/A
N/A
orgllmex.ksh
RDW interface
N/A
N/A
orglocex.ksh
RDW interface
N/A
N/A
orglolex.ksh
RDW interface
N/A
N/A
orgltmex.ksh
RDW interface
N/A
N/A
orgltrex.ksh
RDW interface
N/A
N/A
orgrgnex.ksh
phasex.ksh
RDW interface
RDW interface
N
N
N/A
N/A
N/A
N/A
prdclsex.ksh
prdcmpex.ksh
RDW interface
RDW interface
N
N
N/A
N/A
N/A
N/A
prddepex.ksh
RDW interface
N/A
N/A
prddiffex.ksh
RDW interface
N/A
N/A
prddivex.ksh
RDW interface
N/A
N/A
prddtypex.ksh
RDW interface
N/A
N/A
prdgrpex.ksh
prdislex.ksh
RDW interface
RDW interface
N
N
N/A
N/A
N/A
N/A
Pre-dependency
A, B
A, B
A, B
A, B
A, B
A, B
A, B, storeadd (RMS), dlyprg (RMS),
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
lclrbld (RMS)
A, B
A, B, cremhierdly (RMS), reclsdly (RMS),
dlyprg (RMS)
A,B
dlyprg (RMS)
dlyprg (RMS)
dlyprg (RMS)
dlyprg (RMS)
dlyprg (RMS)
A, B
prditmex.ksh
RDW interface
N/A
N/A
prditmlex.ksh
RDW interface
N/A
N/A
prditmlmex.ksh
prditmltmex.ksh
prditmsmex.ksh
RDW interface
RDW interface
RDW interface
N
N
N
N/A
N/A
N/A
N/A
N/A
N/A
prdpimex.ksh
RDW interface
N/A
N/A
prdsbcex.ksh
RDW interface
N/A
N/A
prdudaex.ksh
regngrpex.ksh
regnmtxex.ksh
rsnex.ksh
seasnex.ksh
subtrantypex.ksh
supctrex.ksh
supsupex.ksh
suptrmex.ksh
suptrtex.ksh
tndrtypex.ksh
ttltypex.ksh
wfcustex.ksh
wfcustgrpex.ksh
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Fact source:
Program Name
cmptrprcildex.ksh
cstisldex.ksh
exchngratex.ksh
invildex.ksh
ivaildex.ksh
ivrcpildex.ksh
ivrildex.ksh
ivtildex.ksh
ivuildex.ksh
lptotcldex.ksh
lptotldex.ksh
ncstuildex.ksh
post_dwi_temp.ksh
prcildex.ksh
Functional Area
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
Threaded
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Driver
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
pre_dwi_extract.ksh
pre_dwi_temp.ksh
rplcildex.ksh
RDW interface
RDW interface
RDW interface
N
N
N
N/A
N/A
N/A
N/A
N/A
N/A
savidex.ksh
scmialdex.ksh
scmioldex.ksh
scrqtldex.ksh
scrtlldex.ksh
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
N
N
N
N
N
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Phase
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A

dlyprg (RMS)
dlyprg (RMS)
dlyprg (RMS)
A, B
A, B
dlyprg (RMS)
dlyprg (RMS)
dlyprg (RMS)
A, B
A, B
A, B
A, B
A, B
A, B, cntrmain (RMS)
A,B
A, B
A, B
A, B
daily
N/A
daily
N/A

daily
daily
daily
N
N
N
N/A
N/A
N/A
daily
N/A
daily
N/A

daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Pre-dependency
B
C
B
C, salstage (RMS), mrt (RMS), ordrev (RMS)
C, salstage (RMS), mrt (RMS)
C
C, saexprdw (ReSA), resa2rdw
C, costcalc (RMS)
All extract batches
N/A
Post-dependency
Timing
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
N
N
N
Y
N
N
N
N
N
N
N
N
N
N

cmptrprcildex.ksh output_file_path/output_file_name
cstisldex.ksh output_file_path/output_file_name
exchngratex.ksh output_file_path/output_file_name
invildex.ksh output_file_path/output_file_name
ivaildex.ksh output_file_path/output_file_name
ivrcpildex.ksh output_file_path/output_file_name
ivrildex.ksh output_file_path/output_file_name
ivtildex.ksh output_file_path/output_file_name
ivuildex.ksh output_file_path/output_file_name
lptotcldex.ksh output_file_path/output_file_name
lptotldex.ksh output_file_path/output_file_name
ncstuildex.ksh output_file_path/output_file_name
N/A
prcildex.ksh output_file_path/output_file_name
salmth(RMS). Also refer to RDW operations guide

daily
daily
daily
N
N
N
N/A
N/A
rplcildex.ksh output_file_path/output_file_name

daily
daily
daily
daily
daily
N
N
N
N
Y
savidex.ksh output_file_path/output_file_name
scmialdex.ksh output_file_path/output_file_name
scmioldex.ksh output_file_path/output_file_name
scrqtldex.ksh output_file_path/output_file_name
scrtlldex.ksh output_file_path/output_file_name
daily
sctidex.ksh output_file_path/output_file_name

daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
N
Y
N
N
N
N
N
N
N
n
n
sfcilwex.ksh output_file_path/output_file_name
slsildmex.ksh output_file_path/output_file_name
slsmkdnildex.ksh output_file_path/output_file_name
stlblmthex.ksh output_file_path/output_file_name
stlblwex.ksh output_file_path/output_file_name
ttldmex.ksh output_file_path/output_file_name
vchreschdex.ksh output_file_path/output_file_name
vchrmoveldsgex.ksh output_file_path/output_file_name
vchroutlwex.ksh output_file_path/output_file_name
wfslsildex.ksh output_file_path/output_file_name
wfslsmkdnildex.ksh output_file_path/output_file_name
sctidex.ksh
RDW interface
N/A
N/A
A
B
C, salstage (RMS)
C, cntrprss (RMS), ediupavl (RMS),
rplapprv (RMS)
C, salstage (RMS)
C, salstage (RMS)
C, salstage (RMS)
C, salstage (RMS)
C, rplapprv (RMS), cntrprss (RMS), rplbld (RMS),
cntrmain (RMS),
sfcilwex.ksh
slsildmex.ksh
slsmkdnildex.ksh
stlblmthex.ksh
stlblwex.ksh
ttldmex.ksh
vchreschdex.ksh
vchrmoveldsgex.ksh
vchroutlwex.ksh
wfslsildex.ksh
wfslsmkdnildex.ksh
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
RDW interface
N
N
N
N
N
N
N
N
N
N
N
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
B, rmsl_rpas_forecast.ksh (RMS to RPAS extract)

C, salstage (RMS)
C, salmth (RMS)
C, salweek (RMS)
B, savouch (ReSA)
B, savouch (ReSA)
B, savouch (ReSA)
C, salstage (RMS)
C, salstage (RMS)
Notes:
A is a set of batch processes on the RDW system.
A consists of the following RDW batch modules:
factopendm.ksh
medfactopendm.ksh
factclosedm.ksh
mt_prime.ksh
B is pre_dwi_extract.ksh DWI batch process.
C is pre_dwi_temp.ksh DWI batch process.
Integrated Merchandising Batch Schedule

RMS, ReIM, RTM
Phase 0
Phase 1
Phase 3
Phase 2
Phase 4
Date Set
dealupld
sastdycr
saexprms (ReSA)
ediupavl
posupld
post
sccext
post
pre *
hstbld (rebuild all)
dtesys
ediupack
BatchPurge(ReIM)
reclsdly
post
orddscnt
Ad Hoc Batch
stkvar
post
ibexpl
ditinsrt
pre
precostcalc
costcalc
pre
rplatupd
hstbldmth
post
post
rilmaint
post
repladj
cntrordb
post
reqext
post
rpl_pre
rplext
post
pre
ibcalc
rplbld
supcnstr
cntrprss
pre
edidlprd
post
edidlord
hstbld_diff
hstbldmth_dif
post
stkschedxpld
lifstkup
ordrev
discotbapply
cntrmain
vatdlxpl
post
ediupadd
salins
post
cremhierdly
posgldld
dlyprg
pre
ociroq
pre
rplsplit
pre
rplapprv
whstrasg
post
edidlinv(IM)
auditprg
stkupld
auditsys
ReceiverAdjustment (ReIM) *
pre
Note: The prepost pre batch cycle should be run before
DiscrepancyPurge(ReIM)
the batch cycle starts to turn off security.
* Running of ReceiverAdjustment (ReIM) should
wfcostcalc
post
ordupd
hstwkupd
(weekly)
invclshp (IM) *
The prepost post batch cycle should be run after the
should correspond to the client running their own
entire batch cycle is finished to turn security back on.
programs to check for receiver unit adjustments

(RUA) and receiver cost adjustments (RCA).
cednld(RTM)
hstmthupd
lcmt730(perl) lcupld
otbdnld
ccprg
otbdlsal
dummyctn
otbdlord
tamperctn
lcadnld
lcmt700 (perl)
edidlcon
lcmdnld
lcmt707(perl)
(sqlldr)
(sqlldr)
wasteadj
stkxpld
dfrtbld
(sqlldr)
edidladd
pre
stkupd
post
ediprg
lcmt798(perl) lcup798
mrt
mrtrtv
pre
post
ftmednld
post
genpreiss
fcstrprg
post
gcupld
PriceEventExecutionBatch(RPM)
vrplbld
poscdnld
tifposdn
mrtupd
distropcpub
txrposdn
post
txrtupld
fcstrbld
post
fcstrbld_sbc
hstprg
* Invoice Matching job in RMS
pre
salstage
gradupld
saldly
stkdly
pre
vendinvc*
post
pre
pre
vendinvf*
post
salapnd
salweek **
post
salmth
onordext
onictext
onorddnld
hstprg_diff
soutdnld
cmpupld
stlgdnld
invaprg
nwpyearend
storeadd
rpmmovavg
fifgldn1(FIF)
fifgldn2(FIF)
post
likestore
lclrbld
sitmain
post
post
fifgldn3(FIF)
mrtprg
saleoh
nwppurge
ordprg
invprg(IM)
ordautcl
otbprg
dealcls
dealex
otbupfwd
pre
pre
dealact
dealinc
pre
dealfct
pre
dealday
post
otbupld
dealfinc
posdnld
post
rplprg
supmth
post
rplprg_month
rtvprg
salprg
* Run after salstage for daily processing, before salweek for weekly processing, and before salmth for monthly processing.
schedprg
** salweek is also dependent on dealfct and dealinc.
ediupcat
prepost dealact_nor pre, prepost dealact_po pre, and prepost dealact_sales pre
stkprg
post
stlgdnld**
salmaint
Phase 5 (ReIM)
Phase 6 (ReIM)
Phase 7 (ReIM)
tcktdnld
tranupld(RTM)
EdiUpload *
EdiDownload
ComplexDealUpload **
AutoMatchService
ReasonCodeActionRollupService
FixedDealUpload **
DisputedCreditMemoResolutionRollupServResolutionPostingService
ReceiptWriteOffService
tsfclose
tsfprg
whadd
post
cmpprg
dealprg
* Runs after edidlinv has generated an EDI file

.
Can also run ad hoc but before phase6.
** Runs after vendinvc, vendinvf.
docclose
pre
wfordupld.ksh
elccostcalc
post
wfordcls
wfordprg
wfrtnprg
Hts240_to_2
400 (perl),
Ushts2rms
(perl), pre
htsupld(RTM)
prepost
* Only required before hstbld rebuild processing.
** Ad hoc running of stlgdnld is meant for historic
downloads. See phase 4 for weekly stlgdnld runs.
ReSA
Sales Audit
(sastdycr)
sagetref
sacrypt***
saprepost
pre
saimptlog
saprepost
post
(sqlldr)
savouch
saimptlogfin saimpadj *
satotals
sarules
(Forms
Auditing)
sapreexp
saexprms **
saprepost
post
saexpim **
saexprdw **
resa2rdw(perl)
saprepost
pre
sapurge
saprepost
post
saexpach **
saexpuar **
saexpgl **
saescheat
* Only if there are total adjustments from external systems
Forms Auditing is an online process used to correct any errors found
** Only if the external system is used
during the loading of the data, totaling, and rules checking.
*** Only if RTLOG file from POS is encrypted.

Only if vouchers are being tracked, runs monthly
Not required if saimptlogi is substituted for saimptlog
RPM
Ad Hoc Batch
Price Management
InjectorPriceEventBatch
reclsdly(RMS) ItemReclassBatch
NewItemLocBatch
LocationMoveScheduleBatch
LocationMoveBatch
PriceEventExecutionBatch PriceEventExecutionRMSBatch
salstage(RMS) storeadd(RMS)
MerchExtractKickOffBatch PurgeBulkConflictCheckArtifacts
PriceChangeAutoApproveResultsPurgeBatch
PriceChangePurgeBatch
PriceChangePurgeWorkspaceBatch
PromotionPurgeBatchbatch
PurgeExpiredExecutedOrApprovedClearancesBatch
PurgeUnusedAndAbandonedClearancesBatch
RPMtoORPOSPublishExport.sh
RegularPriceChangePublishExport
PurgeLocationMovesBatch
ZoneFutureRetailPurgeBatch
ItemLocDeleteBatch
priceChangeAreaDifferentialBatch
4
Interface Diagrams for RMS and RPAS
Because RMS is the retailers central merchandising transactional processing system, it is
the principle source of the foundation data needed in some of the Oracle Retail suite of
products. RMS provides foundation data to RPAS, and RPAS provides planning data to
RMS.
This chapter presents flow diagrams for data processing from sources. The source
systems program or output file is illustrated, along with the program or process that
interfaces with the source. After initial interface processing of the source, the diagrams
illustrate the flow of the data.
Before setting up a program schedule, familiarize yourself with the functional and
technical constraints associated with each program. Refer to the Retail Merchandising
System Operations Guide for more information about these interface programs.
Batch Schedule 19
RMS Pre/Post Extract Diagrams
20
RMS Foundation Data Extract Diagrams
RMS
EXT
1
sitmain
(RMS)
reclsdly
(RMS)
dlyprg
(RMS)
rmse_rpas_merchhier.
ksh
rmse_rpas_item_
master.ksh
rmse_rpas_domain.
ksh
rmse_rpas_supplier.
ksh
rmse_rpas_attributes.
ksh
rmse_rpas_
merchhier.dat
rmse_rpas_item_
master.dat
rmse_rpas_
domain.dat
rmse_rpas_
supplier.dat
rmse_rpas_attributes.
dat
TO
RPAS
TO
RPAS
TO
RPAS
TO
RPAS
TO
RPAS
21
Note: The rmse_rpas_

attributes.ksh flow is applicable
only if issues are active.
22
RMS Fact Data Extract Diagrams
23
RPAS-RMS Fact Load Diagram

RPAS
w?demand.??
d?demand.??
? can represent the following:
i (for issues)
s (for stores)
TO
RMS
?? represents domain 01-99.
rmsl_rpas_forecast.ksh
24
5
Interface Diagrams for RMS and RDW
RMS works in conjunction with the Oracle Retail Extract Transform and Load (RETL)
framework. RETL provides high-performance processing to extract data from Oracle
Retail applications for use in data warehouses. The architecture allows database batch
processes to take advantage of parallel processing capabilities.
This chapter presents flow diagrams for the RETL extraction RMS programs. The source
systems program or output file is illustrated, along with the program or process that
interfaces with the source. Note that the data flows are organized according to the logic
(dimension data and table data) of Oracle Retail Data Warehouse (RDW), but you can use
the data to suit your business needs.
For detailed information about dimensions and facts, see the Retail Data Warehouse
Operations Guide.
For summary information about the configuration, architecture, and features of RETL
programs utilized in RMS/ReSA extractions, see the Oracle Retail Management System
Operations Guide Volume 3Backend Configuration and Operations. For more
information about the RETL tool, see the current RETL Programmers Guide.
Legend
A
Signifies the completion of RDW maintenance jobs
Signifies the completion of pre-batch

maintenance jobs that set system variables
Signifies the completion of pre-batch maintenance

jobs that create temporary tables
RMS or ReSA module on which RETL extract modules
are dependent
Batch Schedule 25
26
27
D im ension D ataflow s
O rga niza tion

B
storeadd
(R M S )
dlyprg
(R M S )
orgchnex.ksh
(D W I)
orgaraex.ksh
(D W I)
orgrgnex .ksh
(D W I)
orgdisex.ksh
(D W I)
orglocex.ksh
(D W I)
orgchndm .txt
orgaradm .txt
orgrgndm .txt
orgdisdm .txt
orglocdm .txt
lclrbld .pc
orgltm ex.ksh
(D W I)
orgltrex.ksh
(D W I)
orglolex .ksh
(D W I)
orgllm ex.ksh
(D W I)
orgchanex.ksh
(D W I)
orgltm dm .txt
orgltrdm .txt
orgloldm .txt
orgllm dm .txt
orgchandm .txt
cntrm ain.pc
S upp lier D im e nsion
Ite m -S up plier-Locatio n
M a trix D im e nsio n
prdislex .ksh
(D W I)
supsupex.ksh
(D W I)
suptrtex.ksh
(D W I)
suptrm ex.ksh
(D W I)
supctrex .ksh
(D W I)
prdisldm .txt
supsupdm .txt
suptrm dm .txt
suptrtdm .txt
28
supctrdm .txt
Dimension Dataflows
Sub-transaction
Type Dimension
Currency Code
Dimension
ReSA Total Type

Dimension
crncycdex.ksh
(DWI)
subtrantypex.ksh
(DWI)
ttltypex.ksh
(DWI)
crncycddm.txt
subtrantypedm.txt
ttltypdm.txt
Code Detail
Dimension
B
Item-Location Trait
Matrix Dimension
cdedtlex.ksh
prditmltmex.ksh
(DWI)
Employee
Dimension
B
Competitor
Dimension
prditmltmdm.txt
emplyex.ksh
(DWI)
emplydm.txt
cmptrex.ksh
(DWI)
cmptrlocex.ksh
(DWI)
cmptrlmex.ksh
(DWI)
29
cdedtldm.txt
Tender Type
Dimension
Dimension Dataflows
Product Season
Dimension
seasnex.ksh
(DWI)
phasex.ksh
(DW I)
prditmsmex.ksh
seasndm .txt
phasdm.txt
prditmsmdm.txt
Inventory
P osition
tndrtypex.ksh
(DWI)
rsnex.ksh
(DW I)
regngrpex.ksh
(DW I)
regnmtxex.ksh
(DWI)
rsndm .txt
regngrpdm.txt
regnmtxdm.txt
salstage.pc
(R M S )
Inventory
T ransfers
ivtildex .ksh
(D W I)
Regionality Dimension
lndrtypedm.txt
F a ct D ataflow s
ordrev.p c
(R M S )
Reason
Dimension
Inventory
A djustm ents
ivaildex .ksh
(D W I)
m rt.pc
Inventory
R eceipts
ivrcpildex .ksh
(D W I)
U navailable
Inventory
ivuildex .ksh
(D W I)
invildex .ksh
(D W I)
ivtilddm .txt
ivailddm .txt
invilddm .txt
salstage.pc
(R M S )
M arkdow ns
C
slsm kdn ildex .ksh
(D W I)
30
ivrcpilddm .txt
ivuilddm .txt
Fact Dataflows
Cost
Competitor
Pricing
RPM Pricing
C
B
cstisldex.ksh
(DWI)
prcildex.ksh
(DWI)
cmptrprcildex.ksh
(DWI)
prcilddm.txt
cmptrprcilddm.txt
sccext.pc
(RMS)
cstislddm.txt
Stock Ledger
C
salweek.pc
(RMS)
stlblmth.ksh
(DWI)
stlblwex.ksh
(DWI)
Stlblmthdm.txt
stlblwdm.txt
Note:
Run stock ledger fact
loads once weekly.
31
salmth.pc
(RMS)
Fact Dataflows
Supplier Contract
Supplier Availability
cntrprss.pc
(RMS)
ediupavl.pc
(RMS)
cntrprss.pc
(RMS)
rplapprv.pc
(RMS)
rplbld.pc
(RMS)
rplprg.pc
(RMS)
rplapprv.pc
(RMS)
C
C
sctidex.ksh
(DWI)
savidex.ksh
(DWI)
Return to Vendor
sctiddm.txt
ivrildex.ksh
(DWI)
ivrilddm.txt
Net Cost
costcalc.pc
(RMS)
C
ncstuildex.ksh
(DWI)
ncstuilddm .txt
32
cntrmain.pc
(RMS)
hsupld.pc
(RMS)
F a ct D a ta flo w s
E xch a n g e R a te s
S a le s F o re ca sts
B
fcslu pld.p c
(R M S )
exch ng ratex.ksh
(D W I)
sfcilw ex.ksh
(D W I)
e xchn grate dm .txt
sfcilw dm .txt
33
N ote:
R un sales forecast fact loads
once w eekly .
34
Fact Dataflows
saexprdw.pc
(ReSA)
RDWC
file
Loss Prevention
Totals
Loss Prevention
Totals
resa2rdw
(ReSA Perl script)
(User-Defined Totals)
(Cashier Over or Short)
RDWC
file
RDWS
file
resa2rdw
(ReSA Perl script)
C
RDWS
file
lptotcldex.ksh
(DWI)
C
lptotclddm.txt
lptotldex.ksh
(DWI)
lptotlddm.txt
savouch.pc
(ReSA)
savouch.pc
(ReSA)
Voucher
Movement
vchrmoveldsgex.ksh
(DWI)
vchroutlwex.ksh
(DWI)
vchrmoveldsg.txt
vchroutlwdm.txt
savouch.pc
(ReSA)
Outstanding
Vouchers
Escheated
Vouchers
vchreschdex.ksh
(DWI)
vchreschddm.txt
35
Fact Dataflows
Supplier Compliance
salstage.pc
(RMS)
Delivery
Timeliness
scrtlldex.ksh
(DWI)
scrqtldex.ksh
(DWI)
scrtllddm.txt
scrqtlddm.txt
Delivery
Quantities
scmialdex.ksh
(DWI)
scmioldex.ksh
(DWI)
scmialddm.txt
scmiolddm.txt
Missed
Shipments
36
Missed
Purchase
Orders
6
Interface Diagram for RPM and RDW
This following program flow diagram shows the RETL extraction program that extracts
the Promotion dimension from RPM through the Data Warehouse Interface (DWI). The
diagram shows the output files and the scripts that interface with the source. Note that
the outputs are based on the logic (dimension data and table data) of Oracle Retail Data
Warehouse (RDW), but you can use the data to suit your business needs.
Operations Guide.
See the Retail Merchandising System Operations Guide Volume 1Batch Overviews and
Designs for more information about the modules shown in the following diagram.
Legend
A
Signifies the completion of pre-batch maintenance jobs
Signifies the completion of pre-DWI maintenance

module to set system variables
Program Flow Diagram

Promotion Dimension
A
prmevtex.ksh
(DWI)
prmhdrex.ksh
(DWI)
prmevtdm.txt
prmhdrdm.txt
prmdtlex.ksh
(DWI)
prmdtldm.txt
Batch Schedule 37
Interface Diagram for RPM and RDW
7
Interface Diagram for ReIM and RDW
This following program flow diagram shows the RETL extraction program that extracts
the Promotion dimension from ReIM through the Data Warehouse Interface (DWI). The
diagram shows the output files and the scripts that interface with the source. Note that
the outputs are based on the logic (dimension data and table data) of Oracle Retail Data
Warehouse (RDW), but you can use the data to suit your business needs.
Operations Guide.
See the Retail Merchandising System Operations Guide Volume 1Batch Overviews and
Designs for more information about the modules shown in the following diagram.
Legend
RMS module on which RETL extract
modules are dependent
Signifies the completion of pre-DWI maintenance

module to create currency conversion tables
Program Flow Diagram
Batch Schedule 39
Interface Diagram for ReIM and RDW

MRCH Batch Schedule

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MRCH Batch Schedule

Diunggah oleh

Hak Cipta:

Format Tersedia

Oracle Retail Merchandising

Oracle Retail Merchandising Batch Schedule, Release 13.0

Copyright 2008, Oracle. All rights reserved.

Value-Added Reseller (VAR) Language

Oracle Retail Merchandising System (RMS)

Oracle Retail Invoice Matching (ReIM)

Oracle Retail Price Management (RPM)

Oracle Retail Sales Audit (ReSA)

Oracle Retail Trade Management (RTM)

Oracle Retail Allocation

application, it is not represented in this batch schedule

Oracle Retail Merchandising Implementation Guide

Oracle Retail Merchandising System Operations Guide

Oracle Retail Price Management Operations Guide

Oracle Retail Invoice Matching Operations Guide

Oracle Retail Data Warehouse Operations Guide

Oracle Retail Predictive Application Server documentation

Oracle Retail Demand Forecasting documentation

Product version and program/module name

Functional and technical description of the problem (include business impact)

Detailed step-by-step instructions to re-create

Exact error message received

Screen shots of each step you take

Review Patch Documentation

Oracle Retail Documentation on the Oracle Technology Network

important, but not necessarily part of the procedure.

A hyperlink appears like this.

To process large volumes of transaction data

To interface with external systems

To perform internal maintenance

Types of Batch Programs

Functional maintenance programs process data specific to a functional area. For

Batch Schedule and Phases

2 Oracle Retail Merchandising

Merchandising Batch Schedule

Merchandising Batch Schedule

Oracle Retail Merchandising System (RMS)

Oracle Retail Trade Management (RTM)

Oracle Retail Sales Audit (ReSA)

Oracle Retail Invoice Matching (ReIM)

Oracle Retail Price Management (RPM)

application, it is not represented in this batch schedule

Name of the program or script

Functional area of the application for which the batch program

Whether the program is threaded (Y/N)

Programs that must be completed before the program can be

Programs that must be run after the program completes

How often the program is run (for example, daily, weekly,

Whether the program uses restart/recovery (R=Yes, N=No)

Run Parameters for Program

Command syntax to run the program

dealinc, dealfinc, prepost dealday pre

prepost dealday post, salmnth

The program list is grouped in the following order:

RMS, RTM, and ReSA programs

RMS extracts for Retail Predictive Application Server (RPAS)

RMS extracts for Retail Data Warehouse (RDW)

4 Oracle Retail Merchandising

Batch Schedule Diagram

Batch Schedule Diagram

RMS, RTM, ReIM

RMS, ReIM, RTM Section

The first phase performs essential table maintenance including:

Updates to currency exchange rates