Oracle Retail Merchandising System 10.1.13 Operations Guide Addendum

120 Pages·2005·0.49 MB·English

®
Oracle Retail Merchandising
™
System
10.1.13
Operations Guide Addendum

The software described in this documentation is furnished
Corporate Headquarters:
under a license agreement, is the confidential information of
Oracle
Oracle Retail Inc., and may be used only in accordance with
950 Nicollet Mall
the terms of the agreement.
Minneapolis, MN 55403
No part of this documentation may be reproduced or
USA
transmitted in any form or by any means without the express
888.61.RETEK (toll free US)
written permission of Oracle Customer Support, 950 Nicollet
Switchboard:
Mall, Minneapolis, MN 55403, and the copyright notice may
[phone]
not be removed without the consent of Oracle.
Fax:
Information in this documentation is subject to change
[phone]
without notice.

Oracle Retail provides product documentation in a read-only-
European Headquarters: format to ensure content integrity. Oracle Customer Support
cannot support documentation that has been changed without
Oracle
Oracle authorization.
110 Wigmore Street
The functionality described herein applies to this version, as
London
reflected on the title page of this document, and to no other
W1U 3RW
versions of software, including without limitation subsequent
United Kingdom
releases of the same software component. The functionality
Switchboard:
described herein will change from time to time with the
[phone]
release of new versions of software and Oracle reserves the
Sales Enquiries: right to make such modifications at its absolute discretion.
[phone] Oracle Retail ® Merchandising SystemTM is a trademark of
Fax: Oracle.
[phone]
Oracle and the Oracle logo are registered trademarks of
Oracle.
This unpublished work is protected by confidentiality
agreement, and by trade secret, copyright, and other laws. In
the event of publication, the following notice shall apply:
©2005 Oracle. All rights reserved.
All other product names mentioned are trademarks or
registered trademarks of their respective owners and should
be treated as such.
Printed in the United States of America.
Oracle Retail Merchandising System

Customer Support
Customer Support hours
Customer Support is available 7x24x365 via email, phone, and Web access.
Depending on the Support option chosen by a particular client (Standard, Plus, or Premium), the
times that certain services are delivered may be restricted. Severity 1 (Critical) issues are
addressed on a 7x24 basis and receive continuous attention until resolved, for all clients on active
maintenance. Oracle customers on active maintenance agreements may contact a global Customer
Support representative in accordance with contract terms in one of the following ways.
Contact Method Contact Information
E-mail [e-mail]
Internet (ROCS) rocs.retek.com
Oracle Retail’s secure client Web site to update and view issues
Phone [phone]
Toll free alternatives are also available in various regions of the world:
Australia [phone] (AU-Telstra) or [phone] (AU-Optus)
France 0800 90 91 66
Hong Kong 800 96 4262
Korea 00 308 13 1342
United Kingdom 0800 917 2863
United States +1 800 61 RETEK or 800 617 3835
Mail Oracle Customer Support
950 Nicollet Mall
Minneapolis, MN 55403
When contacting Customer Support, please provide:
• Product version and program/module name.
• Functional and technical description of the problem (include business impact).
• Detailed step-by-step instructions to recreate.
• Exact error message received.
• Screen shots of each step you take.
Contents

Contents
Chapter 1 – Introduction..................................................................1
Overview.......................................................................................................................1
Chapter 2 – RMS – Oracle RPAS for Demand Forecasting
interface RETL batch........................................................................3
Oracle Retail ETL architecture.....................................................................................3
RETL program overview..............................................................................................4
Configuration.....................................................................................................................5
Program return code......................................................................................................8
Program status control files..........................................................................................8
File naming conventions....................................................................................................8
Restart and recovery...........................................................................................................8
Message logging...........................................................................................................9
Daily log file.......................................................................................................................9
Format..............................................................................................................................10
Program error file.............................................................................................................10
RMSE reject files........................................................................................................10
Schema files overview................................................................................................11
Command line parameters..........................................................................................11
rmse_config.env...............................................................................................................11
RMSE I/O file names.......................................................................................................14
Enhancements and assumptions related to the interface.............................................15
Typical run and debugging situations.........................................................................17
Programs packaged for RMS-RPAS 11.1 integration......................................................19
Program flow diagrams...............................................................................................21
RMS pre/post extract diagrams........................................................................................23
RMS foundation data extract diagrams............................................................................24
RMS fact data extract diagrams.......................................................................................26
RPAS-RDF fact transform diagrams................................................................................27
Naming conventions.........................................................................................................29
i
Oracle Retail Merchandising System

