Modified 12-MAR-2010 Type WHITE PAPER Status PUBLISHED
In this Document
Abstract
Document History
Oracle Retail Business Process Documents for Implementing the Release 13.1.x Oracle Retail Merchandising Products
Assumptions
Related Documents
Usage
Design Notes
Overview
Key Definitions and Acronyms
Process Naming Standard and Numbering Conventions
Process Maps (Swim lane Diagram)
Process Design (Spreadsheet)
Centralized Configuration Document
Applies to:
Oracle Retail Merchandising System - Version: 13.1 to 13.1 - Release: 13 to 13
Information in this document applies to any platform.
Abstract
This document explains how to use the Merchandising business processes. The processes are written assuming that version 13.1 of the following Oracle Retail products will be installed:
Merchandising System - RMS
Invoice Matching - ReIM
Sales Audit - ReSA
Price Management - RPM
Trade Management - RTM
Allocation
Document History
Update Date 12-March-2010
Oracle Retail Business Process Documents for Implementing the Release 13.1.x Oracle Retail Merchandising Products
While the processes are developed with the previous product set in mind, they can be applied to any retailer who has purchased the Oracle Retail Merchandising products. There are four general audiences for whom these processes are written:
Retail clients who have purchased and are implementing the Oracle Retail Merchandising products
Integrators and implementers who are implementing the Merchandising products
Business analysts who want to understand how the Merchandising System can be applied as a business solution
System analysts and system operations personnel who need additional functional understanding of the Merchandising products
Assumptions
Any application not in the standard list above (for example, store systems, financial systems, warehouse systems) does not have a step-by-step explanation within the process. The processes focus on the list of products above. Any other product referred to should be considered a generic product.
These business processes are tailored to the Oracle Retail applications; however, they do not include detailed technical information such as interfaces or batch programs. Additionally, these documents should not be viewed as a substitute for product training.
Each retailer will still modify some of the processes to tailor them to their specific business needs.
Related Documents
For more information, see the following Oracle Retail documentation:
Oracle Retail Allocation User Guide
Oracle Retail Invoice Matching User Guide
Oracle Retail Merchandising System User Guide
Oracle Retail Price Management User Guide
Oracle Retail Sales Audit User Guide
Oracle Retail Trade Management User Guide
Usage
The business process designs are intended to support an implementation of the Merchandising products. These designs are a guide for both the business and implementation teams. They explain some scenarios and factors that need to be considered for a successful implementation. The designs are created for a generic retailer, with some considerations made for hardlines, apparel (softlines) and grocery. Because of this, retailers may find that they want to change the business processes to meet their unique needs, but the documents should provide a solid initial foundation.
Design Notes
Overview
The Oracle Retail business process designs are separated into six functional categories:
1.0 Manage Foundation Data
2.0 Manage Items
3.0 Manage Pricing
4.0 Manage Purchase Orders
5.0 Manage Inventory
6.0 Manage Finance
Each category is then broken down into more specific functional subcategories. Every process map and design falls into one of the subcategories. For example, category 1 is divided as follows:
1.0 Manage Foundation Data
1.1 Manage Merchandise Foundation
1.1.1 Manage Merchandise Hierarchy
1.1.1.1 Create Merchandising Hierarchy (business process designs required)
1.1.1.2 Maintain Merchandising Hierarchy (business process designs required)
1.1.2 Manage Reclassification
1.1.3 Manage Diffs
1.2 Manage Organization Foundation
1.3 Manage Other Foundation Data
For each subcategory for which business process designs are required, a process map and process design are delivered:
Process Map (swim lane diagram) - The process map is a visual representation of how the end user would carry out a specific business process. This process shows how data flows through the system, decisions that users will need to make, and activities that the user will have to carry out to complete a particular process.
Process Design (spreadsheet) - The process design covers the same process as the swim lane diagram, but it offers a detailed step-by-step instruction set for the user to complete the process. The spreadsheet also offers a comprehensive look at all the factors that go into successfully carrying out the process, including key system parameters and implementation considerations.
Key Definitions and Acronyms
BPD - Business process designs
WH - Warehouse
POS - Point of sale system
Process Naming Standard and Numbering Conventions
Process Map 1.2.3.4
1.2.3.4 = Process ID
Title numbering for the process maps is for categorizing purposes only, and is not to be interpreted as a sequential order of implementation.
Process Design 1.2.3.4
The activity shapes within a process map are numbered with the process ID, followed by sequential numbering, and correspond to the step-by-step directions used in the process design to list activity details. For example, 1.2.3.4.1 represents the first step in the process with the ID 1.2.3.4.
Process Maps (Swim lane Diagram)
For a detailed explanation of the symbols used, consult the Retail Business Process Modeling Symbols document.
Note: Roles documented in the process maps and process designs are subject to change, depending on the organizational structure of the retailer.
Process Design (Spreadsheet)
The process designs are a more detailed representation of the process maps. The process designs are detailed in five tabs:
Subprocess: The subprocess tab is an overview of the entire process, describing assumptions, functional areas and roles, user access, frequency of the process, key impacts for each role, benefits, benefit impacts, key performance indicators, and system availability requirements.
Activity and Task: The activity and task tab is a more detailed, step-by-step representation of the process maps. This tab identifies the system, screen name, and field name of each step the user needs to complete, and also calls out any Oracle Retail User Guide documentation available to support this process.
System Parameters: The system parameters tab details any system settings (typically from the system options, system variables, or unit options tables) and the suggested settings of these parameters to support the specific process.
Implementation Considerations: The implementation considerations tab highlights any key steps that may be need to be carried out before or during implementation of the system or process involved.
Issues: The issues tab is for retailers and implementers who might want to list any outstanding issues that apply to this process in their own unique environment.
Drop Down Lists: This tab contains the source of the lists used for the drop-down boxes within the other tabs of the spreadsheet.
Centralized Configuration Document
This document consolidates all the configuration requirements and the suggested settings by retail segments (hardlines, apparel [softlines], and grocery) in the Oracle Retail Merchandising System, Invoice Matching, Price Management, Allocation, Trade Management, and Sales Audit applications. The centralized configuration document includes the following tabs:
SE Configuration: This tab details the following for the configuration parameters that need to be defined and maintained in the Merchandising products, including the following:
System parameter settings - These are indicators set in the system parameter tables that enable certain functionalities within the products. Generally, these parameters are set during implementation and are not changed.
Codes - The code tables contain predefined lists that commonly appear in drop-down boxes and list-of-values fields in the products. The business can add additional values to the relevant code details based on the client specific business requirements; however, it is not recommended to remove any system-defined code detail values (especially those marked with "required"), unless there is a strong business reason behind the decision to do so. Code detail values may be referenced by various modules, and removing these values might have undesirable system impacts. Detailed analysis is recommended before removing the system-defined code detail values to ensure no system impact. It is also recommended that the original scripts for the code tables are not modified, so that the original values can always be referenced. Instead, new scripts can be created to update, add, or remove values from the original script to create the client-specific version. The code values that can be configured have been included in the centralized configuration document.
Configuration Master Data - Configuration data is more static in nature, and the frequency of the maintenance is very low (for example, inventory reason codes, price change reason codes)
Translations: This tab contains some additional configuration guidelines for retailers who want to use translated values in Merchandising products. This information can be used in conjunction with the detailed instructions available in the Operations Guide for each product.
VAT Reference: This tab illustrates how to set up VAT functionality in Oracle Retail Merchandising System.
Out of Scope Parameters: This tab includes all system parameters that affect functionalities that are not included in the Standard Edition scope (for example, contract, data warehouse).
Attachments
1Foundation.pdf (700.84 KB)
1ManageFoundation.zip (1,502.68 KB)
2ManageItems.pdf (478.3 KB)
2ManageItems.zip (979.42 KB)
3ManagePricingVendorCost.pdf (649.86 KB)
3ManagePricingVendorCost.zip (1,248.43 KB)
4ManagePOsAllocReplDealsRTM.pdf (705.77 KB)
4ManagePOsAllocReplDealsRTM.zip (1,690.88 KB)
5ManageInventoryRESA.pdf (834.78 KB)
5ManageInventorySalesAudit.zip (1,812.9 KB)
6FinancialCostAdStockLedgerInvoiceMatching.zip (769.21 KB)
6FinancialCostAdjStockLedgerREIM.pdf (326.53 KB)
Level1Categorization.zip (156.56 KB)
Level2ProcessDesigns.zip (602.98 KB)
MerchandiseSELevel2.pdf (197.04 KB)
RetailBusinessProcessModelingSymbols.pdf (60.1 KB)
SEBPDReadMeDocument.zip (45.66 KB)
SECentralizedConfiguration.zip (148.05 KB)
Related
Products
More Applications > Industry Solutions > Retail > Oracle Retail Merchandising System
Back to top
No comments:
Post a Comment