Aip 1312 Impg

Oracle® Retail Advanced Inventory Planning
Implementation Guide
Release 13.1.2
March 2010
Oracle® Advanced Inventory Planning Implementation Guide, Release 13.1.2
Copyright © 2010, Oracle. All rights reserved.

Primary Author: Melissa Artley
This software and related documentation are provided under a license agreement containing
restrictions on use and disclosure and are protected by intellectual property laws. Except as
expressly permitted in your license agreement or allowed by law, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or
display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be
error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. 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 agency-
specific supplemental regulations. As such, the use, duplication, disclosure, modification, and
adaptation shall be subject to the restrictions and license terms set forth in the applicable
Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December
2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It
is not developed or intended for use in any inherently dangerous applications, including
applications which may create a risk of personal injury. If you use this software in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy,
and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and
services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages
incurred due to your access to or use of third-party content, products, or services.
Licensing Note: This media pack includes a Restricted Use license for Oracle Retail Predictive
Application Server (RPAS) - Enterprise Engine to support Oracle® Retail Advanced Inventory
Planning only.
Value-Added Reseller (VAR) Language
Oracle Retail VAR Applications

The following restrictions and provisions only apply to the programs referred to in this section and
licensed to you. You acknowledge that the programs may contain third party software (VAR
applications) licensed to Oracle. Depending upon your product and its version number, the VAR
applications may include:
(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, Oracle Retail Demand Forecasting, Oracle Retail Regular Price Optimization, Oracle
Retail Size Profile Optimization, Oracle Retail Replenishment Optimization 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 Mobile Store Inventory
Management.
(v) the software component known as Crystal Enterprise Professional and/or Crystal Reports
Professional licensed by SAP 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 DataBeacon™ developed and licensed by Cognos
Incorporated of Ottawa, Ontario, Canada, to Oracle and imbedded in the Oracle Retail Value Chain
Collaboration application.
You acknowledge and confirm that Oracle grants you use of only the object code of the VAR
Applications. Oracle will not deliver source code to the VAR Applications to you.
Notwithstanding any other term or condition of the agreement and this ordering document, you
shall not cause or permit alteration of any VAR Applications. For purposes of this section,
“alteration” refers to all alterations, translations, upgrades, enhancements, customizations or
modifications of all or any portion of the VAR Applications including all reconfigurations,
reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or
reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You
acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or
confidential information of the VAR Applications for purposes of competitive discovery.
The VAR Applications contain trade secrets of Oracle and Oracle’s licensors and Customer shall
not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or
other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to
replace, with functional equivalent software, any of the VAR Applications in future releases of the
applicable program.
iii
Contents
Send Us Your Comments................................................................................................ xi
Preface ............................................................................................................................ xiii
Audience .............................................................................................................................. xiii
Related Documents............................................................................................................. xiii
Customer Support............................................................................................................... xiv
Review Patch Documentation ........................................................................................... xiv
Oracle Retail Documentation on the Oracle Technology Network.............................. xiv
Conventions......................................................................................................................... xiv
1 Overview ......................................................................................................................... 1
2 Pre-Implementation Considerations ............................................................................ 3
Overview..................................................................................................................................3
3 Building a Production AIP RPAS Domain ................................................................... 7
Introduction .............................................................................................................................7
Hierarchy Data Overview...............................................................................................8
Production AIP RPAS Domain Build Overview .........................................................9
Manipulate the Hierarchy Data, Part One..................................................................10
Run the AIP RPAS Installer..........................................................................................11
Configuring the AIP Solution ......................................................................................12
Insert External System Data into the AIP RPAS Domain.........................................13
Generate Load-Ready AIP Hierarchy Data................................................................14
Create the AIP RPAS Global Domain Configuration XML File ..............................15
Manipulate the Hierarchy Data, Part Two .................................................................16
Build the AIP RPAS Global Domain ...........................................................................17
AIP RPAS Domain Build Completion Summary ......................................................18
Move the RPAS Domain (Optional) ............................................................................19
Configure the RPAS Client to Use the Domain .........................................................19
Post Installation Instructions ...............................................................................................20
4 System Configuration.................................................................................................. 21
Setting Environment Variables ...........................................................................................21
Configuring AIP RPAS Environment Variables........................................................21
Configuring AIP Online Environment Variables ......................................................24
Using the Scheduler to Run AIP Batch Processes.............................................................27
Pre-Critical Path Tasks ..................................................................................................28
Critical Path Tasks .........................................................................................................31
Post Critical Path Tasks.................................................................................................33
Interval Batch Tasks.......................................................................................................35
v
5 AIP Online Configurations .......................................................................................... 39
AIP Online UNIX Environment ..........................................................................................39
config.xml .......................................................................................................................39
Integration Directories ..................................................................................................40
Shared Files.....................................................................................................................40
Importing Configuration Files .....................................................................................41
Export Configuration Files ..................................................................................................42
Oracle Database.....................................................................................................................42
SYSTEM_PARAMETERS..............................................................................................43
RESTART_CONTROL ..................................................................................................48
ORDER_NUMBER.........................................................................................................48
ORDER_PURGE_PERIOD............................................................................................48
ORDER_DEFINITION ..................................................................................................48
ORDER CYCLES ............................................................................................................49
DATA_PURGE_PARAMETERS..................................................................................52
WH_TYPE_INITIAL_PACK_TYPE.............................................................................54
SUPPLIER .......................................................................................................................54
STOCKING_POINT.......................................................................................................54
SHIP_TO_WH_TYPE_SOURCE ..................................................................................54
SHIP_TO_WH_TYPE_DEST ........................................................................................54
ALERT_DEFINITION ...................................................................................................55
ALERT_DEFINITION_DESC.......................................................................................55
ALERT_STATUS_DESC................................................................................................55
AIP Application Server ........................................................................................................56
db.properties ..................................................................................................................56
main.properties ..............................................................................................................57
rcapps.properties ...........................................................................................................59
security.properties .........................................................................................................60
strings_en.properties .....................................................................................................60
Config.properties ..................................................................................................................61
6 AIP RPAS Configurations ........................................................................................... 67
shortfallPriorityMatrix.xml..................................................................................................67
surplusStorePriorityMatrix.xml ..........................................................................................68
Measures ................................................................................................................................70
Modifying Measure Base Intersections Using Configuration Tools ..............................76
Import Configuration Files ..................................................................................................76
Moving Integration Data Source from RMS to a Non-RMS External System .......85
7 AIP Calendar Hierarchy ............................................................................................... 89
AIP Calendar Data – clnd.dat or clnd.csv.dat...................................................................89
Notes on manual construction .....................................................................................90
vi
8 Integration..................................................................................................................... 91
Overview of the Integrated Inventory Planning Suite.....................................................91
Integrated Inventory Planning Suite Data Flow........................................................91
Data Flow Description ..................................................................................................92
9 RMS Integration and Data Mapping ........................................................................... 95
RMS to AIP Data ...................................................................................................................95
Hierarchy Data ...............................................................................................................95
Measure Data..................................................................................................................99
File Formats ..................................................................................................................101
File Format Including Mapping to AIP RPAS Measure Format ...........................107
RMS RETL Extract and RMS-AIP Transformation Overview ......................................112
10 RDF Integration ........................................................................................................ 115
RDF to AIP Data..................................................................................................................115
Measure Data................................................................................................................115
iprdfdtdaltv.txt ....................................................................................................................116
sr0_rdfdtdmsk.txt................................................................................................................117
sr0_rdfdtdcnt.txt..................................................................................................................118
sr0_fcterrlvl1.txt ..................................................................................................................119
sr0_fcterrlvl2.txt ..................................................................................................................121
sr0_frclvl1_[1..n].txt ............................................................................................................122
sr0_frclvl2.txt .......................................................................................................................123
11 External System Integration ................................................................................... 125
External System to AIP Data .............................................................................................125
Hierarchy Data .............................................................................................................125
Measure Data................................................................................................................125
had.txt...................................................................................................................................127
intv.txt...................................................................................................................................128
default_wh.txt......................................................................................................................129
direct_store_format_pack_size.txt ....................................................................................131
direct_store_pack_size.txt..................................................................................................132
dm0_ofseffdt_.txt ................................................................................................................134
dm0_onseffdt_.txt ...............................................................................................................135
dmx_pcktyp.txt ...................................................................................................................136
dmx_pprsts.txt.....................................................................................................................138
dmx_shpto_.txt....................................................................................................................139
ipadrltntsi.txt .......................................................................................................................140
ipadendi.txt..........................................................................................................................141
ipadstai.txt............................................................................................................................143
ipavgrtslsi.txt .......................................................................................................................144
ipcmtmtde.txt ......................................................................................................................145
ipfctwkprfd.txt ....................................................................................................................146
ipfctwkprfe.txt .....................................................................................................................148
vii
iphldbckqtyi.txt ...................................................................................................................150
ipldssi.txt ..............................................................................................................................151
ipodcmti.txt..........................................................................................................................152
iprplstcdi.txt.........................................................................................................................154
iprpltcdi.txt ..........................................................................................................................155
ipslsi.txt ................................................................................................................................156
ipttlhlstki.txt.........................................................................................................................158
ipwhhldcpci.txt ...................................................................................................................159
item_attribute.txt.................................................................................................................160
item_attribute_type.txt.......................................................................................................162
rmse_order_purge.dat........................................................................................................163
sister_store.txt......................................................................................................................164
sister_wh.txt.........................................................................................................................165
sr0_ad_.txt ............................................................................................................................167
sr0_ad_go_.txt......................................................................................................................168
sr0_ad_irt.txt ........................................................................................................................170
sr0_ad_oth.txt ......................................................................................................................171
sr0_ad_rop.txt......................................................................................................................172
sr0_adjsls.txt.........................................................................................................................174
sr0_avgrosld_.txt .................................................................................................................175
sr0_co_.txt ............................................................................................................................176
sr0_dyscsls.txt......................................................................................................................177
sr0_expwrtoff.txt .................................................................................................................179
sr0_hstls_.txt ........................................................................................................................180
sr0_invadj.txt .......................................................................................................................181
sr0_knowndemand.txt........................................................................................................183
sr0_rplcde.txt .......................................................................................................................184
sr0_rplsubcde.txt.................................................................................................................185
sr0_ss_ld_.txt .......................................................................................................................186
sr0_tdgday.txt......................................................................................................................188
sr0_wkbsf_ld.txt ..................................................................................................................189
sr0_wstadj.txt.......................................................................................................................190
srx_poidst.txt .......................................................................................................................191
srx_prdrpr.txt ......................................................................................................................193
store_format_pack_size.txt ................................................................................................194
store_pack_size.txt ..............................................................................................................196
sku_cost.dat .........................................................................................................................197
SKU Cost – Online Load Process ...............................................................................199
sku_weight_volume.dat.....................................................................................................200
SKU Weight and Volume – Online Load Process ...................................................202
viii
12 RO Integration .......................................................................................................... 203
Store Measure Data.............................................................................................................203
STR_MINMAX .............................................................................................................203
STR_DYNAMIC...........................................................................................................205
STR_TIMESUPPLY ......................................................................................................207
STR_HYBRID................................................................................................................209
STR_POISSON..............................................................................................................211
STR_MINSS ..................................................................................................................212
STR_ROUpdate ............................................................................................................214
Warehouse Data Interfaces ................................................................................................215
WH_MINMAX .............................................................................................................216
WH_DYNAMIC...........................................................................................................218
WH_TIMESUPPLY......................................................................................................220
WH_HYBRID ...............................................................................................................222
WH_MINSS ..................................................................................................................224
WH_ROUpdate ............................................................................................................225
13 AIP to RMS Interfaces and Data Mapping ............................................................. 227
RIB Publications ..................................................................................................................227
AIP Message Flow ..............................................................................................................227
Purchase Order Messages..................................................................................................228
XORDERCRE................................................................................................................228
XORDERDTLCRE........................................................................................................228
XORDERMOD..............................................................................................................228
XORDERDTLMOD......................................................................................................228
Transfer Messages...............................................................................................................229
XTSFCRE.......................................................................................................................229
AIP to RMS Data .................................................................................................................229
Messages Layout..........................................................................................................230
Purchase Orders and Transfers Message Flow in AIP ...........................................232
Store – Purchase Orders and Transfers Message Flow...........................................233
Warehouse – Purchase Orders and Transfers Message Flow .......................................235
Data Formats for Creating Order – XORDERCRE ..................................................237
Create Order Layout – XORDERDTLCRE ...............................................................242
Modify Order Header Layout – XORDERMOD .....................................................244
Modify Order Layout – XORDERDTLMOD............................................................248
Create Transfer Layout – XTSFCRE ..........................................................................250
AIP Purchase Order Messages – RMS Load Process ..............................................254
AIP Transfer Messages – RMS Load Process ...........................................................256
XORDER Header – RMS ORDHEAD Mapping ......................................................257
XORDER Detail – ORDSKU & ORDLOC Mapping................................................263
XTSF Header – RMS TSFHEAD Mapping ...............................................................267
XTSF DTL – RMS TSFDETAIL Mapping..................................................................270
ix
14 AIP to External System Interfaces.......................................................................... 273
Overview..............................................................................................................................273
purchase_order.dat.1 ..........................................................................................................273
transfer_order.dat.1 ............................................................................................................275
15 AIP to RO Interfaces ................................................................................................ 279
STR_AIP_DATA..................................................................................................................279
WH_AIP_DATA .................................................................................................................281
16 First Day of AIP ........................................................................................................ 283
Introduction .........................................................................................................................283
Overview..............................................................................................................................283
The First Day of AIP Explained ........................................................................................283
Load Data......................................................................................................................284
Enable Automated Data Maintenance ......................................................................285
The First Day of AIP Execution.........................................................................................287
Step 1: Virtual Date (Vdate)...............................................................................................288
Step Details ...................................................................................................................288
Step Execution ..............................................................................................................288
Step 2: Build the SRP Implementation Parameters Workbook.....................................289
Step Details ...................................................................................................................289
Step Execution ..............................................................................................................289
Step 3: First Day of AIP on RPAS Batch...........................................................................289
Step Details ...................................................................................................................289
Step Execution ..............................................................................................................290
Step 4: First Day of AIP on Oracle Import .......................................................................291
Step Details ...................................................................................................................291
Step Execution ..............................................................................................................292
Step 5: First Day of AIP on Oracle Manual Setup...........................................................292
Step Details ...................................................................................................................292
Step Execution ..............................................................................................................293
Step 6: First Day of AIP on Oracle Automation..............................................................293
Step Details ...................................................................................................................293
Step Execution ..............................................................................................................293
Step 7: First Day of AIP on Oracle Import of Non-critical Alerts.................................293
Step Details ...................................................................................................................293
Step Execution ..............................................................................................................293
Step 8: Manual Setup of AIP..............................................................................................294
Step Details ...................................................................................................................294
Step Execution ..............................................................................................................294
x
Send Us Your Comments
Oracle Retail Advanced Inventory Planning, Implementation Guide, Release 13.1.2
Oracle welcomes customers' comments and suggestions on the quality and usefulness of
this document.
Your feedback is important, and helps us to best meet your needs as a user of our
products. For example:
Are the implementation steps correct and complete?
Did you understand the context of the procedures?
Did you find any errors in the information?
Does the structure of the information help you with your tasks?
Do you need different information or graphics? If so, where, and in what format?
Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us
your name, the name of the company who has licensed our products, the title and part
number of the documentation and the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to

check that you have the latest version of the document and if
any concerns are already addressed.
Send your comments to us using the electronic mail address: retail-doc_us@oracle.com

Please give your name, address, electronic mail address, and telephone number
(optional).
If you need assistance with Oracle software, then please contact your support
representative or Oracle Support Services.
If you require training or instruction in using Oracle software, then please contact your
Oracle local office and inquire about our Oracle University offerings. A list of Oracle
offices is available on our Web site at www.oracle.com.
xi
Preface
The Oracle Retail Advanced Inventory Planning Implementation Guide describes post-
installation tasks that need to be performed in order to bring Advance Inventory
Planning online and ready for production use.
The Implementation Guide includes some or all of the following sections, depending
upon the release:
System configuration settings for the UNIX and AIP environments
Interfaces and data mappings between AIP and other systems
Audience
The Implementation Guide is intended for the AIP integrators and implementation staff,
as well as the retailer’s IT personnel.
The reader should have an in-depth understand the following concepts and applications
in order to perform the processes describes in this document:
UNIX system administration, shell scripts, and job scheduling
Oracle Retail Integration Bus (RIB)
Oracle Retail Predictive Application Server (RPAS)
Oracle Retail Demand Forecasting (RDF)
Oracle databases
Performance constraints based on the retailer’s infrastructure
Technical architecture for AIP
Retailer’s hierarchical (SKU/Store/Day) data
AIP batch processes
Related Documents
For more information, see the following documents in the Oracle Retail Advanced
Inventory Planning Release 13.1.2 documentation set:
Oracle Retail Advanced Inventory Planning Release Notes
Oracle Retail Advanced Inventory Planning Installation Guide
Oracle Retail Advanced Inventory Planning Data Management Online Online Help
Oracle Retail Advanced Inventory Planning Data Management Online User Guide
Oracle Retail Advanced Inventory Planning Order Management Online Help
Oracle Retail Advanced Inventory Planning Store Replenishment Planning User Guide
Oracle Retail Advanced Inventory Planning Warehouse Replenishment Planning User Guide
Oracle Retail Advanced Inventory Planning Operations Guide and Administration Guide
Oracle Retail Advanced Inventory Planning Data Model Volume 1 Oracle Data Model
Oracle Retail Advanced Inventory Planning Data Model Volume 2 Measure Reference Guide
The following documentation may also be needed when implementing AIP:
Oracle Retail Integration Bus (RIB) 13.1.1 documentation, based on type of
deployment
RETL 13.1 documentation
Oracle Retail Predictive Application Server (RPAS) documentation
xiii
Customer Support
To contact Oracle Customer Support, access My Oracle Support at the following URL:
https://support.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

When you install the application for the first time, you install either a base release (for
example, 13.1) or a later patch release (for example, 13.1.2). If you are installing the base
release and additional patch and bundled hot fix releases, read the documentation for all
releases that have occurred since the base release before you begin installation.
Documentation for patch and bundled hot fix releases can contain critical information
related to the base release, as well as information about code changes since the base
release.
Oracle Retail Documentation on the Oracle Technology Network

Documentation is packaged with each Oracle Retail product release. Oracle Retail
product documentation is also available on the following Web site:
http://www.oracle.com/technology/documentation/oracle_retail.html
(Data Model documents are not available through Oracle Technology Network. These
documents are packaged with released code, or you can obtain them through My Oracle
Support.)
Documentation should be available on this Web site within a month after a product
release.
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.”
This is a code sample
It is used to display examples of code
xiv
1
Overview
Once AIP has been installed, you need to configure the system environment variables,
create integration files, and configure the system according to the retailer’s specifications.
This guide provides information on
Implementing the AIP solution.
Customizing AIP for the retailer’s environment and needs.
Integrating AIP with merchandising, forecasting, and other external systems.
For information on compatibility and hardware requirements, refer to the AIP Installation
Guide.
Note: AIP Java/Oracle, AIP on Oracle, and AIP online are

often used interchangeably to refer to those parts of AIP that
access the Oracle relational database. This includes the Data
Management and Order Management GUI components and
a host of UNIX shell scripts and PL/SQL modules.
Overview 1
2
Pre-Implementation Considerations
Overview
When preparing to implement the Advanced Inventory Planning solution, you must
closely explore the retailer’s infrastructure, hierarchy data, and other factors that may
require customizing the AIP environment through the use of configuration files and
settings, custom scripts, and the RPAS Configuration Tool. Prepare your environment
and analyze your retail and data needs thoroughly before implementing AIP.
The following list provides some of the issues that the implementation team may need to
address prior to implementation:
1. Hierarchy Setup
Identify the attributes used by the Product, Location and Time hierarchies, as
well as their sources and update frequency.
Define the dimensions within each of the Hierarchies and determine the default
spreading settings.
Define any Alternate Hierarchies and identify the relationship of the required
Attributes that drive those Alternates.
Define User Defined Hierarchies to be used by planners.
The hierarchy setup mentioned above may vary depending on the extent that the
Configuration Tool will be used by the application.
2. Measure Settings
The following measure settings need to be addressed during implementation, which
can vary depending on the extent that the Configuration Tool will be used by the
application.
Metric/Measure definitions, usage, interaction and calculations.
Default Label to use when building measure labels
Default Data Type
Default NA Value
Default Base Intersection
Default Aggregation Method
Default Spread Method
Default Base State Read / Write Status at the base level
Default Agg State Read / Write Status at aggregated levels
3. Setting Custom Wizards
Determine if any custom wizards are required that don’t exist in the base application.
The use or implementation of wizards can vary depending on the extent that the
Configuration Tool will be used by the application.
4. Workbook Templates, Worksheets, Tabs, Formats
Workbooks can be created or refreshed through batch processing. By doing the
processing in batch at night, the end users are spared from the wait time associated
with each action. The Batch Processing section should outline when each of these
operations will take place.
Pre-Implementation Considerations 3
Overview
For these default auto workbook builds, the layout, formatting, hierarchies, wizard,
tabs, and worksheets must be defined.
Configuring the timing of data loads, refreshes, and purges/deletions of workbooks
must be set.
5. Daily and Weekly Batch Processing and scheduling
Configure the system for the following defaults:
Batch Processes
Week-ending Processes
Day Ending Processes
Data Updates
Restructures – Adds, Renames, Deletes
New Year Setup-- 53 weeks
Data Aging/Purging
Administrative Processes
Backups
6. Sizing Estimates/Hardware Requirements
A sizing estimate spreadsheet and hardware requirements should be supplied to the
client. These factors are dependent on the number of domains, intersection points,
number of workbooks, purge and delete strategy, planning horizon, retention of
data, etc.
7. Security Access and Viewing
User Setup/Security
To define Workbook Template Security, the system administrator will grant
individual users, or user groups, access to specific workbook templates. Granting
access to workbook templates provides users the ability to create, modify, save,
and commit workbooks for the assigned workbook templates. Users will
typically be assigned to “groups” based on their user application (or solution)
role. Users in the same group can be given access to workbook templates that
belong to that group alone. Users can be assigned to more than one “group” and
granted workbook template access without belonging to the user group that
typically uses a specific workbook template. Workbook access is either denied,
read only, or full access. Read only access will allow a user to create a workbook
for the template, but the user will not be able to edit any values or commit the
workbook. The read only workbook can be refreshed.
When users save a workbook, they assign one of three access permissions to the
workbook:
– World – Allow any user to open and edit the workbook.
– Group – Allow only those users in their same group to open and edit the
workbooks.
– User – Allow no other users to open and edit the workbook.
Note: A user must have access to the workbook template in

order to access the workbook, even if the workbook has
world access rights.
Workbook Limits
4 Oracle Retail Advanced Inventory Planning

Overview
Another aspect of workbook security is the ability to set limits for the number of
workbooks that a user can have saved at any given time. Limits can be set at the
following levels:
– User per template
– User Group per template
– Globally per template for all users
The limits are evaluated in the above order, which means that a limit defined at
user-template overrides any values defined at group-template or global-template
levels. If the above limits are not defined, the default value is one billion. The
limits are checked when a user begins the workbook build process. If the user’s
limit has been reached, an error message appears that informs the user that the
workbook build process cannot be completed because the user has reached their
limit. The message also informs the user what that limit is. The wizard process
then terminates.
8. Data Management Automation
Creation of certain logical constructs in Data Management may be set automatically
depending on the setting of certain parameters.
Examine the system parameter configurations and determine which pieces of
automation will be turned on. Map out each supplier’s “Ship-to” value and each
warehouse’s “Warehouse Type” that will be needed to effectively automate the
supply chain setup for those processes that are enabled.
Note: Keep in mind that the “Warehouse Type” helps define

Order Group destinations, Delivery Group destinations, and
the default ordering pack size for a SKU into a store and
warehouse.
9. Reconciliation
The reconciliation period is set to a day if the method is Reconciliation day-on-day
and is set to a review period at source if the method is Reconciliation-over-time.
Therefore, it has to be determined which reconciliation method will be selected at
SKU level.
You must set a flag to have a SKU reconciled in a constrained scenario.
10. Replenishment Methods
Define the replenishment methods to be used. Rule out replenishment methods that
are not applicable.
11. Perishables functionality
Spoilage threshold is calculated using the Acceptable Loss parameter. Acceptable
loss is a user-managed parameter in SRP, defined either at the class/store format
level or the SKU/store/day level.
Users have the ability to determine when to use expected spoilage via a ‘Store use
inventory aging flag’. Constraints on the application of inventory aging are as
follows
a. A global limit (in number of days) on or inside which an item with product life
can be considered in the expected spoilage calculation.
b. An expected write-off’s user maintained measure.
Implementation Guide 5
Overview
The first constraint is used as a high limit in number of days for a product life and is
called ‘Store Inventory Aging Limit.’ Product life as entered by a user does not have
a limit. The effectiveness of product life needs to be controlled by a User. Therefore a
global limit respective to the product life is necessary and configurable. The second
constraint refers to the fact that aging is a calculated number, not an actual number.
The user may have an actual number of spoilage that is to be used. A measure
(expected write-off’s) can be entered by the user and if entered will override any
spoilage calculation and be used as the amount to spoil on the given day.
To summarize the user input for expected spoilage:
The product life of the inventory at the point of receipt into the final selling
destination. (SKU/Str/Day)
The “Store use inventory aging flag” (SKU)
The global limit for using inventory aging (Scalar)
Expected write-off’s (amount to spoil). (SKU/Str/Day)
12. Shelf capacity
If the Shelf Capacity flag is set to “True,” then shelf capacity will be considered when
setting boundaries.
13. Substitution and value added functionality
The linked product flag is only used for user review purposes in AIP and indicates
whether there is a value added/pre-priced commodity or banded item association
with that particular SKU. If there is a value added/pre-priced association, the linked
product flag is only True between the promotional start and end dates. This flag will
be set within RMS.
Also a Substitution Flag must be set at the SKU level within Data Management,
which sets that a SKU is substitutable across Demand Group.
14. User Specified Allocations
You must set the number of days of history required for using USA Indexed.
15. Alerts
Set the days that an alert will be run.
16. Store Reconciliation Matrix configuration
The number of store priorities is configurable; therefore, the Shortage and Stockless
Surplus Priority Matrices may grow or shrink. However no screens or workbooks are
provided to view and maintain the configuration.
The priority of each boundary, for each store priority, will depend on the number of
store priorities defined. The order in which each boundary is met is configurable
however no screens or workbooks are provided to view and maintain the
configuration.
17. Network Throughput settings
The WRP Network Threshold Maintenance workbook is used to maintain network
alert parameters. The WRP Network Threshold Maintenance workbook is available
at the global and local domain levels. All measures should reflect the value in the
domain during load and refresh times, and all editable measures should be
committed to the domain unless otherwise stated.

3
Building a Production AIP RPAS Domain
Introduction
During the installation of the AIP RPAS batch code (as detailed in the AIP Installation
Guide) the installer has the option of creating an AIP RPAS domain using the sample
hierarchy data provided with the AIP package. This domain is not suitable for
production use.
This chapter provides detail to the user on the process for creating an AIP RPAS domain
with production-quality data. This process may be run whether or not you have already
run the AIP RPAS Installer.
For reference purposes, this chapter will use the notation <AIP Installer> to refer to the
UNIX directory where the AIP-13.1.2-rpas-installer.zip archive has been unpacked. The
UNIX environment variable $AIP_INSTALL refers to the directory location specified
during the execution of the AIP RPAS Installer for “Dir to store configurations,” as seen
in the below screen shot.
Base Paths for Solution Screen

In the screen shot above, /tmp/mike/acusys/configurations/aip was entered as the
directory to store the configurations. For purposes of this document, $AIP_INSTALL will
refer to this directory.
The table below provides information about the directories inside the $AIP_INSTALL
directory. These directories will be populated by the AIP RPAS Installer once it is run.
Building a Production AIP RPAS Domain 7

Introduction
Directory Contents
$AIP_INSTALL/configuration/AIP AIP base XML files generated by and which

are customizable by using the RPAS
Configuration Tools.
$AIP_INSTALL/domain_build/AIP/config AIP default XML files used by the RPAS
domain build process.
$AIP_INSTALL/domain_build/AIP/interface Directories and files copied into the RPAS
domain during domain build process.
These files are used by the interface
between AIP Oracle and external systems
(e.g. RMS, RDF).
$AIP_INSTALL/input AIP default/sample hierarchy data files
and message strings loaded into the RPAS
domain build during domain build process.
Hierarchy Data Overview

The $AIP_INSTALL/input directory contains a set of hierarchy data files that are
provided as a sample for load during the AIP RPAS domain build during the execution
of the AIP RPAS Installer. These hierarchy data files contain positions along each
dimension in each hierarchy. These hierarchy data files are described in the following
table.
Hierarchy Data File Description
bcsk.dat Baseline/Contingency Stock

clnd.dat Calendar
dsp.dat Destination Stocking Point
had.dat Advertising
hdgr.dat Delivery Group
hseq.dat Sequence Number
hspl.dat Supplier
husa.dat User Specified Allocation
intv.dat Interval
loc.dat Location
ntwg.dat Network Group
oltc.dat Order Lead Time
ordg.dat Order Group
proc.dat Profile Order Cycle
prod.dat Product
prof.dat Profile
ssp.dat Source Stocking Point
whse.dat Warehouse

Introduction
Some of the data provided in the AIP package will be of no use to the client running AIP
in a production environment because the positions are sample positions only, while other
hierarchy data contain generic positions that do not need to be customized (e.g. hseq,
intv). Therefore a domain built on this data is suitable only for proof of installation
correctness, including viewing with the RPAS Client, but not suitable for production.
Note: The client must build the domain with the BCSK
hierarchy even if they are not using this functionality. A core
dump will occur during AIP RPAS batch processes if there is
a lack of BCSK hierarchy positions in the hierarchy
maintenance database (hmaint).
Note: In previous versions of AIP the calendar hierarchy
could be generated at domain build time using RPAS
functionality. In this version of AIP, the calendar hierarchy
must be loaded as a flat file alongside the other hierarchy
files. There is no calendar generator provided with the
version of RPAS compatible with this version of AIP. See
“AIP Calendar Hierarchy” chapter of this guide for detailed
information on file format of calendar hierarchy.
In addition to the hierarchy data listed in the above table, there are two additional files
contained in the $AIP_INSTALL/input directory. These are non-optional, non-sample,
base code files containing message strings, which must co-exist with the hierarchy data.
These must be left intact and must not be replaced. During domain creation, these files
are loaded into the domain. These message string data files are described in the following
table.
Message Strings File Description
msgs.dat.aip Message hierarchy Positions

r_msglabel.ovr.aip.english Message String Data Overlay
Production AIP RPAS Domain Build Overview

This section describes the procedure by which the AIP installation files can be used as a
starting point for creating an AIP RPAS domain that contains production data. The
process consists of some manual intervention during certain points of the installation to
most efficiently and expediently create a usable AIP RPAS domain built on customer
hierarchy data. The intervention entails a combination of manipulation of the packaged
files, running the AIP RPAS Installer, and running some AIP RPAS batch scripts.
These instructions are organized into the following sections:
Manipulate the Hierarchy Data, Part One
Run the AIP RPAS Installer
Configuring the AIP Solution
Insert External System Data into the AIP RPAS Domain
Generate Load-Ready AIP Hierarchy Data
Create the AIP RPAS Global Domain Configuration XML File
Manipulate the Hierarchy Data, Part Two
Build the AIP RPAS Global Domain
AIP RPAS Domain Build Completion Summary
Introduction
Move the RPAS Domain (Optional)

Configure the RPAS Client to Use the Domain
Manipulate the Hierarchy Data, Part One

1. Locate and extract AIP-13.1.2-rpas-installer.zip into a newly created staging
directory, referred to as <AIP Installer>. Note that <AIP Installer> is not the same as
the environment variable, $AIP_INSTALL, used later.
For more information about the AIP Installer, read the Oracle Retail Advanced
Inventory Planning Installation Guide, Chapter “Installing AIP RPAS.”
The AIP-13.1.2-rpas-installer.zip file contains the following:
<AIP Installer>/aip/aip/aip_install/aip.tar.zip
This aip.tar.zip archive must be unpacked and manipulated as detailed in the
following steps.
2. Change directories to the <AIP_Installer>/aip/aip/aip_install/ directory where
aip.tar.zip is located, and unpack the aip.tar.zip archive using the following
commands:
cd <AIP_Installer>/aip/aip/aip_install
cp aip.tar.zip aip.tar.zip.orig
unzip -p aip.tar.zip | tar -xf –
This results in the creation of several subdirectories, including an
<AIP_Installer>/aip/aip/aip_install/input subdirectory.
3. Replace the <AIP_Installer>/aip/aip/aip_install/input/clnd.dat file with a clnd.dat
file created by the RMS to AIP transform script or by the customer. The clnd.dat must
be replaced "with a clnd.dat file created by customer, or a clnd.csv.dat created by
RMS-AIP transform script or by the customer."
The details for creating a clnd.csv.dat. file from RMS to AIP transformation can be
found in the Oracle Retail Advanced Inventory Planning Operations Guide.
The clnd.csv.dat file contains the calendar hierarchy information. The details on the
file format of this file for manual file creation (non-RMS) can be found in the chapter,
AIP RPAS Configurations. This file should be customized to contain the customer’s
desired calendar, including the start and end days required by the business. Note
that the calendar must begin with a Sunday.
4. Replace each of the following .dat files in <AIP_Installer>/aip/aip/aip_install/input
with a 0-byte file:
had.dat
hdgr.dat
oltc.dat
ordg.dat
proc.dat
Use the UNIX built-in shell commands rm and touch to accomplish this task:
cd <AIP_Installer>/aip/aip/aip_install/input
rm had.dat hdgr.dat oltc.dat ordg.dat proc.dat
touch had.dat hdgr.dat oltc.dat ordg.dat proc.dat

Introduction
Note: The hdgr (Delivery Group hierarchy), oltc (Order

Lead Time Cycle hierarchy), ordg (Order Group hierarchy),
and proc (Profile Order Cycle hierarchy) data files will be
supplied by AIP Oracle table exports, and the had
(Advertising hierarchy) file will be supplied by the
customer’s external system, so we do not want to load
sample positions into these hierarchies. This is the reason
they are zeroed out.
Note: AIP Oracle will also supply the ntwg (Network Group
hierarchy) data file, but this hierarchy must have positions in
it for the domain build process to succeed. The sample data
for ntwg will be removed at the end of this process.
At this point there is no further hierarchy manipulation that can be done to replace
sample hierarchy data files with non-sample hierarchy data files, without running
part of AIP RPAS batch. Therefore the
<AIP_Installer>/aip/aip/aip_install/aip.tar.zip file must be repacked so it can be
used by the AIP RPAS Installer.
5. Repack the aip.tar.zip archive using the following commands:
tar -cf aip.tar input configuration domain_build
zip aip.tar.zip aip.tar
Run the AIP RPAS Installer

The goal of this step is to not only install the AIP binary code, but to also build a
temporary AIP RPAS domain that will be used for running a subset of AIP RPAS batch
processes to create RPAS-loadable, customer-sourced, hierarchy data.
With the repacked aip.tar.zip file, the installation instructions in Chapter 7 of the Oracle
Retail Advanced Inventory Planning Installation Guide must be followed in their entirety,
except that the AIP RPAS Installer does not need to be unpacked again. When prompted
to build an AIP domain, make note of the location of the domain (AIP path prompt on
Domain installation paths screen) as this is required as an environment variable,
$TEST_AIPDOMAIN. Also be sure to request the creation of the domain at the Create
AIP Domain prompt.
Running the AIP RPAS Installer installs all the AIP binary code and creates an AIP RPAS
domain that contains the customer’s Calendar hierarchy and the following empty
hierarchies:
Advertising
Delivery Group
Order Lead Time Cycle
Order Group
Profile Order Cycle
The remaining hierarchies in this temporary domain contain sample data.
Using this hybrid sample-customer hierarchy domain, an abbreviated AIP RPAS batch
can be executed, according to the instructions in the next section, to create the remaining
AIP RPAS hierarchies. These hierarchies will then be used to create a final domain that is
built with customer hierarchy data.
During the RPAS Installer execution, you were prompted to enter the path to store a
newly created retaillogin.ksh script. During the AIP RPAS Installer execution, an
$AIP_INSTALL/aiplogin.ksh script was created, which is called by retaillogin.ksh. This
Introduction
retaillogin.ksh script must be executed prior to running the AIP RPAS batch processes
because it sets some environment variables, including AIP-specific variables set by
aiplogin.ksh, which are needed for the next steps.
At this point you should source the retaillogin.ksh script to set your environment for the
remaining steps. It will call aiplogin.ksh which was created by the AIP RPAS Installer,
which will set the $AIP_INSTALL and $TEST_AIPDOMAIN environment variables.
cd <Path to retaillogin.ksh script>
. ./retaillogin.ksh
Configuring the AIP Solution

Users must make any optional customizations to the AIP configuration prior to building
the production domain. Configure the AIP solution using RPAS Configuration Tools.
Note: This section requires that the RPAS Configuration

Tools are installed and working properly on your Windows
workstation. For information on installing and
troubleshooting RPAS Configuration Tools, refer to the
RPAS Installation Guide.
AIP is packaged with a base configuration that all implementations must use as a starting
point for any customization. This base configuration is stored within various files and
directories which are unpacked during installation. In order to modify this configuration
the configuration files must be loaded onto a Windows workstation in order to load them
into the RPAS Configuration Tools.
Note: This release of the AIP RPAS configuration is enabled

for multi-language capability as a default. This means that
the domain build will set up positions in the database arrays
into which translated strings may be optionally loaded by
the domain administrator. See the Oracle Retail Application
Server Administration Guide for details. It is strongly
recommended that the multi-language setting remain at
“true". RPAS does not support upgrading a domain that is
not multi-language to a multi-language configuration.
Because the RPAS Configuration Tools must run on a Windows workstation, in order to
customize the configuration, the $AIP_INSTALL/configuration/AIP directory must be
accessible from or copied to a Windows PC on a local or network drive.
The AIP solution is configurable to a limited degree. The following describes what you
may and may not customize with respect to maintaining the integrity of this release:
Clients cannot change existing measures or rules, or add rules to existing rule
groups. Doing so will result in a non-supported AIP configuration, which will yield
unpredictable results during the operation of AIP.
Clients may add additional measures, rule groups and workbooks. These will not be
modified or otherwise touched during the patch installation.
Clients may customize the domain Hierarchy contained in hierarchy.xml. In order to
insert a customized hierarchy.xml into the configuration, the modified (using the
RPAS Configuration Tools) hierarchy.xml must be copied to
$AIP_INSTALL/configuration/AIP/hierarchy.xml. This is where the domain build
will be looking for the hierarchy.
The AIP RPAS domain must be partitioned along the product hierarchy at the
subclass (scls) dimension. This is not configurable.

Introduction
Basic instructions for running the RPAS Configuration Tools are as follows:
1. Double-click the ConfigTools.exe file in your RPAS Configuration Tools installation
directory to launch the RPAS Configuration Tools.
The AIP solution consists of one domain structure, named “AIP”.
2. From the File menu, select Open and navigate to the configuration directory on your
local or network drive.
3. Navigate to the configuration/AIP directory and select the AIP.xml file to open the
AIP domain configuration.
4. Perform any configuration tasks that are necessary, save and then close the AIP
configuration.
5. Once you are satisfied with the configuration, copy the configuration directory back
to $AIP_INSTALL before proceeding.
Insert External System Data into the AIP RPAS Domain

External system hierarchy and measure data must be introduced into the AIP RPAS
domain in order for the AIP RPAS batch processes to execute and create the remaining
AIP RPAS-loadable hierarchies.
To run a partial batch that will result in loadable hierarchy data, those external system
files required by AIP RPAS batch must be placed into the AIP RPAS domain.
Even though only the hierarchy data files will be used for creating the RPAS loadable
hierarchy files, the required measure data files must also be present for the batch
processes to complete without error, because the batch processes will check for the
existence of all required files in the early batch of external files. For reference, these early
files are listed with their options (REQUIRED or OPTIONAL) in
$AIPDOMAIN/interface/config/external/earlyfiles.config.
1. The following hierarchy data files must be prepared according to the file formats
defined in this guide, and copied to the $AIPDOMAIN/interface/rms directory.
item.txt
loc.txt
splr.txt
whse.txt
Currently, the AIP RPAS batch process will check for existence of all required files
and halt the process if any required files are missing. Therefore, to complete the
batch processes without error, some measure data files must also be present in the
$AIPDOMAIN/interface/rms directory. However, they only need to exist to pass the
existence check. They do not need to be populated with data.
2. Use the UNIX command touch to create 0-byte data files for the REQUIRED
measures. The OPTIONAL data files do not need to be created. To avoid error in
batch processing that expects to process advertising and interval hierarchies even
when they are not present (as they are configured as optional), also touch had.txt and
intv.txt.
dm0_ofseffdt_.txt
dm0_onseffdt_.txt
dmx_prdspllks.txt
dmx_dirspl.txt
had.txt
intv.txt
Introduction
Note: The goal of this preparation step is to provide files

needed to create RPAS-loadable hierarchy files, which can be
used to build a domain based on customer hierarchy data.
As a result only the first few steps of AIP RPAS batch will be
run as described in the next section. It follows then that the
inventory and forecast data files are not required even in 0-
byte stub form, because the AIP RPAS batch processes which
process those files will not be run.
Generate Load-Ready AIP Hierarchy Data

A subset of the first-day AIP RPAS batch processes can now be run against the AIP RPAS
domain created in the previous sections. The batch steps run will create hierarchy data
files which can then be used to create a domain using customer hierarchy data positions
(for example, customer SKUs and stores).
Note: During the RPAS Installer execution, you were

prompted to enter the path to store a newly created
retaillogin.ksh script. During the AIP RPAS Installer
execution, an $AIP_INSTALL/aiplogin.ksh script was
created, which is called by retaillogin.ksh. This
retaillogin.ksh script must be executed prior to running the
AIP RPAS batch processes because it sets some environment
variables, including AIP-specific variables set by
aiplogin.ksh, which are needed for the next steps.
1. The master AIP RPAS batch script “aip_batch.sh” reads from aip_env_rpas.sh to find
the locations of the domain and log path. The domain and log path variables
(AIPDOMAIN and RPAS_INTEGRATION_HOME) are defaulted to the
$TEST_AIPDOMAIN and $TEST_RPAS_INTEGEATION_HOME variables.
Therefore, add a definition of TEST_RPAS_INTEGRATION_HOME to
$AIP_INSTALL/aiplogin.ksh, or redefine the RPAS_INTEGRATION_HOME
variable inside $RPAS_HOME/bin/aip_env_rpas.sh. This is the location where the
logs will be written.
2. Execute the following command:
aip_batch.sh -f -s set_implementation_parameters -e convert_hierarchies_for_loading
This command instructs the AIP RPAS batch to run all first-day steps as scheduled in
the $RPAS_HOME/bin/aip_batch.sh script from the
set_implementation_parameters step through the convert_hierarchies_for_loading
step. These steps accomplish the task of creating RPAS loadable hierarchy files for
the following:
product (prod.dat)
warehouse (whse.dat)
supplier (hspl.dat)
location (loc.dat)
profile (prof.dat)
source stocking point (ssp.dat)
destination stocking point (dsp.dat)
These hierarchy data files are now located in $AIPDOMAIN/input directory.
If there are any errors resulting from these batch processes, see the log files written to
$TEST_RPAS_INTEGRATION_HOME to determine the error. If the logs indicate

Introduction
that any measure data files are missing, ensure that 0-byte versions of these files are
located in the $AIPDOMAIN/interface/rms directory and rerun the above
aip_batch.sh command.
Create the AIP RPAS Global Domain Configuration XML File

Some previous versions of AIP allowed for two kinds of RPAS domains. The first was an
RPAS simple domain, where all the hierarchy and measure data are contained in one set
of databases. The second was an RPAS global domain, where the hierarchy and measure
data are partitioned across several sets of databases. In a global domain set, there is one
master domain and one or more local domains (or subdomains).
This version of AIP supports only RPAS global domains.
The $AIP_INSTALL/domain_build directory contains files necessary to instruct the
build programs how and where to build domains, as well as partitioning information for
global domains. Within $AIP_INSTALL/domain_build, there is one directory, AIP,
corresponding to the build instructions for the AIP domain. Within the AIP directory is a
config directory, which contains files that must be edited during installation.
The directory $AIP_INSTALL/domain_build/AIP/config contains one file:
globaldomainconfig.xml
Inside the globaldomainconfig.xml file are XML tags read by the RPAS domain build
program that specify the name, location, and partitioning information for each domain in
a global domain structure.
The settings provided with this installation specify a global domain set with one master
domain and two local domains. The default partitioning dimension is subclass (SCLS)
and the default partitioning dimensions are set to match the subclasses contained in the
sample data files provided in the input.tar file. The partitioning dimension is not
customizable and must remain at subclass (SCLS). However, the subclasses in each local
domain, and the number of local domains, must be determined according to the business
needs.
The default globaldomainconfig.xml for AIP is similar to the example below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<rpas>
<globaldomain>
<path>DOMAIN_PATH</path>
<partitiondim>SCLS</partitiondim>
<subdomain>
<subpath>DOMAIN_PATH/ldom0</subpath>
<subpositions>1414_1000_1000,25_110_1204,25_116_438,25_116_439,25_116_440,25_116_442,25_119_692,3_564_984,43
_813_1458,43_813_516,44_602_1212,44_602_1214,44_602_1215,48_264_683,48_906_803</subpositions>
</subdomain>
<subdomain>
<subpath>DOMAIN_PATH/ldom1</subpath>
<subpositions>48_906_804,48_906_805,5_503_1401,5_503_1503,5_503_1504,5_530_246,5_531_658,5_699_817,66_213_48
2,66_214_553,66_223_394,66_224_1117,71_710_112,71_710_113,71_710_1497,7_562_1108</subpositions>
</subdomain>
</globaldomain>
</rpas>
If the desired global domain solution for the AIP module contains more than two local
domains, copy the <subdomain> … </subdomain> tag-set as many times as needed, then
customize each new copy of the tag-set.
Introduction
Tip: Each sub-domain (i.e. local domain) must contain at

least one position along the partitioning dimension (e.g.,
SCLS) in the production hierarchy data set, namely,
prod.dat. In addition, all the positions along the partitioning
dimension in the data set (prod.dat) must be listed in one of
the local domains; otherwise, the domain creation will fail.
An error will be reported in the build log.
The <path> … </path> and <subpath> … </subpath> tags in the globaldomainconfig.xml files must be
modified, since they specify the absolute path to each component of each global domain.
This XML file currently contains DOMAINPATH as a placeholder, which you must replace
with the actual domain path components.
Tip: If the globaldomainconfig.xml file refers to domain

directories that already exist, the domain build process
below will not overwrite these domains. Rather, they will be
skipped. It is essential that the <path> and <subpath> tags contain
paths that do NOT exist.
Example:
<path>/u01/acusys/rpas/Domains/aip</path>
<subpath>/u01/acusys/rpas/Domains/aip/ldom0</subpath>
<subpath>/u01/acusys/rpas/Domains/aip/ldom1</subpath>
where /u01/acusys/rpas/Domains/aip does NOT currently exist.
Note: Before invoking the utility (described below) to create

the AIP domain there is one system environment variable
clients may wish to consider. This environment variable can
be configured to control certain behaviors of the RPAS
Configuration Tools utility, rpasInstall, which does the majority
of the work to build a domain. The variable name is
RIDE_OPTIONS. Please consult the RPAS documentation
for more information about various options that may be
configured by customizing the RIDE_OPTIONS variable.
Manipulate the Hierarchy Data, Part Two

The AIP Package files must be updated with the newly created required hierarchy and
configuration XML files.
1. Repackage the <AIP_Installer>/aip/aip/aip_install/aip.tar.zip file with the
following newly created files from the $AIPDOMAIN/input directory:
prod.dat
whse.dat
hspl.dat
loc.dat
prof.dat
dsp.dat
ssp.dat
Repackage the <AIP_Installer>/aip/aip/aip_install/aip.tar.zip file using the
following commands:
cd <AIP_Installer>/aip/aip/aip_install/input

Introduction
cp $TEST_AIPDOMAIN/input/prod.dat .
cp $TEST_AIPDOMAIN/input/whse.dat .
cp $TEST_AIPDOMAIN/input/hspl.dat .
cp $TEST_AIPDOMAIN/input/loc.dat .
cp $TEST_AIPDOMAIN/input/prof.dat .
cp $TEST_AIPDOMAIN/input/ssp.dat .
cp $TEST_AIPDOMAIN/input/dsp.dat .
tar -cf aip.tar input configuration domain_build
zip aip.tar.zip aip.tar
It is important for the domain build process, described in the next section, to find the
customer hierarchy data in the <AIP_Installer>/aip/aip/aip_install/input directory
and the globaldomainconfig.xml file in the
<AIP_Installer>/aip/aip/aip_install/domain_build/AIP/config directory.
Note: The aip.tar.zip file does not have to be repackaged in

order to run the domain build independently. Nevertheless,
it is suggested that the aip.tar.zip file be repackaged so that
the entire AIP RPAS installer can be run again in the future
with the end result of an AIP RPAS domain that contains
customer data.
Build the AIP RPAS Global Domain

Once the various configuration files and hierarchy files are customized, the temporary
AIP RPAS domain can be deleted, and the final AIP RPAS domain can be built. Invoke
the build_aip_domains.ksh script to initiate the AIP domain build process manually. There is no
need to go through the Installer to build the domain. This script is located in the
$RPAS_HOME/bin directory. Make sure that this directory is in the $PATH
environment variable of the UNIX account running the batch. If you have executed
retaillogin.ksh previously then $RPAS_HOME/bin should be in your $PATH.
The build_aip_domains.ksh requires several command line options displayed in the table below.
Option Option Description Argument Value
-d Domain source $AIP_INSTALL/domain_build

-c Configuration $AIP_INSTALL/configuration
-i Input $AIP_INSTALL/input
-l Log file < any path and filename to an output log file >
Example execution command:

build_aip_domains.ksh -d $AIP_INSTALL/domain_build -c $AIP_INSTALL/configuration
-i $AIP_INSTALL/input -l $AIP_INSTALL/aip_build.log
This build script internally calls the appropriate RPAS installation programs to perform
the following:
Create an RPAS global domain in the paths/locations specified by the configuration
files. If domain components already exist in the specified locations, they will not be
overwritten.
Register all measures, templates, and rules that were created using the RPAS
Configuration Tools in the domain.
Establish the partitioning mapping according to the partitioning information
specified in the globaldomainconfig.xml file.
Introduction
Verify the domain build process for errors after the installation programs are
complete. In the event that errors occurred in the domain build, the user will be
alerted and should check the log file to determine the source of the error.
The log file may be scanned for errors by using any text editor or UNIX text search
commands. If an error occurs, it will most likely contain the word ‘error’, so the following
command might be useful for detecting if any build errors occurred:
grep –i error $AIP_INSTALL/build_logs/*.log
Other keywords to search for are “<E”, “not found”, and “exception”.
Note: When viewing or searching through the build log,

please consult the Oracle Retail Advanced Inventory Planning
Release Notes. The Release Notes contain all known issues
associated with this release.
Note: Once the domain build has successfully completed,
you must preserve the $AIP_INSTALL directory. The
domain configuration files are automatically copied inside
the domain after a successful build. However, the
$AIP_INSTALL directory will be used for AIP patches.
Once the domain build is completed, the sample positions from the Network Group
hierarchy should be removed. This is done in order that there will be no sample positions
in this hierarchy once the AIP Oracle export provides new hierarchy positions during
daily AIP RPAS batch.
Remove the Network Group hierarchy positions using the following commands:
touch $TEST_AIPDOMAIN/input/ntwg.dat
loadHier -d $TEST_AIPDOMAIN –load ntwg -checkParents -purgeAge 0
The -purgeAge option indicates that all positions in the hierarchy older than the number
specified (in days) should be removed from the hierarchy. Using 0 ensures all positions
are removed, and since there are no positions in the ntwg.dat file to be loaded, the
hierarchy is effectively cleared.
AIP RPAS Domain Build Completion Summary

The end result after executing the steps in the previous sections is an AIP RPAS domain
with the customer-specified arrangement of product subclasses per local domain,
together with the following arrangement of hierarchies:
Customer Data Hierarchies:

Calendar Supplier Source Stocking Point
Product Location Destination Stocking Point
Warehouse Profile Advertising
Empty Hierarchies:
Delivery Group Profile Order Cycle
Order Lead Time Cycle Network Group
Order Group

Introduction
Default / Sample Hierarchies:

Baseline/Contingency Stock User Specified Allocation
Sequence Number Interval
Note: The empty hierarchies will be populated during a full

AIP RPAS batch run. The data for these hierarchies will be
supplied by the AIP Oracle export which will be loaded into
the AIP RPAS domain.
Move the RPAS Domain (Optional)

RPAS global domains contain internal pointers that specify the disk location of the
master and local domains. The master domain must know where the local domains exist
on disk, and the local domains must each know where the master domain exists.
After the AIP domain is created, you may move it to a different location. However, the
following process must be followed to copy or move the domain components in order to
update the newly copied/moved domain component directories.
If the local domain directories are subdirectories of the master domain directory, or if
you want your local domains to be moved inside the master domain, perform the
following:
Use the RPAS copyDomain utility. Refer to the RPAS Administration Guide for details
about this utility. This utility updates the internal pointers between master and sub
domains. It converts the pointers between master and local from absolute UNIX paths to
relative paths. The master domain refers to local domains by directory name only (e.g.
ldom0), and the local domains refer to the master domain by “..”.
If the sub domain directories are not subdirectories of the master domain, and you wish
to preserve this “spread-out” global domain set, but at the same time you wish to move a
local domain or the master domain, use the RPAS moveDomain utility. This utility will move
some or all parts of an RPAS domain by specifying the new paths in an XML file. Refer to
the RPAS Administration Guide for details about this utility.
Note: Previous versions of AIP contained an updateGlobalPointers

utility. This utility is deprecated in AIP due to increased
functionality in the copyDomain and moveDomain RPAS utilities.
Configure the RPAS Client to Use the Domain

The RPAS Client must be configured to point to one of the newly created domains.
Refer to the RPAS Installation Guide for instructions on how to attach the domains to the
client. Double-click the EConfigure.exe file to define the RPAS Client configuration.
Post Installation Instructions
Post Installation Instructions

Refer to other chapters in this AIP Implementation Guide and the AIP Operations Guide for
information on loading data into the domains and for practical use of the AIP batch
domains.
The AIP RPAS domain does not contain any accounts. The domain build process for
previous versions of AIP and RPAS created the default accounts of adm and usr during
the domain build. These accounts are not created in the domain build process for this
release.
For details and instructions on how to create admin and user accounts for the AIP RPAS
domain, read the:
Oracle Retail Predictive Application Server Release Notes
Oracle Retail Predictive Application Server Administration Guide for the description of
the usermgr utility in the "Operational Utilities" chapter
Oracle Retail Predictive Application Server Administration Guide’s chapter on "Security
and User Administration"

4
System Configuration
Setting Environment Variables
After AIP is installed, you must define the environment variables for the domain paths,
integration directory paths, message logging levels, etc. These variables define the
environment in which batch scripts are run. These settings do not affect the way in which
the business uses AIP to replenish the supply-chain.
The scripts run as part of the nightly batch on both of the AIP platforms, RPAS and
Oracle. Both platforms have defined environment variables for configuration.
Configuring AIP RPAS Environment Variables

The following aspects of the RPAS-side batch must be configured so that the controller
scripts—aip_batch.sh, aip_export_to_ro.sh, and aip_import_from_ro.sh—and each batch
step script can be run from the command line or from a job scheduler.
Setting RPAS Position Level Security

The position level security for RPAS needs to be modified. Position Level Security allows
access control for dimensions on a position-by-position basis. Refer to the RPAS
Administration for detail information this feature. To specify the security dimension for a
hierarchy, use the RPAS Configuration Tools or hierarchyMgr utility. Refer to the RPAS
Configuration Tools User Guide for more information.
aip_env_rpas.sh
The variables displayed in the following table need to be defined properly within
aip_env_rpas.sh.
It is important to note that the values of the environment variables can be variables
themselves depending on the business needs. Such variables may add flexibility for
environment maintenance, patch testing, etc. and are used at the discretion of the
business.
For example:
If aip_env_rpas.sh contains
RPAS_INTEGRATION_HOME= "${TEST_RPAS_INTEGRATION_HOME}"
TEST_RPAS_INTEGRATION_HOME is a client specific environment variable whose value is the
correct path to the root integration directory. This and all other such variables must also
be defined in order to run the batch.
Finally, the variables below corresponding to directory paths must not contain white
space. For example, AIPDOMAIN may be defined as “/files1/aip/AIP1” but may not be
defined as “/files1/aip/AIP RPAS Domain”.
System Configuration 21
Environment Variable Description
AIPDOMAIN Fully qualified path of the AIP RPAS global domain. The default value
(TEST_AIPDOMAIN) provided at the time of installation is a variable which
must also be defined apart of aip_env_rpas.sh if it is to be retained as the
value.
RPAS_INTEGRATION_HOME Fully qualified path of a readable/writeable directory that serves mainly as
a base for other path definitions later in aip_env_rpas.sh. Commonly set
equal to AIPDOMAIN. The default value
(TEST_RPAS_INTEGRATION_HOME) provided at the time of installation
is a variable which must also be defined apart of aip_env_rpas.sh if it is to be
retained as the value.
DEFAULT_DOMAIN Fully qualified path of the AIP RPAS local domain into which any new
subclass will be added.
BSA_TEMP_DIR Fully qualified path of readable/writeable directory where scripts may store
temporary files. Valid definition of this variable is required by the BSA
common scripts.
Note: THIS SHOULD NOT BE SET TO /tmp. Failures may occur due to
insufficient temporary workspace.
BSA_LOG_LEVEL Script logging threshold severity. Only log entries at this or higher severity
level will be written to the script logs. Must be one of { PROFILE | DEBUG |
INFORMATION | WARNING | ERROR }. Valid definition of this variable is
required by the BSA common scripts.
BSA_MAX_PARALLEL Script parallel process fan-out maximum. The number of processes that any
given process (script instance) may spawn. Valid definition of this variable is
required by the BSA common scripts.
BSA_LOG_HOME Fully qualified path of readable/writeable directory where script logs will
be rooted. Script logs are written into a hierarchy that parallels the script call
tree, rooted in a date stamped directory located in this specified directory.
Valid definition of this variable is required by the BSA common scripts.
BSA_LOG_TYPE Integer parameter that specifies the type of script log files to be written.
Must equal one of { 0 | 1 | 2 | 3 }. These values are defined as follows:
0 = No logging
1 = Text ".log" files;
2 = XML structured ".xml" file;
3 = Text and XML log files.
BSA_CONFIG_DIR Fully qualified path to directory that contains the BSA configuration file
bsa_prep_files.config. Valid definition of this variable is required by the BSA
common scripts.
BSA_ARCHIVE_DIR Fully qualified path to directory to which BSA file processing operations will
archive files. Valid definition of this variable is required by the BSA common
scripts.
RPAS_LOG_LEVEL RPAS binary logging threshold severity. Only log entries at this or higher
severity level will be written to the script logs from binaries that accept a –
loglevel argument. Must be one of
{ PROFILE | DEBUG | INFORMATION | WARNING | ERROR }.
RAW_RMS_DATA_DIR Fully qualified path to directory that contains untransformed RMS output
data.

RMS_SCHEMA_DIR Fully qualified path to the directory that contains the RETL schema files
corresponding to the untransformed RMS version 11+ output data.
RMS10_SCHEMA_DIR Fully qualified path to the directory that contains the RETL schema files
corresponding to the untransformed RMS version 10 output data.
AIP_SCHEMA_DIR Fully qualified path to directory that contains RETL schema files depicting
the transformed RMS output data.
RPAS_PAGE_SPLIT_PERCENTAGE This variable is used to optimize AIP performance. Do not alter this setting
without consulting AIP Technical Management.
ORACLE_AIP_PERISHABLE_ON This UNIX variable is set to YES (ORACLE_AIP_PERISHABLE_ON=yes)
when AIP is replenishing perishable products. This setting is case sensitive.
LIMIT_OF_SKPS_LOCAL_DOMAIN Maximum number of SKU-Pack Sizes allowed in a local domain when
considering where to add a new subclass received from Merchandising
System.
CYCLE_START_DATE The date in YYYYMMDD format, which denotes the start date for counting
day of fortnight and day of four-week period positions. This variable can be
customized if you are not using AIP-Oracle.
Note: aip_env_rpas.sh also includes some Implementation

Parameters. See the chapter on AIP RPAS Configurations for
details on these parameters.
aip_ro_common.sh
The variables displayed in the following table need to be defined properly in order for
the Oracle Retail Replenishment Optimization (RO) integration controller scripts to
execute.
Installations not integrating with a replenishment optimization solution may disregard
these settings.
Environment Description
Variable
RO_INPUT The location of input data copied or transferred from the RO server.
RO_OUTPUT The location of output data to be copied or transferred to RO.
RO_CONFIG The location of RO integration configuration files.
RO_FILE_TYPE The file type for data exchange between AIP and RO. Must be either
‘csv’ or ‘txt’.
RPAS_TODAY
This value defines ‘TODAY’ for the AIP RPAS environment. It is used to ensure that the
replenishment batch can be run for a single calendar day, independent of the actual
server date. During a normal production run of the batch, this value should be set by the
VDATE (virtual date) value exported from AIP Online. This variable can be set for ad hoc
procedures, but it should be cleared after the procedure has completed as this may have
an adverse affect on the user workbooks.
Number of Available File Handles (ULIMIT)

Prior to AIP batch execution the System Administrator should ensure the limit of
available file handles (ulimit –n <number>) is above 2000 file handles per process.
Setting ulimit less than recommended value may cause AIP batch process to fail. Please
exercise caution while setting this system variable. Do not set this too high, as it can
seriously impact performance system-wide.
Configuring AIP Online Environment Variables

aip_env_online.sh
The aip_env_online.sh variables in the following table need to be configured for your
environment. This information can also be found in the README file provided with the
online integration files.
It is important to note that the values of the environment variables can be variables
themselves depending on the clients needs. Such variables may add flexibility for
environment maintenance, patch testing, etc. and are used at the discretion of the
business.
INTEGRATION_HOME Fully qualified path to the interface home directory. The default value references
TEST_ONL_INTEGRATION_HOME, an externally defined variable. However, the
client may assign a hardcoded path to this value at their discretion.
ONL_OUTBOUND_DIR The default is ${INTEGRATION_HOME}/outbound. This variable defines the
directory location where the cron_export.sh script will put the files containing the data
exported from AIP Online. If bypassing the RIB the tsf_po_export.sh script will also
write the exported transfers and purchase order files to this directory. This must match
the ONL_OUTBOUND_DIR defined in aip_env_rpas.sh script, which may reside on a
different server.
ONL_INBOUND_DIR The default is ${INTEGRATION_HOME}/inbound. This variable defines the directory
location where cron_import.sh and cron_import_order.sh expect the inbound files
from RPAS to be sourced from.
BSA_ARCHIVE_DIR The default is ${INTEGRATION_HOME}/archive. This variable defines the directory
location where cron_import.sh and cron_import_order.sh scripts will send the input
data files for archiving.
BSA_LOG_HOME Fully qualified path of readable/writeable directory where script logs will be rooted.
Script logs are written into a hierarchy that parallels the script call tree, rooted in a date
stamped directory located in this specified directory. Valid definition of this variable is
required by the BSA common scripts. This variable is initially set to
${INTEGRATION_HOME}/logs.
BSA_CONFIG_DIR Fully qualified path to directory that contains the BSA configuration file
bsa_prep_files.config. Valid definition of this variable is required by the BSA common
scripts. This variable is initially set to ${INTEGRATION_HOME}/config.
BSA_TEMP_DIR Fully qualified path of readable/writeable directory where scripts may store
temporary files. Valid definition of this variable is required by the BSA common
scripts.
BSA_LOG_LEVEL Logging severity threshold for batch scripts. Only log entries at this or higher severity
level will be written to the script logs from procedures that accept the –loglevel
argument. Listed in increasing order of severity, one of the following levels must be
selected { PROFILE | DEBUG | INFORMATION | WARNING | ERROR }.

BSA_LOG_TYPE Integer parameter that specifies the type of script log files to be written. Must equal
one of { 0 | 1 | 2 | 3 }. These values are defined as follows:
0 = No logging
1 = Text ".log" files
2 = XML structured ".xml" file
3 = Text and XML log files
BSA_MAX_PARALLEL Script parallel process fan-out maximum. The number of processes that any given
process (script instance) may spawn. Valid definition of this variable is required by the
BSA common scripts.
DEFAULT_BSA_SQL_CRED_APP The default is DATABASE. It is used by bsa_sql.sh script to perform a lookup from the
config.xml file to connect to the AIP Online database.
RETL_MAX_HEAP_SIZE The default value is 700M. Raise this limit to improve performance on production
systems.
RETL_CONFIG_FILE File name containing database connection information. This variable is used by RETL
scripts. The default value references TEST_RETL_CONFIG_FILE, an externally defined
variable. However, the client may assign a hardcoded value at their discretion. In
either case, the variable should ultimately point to the fully-qualified path of a RETL
configuration file. An example config.xml file is included with AIP.
AIPDOMAIN Fully qualified path of the AIP RPAS global domain. The default value references
TEST_AIPDOMAIN, an externally defined variable. However, the client may assign a
hardcoded path to this value at their discretion.
HAVE_WIP Indicates if WIP is enabled to export and import data. The default value is set to false.
WIP is not implemented for this release of AIP..
ONL_SCHEMA_OWNER This variable sets the database schema owner. It is used by the store_source extract.
For example, if you are running AIP online extracts as "aipdev131user" but the schema
owner is "aipdev131", then regardless of the running database user,
ONL_SCHEMA_OWNER should be set to "aipdev131".
NLS_LANG This variable defines the character encoding of the RETL import files.
ONL_VDATE_DIR The directory location of the vdate.int file.
ONL_DATA_DIR This variable defines the location of data directory that contains the compressed and
zipped orders from AIP-RPAS. i.e. location where srp.tar.Z is placed for
cron_import_order.
RETL_INIT_HEAP_SIZE The default value is 200M. Raise this limit to improve performance on production
systems.
Note: RETL runs within a Java Virtual Machine (JVM).

Errors concerning the JVM stack size may be encountered
when executing AIP Oracle batch processes. This value
represents the amount of memory allocated to a single JVM
thread and is defaulted by the JVM. The user may override it
by setting the RETL_THREAD_STACK_SIZE variable in
aip_env_online.sh or in their user profile.
Example:
export RETL_THREAD_STACK_SIZE=200000
It can also be set in rfx.conf, the configuration file for RETL

itself. However, modifying rfx.conf will affect all users
accessing the RETL installation, not just those using AIP.
When manipulating the JVM stack size, extreme care should
be taken to prevent RETL from using an inordinate amount
of the available physical memory.
RETL
Once RETL is installed, the environment variables displayed in the table below should be
defined. Verify that these environment variables are properly defined.
Variable Description
RFX_HOME The RETL home directory

RFX_TMP The RETL temp directory
ORACLE_HOME Oracle installation directory
User Path
When invoking online shell scripts, the user’s PATH must include the following
directories:
$INTEGRATION_HOME
$INTEGRATION_HOME/bsa
$INTEGRATION_HOME/config
$INTEGRATION_HOME/scripts
$RFX_HOME
$RFX_TMP
$ORACLE_HOME
For some variables defined in aip_env_online.sh, the value is defaulted to another
externally-defined variable. This approach provides flexibility in that multiple users can
use a single aip_env_online.sh but point to different test directories, domains, or RETL
configuration files. It is important to note that the test directories listed in the externally
defined variables must also be in the user’s PATH. Please refer to the AIP Installation
Guide for further details on defining variables in the .profile file.

Using the Scheduler to Run AIP Batch Processes
Example:
If aip_env_online.sh contains
INTEGRATION_HOME= "${TEST_ONL_INTEGRATION_HOME}"
TEST_ONL_INTEGRATION_HOME is an environment variable whose value is the correct path
to the root integration directory. The path that is defined for TEST_ONL_INTEGRATION_HOME
must be in the user’s PATH.

This topic provides information about using the Scheduler to run the AIP on RPAS and
AIP on Oracle batch processes. The batch processes span both platforms and depend on
inputs from the merchandising and forecasting and optimization systems.
The following control scripts can be used to execute AIP batch:
vdate.sh aip_t_master.ksh
cron_export.sh aip_batch.sh
cron_import.sh pre_scale.sh
cron_import_order.sh scale_order.sh
merge_order.sh cron_release.sh
post_scale.sh cron_post_release.sh
cron_purge.sh aip_import_from_ro.sh
aip_export_to_ro.sh
If the Oracle Retail Integration Bus (RIB) will not be used to communicate the purchase
orders and transfers released by the overnight batch, the following script should also be
used:
tsf_po_export.sh
Also once a week or once a month data purging script can be run to delete invalid or
ineffective data from Oracle tables by executing following script:
scripts/aip_purge.sh
This script should be followed by executing purging_aip_batch.sh.to make
corresponding changes in AIP-RPAS database
Many of these control scripts accept or require parameters to indicate the specific logic to
execute. Therefore you will notice that the control script may be called multiple times
with different parameters. Where restart/recovery at the control script level is not
sufficiently granular the sub-scripts, called by the top level control script, can be
scheduled instead. However the scheduled tasks must carefully consider all tasks
executed by the control script, including common environment control.
The following diagram outlines the AIP script/step execution and dependencies. Note
that the shaded boxes of the pre-critical, critical, and post-critical diagrams represent the
executable steps of aip_batch.sh. The aip_batch.sh step name, in bold, can be passed into
the script as a parameter or the subscript, listed below the step name, can be scheduled.
Note: AIP does not move data between platforms internally

or retrieve files which were generated external to AIP. All
data that is input to AIP must be transferred via FTP or
copied to the appropriate inbound directory on the AIP
server.
Pre-Critical Path Tasks

The diagram and table below provide information about the pre-critical path steps that
need to be performed.
Pre-Critical Tasks Process Flow Diagram

The table below provides information about the script or action performed in the Pre-
Critical Tasks process flow diagram. These steps include the scaling module scripts
which are only required by those Retailers who are supplier scaling and/or container
scaling.
Script or Action Parameter(s) Platform Location
Bring down the online application server and domain Oracle, RPAS
daemon to lockout users
vdate.sh inc export Oracle
cron_export.sh Oracle
Copy/FTP vdate.int file from RPAS
${INTEGRATION_HOME}/vdate to
${AIPDOMAIN}/interface/import/meas
Copy/FTP AIP Online export files from RPAS
${ONL_OUTBOUND_DIR} to
${AIPDOMAIN}/interface/export
Copy/FTP RMS data files to ${RAW_RMS_DATA_DIR}. RPAS
Perform uncompress and un-tar operations.
aip_t_master.ksh RPAS
Copy/FTP all external/custom data files to RPAS
${AIPDOMAIN}/interface/rms. Perform uncompress and
un-tar operations.
aip_batch.sh check_process_external_data RPAS
aip_batch.sh prep_onl_data RPAS
aip_batch.sh merge_hierarchies RPAS
aip_batch.sh convert_hierarchies_for_loading RPAS
aip_batch.sh reconfig_domain_partitions RPAS
aip_batch.sh load_all_hierarchies RPAS
aip_batch.sh load_onl_data RPAS
aip_batch.sh load_rms_dm_data RPAS
aip_batch.sh create_alerts RPAS
aip_batch.sh load_non_rms_external RPAS
aip_batch.sh auto_commit_wkbooks_batch RPAS
aip_batch.sh run_dm_batch RPAS
aip_batch.sh export_dm_data RPAS
Copy/FTP RPAS export files from Oracle
${AIPDOMAIN}/interface/export to
${INTEGRATION_HOME}/data.
cron_import.sh dm Oracle
Copy/FTP SKU dimension export files to Oracle
${ONL_INBOUND_DIR}. Perform uncompress and un-tar
operations.
cron_import.sh sku-attributes Oracle

pre_scale.sh Oracle
Copy or FTP the RDF forecast files to RPAS
${INTERFACE_FORECAST_DIR}. Perform uncompress
and un-tar operations.
aip_batch.sh check_load_forecast_data RPAS
aip_batch.sh purge_low_variability_advance RPAS
aip_batch.sh purge_truncate_history RPAS
aip_batch.sh copy_sister_data RPAS
Copy/FTP RMS and custom OM data files to Oracle
${ONL_INBOUND_DIR}. Perform uncompress and un-tar
operations.
cron_import.sh om Oracle

Critical Path Tasks

The diagram below displays the Critical Path Tasks process flow diagram.
Critical Path Tasks Process Flow Diagram
Note: The release of Purchase Orders can be executed before

the release of Transfers; however the release of Transfers and
Purchase Orders MUST NOT run in parallel when using the
tsf_po_export.sh script to extract the Transfers and/or POs
to a flat file.
Note: cron_release must not be run for a second time until
tsf_po_export.sh has completed for the previous set.
The table below provides information about the critical path steps that need to be
performed.
Copy/FTP the RMS inventory position files to RPAS

${AIPDOMAIN}/interface/rms. Perform
uncompress and un-tar operations.
aip_batch.sh check_process_inventory_data RPAS
aip_batch.sh load_rms_replenishment_data RPAS
aip_batch.sh run_replenishment RPAS
aip_batch.sh export_replenishment_data RPAS
aip_batch.sh send_replenishment_to_online RPAS
Copy/FTP RPAS export files from Oracle
${AIPDOMAIN}/interface/export to
${INTEGRATION_HOME}/data.
cron_import_order.sh order_type_transfer dest_type_all Oracle
cron_release.sh order_type_transfer dest_type_all Oracle
tsf_po_export.sh (for RIB bypass) Oracle
cron_import_order.sh order_type_purchase dest_type_all Oracle
scale_order.sh releasing_today Oracle
merge_order.sh releasing_today Oracle
cron_release.sh order_type_purchase dest_type_all Oracle
tsf_po_export.sh (for RIB bypass) Oracle
When bypassing the RIB, copy/FTP the AIP Oracle
purchase order and transfer files from
${ONL_OUTBOUND_DIR} to RMS.

Post Critical Path Tasks

The diagram below displays the Post Critical Path Tasks process flow diagram.
Post Critical Path Tasks Process Flow Diagram

The table below provides information about the post-critical path steps that need to be
performed. . These steps include the scaling module scripts which are only required by
those Retailers who are supplier scaling and/or container scaling.
Script or Action Parameter(s) Platform

Location
scale_order.sh releasing_in_future Oracle

merge_order.sh releasing_in_future Oracle
post_scale.sh Oracle
aip_batch.sh post_ocs_import RPAS
aip_batch.sh run_replenishment_post_processing RPAS

Location
aip_batch.sh run_dm_alerts RPAS

aip_batch.sh export_dm_alerts RPAS
cron_import.sh alerts Oracle
Restart the AIP Online application server. Oracle
aip_batch.sh run_srp_alerts RPAS
aip_batch.sh run_wrp_item_alerts RPAS
aip_batch.sh run_wrp_network_alerts RPAS
aip_batch.sh run_replenishment_alerts_post_processing RPAS
aip_batch.sh auto_build_wkbooks_batch RPAS
Start the AIP RPAS domain daemon. RPAS
cron_post_release.sh 1. order_type Oracle
2. dest_type
See the details of this script in the AIP Operations
Guide for the possible valid values of these 2
parameters.
cron_purge.sh 1. order_type Oracle
2. dest_type
See the details of this script in the AIP Operations
Guide for the possible valid values of these 2
parameters.

Interval Batch Tasks

The first opportunity that AIP will have to apply new replenishment settings to the plan
is the very next replenishment batch run that occurs after the data is loaded from RO.
AIP assumes that RO or the legacy system which is providing the optimized
replenishment settings has set the appropriate effective date for the data. The following
examples illustrate when the data will be applied to the AIP replenishment plan.
Example 1: For a particular virtual date the replenishment batch run occurs after the load
of RO data into AIP. The loaded replenishment methods and thresholds will be used in
the upcoming replenishment batch run.
Example 2: This order of execution is only valid if RO RPAS_TODAY is set to Vdate + 1

before extracting the data because the data loaded from RO will not be used in
replenishment planning until the next replenishment batch run that occurs on vdate + 1.
The user must see the loaded data effective tomorrow, instead of today.
Export to RO
The diagram below displays the export of data from AIP to RO.
The table below provides information about the export steps that need to be performed.
These steps assume the data exported from AIP will be limited by the RO Update Flag,
and that this information is specified by the RO User. It also assumes that the next set of
sku/locations to be exported/optimized is not known until a time after the last import of
replenishment data (therefore the file is not imported with the last set of optimized
replenishment data files),
Copy/FTP the RO Update SKU/locations to RPAS

${RO_INPUT}. Perform uncompress and un-tar
operations.
aip_import_from_ro.sh RPAS
aip_export_to_ro.sh RPAS

Import from RO
The diagram below displays the import of replenishment optimization data from RO.
The table below provides information about the export steps that need to be performed.

Location
Copy/FTP the RO files to ${RO_INPUT}. RPAS

Perform uncompress and un-tar operations.
aip_import_from_ro.sh RPAS
Purging
Purging data is important to maintaining database sizing as well as improving user
experience. Purging data decreases the amount of data that a user has to sort through in
order to get to the data that is desired.
Purging should be executed on a routine basis of weekly or monthly
The table below provides information about purging data.

Location
aip_purge.sh Oracle
Copy/FTP AIP Online purge_hierarchy.tar.Z file from RPAS
${ONL_EXPORT_DIR} to
${AIPDOMAIN}/interface/purge/import
purging_aip_batch.sh purging_prep_oracle_data RPAS
purging_aip_batch.sh purging_process_hierarchies RPAS
Copy/FTP additional hierarchies to ${AIPDOMAIN}/input RPAS
purging_aip_batch.sh purging_load_hierarchies RPAS
purging_aip_batch.sh purging_process_measures RPAS

5
AIP Online Configurations
AIP Online consists of three different but equally important environments: a UNIX-based
platform for executing RETL scripts and batch shell scripts; an Oracle database; and an
application server for hosting the web-based Java graphical user interface (GUI). Each
environment requires specific values, properties, and files to be configured in order to
fully implement the AIP Online portion of the solution.
AIP Online UNIX Environment

The batch scripts which execute on the data stored in the Oracle database run on a UNIX-
based platform. RETL must be installed and it must be able to access the AIP Oracle
database. In order to execute the batch scripts config.xml, the integration directories, and
any files shared by the Online and RPAS must be setup and operational.
config.xml
The RETL interface process, run from a UNIX-based platform, is designed to be fully
automated once configured. In addition to the environment variables described above
config.xml is required when invoking the RETL scripts. This file should be located in the
root integration directory on the UNIX server in which the AIP Online application is
installed.
This configuration file contains the database connection information required by RETL
for performing import and export operations. Refer to the RETL documentation for
detailed descriptions of element definitions. There are two operator sections that need to
be completed, one for oraread and one for orawrite. The oraread section defines the
properties required for all export operations on the database and the orawrite section
defines these for all import operations. Though both contain similar attributes, it’s
imperative that each section is defined as needed for the specific Oracle database
installation. This information is also dependent on the requirement that all databases can
be connected to via a properly defined tnsnames file and reachable by SQLPlus.
Example config.xml file:
<CONFIG>
<DEFAULTS operator="oraread">
<PROPERTY name="arraysize" value="5000" />
<PROPERTY name="dbname" value="DEV029i"/>
<PROPERTY name="connectstring" value="aiprmsint130user/retek"/>
<PROPERTY name="jdbcdriverstring" value="oracle.jdbc.driver.OracleDriver" />
<PROPERTY name="jdbcconnectionstring" value="jdbc:oracle:oci:@ " />
</DEFAULTS>
<DEFAULTS operator="orawrite">
<PROPERTY name="dbname" value="DEV029i"/>
<PROPERTY name="dbuserid" value="aiprmsint130user/retek"/>
<PROPERTY name="method" value="conventional"/>
<PROPERTY name="jdbcdriver" value="oci"/>
</DEFAULTS>
</CONFIG>
AIP Online Configurations 39

Integration Directories
The following directories must be created by the system administrator. They are required
and will cause errors if absent:
$INTEGRATION_HOME/inbound
$INTEGRATION_HOME/archive
Shared Files
When the AIP RPAS module is not installed on the same server as the AIP ONLINE
module, the shared credential and verification files must be present in both locations.
The following table lists the files and the appropriate location on the UNIX server. Copy
the files from the AIP RPAS server location to the AIP ONLINE server. Where the
destination directory does not exist, one should be made. All server locations are written
in reference to the aip_env_online.sh environment variables.
File Name Location
prep_files.sh $INTEGRATION_HOME/scripts/
bsa_prep_files.config $INTEGRATION_HOME/config
bsa_archive.sh $INTEGRATION_HOME/bsa
bsa_check_for_required_files.sh $INTEGRATION_HOME/bsa
bsa_common.sh $INTEGRATION_HOME/bsa
bsa_cred.sh $INTEGRATION_HOME/bsa
bsa_env.sh $INTEGRATION_HOME/bsa
bsa_prep_files.sh $INTEGRATION_HOME/bsa
bsa_logger.sh $INTEGRATION_HOME/bsa
bsa_para.sh $INTEGRATION_HOME/bsa
bsa_sort.sh $INTEGRATION_HOME/bsa
bsa_sql.sh $INTEGRATION_HOME/bsa
bsa_verify.sh $INTEGRATION_HOME/bsa

Importing Configuration Files

The files imported into AIP Online are bundled (in a *.tar file) together into logical
groupings based on dependencies and availability within the batch window. Each RETL
import file has one, and only one, corresponding script that executes the loading of the
file into the database. The execution of all RETL import scripts is controlled by a set of
configuration files that list the load scripts to be run, and the order in which they will
run. Each configuration file corresponds to one *.tar file.
The configuration files can be modified to prevent execution of load scripts for files
which will never be present (e.g. they are optional files for functionality that will not
be used by the business). For example, “Sister Stores” may not be available in the
merchandising system to provide to AIP, or purged order numbers may not be
available for PO number recycling. The line containing the path to the “_in.sh” load
script should be deleted or commented out.
The configuration files are a command line argument passed to the parent script,
process_aiponline_data.sh. A modified configuration file or a specially constructed
configuration file can be passed to the parent script to aid the initial, first day import,
restart/recovery, or special ad hoc processing.
The parent script will execute all load files listed in the configuration file passed to it.
A warning message will be logged when the load script is executed but the
corresponding data file is not present.
The import configuration files are listed in the following table along with any potentially
optional load scripts. Optional load scripts are those which are not critical to
replenishment processing. They are related to functionality outside of replenishment or
provide special information that can be used as an alternative to the standard processing.
Settings in both AIP RPAS import/export configuration files and AIP Online import
configuration files should reflect the file requirements consistently.
Configuration File Optional Load Scripts
import_hierarchy.config
import_dm.config dm_banded_comm_in.sh
dm_is_prepriced_in.sh
dm_dir_store_frmt_pksz_in.sh
dm_dir_store_pksz_in.sh
dm_sis_store_in.sh
dm_sis_wh_in.sh
dm_store_frmt_pksz_in.sh
dm_store_pksz_in.sh
dm_value_added_comm_in.sh
dm_wh_prom_dates_in.sh
import_dm_alerts.config
import_sale_date.config
import_om.config om_po_recycling_in.sh
import_sku_attribute.config commodity_weight_volume_in.sh
commoditiy_cost_in.sh
Export Configuration Files
Export Configuration Files

The files exported from AIP Online are bundled (.tar) together into logical groupings
based on dependency. Each RETL export file has one, and only one, corresponding script
that executes the extraction of the file data from the database. The execution of all RETL
extract scripts is controlled by a set of configuration files that list the export scripts to be
run, and the order in which they will run.
The configuration files can be modified to prevent execution of export scripts for files
which will never be present (e.g. they are optional files for functionality that will not
be used by the current client). For example, if “Sister Stores” are never imported then
the copy date never needs to be extracted for AIP on RPAS.
Note: Files that are optional for import may not be optional
for export. Some import files are optional because the data
can be loaded. Alternatively the data can be entered in the
DM online application. Regardless of how the data gets into
the Oracle database, this data is required by AIP RPAS to
run replenishment batch.
The configuration files are a command line argument passed to the parent script,
process_aiponline_data.sh. A modified configuration file or a specially constructed
configuration file can be passed to the parent script to aid restart/recovery or special
ad hoc processing.
The export configuration files are listed below.
export_hierarchy.config
export_dm.config
export_tsf_po.config
export_scale.config
export_hierarchy_purge.config
Oracle Database
The configurations performed in the Oracle database affect how the business uses AIP.
Each setting will be used when performing some action of supply chain setup—either
automatically or manually—or order execution and maintenance.

Oracle Database
SYSTEM_PARAMETERS
The following table contains the configuration parameters contained in the
SYSTEM_PARAMETERS database table, the default value assigned to the parameter, and
a description about what the parameters controls. The default parameter values in the
table need to be set according to your individual business needs.
Configuration Parameter Default Description

Value
AIP_VERSION 13.1.2 The currently installed version of AIP Online.

AUTO_ASSIGN_CASE_WT N Indicates whether case weights should be
automatically assigned for new SKU/pack size
combinations.
This flag and the assignment process is
deprecated.
AUTO_ASSIGN_OF_SKUS_TO_PROFILES Y Indicates whether to automatically assign the
SKU of new SKU/supplier combos to profiles.
AUTO_ASSIGN_ORDER_CYCLES Y Indicates whether to calculate the store lead time
prior to the store opening. If no calculation is
performed the profile order cycle and any
applicable exceptions will be used.
AUTO_ASSIGN_ORDER_MULTIPLES Y Indicates whether order multiples should be
combinations.
AUTO_ASSIGN_PALLET_MULT N Indicates whether pallet multiples should be
combinations.
AUTO_ASSIGN_STACKING_FLAG N Indicates whether stacking flag should be
combinations.
This flag and the assignment process is
deprecated.
AUTO_ASSIGN_STORE_FORMAT_PACK_SIZE Y Indicates whether to automatically assign a store
format pack size for warehouse and supplier
sources.
AUTO_CREATION_OF_DELIVERY_GROUP Y Indicates whether to automatically create delivery
groups for new supplier.
AUTO_CREATION_OF_ORDER_GROUP Y Indicates whether to automatically create order
groups for new supplier.
AUTO_CREATION_OF_PROFILE Y Indicates whether to automatically create profiles
for new suppliers.
AUTO_RANGE_BY_SHIP_TO_ONLY N Indicates whether to automatically range new
SKU packs only to warehouses that match the
supplier Ship To value. Otherwise ranges to all
valid SKU pack/warehouse combinations.
AUTO_RANGE_DEMAND_GROUP Y Indicates whether to automatically range demand
group for new SKU.
Oracle Database

Value
CONTAINER_SCALING_GLOBAL_FLAG Y Indicates whether or not Container Scaling is

enabled at a global level. Valid values are Y and
N.
CONTINUE_ORDER_SENDER_BEAN_FOR_PO Y Switch to start/stop polling for purchase orders
by order sender bean. Possible values are Y (start)
and N (stop).
CONTINUE_ORDER_SENDER_BEAN_FOR_TSF Y Switch to start/stop polling for transfer orders by
order sender bean. Possible values are Y (start)
and N (stop).
COPY_SISTER_STORE Y Indicates whether to copy sister store to
associated new store.
COPY_SISTER_WAREHOUSE Y Indicates whether to copy sister warehouse to
associated new warehouse.
DEFAULT_CASE_WT 1 The default case weight used by the case weight
automatic assignment process. This value must be
between .1 and 9999.99, inclusive.
DEFAULT_DMG_SIZE 1 The demand group size inserted for all
automatically created demand groups. Valid
values are 1 (small), 2 (medium), 3 (large), 4 (x-
large).
DEFAULT_DMG_TYPE 0 The demand group type inserted for all
automatically created demand groups. Valid
values are 0 (cases), 1 (merchandising unit).
DEFAULT_PALLET_SETTING_USE_PALLET_HEIG N Indicates whether to use pallet height in pallet
HT settings for system generated delivery groups.
DEFAULT_PALLET_SETTING_USE_PALLET_WEIG N Indicates whether to use pallet weight in pallet
HT settings for system generated delivery groups.
DEFAULT_STACKING_FLAG 0 The default stacking flag used by the order
multiple automatic assignment process. Valid
values are: 0 = Yes, 1 = Same, 2 = No. Note that
Same implies that only item A can be stacked on
top of item A.
DEFAULT_VEHICLE_FOOTPRINT 22 Indicates the default vehicle footprint for system
generated delivery groups.
DEFAULT_VEHICLE_HEIGHT 1 Indicates the default vehicle height for system
generated delivery groups.
DEFAULT_VEHICLE_MINIMUM_DROP 0 Indicates the default vehicle minimum drop for
system generated delivery groups.
DEFAULT_VEHICLE_WEIGHT_LIMIT 99999 Indicates the default vehicle weight limit for
system generated delivery groups.
DIFFERENT_ORDER_MULTIPLE_FLAG Y Indicates if there is more than one order multiple
for the scaling group assignments.
This parameter is used in PO scaling.

Oracle Database

Value
DLG_OG_VALIDATION_IND Y This property indicates whether the validation

which checks if there is a delivery group and/or
order group assigned for the given demand
group, destination, and effective date should
execute.
DMG_ASSIGNMENT_METHOD 1 The value 1 indicates that new pack sizes
associated with an existing SKU will be assigned
to the existing SKU’s demand group. The value 2
indicates that each new SKU/pack size will be
assigned to a unique demand group.
EXTENDED_PLANNING_HORIZON 7 The number of days beyond the planning horizon
for which AIP Online will extract data. This
ensures proper order quantities for delivery on
the last day of the planning horizon and must
match the corresponding AIP RPAS
implementation parameter.
GATHER_SCHEMA_STATS Y Switch to turn ON/OFF schema analyze option.
A value of Y will turn the option ON and N will
turn the option OFF.
GATHER_SCHEMA_STATS_ESTIMATE_PERCENT 100 The estimate percent to be used for gathering
schema statistics.
INVENTORY_TRACKING_LEVEL EACHE The level at which inventory is tracked. Valid
S values are PACKS and EACHES. If the value is
EACHES, then the
DMG_ASSIGNMENT_METHOD parameter will
be overridden and all pack sizes of a SKU will be
assigned to the same demand group.
LOG_DEBUG N Indicates whether debug messages will be written
to DBMS_OUTPUT.
MAX_WALKING_LEAD_TIME 22 Indicates the maximum lead time to use in
calculating a walking lead time.
MIN_PLANNING_HORIZON 35 Minimum number of planning days for any SKU.
This value is used in SKU planning horizon when
there exists no SKU level planning horizon
exception or class level planning horizon default.
MULTIPLE_DELIVERY_DATE_FLAG Y Indicates if there are multiple delivery dates for a
warehouse schedule. This parameter is used in
PO scaling.
OFF_SUPPLY_OFFSET 3 The corporate off supply offset value is used to
calculate off-supply dates based on off-sale dates
imported from the merchandising system. Off-
supply dates will be set to: [off-sale date] -
OFF_SUPPLY_OFFSET.
ONL_SCHEMA_OWNER USER The username of the AIP Online schema owner.
Oracle Database

Value
ON_OFF_SUPPLY_OVERWRITE_IND Y Indicates whether or not to update the existing

on/off supply dates when importing sale dates. A
value of Y will update both on/off supply and
on/off sale dates. A value of N will update only
the on/off sale dates.
ON_SUPPLY_OFFSET 3 The corporate on supply offset value is used to
calculate on-supply dates based on on-sale dates
imported from the merchandising system. On-
supply dates will be set to: [on-sale date] -
ON_SUPPLY_OFFSET.
PO_INTERFACE_METHOD M Determines whether purchase orders are
interfaced to external systems via XML messages
(M) or text files (F).
PULL_ACROSS_STOCKLESS_DAYS N Indicates whether orders can be pulled across
stockless days when performing Supplier Scaling
and Container Scaling. Valid values are Y for yes
and N for no.
REBUILD_INDEXES_POST_RELEASE Y A value of Y (recommended) will rebuild
unusable indexes after all orders are released. A
value of N will rebuild the indexes during LOAD.
This flag and the rebuild process is deprecated.
RESET_SEQUENCE_FOR_SCALING Y Indicates if IDs used in order scaling start from
same value on every load.If N, the order id starts
from sequence NEXTVAL
RESTART_SCALING_FROM_SAVEPOINT Y Indicates if system recovery should be used for
scaling. If Y then the scaling starts from the point
that it failed earlier, else this starts from
beginning.
SCALING_HORIZON_MAX 35 The Scaling Horizon Max is a maximum cap to
individual Scaling Group horizon values. All
individual Scaling Group horizon values will be
capped by this value.
SCHEDULE_EXCEPTION_OFFSET 9 Indicates the number of days after store open that
schedule exceptions copied in the sister store
process will begin.
SCHEMA_STATS_DEGREE 8 Controls parallelization of function
gen_schema_stats.
SEQUENCE_CACHE_BULK_INSERT_VALUE 20 This is the recommended cache value for the
sequences while doing bulk insert.
SET_WH_ORD_MULT 1000 Bulk fetch limit for the procedure/function.
SISTER_STORE_OFFSET_WEEKS 12 Indicates the maximum number of weeks before
store open that a sister store copy will take place.
SISTER_WAREHOUSE_OFFSET_WEEKS 12 Indicates the maximum number of weeks before
warehouse open that a sister warehouse copy will
take place.

Oracle Database

Value
SUPPLIER_MINIMUM_SCALING_GLOBAL_FLAG Y Indicates whether or not Supplier Minimum

Scaling is enabled at a global level. Valid values
are Y for yes and N for no.
SYSTEM_HIGH_DATE 9999123 The default high date used by the system. Date
1 format is yyyymmdd.
TABLE_STATS_DEGREE 8 Controls parallelization of function
gen_table_stats.
TSF_INTERFACE_METHOD M Determines whether transfers are interfaced to
external systems via XML messages (M) or text
files (F).
USE_DBMS_STATS_AUTO_SAMPLE_SIZE Y A value of Y (recommended) will use
AUTO_SAMPLE_SIZE as estimate_percent in gen
stat functions of aip_util package. A value of N
will use NULL in gen_table_stats and
GATHER_SCHEMA_STATS_ESTIMATE_PERCE
NT in gen_schema_stats.
VALID_SOURCE_VALIDATION_IND Y Indicates whether to execute the validation to
determine whether a source is valid. A valid
source is one that is currently acting as a
destination with a split % against it or where all
the commodity pack sizes for the demand group
are pending de-ranged.
VDATE 1999123 Used to maintain the same date throughout the
1 batch run. Functions get_vdate, set_vdate, and
inc_vdate of the aip_util package are used to
retrieve, set, and increment. Date format is
YYYYMMDD.
WALKING_LEAD_TIME_OFFSET 45 Indicates the number of days before a store open
date to begin calculating a walking lead time for
that store.
WIP_IND N Indicates if the WIP subsystem is being used.
WIP-related extracts will only be performed if this
value is Y.
Oracle Database
In addition to the parameters listed above there a number of parameters that might be
tweaked for performance reasons. These parameters begin with the “BFL” prefix and
serve to limit the number of records retrieved at one time when executing a Bulk Fetch.
The parameters are specific to a procedure or function.
RESTART_CONTROL
The Oracle RESTART_CONTROL table defines the number of parallel subprocesses that
a high data volume process uses in shell script. For example:
Importing STORE SOURCE data from RPAS into Online
Exporting STORE SOURCE data from Online to RPAS
Importing INTO-STORE PURCHASE ORDERS from RPAS to Online
Importing INTO-STORE Transfers from RPAS to Online
Importing ON-SALE-OFF-SALE data from RPAS to Online
Executing ORDER-SCALING process in AIP Online.
The column NUM_THREADS controls the degree of parallelism while executing the
processes defined in column PROGRAM_NAME of this table.
ORDER_NUMBER
The Oracle ORDER_NUMBER table defines the valid range of order numbers for
purchase orders and transfers. The range of values should not overlap the range of
values allocated to any other system capable of generating orders. Update the
ORDER_NUMBER table to reflect the range of purchase order and transfer numbers that
are appropriate for AIP.
ORDER_PURGE_PERIOD
The Oracle ORDER_PURGE_PERIOD table defines the number of day an order remains
in the system after it has been set to a Closed status. Review the default purge periods
inserted in the table at installation time, and update the values for purchase order
purging and transfer purging when needed.
ORDER_DEFINITION
In AIP Online orders are held at order detail level (i.e. order line time level). When an
order number is generated, it is generated at order header level. The Oracle
ORDER_DEFINITION table holds information that specifies how order line items are
grouped into to order headers.
The following options are available for defining the level of grouping:
Source - Indicates if order sources are used in order header roundup.
SKU - Indicates if SKUs are used in order header roundup.
Pack Size - Indicates if pack sizes used in order header roundup.
Destination - Indicates if the order destinations are used in order header roundup.
Delivery Date - Indicates if delivery dates are used in order header roundup.
In the example below SKU (commodity) and pack size are not used in the order
definition. This means that for each order type an order number will be assigned to each
unique combination of source, destination, and delivery date. This will result in one too
many SKU pack sizes being grouped under a single order number for an order type.

Oracle Database
Destination Order Type Use Use Use Usedest Use

Source Commodity Pack_Size Delivery_Date
Warehouse Purchase Order Y N N Y Y

Store Purchase Order Y N N Y Y
Warehouse Transfer Y N N Y Y
Store Transfer Y N N Y Y
Review the ORDER_DEFINITION table and change the settings if needed.
Note: The only supported configurations for this release of

AIP are the defaults provided in the table above and Y for all
columns. These two configurations can be applied per
destination/order type. They do not need to be applied
uniformly across destination or order type.
ORDER CYCLES
The default order cycles created at implementation time are used by the batch processes
that automatically create Profiles and Order Groups. These order cycles can be modified
to match your business needs however they must remain in sync with the same special
default order cycles created in the RPAS platform.
Store Order Cycles

Store order cycles are assigned to a profile when it is automatically generated by the
batch processes. The following Store Order Cycles exist for these procedures
Warehouse profiles (PRFWS)
Direct Profiles (PRFVS).
The following store order cycles are created during installation.
Order Cycle Sun Mon Tues Wed Thurs Fri Sat
PRFVS 15
PRFWS 1 1 1 1 1 1 1
Store Order cycles are maintained in two tables, STORE_ORDER_CYCLE and

STORE_ORDER_CYCLE_LEAD_TIME.
STORE_ORDER_CYCLE
STORE_ORDER STORE_ORDER STORE_ORDER_CYCLE_NAME STORE_ORDER

_CYCLE_ID _CYCLE_CODE _CYCLE_LENGTH
2 PRFVS New Sup To Store Default OC 7

3 PRFWS New Sup Warehouse to Store OC 7
Oracle Database
STORE_ORDER_CYCLE_LEAD_TIME
STORE_ORDER STORE_ORDER RELEASE PLACEMENT

_CYCLE_ID _CYCLE_SEQ _LEAD_TIME _LEAD_TIME
2 1 -1 -1
2 2 15 15
2 3 -1 -1
2 4 -1 -1
2 5 -1 -1
2 6 -1 -1
2 7 -1 -1
3 1 1 1
3 2 1 1
3 3 1 1
3 4 1 1
3 5 1 1
3 6 1 1
3 7 1 1
The STORE_ORDER_CYCLE_LENGTH is 7; therefore there is one row in the

STORE_ORDER_CYCLE_LEAD_TIME table for each of the 7 days in the order cycle.
Changing the length of the Store order cycle would require additional rows to be
added to the STORE_ORDER_CYCLE_LEAD_TIME table such that the
STORE_ORDER_CYCLE_SEQ runs from 1 to n where n is the order cycle length. The
ONLY supported lengths are 7, 14, or 28. DO NOT choose a length other than those
values.
A RELEASE_LEAD_TIME or PLACEMENT_LEAD_TIME value of -1 indicates
“blank” on the screen or no lead time.
The PLACEMENT_LEAD_TIME value MUST be equal to or greater than the
RELEASE_LEAD_TIME. Therefore you cannot change one and not the other. The
PLACEMENT_LEAD_TIME must NOT contain a value other than -1 when the
RELEASE_LEAD_TIME is -1.
Warehouse Order Cycles

Warehouse order cycles are assigned to an Order Group when it is automatically
generated by the batch procedures. The following Warehouse Order Cycles exist for
these procedures:
Warehouse sourced Order Groups (OGWW)
Supplier sourced Order Groups (OGVW)

Oracle Database
The following store order cycles are created during installation.
Order Cycle Sun Mon Tues Wed Thurs Fri Sat
OGVW 15
OGWW 1 1 1 1 1 1 1
Warehouse order cycles are maintained in two tables, ORDER_CYCLE and

ORDER_CYCLE_LEAD_TIME.
ORDER_CYCLE
ORDER_CYCLE ORDER_CYCLE ORDER_CYCLE ORDER_CYCLE COLLECTION

_ID _CODE _NAME _LENGTH _LEAD_TIME
1 OGVW New Supplier Default 7 -1

Order Cycle
2 OGWW New Supplier Whs to 7 -1
Whs Order Cycle
ORDER_CYCLE_LEAD_TIME
ORDER_CYCLE_ID ORDER_CYCLE_SEQ ORDER_LEAD_TIME
1 1 -1
1 2 15
1 3 -1
1 4 -1
1 5 -1
1 6 -1
1 7 -1
2 1 1
2 2 1
2 3 1
2 4 1
2 5 1
2 6 1
2 7 1
The warehouse order cycle length (ORDER_CYCLE_LENGTH) is 7; therefore there is

one row in the ORDER_CYCLE_LEAD_TIME table for each of the 7 days in the order
cycle. Changing the length of the warehouse order cycle would require additional
rows to be added to the ORDER_CYCLE_LEAD_TIME table such that the
ORDER_CYCLE_SEQ runs from 1 to n where n is the order cycle length. The ONLY
supported lengths are 7, 14, or 28. DO NOT choose a length other than those values.
An ORDER_LEAD_TIME value of -1 indicates ‘blank’ on the screen or no lead time.
Oracle Database
The COLLECTION_LEAD_TIME must be equal to or less than the smallest

ORDER_LEAD time for the order cycle. For the existing, unmodified, order cycle
OGVW, the COLLECTION_LEAD_TIME can be at most 15. For the existing,
unmodified, order cycle OGWW, the COLLECTION_LEAD_TIME can be at most 1.
DATA_PURGE_PARAMETERS
In order to purge invalid or ineffective hierarchy data from AIP Online tables, purge
parameters are used to configure the purge ages. These parameters are defined in a table
called PURGE_PARAMETER and are used by purging script aip_purge.sh to identify
invalid/ineffecttive data for purging. The default parameter values in the table need to
be set according to individual business needs.
Name Value Description
AUDIT_PURGE_FREQUENCY W The frequency at which audit tables are purged. Valid

values are D (Daily), W (Weekly), M (Monthly), H
(every 6 months), Y (Yearly)
CHAMBER_PURGE_AGE 60 The number of days a chamber remain in the system
before being purged, beginning from when the
chamber was set to a closed status.
CLOSED_ALERT_PURGE_AGE 14 The number of days a closed alert remain in the system
before being purged, beginning from when the alert
was closed.
COMMODITY_PACK_SIZE_PURGE_ 30 The number of days a SKU-pack size remain in the
AGE system before being purged, beginning from when the
SKU-pack size does not appear in the daily import
from RPAS.
DELIVERY_GROUP_PURGE_AGE 60 The number of days a delivery group remain in the
system before being purged, beginning from when the
delivery group does not have at least one demand
group assigned to it.
ENT_AUDIT_PURGE_AGE 90 The number of days a END_AUDIT record remain in
the system before being purged, beginning from when
the record was created.
LAST_AUDIT_PURGE_DATE <SYSDAT The date the audit tables were last purged. Used in
E> conjunction with the AUDIT_PURGE_FREQUENCY to
determine when audit tables are purged.
NON_ORDER_NON_RELEASE_PURGE_ 180 The number of days a non-order or non-release date
AGE record remain in the system after it has passed before
being purged.
ON_SUPPLY_OFF_SUPPLY_PURGE_ 45 The number of days an on supply/off supply record
AGE remain in the system before being purged, beginning
from the off sale date.
ORDER_GROUP_PURGE_AGE 60 The number of days an order group remain in the
order group does not have at least one demand group
assigned to it.

Oracle Database
Name Value Description
PLANNING_GROUP_PURGE_AGE 90 The number of days a planning group remain in the

planning group is not assigned to at least one network
group.
PROFILE_PURGE_AGE 60 The number of days a profile remain in the system
before being purged, beginning from when the profile
does not have at least one SKU assigned to it.
SCALING_GROUP_PURGE_AGE 60 The number of days a scaling group remain in the

order group does not have at least one SKU assigned to
it.
STORE_ORDER_CYCLE_PURGE_AGE 366 The number of days a store order cycle remain in the
order cycle is not assigned to at least one profile.
STORE_PURGE_AGE 90 The number of days a store remain in the system before

being purged, beginning from when the store does not
appear in the daily import from RPAS.
SUPPLIER_COMMODITY_PACK_ 30 The number of days an on supplier/sku link remain in

SIZE_PURGE_AGE the system before being purged, beginning from when
the link does not appear in the daily import from
RPAS. This value should be less than or equal to
COMMODITY_PACK_SIZE_PURGE_AGE and
SUPPLIER_PURGE_AGE values.
SUPPLIER_PURGE_AGE 90 The number of days a supplier remain in the system

supplier does not appear in the daily import from
RPAS.
WAREHOUSE_ORDER_PURGE_AGE 366 The number of days a warehouse order cycle remain in

the system before being purged, beginning from when
the order cycle is not assigned to at least one order
group.
WAREHOUSE_PURGE_AGE 90 The number of days a warehouse remain in the system

warehouse does not appear in the daily import from
RPAS.
Oracle Database
WH_TYPE_INITIAL_PACK_TYPE
The Oracle WH_TYPE_INITIAL_PACK_TYPE table contains the warehouse type and
pack type associations that are used for defaulting warehouse orderable units and order
multiples. When the AIP Automated Data Maintenance batch processes run the pack
type value defined for the respective process will define which pack size should be used
for assignment first. If the pack size associated with the pack type is not valid for a given
warehouse of the assigned warehouse type, additional logic in the batch will determine
the next valid pack size to use.
The constraints on the table will need to be modified if additional warehouse types are
added to the system via the STOCKING_POINT table. The warehouse type describes the
destination warehouse type.
The process type identifies the process to which the warehouse type/pack type setting
applies – either warehouse orderable units or order multiples.
SUPPLIER
Prior to importing any supplier data, the column constraint on the SHIP_TO column
should be modified to match the SHIP_TO values that will be imported from the
merchandising system. If additional values are being added, the Ship-to source and
destination mappings must also be added to the SHIP_TO_WH_TYPE_SOURCE and
SHIP_TO_WH_TYPE_DEST tables.
STOCKING_POINT
Prior to importing any warehouse data, the column constraint on the WH_TYPE column
should be modified to match the WH_TYPE values that will be imported from the
merchandising system.
SHIP_TO_WH_TYPE_SOURCE
This Oracle table contains the mappings between Supplier SHIP_TO values and the
appropriate sources. These values are used when automatically generating Delivery
Groups and Order Groups. When the WH_TYPE column is null, the supplier will be
used as the source. A non-null WH_TYPE value indicates the warehouse that the
supplier ships to is an intermediate warehouse that does not ship directly to the store.
When the WH_TYPE is populated, the source of the Delivery Groups and Order Groups
created will be Warehouses that match the WH_TYPE.
SHIP_TO_WH_TYPE_DEST
This Oracle table contains the mappings between Supplier sources
(SHIP_TO_WH_TYPE_SOURCE) and the destinations. The destinations are used to
determine the valid warehouse chambers to assign to the delivery groups and order
groups. One SHIP_TO value can map to many sources and destination WH_TYPEs.

Oracle Database
ALERT_DEFINITION
Every alert is assigned a priority based on the type of the alert. The priority assigned to
each alert type can be set in the ALERT_DEFINITION table. The priority setting currently
has no bearing on the rest of the system. It is simply a visual indicator of importance and
search mechanism for the user.
Note: Updating the alert type priority in the

ALERT_DEFINITION table changes the priority of any
previously existing alerts corresponding to the alert type
being modified
ALERT_DEFINITION_DESC
The Oracle ALERT_DEFINITION_DESC table contains the text of each alert, and the
corresponding SHORT_DESC or alert type description. The SHORT_DESC value is
displayed to the user as search criteria. You may modify the text of the SHORT_DESC,
however, the screen is optimized to display the values provided in the installation. It is
not recommended that you modify the LONG_DESC as the correct placement of the data
displayed to the user depends on the structure of the LONG_DESC text.
The LONG_DESC and SHORT_DESC can be translated for another LANG and
COUNTRY if desired.
ALERT_STATUS_DESC
Each alert that is imported or generated by AIP Automated Data Maintenance batch will
be assigned a status. The status is displayed to the user in the DM online screen. The user
can then modify the status of the alert by selecting a status option from a drop-down list.
The status options displayed in the list and their descriptions are contained in the
ALERT_STATUS_DESC table.
Adding a Status
The ALERT_STATUS_CODE indicates the chronological order of the statuses displayed
on the screen as well as the code that is saved indicating the alert’s current status.
When adding a status:
The smallest value will be automatically assigned to every new alert.
The largest value will be considered the final status indicating no more work needs
to be completed related to the alert.
It must be added to every set of LANG/COUNTRY combinations. Therefore, the
same set of ALERT_STATUS_CODE values must exist for every LANG and
COUNRTY on the table.
AIP Application Server

The following properties files are used to configure the application during
implementation. All files are located in <aip app server install location>/config. Review
the values in the files for completeness and accuracy. There are additional properties
outlined below which must be manipulated when using the RIB with AIP.
db.properties
File Location: <aip app server install location>/config
This file contains configuration values that are related to the system’s database. This file
tells the DM Online and OM Online application how to connect to the database. After
installation, this file should contain the correct information because it is set in the initial
run of the AIP Online application. However, it is a good idea to review the values in the
files for completeness and accuracy. The following table provides a description of the
values contained in the db.properties file.
Configuration Value Description
common.prop.db This value defines the database that the system is utilizing. This value is set to
Oracle.
common.prop.oracle.sid This value is an Oracle parameter that defines the database name that the system
is utilizing. SID stands for system identifier.
common.prop.oracle.host This value is an Oracle parameter that refers to the database listener. This value
defines the “host:port” that the database listener is using. If Oracle database is
configured as clustered database, then this property should be left blank.
common.prop.oracle.schema This value is an Oracle parameter that defines the schema owner’s username. If
the username/password defined in common.prop.user is not the schema owner,
then this field must also be added and defined in order for the AIP Online
Administration screens to function properly.
common.prop.user This value is an Oracle parameter that defines the username/password of the
database. This can be a schema owner or a standard user.
common.prop.poolsize. This property represents the connection pool size that AIP application uses. This
does not include the connections that EJB might establish with the database.
Default value of this property is set to 40. The user is allowed to increase this
value but not to decrease it.
common.prop.oracle.dburl A required property to connect to clustered database. When using this
common.prop.oracle.host should be left blank.

main.properties
The following table provides a description of the properties contained in the
main.properties file. This file is used by the Java enabled applications: DM online, OM,
and RIB publication via the OrderSenderBean.
Property Description
base This must match the context root of the ear or war file. This is "/" for a production
system, or "/test1" for the 1st of several test systems on a single physical computer.
securemode This is set to "1" to force connections to switch from http (non-secure) to https
(secure) upon logon. This value can also be set to "0" to prevent the connection from
being switched from non-secure to secure mode.
setfileattr.rcapps.properties This defines a file to contain color attributes. The default setting is
rcapps.properties.
Publishing Purchase Orders and Transfer Data to RMS

You can configure AIP Online to publish Purchase Order and Transfer Data to the Oracle
Retail Merchandising System (RMS) via the Oracle Retail Integration Bus (RIB). Perform
the following procedure to enable RIB publication.
1. Uncomment the following parameters and change the OFF status of keys to ON
status where applicable in the main.properties file to activate the OrderSenderBean, which
calls the RIB publication routines:
#aip.prop.order.po.export=OFF
#aip.prop.order.tsf.export=OFF
#aip.prop.order.period.count=1
#aip.prop.order.period.start.1=08:00:00
#aip.prop.order.period.end.1=20:00:00
#aip.prop.order.time.interval=00:01:00
#aip.prop.order.po.message.family=XOrder
#aip.prop.order.po.message.type.name=msg_type
#aip.prop.order.po.queue.table.name=PO_MFQUEUE
#aip.prop.order.po.table.id.name= orderNo
#aip.prop.order.tsf.message.family=XTsf
#aip.prop.order.tsf.message.type.name=msg_type
#aip.prop.order.tsf.queue.table.name=TSF_MFQUEUE
#aip.prop.order.tsf.table.id.name= tsfNo
#aip.prop.order.max.message.bundle.size=10
#aip.prop.order.max.publishing.count=20
2. Save the main.properties file.
3. Have the application server administrator restart the server instance where the
OrderSenderBean and AIP Online application are deployed.
main.properties Publication Properties

The following table provides a description of the publication properties referenced in the
previous topic.
aip.prop.order.po.export This property must be set to ‘ON’ to do RIB-based publications Purchase

Orders. (PO_MFQUEUE)
aip.prop.order.tsf.export This property must be set to ‘ON’ to do RIB-based publications of

Transfers (TSF_MFQUEUE)
aip.prop.order.period.count The number of periods in the day during which the OrderSenderBean
will invoke RIB publication. This value must be greater than zero if RIB-
based publication is to be used. In addition, at least one of the above two
properties must in set to ‘ON’.
aip.prop.order.period.start.x The start time in HH:MM:SS format of period x where x is 1 …

aip.prop.order.period.count.
aip.prop.order.period.end.x The end time in HH:MM:SS format of period x where x is 1 …

aip.prop.order.period.count.
aip.prop.order.time.interval The amount of time in HH:MM:SS format between calls to

OrderSenderBean.checkAndPublish() function.
aip.prop.order.po.message.family The purchase order message family name. This value is required by the
RIB to ensure proper validation of message payloads. This value should
be set to ‘XOrder’.
aip.prop.order.po.message.type.name This value can be used to indicate if the message is a header-create,
header-update, detail-create, or detail-update message. Although
message types are used to order the OrderSenderBean query, this parameter
value is not currently used.
aip.prop.order.po.queue.table.name The AIP Online table which OrderSenderBean queries to check for Purchase
Order related messages awaiting publication. This value should be
‘PO_MFQUEUE’.
aip.prop.order.po.table.id.name This value is used to group functionally related message content. For
example, all message content related to purchase order number 123
would be grouped. This value should be ‘orderNo’.
aip.prop.order.tsf.message.family The transfer message family name. This value is required by the RIB to
ensure proper validation of message payloads. This value should be set to
‘XTsf’.
aip.prop.order.tsf.message.type.name This value can be used to indicate if the message is a header-create,
header-update, detail-create, or detail-update message. Although
message types are used to order the OrderSenderBean query, this parameter
value is not currently used.
aip.prop.order.tsf.queue.table.name The AIP Online table which OrderSenderBean queries to check for Transfer
related messages awaiting publication. This value should be
‘TSF_MFQUEUE’.

aip.prop.order.tsf.table.id.name This value is used to group functionally related message content. For
example, all message content related to transfer number 456 would be
grouped. This value should be ‘tsfNo’..
aip.prop.order.max.message.bundle.size The maximum number of message bundles to publish per call to

OrderSenderBean.checkAndPublish(). The default is 10, but this number should
be recalculated by the client based upon on-site performance testing.
aip.prop.order.max.publishing.count The maximum number of messages per message bundle. For example,
multiple Purchase Order header create message can be grouped in one
message bundle to improve performance. The default value is 20, but this
value should be recalculated by the client based upon on-site performance
testing.
rcapps.properties
These properties are applied to the main application login and navigation pages. These
property settings do not apply to the pop-up applet screens.
The color properties can be set to any 6 character hexadecimal value and are preceded
with the # symbol.
Hexadecimal color property examples:
#0000FF = blue
#FF0000 = red
The files defined for various properties are located off of the following base directory:
<OAS Home>/j2ee/<AIP Instance>/applications/<AIP Application>/AIPOnlineWAR
Property settings that contain path assignments are appended to the base directory
provided above. Use the complete path, base directory plus property path to locate
specific files as needed.
Example:
apptop.page=/fragments/apptop.jsp
apptop.jsp can be found in the following path:
<OAS Home>/j2ee/<AIP Instance>/applications/<AIP
Application>/AIPOnlineWAR/fragments
rcapps.properties file.
about.width Width of ‘about’ windows. Currently, no ‘about’ windows are supported.

apps.width Width of application windows.
appbanner.bg Defines the main background color. This appears as the horizontal banner.
appmenu.bg Menu banner background color. This appears as the vertical strip on the left side of the
page. It is the background for any ‘Applications’, ‘User Console’, and ‘Administration’
menu items.
text.fg Main text color. This is the text color for the main welcome on the login pages.
applet.codebase Applet default codebase. The default value is appclasses. This is not expected to ever
change.
apppage_top.page Contains the code content for the upper fragment of the page including the top and left
banners. The default value is /fragments/apppage_top.jsp
apptop.page Defines the standard top banner (normal and compact versions). The default value is
/fragments/apptop.jsp.
apptop_about.page Defines the content of the ‘about’ page. ‘About’ pages typically contain version numbers
and company information. ‘About’ pages are not supported by Oracle AIP. The default
value is /fragments/apptop_about.jsp.
head.page Contains the code content getting the configurations and saving them in variables used
throughout the page. The default value is /fragments/head.jsp.
appbot.page Defines the standard bottom banner. The default value is /fragments/appbot.jsp.
apppage_bot.page Contains the code content for the lower page fragment. The default value is
/fragments/apppage_bot.jsp.
securemode.allow Used to enable securemode.
Set to "*" to enable securemode on all clients, or set to "*, !Mac" to enable securemode on all
clients except those that are using a Macintosh.
webmeter.allow Used to display webmeter.
Set to "*" to display WebMeter for all clients, or "*, !Mac" to display WebMeter for all clients
except those that are using a Macintosh.
webmeter.page Defines the file containing code for the WebMeter page. The default is
/fragments/webmeter.jsp.
security.properties
This file defines security administration settings for the application.
security.properties file.
trackeradmin.prop.adminhosts This is a comma delimited list of "host/mask" values that are allowed to access
phantasm (the primary administration page).
strings_en.properties
This file provides the displayed text for the screens. Error text originating in the database
is not provided in this file and is not accessible for customization. Customizing this file
can have an affect on the visual presentation of the screen or popup message. The new
text should be of equal or similar character lengths as the modified text.
The file is located in the following server path:
<OAS Home>/j2ee/<AIP Instance>/applications/<AIP
Application>/AIPOnlineWAR/appclasses/res/com/retek/applet/strings_en.properties

Config.properties
Config.properties
This file contains configurable settings for Data Management and Order Management
that determine how certain screens appear immediately when opened. It also contains
settings which allow or prevent certain user activities on the screens.
This file is located in <OAS Home>/j2ee/<AIP Instance>/applications/<AIP
Application>/AIPOnlineWAR/appclasses/res/com/retek/applet.Data Management
Online Settings
The following table provides a description of properties found in the Config.properties
file that are used to define Data Management online (DMo) settings.
datamanagement.suppress.pre.save.message Indicates whether or not to suppress the pre-save message saying

that all applicable rows will be updated. This setting currently only
applies to the On Supply/Off Supply screen when performing mass
updates of SKUs and Stores. The valid values for this property are 0
to display the pre-save message and 1 for do not display the pre-save
message.
datamanagement.unit.of.measure.default Defines the unit of measure (UOM) radio button that is initially
selected when displaying DM Online screens containing UOM. Valid
values are 0 for cases, or 1 for eaches.
datamanagement.warehouse.type.available This setting determines whether the warehouse type field is
displayed in the DM online application. This should be set to 0 when
warehouse types are not defined for warehouses, or set to 1 if
warehouse types are assigned to warehouses.
export.launch When the user exports the Alerts from the DM online application to a
savable file, this setting will determine whether the file is opened
immediately or not. If set to launch immediately, the user must have
a default program for the particular file extension being saved. Two
file formats are available, spreadsheet (.xls) or comma delimited
(.csv). The default program associated with the file extension is
specific per PC and is not an AIP controlled setting. If no program is
associated to the file extension, the user may receive an error and the
file will not be opened. If an error occurs, the user must manually
open the file in the appropriate program. The valid values for this
property are 0 for don’t launch, and 1 for launch immediately.
export.type.default When exporting the Alerts from the DM online application to a
savable file, the user has the option of saving the data in spreadsheet
or comma delimited file format. This property setting is applied to
the initial radio button selection that defines the format. This
property defines the value selected by default. The user has the
option of choosing the other format by selecting the other radio
button option. The valid values for this property are 0 for comma-
separated file (CSV) or 1 for spreadsheet (XLS).
paginggrid.page.size This is the default “pagesize” setting applied to all screens with
paging. Pages contain a certain number of rows and only the content
for one page is displayed at a time. This property defines the number
of rows that are displayed in a single page. When setting this value
you should consider that the setting is system wide setting, not user
specific. The resolution of each user’s screen will affect how many
rows are visible without scrolling. Assign a large number to this
property may result in the need for some users to scroll down the
page to see all of the rows. Setting this property to an arbitrarily large
Config.properties
number also negates the benefits of paging, which is used to improve
screen rendering time performance and display information in a
more usable fashion. This property can be set to any value greater
than 0 and less than or equal to 9999999.
paginggrid.<screen name>.page.size Each screen that uses paging has its own pagesize setting. This
setting, when greater than 0, will override the default ‘pagesize’
setting. The same considerations for the default should be applied to
the individual screen settings. A value of -1 indicates that the default
should be used. The valid values for this property are -1 or any
number greater than 0 and less than or equal to 9999999.
scalinggroups.container.assignments.default This property indicates the default selection for Container
Assignments when creating new Scaling Groups.
0 for Same as Scaling Group
1 for Expand Scaling Group
Order Management Settings

The following table provides a description of properties found in the config.properties
file that are used to define Order Management (OM) settings.
ordermanagement.order.type.default This setting defines which order type radio button is selected by
default. The available options are All, Transfers, or Purchase Orders.
This setting applies to all Order Management screens which allow
the user to search or select an order type. Valid values for this
property are as follows:
0 for All
1 for Purchase Orders
2 for Transfers
Note: The ordermanagement.viewable.order.type setting takes
precedence over this setting. If this setting conflicts with it, the
ordermanagement.viewable.order.type will be used instead.
ordermanagement.viewable.order.type This setting defines which order types users are able to view and
possibly manipulate. Users cannot perform any operations on orders
types that do not match this setting, nor can they view order types
that do not match this setting. This setting applies to all Order
Management screens. The valid values for this property are as
follows:
0 for All
1 for Purchase Orders
2 for Transfers
Note: Users may have privileges to the Order Create screen but they
will be unable to perform any operations if the
ordermanagement.viewable.order.type is not set to All or Purchase
Order.
ordermanagement.unit.of.measure.default Defines the unit of measure (UOM) radio button that is initially
selected when displaying OM Online screens containing UOM. Valid
values are 0 for cases, or 1 for eaches.

Config.properties
ordermaintenance.order.display.format This setting defines the display format that is selected by default in
the Order Maintenance search criteria pop up. The valid options for
this property are 0 for the tree format and 1 for the grid format.
ordermaintenance.expand.all.default When the search results in the Order Maintenance screen are
displayed in a tree format, this setting is used to determine whether
the tree should be initially displayed in a collapsed or expanded
state. When collapsed, only the header level order information
appears. When expanded, all of the SKU-pack sizes and order
quantities associated with the order display. Valid values for this
property are 0 for collapsed or 1 for expanded.
ordermaintenance.update.quantity.default In the Order Maintenance screen, the user has the option of viewing
the quantity on the order as the total ordered quantity or as the
outstanding, un-received order quantity. This setting is used to
determine which radio button option will be initially selected on the
screen. The valid values for this property are 0 to view the total order
quantity, or 1 to view the unreceived order quantity.
ordermaintenance.supplier.tracking.default When moving the un-received purchase order quantity to a new
delivery date and/or destination, the user must specify whether the
supplier was the cause of the change or their business. The value that
is specified affects the supplier performance tracking. This property
defines which drop-down list option should be selected by default.
The valid values are as follows:
0 – Always Ask
1 – Supplier Initiated
2 – Business Initiated
The Always Ask option is recommended if the business will be
viewing and using the supplier performance tacking information.
This option forces the user to consciously select the appropriate
value.
If the business will not be using the supplier performance tracking
information, then either the Supplier Initiated or Business Initiated
option should be selected so that a value is always selected by
default. This prevents the user from having to randomly pick one of
the two options, as well as prevents the unnecessary popup which
appears when the Always Ask option is selected in the drop-down
list.
ordermaintenance.view.default This setting defines which view should be displayed initially in the
Order Maintenance Screen—the Standard View or the Extended
View. The extended view includes the Supplier Tracking value and
the Release Date. The additional columns displayed in the extended
view results in each column having a smaller display size. Valid
values for this property are 0 for the standard view and 1 for the
extended view.
ordermaintenance.allow.move.unreceived This setting allows the business to prevent users from changing the
destination and delivery date of a purchase order. The valid values
for this property are 0 to allow changing delivery dates and
destinations, or 1 to prohibit changing delivery dates and
destinations.
Config.properties
ordermaintenance.move.unreceived.criteria This setting allows the business to define when it is acceptable to

move un-received order quantities to a new delivery date and/or
destination.
The first option is anytime the order quantity is less than the received
quantity. This means that the user can change the order delivery date
and/or destination any time the order is released and not fully
received.
The second option is anytime the order is totally un-received. This
means that the user can change the order delivery date and/or
destination anytime the order has been released but not yet received
against.
The valid values for this property are 0 for not fully received or 1 for
0 received quantity.
ordermaintenance.move.allow.destination.c This setting allows the business to restrict users from changing
hange delivery destinations of their orders. This setting is used in the Order
Maintenance Move Unreceived Order Quantity popup. When users
are not allowed to change order destinations, they are left with the
sole option of changing the delivery date. Valid values for this
property are 0 to allow destination changes, or 1 to prevent
destination changes.
ordermaintenance.move.require.new.order. This setting determines whether or not a new order number is
number required when moving an order. If a new order number is not
required, users are allowed to choose whether to retain the existing
order number or generate a new one when moving un-received
quantities. Valid values for this property are 0 – Do not require a new
order number or 1 – Require a new order number.
ordermaintenance.allow.cancel.unreceived This setting allows the business to restrict users from fully canceling
a Purchase Order. The user can still modify the Purchase Order
quantity but they cannot fully cancel the un-received quantity. The
valid values for this property are 0 to allow the un-received order
quantity to be canceled or 1 to prohibit the cancelling of all un-
received order quantity.
ordermaintenance.allow.release.orders This setting allows the business to prevent users from manually
releasing purchase orders in the Order Maintenance screen. Orders
that have not been released cannot be modified. Only purchase
orders released on their lead time by the batch order release process
would be available for modification. The valid values for this
property are 0 to allow manual release of orders, or 1 to prevent
manual release of orders.
ordermaintenance.allow.edit.quantities The setting allows the business to prevent users from modifying
purchase order quantities. The user will still have the ability to cancel
the outstanding unreceived order quantity unless the
ordermaintenance.allow.cancel.unreceived property is also set to
disallow cancelling unreceived order quantities. Valid values for this
property are 0 to allow modification of order quantities, or 1 to
prevent modification of order quantities.
ordermaintenance.release.status.default This setting determines which Release Status radio button is initially
selected in the Order Maintenance search criteria popup. The valid
values for this property are 0 for all statuses, 1 for Released, or 2 for
unreleased.

Config.properties
orderreview.display.quantity.default This determines which Display Quantity value is initially selected in

the Order Review search criteria popup.
The first option is total quantity. This displays the summed order
quantity in the search results.
The second option is unreceived quantity. This will display the total
order quantity that is still outstanding or yet to be received. This
quantity is calculated as the total order quantity minus the total
received quantity.
The third option is received quantity. This will display the summed
received quantity in the search results.
The valid values for this property are 0 for total quantity, 1 for
unreceived quantity, and 2 for received quantity.
orderreview.display.zero.values.default This determines whether the Display Zero Values checkbox is
initially checked or unchecked in the Order Review search criteria
popup. Choosing to display zero values will result in zeros being
displayed in the columns where no quantity is found. Note, however
that at least one order must be found for the search criteria and date
range in order to have a row displayed in the search results. When
choosing to view received or unreceived quantities instead of the
order quantity, it will be impossible to distinguish a displayed zero,
which means no orders were found for the date range, from a 0
quantity was received or 0 quantity is yet to be received.
The valid values for this property are 0 to not initially select the
checkbox (do not display zeros) or 1 to initially select the checkbox
(display zeros).
6
AIP RPAS Configurations
The AIP RPAS configurations listed in this section allow the business to manipulate AIP
to meet their business needs. The XML files, configuration files, measures, etc. are
applied to the replenishment processing to affect the plan that is produced.
shortfallPriorityMatrix.xml
The Shortfall Priority Matrix describes the order in which available inventory is allocated
when an inventory shortfall occurs. The matrix is organized across two axes, Destination
Types and Boundaries.
The Destination Types are the list of store priorities in the system plus a single entry for
warehouses (because warehouses do not have priorities). The list of store priorities is
configurable, but the default Destination Types are as follows:
Super High Priority Stores
High Priority Stores
Normal Priority Stores
All Warehouses
The four Boundaries in the Shortfall Priority Matrix are as follows:
CORT (Customer Orders over Review Time)
MSS (Minimum Sales Stock)
RP (Receipt Point)
RUTL (Receive Up To Level)
The following is the default Shortfall Priority Matrix.
Default Shortfall Priority Matrix
CORT MSS RP RUTL
Super High 1 4 5 6
High 2 7 9 11
Normal 3 8 10 12
Warehouse 13 14 15
Note that CORT is not a valid boundary for Warehouses because Warehouses do not deal
directly with customers.
AIP RPAS Configurations 67

surplusStorePriorityMatrix.xml
The Shortfall Priority Matrix ranking is configurable. The configuration is specified using
an XML file, shortfallPriorityMatrix.xml, which is formatted as shown below.
<reconciliation-priority-matrix>
<boundary componentName="CustomerOrderOverReviewTime">
<group id="1" priority="1"/>
</boundary>
<boundary componentName="WarehouseMinimumStock">
</boundary>
<boundary componentName="MinimumSalesStock">
</boundary>
<boundary componentName="SupplyChainReceiptPoint">
</boundary>
<boundary componentName="SupplyChainReceiptUptoLevel">
</boundary>
Within the XML file, the "group id" corresponds to a destination priority, where “0” is
reserved for All Warehouses. The remaining destination priorities should match the store
priorities. For example, the default destination priorities are “1” for Super High Priority
Stores, “2” for High Priority Stores, “3” for Normal Priority Stores. The "componentName" is
the name of a numeric DataContainer which will contain the calculated allocation
boundary data.
For each group the allocation boundaries should only be prioritized in the following
ascending order: CORT < MSS < RP < RUTL. Since the allocation boundaries are
cumulative, undesirable results may be generated if this order is not followed.
It should also be noted that same priority numbers across multiple cells will not be
supported in the current release. Each cell within the matrix should be assigned a unique
priority number. Not doing so will result in erroneous results.
The Surplus Store Priority Matrix describes the order in which available inventory is
allocated to stores when an inventory surplus occurs. This matrix is used when pushing
only to stores. There are two surplus matrices, surplusStorePriorityMatrix and
surplusAllPriorityMatrix, and which one is used for pushing depends on the valid
destinations served by a supplier with a fixed purchase quantity or stockless warehouse.
The surplusAllPriorityMatrix is not configurable and therefore is not listed in this guide.
The matrix is organized across two axes, Destination Types and Boundaries. The
Destination Types are the same as those in the shortfall version, but the Boundaries are
different.

The two Boundaries in the Surplus Priority Matrix are as follows:

Up To Upper Boundary
Above Upper Boundary
Default Prioritized Store Surplus Priority Matrix
Up To Upper Boundary Above Upper Boundary
Super High 1 6
High 2 5
Normal 3 4
Warehouse 7
Default All Destination Type Surplus Priority Matrix
Up To Upper Boundary Above Upper Boundary
All Destinations 1 2
When stepping through the Surplus Priority Matrix, the ‘Upper Boundary’ is simply the
appropriate Upper Boundary for the SKU and destination type. The ‘Lower Boundary’
on the other hand is always assumed to be zero. This is because when pushing inventory
to destinations, the inventory position of those destinations need not have reached any
particular lower boundary, because they may not have ordered anything. Therefore, by
treating the lower boundary as zero, it is possible to assess all destinations against the
Upper Boundary, regardless of their inventory position.
This matrix is configurable through direct access to the database. However, the rule that
must be observed is that for any given Destination Type (consider this a row in the
matrix), the boundaries must be addressed in increasing numerical order – there is no
point in giving destinations a quantity ‘Up to their Upper Boundary’ after giving them
inventory ‘Above their Upper Boundary’. Note that by definition, the ‘Above the Upper
Boundary’ cell has no upper numerical limit, and so as long as there are destinations
associated with a particular row to which inventory can be sent, an ‘Above Upper
Boundary’ cell will always exhaust all remaining inventory.
The Surplus Priority Matrix ranking is configurable. The configuration is specified using
an XML file, surplusStorePriorityMatrix.xml which is formatted as shown below.
<reconcilication-priority-matrix>
<boundary componentName="Above Upper Boundary">
<group id="1" priority="6" method="fair-share"/>
</boundary>
<boundary componentName="Up To Upper Boundary">
</boundary>
</reconcilication-priority-matrix>
Measures
Within the XML file, the group id corresponds to a destination grouping. The destination
priorities should match the store priorities. For example, the default destination priorities
are “1” for Super High Priority Stores, “2” for High Priority Stores, “3” for Normal
Priority Stores. The "componentName" is the name of a numeric DataContainer which will
contain the calculated allocation boundary data. The “method” currently has only one
valid designation (“fair-share”) and should not be changed.
For each group the allocation boundaries should only be prioritized in the following
ascending order: ‘Up To Upper Boundary’ < ‘Above Upper Boundary’. Since the
allocation boundaries are cumulative, undesirable results may be generated if this order
is not followed.
It should also be noted that same priority numbers across multiple cells will not be
supported in the current release. Each cell within the matrix should be assigned a unique
priority number. Not doing so will result in erroneous results.
Measures
aip_env_rpas.sh
In addition to the infrastructure-type environment variables listed in Chapter 4, “System
Configuration,” of this Oracle Retail Advanced Inventory Planning Implementation Guide, the
aip_env_rpas.sh script contains implementation parameters which the business must
customize. The values assigned to the variables in the “Implementation Parameters”
section of aip_env_rpas.sh will be assigned as values to selected AIP RPAS measures
during execution of the set_implementation_parms.sh script--which is run from
aip_batch.sh when the ‘first time’ parameter is True. See Chapter 13, “First Day of AIP,”
for details on running AIP batch with ‘first time’ parameter set to True.
The following table contains a description of the variables in aip_env_rpas.sh which
correspond to the Implementation Parameters for AIP RPAS.
Implementation Parameter(s) Default Value(s) Description
DEFAULT_PLANNING_HORIZON 35 This variable is used as a default store

planning horizon for DM.
This parameter will be used to initialize the
RPAS measure: dm0_defplnhzn.
POST_PROMOTION_SUBSTITUTION FALSE The Post Promotion Substitution Flag
_FLAG determines whether promotional items
should be substituted after their
promotional date.
RPAS measure: dmx_pstpmsflg.

Measures
SUPPLIER_ORDER_MULTIPLE_ALG 1 This flag determines whether the user will

ORITHM manually enter ordering parameters for the
entire supply chain, or whether the
supplier's value for Pallet Multiple and
Order Multiple will be spread through the
supply chain.
If the value is 1, the two parameters listed
above must be defined for both supplier to
warehouse and warehouse to warehouse
combinations of the supply chain.
If the value is 0, the two parameters listed
above need only be defined for the top tier
of the supply chain--supplier to warehouse
combinations. An algorithm will run as part
of DM Batch to set the values for the inner
tiers of the supply chain equal to the value
of the top tier. Note that any warehouse to
warehouse combinations that are either
system generated by DM Automated
Maintenance, or user generated will be
overwritten in the RPAS measure!
RPAS measure: dmx_somalg.
Measures
SPECIAL_ORDER_CYCLE_ZERO "PFOCPRFVS" The dmx_speocy measure contains 5 values

SPECIAL_ORDER_CYCLE_ONE "PFOCOGVW" unique Order Cycle identifiers. These order
cycles are used by default when
SPECIAL_ORDER_CYCLE_TWO "PFOCPRFWS"
automatically generating profiles and order
SPECIAL_ORDER_CYCLE_THREE "PFOCFULLC" groups. These should not be changed unless
SPECIAL_ORDER_CYCLE_FOUR "PFOCOGWW" the AIP Oracle PL/SQL is customized to use
the new Order Cycle codes and the order
cycle exists in the AIP Oracle database.
The order cycle lengths and lead times are
not defined in AIP RPAS at implementation
time. The order cycle lengths and lead times
are defined in AIP Oracle at implementation
time and will be loaded into AIP RPAS
before the first full run of DM Batch.
PFOCPRFVS - Used when automatically
creating a new Supplier Profiles.
PFOCPRFWS - Used when automatically
creating new Warehouse Profiles.
PFOCOGVW - Used when the system
creates Automated Supplier sourced Order
Groups.
PFOCOGWW - Used when the system
creates Automated Warehouse sourced
Order Groups.
PFOCFULLC - This is an empty order cycle
which is used to wipe out all receipt points
and lead times. It is used for new Stores
which will have a walking lead time
calculated prior to the store opening. It can
also be assigned as a profile order cycle.
These parameters will be used to initialize
the RPAS measure: dmx_speocy.
STORE_ONLY_STRING STR This string contains the Supplier Ship-to
code that represents 'Stores Only'. This code
is used when attempting to automatically set
the store source value for a new SKU.
Because the Supplier Ship-to values are also
sent to AIP on Oracle, the codes and table
constraints in both systems must remain
consistent.
RPAS measure: dmx_storeonly.

Measures
CSC_STORE_FORMAT_STRING SFMT1002 This string contains the store format of the

stores which receive their SKUs from the
warehouse when the supplier of the SKU
can supply both the stores and the
warehouses.
This setting is used when the batch tries to
automatically set the Store Source value for
a new SKU. When the selected supplier of
the SKU has a Supplier Ship-to value equal
to the value in dmx_cscdir, this indicates
that the supplier can ship to either CSC
warehouses or directly to stores. To
determine which store source to select (the
supplier or warehouse) the store format of
each store that the SKU is on-supply at is
compared to the store format listed in this
measure. If the store's format matches, then
the store’s default CSC warehouse is saved
as the source for the SKU/store. This means
that the supplier will provide the SKU to the
warehouse and the warehouse will provide
the SKU to the store.
The selected store format to be saved in this
measure must have the prefix 'SFMT' added
to it.
RPAS measure: dmx_cscstrfmt.
CSC_AND_STORE_DIRECT_STRING CS_ST This is the supplier ship-to value that
indicates the supplier ships to both CSC
warehouses and stores. Because the Supplier
Ship-to values are also sent to AIP on Oracle,
the codes and table constraints in both
systems must remain consistent.
RPAS measure: dmx_cscdir.
WAREHOUSE_TYPE_RDC CS_RG The value of this variable is a string that is
used to represent warehouses which are
Regional Distribution Centers.
RPAS measure: IpWhTypRDCI.
WAREHOUSE_TYPE_GSS XD_GS The value of this variable is a string that is
Deconsolidation Centers.
RPAS measure: IpWhTypGSSI.
WAREHOUSE_TYPE_XDK XD_RG The value of this variable is a string that is
Cross docks.
RPAS measure: IpWhTypXDKI.
Measures
AUTOMATIC_WAREHOUSE_PROFIL FALSE Controls the execution of the automatic

E_CREATION warehouse profile creation logic. If set to
False, the logic will not execute and
warehouse profiles will not be automatically
created. The user is responsible for manually
creating warehouse profiles. If set to True,
one warehouse profile is created for each
new supplier. This parameter should be
True if
AUTOMATIC_WAREHOUSE_PROFILE_A
SSIGNMENT is set to 1- 'Supplier'.
Otherwise, false.
Valid values are TRUE and FALSE
AUTOMATIC_WAREHOUSE_PROFIL 0 This measure controls the execution of the
E_ASSIGNMENT automatic warehouse profile assignment
logic. If set to 2- 'Disabled,' the logic will not
execute and the user is responsible for
manually assigning new SKUs to warehouse
profiles. If set to 1 - 'Supplier,' the system
will search for a warehouse profile that was
created for one of the SKU's suppliers and
assign the new SKU to it. If set to 0 - 'Class,'
the system will look for the warehouse
profile that has been designated as the
default profile for the SKU's class (Class to
Profile Assignment) and assign the new SKU
to it. This measure should be set to 'Class' or
'Disabled' when
AUTOMATIC_WAREHOUSE_PROFILE_C
REATION is FALSE.
IpRoLocTypeI - Replenishment Optimization Location Types

This measure specifies which location types are considered when extracting data for RO.
By default this measure is set to “Stores”. The valid values for this measure are 0, 1, or 2:
0 - Stores, 1 - Warehouses or 2 - Stores and Warehouses. This measure can also be edited
by inserting it into an analysis workbook. This measure value should be limited to just
those location types that are optimized in the optimization system AND replenished in
AIP.
IpFirstBusDayI - Replenishment Optimization First Business Day

This measure represents the first day of the normal business week, which is used to
determine the first day-of-week that the extract processes will begin to search for the lead
times to send to RO. By default this measure is set to 0 (Monday). The valid values of this
measure are 0 to 6: 0 – Monday, 1-Tuesday, 2-Wednesday, 3-Thursday, 4-Friday, 5-
Saturday, 6-Sunday. This measure can also be edited by inserting it into an analysis
workbook.

Measures
IpRoRtDaysStrI - Replenishment Optimization Review Time Extract Days for Stores

This measure specifies the period of time (in days) to search for a review time to send to
RO when extracting store data. This measure is an integer and by default this measure is
set to “28”. The valid value for this measure is any integer. This measure can also be
edited by inserting it into an analysis workbook.
IpRoRtDaysWhI - Replenishment Optimization Review Time Extract Days for Warehouses

This measure specifies the period of time (in days) to search for a review time to send to
RO when extracting warehouse data. This measure is an integer and by default this
measure is set to “28”. The valid value for this measure is any integer. This measure can
also be edited by inserting it into a workbook.
Modifying Measure Base Intersections Using Configuration Tools
Modifying Measure Base Intersections Using Configuration Tools

Using the RPAS Configuration Tools, the base intersection of the following measures can
be modified.
Note: The data file containing the data must match the
configured measure intersection.
Measure Description Valid Configuration
IpFctWkPrfD Week to Day Demand All Products/Chain/Day-Of-Week

Forecast Percentage Company/Chain/Day-Of-Week
Default Division/Chain/Day-Of-Week
Department/Chain/Day-Of-Week
Class/Chain/Day-Of-Week
Subclass/Chain/Day-Of-Week
IpFctWkPrfE Week to Day Demand Subclass/Chain/Day-of-Week
Forecast Percentage
Override
Import Configuration Files

Missing data files can corrupt downstream data and cause errors which are difficult to
interpret and trace to the root. Therefore, validation of the received import files must be
performed prior to running any batch calculations or loading any files with
dependencies. A set of configuration files are used to validate that all required files are
present before proceeding to load them.
The configuration files provide a complete list of hierarchy and measure data that
can be loaded. If a client chooses to load additional data rather than have the user
enter it, they may add the file to the appropriate configuration file so that its presence
in the AIP RPAS import directory is validated.
– The configuration files can be modified to specify whether a file is required
or optional.
– A file is considered required if its presence is essential for the batch run. A
missing required file will cause batch to halt. A required file must be present,
even if it is zero (0) byte, which indicates that the extracting worked correctly
but there was no data to extract.
– A file is considered optional if the batch will not halt when the file is not
present. No zero (0) byte file is required. A file can only be deemed optional
if it provides data that is not required by the replenishment batch modules, is
not required by AIP Online, and there are no required files that are
dependent on it.
– Additionally, if the same data can be entered in a workbook before the batch
run, the loaded data may also be considered optional.
– Optional files do not have to be loaded, or they may be loaded weekly or less
frequently depending on the file/purpose.
The configuration files for validation are listed below:
earlyfiles.config
latefiles.config
forecastdata_from_external.config

After the presence of all required files has been validated a number of files are run
through a stocking point prefix-adding script as well as a binary executable called
interutil. These processes perform a myriad of formatting tasks including splitting files,
adding S, V or W prefixes to Stores, Suppliers, and Warehouses respectively, and
transforming RMS-sourced files from RMS SKU to AIP SKU or SKU-pack size. The list of
files containing measure data that are reformatted by interutil is determined by a second
set of configuration files.
The configuration files can be modified to prevent interutil from being run for files
that are in AIP RPAS loadable format.
Only files containing measure data are listed in the configuration files. Hierarchy
files must be provided in the predetermined format.
Note: The AIP Operations Guide and “RMS Integration and

Mapping” information provided within this document
should be carefully reviewed for file format and file output
from interutil before modifying the contents of the
configuration files.
The interutil configuration files are listed below:

dm_rms_measures.config
srp_rms_measures.config
wrp_rms_measures.config
The table below provides information about each of the loadable configuration files.
Value Name File Name Description of Value and Purpose for Loading Early, Late-
precritical, or
Late (critical)
Ad had.txt Used for viewing Ad information and filtering Early

(advertisement) workbook wizard selections based on Ad
Hierarchy information.
Ad/Rollout Notes ipadrltntsi.txt Notes to the Planner about advertisements, new Early
SKU rollout, or any other pertinent information
needed for planning. Notes can be
entered/changed in workbooks as well.
Banded SKU dmx_bndprdasc.txt Used if the client buys merchandise in product Early
weight bands (i.e. turkeys). This file contains the
parent child relationship between the SKUs.
Customer Orders sr0_co_.txt Contains a total order quantity of a SKU that has Early
been committed to customers. Customer Orders are
treated as additional need above and beyond
forecasted need.
Daily Forecast sr0_frclvl1_[1..n].txt The daily forecast is optional for 3 reasons. 1. Both a Late-precritical
daily and weekly forecast are not required. One can
be provided and not the other (depending on
system configuration). 2. An updated forecast is
typically not reproduced daily, and therefore is not
required daily. 3. A forecast is not required if using
replenishment methods which use historical sales.
precritical, or
Late (critical)
Daily Forecast sr0_fcterrlvl1.txt Standard Deviation of the daily forecast. Late-precritical

Standard
Deviation
Daily Sales sr0_dayslsld.txt Daily Sales are used in store replenishment to Early
calculate "Today's" Projected Inventory position
when a Current Inventory Feed is not available. If
daily sales are also unavailable then another
calculation alternative is used.
Daily Short Code sr0_dyscsls.txt This value represents the number of units that were Late
Sales sold as a Markdown yesterday. This value is used
for calculating High Dissipation alerts.
Default default_wh.txt Used to automatically assign the STORE SOURCE. Early
Warehouse If not provided, the Default Warehouse CSC might
be used otherwise the store source will not be
automatically assigned when the store's source is
determined to be the default warehouse (based on
the SKU's supplier/ship-to value).
Default default_wh.txt Used to automatically assign the STORE SOURCE. Early
Warehouse CSC If not provided, the Default Warehouse might be
used. Otherwise the store source will not be
automatically assigned when the store's source is
determined to be the default CSC warehouse (based
on the SKU's supplier/ship-to value).
Direct Supplier dmx_dirspl.txt This flag indicates whether the Supplier is able to Early
Flag supply stores directly or not. This prevents the
system from allowing certain supply-chain setups.
Discontinuation dmx_dscdt_.txt Flags SKU-packs as discontinued. Used to Early
Date automatically de-range SKU-pack sizes and
automatically re-assign ordering pack sizes.
Expected Write- sr0_expwrtoff.txt Represents the quantity of stock expected to be Early
off thrown out for any reason (spoilage, breakage, etc.)
on a given day. Expected Write-offs override
calculated expected spoilage.
Historical Lost sr0_hstls_.txt Used in Alert Calculations. Early
Sales
Interval Hierarchy intv.txt This is used when loading the Poisson Distribution Early
Lookup table. This is required if Poisson will be
used as a replenishment method.
Inventory sr0_invadj.txt This value contains the total of all Inventory Late
Adjustments Adjustments made yesterday for the SKU at a
particular store. This value may be used for
resolving alerts. This value can be positive or
negative since it represents net adjustments, some
of which can be negative (inventory decreases).

precritical, or
Late (critical)
Off Sale Dates dm0_ofseffdt_.txt Contains Store, SKU, Off Sale Dates. Determines the Early
date that the SKU will no longer be sold at the store.
This value is used in determining the off-supply
date which determines when AIP will no longer
replenish the SKU at the store. If this file value is
blank the system will use the
SYSTEM_HIGH_DATE (infinity) as the off-sale
date.
On Sale Dates dm0_onseffdt_.txt Contains Store, SKU, On Sale Dates. Determines Early
when the SKU will be sold at the store. This value is
used in determining the on-supply date which
determines when AIP will begin to replenish the
SKU at the store.
Pack Type dmx_pcktyp.txt Defines a single pack type for each SKU-pack size. Early
Pack Type is used in the Automation to set Location
Orderable Unit, Order Multiple, and store ordering
pack sizes (store/store format pack size).
Automation will not be able to assign a value if the
pack type is not defined for SKU-pack sizes.
Poisson srx_poidst.txt Poisson Distribution Table. Early
Distribution Table
Pre-Priced Status dmx_pprsts.txt Used to substitute a pre-priced item in place of a Early
standard item during a promotion. The Default
status of a SKU is 'False' or 'Not Pre-priced.'
Product Life (shelf sr0_prdlfe.txt Indicates the number of days a product can sit in Late
life) the store before is spoils. This value should only be
set for short life items that are at high risk of waste
due to spoilage.
Promotional dm0_pmsstasrc.txt Used for substituting a promotional item for a Early
Substitution End standard item during a promotion. Defines the end
Date (WH Source) of the promotional period.
Promotional dm0_pmsendsrc.txt Used for substituting a promotional item for a Early
Substitution Start standard item during a promotion. Defines the start
Date (WH Source) of the promotional period.
RDF Detail Alert sr0_rdfdtdmsk.txt Optional flag to load into AIP from forecasting Late-precritical
(for Store) system indicating there is an issue resolving in AIP,
the planning app, instead of the forecasting app.
RDF Detail Alert iprdfdtdaltv.txt Optional flag to load into AIP from the forecasting Late-precritical
(for Warehouse) system for resolving in AIP, the planning app,
instead of the forecasting app.
RDF Detail Alert sr0_rdfdtdcnt.txt Count of all RDF Detail alerts generated for a Late-precritical
Count SKU/store.
Sister Store sister_store.txt Defines a 'like store' for a New Store. When the file Early
is provided along with a future store open date the
system will copy the supply-chain of the existing
store to the new store.
precritical, or
Late (critical)
Sister Warehouse sister_wh.txt Defines a 'like warehouse' for a New Warehouse. Early
When the file is provided along with a future
warehouse open date the system will copy the
supply-chain of the existing warehouse to the new
warehouse.
SKU Hierarchy item.txt Contains all SKUs that should exist in AIP. All files Early
(Product that contain a SKU intersection are dependent upon
Hierarchy) this file. SKUs begin to age when not
present/loaded from this file. If not yet purged, the
age of a SKU is reset if it is later re-loaded.
SKU Retail Price srx_prdrpr.txt SKU Retail Price interfaced via an external system Early
or custom RMS.
SPQ Commitment ipcmtmtde.txt This value can be entered in the workbooks or Early
Type Exception loaded (one or the other is expected). The SPQ
Commitment Type is only needed if Supplier
Purchase Quantities will be entered.
SPQ Order ipodcmti.txt This is the quantity that has been committed to be Early
Commit Quantity ordered/purchased from the supplier in a
particular week. The nature of the commitment is
defined in the SPQ commitment type. This value
can be entered manually in a workbook, or loaded.
Store Ad End ipadendi.txt Defines the end date of a Store Ad. Early
Date
Store Ad Start ipadstai.txt Defines the start date of a Store Ad. Early
Date
Store Adjusted sr0_adjsls.txt May be used in User Specified Allocations for Early
Sales Allocation on Rule Based Index.
Store Ads - Grand sr0_ad_go_.txt Determines which SKU/store/day has grand Early
Opening opening ads.
Store Ads - Inserts sr0_ad_irt.txt Indicates inserts ads exist for the listed Early
SKU/Store/Day.
Store Ads - Others sr0_ad_oth.txt Indicates ads classified as "other" non-standard ads Early
exist for the listed SKU/Store/Day
Store Ads - Run sr0_ad_rop.txt Indicates an Ad has been run as a result of extra Early
On Press Press for the listed SKU/Store/Day.
Store Ads sr0_ad_.txt Information to be viewed in the Workbooks. Flags Early
(advertisements) whether a SKU/store is included in any ads.
Store Average sr0_avgrosld_.txt Used to calculate the total Average Weekly Rate of Early
Weekly Rate of Sales across all stores served by a warehouse. The
Sale value is used when the warehouse replenishment
method is Factor ARS.
Store Current sr0_curinv_1.txt The quantity of inventory at the store that is Late
Inventory available to meet immediate demand.

precritical, or
Late (critical)
Store Hierarchy loc.txt Contains all Stores that should exist in AIP. All files Early
that contain a Store intersection are dependent
upon this file. Stores begin to age when not
present/loaded from this file. If not yet purged, the
age of a Store is reset if it is later re-loaded.
Store In-transit sr0_it_.txt In Transit quantities represent those orders which Late
Quantity have physically shipped to the destination.
Store Known sr0_knowndemand.txt Used in place of forecasted demand if loaded. Early
Demand
Store Loaded sr0_ss_ld_.txt Safety Stock for Loaded Safety Stock Dynamic Early
Safety Stock replenishment method.
Store On Order sr0_oo_.txt On Order Quantity represents those orders which Late
Quantity have been executed, but as of yet there is no
information regarding their physical shipment to
the destination.
Store Open Date sister_store.txt Defines the date that a new store is opening. This Early
date is used along with the Sister Store data to
perform a copy of the existing Store's supply-chain
to the new store. This value is also used for Walking
Store Lead Time automation.
Store RALT ipstrraltd.txt Contains the Default level intersection of Store Early
Default RATL. See Store RALT Global Default for full
explanation. The Default is not required. Default
values are needed if the Global Default is not the
desired value for a particular combination of
product and store.
Store RALT ipstrralte.txt Contains the Exception level intersection of Store Early
Exception RATL. See Store RALT Global Default for full
explanation. The Exception is not required.
Exception values are needed if the Global Default or
Default is not the desired value for a particular
combination of product and store.
Store RALT ipstrraltg.txt Contains the Receipt-to-Availability Lead Time Early
Global Default (RALT) to be applied when replenishing the
store(s). RALT is an integer representing the
number of days after receipt that an order is
available to start meeting demand. RALT should
currently be limited to a value of 0 or 1. The global
default is a higher level intersection than the default
and exception.
Store sr0_rplsubcde.txt This is for informational purposes only. It provides Early
Replenishment the planner more detailed information about how
Subtype Code the SKU is replenished at the store.
Store sr0_rplcde.txt This is for informational purposes only. It provides Early
Replenishment the planner information about how the SKU is
Type Code replenished at the store.
precritical, or
Late (critical)
Store Trading sr0_tdgday.txt Used to calculate the In-Scope indicator for Alerts. Early
Days Typically a day will not be counted or considered
during alert calculations if it is not a trading day
(e.g. the business is not Open). By default all days
are trading days.
Supplier splr.txt Contains all Suppliers that should exist in AIP. All Early
Hierarchy files that contain a Supplier intersection are
dependent upon this file. Suppliers begin to age
when not present/loaded from this file. If not yet
purged, the age of a Supplier is reset if it is later re-
loaded.
Supplier Ship-to dmx_shpto.txt Provides a 'code' that maps the supplier to the types Early
of locations that it ships products to. The ship-to
mappings (configured in a table) are used to
automatically setup the supply-chain. If missing,
Automation will be unable to automatically setup
the supply chain for the new Supplier and its new
SKUs.
Supplier/SKU- dmx_prdspllks.txt Defines which SKU-pack Sizes are available from Early
pack size each Supplier.
Associations
Total Store ipavgrtslsi.txt Can be calculated by summing the values in Early
Average Rate of sr0_avgrosld_ for each store that is served by the
Sales warehouse, or loaded outright. It is used when the
warehouse replenishment method is Factor ARS.
Value Added dmx_vadprdasc.txt Used to substitute pre-priced/added value items Early
Product for standard items during a promotion. This file
Association contains the parent child relationship between the
SKUs.
Warehouse wr1_curinv.txt The quantity of inventory at the warehouse that is Late
Current Inventory available to meet immediate demand. This file is
required. A 0-byte 'empty' file may be provided in
place of actual values if inventory positions at the
warehouse are not available. Replenishment will
then fall into the 'contingency' processing for
missing warehouse inventory positions.
Warehouse whse.txt Contains all stockholding Warehouses that should Early
Hierarchy exist in AIP. All files that contain a Warehouse
intersection are dependent upon this file.
Warehouses begin to age when not present/loaded
from this file. If not yet purged, the age of a
Warehouse is reset if it is later re-loaded.
Warehouse ipslsi.txt Historic Weekly Sales are used in the Sales Week Early
Historical Weekly Range and Average Weekly Sales replenishment
Sales methods. The value will be used when warehouse
replenishment method is set to either of these
methods.

precritical, or
Late (critical)
Warehouse iphldbckqtyi.txt A quantity of inventory at the warehouse that Early

Holdback should be held in reserve.
Quantity
Warehouse ipwhhldcpci.txt Used for Network Group Alert calculations Early
Holding Capacity
Warehouse In- wr1_it_.txt In Transit quantities represent those orders which Late
transit Qty have physically shipped to the destination. If no on-
order quantity exists it is assumed to be 0. This file
is required. A 0-byte 'empty' file may be provided if
running Store-only replenishment without
reconciliation.
Warehouse ipldssi.txt Required if the Loaded Safety Stock replenishment Early
Loaded Safety method will be used for warehouse replenishment.
Stock
Warehouse On wr1_oo_.txt On Order Quantity represents those orders which Late
Order Qty have been executed, but as of yet there is no
information regarding their physical shipment to
the destination. If no on-order quantity exists it is
assumed to be 0. This file is required. A 0-byte
'empty' file may be provided in place of actual
values if running Store-only replenishment without
reconciliation.
Warehouse wr1_ow_.txt The quantity of previously executed orders in the Late
Orders in the Well warehouse which have not yet been satisfied. This
quantity is deducted from the current inventory
position. If no order-in-the-well quantity exists it is
assumed to be 0. This file is required. A 0-byte file
may be provided in place of actual values.
Warehouse iprplstcdi.txt Information to be viewed in the Workbooks. Early
Replenishment Indicates how the SKU is replenished at the
Sub-type Code warehouse.
Warehouse iprpltcdi.txt Information to be viewed in the Workbooks. Early
Replenishment Indicates how the SKU is replenished at the
Type Code warehouse.
Warehouse Total ipttlhlstki.txt Total quantity of unavailable stock held at the Early
Held Stock warehouse. This quantity is for informational
purposes only. It is assumed to have been
subtracted out of the Current Inventory position
provided.
Warehouse Type wh_type.txt This warehouse attribute is used for virtually all Early
into-warehouse automation. It is also used in the
WRP Company Level Inventory Analysis
Worksheet which, if used, displays end of week
inventory against specific warehouse types. This
data should be set to required if into-warehouse
Automation is desired.
precritical, or
Late (critical)
Waste sr0_wstadj.txt This value contains the total of all Waste Late
Adjustments Adjustments made yesterday for the SKU at a
particular store. This value may be used for
calculating High Dissipation alerts. This value is
expected to be negative because waste decreases
inventory.
Week to Day ipfctwkprfd.txt Used to spread weekly forecasts to a daily level. Early
Forecast This file is needed when using weekly forecasts.
Percentage
Default
Week to Day ipfctwkprfe.txt Used to spread weekly forecasts to a daily level. Early
Forecast This file is only needed if an exception to the
Percentage default is needed.
Exception
Weekly Base Sales sr0_wkbsf_ld.txt A base line forecast at the weekly level that does not Late-precritical
Forecast include promotions. Used in calculated
Presentation Stock.
Weekly Forecast sr0_frclvl2_[1..n].txt The weekly forecast is optional for 3 reasons. 1. Late-precritical
Both a daily and weekly forecast are not required.
One can be provided and not the other (depending
on system configuration). 2. An updated forecast is
typically not reproduced daily, and is therefore not
required daily. 3. A forecast is not required if using
replenishment methods which use historical sales.
Weekly Forecast sr0_fcterrlvl2.txt Standard Deviation of the weekly forecast. Late-precritical
Standard
Deviation

Moving Integration Data Source from RMS to a Non-RMS External System

AIP is configurable to allow some files, whose default source is RMS, to be sourced
instead from a Non-RMS External System. The following instructions are the procedure
for adjusting the configuration files to support this change of source.
Pre-requisites for Moving the Source Application of an RMS Data Feed

1. The data feed must be one of the inventory data feeds that arrives late from RMS, as
listed in wrp_rms_measures.config or srp_rms_measures.config file, as well as the
latefiles.config file. These files are located in the following directory of the domain:
$AIPDOMAIN/interface/config/external/latefiles.config
$AIPDOMAIN/interface/config/rms/srp_rms_measures.config
$AIPDOMAIN/interface/config/rms/wrp_rms_measures.config
2. The data feed must now be formatted in RPAS-loadable format. No processing will
be performed to translate RMS SKU to AIP SKU, or to add stocking-point prefixes.
However, the data can still be split into multiple pieces (for Store Current Inventory,
namely sr0_curinv).
Note: For the RPAS measure loadable formats of the

inventory data feeds, see “
File Format Including Mapping to AIP RPAS Measure

Format” in Chapter 8 of this Implementation Guide.
3. The data feed is still considered to be a "late" arrival.
Setup
1. Add the data feed to the measdata_from_external.config configuration file. It is
located is in the following directory of the domain:
$AIPDOMAIN/interface/config/external/measdata_from_external.config
2. Remove the data feed from srp_rms_measures.config or wrp_rms_measures.config.
Also remove the data feed from inv_meas_ntier_prefix.config. These configuration
files are located in the following directories of the domain:
$AIPDOMAIN/interface/config/rms/srp_rms_measures.config
$AIPDOMAIN/interface/config/rms/wrp_rms_measures.config
$AIPDOMAIN/interface/config/rms/meas/inv_meas_ntier_prefix.config
Process
1. After the “early files” (as listed in earlyfiles.config) are placed into the domain, run
the appropriate aip_batch processes, as normal, to process external data.
Note: process_external_data.sh will not process any file that

has been moved from RMS to External source, as the feed is
still considered "late."
Additionally, load_non_rms_external.sh will not load the
moved feed, as it is not in the
$INTERFACE_EXTERNAL_DIR directory yet.
2. After the “late files” (as listed in latefiles.config) are placed into the domain (in the
$INTERFACE_RMS_DIR directory), run the appropriate aip_batch steps, as normal,
to process inventory data.
Note: process_inventory_data.sh will consolidate the current

inventory data feeds as prescribed in the script regardless of
whether they are RMS-sourced or non-RMS-sourced.
However, process_inventory_data.sh will not process any
moved feed by adding stocking point prefixes, or conversion
from RMS SKU to AIP SKU/SKU-pack size, as the feed is no
longer listed in the appropriate configuration files as in Step
2 of the setup above.
Finally, load_rms_replenishment_measures.sh will not load
the moved feed, for the same reason.

Note: All non-RMS external late files will be moved and

loaded without manual client intervention by way of logic
added to process_inventory_data.sh and
load_non_rms_files.sh as called by
load_rms_replenishment_measures.sh.
process_inventory_data.sh will move the files to the correct
spot for external processing, and load_non_rms_files.sh will
load the files.
7
AIP Calendar Hierarchy
AIP Calendar Data – clnd.dat or clnd.csv.dat
The table below provides information about the AIP clnd.dat file or clnd.csv.dat formats,
which contains AIP calendar hierarchy data.
Note: When constructing the clnd.dat file, ensure the first

day of the calendar is a Sunday. This is a requirement of the
AIP RPAS functionality.
Note: Manual creation of the calendar hierarchy should still

be done in a space separated file (clnd.dat). When calendar
hierarchy is created by the transform scripts it will be
comma separated (clnd.csv.dat).
# Data Entry Description Start Width Format Example
1 DAY Day 1 9 Dyyyymmdd D20040104

2 DAY Label 10 20 mm/dd/yy 01/04/04
3 DOFP Day of 4 Week Period 30 8 nn 01
4 DOFP Label 38 20 DOFP nn DOFP 01
5 DOFN Day of Fortnight 58 8 nn 01
6 DOFN Label 66 20 DOFN nn DOFN 01
7 DOW Day of Week 86 8 Day of Week (short)1 SUN
2
8 DOW Label 94 20 Day of Week (long) Sunday
9 DOS Day of Season 114 8 DOSnnn DOS008
10 DOS Label 122 20 DOS nnn DOS 008
11 WEEK Week 142 8 Wnn_yyyy W02_2004
12 WEEK Label 150 20 Week mm/dd/yy Week 01/10/04
13 WOS Week of Season 170 8 WOSnn WOS02
14 WOS Label 178 20 WOS nn WOS 02
15 WOY Week of Year 198 8 WYnn WY02
16 WOY Label 206 20 WOY nn WOY 02
17 UMC1 Week Grouping - 1 226 8 UMC1UNASSIGNED UMC1UNAS
18 UMC1 Label 234 20 Unassigned Unassigned
19 MNTH Month 254 8 Mnn _yyyy M01_2004
AIP Calendar Hierarchy 89

AIP Calendar Data – clnd.dat or clnd.csv.dat
# Data Entry Description Start Width Format Example
20 MNTH Label 262 20 Mnn, FY yyyy M01, FY 2004

21 MOY Month of Year 282 8 MYnn MY01
22 MOY Label 290 20 MOY nn MOY 01
23 QRTR Quarter 310 8 Qn_yyyy Q1_2004
24 QRTR Label 318 20 Qn FY yyyy Q1, FY 2004
25 YEAR Year 338 8 Ayyyy A2004
26 YEAR Label 346 20 FYyyyy FY2004
1
Day of Week (short): Short form of day-of-week names (“SUN”, “MON”, “TUE”,
“WED”, “THR”, “FRI”, “SAT”)
2
Day of Week (long): Long form of day-of-week names (“Sunday”, “Monday”,
“Tuesday”, “Wednesday”, “Thursday”, “Friday”, “Saturday”)
The Day of Fortnight (DOFN) and Day of 4-week Period (DOFP) values directly relate to
the order cycles values that the retailers will set up in the DM Online application. When
the user sets up a 14 or 28 day lead time cycle, that cycle day should correspond to the
AIP RPAS DOFN and DOFP values; otherwise, the schedules shown to the user in DM
Online will not match the executed plan and plan days viewed in the Workbooks. To
ensure the AIP RPAS DOFN and DOFP match the DM Online cycle days perform the
following:
1. For the first day in the calendar determine the DOFN and DOFP values by replacing
the values marked by < > with an appropriate value, and performing the following
SQL select statement:
MOD((TO_DATE('<FIRST CALENDAR DAY>', 'MM/DD/YYYY') - TO_DATE('01/02/2000',

'MM/DD/YYYY')), <14 FOR DOFN and 28 FOR DOFP>) +1
For example:
MOD((TO_DATE('04/01/2007', 'MM/DD/YYYY') - TO_DATE('01/02/2000', 'MM/DD/YYYY')),
14) +1
2. Format the cycle day (01-14 for DOFN, 01-28 for DOFP) from the SQL statement
above and use it as the starting cycle day in the file.
3. Increment the DOFN value for each subsequent day to 14 then restart the count at 1.
Increment the DOFP value for each subsequent day to 28 then restart the count at 1.
Notes on manual construction

1. The file clnd.dat must start at the beginning of a 4-5-4 fiscal year. This ensures the day-
of-week, day-of-season, and week-of-season are appropriately calculated and/or
loaded.
2. AIP supports a Sunday to Saturday week. However, in order to enable
customization, the transformation of the RMS calendar feed to clnd.csv.dat can
appropriately generate the day-of-week for non-Sunday based weeks. See the
chapter on RMS Integration and Data Mapping in this Implementation Guide.

8
Integration
Overview of the Integrated Inventory Planning Suite
The Integrated Inventory Planning Suite is the integration of Demand Forecasting (RDF),
Advanced Inventory Planning (AIP), Replenishment Optimization (RO), and Analytic
Parameter Calculator Replenishment Optimization (APC RO) as a full-suite inventory
management solution for retailers.
Figure 1: Conceptual Overview
Note: The integration interface between RDF and AIP is not

fully certified.
This solution supports data sharing among these applications. Note that the data sharing
functionality is not dependent on the presence of all these applications. The defined data
sharing between any of the applications works for the entire suite as well as for a subset
of the applications.
Integrated Inventory Planning Suite Data Flow

Figure 2 shows the integration of the Integrated Inventory Planning Suite applications
and the flow of data among those applications. Note that the figure below shows a
replenishment system. This can be AIP or any other replenishment system. The demand
forecasting application can be RDF or any other forecasting system.
Integration 91
Figure 2: Integrated Inventory Planning Suite Data Flow
Note: The integration interface between RDF and AIP is not

fully certified.
Data Flow Description

These descriptions explain each of the data flows in Figure 2.
From a Demand Forecasting Application (such as RDF) to APC RO

Sends historic demand forecasts for a forecast horizon for a series of forecast start
dates. It sends a separate forecast file for each forecast start date.
From a Demand Forecasting Application (such as RDF) to a Replenishment System (such as AIP)
Sends time-phased demand forecasts (starting today and looking forward) at the
item/store level.
Sends the cumulative standard deviation of the forecast. This is needed for the
calculation of safety stock.
From APC RO to RO
Sends simulation information and statistics:
– Item/location/scenario level information
– Mean/variability/lead time grouping level information
– Mean/variability grouping/scenario level information
– Scenario level information
From a Replenishment System (such as AIP) to RO

Sends the lead time in flat files. The lead time (or order cycle) pattern generally
contains the same lead time on all days that have a lead time; however, the lead time
may increase for the weekend. Therefore the most common lead time is found during
the business week.
Sends the review time in flat files. Review time is the number of days until the next
possible receipt. It is a key factor in determining the minimum amount of projected
stock that should be available until the next receipt. Since review time can change
daily, the minimum available inventory must cover the longest review time in order
to avoid stock outs.
Sends the ordering pack size in flat files. The ordering pack size is the preferred pack
size of an item that should be ordered from a source to the destination.

From a Demand Forecasting Application (such as RDF) to RO

Sends time-phased demand forecasts (starting today and looking forward) at the
item/store level. This allows the user to understand how the replenishment settings
would perform based on that demand.
Sends the cumulative standard deviation of the forecast. This is needed for the
calculation of safety stock.
From RO to a Replenishment System (such as AIP)

Sends the recommended replenishment methods and parameters in flat files based
on the schedule that the user sets.
For AIP specifically, RO performs the necessary transformations needed to convert
order-based replenishment parameters to a relevant form before sending it to AIP
since AIP is a receipts-based system.
9
RMS Integration and Data Mapping
RMS to AIP Data
There are two types of data which RMS may provide to AIP:
Hierarchy data
Measure data
Hierarchy Data
Overview
The table below displays the hierarchy files that AIP may receive from RMS.
File Name Description Source
1 loc.txt Location Hierarchy RMS-partial (†)

2 item.txt Item Hierarchy (Product Hierarchy) RMS-partial (*)
3 splr.txt Supplier Hierarchy RMS
4 whse.txt Warehouses RMS-partial (*)
5 clnd.csv.dat Calendar Hierarchy RMS
(†) RMS delivers only some fields in the location hierarchy. See below for details.
(*) These hierarchies go through a merge process with AIP-Oracle data prior to being
fully loaded into AIP-RPAS.
File Format
The Retail Extraction, Transformation, and Loading (RETL) tool, via the RMS-AIP
Transformation scripts, provides AIP with the file format displayed in the following
table.
Note: Customers who do not have RETL are required to

provide files with this same format.
Location Hierarchy File Name: loc.txt
Data Entry Start Width Source
Store 1 20 RMS
Store Description 21 60 RMS
Site 81 20 RMS
Site Description 101 40 RMS
Region 141 20 RMS
Region Description 161 40 RMS
Zone 201 20 RMS
RMS Integration and Data Mapping 95

RMS to AIP Data
Zone Description 221 40 RMS

Chain 261 20 RMS
Chain Description 281 40 RMS
Company 321 20 RMS
Company Description 341 40 RMS
TV Region 381 4 External
TV Region Description 385 24 External
Weather Region 409 4 External
Weather Region Description 413 24 External
Market Region 437 4 External
Market Region Description 441 24 External
Store Format 465 20 RMS
Store Format Description 485 40 RMS
Note: In the location hierarchy file, if RMS does not provide

a field value, the AIP transformation script creates a “0” for
the field. RMS can provide a store format; however, it is an
optional value in RMS. Store Format is not optional in AIP
and should be set appropriately in RMS to prevent errors in
AIP.
Item Hierarchy (Product Hierarchy) * File Name: item.txt
Data Entry Start Width Source/Comments
AIP SKU 1 20 RMS /This is the forecasted, selling SKU.

Order Multiple 21 4 RMS
Pack Quantity 25 4 RMS
RMS SKU 29 20 RMS
RMS SKU Description 49 60 RMS/ The description must not contain the
pipe character due to its use as a field
delimiter in the flat files loaded within AIP.
Banded Item Indicator 109 1 RMS/banded = 1
Not banded=0
Segment 110 20 RMS
Segment Description 130 60 RMS
Sub-Category 190 20 RMS
Sub-Category Description 210 60 RMS
Category 270 20 RMS

RMS to AIP Data
Data Entry Start Width Source/Comments
Category Description 290 60 RMS

Super-Category 350 20 RMS
Super-Category Description 370 60 RMS
Business Unit 430 20 RMS
Business Unit Description 450 60 RMS
Company 510 20 RMS
Company Description 530 60 RMS
SKU Type 590 20 RMS
SKU Type Description 610 100 RMS
The item.txt file maps as follows:

1. The RMS SKU to the AIP SKU.
2. The Pack Quantity and Order Multiple to the AIP SKU-pack size. AIP processing
code creates a mapping table (measure) to tie the RMS SKU to the AIP SKU pack size,
and uses this mapping method to send data back to RMS using the RMS SKU.
3. The Pack Quantity must be Null, and the Order Multiple equal to the AIP SKU-pack
size.
Note: While RMS can extract pack items AIP does not
support RMS Formal Packs. All item related data must be for
the forecasted, selling SKU.
Mapping Table
The following table is used for mapping the RMS SKU to the AIP SKU pack size. This
information is sent in the item.txt file. (See comments above):
Mapping table: (examples)
RMS SKU Order Multiple Pack Quantity AIP SKU Pack Size
300 1 (null) 300_1

303 6 (null) 300_6
Note: RMS truncates fractional pack sizes before sending the

data to AIP as AIP cannot handle fractional pack sizes.
Banded items mapping table: (examples)
RMS SKU Order Multiple Pack Quantity AIP SKU-Pack Size
300 1 (null) 300_1

303 6 (null) 303_6
Note: RMS handles the setting of banded items in item.txt

file.
RMS to AIP Data
Supplier hierarchy File name: splr.txt
Supplier 1 20 RMS
Supplier Description 21 40 RMS
Warehouse hierarchy File name: whse.txt
Warehouse Chamber 1 20 DM-Online

Warehouse Chamber Description 21 40 DM-Online
Warehouse 61 20 RMS
Warehouse Description 81 40 RMS
Note: RMS sends warehouse chamber values equal to

warehouse values.
Calendar hierarchy File name: clnd.csv.dat
Data Entry Source
Day RMS
Day Label AIP
DOFP AIP
DOFP Label AIP
DOFN AIP
DOFN Label AIP
DOW RMS
90 DOW Label AIP
DOS RMS
DOS Label AIP

Week RMS
Week Label AIP
WOS AIP
WOS Label AIP
WOY AIP
WOY Label AIP
UMC AIP
UMC Label AIP
Month RMS

RMS to AIP Data
Data Entry Source
Month Label AIP
MOY AIP
MOY Label AIP
Quarter RMS
Quarter Label AIP
Year RMS
Year Label AIP
Note: See the chapter on AIP Calendar Hierarchy for a

detailed file format of the calendar hierarchy.
Measure Data
Overview
AIP receives the following measure files from RMS:
1 dm0_pmsstasrc.txt Store Promotional Substitution Start Date for Warehouse RMS

2 dm0_pmsendsrc.txt Store Promotional Substitution End Date for Warehouse RMS
3 dmx_dscdt_.txt Corporate Discontinuation Date RMS
4 dmx_vadprdasc.txt Value Added Commodity Association RMS
5 dmx_prdspllks.txt Commodity-Supplier Links RMS
6 dmx_bndprdasc.txt Banded Item Association RMS
7 dmx_dirspl.txt Direct Suppliers RMS
8 sr0_curinv_[1..n].txt Store on hand inventory (used to be historical inv) RMS
9 sr0_it_.txt Store In transits RMS
10 sr0_oo_.txt Store On Orders RMS
11 sr0_prdlfe.txt Store Product Life RMS
12 wr1_curinv.txt Current WH Inventory (on hand) RMS
13 wr1_oo_.txt Warehouse On Orders RMS
14 wr1_it_.txt Warehouse In Transits RMS
15 wr1_aiw.txt Warehouse Allocations in the Well RMS
16 wr1_tiw.txt Warehouse Transfers in the Well RMS
17 wh_type.txt Warehouse Type RMS
18 sr0_dayslsld.txt Daily Sales RMS
19 received_qty.txt RMS received quantity RMS*
20 closed_order.txt RMS closed orders RMS*
RMS to AIP Data
Note: The last files, with *, are files coming from RMS to
AIP-Oracle and are NOT loaded into AIP-RPAS.
Note on File Formats

Two sets of file formats for the data listed above follow in the tables below.
The first set of file format tables (described in the “File Format” topic below”) describes
the format the data have after the RMS-AIP Transformation scripts have completed. For
more information about the RMS-AIP Transformation process, read the Oracle Retail
Advanced Inventory Planning Operations Guide, Chapter 5, “AIP Interfaces and
Transformation Scripts.”
The second set of file format tables (“

RMS to AIP Data
File Format Including Mapping to AIP RPAS Measure Format”) describes the mapping
between the RMS-AIP Transformation output format and the RPAS measure format. AIP
RPAS batch scripts contain logic to transform the data into the RPAS measure loadable
format.
When moving an integration data source from RMS to a non-RMS external system, as
described in Chapter 6, “AIP RPAS Configurations,” it is assumed that the RMS-AIP
Transformation process will not be run. Therefore, it is the user’s responsibility to create
the data files in the RPAS measure loadable format, as described in the second set of file
format tables, below. The “AIP Field”, “Start” and “Width” columns make up the RPAS
measure loadable format.
File Formats
The Retail Extraction, Transformation, and Loading (RETL) tool provides AIP with the
file formats displayed in the tables below.
Note: Customers who do not have RETL are required to

provide files with these same formats.
Store Promotional Substitution Start Date for Warehouse Data
File Name: dm0_pmsstasrc.txt
Field Name Type Start Width Source/Comments
Warehouse String 1 20 RMS

RMS SKU (Promotional) String 21 20 AIP will get the Store from
store source measure.
Order Multiple String 41 4
Store Promotional YYYYMMDD 45 8
Substitution Start Date

RMS to AIP Data
Store Promotional Substitution End Date for Warehouse Data
File Name: dm0_pmsendsrc.txt

RMS SKU (Promotional) String 21 20 AIP will get the store value
from the store source
Order Multiple String 41 4 measure.
Store Promotional YYYYMMDD 45 8

Substitution End Date
Corporate Discontinuation Date Data
File Name: dmx_dscdt_.txt
RMS SKU String 1 20 RMS

Order Multiple String 21 4 RMS will send today’s date.
AIP will set the ranging
Corporate Discontinuation YYYYMMDD 25 8 status at all supply locations
Date to pending-deranged as well
as initialize the stop-
receiving-dates at all
warehouses
Value Added Commodity Association
File Name: dmx_vadprdasc.txt
RMS SKU (child) String 1 20 RMS

RMS SKU (parent) String 25 20
Commodity-Supplier Links
File Name: dmx_prdspllks.txt
Supplier String 1 20 RMS

RMS SKU String 21 20
SKU Supplier Links Boolean 45 1

RMS to AIP Data
Banded Item Association
File Name: dmx_bndprdasc.txt
RMS SKU (child) String 1 20 RMS

RMS SKU (parent) String 25 20
Direct Suppliers
File Name: dmx_dirspl.txt
Supplier String 1 20 RMS

Direct Supplier Boolean 21 1
Store Current Inventory Data
File Name: sr0_curinv_[1..n].txt
Store String 1 20 RMS

RMS SKU String 21 20 Order Multiple value is always
one (1).
Store current inventory Float 41 8
Note: RMS can also send the Store Current Inventory file in
partitions. For example, AIP interface code can handle
sr0_curinv_[1..n].txt where n is the partition number. The
data will always arrive from RMS RETL extract with at least
one partition, namely, sr0_curinv_1.txt.
Store In Transits Data
File Name: sr0_it_.txt
Day DYYYYMMDD 1 9 RMS

Store String 10 20
Store In Transits Float 54 8

RMS to AIP Data
Store On Orders Data
File Name: sr0_oo_.txt

Store String 10 20 RMS will send today’s date
with sum of all previous # of
RMS SKU String 30 20 days values.
Store On Orders Float 54 8
Store Product Life Data
File Name: sr0_prdlfe.txt

Store Product Life Float 34 8
Current Warehouse Inventory Data
File Name: wr1_curinv.txt

Current Warehouse Inventory Float 45 8
On Orders Data
File Name: wr1_oo_.txt

Supplier String 10 20 RMS will send today’s date
with sum of all previous # of
Warehouse String 30 20 days values.
On Orders Float 74 8

RMS to AIP Data
In Transit Data
File Name: wr1_it_.txt

Supplier String 10 20
Warehouse String 30 20
In Transit Float 74 8
Allocations in the Well Data
File Name: wr1_aiw.txt

Warehouse String 10 20 RMS sends today’s date with
the sum of all pervious # of
Allocations in the Well Float 54 8
Transfers in the Well Data
File Name: wr1_tiw.txt

Warehouse String 10 20 RMS sends today’s date with
the sum of all pervious # of
Transfers in the Well Float 54 8

RMS to AIP Data
Daily Sales Data
File Name: sr0_dayslsld

Store String 10 20
Daily Sales Float 50 8
RMS received quantity Data
File Name: received_qty.txt
Order Number Integer 1 10 RMS

Order Type String 11 1
Order Multiple Integer 37 8
Pack Quantity Integer 45 8
Store Integer 53 10
Warehouse Integer 63 10
Received Date Date 73 8
Quantity Integer 81 8
RMS closed orders Data
File Name: closed_order.txt
Order Number Integer 1 10 RMS

Order Type String 11 1

RMS to AIP Data
File Format Including Mapping to AIP RPAS Measure Format

Store Promotional Substitution Start Date for Warehouse Data
File Name: dm0_pmsstasrc.txt
RMS Field Start Width AIP Field Start Width
Warehouse 1 20 Store 1 20
RMS SKU 21 20 Warehouse 21 20
Order Multiple 41 4 SKU 41 20
Store Promo Subs Start Date 45 8 Store Promo Subs Start 61 8
Date
Store Promotional Substitution End Date for Warehouse Data
File Name: dm0_pmsendsrc.txt
Warehouse 1 20 Store 1 20
RMS SKU 21 20 Warehouse 21 20
Order Multiple 41 4 SKU 41 20
Store Promo. Subs. Date 45 8 Store Promo. Subs. Date 61 8
Corporate Discontinuation Date Data
File Name: dmx_dscdt_.txt
RMS SKU 1 20 Commodity-Pack Size 1 20

Order Multiple 21 4
Corp Disc. date 25 8 Corp. Disc. Date 21 8

RMS to AIP Data
Value Added Association
File Name: dmx_vadprdasc.txt
RMS SKU (child) 1 20 SKU (child) 1 20

Order Multiple 21 4
RMS SKU (parent) 25 20 SKU (parent) 21 24
Order Multiple 45 4
Commodity Supplier Links
File Name: dmx_prdspllks.txt
Supplier 1 20 Supplier 1 20
Order Multiple 41 4
SKU Supplier Links 45 1 Commodity-Supplier Links 41 1
Banded Item Association:
File Name: dmx_bndprdasc.txt
RMS SKU (child) 1 20 SKU (child) 1 20

Order Multiple 21 4
RMS SKU (parent) 25 20 SKU ( parent) 21 24
Order Multiple 45 4
Direct Suppliers
File Name: dmx_dirspl.txt
Direct Supplier 21 1 Direct Supplier 21 1

RMS to AIP Data
Store Current Inventory Data
File Name: sr0_curinv_[1..n].txt
Store 1 20 Store 1 20
RMS SKU 21 20 SKU 21 20
Store current 41 8 Store Current Inventory 41 8
inventory
Store In Transit Data
File Name: sr0_it_.txt
Day 1 9 Day 1 9
RMS SKU 30 20 SKU 30 20
Order Multiple 50 4
Store In Transits 54 8 Store Intransits 50 8
Store On Orders Data
File Name: sr0_oo_.txt
Day 1 9 Day 1 9
RMS SKU 30 20 SKU 30
Order Multiple 50 4
Store Orders 54 8 Store Orders 50 8
Store Product Life Data
File Name: sr0_prdlfe.txt
Day 1 9 Day 1 9
RMS SKU 10 20 SKU 10 20
Order Multiple 30 4
Store Product Life 34 8 Store Product Life 30 8

RMS to AIP Data
Current Warehouse Inventory Data
File Name: wr1_curinv.txt
Warehouse 1 20 Warehouse 1 20
Order Multiple 41 4
Current Warehouse 45 8 Current Warehouse 41 8
Inventory Inventory
On Orders Data
File Name: wr1_oo_.txt
Day 1 9 Day 1 9
Order Multiple 70 4
On Orders 74 8 On Orders 70 8
In Transit Data
File Name: wr1_it_.txt
Day 1 9 Day 1 9
Order Multiple 70 4
In Transit 74 8 In Transit 70 8

RMS to AIP Data
Allocations in the Well Data
File Name: wr1_aiw.txt
Day 1 9 Day 1 9
Order Multiple 50 4
Allocations in the Well 54 8 Allocations in the Well 50 8
Transfers in the Well Data
File Name: wr1_tiw.txt
Day 1 9 Day 1 9
Order Multiple 50 4
Transfers in the Well 54 8 Transfers in the Well 50 8
Daily Sales Data
File Name: sr0_dayslsld
Day 1 9 Day 1 9
RMS SKU 30 20 SKU 30 20
Daily Sales 50 8 Daily Sales 50 8

RMS RETL Extract and RMS-AIP Transformation Overview

AIP requires the following text files that need to be processed from an external system.
The list of text files that needs to be processed by the merchandising system are:
Closed POs
Item Sale
Item Supplier
Location Mapping
Received Qty
Store Current Inv
Store Product Life
Substitute Items
Supplier
Warehouse Current Inv
Warehouse
Item
Calendar
Daily Sales
The Oracle Retail Merchandising Batch Schedule, and Oracle Retail Merchandising System
Operations Guide, Volume 1 - Batch Overviews and Designs, detail the RMS RETL Extract
scripts used to extract the data from various tables in RMS. These extracts are processed
by the RMS-AIP Transformation scripts to generate the data.
Mapping Overview
Some of the data RMS RETL Extracts generate require transformation by an RMS-AIP
Transform Script. The RMS RETL Extracts and the RMS-AIP Transform Scripts which
transform them are listed below. Some of these RMS RETL Extracts are inputs to multiple
transform scripts to create different AIP input files. All of the transformations are for data
files that are loaded into AIP-RPAS.
Note that the RMS RETL Extracts listed below correspond to the RMS 13.1.2 name set.
AIP-RPAS Required File RMS-AIP Transform Script RMS RETL Extract(s)
clnd.cvs.dat aipt_clnd.ksh date_format_preference.txt

last_day_of_week.txt
rmse_rpas_clndmstr.dat
dm0_pmsendsrc.txt aipt_sub_items.ksh rmse_aip_item_master.dat
dm0_pmsstasrc.txt rmse_aip_item_supp_country.dat
dmx_vadprdasc.txt rmse_aip_substitute_items.dat
dmx_dscdt_.txt aipt_item.ksh dmx_bndprdasc.txt
item.txt rmse_aip_item_master.dat
rmse_aip_item_retail.dat
rmse_aip_item_supp_country.dat
rmse_aip_merchhier.dat
rmse_aip_purged_item.dat

AIP-RPAS Required File RMS-AIP Transform Script RMS RETL Extract(s)
loc.txt aipt_orghier.ksh rmse_aip_orghier.dat

rmse_aip_store.dat
sr0_dayslsld.txt aipt_sr0_dayslsld.ksh rmse_rpas_daily_sales.dat
sr0_it_.txt aipt_future_delivery.ksh rmse_aip_alloc_in_well.dat
sr0_oo_.txt rmse_aip_future_delivery_alloc.dat
wr1_aiw.txt rmse_aip_future_delivery_order.dat
wr1_it_.txt rmse_aip_future_delivery_tsf.dat
wr1_oo_.txt rmse_aip_store.dat
wr1_tiw.txt rmse_aip_tsf_in_well.dat
rmse_aip_wh.dat
rmse_aip_wh.txt
sr0_prdlfe.txt aipt_str_prd_life.ksh rmse_aip_item_loc_traits.dat
rmse_aip_item_master.dat
rmse_aip_store.dat
rmse_aip_item_supp_country.dat
whse.txt aipt_rename.ksh rmse_aip_wh.txt
wh_type.txt aipt_rename.ksh rmse_aip_wh_type.txt
The RMS-AIP Transform Scripts reside in $RPAS_HOME/bin directory. In addition to

the required RMS RETL Extract files for input, the RMS-AIP Transform scripts depend on
two sets of file format schemas. The input schemas match the RMS RETL Extracts and are
bundled with RMS installation. The outputs schemas match the AIP-RPAS Required Files
and are bundled with the AIP installation.
Some of the data are extracted from RMS in the format required by AIP. These do not
require transformation by the RMS-AIP Transformation scripts.
closed_order.txt
dmx_dirspl.txt
dmx_prdspllks.txt
received_qty.txt
splr.txt
sr0_curinv_[1..n].txt
wr1_curinv.txt
Some of the data extracted by the RMS RETL Extract Scripts are not used by AIP. These
extracts are listed in the following table.
dm0_ofseffdt_.txt ‡
dm0_onseffdt_.txt ‡
rmse_aip_item_supp_country_reject_ord_mult.txt
rmse_aip_suppliers.dat

Note: this release of AIP cannot load the on sale/off sale

files, dm0_onseffdt_.txt and dm0_ofseffdt_.txt, which RMS
RETL Extract scripts produce. These files are considered to
be coming from an external system. The customer may
create a custom transformation in order to load these files
into AIP. This transformation should drop the order
multiple field and only retain the single unique on sale date
and off sale date for the SKU/Store. This script needs to
place the file in the external files inbound directory.
Technical Details of Load Process

For technical details of the processing and loading of the merchandising system
hierarchy and measure data, read the Oracle Retail Advanced Inventory Planning Operations
Guide. There are multiple versions of the RMS-AIP Transformation script sets. Each set is
for a different version of RMS. For example, aipt_item_rms10.ksh,
aipt_orghier_rms10.ksh, etc., are used for RMS 10, and aipt_item.ksh, aipt_orghier.ksh,
etc., are used for RMS 11+. The following documentation refers to non-RMS-version
specific instances of the shell scripts for brevity.

10
RDF Integration
RDF to AIP Data
AIP receives only measure data from Retail Demand Forecasting system.
Measure Data
Overview
AIP receives the following measure files from RDF:
1 iprdfdtdaltv.txt RDF Detail Alert RDF

2 sr0_rdfdtdmsk.txt RDF Detail Alert Mask RDF
3 sr0_rdfdtdcnt.txt RDF Detail Alert Count RDF
4 sr0_fcterrlvl1.txt Daily Store Forecast Standard Deviation RDF
5 sr0_fcterrlvl2.txt Weekly Store Forecast Standard Deviation RDF
6 sr0_frclvl1_[1..n].txt Daily Store Demand Forecast RDF
7 sr0_frclvl2_[1..n].txt Weekly Store Demand Forecast RDF
Note on File Formats

AIP requires that the file formats of the data files corresponding to the RDF exports have
the file formats displayed in the tables below.
Technical Details of Load Process

For technical details of the processing and loading of the forecasting system measure
data, read the Oracle Retail Advanced Inventory Planning Operations Guide.
RDF Integration 115

iprdfdtdaltv.txt
iprdfdtdaltv.txt
Data Element Details
Data Type Data Element Name Data Description
Measure RDF Detail Alert Contains destination stocking

point, SKU and RDF Detail Alert
flag.
Extracting Program Details
Program Type N/A
Program Name N/A
Schema File N/A
Program Frequency Daily
Data Source and Target Details
Data Source Details Target Data Details
Data Origin System External Systems Target Object Type RPAS Measure
Source Object Type Fixed Length Text File Target Object Name iprdfdtdaltv
Source Object Name iprdfdtdaltv.txt Target Object Database data/rdfdtdalt
Required/Optional Optional Target Object Load dstk_sku
Intersection
Field Level Mapping – Source
Source Fields Source Field Description Field Start Field

Position Width
STR Store 1 20
SKU SKU 21 20
Value RDF Detail Alert 41 1

sr0_rdfdtdmsk.txt
Field Level Mapping – Target
Target Data Field Name Target Field Description Target Field Condition/Format
Data Type
Dstk Destination Stocking Point String "S303 "

SKU SKU Int "100048001 "
Value RDF Detail Alert Boolean "1"
NaVal= false
Formatting Conditions
All Stores should be prefixed with an “S” (case sensitive).
Note that the RDF extract will only contain stores even though AIP reads the store into
the destination stocking point dimension which can hold warehouses, stores or suppliers.
Example of iprdfdtdaltv.txt Extract File Format:
S303 100048001 1
S303 100049004 1
sr0_rdfdtdmsk.txt
Measure RDF Detail Alert Mask Contains Store, SKU and RDF
Detail Alert Mask flag.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name sr0_rdfdtdmsk
Source Object Name sr0_rdfdtdmsk.txt Target Object Database data/sr0_rdfdtdmsk
Required/Optional Optional Target Object Load str_sku_
Intersection

sr0_rdfdtdcnt.txt

Position Width
STR Store 1 20
SKU SKU 21 20
Value RDF Detail Alert Mask 41 1
Data Type
STR Store String "S441090 "

SKU SKU Int "100048001"
Value RDF Detail Alert Mask Boolean "1"
NaVal= false
Example of sr0_rdfdtdmsk.txt Extract File Format:
S441090 100048001 1
S402 100048001 1
sr0_rdfdtdcnt.txt
Measure RDF Detail Alert Count Numeric measure at SKU/store

containing the number of alert
hits in the RDF Alert.
Program Type N/A
Program Name N/A
Schema File N/A

sr0_fcterrlvl1.txt
Source Object Type Fixed Length Text File Target Object Name sr0_rdfdtdcnt
Source Object Name sr0_rdfdtdcnt.txt Target Object Database data/sr0_rdfdtdcnt
Intersection

Position Width
STR Store 1 20
SKU SKU 21 20
Value RDF Detail Alert Count 41 8
Data Type

SKU SKU String “118525 “
Value RDF Detail Alert Count Int "5 "
NaVal = 0
Example of sr0_rdfdtdcnt.txt Extract File Format:
S303 118525 5
sr0_fcterrlvl1.txt
Measure Daily Store Forecast Standard Contains Store, SKU and Store
Deviation Forecast Standard Deviation
value.

sr0_fcterrlvl1.txt
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name sr0_fcterrlvl1
Source Object Name sr0_fcterrlvl1.txt Target Object Database data/sr0_fcterrlvl1
Required/Optional Optional Target Object Load str_sku
Intersection

Position Width
STR Store 1 20
SKU SKU 21 20
Value Daily Store Forecast Standard Deviation 41 8
Data Type

SKU SKU Int "100076002 "
Value Daily Store Forecast Standard Real "1.000000"
Deviation NaVal = 0
Example of sr0_fcterrlvl1.txt Extract File Format:
S441090 100048001 1.000000

sr0_fcterrlvl2.txt
sr0_fcterrlvl2.txt
Measure Weekly Store Forecast Contains Store, SKU and Store

Standard Deviation Forecast Standard Deviation
value.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name sr0_fcterrlvl2
Source Object Name sr0_fcterrlvl2.txt Target Object Database data/sr0_fcterrlvl2
Required/Optional Optional Target Object Load sku_str_
Intersection
Source Fields Source Field Description Field Start Position Field Width
STR Store 1 20
SKU SKU 21 20
VALUE Weekly Store Forecast Standard Deviation 41 8
Data Type

SKU SKU Int "100076002 "
Value Weekly Store Forecast Real "1.000000"
Standard Deviation NaVal = 0

sr0_frclvl1_[1..n].txt
All Supplier values should be prefixed with a “V” (case sensitive), all Warehouses should
be prefixed with a “W” (case sensitive) and all Stores should be prefixed with an “S”
(case sensitive).
Example of sr0_fcterrlvl2.txt Extract File Format:
S441090 100048001 1.000000
sr0_frclvl1_[1..n].txt
Measure Daily Store Demand Forecast Contains Day, Store, SKU and Daily Store
Demand Forecast value.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name sr0_frclvl1
Source Object Name sr0_frclvl1_[1..n].txt Target Object Database data/sr0_frclvl1
Required/Optional Optional Target Object Load day_str_sku
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Daily Store Demand Forecast 50 8

sr0_frclvl2.txt
Data Type
DAY Day String "D20060420"

SKU SKU Int "100049004 "
Value Daily Store Demand Forecast Real "1000 " NaVal = 0
All Stores should be prefixed with an “S” (case sensitive)and all Day values should be
prefixed with a “D” (case sensitive). Although the intersection is at day, AIP is expecting
the entire forecast for the week to be on one day of that week. RDF places the week's
forecast on the last day of the week.
Example of sr0_frclvl1_[1..n].txt Extract File Format:
D20060420S411 100049004 1000
Note: The client may partition this data file for space or size
considerations, e.g. sr0_frclvl1_1.txt, sr0_frclvl1_2.txt,
sr0_frclvl1_3.txt, etc.
sr0_frclvl2.txt
Measure Weekly Store Demand Contains Day, Store, SKU and

Forecast Weekly Store Demand Forecast.
Program Type N/A
Program Name N/A
Schema File N/A

sr0_frclvl2.txt
Source Object Type Fixed Length Text File Target Object Name sr0_frclvl2
Source Object Name sr0_frclvl2_[1..n].txt Target Object Database data/sr0_frclvl2
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
Value Weekly Store Demand Forecast 50 8
Data Type

SKU SKU Int "100044001 "
Value Weekly Store Demand Forecast Real "1000 "
NaVal = 0
All Stores should be prefixed with an “S” (case sensitive) and all Day values should be
prefixed with a “D” (case sensitive).
Example of sr0_frclvl2_[1..n].txt Extract File Format:
D20060401 100044001 1000
Note: The client may partition this data file for space or size
considerations, e.g. sr0_frclvl2_1.txt, sr0_frclvl2_2.txt,
sr0_frclvl2_3.txt, etc.

11
External System Integration
External System to AIP Data
External System data is data that AIP is able to load but which is not provided to AIP by
any available extract. There are two types of external data which are accepted as inputs
into AIP:
Hierarchy data
Measure data
Hierarchy Data
The table below displays the hierarchy files that AIP receives from External System:
1 had.txt Ad Hierarchy External

2 intv.txt Interval Hierarchy External
Measure Data
The table below displays the measure files AIP receives from External System.
default_wh.txt Default Warehouse External**

direct_store_format_pack_size.txt Direct Store Format Pack Size External*
direct_store_pack_size.txt Direct Store Pack Size External*
dm0_ofseffdt_.txt Off-Sale Effective Date External
dm0_onseffdt_.txt On-Sale Effective Date External
dmx_pcktyp.txt Pack Type External*
dmx_pprsts.txt Pre-Priced Status External
dmx_shpto_.txt Receiving Supplier / Ship To External
ipadrltntsi.txt Ad/Rollout Notes External
ipadendi.txt Store Ad End Date External
ipadstai.txt Store Ad Start Date External
ipavgrtslsi.txt Total Store Average Rate Of Sales External
ipcmtmtde.txt SPQ Commitment Type Exception External
ipfctwkprfd.txt Week to Day Forecast Percentage Default External
ipfctwkprfe.txt Store Week to Day Forecast Percentage Override External
iphldbckqtyi.txt Hold Back Quantity External
ipldssi.txt Loaded Safety Stock External
External System Integration 125

External System to AIP Data
ipodcmti.txt SPQ Order Commit Quantity External

iprplstcdi.txt Replenishment Subtype Code External
iprpltcdi.txt Replenishment Type Code External
ipslsi.txt Historical Weekly Sales External
ipttlhlstki.txt Total Held Stock External
ipwhhldcpci.txt Stocking Point Holding Capacity External
item_attribute.txt Item Attribute External*
item_attribute_type.txt Item Attribute Type External*
rmse_order_purge.dat Available Purchase Order Number External*
sister_store.txt Sister Store External**
sister_wh.txt Sister Warehouse External**
sr0_ad_.txt Store Ads External
sr0_ad_go_.txt Store Ads Grand Opening External
sr0_ad_irt.txt Store Ads Inserts External
sr0_ad_oth.txt Store Ads Others External
sr0_ad_rop.txt Store Ads Run On Press External
sr0_adjsls.txt Store Adjusted Sales External
sr0_avgrosld_.txt Store Average Weekly Rate of Sale Loaded External
sr0_co_.txt Store Customer Orders External
sr0_dyscsls.txt Daily Short Code Sales External
sr0_expwrtoff.txt Store Expected Write-off External
sr0_hstls_.txt Store Historical Lost Sales External
sr0_invadj.txt Inventory Adjustments External
sr0_knowndemand.txt Store Known Demand External
sr0_rplcde.txt Store Replenishment Type Code External
sr0_rplsubcde.txt Store Replenishment Subtype Code External
sr0_ss_ld_.txt Store Loaded Safety Stock External
sr0_tdgday.txt Store Trading Days External
sr0_wkbsf_ld.txt Loaded Weekly Base Sales Forecast External
sr0_wstadj.txt Waste Adjustments External
srx_poidst.txt SRP Poisson Distribution Lookup External
srx_prdrpr.txt SKU Retail Price External
store_format_pack_size.txt Store Format Pack Size External*
store_pack_size.txt Store Pack Size External*

had.txt
sku_cost.dat SKU Cost External*

sku_weight_volume.dat SKU Weight and Volume External*
Note: Files with * are coming from External System to AIP-

Oracle and are NOT loaded into AIP-RPAS; files with ** are
coming from External System to AIP-Oracle and are also
loaded into AIP-RPAS.
had.txt
Foundation Advertisement Hierarchy Contains Ad and Ad description.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name had.txt
Source Object Name had.txt Target Object Database Global
Required/Optional Optional Target Object Load N/A
Intersection

Position Width
Ad Ad 1 20
Ad Label Ad Description 21 40

intv.txt
Target Data Target Field Description Target Field Condition/Format

Field Name Data Type
Ad Ad String "A23456789100ABCDE00Q"
Ad Label Ad Description String "NEW ADVERTISEMENT BB "

NaVal = ''
None.
Example of had.txt Extract File Format:
A23456789100ABCDE00QNEW ADVERTISEMENT AA
B23456789100ABCDE00QNEW ADVERTISEMENT BB
intv.txt
Foundation Interval Hierarchy Contains Interval Code and

description.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name intv.txt
Source Object Name intv.txt Target Object Database Global
Intersection

default_wh.txt

Position Width
Interval Interval 1 20
Interval Description Interval Description 21 40
Target Data Target Field Target Field Data Condition/Format

Field Name Description Type
INT Interval Code String "A23456789100ABCDE00Q"

INT-Label Interval Description String "NEW INTERVAL AA "
NaVal = ''
None.
Example of intv.txt Extract File Format:
A23456789100ABCDE00QNEW INTERVAL AA
B23456789100ABCDE00QNEW INTERVAL BB
default_wh.txt
Measure Store Default Warehouses Contains Store, default

warehouse and default
warehouse CSC.
Program Type N/A
Program Name N/A
Schema File N/A

default_wh.txt
Data Origin System External Systems Target Object Type RPAS Measures &
Oracle Data Point
Source Object Type Fixed Length Text File Target Object Name dmx_defwh_ &
dmx_defwh_csc &
Warehouse Type
Source Object Name default_wh.txt Target Object Database data/dmx_defwh_ &
data/dmx_defwh_csc &
Oracle Database
Required/Optional Optional Target Object Load str_
Intersection

Position Width
STR Store 1 20
VALUE 1 Default Warehouse 21 20
VALUE 2 Default Warehouse Customer Service 41 20
Center
Data Type

Value 1 Default Warehouse String "W1090 " NaVal = ''
Value 2 Default Warehouse Customer String "W1090 " NaVal = ''
Service Center
All Warehouses should be prefixed with a “W” (case sensitive) and all Stores should be
prefixed with an “S” (case sensitive).
Example of default_wh.txt Extract File Format:
S348 W1090 W1090
S402 W1105 W1150
Load Notes
AIP RPAS batch processes split this data file into two flat files which are loaded into two
AIP RPAS measures. Then the original file is packaged for transfer to and load by AIP
Oracle batch processes.

direct_store_format_pack_size.txt
direct_store_format_pack_size.txt
N/A Direct Store Format Pack Size Contains the pack size that
This information is not should be ordered when the store
loaded into an RPAS is ordering the SKU from the
measure. It is loaded into an Direct Supplier.
Oracle table only.
Program Type N/A
Program Name N/A
Schema File N/A
Data Origin System External Systems Target Object Type Oracle Data point
Source Object Type Fixed Length Text File Target Object Name Direct Store Format
Pack Size
Source Object Name direct_store_format_pack_size.txt Target Object Database Oracle DB
Intersection

Position Width
Store Format Code Store Format 1 20

Commodity Code AIP SKU 21 20
Pack Size Pack Size 41 4
Supplier Code Supplier 45 20
Start Date Start Date 65 8
End Date End Date 73 8

direct_store_pack_size.txt
Data Type
Store Format Store Format String "1 "
Commodity Code AIP SKU String "100053003 "
Pack Size Pack Size int "36 "
Supplier Code Supplier String "V505 "
Start Date Start Date String "20050101"
End Date End Date String "20051201"
All Supplier values should be prefixed with a “V” (case sensitive).
Example of direct_store_format_pack_size.txt file:
1 100053003 36 V505 2005010120051201
Measure Direct Store Pack Size Contains Store, Commodity

Code, Pack Size, Supplier, Start &
End dates.
Program Type N/A
Program Name N/A
Schema File N/A
Data Origin System External Systems Target Object Type Oracle Data Point
Source Object Type Fixed Length Text File Target Object Name Direct Store Pack Size
Source Object Name direct_store_pack_size.txt Target Object Database Oracle Database
Intersection


Position Width
Store Code Store 1 20

Data Type
Supplier Code Supplier String "V505 "
All Supplier values should be prefixed with a “V” (case sensitive) and all Stores should
be prefixed with an “S” (case sensitive).
Example direct_store_pack_size.txt file:
S303 100053003 1 V505 2005010120051201

dm0_ofseffdt_.txt
dm0_ofseffdt_.txt
A custom transformation must be created to properly format this file before it can be
loaded. The transformation should drop the Order multiple and only retain the single
unique on sale date and off sale date for the SKU/Store.
Foundation Item Off Sale Dates Contains Store, SKU, Order

Multiple, and Off Sale Dates.
Program Type N/A
Program Name N/A
Schema File N/A
Source Table(s)/File(s) Fixed Length Text File Target Object Name Off-sale Effective Date
Source Object Name dm0_ofseffdt_.txt Target Object Database data/dm0_ofseffdt_
Required/Optional Required Target Object Load str_sku
Intersection

Position Width
STR Store 1 20
RMS_SKU RMS SKU 21 20
ORDM Order Multiple 41 4
Value Off Sale Effective Date 45 8

dm0_onseffdt_.txt
Data Type
SKU SKU String "100048001 "
Value Off Sale Effective Date date YYYYMMDD
Example dm0_ofseffdt_ file:
S303 100072001 20070101
S309 100072001 20070101
S348 100072001 20070101
S402 100072001 20070101
S411 100072001 20070101
dm0_onseffdt_.txt
A custom transformation must be created to properly format this file before it can be
loaded. The transformation should drop the Order multiple and only retain the single
unique on sale date and off sale date for the SKU/Store.
Foundation Item On Sale Dates Contains Store, SKU, Order

Multiple, and On Sale Dates.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fix Length Text File Target Object Name On-sale Effective Date
Source Object Name dm0_onseffdt_.txt Target Object Database data/dm0_onseffdt_
Required/Optional Required Target Object Load str_sku
Intersection

dmx_pcktyp.txt

Position Width
STR Store 1 20
RMS_SKU RMS SKU 21 20
ORDM Order Multiple 41 4
Value On Sale Effective Date 45 8
Data Type
Value On Sale Effective Date date YYYYMMDD
Example dm0_onseffdt_ file:
S303 100072001 20050101
S309 100072001 20050101
S348 100072001 20050101
S402 100072001 20050101
S411 100072001 20050101
dmx_pcktyp.txt
Measure Pack Type Contains SKU Pack Size and

Pack Type.
Program Type N/A
Program Name N/A
Schema File N/A

dmx_pcktyp.txt
Source Object Type Fixed Length Text File Target Object Name dmx_pcktyp
Source Object Name dmx_pcktyp.txt Target Object Database data/dmx_pcktyp
Required/Optional Optional Target Object Load skps
Intersection

Position Width
SKPS SKU Pack Size 1 20

VALUE Pack Type 21 24
Data Type
SKPS SKU Pack Size String "100033002_1 "
Value Pack Type String "CASE "

NaVal = ''
Even though the width of the value field is 24, only 6 characters can be utilized by this
field. The export of this data to AIP-Oracle contains only 6 characters of value.
Example of dmx_pcktyp.txt File:
100033002_1 EACH
100033002_4 CASE

dmx_pprsts.txt
dmx_pprsts.txt
Measure Pre-Priced Status Contains SKU Pack Size and Pre-

price status.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name dmx_pprsts
Source Object Name dmx_pprsts.txt Target Object Database data/dmbase

Required/Optional Optional Target Object Load Intersection skps

Position Width
SKPS SKU Pack Size 1 20

VALUE Pre-Priced Status 21 8
Data Type
SKPS SKU Pack Size String "100033002_1 "
Value Pre-Priced Status Integer "12 "

NaVal = 0

dmx_shpto_.txt
None.
Example of dmx_pprsts.txt Extract File Format:
100033002_1 12
100033002_4 15
dmx_shpto_.txt
Measure Receiving Supplier / Ship To Contains Supplier and Ship To

values.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name dmx_shpto_
Source Object Name dmx_shpto_.txt Target Object Database data/dmx_shpto_
Required/Optional Required Target Object Load splr
Intersection

Position Width
Supplier Supplier 1 20
Value Ship To 21 24

ipadrltntsi.txt
Target Data Field Name Target Field Description Data Type Condition/Format
Supplier SPLR Dimension String "V166 "
Ship To Ship To Code String "XD_GS "

NaVal = ''
(case sensitive).
Even though the width of the value field is 24, only 6 characters can be utilized by this
field. The export of this data to AIP-Oracle contains only 6 characters of value.
Example of dmx_shpto_.txt Extract File Format:
V166 CS_RG
V505 XD_GS
ipadrltntsi.txt
Measure Ad/Rollout Notes Simple Parameter
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name ipadrltntsi
Source Object Name ipadrltntsi.txt Target Object Database data/adrltnts
Required/Optional Optional Target Object Load week_skug
Intersection

ipadendi.txt

Position Width
WEEK Week 1 8
SKUG SKU Group 9 20
VALUE Ad/Rollout Notes 29 24
Data Type
Week Week String "W44_2006"
SKUG SKU Group String "100117118A "

Value Ad/Rollout Notes String "Example Notes "
NaVal = ''
All Weeks should be prefixed with “W” (case sensitive).
Example of ipadrltntsi.txt Extract File Format:
W44_2006100117118A Example Notes
ipadendi.txt
Measure Store Ad End Date Defines the end date of a Store

Ad
Program Type N/A
Program Name N/A
Schema File N/A
Program Frequency N/A

ipadendi.txt
Source Object Type Fixed Length Text File Target Object Name ipadendi
Source Object Name ipadendi.txt Target Object Database data/ad
Required/Optional Optional Target Object Load ad
Intersection

Position Width
AD Advertisement 1 20
Value Store Ad End Date 21 8
Data Type
Ad AD Dimension String "201CU50505 "
Value Store Ad End Date Date "20060225"
None.
Example of ipadendi.txt Extract File Format:
201CU50505 20060225

ipadstai.txt
ipadstai.txt
Measure Store Ad Start Date Defines the start date of a Store

Ad
Program Type N/A
Program Name N/A
Schema File N/A
Program Frequency N/A
Source Object Type Fixed Length Text File Target Object Name ipadstai
Source Object Name ipadstai.txt Target Object Database data/ad
Required/Optional Optional Target Object Load ad
Intersection

Position Width
VALUE Store Ad Start Date 21 8
Data Type
AD Advertisement String "201CU50505 "
Value Store Ad Start Date Date "20060225"
None.
Example of ipadstai.txt Extract File Format:
201CU50505 20060225

ipavgrtslsi.txt
ipavgrtslsi.txt
Measure Total Store Average Rate Of Contains destination stocking

Sales point, SKU and Subtype code.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name ipavgrtslsi
Source Object Name ipavgrtslsi.txt Target Object Database data/avgrtsls
Intersection

Position Width
DSTK Destination Stocking Point 1 20

SKU SKU 21 20
Value Total Store Average Rate Of Sales 41 8
Data Type
DSTK Destination Stocking Point String "W1090 "
SKU SKU Int "100048001 "
Value Total Store Average Rate Of Real "123.5678"

Sales NaVal= -1

ipcmtmtde.txt
(case sensitive).
Example of ipavgrtslsi.txt Exact File Format:
W1090 100048001 123.5678
ipcmtmtde.txt
Measure SPQ Commitment Type Composite Parameter

Exception
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name ipcmtmtde
Source Object Name ipcmtmtde.txt Target Object Database data/cmtmtd
Required/Optional Optional Target Object Load week_dstk_sku
Intersection

Position Width
WEEK Week 1 8
SKU SKU 29 20
VALUE SPQ Commitment Type Exception 49 24

ipfctwkprfd.txt
Data Type
DSTK Destination Stocking Point String "S510 "
Value SPQ Commitment Type Integer "1"

Exception NaVal = -1
(case sensitive). All Weeks should be prefixed with a “W” (case sensitive).
Example of ipcmtmtde.txt Extract File Format:
W25_2005S510 100033002 1
ipfctwkprfd.txt
Measure Week to Day Forecast Contains day of week, chain,

Percentage Default department and Week to day
forecast percentage default value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name ipfctwkprfd
Source Object Name ipfctwkprfd.txt Target Object Database data/ipfctwkprfd
Required/Optional Optional Target Object Load dow_chn_dept
Intersection

ipfctwkprfd.txt

Position Width
DOW Day of Week 1 8

CHN Chain 9 20
DEPT Department 29 20
Value Week to Day Forecast Percentage Default 49 8
Data Type
DOW Day of Week String "MON "
CHN Chain String "1 "
DEPT Department Int "5 "
VALUE Week to Day Forecast Real "0.14 "

Percentage Default NaVal = 0
None.
Example of ipfctwkprfd.txt Extract File Format:
MON 1 5 0.14
TUE 1 5 0.14

ipfctwkprfe.txt
ipfctwkprfe.txt
Measure Store Week to Day Forecast Contains day, chain, subclass and
Percentage Override (Un- Week to day forecast percentage
Normalized) override value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name ipfctwkprfe
Source Object Name ipfctwkprfe.txt Target Object Database data/ipfctwkprfe
Required/Optional Optional Target Object Load day_chn_scls
Intersection

Position Width
DAY Day 1 9
CHN Chain 10 20
SCLS Subclass 30 20
VALUE Store Week to Day Forecast Percentage 50 8
Override

ipfctwkprfe.txt
Data Type
CHN Chain String "1 "
SCLS Subclass Int "5 "
VALUE Store Week to Day Forecast Real "0.14 "

Percentage Override NaVal = 0
None.
Example of ipfctwkprfe.txt Extract File Format:
D200901011 5 0.14
D200901021 5 0.14

iphldbckqtyi.txt
iphldbckqtyi.txt
Measure Hold Back Quantity Contains day, destination

stocking point, SKU and Hold
Back Quantity value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name iphldbckqtyi
Source Object Name iphldbckqtyi.txt Target Object Database data/hldbckqty
Required/Optional Optional Target Object Load day_dstk_sku
Intersection

Position Width
DAY Day 1 9
SKU SKU 30 20
VALUE Hold Back Quantity 50 8

ipldssi.txt
Data Type
SKU SKU Int "100048001 "
Value Hold Back Quantity Real "280 "

NaVal = -1
(case sensitive).
Example of iphldbckqtyi.txt Extract File Format:
D20050820W1090 100048001 280
ipldssi.txt
Measure Loaded Safety Stock Contains destination stocking

point, SKU and Loaded safety
stock value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name ipldssi
Source Object Name ipldssi.txt Target Object Database data/ldss
Intersection

ipodcmti.txt

SKU SKU 21 20
Value Loaded Safety Stock Value 41 8
Target Data Field Name Target Field Description Target Field Data Type Condition/Format
SKU SKU Int "100048001 "
Value Loaded Safety Stock Value Real "520.50000"

NaVal =0
(case sensitive).
Example of ipldssi.txt Extract File Format:
W1090 100048001 520.5000
W3066 100049004 520.5000
ipodcmti.txt
Measure SPQ Order Commit Contains the 'Fixed' or 'Capped' Purchase Quantity agreed upon
Quantity with the Vendor.
Program Type N/A
Program Name: N/A
Schema File: N/A

ipodcmti.txt
Source Object Type Fixed Length Text File Target Object Name ipodcmti
Source Object Name ipodcmti.txt Target Object Database data/odcmt
Required/Optional Optional Target Object Load Intersection week_sstk_skug
WEEK Week of the Year 1 8

SSTK Source Stocking Point 9 20
SKUG SKU Group 29 20
Value Order Commit 49 24
WEEK Week String "W25_2005"
SSTK Source Stocking Point String "V1001 "
SKUG SKU Group Int "100117118A "
Value Order Commit Quantity Real "1200.000"

NaVal= -1
(case sensitive).
Example of ipodcmti.txt Extract File Format:
W25_2005V1001 100055017A 1200.000
W26_2005V1001 100055017A 1200.000

iprplstcdi.txt
iprplstcdi.txt
Measure Replenishment Subtype Code Contains destination stocking

point, SKU and Subtype code.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name iprplstcdi
Source Object Name iprplstcdi.txt Target Object Database data/rplstcd
Intersection

Position Width

SKU SKU 21 20
Value Replenishment Type Code Value 41 24
SKU SKU int "100046031 "
Value Replenishment Type Code Value string "H "

NaVal = ''

iprpltcdi.txt
(case sensitive).
Example of iprplstcdi.txt Extract File Format:
W1090 100046031 H
W3066 100033002 O
iprpltcdi.txt
Measure Replenishment Type Code Contains destination stocking

point, SKU and Type code value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name iprpltcdi
Source Object Name iprpltcdi.txt Target Object Database data/rpltcd
Intersection

Position Width

SKU SKU 21 20
Value Replenishment Type Code Value 41 24

ipslsi.txt
Target Data Target Field Description Data Type Condition/Format

Field Name
SKU SKU int "100033002 "
Value Replenishment Type code string "A "

value NaVal = ''
(case sensitive).
Example of iprpltcdi.txt Extract File Format:
W1090 100046031 A
W3066 100033002 O
ipslsi.txt
Measure Historical Weekly Sales Contains weekly sales history To

be used when replenishing via
the Sales Week Range or Average
Weekly Sales replenishment
methods.
Program Type N/A
Program Name: N/A
Schema File: N/A
Data Origin System External Systems Target Object Type Online Data Point
Source Object Type Fixed Length Text File Target Object Name ipslsi
Source Object Name ipslsi.txt Target Object Database data/sls
Required/Optional Optional Target Object Load week_dstk_sku
Intersection

ipslsi.txt

Position Width
WEEK Week 1 8
DSTK Warehouse 9 20
SKU SKU 29 20
Value Historical Weekly Sales 49 8
Data Type
WEEK Week String "W31_2005"
DSTK Unique identifier of a String "W1090 "

Warehouse
SKU SKU Int "100048001 "
Value Historical Weekly Sales value Real "105.0000"

NaVal = 0
(case sensitive).
Example of ipslsi.txt Extract File Format:
W31_2005W1090 100076002 105.0000

ipttlhlstki.txt
ipttlhlstki.txt
Measure Total Held Stock Simple Parameter
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name ipttlhlstki
Source Object Name ipttlhlstki.txt Target Object Database data/ttlhlstk
Required/Optional Optional Target Object Load day_dstk_skps
Intersection
DAY Day 1 9
SKPS Commodity-Pack Size 30 20
VALUE Total Held Stock 50 8
Day Day String "D20060123"
SKPS Commodity-Pack Size String "118525_1 "
Value Total Held Stock Integer "2000 "

NaVal = 0

ipwhhldcpci.txt
(case sensitive).
Example of ipttlhlstki.txt Extract File Format:
D20060123W1090 118525_1 2000
ipwhhldcpci.txt
Measure Stocking Point Holding Simple Parameter

Capacity
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name ipwhhldcpci
Source Object Name ipwhhldcpci.txt Target Object Database data/whhldcpc
Required/Optional Optional Target Object Load dstknwgp
Intersection

Position Width

NWGP Network Group 21 8
Value Stocking Point Holding Capacity 29 8

item_attribute.txt
Data Type
NWGP Network Group Position String "001 "
Value Stocking Point Holding Integer "1000 "

Capacity NaVal = 0
(case sensitive).
Example of ipwhhldcpci.txt Extract File Format:
W4110 001 1000
item_attribute.txt
Measure Item Attribute Contains SKU, Order Multiple,

Pack Quantity, Attribute Type,
Attribute Value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name Item Attributes
Source Object Name item_attribute.txt Target Object Database Online Database
Intersection

item_attribute.txt

Position Width
RMS SKU RMS SKU 1 20

Order Multiple Order Multiple 21 4
Pack Quantity Pack Quantity 25 4
Attribute Type Attribute Type 29 6
Attribute Value Attribute Value 35 40
Data Type
RMS SKU RMS SKU String "100048001 "
Order Multiple Order Multiple Int "1 "
Pack Quantity Pack Quantity String "0 "
Attribute Type Attribute Type String "WHSED "
Attribute Value Attribute Value String "Y"
(case sensitive).
Example of item_attribute.txt Extract File Format:
100048001 1 0 WHSED Y
100049004 1 0 WHSED Y

item_attribute_type.txt
item_attribute_type.txt
Measure Item Type Contains SKU, Order Multiple, Pack Quantity, Attribute Type,
Attribute Value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name Item Attribute Types
Source Object Name item_attribute_type.txt Target Object Database Online Database
Required/Optional Optional Target Object Load Intersection N/A
Filed Level Mapping - Source

Position Width
Attribute Type Attribute Type 1 6

Attribute Type Description Attribute Type Description 7 40
Filed Level Mapping – Target
Attribute Type Attribute Type String "WHSED "
Attribute Type Description Attribute Type Description String "Warehouse Indicator "
(case sensitive).
Example of item_attribute_type.txt Extract File Format:
WHSED Warehouse Indicator
VKSTK Viking Stocked Indicator

rmse_order_purge.dat
rmse_order_purge.dat
N/A Purged Purchase Order Numbers Contains AIP purchase order numbers
This data is not loaded into an that have been purged from the order
RPAS measures. It is loaded into execution system. The PO numbers can
an Oracle table. be assigned to new POs.
Program Type N/A
Program Name N/A
Schema File N/A
Data Origin System External Systems Target Object Type Oracle Table
Source Object Type Fixed Length Text File Target Object Name available_PO_num
Source Object Name rmse_order_purge.dat Target Object Database AIP Online Schema
Intersection

Position Width
ORDER_NUMBER Available Purchase Order Number 1 8
Data Type
ORDER_NO Available Purchase Order Number(8) "123456 "

Number
None
Example of rmse_order_purge.dat Extract File Format:
123456

sister_store.txt
sister_store.txt
Measure Sister Store Contains Sister Store, Existing

Store and open date.
Program Type N/A
Program Name: N/A
Schema File: N/A
Online Data Point
Source Object Type Fixed Length Text File Target Object Name dmx_sst &
dmx_stropndt_ &
Sister Store
Source Object Name sister_store.txt Target Object Database data/dmx_sst &
data/dmx_stropndt &
Online Database
Required/Optional Optional Target Object Load str &
Intersection str &
N/A
Sister/New Store Sister/New Store 1 20

Existing Store Existing Store 21 20
Open Date Open Date 41 8

sister_wh.txt
Data Type
Sister/New Store Sister/New Store String "S303 "
Existing Store Existing Store String "S402 "
Open Date Open Date String "20051201"
(case sensitive).
Example of sister_store.txt Extract File Format:
S303 S402 20051201
S348 S309 20051201
Load Notes
AIP RPAS Batch process split this data file into two flat files which are loaded into two
AIP RPAS measures. The original data file is exported to AIP Oracle and loaded by AIP
Oracle Batch processes.
sister_wh.txt
Measure Sister Warehouse Contains Sister Warehouse,

Existing Warehouse and open
date.
Program Type N/A
Program Name: N/A
Schema File: N/A

sister_wh.txt
Online Data Point
Source Object Type Fixed Length Text File Target Object Name dmx_swh &
dmx_wh_opndt_ &
Sister Warehouse
Source Object Name sister_wh.txt Target Object Database data/dmx_swh &
data/dmx_wh_opndt_ &
Online Database
Required/Optional Optional Target Object Load wh &
Intersection wh &
N/A
Sister/New Warehouse Sister/New Warehouse 1 20

Existing Warehouse Existing Warehouse 21 20
Open Date Open Date 41 8
Data Type
Sister/New Warehouse Sister/New Warehouse String "W1090 "
Existing Warehouse Existing Warehouse String "W1091 "
Open Date Open Date String "20051201"
(case sensitive).
Example of sister_wh.txt Extract File Format:
W1090 W1091 20051201
W1105 W1170 20051201
Load Notes
AIP RPAS Batch process split this data file into two flat files which are loaded into two
AIP RPAS measures. The original data file is exported to AIP Oracle and loaded by AIP
Oracle Batch processes.

sr0_ad_.txt
sr0_ad_.txt
Measure Store Ads Contains Store, SKU, Ad and

Store Ads Boolean flag.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_ad_
Source Object Name sr0_ad_.txt Target Object Database data/sr0_ad_
Required/Optional Optional Target Object Load str_sku_ad
Intersection

Position Width
STR Store 1 20
SKU SKU 21 20
Value Store Ads 61 1
Data Type
SKU SKU int "100055017 "
AD Advertisement String "IC0604051 "
Value Store Ads Boolean "1"

NaVal = false

sr0_ad_go_.txt
Example of sr0_ad_.txt Extract File Format:
S348 100055017 IC0604051 1
sr0_ad_go_.txt
Measure Store Ads Grand Opening Contains Store, SKU, Ad and

Store Ads grand opening value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_ad_go_
Source Object Name sr0_ad_go_.txt Target Object Database data/sr0_ad_go_
Intersection

sr0_ad_go_.txt

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Ads Grand Opening 50 8
Data Type

SKU SKU int "100055017 "
Value Store Ads Grand Opening Real "123.5678"
NaVal = 0
Example of sr0_ad_go_.txt Extract File Format:
D20050801S348 100055017 123.5678

sr0_ad_irt.txt
sr0_ad_irt.txt
Measure Store Ads Inserts Contains Store, SKU, Ad and

Store Ads Inserts Value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_ad_irt
Source Object Name sr0_ad_irt.txt Target Object Database data/sr0_ad_irt
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Ads Inserts 50 8

sr0_ad_oth.txt
Data Type
SKU SKU int "100055017 "
Value Store Ads Inserts Real "1.000000"

NaVal = 0
Example of sr0_ad_irt.txt Extract File Format:
D20050801S348 100055017 1.000000
sr0_ad_oth.txt
Measure Store Ads Others Contains Store, SKU, Ad and

Store Ads Others value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_ad_oth
Source Object Name sr0_ad_oth.txt Target Object Database data/sr0_ad_oth
Intersection

sr0_ad_rop.txt

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Ads Others 50 8
Data Type
SKU SKU int "100055017 "
Value Store Ads Others Real "1 "

NaVal = 0
Example of sr0_ad_oth.txt Extract File Format:
D20050801S348 100055017 1
sr0_ad_rop.txt
Measure Store Ads run on press Contains Store, SKU, Ad and

Store Ads run on press value.
Program Type N/A
Program Name: N/A
Schema File: N/A

sr0_ad_rop.txt
Source Object Type Fixed Length Text File Target Object Name sr0_ad_rop
Source Object Name sr0_ad_rop.txt Target Object Database data/sr0_ad_rop
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
Value Store Ads run on press 50 8
Data Type
SKU SKU int "100055017 "
Value Store Ads run on press Real "1.000000"

NaVal = 0
Example of sr0_ad_rop.txt Extract File Format:
D20050801S348 100055017 1.000000

sr0_adjsls.txt
sr0_adjsls.txt
Measure Store Adjusted Sales Contains Store, SKU, Day and

Store Adjusted Sales value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_adjsls
Source Object Name sr0_adjsls.txt Target Object Database data/sr0_adjsls

Required/Optional Optional Target Object Load Intersection day_str_sku

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
Value Store Adjusted Sales 50 8
Data Type
SKU SKU int "100055017 "
Value Store Adjusted Sales Real "5 "

NaVal = 0

sr0_avgrosld_.txt
Example of sr0_adjsls.txt Extract File Format:
D20050820S441105 100057004 5
sr0_avgrosld_.txt
Measure Store Average Weekly Rate of Contains Store, SKU and Store
Sale Loaded average week rate of sale loaded.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_avgrosld_
Source Object Name sr0_avgrosld_.txt Target Object Database data/sr0_avgrosld_
Intersection

Position Width
STR Store 1 20
SKU SKU 21 20
VALUE Store Average Weekly Rate of Sale 41 8
Loaded

sr0_co_.txt
Data Type
SKU SKU int "100076002 "
Value Store Average Weekly Rate of Real "200.0000"

Sale Loaded NaVal = 0
Example of sr0_avgrosld_.txt Extract File Format:
S441090 100076002 200.0000
sr0_co_.txt
Measure Store Customer Orders Contains Store, SKU, Ad and

Store Customer Orders quantity.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_co_
Source Object Name sr0_co_.txt Target Object Database data/sr0_co_
Intersection

sr0_dyscsls.txt

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Customer Orders 50 8
Data Type
SKU SKU String "S441105 "
STR Store int "100057004 "
Value Store Customer Orders Real "1 "

NaVal = 0
Example of sr0_co_.txt Extract File Format:
D20050820S441105 100057004 1
sr0_dyscsls.txt
Measure Daily Short Code Sales Contains Day, Store, SKU, and
Daily Short Code Sales quantity.
Program Type N/A
Program Name: N/A
Schema File: N/A

sr0_dyscsls.txt
Source Object Type Fixed Length Text File Target Object Name sr0_dyscsls
Source Object Name sr0_dyscsls.txt Target Object Database data/sr0_dyscsls
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
Value Daily Short Code Sales 50 8
Data Type
SKU SKU int "118525 "
Value Daily Short Code Sales Real "123.4500"

NaVal = 0
Example of sr0_dyscsls.txt Extract File Format:
D20060125S303 118525 123.4500

sr0_expwrtoff.txt
sr0_expwrtoff.txt
Measure Store Expected Write-Off Contains Day, Store, SKU and

Store Expected Write-Off value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_expwrtoff
Source Object Name sr0_expwrtoff.txt Target Object Database data/sr0_expwrtoff
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Expected Write-Off 50 8

sr0_hstls_.txt
Data Type
SKU SKU int "100055009 "
Value Store Expected Write-Off Real "5 "

NaVal = -1
Example of sr0_expwrtoff.txt Extract File Format:
D20050801S303 100055009 5
sr0_hstls_.txt
Measure Store Historical Lost Sales Contains Day, Store, SKU and
Store historical lost sales value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_hstls_
Source Object Name sr0_hstls_.txt Target Object Database data/sr0_hstls_
Required/Optional Required Target Object Load day_str_sku
Intersection

sr0_invadj.txt

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Historical Lost Sales 50 8
Data Type
SKU SKU int "100055009 "
Value Store Historical Lost Sales Real "1000.500"

NaVal = 0
Example of sr0_hstls_.txt Extract File Format:
D20050801S303 100055009 1000.500
sr0_invadj.txt
Measure Inventory Adjustments Contains Day, Store, SKU and

Inventory Adjustments value.
Program Type N/A
Program Name: N/A
Schema File: N/A

sr0_invadj.txt
Source Object Type Fixed Length Text File Target Object Name sr0_invadj
Source Object Name sr0_invadj.txt Target Object Database data/sr0_invadj
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
Value Inventory Adjustments 50 8
Data Type

Value Inventory Adjustments Real "123.4500"
NaVal = 0
Example of sr0_invadj.txt Extract File Format:
D20060124S303 163460 123.4500

sr0_knowndemand.txt
sr0_knowndemand.txt
Measure Store Known Demand Contains Day, Store, SKU and

Store known demand value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_knowndemand
Source Object Name sr0_knowndemand.txt Target Object Database data/sr0_knowndemand
Intersection

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
VALUE Store Known Demand 50 8

sr0_rplcde.txt
Data Type
SKU SKU int "100055009 "
Value Store Known Demand Real "1000.500"

NaVal = 0
Example of sr0_knowndemand.txt Extract File Format:
D20050801S303 100055009 1000.500
sr0_rplcde.txt
Measure Store Repl Type Code Contains Store, SKU and

replenishment type code.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_rplcde
Source Object Name sr0_rplcde.txt Target Object Database data/sr0_rplcde
Intersection

sr0_rplsubcde.txt
STR Store 1 20
SKU SKU 21 20
Value Store Replenishment Type Code 41 8
Data Type
SKU SKU Int "100048001 "
Value Store Replenishment Type String "A "

Code NaVal =0
Example of sr0_rplcde.txt Extract File Format:
S303 100046031 A
S348 100033002 M
sr0_rplsubcde.txt
Measure Store Replenishment Subtype Contains Store, SKU and

Code replenishment subtype code.
Program Type N/A
Program Name: N/A
Schema File: N/A

sr0_ss_ld_.txt
Source Object Type Fixed Length Text File Target Object Name sr0_rplsubcde
Source Object Name sr0_rplsubcde.txt Target Object Database data/sr0_rplsubcde
Intersection

Position Width
STR Store 1 20
SKU SKU 21 20
Value Store Replenishment Subtype Code 41 8
Store Store String "S303 "
SKU SKU Int "100048001 "
Value Store Replenishment Subtype String "A "

Code NaVal =0
Example of sr0_rplsubcde.txt Extract File Format:
S303 100046031 A
S348 100033002 J
sr0_ss_ld_.txt
Measure Store Loaded Safety Stock Contains Store, SKU and Loaded
Safety Stock value.

sr0_ss_ld_.txt
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_ss_ld_
Source Object Name sr0_ss_ld_.txt Target Object Database data/sr0_ss_ld_
Intersection
STR Store 1 20
SKU SKU 21 20
VALUE Store Loaded Safety Stock Value 41 8
Data Type
SKU SKU Int "100048001 "
Value Store Loaded Safety Stock Real "155.0000"

Value NaVal =0
Example of sr0_ss_ld_.txt Extract File Format:
S441090 100048001 155.0000
S348 100049004 155.0000

sr0_tdgday.txt
sr0_tdgday.txt
Measure Store Trading Days Contains Day, Store and Store

Trading days flag.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name sr0_tdgday
Source Object Name sr0_tdgday.txt Target Object Database data/ssldat
Required/Optional Optional Target Object Load STR_day_
Intersection
DAY Day 1 9
STR Store 10 20
Value Store Trading Days 30 1
Data Type
Value Store Trading Days Boolean "1"

NaVal = true

sr0_wkbsf_ld.txt
(case sensitive).
Example of sr0_tdgday.txt Extract File Format:
D20050620S303 1
D20050621S303 1
sr0_wkbsf_ld.txt
Measure Loaded Weekly Base Sales Loaded measure at

Forecast SKU/str/week to indicate the
weekly base sales forecast.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name sr0_wkbsf_ld
Source Object Name sr0_wkbsf_ld.txt Target Object Database data/sr0_wkbsf_ld
Required/Optional Optional Target Object Load week_str_sku
Intersection

Position Width
WEEK Week 1 8
STR Store 9 20
SKU SKU 29 20
Value Loaded Weekly Base Sales Forecast 49 8

sr0_wstadj.txt
Data Type

SKU SKU Int "118525 "
Value Loaded Weekly Base Sales Real "1.00000"
Forecast NaVal = 0
Example of sr0_wkbsf_ld.txt Extract File Format:
W05_2006S303 118525 1.00000
sr0_wstadj.txt
Measure Waste Adjustments Contains Day, Store, SKU and

Waste Adjustments value.
Program Type N/A
Program Name N/A
Schema File N/A
Source Object Type Fixed Length Text File Target Object Name sr0_wstadj
Source Object Name sr0_wstadj.txt Target Object Database data/sr0_wstadj
Intersection

srx_poidst.txt

Position Width
DAY Day 1 9
STR Store 10 20
SKU SKU 30 20
Value Waste Adjustments 50 8
Data Type
Value Waste Adjustments Real "123.4500"

NaVal = 0
Example of sr0_wstadj.txt Extract File Format:
D20060126S303 168941 123.4500
srx_poidst.txt
Measure SRP Poisson Distribution Loaded Poisson distribution

Lookup table.
Program Type N/A
Program Name N/A
Schema File N/A

srx_poidst.txt
Source Object Type Fixed Length Text File Target Object Name srx_poidst
Source Object Name srx_poidst.txt Target Object Database data/srx_poidst
Required/Optional Optional Target Object Load seq_int_
Intersection

Position Width
SEQ Sequence Number 1 20

INT Interval 21 20
Value SRP Poisson Distribution Lookup 41 8
Data Type
SEQ Sequence Number String "0016 "
INT Interval String "121000 "
Value SRP Poisson Distribution Real "33.3 "

Lookup NaVal = 0
None.
Example of srx_poidst.txt Extract File Format:
0016 121000 33.3

srx_prdrpr.txt
srx_prdrpr.txt
Measure SKU Retail Price Contains Week, Company, SKU

and Retail Price value.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name srx_prdrpr
Source Object Name srx_prdrpr.txt Target Object Database data/srx_prdrpr
Required/Optional Optional Target Object Load week_cmpn_sku
Intersection

Position Width
WEEK Week 1 8
COMPANY Company 9 20
SKU SKU 29 20
Value SKU Retail Price 49 8

store_format_pack_size.txt
Data Type
Company Company String "1 "
SKU SKU int "100048001 "
Value SKU Retail Price Real "6.460000"

NaVal = 0
None.
Example of srx_prdrpr.txt Extract File Format:
W32_20051 100048001 6.460000
W32_20051 100048001 6.460000
Measure Store Format Pack Size Contains Store Format, AIP SKU,
pack size, Warehouse, start date
& end date.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name Store Format Pack Size
Source Object Name store_format_pack_size.txt Target Object Database Online Database
Intersection


Position Width
Store Format Code Store Format 1 20

Stocking Point Number Warehouse 45 20
Data Type
Store Format Store Format String "1 "
Stocking Point Number Warehouse String "W3066 "
Filtering Conditions
The SKU-pack size should have an AIP ranging status of ‘Profile Ranged,’ ‘Exception
Ranged,’ or ‘Pending De-ranged’ at the warehouse before it is loaded into AIP as the
store ordering pack size.
(case sensitive).
Example of store_format_pack_size.txt Extract File Format:
1 100052001 36 W3066 2005010120051201

store_pack_size.txt
store_pack_size.txt
Measure Store Pack Size Contains the preferred ordering

pack size when ordering the SKU
from the warehouse to the store
during a particular time period.
Program Type N/A
Program Name: N/A
Schema File: N/A
Source Object Type Fixed Length Text File Target Object Name Store Pack Size
Source Object Name store_pack_size.txt Target Object Database Online Database
Intersection

Position Width
Store Code Store 1 20

Stocking Point Number Warehouse 45 20

sku_cost.dat
Data Type
Store Code Store String "S303 "
Stocking Point Number Warehouse String "W3066 "
The SKU-pack size should have an AIP ranging status of ‘Profile Ranged,’ ‘Exception
Ranged,’ or ‘Pending De-ranged’ at the warehouse before it is loaded into AIP as the
store ordering pack size.
(case sensitive).
Example of store_pack_size.txt Extract File Format:
S303 100052001 1 W3066 2005010120051201
sku_cost.dat
Measure SKU Cost Contains the unit cost of a SKU

from a supplier to a warehouse.
Program Type N/A
Program Name: N/A
Schema File: N/A

sku_cost.dat
Data Origin System External Systems Target Object Type Oracle Database
Source Object Type Fixed Length Text File Target Object Name commodity_cost
Source Object Name sku_cost.dat Target Object Database N/A
Intersection

Position Width

Warehouse Number Warehouse 46 20
Commodity Cost SKU Cost 66 20
Data Type
commodity_code Unique AIP SKU identifier String "100052001 "
supplier_code Unique Supplier identifier String "V11111 "
stocking_point_number Unique Warehouse identifier String "W36 "
commodity_cost SKU Cost sfloat "15.9900 "
None.
All Supplier values should be prefixed with a “V” (case sensitive), and all Warehouses
should be prefixed with a “W” (case sensitive).
Example of sku_cost.dat Extract File Format:
“100052001 V11111 W36 15.9900 “

sku_cost.dat
SKU Cost – Online Load Process
SKU Cost – AIP Oracle Load Process Diagram

sku_weight_volume.dat
Measure SKU Weight and Volume Contains the unit weight and/or
volume of a SKU from a supplier.
Program Type N/A
Program Name: N/A
Schema File: N/A
Data Origin System External Systems Target Object Type Oracle Database
Source Object Type Fixed Length Text File Target Object Name commodity_weight_volume
Source Object Name sku_weight_volume.dat Target Object Database N/A
Intersection

Position Width

Commodity Weight SKU weight 46 20
Commodity Volume SKU volume 66 20

Data Type
commodity_code Unique AIP SKU identifier String "100052001 "
supplier_code Unique Supplier identifier String "V11111 "
commodity_weight SKU weight sfloat "3.0000 "
commodity_volume SKU volume sfloat "0.9560 "
None.
All Supplier values should be prefixed with a “V” (case sensitive).
Example of commodity_weight_volume.dat Extract File Format:
“100052001 V11111 3.0000 0.9560 “

SKU Weight and Volume – Online Load Process
Move file to ONL_INBOUND_DIR.

sku_weight_volume.dat If tarred or compressed unpack
the file.
ONL_INBOUND_DIR/ ONL_SCHEMA_DIR/
sku_weight_volume.dat commodity_weight_volume.xml
Import the sku_weight_volume.dat

file using the schema file
commodity_cost.xml and save the
merged file as temp.v
temp.v
Truncate the oracle table

i_commodity_weight_volume and
load the input file temp.v using RETL
binary and execute
‘retl_load.import_commodity_weight
_volume’ procedure
AIP Oracle
Schema
commodity_weight_volume
SKU Weight and Volume – AIP Oracle Load Process Diagram

12
RO Integration
The integration scheme is broken into two by location type, stores and warehouses. This
serves two purposes
First, the optimization system can be implemented for stores and not warehouses. If
in the future, the optimization system does consider warehouses
Second, AIP can be setup to run a Stores-first implementation which would not
execute warehouse replenishment and therefore would not require optimization.
Store Measure Data

The data mapping below is for stores only.
File and Measure Summary

The table below displays the measure files AIP receives from RO.
File Name Measures Loaded
STR_MINMAX.[txt|cvs] sr0_minstk_i, sr0_maxstk_i and sr0_rplmtd_i

STR_DYNAMIC.[txt|cvs] sr0_svclvl_i, sr0_isd_i and sr0_rplmtd_i
STR_TIMESUPPLY.[txt|cvs] sr0_mints_day_i, sr0_maxts_day_i, sr0_ts_hzn_i and
sr0_rplmtd_i
STR_HYBRID.[txt|cvs] sr0_mints_day_i, sr0_isd_i and sr0_rplmtd_i
STR_POISSON.[txt|cvs] sr0_svclvl_i, sr0_isd_i and sr0_rplmtd_i
STR_MINSS.[txt|cvs] sr0_minss_unt_i
STR_ROUpdate.[txt|cvs] iproupdtstri
STR_MINMAX
Measure Store Min Stock Measure at the SKU/Store/Day level; Used in

MIN/MAX Replenishment Method. Min Stock is used
in determining the inventory level at which
replenishment is triggered.
Measure Store Max Stock Measure at the SKU/Store/Day level; set in
MIN/MAX Replenishment Method. The receipt plan
quantity is calculated to bring Net Inventory up to the
max.
Measure Store Repl Method Measure at the SKU/Store/Day level; The
Replenishment Method determines the type of
calculations that will be used in generating a store
replenishment plan. The default is No Replenishment.
RO Integration 203
Store Measure Data
Program Type Korn Shell Script
Program Name ro_export_to_aip.sh
Schema Files exportMinMax.xml, createFile.xml and

transferFilePositions.xml
Program Frequency On request
Data Origin System RO Target Object Type RPAS Measures

Source Object Type Fixed Length Text File or Target Object Names sr0_minstk_i,
Comma Separated Values sr0_maxstk_i and
File sr0_rplmtd_i
Source Object Name STR_MINMAX.[txt|cvs] Target Object Databases data/sr0_minstk_i,
data/sr0_maxstk_i and
data/sr0_rplmtd_i
Required/Optional Optional Target Object Load day_str_sku_
Intersection

Position Width
aipefctvdate_ Effective date 1 9

STR_ Store 10 20
ITEM SKU 30 20
aipreplpval1_ Replenishment Parameter 1 50 10
aiprplmtd_ Replenishment Method 80 10
Data Type
DAY_ Day String “20081231 ”
STR_ Store String “1001 ”
SKU_ SKU String “123456 ”
sr0_minstk_i Store Min Stock Real “123.456 ”
sr0_maxstk_i Store Max Stock Real “123.456 ”
sr0_rplmtd_i Store Replenishment Method Integer “1 ”

Store Measure Data
Example of STR_MINMAX.txt File:

“20081231 1001 123456 123.456 123.456 1 “
Example of STR_MINMAX.csv File:

“20081231,1001,123456,123.456,123.456,1”
STR_DYNAMIC
Data Type Data Element Data Description

Name
Measure Store Service Measure at the SKU/Store/Day level; Used in Dynamic and Poisson Repl
Level Method. Specifies the target percentage level for customer service of a given
item at a store. For example, if the goal is to carry enough safety stock to
maintain a 90% customer service level, .90 should be entered.
Measure Store Inventory Measure at the SKU/Store/Day level; Used to specify number of DAYS of
Selling Days forecasted quantity to be used when calculating the Receive Up To Level
(RUTL). Used in Hybrid, Dynamic, Poisson and Loaded SS Dynamic
Replenishment Methods. For example, to ensure an order will contain at least
14 days of supply, 14 would be entered. NOTE: The GREATER of Inventory
Selling Days and Review Time will be used in the RUTL calculation.
Measure Store Repl Measure at the SKU/Store/Day level; The Replenishment Method determines
Method the type of calculations that will be used in generating a store replenishment
plan. The default is No Replenishment.
Schema Files exportDynamic.xml, createFile.xml and


Store Measure Data

Source Object Type Fixed Length Text File or Target Object Names sr0_svclvl_i, sr0_isd_i and
Comma Separated Values sr0_rplmtd_i
File
Source Object Name STR_DYNAMIC.[txt|cvs] Target Object Databases data/sr0_svclvl_i,
data/sr0_isd_i and
data/sr0_rplmtd_i
Intersection

Position Width

STR_ Store 10 20
ITEM SKU 30 20
Data Type
sr0_svclvl_i Store Service Level Real “123.456 ”
sr0_isd_i Store Inventory Selling Days Real “123.456 ”
Example of STR_DYNAMIC.txt File:

“20081231 1001 123456 123.456 123.456 3“
Example of STR_DYNAMIC.csv File:

“20081231 1001,123456,123.456,123.456,3”

Store Measure Data
STR_TIMESUPPLY
Measure Store Min Time Measure at the SKU/Store/Day level; Used in Time Supply
Supply Days Replenishment Method. It represents minimum stock level in
DAYS that are desired on hand to satisfy demand. Min Time
Supply Days is used in both safety stock and receipt point
calculations. For example, to ensure a minimum inventory level is
at least 14 DAYS of supply, 14 would be entered.
Measure Store Max Time Measure at the SKU/Store/Day level; Used in the Time Supply
Supply Days Replenishment Method. It represents maximum stock level in
DAYS that are desired on hand to satisfy demand. The receipt plan
quantity is calculated to bring Net Inventory up to Maximum Time
Supply Days. For example, to limit an order to bring the inventory
level to no more than to 14 DAYS of supply, 14 would be entered.
Measure Store Time Supply Measure at the SKU/Store/Day level; The number of DAYS of
Horizon forecast used to calculate an average forecast (rate of sale). The
Rate of Sale (ROS) is then multiplied by the minimum time supply
days to generate the safety stock. The Time Supply Horizon can be
used to smooth spiky forecasts over a longer time period or extend
forecasts if the forecasts are not generated throughout the desired
days of supply. Used in Time Supply Replenishment Method.
NOTE: When time supply horizon is specified, ROS is used instead
of the actual forecast.
Measure Store Repl Method Measure at the SKU/Store/Day level; The Replenishment Method
determines the type of calculations that will be used in generating
a store replenishment plan. The default is No Replenishment.
Schema Files exportTimeSupply.xml, createFile.xml and


Store Measure Data

Source Object Type Fixed Length Text File or Target Object Names sr0_mints_day_i,
Comma Separated Values sr0_maxts_day_i,
File sr0_ts_hzn_i and
sr0_rplmtd_i
Source Object Name STR_TIMESUPPLY.[txt|cvs] Target Object Databases data/sr0_mints_day_i,
data/sr0_maxts_day_i,
data/sr0_ts_hzn_i and
data/sr0_rplmtd_i
Intersection

Position Width

STR_ Store 10 20
ITEM SKU 30 20
aipreplAxP1_ Auxiliary Replenishment Parameter 1 70 10
Data Type
sr0_mints_day_i Store Min Time Supply Days Real “123.456 ”
sr0_maxts_day_i Store Max Time Supply Days Real “123.456 ”
sr0_ts_hzn_i Store Time Supply Horizon Real “123.456 ”

Store Measure Data
Example of STR_TIMESUPPLY.txt File:

“20081231 1001 123456 123.456 123.456 123.456 2
“
Example of STR_TIMESUPPLY.csv File:

20081231,1001,123456,123.456,123.456,123.456,2”
STR_HYBRID
Measure Store Min Time Supply Days Measure at the SKU/Store/Day level; Used in Time Supply
Replenishment Method. It represents minimum stock level in
calculations. For example, to ensure a minimum inventory level is
at least 14 DAYS of supply, 14 would be entered.
Measure Store Inventory Selling Days Measure at the SKU/Store/Day level; Used to specify number of
DAYS of forecasted quantity to be used when calculating the
Receive Up To Level (RUTL). Used in Hybrid, Dynamic, Poisson
and Loaded SS Dynamic Replenishment Methods. For example, to
ensure an order will contain at least 14 days of supply, 14 would
be entered. NOTE: The GREATER of Inventory Selling Days and
Review Time will be used in the RUTL calculation.
Measure Store Repl Method Measure at the SKU/Store/Day level; The Replenishment Method
determines the type of calculations that will be used in generating
a store replenishment plan. The default is No Replenishment.
Schema Files exportHybrid.xml, createFile.xml and


Source Object Type Fixed Length Text File or Target Object Names sr0_mints_day_i,
Comma Separated Values sr0_isd_i and
File sr0_rplmtd_i
Source Object Name STR_HYBRID.[txt|cvs] Target Object Databases data/sr0_mints_day_i,
data/sr0_isd_i and
data/sr0_rplmtd_i

Store Measure Data

Intersection

Position Width

STR_ Store 10 20
ITEM SKU 30 20
Data Type
sr0_mints_day_i Store Min Time Supply Days Real “123.456 ”
Example of STR_HYBRID.txt File:

“20081231 1001 123456 123.456 123.456 5 “
Example of STR_HYBRID.csv File:

“20081231,1001,123456,123.456,123.456,5”

Store Measure Data
STR_POISSON
Measure Store Service Level Measure at the SKU/Store/Day level; Used in Dynamic and Poisson Repl
Method. Specifies the target percentage level for customer service of a given
item at a store. For example, if the goal is to carry enough safety stock to
maintain a 90% customer service level, .90 should be entered.
Measure Store Inventory Measure at the SKU/Store/Day level; Used to specify number of DAYS of
Selling Days forecasted quantity to be used when calculating the Receive Up To Level
(RUTL). Used in Hybrid, Dynamic, Poisson and Loaded SS Dynamic
Replenishment Methods. For example, to ensure an order will contain at least
14 days of supply, 14 would be entered. NOTE: The GREATER of Inventory
Selling Days and Review Time will be used in the RUTL calculation.
Measure Store Repl Method Measure at the SKU/Store/Day level; The Replenishment Method determines
the type of calculations that will be used in generating a store replenishment
plan. The default is No Replenishment.
Schema Files exportPoisson.xml, createFile.xml and


Source Object Type Fixed Length Text File or Target Object Names sr0_svclvl_i, sr0_isd_i and
Comma Separated Values sr0_rplmtd_i
File
Source Object Name STR_POISSON.[txt|cvs] Target Object Databases data/sr0_svclvl_i,
data/sr0_isd_i and
data/sr0_rplmtd_i
Intersection

Store Measure Data

Position Width

STR_ Store 10 20
ITEM SKU 30 20
Data Type
sr0_svclvl_i Store Service Level Real “123.456 ”
Example of STR_POISSON.txt File:

“20081231 1001 123456 123.456 123.456 7 “
Example of STR_POISSON.csv File:

20081231,1001,123456,123.456,123.456,7”
STR_MINSS
Measure Store Min Safety Stock Units Measure at the SKU/Store/Day level; Used in
Minimum Safety Stock Boundaries calculation
to specify the minimum number of UNITS to be
kept on hand as safety stock. Used in Hybrid,
Poisson and Dynamic Replenishment Methods.
For example, to ensure the number of UNITS of
safety stock is at least 10 UNITS, 10 would be
entered.

Store Measure Data
Schema Files exportMinSafetyStock.xml, createFile.xml and transferFilePositions.xml
Data Origin System RO Target Object Type RPAS Measure

Source Object Type Fixed Length Text File or Target Object Name sr0_minss_unt_i
Comma Separated Values
File
Source Object Name STR_MINSS.[txt|cvs] Target Object Database data/minss_unt
Intersection

Position Width

STR_ Store 10 20
ITEM SKU 30 20
aipreplaxp2_ Auxiliary Replenishment Parameter 2 80 10
Data Type
sr0_minss_unt_i Store Min Safety Stock Units Real “123.456 ”
Example of STR_MINSS.txt File:

“20081231 1001 123456 123.456 “
Example of STR_MINSS.csv File:

“20081231,1001,123456,123.456”

Store Measure Data
STR_ROUpdate
Measure Replenishment Mask measure provided by the Replenishment

Optimization Update for Optimization (RO) system. This measure is used to
Stores limit what data will be extracted out of AIP for the
purposes of updating values in RO. The mask also
indicates which SKU/stores will be optimized in the
next run of RO.
Schema Files exportRoUpdate.xml, createFile.xml and


Source Object Type Fixed Length Text File or Target Object Name iproupdtstri
File
Source Object Name STR_ROUpdate.[txt|cvs] Target Object Databases data/ro
Intersection

Position Width
STR_ Store 1 20
ITEM SKU 21 20
aipintxupd_ AIP Intersection Update 41 10

Warehouse Data Interfaces
Data Type
iproupdtstri Replenishment Optimization Boolean “1 ”

Update for Stores
Example of STR_ROUpdate.txt File:

“1001 123456 1 “
Example of STR_ROUpdate.csv File:

“1001,123456,1”

The mapping data below is for warehouses only. AIP supports the import of warehouse
replenishment data however optimization of warehouse replenishment may not be
supported by the receiving application. Check the Oracle Retail Replenishment
Optimization guides and the Retailer’s specific implementation to determine if
warehouses can be optimized.
File and Measure Summary
The table below displays the measure files AIP receives from an optimization system that
is capable of optimizing warehouses.
File Name Measures Loaded

WH_MINMAX.[txt|cvs] ipminstke, ipmaxstke and iprplmtde
WH_DYNAMIC.[txt|cvs] ipsvclvle, ipisde and iprplmtde
WH_TIMESUPPLY.[txt|cvs] ipmindaytse, ipmaxdaytse, iptshzne and iprplmtde
WH_HYBRID.[txt|cvs] ipmindaytse, ipisde and iprplmtde
WH_MINSS.[txt|cvs] ipssminunte
WH_ROUpdate.[txt|cvs] iproupdtwhi

WH_MINMAX
Measure Minimum Stock Exception Measure at the SKU/Dstk/Day level; Used in

MIN/MAX Replenishment Method. Min Stock is
used in determining the inventory level at which
replenishment is triggered.
Measure Maximum Stock Exception Measure at the SKU/Dstk/Day level; set in
MIN/MAX Replenishment Method. The receipt
plan quantity is calculated to bring Net Inventory
up to the max.
Measure Replenishment Method Measure at the SKU/Dstk/Day level; The
Exception Replenishment Method determines the type of
calculations that will be used in generating a
warehouse replenishment plan. The default is No
Replenishment.
Program Name Unknown
Schema Files Unknown

Source Object Type Fixed Length Text File or Target Object Names ipminstke, ipmaxstke and
Comma Separated Values iprplmtde
File
Source Object Name WH_MINMAX.[txt|cvs] Target Object Databases data/MinStk,
data/MaxStk and
data/RplMtd
Required/Optional Optional Target Object Load day_dstksku_
Intersection


Position Width

Unknown Warehouse 10 20
ITEM SKU 30 20
Data Type
WH__ Warehouse String “1001 ”
ipminstke Minimum Stock Exception Real “123.456 ”
ipmaxstke Maximum Stock Exception Real “123.456 ”
iprplmtde Replenishment Method Integer “1 ”

Exception
Example of WH_MINMAX.txt File:

“20081231 1001 123456 123.456 123.456 1 “
Example of WH_MINMAX.csv File:

20081231,1001,123456,123.456,123.456,1”

WH_DYNAMIC
Measure Service Level Exception Measure at the SKU/Dstk/Day level; Used in Dynamic and Poisson Repl
Method. Specifies the target percentage level for customer service of a
given item at a warehouse. For example, if the goal is to carry enough
safety stock to maintain a 90% customer service level, .90 should be
entered.
Measure Inventory Selling Days Measure at the SKU/Dstk/Day level; Used to specify number of DAYS
Exception of forecasted quantity to be used when calculating the Receive Up To
Level (RUTL). Used in Hybrid, Dynamic, Poisson and Loaded SS
Dynamic Replenishment Methods. For example, to ensure an order will
contain at least 14 days of supply, 14 would be entered. NOTE: The
GREATER of Inventory Selling Days and Review Time will be used in
the RUTL calculation.
Measure Replenishment Method Measure at the SKU/Dstk/Day level; The Replenishment Method
Exception determines the type of calculations that will be used in generating a
warehouse replenishment plan. The default is No Replenishment.

Source Object Type Fixed Length Text File or Target Object Names ipsvclvle, ipisde and
Comma Separated Values iprplmtde
File
Source Object Name WH_DYNAMIC Target Object Databases data/SvcLvl,
data/Isd and
data/RplMtd
Intersection


Position Width

ITEM SKU 30 20
Data Type
ipsvclvle Service Level Exception Real “123.456 ”
ipisde Inventory Selling Days Real “123.456 ”

Exception
Exception
Example of WH_DYNAMIC.txt File:

“20081231 1001 123456 123.456 123.456 1 “
Example of WH_DYNAMIC.csv File:

“20081231,1001,123456,123.456,123.456,1”

WH_TIMESUPPLY
Measure Minimum Time Measure at the SKU/Dstk/Day level; Used in Time Supply
Supply Days Replenishment Method. It represents minimum stock level in DAYS that
Exception are desired on hand to satisfy demand. Min Time Supply Days is used in
both safety stock and receipt point calculations. For example, to ensure a
minimum inventory level is at least 14 DAYS of supply, 14 would be
entered.
Measure Maximum Time Measure at the SKU/Dstk/Day level; Used in the Time Supply
Supply Days Replenishment Method. It represents maximum stock level in DAYS that
Exception are desired on hand to satisfy demand. The receipt plan quantity is
calculated to bring Net Inventory up to Maximum Time Supply Days. For
example, to limit an order to bring the inventory level to no more than to
14 DAYS of supply, 14 would be entered.
Measure Time Supply Horizon Measure at the SKU/Dstk/Day level; The number of DAYS of forecast
Exception used to calculate an average forecast (rate of sale). The Rate of Sale (ROS)
is then multiplied by the minimum time supply days to generate the
safety stock. The Time Supply Horizon can be used to smooth spiky
forecasts over a longer time period or extend forecasts if the forecasts are
not generated throughout the desired days of supply. Used in Time
Supply Replenishment Method. NOTE: When time supply horizon is
specified, ROS is used instead of the actual forecast.
Measure Replenishment Measure at the SKU/Dstk/Day level; The Replenishment Method
Method Exception determines the type of calculations that will be used in generating a
warehouse replenishment plan. The default is No Replenishment.
Source Object Type Fixed Length Text File or Target Object Names ipmindaytse,
Comma Separated Values ipmaxdaytse, iptshzne
File and iprplmtde
Source Object Name WH_TIMESUPPLY Target Object Databases data/MinDayTs,

data/MaxDayTs,
data/TsHzn and
data/RplMtd

Required/Optional Optional Target Object Load Intersection day_dstksku_

Position Width

ITEM SKU 30 20
aipreplAxP1_ Auxiliary Replenishment Parameter 1 70 10
Data Type
ipmindaytse Minimum Time Supply Days Real “123.456 ”

Exception
ipmaxdaytse Maximum Time Supply Days Real “123.456 ”
Exception
iptshzne Time Supply Horizon Real “123.456 ”
Exception
Exception
Example of WH_TIMESUPPLY.txt File:

“20081231 1001 123456 123.456 123.456 123.456 1 “
Example of WH_TIMESUPPLY.csv File:

“20081231,1001,123456,123.456,123.456,123.456,1”

WH_HYBRID
Measure Minimum Time Supply Measure at the SKU/Dstk/Day level; Used in Time Supply
Days Exception Replenishment Method. It represents minimum stock level in
calculations. For example, to ensure a minimum inventory
level is at least 14 DAYS of supply, 14 would be entered.
Measure Inventory Selling Days Measure at the SKU/Dstk/Day level; Used to specify number
Exception of DAYS of forecasted quantity to be used when calculating
the Receive Up To Level (RUTL). Used in Hybrid, Dynamic,
Poisson and Loaded SS Dynamic Replenishment Methods. For
example, to ensure an order will contain at least 14 days of
supply, 14 would be entered. NOTE: The GREATER of
Inventory Selling Days and Review Time will be used in the
RUTL calculation.
Measure Replenishment Method Measure at the SKU/Dstk/Day level; The Replenishment
Exception Method determines the type of calculations that will be used
in generating a warehouse replenishment plan. The default is
No Replenishment.
Source Object Type Fixed Length Text File or Target Object Names ipmindaytse, ipisde and
Comma Separated Values File iprplmtde
Source Object Name WH_HYBRID Target Object Databases data/MinDayTs, data/Isd
and data/RplMtd
Intersection


Position Width

ITEM SKU 30 20
Data Type
ipmindaytse Minimum Time Supply Days Real “123.456 ”

Exception
ipisde Inventory Selling Days Exception Real “123.456 ”
iprplmtde Replenishment Method Exception Integer “5 ”
Example of WH_HYBRID.txt File:

“20081231 1001 123456 123.456 123.456 5 “
Example of WH_HYBRID.csv File:

20081231,1001,123456,123.456,123.456,1”

WH_MINSS
Measure Minimum Safety Measure at the SKU/Dstk/Day level; Used in Minimum Safety Stock
Stock Units Boundaries calculation to specify the minimum number of UNITS to be
Exception kept on hand as safety stock. Used in Hybrid, Poisson and Dynamic
Replenishment Methods. For example, to ensure the number of UNITS
of safety stock is at least 10 UNITS, 10 would be entered. NOTE: If both
Min SS DAYS and Min SS UNITS are entered, the larger of min SS units
and demand over min SS days is used.
Source Object Type Fixed Length Text File or Target Object Name ipssminunte
File
Source Object Name WH_MINSS Target Object Database data/SsMinUnt

Intersection

Position Width

ITEM SKU 30 20
aipreplaxp2_ Auxiliary Replenishment Parameter 2 80 10

Target Data Field Target Field Description Target Field Data Condition/Format
Name Type
ipssminunte Minimum Safety Stock Units Exception Real “123.456 ”
Example of WH_MINSS.txt File:

“20081231 1001 123456 123.456 “
Example of WH_MINSS.csv File:

“20081231,1001,123456,123.456”
WH_ROUpdate
Measure Replenishment Mask measure provided by the Replenishment

Optimization Update for Optimization (RO) system. This measure is used to
Stores limit what data will be extracted out of AIP for the
purposes of updating values in RO. The mask also
indicates which SKU/stores will be optimized in the
next run of RO.

Source Object Type Fixed Length Text File or Target Object Name iproupdtwhi
File
Source Object Name STR_ROUpdate Target Object Databases data/ro
Required/Optional Optional Target Object Load dstksku_
Intersection


Position Width
ITEM SKU 21 20
aipintxupd_ AIP Intersection Update 41 10
Data Type
iproupdtwhi Replenishment Optimization Boolean “1 ”

Update for Stores
Example of WH_ROUpdate.txt File:

“1001 123456 1 “
Example of WH_ROUpdate.csv File:

“1001,123456,1”

13
AIP to RMS Interfaces and Data Mapping
RIB Publications
The Oracle Retail Integration Bus (RIB) is a near real-time data synchronization solution
used by AIP for publishing orders to RMS. Order publication begins with the order
release batch adding the affected order to the appropriate message family queue staging
table and marking each message with a sequence number. AIP publishes two sets of
order messages to the RIB, Purchase Orders, and Transfers. RMS subscribes to the RIB
messages and inserts the orders into the appropriate RMS Purchase Order and Transfer
tables.
AIP Message Flow

A polling operation on the database triggers the message creation. The polling is
performed by two threads:
One for the PO_MFQUEUE staging table
One for the TSF_MFQUEUE staging table
The polling is controlled by the configuration settings in the main.properties file.
The order period count defines the number of time intervals that are to be used. An
order period count of 0 indicates that no orders will be released. If the order period
count is 0, no threads are started.
The time interval defines the amount of time the threads sleep. A thread will not go
to sleep until less than the maximum number of allowable messages is processed in a
given call to the publisher (OrderSenderBean). Publishing less than the maximum
allowable messages indicates that all orders on the staging table (at the time it was
queried) have been processed. Any orders added to the staging table afterward will
be processed the next time the thread wakes up and the publisher is invoked.
For each order period count greater than zero, an order period start and order period
end must be added to the properties file. When the thread wakes up and the current
time falls between the start and end of any of the intervals (up to X intervals where X
is the order period count), the thread will call the publication procedure. If desired,
various time intervals can be created to manage the publication of orders by forcing
the threads to only poll the staging tables between certain time periods.
The publisher is an Enterprise Java Session Bean named OrderSenderBean. The
checkAndPublish method will query the staging table and the base order table to get the
message detail. The publisher will also ensure that messages are published to the RIB
in the correct order.
Once the message payload is built by the OrderSenderBean, the RIB message publisher
takes the payload and wraps it with an envelope used by the RIB infrastructure.
AIP to RMS Interfaces and Data Mapping 227

Purchase Order Messages
Purchase Order Messages

The purchase order publication messages are in the XOrder message family. In AIP, this
message family processes the staged orders on the PO_MFQUEUE table.
There are four purchase order message types used by AIP:
XORDERCRE
XORDERDTLCRE
XORDERMOD
XORDERDTLMOD.
All four message types use the XOrderDesc.xsd.
XORDERCRE
This message type indicates that a brand new purchase order is being sent to RMS. The
orders are sent to RMS in an ‘A’pproved status. This message type is inserted into
PO_MFQUEUE in three different circumstances:
1. The purchase order was released by the batch, or you have chosen to release the
purchase order in the OM Order Maintenance screen.
2. You have created a new purchase order in the OM Order Create screen.
3. In the OM Order Maintenance screen, you have chosen to move a purchase order
delivery date and/or destination and generated a new order number.
XORDERDTLCRE
This message type indicates a new line item is being added to the purchase order after
the order was externally communicated. This message type is inserted into
PO_MFQUEUE when you have moved the purchase order destination and chosen to
retain the existing order number, and the destination does not already exist on the order
for that item.
XORDERMOD
This message type indicates that a modification was made to the overall purchase order
details (header level information). This message type is inserted into PO_MFQUEUE in
the following circumstances:
1. You have moved the purchase order delivery date and chosen to retain the existing
order number.
2. You have canceled all ordered quantity of all items on the purchase order. The total
order quantity for the entire purchase order is zero. The purchase order is sent to
RMS with a ‘C’anceled status.
XORDERDTLMOD
This message type indicates that a modification was made to the purchase order line
items after the order was externally communicated. This message type is inserted into
PO_MFQUEUE when you perform various actions in the OM Order Maintenance screen.
1. You have modified the order quantity of a purchase order that is not “Closed.”
2. You have chosen to move a purchase order line item to a new destination and retain
the order number. If the “move to” destination already exists on the order, a message
will be written to the staging table to increase the quantity at the “move to” location.

Transfer Messages
Note: Only one message can be inserted for the “move to”
destination. This will either be an XORDERDTLCRE if the
destination is new or XORDERDTLMOD if the SKU is
already being delivered to the “move to” destination.
The order quantity of the “move from” destination must be decremented to equal the
received quantity. A message will be staged for the “move from” destination.
Transfer Messages
The transfer publication messages are in the XTsf message family. In AIP, this message
family processes the staged orders on the TSF_MFQUEUE table.
There is one transfer message type used by AIP, XTSFCRE, and it uses the XTsfDesc.xsd.
XTSFCRE
This message type indicates that a brand new transfer is being sent to RMS. The transfers
are sent to RMS in an ‘A’pproved status. This message type is inserted into
TSF_MFQUEUE when the transfer is released by the batch.
AIP to RMS Data

The Order Management application within AIP releases the necessary data to be sent to
RMS into staging tables.

AIP to RMS Data
Messages Layout
Purchase Order Header Message Layout
Column Name Data Type RIB XML Message Tag Description/Comments
Order Number string order_no Pre-defined unique number

Supplier ID string supplier Supplier unique identifier
Currency Code string currency_code
Terms string Terms
Delivery Date Date not_before_date Earliest expected delivery date.
not_after_date Latest expected delivery date.
Open-to-buy End-of- Date otb_eow_date
Week Date
Department number dept
Status string Status A status value of “W”orksheet or
“A”pproved is required for
purchase order creation. A
purchase order may not be created
in approved status without detail
line items attached to it.
Attempting to do so will result in
message rejection.
Exchange Rate number exchange_rate
Include on Order string include_on_ord_ind
indicator
Written Date Date written_date
Order Line Item Detail Pointer XOrderDtl This is a pointer to the line item
details. Depending on the message
type, this tag is repeated for each
line item. See below for the Order
Detail Message layout.
Origin Indicator String orig_ind Indicates the System of
Origination.
EDI string edi_po_ind
Pre-Mark Indicator String pre_mark_ind
User ID String user_id
Comments String Comment_desc

AIP to RMS Data
Purchase Order – Detail Message Layout
RMS SKU string XOrderDtl.item Uses the RMS SKU mapping table to
convert AIP commodity pack size into
RMS SKU.
Location integer XOrderDtl.location Globally unique scheduling location
identifier
Unit Cost decimal xOrderDtl.unit_cost Not Available
Reference item string xOrderDtl.ref_item
Origin Country string xOrderDtl.origin_conunty_id
Indicator
Supplier Pack Size decimal XOrderDtl.supp_pack_size
Order Quantity decimal XOrderDtl.qty_ordered
Location Type string XorderDtl.location_type Order Destination Type: Store or
Warehouse
Cancel Indicator string xOrderDtl.cancel_ind
Reinstate Indicator string xOrderDtl.reinstate_ind
Transfers – Header Message Layout
Transfer Number Integer tsf_no Pre-defined unique number

From Location Type String from_loc_type
From Location String from_loc
To Location Type String to_loc_type
To Location String to_loc
Delivery Date Date delivery_date
Department Integer dept Not available in AIP.
Routing Code String routing_code Not Available in AIP
Freight Code String freight_code Not Available in AIP
Transfer Type String tsf_type
Transfer Detail Pointer XTsfDtl* See Transfer Create Details.
Transfer Status String status
User ID String user_id
Comments String comment_desc

AIP to RMS Data
Transfers – Detail Message Layout
RMS SKU string xTsfDtl.item

Transfer Quantity decimal xTsfDtl.tsf_qty
Pack Size decimal xTsfDtl.supp_pack_size
Inventory Status integer xTsfDtl.inv_status
Unit Cost decimal XTsfDtl.unit_cost
Purchase Orders and Transfers Message Flow in AIP
Purchase Orders and Transfers Message Flow Diagram

AIP to RMS Data
Store – Purchase Orders and Transfers Message Flow
Store – Purchase Orders and Transfers Message Flow Diagram (1 of 2)

AIP to RMS Data
Store – Purchase Orders and Transfers Message Flow (2 of 2)

Warehouse – Purchase Orders and Transfers Message Flow
Warehouse – Purchase Orders and Transfers Message Flow Diagram (1 of 2)

Warehouse – Purchase Orders and Transfers Message Flow (2 of 2)

Data Formats for Creating Order – XORDERCRE

RIB Publication Message Create Order Contains Purchase Order header

and details.
Program Type EJB
Program Name OrderSenderBean.java
Schema File N/A
Program Frequency Near Real Time
Data Origin System AIP Online Target Object Type RIB Message - Xorder
Family
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name XORDERCRE Message
SUPPLIER, PO_MFQUEUE,
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT
Target Load Type N/A

# Source Table Source Table Column Source Field Data Type Field
Description Length
1 PO_MFQUEUE ORDER_NUMBER Order Number Number (10,0)

2 SUPPLIER SUPPLIER_CODE Supplier Code Varchar2 20
3 N/A N/A N/A N/A N/A
5 STORE_ORDER DELIVERY_DATE Delivery Date Date N/A
NON_CONTENTS
_ORDER
NON_CONTENTS
_ORDER
9 PO_MFQUEUE STATUS Status Varchar2 1
13 XORDER Detail Records
COMMODITY_MAPPING RMS_SKU_NUMBER RMS SKU Varchar2 25
STORE STORE_CODE Store Code Varchar2 20
STOCKING_POINT STOCKING_POINT_NUMBER Stocking Point Number
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
COMMODITY_MAPPING RMS_ORDER_MULTIPLE RMS Order Multiple Number 8
STORE_ORDER CASE_VOLUME Case Volume Number 8
NON_CONTENTS_ORDER QUANTITY Quantity
COMMODITY_MAPPING PACK_SIZE Pack Size
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

# Target Data Field Target Field Description Field Data Field Condition/Format
Name Type Length
1 order_no The unique identifier for Varchar2 10 N/A

the order
2 supplier The identifier of the Varchar2 10 A substring is used to drop the
supplier from which the “V” prefix that is appended to all
order will be sourced. This RMS supplier numbers.
cannot be modified if
details exist for the PO.
3 currency_code The code of the order's Varchar2 3 Hardcoded as NULL
currency.
4 terms The sales terms of the Varchar2 15 Hardcoded as NULL
order.
5 not_before_date The first date that delivery Date Select the minimum delivery
will be accepted. date from the order line items
which are not closed. All order
line items which are not closed
will have the same delivery date.
6 not_after_date The last date that delivery Date Select the maximum delivery
will be accepted. date from the order line items
which are not closed. All order
line items which are not closed
will have the same delivery date.
7 otb_eow_date The end of week date of Date Hardcoded as NULL
the OTB bucket used.
8 dept The department in which Number 4 Hardcoded as NULL
are all the items on the
order.
9 status The code for the status of Varchar2 1 The table column has a default of
the order. Valid values are ‘A’
“W” worksheet and 'A'
approved for PO creation.
It is also possible to
modify the status to 'C'
closed.
10 exchange_rate The rate of exchange for Number 20 Hardcoded as NULL
the PO used between the
order and primary
currencies.
11 include_on_ord_ind Indicates if the order Varchar2 1 Hardcoded as NULL
should be included in on-
order calculations.
12 written_date The date the order was Date Hardcoded as NULL
created.

Name Type Length
13 XORDER Detail Records

item An approved, transaction Varchar2 25 N/A
level item
location An active store or Number (10,0) A substring is used to drop the
warehouse “S” prefix that is appended to all
RMS store numbers and to drop
the “W” prefix that is appended
to all RMS warehouse numbers.
unit_cost The cost of the item from Number (20,4) Hardcoded as NULL
the supplier in the order's
currency
ref_item The id of a reference item Varchar2 25 Hardcoded as NULL
which can be used instead
of using the item field
origin_country_id The identifier of the Varchar2 3 Hardcoded as NULL
country from which the
item is being sourced
supp_pack_size The supplier pack size for Number (12,3) The AIP SKU-pack size is
the item on the order mapped to the RMS Item and
Order Multiple.
qty_ordered The quantity ordered of Number (12,4) Non-pack SKUs·:
item store_order.case_volume x
commodity_mapping.pack_size·
non_contents_order.quantity x
commodity_mapping.pack_size
Formal Pack SKUs:
store_order.case_volume·
non_contents_order.quantity
location_type The location type of the Varchar2 1 S indicates the destination
location location is a store.
W indicates the destination
location is a warehouse.
cancel_ind Indicates if the detail Varchar2 1 Hardcoded as NULL
record's quantity should
be cancelled
reinstate_ind Indicates if a detail record Varchar2 1 Hardcoded as NULL
which was previously
cancelled should be
reinstated

Name Type Length
14 origin_ind Indicates where the order Varchar2 1 6 is a unique RMS identifier that
originated. Valid values indicates the PO was created in
include: 2 - Manual, 6 - AIP and is hardcoded
AIP generated order, 7 , 8.
15 edi_po_ind Indicates whether or not Varchar2 1 Hardcoded as NULL
the order will be
transmitted to the supplier
via an Electronic Data
Exchange transaction.
Valid values are: Y =
Submit via EDI, N = Do
not use EDI.
16 pre_mark_ind This field indicated Varchar2 1 Hardcoded as NULL
whether or not a supplier
has agreed to break an
order into separate boxes
so that the boxes can be
sent directly to stores.
17 user_id Indicates where the order Varchar2 30 Hardcoded as NULL
was approved. It will be
the user ID of the person
approving the order.
18 comment_desc Any comments pertaining Varchar2 2000 Hardcoded as NULL
to the order.
Store Orders
poQ.file_interface_ind = 'N' AND so.order_number = poQ.order_number AND
so.future_release_ind = 'N' AND so.supplier_id = supp.supplier_id AND
so.commodity_id=cm.commodity_id AND so.pack_size=cm.pack_size AND
s.store_id=so.store_id AND (poQ.store_order_id=so.store_order_id OR
poQ.store_order_id IS NULL)
Warehouse Orders
poQ.file_interface_ind = 'N' AND nco.order_number = poQ.order_number AND
nco.source_type='V' AND nco.source_id=s.supplier_id AND
nco.commodity_id=cm.commodity_id AND nco.pack_size=cm.pack_size AND
nco.stocking_point_id = chamber.stocking_point_id AND
(poQ.non_contents_order_id=nco.non_contents_order_id OR poQ.non_contents_order_id
IS NULL) AND wh.stocking_point_id(+) = chamber.parent_stocking_point_id

Create Order Layout – XORDERDTLCRE

The Order Detail create message is the same format and basic content as the Order Create
message; however, the message will only contain any new order line items. Any line
items which have already been communicated to RMS will not be included in an Order
Detail Create message.
RIB Publication Message Create Order Detail Contains Purchase Order Header
and new detail information.
Program Type EJB
Schema File N/A
Family
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name XORDERDTL Detail
SUPPLIER, PO_MFQUEUE, Message
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT
# Source Table Source Table Column Source Field Source Field

Description Data Type Length
1 COMMODITY_MAPPING RMS_SKU_NUMBER RMS SKU Varchar2 25

2 STORE STORE_CODE Store Code Varchar2 20
6 COMMODITY_MAPPING RMS_ORDER_MULTIPLE RMS Order Multiple Number 8


7 STORE_ORDER CASE_VOLUME Case Volume Number 8

# Target Data Target Field Field Data Field Length Condition/Format

1 item An approved, Varchar2 25 N/A

transaction level item
2 location An active store or Number (10,0) A substring is used to drop the “S”
warehouse prefix that is appended to all RMS
store numbers and to drop the
“W” prefix that is appended to all
RMS warehouse numbers.
3 unit_cost The cost of the item Number (20,4) Hard coded as NULL
from the supplier in
the order's currency
4 ref_item The id of a reference Varchar2 25 Hard coded as NULL
item which can be
used instead of using
the item field
5 origin_country The identifier of the Varchar2 3 Hard coded as NULL
_id country from which
the item is being
sourced
6 supp_pack_siz The supplier pack size Number (12,3) The AIP SKU-pack size is mapped
e for the item on the to the RMS Item and Order
order Multiple.
7 qty_ordered The quantity ordered Number (12,4) Non-pack SKUs:
of item store_order.case_volume x
Formal Pack SKUs:
8 location_type The location type of Varchar2 1 S indicates the destination location
the location is a store.

# Target Data Target Field Field Data Field Length Condition/Format

9 cancel_ind Indicates if the detail Varchar2 1 Hard coded as NULL

record's quantity
should be cancelled
10 reinstate_ind Indicates if a detail Varchar2 1 Hard coded as NULL
record which was
previously cancelled
should be reinstated
Store Orders
so.order_number=pm.order_number AND so.supplier_id = supp.supplier_id AND
s.store_id=so.store_id AND (pm.store_order_id=so.store_order_id OR
pm.store_order_id IS NULL)
Warehouse Orders
nco.source_type=“V” AND nco.order_number=pm.order_number AND
nco.source_id=s.supplier_id AND nco.commodity_id=cm.commodity_id AND
nco.pack_size=cm.pack_size AND nco.stocking_point_id = sp1.stocking_point_id AND
(pm.non_contents_order_id=nco.non_contents_order_id OR pm.non_contents_order_id IS
NULL) AND sp2.stocking_point_id(+) = sp1.parent_stocking_point_id
Modify Order Header Layout – XORDERMOD

RIB Publication Message Modify Order Header Contains Purchase Order header details.
Program Type EJB
Schema File N/A

Family
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name XORDERMOD Header
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT
# Source Table Source Table Source Field Description Source Field

Column Data Type Length

NON_CONTENTS_ORDER
NON_CONTENTS_ORDER

# Target Data Field Target Field Description Target Field Field Length Condition/Format
Name Data Type
1 order_no The unique identifier for the Varchar2 10 N/A

order
2 supplier The identifier of the supplier Varchar2 10 A substring is used
from which the order will be to drop the “V”
sourced. This cannot be prefix that is
modified if details exist for the appended to all
PO. RMS supplier
numbers.
3 currency_code The code of the order's Varchar2 3 Hardcoded as
currency. NULL
4 terms The sales terms of the order. Varchar2 15 Hardcoded as
NULL
5 not_before_date The first date that delivery will Date Select the minimum
be accepted. delivery date from
the order line items
which are not
closed. All order line
items which are not
closed will have the
same delivery date.
6 not_after_date The last date that delivery will Date Select the maximum
be accepted. delivery date from
the order line items
which are not
closed. All order line
items which are not
closed will have the
same delivery date.
7 otb_eow_date The end of week date of the Date Hardcoded as
OTB bucket used. NULL
8 dept The department in which are Number 4 Hardcoded as
all the items on the order. NULL
9 status The code for the status of the Varchar2 1 The table column
order. Valid values are “W” has a default of ‘A’.
worksheet and 'A' approved If all order
for PO creation. It is also quantities are 0 the
possible to modify the status to status of “C”ancel
'C' closed. must be sent to
RMS.
10 exchange_rate The rate of exchange for the Number 20 Hardcoded as
PO used between the order NULL
and primary currencies.
11 include_on_ord_ind Indicates if the order should be Varchar2 1 Hardcoded as
included in on-order NULL
calculations.

# Target Data Field Target Field Description Target Field Field Length Condition/Format
Name Data Type
12 written_date The date the order was Date Hardcoded as

created. NULL
13 origin_ind Indicates where the order Varchar2 1 6 is a unique RMS
originated. Valid values identifier that
include: 2 - Manual, 6 - AIP indicates the PO was
generated order, 7 , 8. created in AIP and is
hardcoded
14 edi_po_ind Indicates whether or not the Varchar2 1 Hardcoded as
order will be transmitted to the NULL
supplier via an Electronic Data
Exchange transaction. Valid
values are: Y = Submit via EDI,
N = Do not use EDI.
15 pre_mark_ind This field indicated whether or Varchar2 1 Hardcoded as
not a supplier has agreed to NULL
break an order into separate
boxes so that the boxes can be
sent directly to stores.
16 user_id Indicates where the order was Varchar2 30 Hardcoded as
approved. It will be the user ID NULL
of the person approving the
order.
17 comment_desc Any comments pertaining to Varchar2 2000 Hardcoded as
the order. NULL
Store Orders
Warehouse Orders

Modify Order Layout – XORDERDTLMOD

The Order Detail Modification message is the same format and similar content as the
Order Create message; however, the message will only contain any modified order line
items. Any line items which have already been communicated to RMS but have not been
modified will not be included in an Order Detail Modification message.
RIB Publication Message Modify Order Detail Contains Purchase Order header
and detail information.
Program Type EJB
Schema File N/A
Family
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name XORDERDTLMOD
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT
Description Length


Description Length
7 STORE_ORDER CASE_VOLUME_DELTA Case Volume Number 8

NON_CONTENTS_ORDER QUANTITY_DELTA Quantity
# Target Data Target Field Description Field Data Field Condition/Format

Field Name Type Length
1 item An approved, transaction Varchar2 25 N/A

level item
2 location An active store or warehouse Number (10,0) A substring is used to drop the
“S” prefix that is appended to
all RMS store numbers and to
drop the “W” prefix that is
appended to all RMS warehouse
numbers.
3 unit_cost The cost of the item from the Number (20,4) Hardcoded as NULL
supplier in the order's
currency
4 ref_item The id of a reference item Varchar2 25 Hardcoded as NULL
which can be used instead of
using the item field
5 origin_country_id The identifier of the country Varchar2 3 Hardcoded as NULL
from which the item is being
sourced
6 supp_pack_size The supplier pack size for Number (12,3) The AIP SKU-pack size is
the item on the order mapped to the RMS Item and
Order Multiple.
7 qty_ordered Changed quantity in eaches Number (12,4) Non-pack SKUs·:
store_order.case_volume_delta
x
_delta x
Formal Pack SKUs:
8 location_type The location type of the Varchar2 1 S indicates the destination
location location is a store.

# Target Data Target Field Description Field Data Field Condition/Format

Field Name Type Length
9 cancel_ind Indicates if the detail Varchar2 1 Hardcoded as NULL

record's quantity should be
cancelled
10 reinstate_ind Indicates if a detail record Varchar2 1 Hardcoded as NULL
which was previously
cancelled should be
reinstated
Store Orders
Warehouse Orders
Create Transfer Layout – XTSFCRE

RIB Publication Message New Transfer Contains Transfer header and

details.
Program Type EJB
Schema File N/A

Data Origin System AIP Online Target Object Type RIB Message XTsf
Family
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name XTSFCRE Message
TSF_MFQUEUE,
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT

1 TSF_MFQUEUE TSF_NUMBER Transfer Number Number (10,0)

3 STOCKING_POINT STOCKING_POINT_NUMBER N/A N/A N/A
NON_CONTENTS_ORDER
11 XTSF Detail Records Layout
COMMODITY_MAPPING RMS_SKU_NUMBER RMS SKU Varchar2 25
STORE_ORDER CASE_VOLUME Case Volume Number 8
COMMODITY_MAPPING RMS_ORDER_MULTIPLE RMS Order Multiple Number 8
N/A N/A N/A N/A N/A
N/A N/A N/A N/A N/A

# Target Data Field Name Target Field Field Data Field Condition/Format
Description Type Length
1 tsf_no Number that Number 10 N/A

uniquely
identifies the
transfer
2 from_loc_type The location type Varchar2 1 Hardcoded as “W”
of the from
location
3 from_loc The location Varchar2 10 A substring is used to drop the
number of the “W” prefix that is appended to
from location all RMS warehouse numbers.
4 to_loc_type The location type Varchar2 1 S' indicates the destination
of the to location location is a store.
“W” indicates the destination
5 to_loc The location Varchar2 10 A substring is used to drop the
number of the to “S” prefix that is appended to all
location RMS store numbers and to drop
the “W” prefix that is appended
to all RMS warehouse numbers.
6 delivery_date The earliest date Date N/A
the transfer can be
delivered.
7 dept The department Number 4 Hardcoded as NULL
number
associated with
the transfer
8 routing_code If the freight Varchar2 1 Hardcoded as NULL
status is expedite,
this is a code
indicating more
detailed freight
info
9 freight_code A code indicating Varchar2 1 Hardcoded as NULL
the freight status
of the transfer
(e.g. normal,
expedite, etc.).
10 tsf_type A code indicating Varchar2 6 Hardcoded as “AIP”
the type of
transfer (e.g. store
requisition, book
transfer, etc.).

# Target Data Field Name Target Field Field Data Field Condition/Format
Description Type Length
11 XTSF Detail Record Layout

item The unique Varchar2 25 N/A
identifier of the
item being
transferred.
tsf_qty The total quantity Number (12,4) Non-pack SKUs·:
of the item store_order.case_volume x
reserved for this commodity_mapping.pack_size·
transfer at the non_contents_order.quantity x
from location. commodity_mapping.pack_size
Formal Pack SKUs:
supp_pack_size The supplier pack Number (12,4) The AIP SKU-pack size is
size for this mapped to the RMS Item and
item/transfer. Order Multiple.
inv_status A code indicating Number 2 Hardcoded as NULL
the inventory
status for this
transfer detail;
valid values are
found on the
inv_status_types
table.
unit_cost Not mapped to a Number (20,4) Hardcoded as NULL
database field.
Sometimes used
to calculate retail
price.
12 status A code indicating Varchar2 1 The transfer will be created in
the status of the ‘Approved’ status so hardcoded
transfer (e.g. as 'A'
approved, closed,
etc.).
13 user_id The user ID of the Varchar2 30 Hardcoded as NULL
user who created
the transfer.
14 comment_desc Comments Varchar2 2000 Hardcoded as NULL
associated with
the transfer.
None.

AIP Purchase Order Messages – RMS Load Process
AIP Purchase Order Messages – RMS Load Process Diagram (1 of 2)

AIP Purchase Order Messages – RMS Load Process Diagram (2 of 2)

AIP Transfer Messages – RMS Load Process
AIP Transfer Messages – RMS Load Process Diagram

XORDER Header – RMS ORDHEAD Mapping

RMS Subscriber Mapping Create/Modify Order Header Contains Purchase Order header
details.
Program Type RIB Subscriber Adapter
Program Name RMS Subscriber Adapter
Schema File N/A
Data Origin System AIP Online Target Object Type RMS Database
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name ORDHEAD Table
SUPPLIER, PO_MFQUEUE,
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT




12 STORE_ORDER min of Delivery Date Date N/A

NON_CONTENTS_ORDER DELIVERY_DATE
13 STORE_ORDER max of Delivery Date Date N/A
NON_CONTENTS_ORDER DELIVERY_DATE




The target table for all data is ORDHEAD.
# Target Data Field Name Target Field Description Field Data Field Condition/Format
Type Length
1 ORDER_NO The unique identifier for NUMBER (8,0) N/A

the order
2 ORDER_TYPE Order Type VARCHAR2 3 Hardcode as 'N/B' at
destination
3 DEPT NUMBER (4,0) Hardcoded as NULL
at Source
4 BUYER NUMBER (4,0) NULL
5 SUPPLIER The identifier of the NUMBER (10,0) A substring is used to
supplier from which the drop the “V” prefix
order will be sourced. This that is appended to all
cannot be modified if RMS supplier
details exist for the PO. numbers.

Type Length
6 SUPP_ADD_SEQ_NO Supplier Address Sequence NUMBER (4,0) Populated with

Number primary address
sequence number for
the primary supplier
7 LOC_TYPE Location Type VARCHAR2 1 NULL
8 LOCATION Location Type NUMBER (10,0) NULL
9 PROMOTION Promotion Number NUMBER (10,0) NULL
10 QC_IND QC Indicator VARCHAR2 1 Hardcoded as 'N' at
destination
11 WRITTEN_DATE The date order was created DATE Hardcoded as today's
Vdate
12 NOT_BEFORE_DATE The first date that delivery DATE If Source value is
will be accepted. NULL, then Vdate
Else Source Value.
13 NOT_AFTER_DATE The last date that delivery DATE If Source value is
will be accepted. NULL, then Vdate
Else Source Value.
14 OTB_EOW_DATE The end of week date of DATE Populated with EOW
the OTB bucket used. date for the date
NOT_AFTER_DATE
at destination
15 EARLIEST_SHIP_DATE Earliest Shipment Date DATE Populated as
NOT_BEFORE_DATE
at destination
16 LATEST_SHIP_DATE Latest Shipment Date DATE Calculated at
destination as
NOT_BEFORE_DATE
+
LATEST_SHIP_DAYS
from
SYSTEM_OPTIONS
table
17 CLOSE_DATE Order Close Date DATE Hardcoded as NULL
18 TERMS The sales terms of the VARCHAR2 15 Populated as TERMS
order. of primary supplier
from SUPS table
19 FREIGHT_TERMS The freight terms of the VARCHAR2 30 Populated as
order. FREIGHT_TERMS of
primary supplier from
SUPS table
20 ORIG_IND Indicates where the order NUMBER (1,0) 6 is a unique RMS
originated. Valid values identifier that
include: 2 - Manual, 6 - AIP indicates the PO was
generated order, 7 , 8. created in AIP and is
hardcoded at source

Type Length
21 CUST_ORDER Customer Order Indicator VARCHAR2 1 Hardcoded as 'N' at

destination
22 PAYMENT_METHOD Payment Method for the VARCHAR2 6 Populated as
Order PAYMENT_METHOD
of primary supplier
from SUPS table
23 BACKHAUL_TYPE Backhaul Type VARCHAR2 6 NULL
24 BACKHAUL_ALLOWANCE Backhaul Allowance NUMBER (20,4) NULL
25 SHIP_METHOD Shipping Method VARCHAR2 6 Populated as
SHIP_METHOD of
primary supplier from
SUPS table
26 PURCHASE_TYPE Purchase Type VARCHAR2 6 NULLablel column
27 STATUS The code for the status of VARCHAR2 1 Source has the status
the order. as 'A'
28 ORIG_APPROVAL_DATE Original Approval Date of DATE If Status is Approved,
the Order hardcoded as VDATE
at destination Else
NULL
29 ORIG_APPROVAL_ID Original Approval User ID VARCHAR2 30 User ID used to run
the batch/adapter
30 SHIP_PAY_METHOD Shipment Pay Method VARCHAR2 2 NULL
31 FOB_TRANS_RES Trans Reserve VARCHAR2 2 NULL
32 FOB_TRANS_RES_DESC Trans Reserve Description VARCHAR2 45 NULL
33 FOB_TITLE_PASS Title Pass VARCHAR2 2 Populated as
FOB_TITLE_PASS
from
SYSTEM_OPTIONS
table
34 FOB_TITLE_PASS_DESC Title Pass Description VARCHAR2 45 NULL
35 EDI_SENT_IND EDI Sent Indicator VARCHAR2 1 Hardcoded as 'N' at
destination
36 EDI_PO_IND EDI PO Indicator VARCHAR2 1 Hardcoded as 'N' at
destination
37 IMPORT_ORDER_IND Import Order Indicator VARCHAR2 1 Hardcoded as 'N' at
destination
38 IMPORT_COUNTRY_ID Imported Country ID VARCHAR2 3 Populated as
BASE_COUNTRY_ID
from
SYSTEM_OPTIONS
table
39 PO_ACK_RECVD_IND PO Acknowledgement VARCHAR2 1 Hardcoded as 'N' at
Received Indicator destination

Type Length
40 INCLUDE_ON_ORDER_IND Indicates if the order VARCHAR2 1 Hardcoded as 'Y' at

should be included in on- destination
order calculations.
41 VENDOR_ORDER_NO Vendor Order Indicator VARCHAR2 15 NULL
42 EXCHANGE_RATE The rate of exchange for NUMBER (20,10) Populated as
the PO used between the Exchange rate for the
order and primary primary currency and
currencies. exchange type 'P'
43 FACTORY Factory VARCHAR2 10 NULL
44 AGENT Agent VARCHAR2 10 NULL
45 DISCHARGE_PORT Discharge Port VARCHAR2 5 NULL
46 LADING_PORT Landing Port VARCHAR2 5 NULL
47 BILL_TO_ID Location to be billed VARCHAR2 5 Populated as
BILL_TO_LOC from
SYSTEM_OPTIONS
table
48 FREIGHT_CONTRACT_NO Freight Contract Number VARCHAR2 10 NULL
49 PO_TYPE PO Type VARCHAR2 4 NULL
50 PRE_MARK_IND Pre Mark Indicator VARCHAR2 1 Hardcoded as 'N' at
destination
51 CURRENCY_CODE Currency Code of the order VARCHAR2 3 Populated as
CURRENCY_CODE
of the primary
supplier from SUPS
table
52 REJECT_CODE Rejection Code VARCHAR2 6 NULL
53 CONTRACT_NO Contract Number NUMBER (6,0) NULL
54 LAST_SENT_REV_NO Last Sent Review Number NUMBER (6,0) NULL
55 SPLIT_REF_ORDNO Split Order Reference NUMBER (8,0) NULL
Number
56 PICKUP_LOC Pickup Location VARCHAR2 45 NULL
57 PICKUP_NO Pickup Number VARCHAR2 25 NULL
58 PICKUP_DATE Pickup Date DATE If
NOT_BEFORE_DATE
is not null then
NOT_BEFORE_DATE
else VDATE
59 APP_DATETIME Approved Date & Time DATE NULL
60 COMMENT_DESC Comments VARCHAR2 250 NULL
None.

XORDER Detail – ORDSKU & ORDLOC Mapping

This section addresses the RMS Subscriber mappings from the XORDER detail message,
which contains Purchase Order line item detail. The detail information contained in the
message is mapped to two RMS database tables, the Order SKU (ORDSKU) and Order
Location (ORDLOC) tables.
RMS Subscriber Mapping Create/Modify Order Detail Contains Purchase Order Line
Item details
Schema File N/A
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name ORDSKU & ORDLOC
SUPPLIER, PO_MFQUEUE, Tables
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT
Field Level Mapping – Source for Order SKU (ORDSKU) Table

The following table shows source data mapped to the Order SKU (ORDSKU) table.
# Source Table Source Table Column Source Field Description Data Type Field
Length


# Source Table Source Table Column Source Field Description Data Type Field
Length

Field Level Mapping – Target Order SKU (ORDSKU) Table

The following table displays target attributes for the source data being mapped to the
Order SKU table (ORDSKU).
Name Type Length
1 ORDER_NO The unique identifier for the NUMBER (8,0) N/A

order
2 ITEM An approved, transaction VARCHAR2 25
level item
3 REF_ITEM The id of a reference item VARCHAR2 25 Hardcoded as NULL at
which can be used instead of Source
using the item field.
4 ORIGIN_COUNTRY_ID The identifier of the country VARCHAR2 3 Populated as
from which the item is being ORIGIN_COUNTRY_ID
sourced of the primary supplier
& item combination
from
ITEM_SUPP_COUNTRY
table
5 EARLISET_SHIP_DATE Earliest Shipment Date DATE Populated as
EALISET_SHIP_DATE
of the header row from
ORDHEAD table
6 LATEST_SHIP_DATE Latest Shipment Date DATE Populated as
LATEST_SHIP_DATE of
the header row from
ORDHEAD table
7 SUPP_PACK_SIZE The supplier pack size for NUMBER (12,4) NULL
the item on the order
8 NON_SCALE_IND Non Scale Indicator VARCHAR2 1 Hardcoded as “Y” at
destination
9 PICKUP_LOC Pickup Location VARCHAR2 45 NULL
10 PICKUP_NO Pickup Number VARCHAR2 25 NULL

Field Level Mapping – Source for Order Location (ORDLOC) Table

The following table shows source data mapped to the Order Location (ORDLOC) table.
Description Length


Field Level Mapping – Target Order Location (ORDLOC) Table

The following table displays source data that is mapped to Order Location table
(ORDLOC).
Target Data Field Target Field Field Data Field Condition/Format

Name Description Type Length
1 ORDER_NO The unique identifier NUMBER (8,0) N/A

for the order
2 ITEM An approved, VARCHAR2 25
transaction level item
3 LOCATION An active store or NUMBER (10,0) A substring is used to drop the
warehouse. If “S” prefix that is appended to
multichannel is on, and all RMS store numbers and to
a warehouse is being drop the “W” prefix that is
order to, a virtual appended to all RMS warehouse
warehouse is expected numbers at Source
4 LOC_TYPE The location type of the VARCHAR2 1 S indicates the destination
location. location is a store at Source
location is a warehouse at
Source
5 UNIT_RETAIL Unit Retail price for NUMBER (20,4) Calculated at destination as for
item & location non-sellable pack item, build
combination the unit_retail based on
component items unit_retail
and for non-pack item or
sellable pack item, get the
unit_retail from
item_zone_price
6 QTY_ORDERED The quantity ordered NUMBER (12,4) Non-pack SKUs·:
of item store_order.case_volume x
Formal Pack SKUs:
7 QTY_PRESCALED Quantity Prescaled NUMBER (12,4) Populated same as
QTY_ORDERED at destination
8 QTY_RECEIVED Received Quantity NUMBER (12,4) NULL
9 LAST_RECEIVED Last Received Quantity NUMBER (12,4) NULL
10 LAST_ROUNDED_QTY Last Rounded Quantity NUMBER (12,4) NULL
11 LAST_GRP Last GRP Rounded NUMBER (12,4) NULL
_ROUNDED_QTY Quantity
12 QTY_CANCELLED Quantity Cancelled NUMBER (12,4) NULL
13 CANCEL_CODE Cancellation Code VARCHAR2 1 NULL
14 CANCEL_DATE Cancellation Date DATE NULL
15 CANCEL_ID User ID Cancelled VARCHAR2 30 NULL


16 ORIGINAL_REPL_QTY Original NUMBER (12,4) NULL

Replenishment
Quantity
17 UNIT_COST The cost of the item NUMBER (20,4) Populated from
from the supplier in the ITEM_SUPP_COUNTRY_LOC
order's currency or ITEM_SUPP_COUNTRY for
the combination
item/supplier/country/loc.
18 UNIT_COST_INIT Initial Unit Cost NUMBER (20,4) NULL
19 COST_SOURCE VARCHAR2 4 Hardcoded as “NORM” at
destination
20 NON_SCALE_IND VARCHAR2 1 Hardcoded as “Y” at
destination
21 TSF_PO_LINK_NO NUMBER (10,0) NULL
None.
XTSF Header – RMS TSFHEAD Mapping

RMS Subscriber Mapping Create Transfer Header Contains Transfer header details.
Schema File N/A

Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name TSFHEAD Table
TSF_MFQUEUE,
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT
Field Level Mappings – Source
Description Length
1 TSF_MFQUEUE TSF_NUMBER Order Number Number (10,0)

3 STOCKING_POINT STOCKING_POINT_NUMBER N/A N/A N/A
NON_CONTENTS_ORDER


1 TSF_NO Number that uniquely NUMBER (10,0) N/A

identifies the transfer.
2 FROM_LOC_TYPE The location type of the VARCHAR2 1 Hardcoded as “W” at Source
from location.
3 FROM_LOC The location number of NUMBER (10,0) A substring is used to drop the
the from location. “W” prefix that is appended to
all RMS warehouse numbers.
4 TO_LOC_TYPE The location type of the VARCHAR2 1 Hardcoded as “S” which
to location. indicates the destination
location is a store
“W” indicates the destination
5 TO_LOC The location number of NUMBER (10,0) A substring is used to drop the
the to location. “S” prefix that is appended to
all RMS store numbers and to
drop the “W” prefix that is
appended to all RMS warehouse
numbers.
6 DEPT The department NUMBER (4,0) Hardcoded as NULL at Source
number associated
with the transfer.
7 TSF_TYPE A code indicating the VARCHAR2 6 Hardcoded as “AIP” at Source
type of transfer (e.g.
store requisition, book
transfer, etc.).
8 STATUS A code indicating the VARCHAR2 1 The transfer will be created in
status of the transfer ‘Approved’ status so hardcoded
(e.g. approved, closed, as 'A' at Source
etc.).
9 FREIGHT_CODE A code indicating the VARCHAR2 1 Hardcoded as 'N' at destination
freight status of the
transfer (e.g. normal,
expedite, etc.).
10 ROUTING_CODE If the freight status is VARCHAR2 1 Hardcoded as 'NULL'
expedite, this is a code
indicating more
detailed freight info.
11 CREATE_DATE Transfer Creation Date DATE Hardcoded as today's Vdate
12 CREATE_ID User who created the VARCHAR2 30 Hardcoded as current logged in
transfer User
13 APPROVAL_DATE Transfer Approval DATE Hardcoded as today's Vdate
Date
14 APPROVAL_ID User who approved the VARCHAR2 30 Hardcoded as current logged in
transfer User


15 DELIVERY_DATE The earliest date the DATE N/A

transfer can be
delivered.
16 CLOSE_DATE DATE NULL
17 EXT_REF_NO VARCHAR2 14 NULL
18 REPL_TSF_APPROVE VARCHAR2 1 Hardcoded as “N” at
_IND destination
19 COMMENT_DESC Comments associated VARCHAR2 300 NULL
with the transfer.
None.
XTSF DTL – RMS TSFDETAIL Mapping

RMS Subscriber Mapping Create Transfer Detail Contains Transfer detail line of items.
Schema File N/A
Source Table(s)/File(s) STORE_ORDER, STORE, Target Object Name TSFDETAIL Table
TSF_MFQUEUE,
COMMODITY_MAPPING,
NON_CONTENTS_ORDER,
STOCKING_POINT


Description Length
1 TSF_MFQUEUE TSF_NUMBER Order Number Number (10,0)


1 TSF_NO Number that uniquely Varchar2 (10,0) The transfer number from
identifies the transfer header row
2 TSF_SEQ_NO Transfer Line Item Number (8,0) Transfer line item number
Number under the current header row
3 ITEM The unique identifier of Number 25 N/A
the item being
transferred.
4 INV_STATUS A code indicating the Number (2,0) Hardcoded as NULL
inventory status for
this transfer detail;
valid values are found
on the inv_status_types
table


5 TSF_QTY The total quantity of Number (12,4) Non-pack SKUs·:

the item reserved for store_order.case_volume x
this transfer at the from commodity_mapping.pack_size·
location. non_contents_order.quantity x
Formal Pack SKUs:
6 FILL_QTY Fill Quantity Varchar2 (12,4) NULL
7 SHIP_QTY Shipped Quantity Number (12,4) NULL
8 RECEIVED_QTY Received Quantity Number (12,4) NULL
9 DISTRO_QTY Distributed Quantity Number (12,4) NULL
10 SELECTED_QTY Selected Quantity Number (12,4) NULL
11 CANCELLED_QTY Cancelled Quantity Varchar2 (12,4) NULL
12 SUPP_PACK_SIZE Supplier Pack Size Number (12,4) The AIP SKU-pack size is
mapped to the RMS Item and
Order Multiple.
13 TSF_PO_LINK_NO Transfer to PO Link Number (10,0) NULL
number
14 MBR_PROCESSED_IND Member Processed Number 1 NULL
Indicator
15 PUBLISH_IND Publishing Indicator Number 1 Hardcoded as “N”
None.

14
AIP to External System Interfaces
Overview
In addition to the RIB, as explained in chapter 11, AIP provides a second method of
communicating Purchase Order and Transfer information to an order procurement
system. It is text file based and can be used in place of the RIB for communicating
Purchase Orders and Transfers created and released in the overnight batch.
Note: This process does not currently support any action

taken by the user in the Order Management application.
This is the recommended method of integration when large volumes of Purchase Orders
and Transfers are expected to be executed each night.
purchase_order.dat.1
Text File Purchase Orders New Purchase Orders
Program Type RETL
Program Name ord_exp_po_out.sh
Schema File ord_exp_po.xml
AIP to External System Interfaces 273

purchase_order.dat.1
Data Origin System AIP Target Object Type Delimited Text File
Source Object Type Delimited Text File Target Object Name purchase_order_.dat.1
Source Object Name PO_MFQUEUE, Target Object Database N/A
STORE_ORDER,
NON_CONTENTS_ORDER,
SUPPLIER,
STOCKING_POINT, STORE,
COMMODITY,
COMMODITY_MAPPING
Intersection
Field Delimiter |
Final Delimiter 0x0A
# Source Fields Source Field Description Field Start Maximum

Position Field Length
1 PO_MFQUEUE.order_number Order Number 1 10

2 SUPPLIER.supplier_code Unique Supplier Identifier N/A 20
3 MIN(STORE_ORDER. Delivery Date N/A N/A
DELIVERY_DATE),
MIN(NON_CONTENTS
_ORDER.DELIVERY_DATE)
4 MAX(STORE_ORDER. Delivery Date N/A N/A
DELIVERY_DATE)
MAX(NON_CONTENTS
5 PO_MFQUEUE.STATUS Order Status N/A 1
6 N/A S for Store destination, or W for N/A 1
Warehouse destination
7 STORE.store_code, Unique Identifier for Store or N/A 20
STOCKING_POINT.stocking Warehouse destination.
_point_number
8 COMMODITY_MAPPING.rms_ Unique SKU identifier N/A 25
sku_number
9 COMMODITY_MAPPING.pack_size, Case Quantity N/A N/A
STORE_ORDER.case_volume,
NON_CONTENTS_ORDER.quantity,
10 COMMODITY_MAPPING.rms_ Pack Size N/A N/A
order_multiple

transfer_order.dat.1
Target Data Field Name Target Field Field Data Condition/Format

Description Type
1 ORDER_NO Unique Order Identifier String 10000|

2 NOT_BEFORE_DATE Earliest Expected Date 20080128|
Delivery Date:
YYYYMMDD
3 NOT_AFTER_DATE Latest Expected Delivery Date 20080128|
Date: YYYYMMDD
4 STATUS Order Status String A|
5 LOCATION_TYPE Destination Location String S| or W|
Type—S for Store, W for
Warehouse
6 LOCATION Unique Identifier for the String 2000|
Destination with any
AIP prefixes removed.
7 ITEM Unique Identifier of the String 4000000|
Product to be Ordered
8 QTY_ORDERED Order Quantity in Decimal 30|
Eaches
9 SUPP_PACK_SIZE Pack Size Integer 6|
All prefixes added by AIP are removed.
Example of purchase_order.dat.1 Extract File Format:

10000|20080128|20080128|A|S|2000|4000000|30|60x0A
Text File Transfers New Transfers

Program Type RETL
Program Name ord_exp_tsf_out.sh
Schema File ord_exp_tsf.xml
Data Origin System AIP Target Object Type Delimited Text File
Source Object Type Delimited Text File Target Object Name transfer_order_.dat.1
Source Object Name PO_MFQUEUE, Target Object Database N/A
STORE_ORDER,
NON_CONTENTS_ORDER,
STOCKING_POINT,
STORE, COMMODITY,
COMMODITY_MAPPING
Intersection
Field Delimiter | Field Delimiter |
Final Delimiter 0x0A Final Delimiter 0x0A

1 TSF_MFQUEUE.tsf_number Transfer Number 1 10

2 STOCKING_POINT.stocking_point Unique source Warehouse N/A 20
_number Identifier
3 N/A S for Store destination, or W for N/A 1
Warehouse destination
4 STORE.store_code, Unique Identifier for Store or N/A 20
STOCKING_POINT.stocking Warehouse destination
_point_number
5 MIN(STORE_ORDER. Delivery Date N/A N/A
DELIVERY_DATE),
MIN(NON_CONTENTS
6 N/A Routing Code not available in N/A 1
AIP


7 N/A Freight Code not specified in AIP N/A 1
8 COMMODITY_MAPPING.rms_ Unique SKU identifier N/A 25

sku_number
9 COMMODITY_MAPPING.pack_size, Case Quantity N/A N/A
STORE_ORDER.case_volume,
NON_CONTENTS_ORDER.quantity,
10 COMMODITY_MAPPING.rms_ Pack Size N/A N/A
order_multiple
Target Data Field Name Target Field Description Field Data Type Condition/Format
1 TSF_NO Unique Transfer Identifier String 10000|

2 FROM_LOC Unique Warehouse identifier with Integer 1000|
any AIP prefixes removed.
3 TO_LOC_TYPE Destination Location Type—S for String S| or W|
Store, W for Warehouse
4 TO_LOC Unique identifier for the Store or String 2000|
Warehouse destination with any
AIP prefixes removed.
5 DELIVERY_DATE Expected Delivery Date: Date 20080128|
YYYYMMDD
6 ROUTING_CODE An optional Routing Code String |
7 FREIGHT_CODE An optional Freight Code String |
8 ITEM Unique Identifier of the Product to String 4000000|
be Ordered
9 TSF_QTY Transfer Quantity in Eaches Decimal 30|
10 SUPP_PACK_SIZE Pack Size Integer 6|
All prefixes added by AIP are removed.
Example of transfer_order.dat.1 Extract File Format:

10000|1000|S|2000|20080128|||4000000|30|60x0A

15
AIP to RO Interfaces
STR_AIP_DATA
Measure Lead Time Contains the number of days the source takes to
deliver the item once the order is released from AIP.
Lead time, is an integer for a SKU/store.
Measure Review Time Review time is the number of days until the next
receipt becomes available. This field contains the
longest review time found within a certain time
period. Review time is an integer for a SKU/store.
Measure Pack Size Contains the preferred ordering pack size when
ordering the SKU to the store.
Program Name aip_export_to_ro.sh
Schema Files N/A
Data Origin System AIP Target Object Type Fixed Length Text File or
File
Source Object Type RPAS measures Target Object Names STR_AIP_DATA.[txt csv]
Source Object Name sr0_lt, sr0_rt, sr0_ordpkz Target Object Load str_item
Intersection
Required/Optional Optional
AIP to RO Interfaces 279

STR_AIP_DATA

Position Width
STR_ Unique store identifier 1 20

SKU_ Unique SKU identifier 21 20
sr0_lt Lead Time 41 10
sr0_rt Review Time 51 10
sr0_ordpkz Store Ordering Pack Size 61 10
Data Type
STR_ Unique store identifier. String “1001 ”
ITEM Unique item identifier String “123456 ”
gleadtime_ GLEADTIME_ Real “3.0000 ”
greview_time_ GREVIEW_TIME_ Real “14.0000 ”
gpacksize GPACKSIZE_ Real “24.0000 ”
None.
Example of STR_AIP_DATA.txt File:

“1001 123456 3.0000 14.0000 24.0000 “
Example of STR_AIP_DATA.csv File:

“1001,123456,3.0000,14.0000,24.0000”

WH_AIP_DATA
WH_AIP_DATA
AIP can be configured to export warehouse supply-chain information. However, few
optimization systems can optimize warehouse replenishment. Check the Oracle Retail
Replenishment Optimization guides and the retailer’s specific implementation to determine
if warehouses can be optimized.
Measure Lead Time Contains the number of days the source takes to deliver the item once the
order is released from AIP. Lead time, is an integer for a SKU/warehouse.
Measure Review Time Review time is the number of days until the next receipt becomes
available. This field contains the longest review time found within a
certain time period. Review time is an integer for a SKU/warehouse.
Measure Pack Size Contains the preferred ordering pack size when ordering the SKU to the
warehouse.
Program Name aip_export_to_ro.sh
Schema Files N/A
Data Origin System AIP Target Object Type Fixed Length Text File or
File
Source Object Type RPAS Measures Target Object Names WH_AIP_DATA.[txt|csv]
Source Object Name IpWhLtO, IpWhRtO, Target Object Load WH__SKU_
IpWhOrdPkzO Intersection
Required/Optional Optional

Position Width
WH__ Unique warehouse identifier. 1 20

SKU_ Unique SKU identifier 21 20
IpWhLtO Lead Time 41 10

WH_AIP_DATA

Position Width
IpWhRtO Review Time 51 10

IpWhOrdPkzO Warehouse Ordering Pack Size 61 10
Data Type
WH Unique warehouse identifier. String “1001 ”
ITEM Unique item identifier. String “123456 ”
Lead time Lead Time Real “21.0000 ”
Review time Review Time Real “14.0000 ”
WH Pack Size WH Ordering Pack Size Real “48.0000 ”
None.
Example of WH_AIP_DATA.txt File:

“1001 123456 21.0000 14.0000 48.0000 “
Example of WH_AIP_DATA.csv File:

“1001,123456,21.0000,14.0000,48.0000”

16
First Day of AIP
Introduction
The phrase “First Day of AIP” encompasses the steps required to initially load the
Enterprise and Merchandise data into AIP for setup of the supply-chain, and
replenishment parameter definition. The term ‘day’ in this phrase does not necessarily
correspond to a single calendar day. The ‘First Day’ process, as defined by this
document, and required for the use of AIP, executes the minimal set of steps required to
populate an empty database while leveraging the automated supply-chain set up logic.
While this process populates an empty database it is not a ‘conversion’ process that so
often occurs when transitioning off of legacy systems. AIP works in tandem with the
merchandising system and the execution of this process will build out the database with
the initial Enterprise and Merchandise data. This specific process is only executed for the
very initial load of the database however maintenance of the Enterprise and Merchandise
hierarchy is a constant, ongoing task.
The goal of this process is to ready the database for automated supply-chain setup as
well as manual supply-chain setup and replenishment parameter definition. Its success is
pertinent to the ability to complete setup and therefore the system’s overall ability to
begin replenishment of items.
The following information and procedures are written with the assumption that all AIP
components have been properly installed and configured to interact appropriately. See
the Oracle Retail Advanced Inventory Planning Installation Guide for details. The necessary
environments must exist and be setup as indicated in the Oracle Retail Advanced Inventory
Planning Implementation Guide. Also, for more specific instructions and details around the
batch process, please reference the Oracle Retail Advanced Inventory Planning Operations
Guide.
Overview
The First Day of AIP is little more than the first iteration of the daily AIP batch cycle. It
virtually mirrors the cycle but executes only a subset of the daily processes. This
document will not only outline the actions to execute the First Day of AIP but will also
explain what the process is accomplishing and why. Understanding the goal of the First
Day, the reason it is different and how it executes will provide a deeper understanding of
the flow of data between AIP and external systems as well as between the two AIP
platforms—RPAS and Oracle.
Keeping in mind the goal and purpose of the First Day of AIP will provide the needed
insight to clearly understand how the required actions accomplish the goal.
The First Day of AIP Explained

The First Day of AIP has two very clear goals:
Load the database with Enterprise and Merchandise hierarchy data.
Enable automated data maintenance to run for the new data being loaded.
First Day of AIP 283

Load Data
On a day-to-day basis AIP is synchronized with both the external data coming from the
merchandising and forecasting systems and the internal data created on each platform.
This must occur on both AIP platforms—RPAS and Oracle. This occurs first in RPAS
prior to the replenishment planning calculations. All data required for the replenishment
planning calculations are loaded into AIP on the RPAS platform. This means that the
data is first extracted out of AIP on Oracle, the merchandising system, forecasting
system, etc. for loading into AIP on RPAS. In a daily batch run the RPAS database would
be synchronized with
Enterprise Hierarchy
Merchandise Hierarchy
Supply-chain Parameters
Inventory Positions
Forecasts
AIP Supply-chain
Following the data manipulation and replenishment planning on RPAS the plan,
hierarchies, and other modified supply chain data is extracted and/or passed from RPAS
to the Oracle database. The Oracle database is then synchronized with the latest data
passed to, or created by, AIP on RPAS. In a daily batch run the Oracle database would be
synchronized with
Enterprise Hierarchy
Merchandise Hierarchy
Supply Chain Parameters
AIP Supply-chain
Supply-chain Alerts
Replenishment Plan
Order Information (received quantities, closed orders, etc.)
The First Day attempts to follow the same process as the daily batch however only some
of the physical supply-chain elements exist, not the complete supply-chain
representation. Therefore the first day batch processes must be limited to merely loading
the data and setting up the logical connections and replenishment parameters without
doing any replenishment planning.
Impact to AIP on RPAS

Since AIP on RPAS is the first part of the AIP application to be synchronized, up to the
point of loading the data both the RPAS and Oracle databases are empty with the
exception of a minor amount of seed data.
Where normally there would be data to load from the Oracle database there is none.
All logic related to retrieving and loading data from AIP on Oracle will be skipped
since there is virtually no data.
Since the supply-chain is not yet defined in Data Management Online (AIP on
Oracle) replenishment will not be run. No replenishment plan is produced.
Consequently, because replenishment will not be run, all logic related to retrieving
and loading the inventory positions and forecasts will not be executed.
A portion of the automated data maintenance is executed on RPAS. The processes
that are triggered by—or identify—new hierarchy elements are executed. The
processes that operate on the premise of maintaining existing supply chain data are
not executed.

Impact to AIP on Oracle

AIP on Oracle is loaded after AIP on RPAS. The first day load process is quite similar to
the daily load process but should account for the fact that the replenishment plan does
not exist nor do any past AIP Orders.
No received quantities, closed orders, or recycled order numbers are available
because no purchase orders or transfers have been executed from AIP.
No replenishment plan exists to import from AIP on RPAS. Therefore all logic related
to retrieving and loading data from AIP on RPAS will be skipped.
A subset of data setup alerts will be loaded. These alerts pertain to data that is
available or created on the first day of AIP.
Note that the export logic is not executed to extract data out of the Oracle database before
the first AIP on RPAS load.
Enable Automated Data Maintenance

Automated Data Maintenance constitutes a significant portion of the AIP batch processes
that occur on the Oracle platform. It is comprised of a number of processes that not only
select default values but also setup a significant portion of the supply chain for new
entities—such as suppliers, locations, or items.
The magnitude of these operations—both in terms of saved user effort and the
importance of automation—is evident in the diagram below, which provides a detailed
outline of the AIP supply chain structure.

Supplier SKU-pack Link

Demand Group
Ranged Source Warehouse
Ranged Destination Warehouse SKU Pack Size
On Supply SKU Pack Size
Not Created by Automated Data SKU Pack Size
Maintenance
Shaded boxes are physical entities not
mastered in AIP.
Unshaded boxes are logical entities
Supplier
Order Group Delivery Group Order Group Source
Order Cycle Demand Group Order Cycle

Demand Source
Demand Group Demand Group Group
Demand Group Split %
Demand Group Demand Group
Destination
Warehouse Warehouse
Warehouse
Chamber Chamber
Chamber
Source
Source
Delivery Group Order Group
Demand Group Order Cycle

Demand Source
Demand Group Group Split %
Demand Group
Demand Group
Destination
Warehouse
Warehouse
Chamber
Chamber
Source
Profile Profile Profile
Store SKU Order Cycle Order Cycle Order Cycle
Source SKU
Store
Source
SKU SKU SKU
Destination SKU SKU SKU Destination

Store Store
Store Store Store
AIP Supply Chain Structure Diagram

The First Day of AIP Execution
The AIP supply chain structure diagram lists the physical as well as logical entities of the
supply chain which must be defined within AIP. If configured correctly, all logical
entities can be created by the Automated Data Maintenance processes with the exception
of those noted in the diagram, and the Supplier SKU pack size links.
The diagram provides an easy-to-discern list of needed supply chain elements. For
example, by examining this diagram from top to bottom, it can be seen that:
A source must be connected to a Delivery Group and Order Group for delivery into
warehouses and a Profile for delivery into the store.
The Order Group must be associated with an Order Cycle.
Demand Groups must be associated with an Order Group and Delivery Group for
deliveries from a source to a warehouse-chamber destination.
Demand Groups must be created for SKU-pack sizes.
etc.
The diagram illustrates what the First Day of AIP needs to accomplish on the Oracle
platform. By fully comprehending each element of the diagram it becomes clear why the
first day process should be different for AIP on Oracle and how to maximize the effect of
automation while minimizing the amount of extra effort required to enable it.
The full analysis of each element of the diagram is out of the scope of this document
however the elements that impact the first day will be examined.
Order Cycles are required to create Order Groups and Profiles. Order Cycles are not
created by Automated Data Maintenance, however default Order Cycles are
provided as seed data loaded before the Fist Day.
Warehouse chambers are required to create Order Groups, Delivery Groups, and
ranged warehouse/SKU-pack sizes. Chambers are not created by Automated Data
Maintenance since there is not a single rule-set that will work for all businesses. It is
maintained as a manual process. Automated Data Maintenance could do very little
setup the first day if the First Day process was not altered to accommodate for this
fact.
The First Day of AIP Execution

Prior to executing the steps listed below ensure that all installations and configurations
are set according to the AIP Installation Guide, RPAS Installation Guide, and AIP
Implementation Guide.
The detailed First Day processes that will be executed for AIP on RPAS can be found in
the AIP Operations Guide.
The First Day execution steps are quite similar to the daily steps however because it is
typically when the most new data is introduced the execution time will likely extend
beyond a normal batch window.
The First Day of AIP consists of the following main steps:
1. Virtual Date (Vdate)
Sets and synchronizes the virtual/notional date across AIP on Oracle and AIP on
RPAS.
2. Build the SRP Implementation Parameters Workbook
Customizes implementation parameters required for AIP RPAS batch logic and
calculations.
3. First Day of AIP on RPAS Batch
Loads RMS hierarchies into AIP RPAS domain

Step 1: Virtual Date (Vdate)
Calculates new hierarchy element alerts

Creates specific hierarchy attributes
Calculates certain supply chain logical concepts for Online
4. First Day of AIP on Oracle Import
Imports hierarchies into AIP on Oracle
Full import of all AIP on RPAS exports
Automation creates a significant portion of the logical supply chain structure
5. First Day of AIP on Oracle Manual Setup
Creation of Warehouse Chambers and assignment of SKU types
6. First Day of AIP on Oracle Automation
Executes the entire set of Automated Data Maintenance processes to
automatically setup the supply chain.
7. First Day of AIP on Oracle Import of Non-critical Alerts
Imports the non-critical Data Management alerts from AIP RPAS.
8. Complete all manual setup of AIP
Set AIP on RPAS replenishment defaults and exceptions
Set or modify Data Management Online supply chain parameters, defaults, and
exceptions.
Step 1: Virtual Date (Vdate)

Step Details
As this is the first time AIP Batch will be run, the Vdate must be set so both AIP on
Oracle and AIP on RPAS are in sync. The intention of Vdate is to ensure that the nightly
batch processing occurs for a single calendar day and does not need to account for the
system date changing calendar days as the clock reaches midnight. Under normal
circumstances the Vdate will match SYSDATE when the batch is complete. For the
purposes of exporting the data generated by the Automated Data Maintenance processes
it is important to set the Vdate to a date that is equal to or greater than the date when all
the First Day activities will be completed.
For example, if it is expected that the automation and manual setup will take 2 days to
st
complete for the First Day setup and today is April 1 , 2007, then Vdate should be set to
20070403. This will then allow the Vdate to be set to 20070404 when the first full end-to-
end AIP Batch is run.
Step Execution
Run vdate.sh script to set the Vdate in the AIP Oracle database and export the value to a
flat file.
/aip/oracle> vdate.sh set export 20070101
Copy the flat file vdate.int from ${INTEGRATION_HOME}/vdate to
${AIPDOMAIN}/interface/import/meas.

Step 2: Build the SRP Implementation Parameters Workbook
Step 2: Build the SRP Implementation Parameters Workbook

Step Details
Before running the AIP RPAS batch steps using aip_batch.sh script as detailed in the
following steps, one RPAS workbook must be built and values in the workbook changed
as desired. There are RPAS batch steps that depend on the values which can be
customized in this workbook.
Most importantly, the RPAS measure “Inventory Tracking Level” (sr0_invtrklvl) is
queried by batch steps “check_process_external_data” and
“check_process_inventory_data” in order to choose between logic based on packs or
eaches processing mode. Therefore the appropriate level must be determined before AIP
RPAS batch is executed.
Step Execution
Log in to the SRP workbook. Refer to the Oracle Retail Store Replenishment Planning User
Guide for details on building and modifying the values in this workbook.
Step 3: First Day of AIP on RPAS Batch

Step Details
The goal of the First Day of AIP RPAS batch processing is to load all hierarchy elements
into the AIP RPAS domain and perform various supply chain setup activities. This step
consists of a subset of the daily AIP RPAS batch script steps. Refer to the AIP Operations
Guide for a detailed list of the steps. The output of these processes is put into flat files to
pass to AIP on Oracle. The flat files are loaded into the Oracle database in the next step.
Below are the details of this output.
Hierarchy Files
Product hierarchy prod.dat
Profile hierarchy prof.dat
Store hierarchy loc.dat
Supplier hierarchy hspl.dat
Warehouse hierarchy whse.dat
Hierarchy Alerts
New SKU Alert dmx_newprd.dat
New SKU Packsize Alert dmx_newpsz.dat
New Store Alert dm0_new.dat
New Supplier Alert dm0_newspl.dat
New Warehouse Alert dm1_new.dat

Step 3: First Day of AIP on RPAS Batch
Attributes
Default Warehouse info for Stores default_wh.dat
Direct-supply flag dmx_dirspl.dat
SKU Packsize Pack-type dmx_pcktyp.dat
SKU Packsize Attribute item_attribute_type.dat
SKU Packsize Attribute Value item_attribute.dat
Supplier Ship-to info dmx_shpto_.dat
Warehouse Type info wh_type.dat
Warehouse Promotional Start Date dm0_pmsstasrc.dat
Warehouse Promotional End Date dm0_pmsendsrc.dat
RMS to AIP SKU Map dmx_rmsskumap.dat
Supply Chain Logical Links

Home Warehouse dm1_prfhme.dat
Product-Profile Links dmx_prdprflks.dat
Product-Supplier Links dmx_prdspllks.dat
Profile Default Order Cycle dmx_prfdefocy.dat
Profile Links dm1_prflks.dat
Off-sale dm0_ofseffdt_.dat
On-sale dm0_onseffdt_.dat
Store Source dm0_src_i.dat
Step Execution
The aip_batch.sh control script has a –f flag that automatically runs all necessary steps (or
the start and end flags can be used as well):
/aip/rpas> aip_batch.sh –f
- OR -
/aip/rpas> aip_batch.sh –f –s set_implementation_parameters\ –e auto_build_wkbooks_batch

Step 4: First Day of AIP on Oracle Import
Step 4: First Day of AIP on Oracle Import

Step Details
The First Day of AIP on Oracle import is merely a subset of the complete import that is
executed on a daily basis. In addition, there is a pause between the execution of the
import and the automation tasks that occur afterward. The pause is required to allow the
next step, Step 5, to occur.
Below is a list of the files imported in the First Day import.
Hierarchy Import
Description File name Import Directory
Product hierarchy prod.dat sku_pack

SKU Packsize Pack-type dmx_pcktyp.dat sku_pack
SKU Packsize Attribute item_attribute_value.dat sku_pack
SKU Packsize Attribute Value item_attribute.dat sku_pack
Profile hierarchy prof.dat profile
Store hierarchy loc.dat store
Default Warehouse for Stores default_wh.dat store
Supplier hierarchy hspl.dat supplier
Supplier Ship-to info dmx_shpto_.dat supplier
Warehouse hierarchy whse.dat warehouse
Warehouse Type info wh_type.dat warehouse
Data Management Import
New Product Alert dmx_newprd.dat alerts

New Packsize Alert dmx_newpsz.dat alerts
New Store Alert dm0_new.dat alerts
New Supplier Alert dm0_newspl.dat alerts
New Warehouse Alert dm1_new.dat alerts
Direct-supply flag dmx_dirspl.dat direct_suppliers
Direct-to-Store Format Ordering Pack direct_store_format_pack_size.dat direct_store_format_pack_size
Size
Direct-to-Store Ordering Pack Size direct_store_pack_size.dat direct_store_pack_size
Off-sale dm0_ofseffdt_.dat on_supply_off_supply
On-sale dm0_onseffdt_.dat on_supply_off_supply
WH-to-Store Format Ordering Pack Size store_format_pack_size.dat store_format_pack_size
WH-to-Store Ordering Pack Size store_pack_size.dat store_pack_size

Step 5: First Day of AIP on Oracle Manual Setup
Store Source dm0_src_i.dat store_source

Home Warehouse dm1_prfhme.dat home_warehouse
Product-Profile Links dmx_prdprflks.dat assigned_commodity
Product-Supplier Links dmx_prdspllks.dat commodity_supplier_links
Profile Order Cycle dmx_prfdefocy.dat profile_order_cycle
Profile Links dm1_prflks.dat valid_warehouse
RMS to AIP SKU Map dmx_rmsskumap.dat sku_map
Warehouse Promotional Start Date dm0_pmsstasrc.dat warehouse_promotional_dates
Warehouse Promotional End Date dm0_pmsendsrc.dat warehouse_promotional_dates
Step Execution
Perform the following procedure.
1. Set the environment variables for the session.
/aip/oracle> . aip_common_online.sh
2. Prepare the flat files in the import directory
/aip/oracle> ${INTEGRATION_HOME}/scripts/prep_files.sh DM_data AIP-ONLINE
3. Verify the success of the operation by checking the log files for errors and checking
the return value of the last operation.
/aip/oracle> echo $?
4. Import the hierarchy values and attributes.
/aip/oracle> ${INTEGRATION_HOME}/scripts/process_aiponline_data.sh -l
"${INTEGRATION_HOME}/config/import_hierarchy.config"
6. Import the measure data.
"${INTEGRATION_HOME}/config/import_dm.config"
Step 5: First Day of AIP on Oracle Manual Setup

Step Details
In order to achieve the maximum benefit from Automated Data Maintenance the user is
required to create warehouse chambers and assign SKU-types to them. These actions
occur in the Data Management Online application. Refer to the Oracle Retail Data
Management Online User Guide or the online Help for details on creating chambers and
assigning one or more SKU types.

Step 6: First Day of AIP on Oracle Automation
Step Execution
Log in to Data Management Online. Follow the steps to create one or more chambers for
each warehouse. Follow the steps to assign one or more SKU types to each chamber.
Step 6: First Day of AIP on Oracle Automation

Step Details
When configured and executed, Automated Data Maintenance will setup the supply-
chain for new Suppliers, new SKU-pack sizes, sister warehouses, and sister stores. The
first day this pertains to all suppliers and SKU-pack sizes because all data is new to AIP.
None of the ‘maintenance’ activities will have an effect because all data is new and
therefore no invalid relationships exist. Refer to the Oracle Retail Advanced Inventory
Planning Operations Guide for a detailed explanation of the processes executed to setup
and maintain the supply-chain.
Note that sister store and sister warehouse automation do nothing the first day.
Step Execution
Perform the following procedure to execute the process.
1. Execute the automation control script.
/aip/oracle> ${INTEGRATION_HOME}/scripts/post_import_wrapper.sh
2. Verify the success of the operation by checking the log files and the return value of
the last operation.
Step 7: First Day of AIP on Oracle Import of Non-critical Alerts

Step Details
The non-critical alerts are informative alerts that identify potential holes in the supply
chain. During batch runs subsequent to the First Day these alerts may trigger automated
maintenance of certain data in addition to an informative alert visible to the user in Data
Management Online.
Step Execution
Perform the following procedure to execute the process.
1. Prepare the flat files in the import directory.
/aip/oracle> ${INTEGRATION_HOME}/scripts/prep_files.sh DM_alerts AIP-ONLINE
3. Import the hierarchy values and attributes.
"${INTEGRATION_HOME}/config/import_dm_alerts.config"
the return value of the last operation. Note that you will likely see warning messages
indicating that some files do not exist. This is expected on the first day.

Step 8: Manual Setup of AIP
Step 8: Manual Setup of AIP

Step Details
Although the Automated Data Maintenance logic creates the majority of the supply chain
representation AIP has various other attributes and exceptions that, if they are to be
leveraged, must be manually created. The user can also choose to modify the supply
chain created by automation.
The Data Management Online attributes and exceptions that are not created by
automation include:
Planning Groups
Network Groups
Planning Horizons (Global default is set at implementation time)
Singles Enabled SKU
Store Order Cycle Exceptions
Non-release Dates and Exceptions
Non-receipt Dates
Store Receiving Calendar*
Direct/Warehouse to Store Pack Size Exceptions (can be loaded)
Warehouse Coupled Flag
Stockless Indicator Exceptions
Receipt to Availability Lead Time
Shifts and Slots*
Receiving Windows
Time Balanced Order Source Splits (partially created by automation)*
Supplier Locks
Non Order Dates and Exceptions
Non Delivery Dates and Exceptions
*Required for replenishment
AIP on RPAS replenishment parameters must be set prior to executing the first full AIP
batch run in order for a plan to be generated. The parameters define replenishment
methods, tolerances, and other attributes required for generating planned orders.
Note that this setup can occur at any point after Step 3, but must be completed prior to
executing a full batch cycle which includes replenishment planning.
Step Execution
Log in to the Data Management Online application. Refer to the Oracle Retail Advanced
Inventory Planning Data Management User Guide for a detailed description of how to
perform each action.
Log in to the SRP and WRP workbooks. Refer to the Oracle Retail Advanced Inventory
Planning Store Replenishment Planning User Guide and Oracle Retail Advanced Inventory
Planning Warehouse Replenishment Planning User Guide for details on building workbooks
and modifying the Administration Workbooks.

Aip 1312 Impg

Uploaded by

Copyright:

Available Formats

Aip 1312 Impg

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aip 1312 Impg

Uploaded by

Copyright:

Available Formats

Oracle® Retail Advanced Inventory Planning

Copyright © 2010, Oracle. All rights reserved.

Oracle Retail VAR Applications

Note: Before sending us your comments, you might like to

Send your comments to us using the electronic mail address: retail-doc_us@oracle.com

Review Patch Documentation

Oracle Retail Documentation on the Oracle Technology Network

Note: AIP Java/Oracle, AIP on Oracle, and AIP online are

Note: A user must have access to the workbook template in

4 Oracle Retail Advanced Inventory Planning

Note: Keep in mind that the “Warehouse Type” helps define

6 Oracle Retail Advanced Inventory Planning

Base Paths for Solution Screen

Building a Production AIP RPAS Domain 7

$AIP_INSTALL/configuration/AIP AIP base XML files generated by and which

Hierarchy Data Overview

Hierarchy Data File Description

bcsk.dat Baseline/Contingency Stock

8 Oracle Retail Advanced Inventory Planning

Message Strings File Description

msgs.dat.aip Message hierarchy Positions

Production AIP RPAS Domain Build Overview

 Move the RPAS Domain (Optional)

Manipulate the Hierarchy Data, Part One

10 Oracle Retail Advanced Inventory Planning

Note: The hdgr (Delivery Group hierarchy), oltc (Order

Run the AIP RPAS Installer

Configuring the AIP Solution

Note: This section requires that the RPAS Configuration

Note: This release of the AIP RPAS configuration is enabled

12 Oracle Retail Advanced Inventory Planning

Insert External System Data into the AIP RPAS Domain

Note: The goal of this preparation step is to provide files

Generate Load-Ready AIP Hierarchy Data

Note: During the RPAS Installer execution, you were

14 Oracle Retail Advanced Inventory Planning

Create the AIP RPAS Global Domain Configuration XML File

Tip: Each sub-domain (i.e. local domain) must contain at

Tip: If the globaldomainconfig.xml file refers to domain

Note: Before invoking the utility (described below) to create

Manipulate the Hierarchy Data, Part Two

16 Oracle Retail Advanced Inventory Planning

Note: The aip.tar.zip file does not have to be repackaged in

Build the AIP RPAS Global Domain

Option Option Description Argument Value

-d Domain source $AIP_INSTALL/domain_build

Example execution command:

Note: When viewing or searching through the build log,

AIP RPAS Domain Build Completion Summary

Customer Data Hierarchies:

18 Oracle Retail Advanced Inventory Planning

Default / Sample Hierarchies:

Note: The empty hierarchies will be populated during a full

Move the RPAS Domain (Optional)

Note: Previous versions of AIP contained an updateGlobalPointers

Configure the RPAS Client to Use the Domain

Post Installation Instructions

20 Oracle Retail Advanced Inventory Planning

Configuring AIP RPAS Environment Variables

Move the RPAS Domain (Optional)