RETL extraction programs.........................................................................................29
Maintenance programs................................................................................................38
RETL programs that load into RMS...........................................................................38
Load batch scripts and data files......................................................................................38
rmsl_forecast.ksh..............................................................................................................38
Weekly forecasted demand layout....................................................................................38
Daily forecasted demand layout.......................................................................................39
Chapter 3 – EDI purchase order download [edidlord.pc] ...........41
Chapter 4 – Sales audit export to GL [saexpgl.pc].....................57
Chapter 5 – Sales audit export to RDW [saexprdw.pc]...............65
Chapter 6 – File layouts for interface between sales audit and
data warehouse. .............................................................................89

ii
Chapter 1 – Introduction

Chapter 1 – Introduction
Overview
This addendum to the Oracle Retail Merchandising System (RMS) 10 Operations Guide presents
changes that have resulted from work completed during RMS 10.1.13 development and customer
support.

1

Chapter 2 – RMS – Oracle RPAS for Demand Forecasting interface RETL batch

Chapter 2 – RMS – Oracle RPAS for
Demand Forecasting interface RETL
batch
Because RMS is the retailer’s central merchandising transactional processing system, the system
is the principle source of the foundation data needed in some of the Oracle Retail suite of
products. This chapter includes information regarding RETL programs related to the Oracle
Retail Merchandising System (RMS)-RPAS for the Demand Forecasting (RDF) interface.
Please note the RETL programs that have been enhanced are specifically for RMS 10.1 to RDF
11.1. The programs contained within this patch should only be used by retailers that want to
integrate RMS 10.1 with RDF 11.1.
Oracle Retail ETL architecture
RMS works in conjunction with the Oracle Retail Extract Transform and Load (RETL)
framework. This architecture utilizes a high performance data processing tool that allows
database batch processes to take advantage of parallel processing capabilities.
The RETL framework runs and parses through the valid operators composed in XML scripts.
More information about the RETL tool is available in the latest RETL Programmer’s Guide.
The diagram below illustrates the extraction processing architecture. Instead of managing the
change captures as they occur in the source system during the day, the process involves extracting
the current data from the source system. The extracted data is output to flat files. These flat files
are then available for consumption by products such as RPAS for Demand Forecasting.
The target system has its own way of completing the transformations and loading the necessary
data into its system, where it can be used for further processing in the environment. See RPAS for
Demand Forecasting documentation for information related to transformations and loadings.
The architecture relies upon two distinct stages, shown in the diagram below. Stage 1 is the
extraction from the RMS database using well-defined flows specific to the RMS database. The
resulting output is comprised of data files written in a well-defined schema file format. This stage
includes no destination specific code.
Stage 2 introduces a flow specific to the destination. In this case, flows for RPAS for Demand
Forecasting are designed to transform the data so that RPAS can import the data properly.
3
Oracle Retail Merchandising System

Stage 1
RMS extraction
RMS extraction
RMS DB flows and output
process
schemas
RMS extraction files
(in output schema format)
Stage 2
Transformation Transformation
process flows
Load files
Destination DB

The two stages of RETL processing
RETL program overview
This section summarizes the RETL program features utilized in the RMS extractions and loads..
Installation information about the RETL tool is available in the latest RETL Programmer’s Guide.
4