| Oracle® Retail Warehouse Management System Implementation Guide Release 15.0 E68108-01 |
|
 Previous |
 Next |
| Oracle® Retail Warehouse Management System Implementation Guide Release 15.0 E68108-01 |
|
Previous |
Next |
This chapter provides a high-level overview of the process required for a successful installation of the Oracle Retail Warehouse Management System (RWMS) application. For complete step-by-step installation details, see the Oracle Retail Warehouse Management System Installation Guide.
This chapter contains the following sections:
New Distribution Center (DC) Setup
When RWMS is installed it automatically creates a Facility ID of PR with a Destination ID of 01 as a default. The client can change this Destination ID in the Facility Setup Editor to their desired Facility Number. The Destination used must pre-exist in the Destination Editor/Table downloaded from the host system and it must be classified as Dest Type DC. You must also set the DC_dest_ID in the System Parameter Editor/Table to match this Facility Number. RWMS allows for multiple facilities to be created in the same instance. Clients create multiple facilities so they can have TEST and QA facilities before finalizing all of the configuration in the Production Facility.
To make a Copy of the Production Facility utilize the Facility Copy Editor found under Setup Administration.
For more information on DC Setup, refer Chapter 6.
System Parameters
Many RWMS configuration options are defined in System Control Parameters (SCPs) which apply to the entire facility. SCPs are set up according to each client's specific process flows.
For more information on System Control Parameters, refer to Chapter 7.
Accounts and Passwords
All users have their own user ID and password.
Logon standards require that passwords are changed after a predefined number of days have passed. This is controlled by two SCPs:
password_old : This is the number of days since the last password change; suggests that users change their password.
password_expire : This is the number of days since the last password change; forces users to change their passwords.
Passwords must be:
unique
at least seven characters in length
The minimum length of the password is controlled by the SCP min_password_length.
have a minimum of one alphabet and one numeric character
This is controlled by the SCP password_complexity. Set to N for numeric only passwords, A for alphabetic only passwords, AN for Alphanumeric only passwords (One alphabet and one number mandatory), ANX for Alphanumeric and any other special character based password (Minimum of one alphabet, one number and one special character (punctuation) mandatory) and X for any character based password. ANX is the suggested and the strongest setting. Any other setting will leave the system prone to brute force attacks.
different from the user name
Passwords are case-sensitive.
|
Note: The passwords are reset to the respective User IDs. This password must be changed immediately upon login. |
If an invalid password is used during login, the account gets locked after a few attempts. The number of attempts after which an account gets locked is set by the SCP max_invld_login_cnt. The account can be reset by the system administrator. If the account of the system administrator gets locked, it can be reset using a script rwms_reset_app_user_pwd.sh or using the User Interface. See Oracle Retail Warehouse Management System UI User Guide for more details.
User Roles
Standard RWMS security is based on the concept of privilege levels. Each user and RWMS function is assigned a privilege level (1-9). Users only have access to functions that are assigned to a privilege level less than or equal to their own privilege level.
For example, a user assigned privilege level 3 only has access to functions with a privilege level of 1, 2 or 3.
It is the responsibility of each client to set the privilege level of each screen in RWMS and then set the privilege level of each user in RWMS. It is critical that specific screens are set at high (9) privilege levels to prevent general users from accessing system setup screens. For example, the SCP Editor, User Editor, and Menu Editor should be set at privilege level 9 to protect global control settings.
Application Function/User Role Matrix
There are over 390 functions in RWMS. A full screen user process flow needs to be completed to ensure that all functions are assigned to the correct classification of users.
Create the Facility ID to be used for your production environment.
Ensure the DEST ID is created that represents the DC. (Destination Editor).
Some fields are required when creating new destinations. Client will need to create additional data such as carrier, service, and route before finalizing destinations.
Ensure the SCP. DC_dest_ID is updated with the DEST ID chosen for the DC.
Create the facility type for the new facility.
Create the new facility.
For System Control Parameters (SCP), review periodically and update as the data for the facility is being created.
Create Users/User Groups that will be involved in the creation/setup of the environment.
Associate proper privileges to users created in Step 1.
|
Note: Warehouse users can be defined later in the process. |
Define Menus/Privileges.
Set Working Days. Ensure to include the appointment start/end time and interval
Define location types.
Define Zones and Aisles.
Define locations (reserve, doors, staging, forward picking locations, put to store locations, and so forth).
If Task Management and/or Labor Management is enabled, Define Reference Points, Reference Point Mapping, and Location Reference associations.
Define Equipment Classes and Equipment.
Define receiving and shipping doors.
Define Unit Pick Systems. If applicable, set up Put To Store and 3rd Party Systems.
Define Printer and Print queues.
Configure Cubiscan device if the facility needs to capture the item dimensions and weight during receiving.
Review all System Control Parameters and make adjustments as needed to optimize your process flows.
Validate Vendor download from Host.
Define additional RWMS Item Attributes in the Item Default Editor at the Department, Class or Subclass Level before item download.
Validate Item download from Host. Perform additional item definition required to operate Distribution Center by using Item Master Editor.
Validate Purchase Order download from Host.
Validate Destination (Store, DC, Virtual) download from Host. Perform additional destination definition required to operate Distribution Center by using Destination Editor.
Validate Stock Order download from host.
Define Putaway Plans. Define Zone sequence and Fill Method (Empty, Same, Different).
Define Cycle Count Plans.
Choose a replenishment method from among ROP, Preplanned and Top Off and define the same.
Review and create/define Inventory Adjustment Codes, Disposition codes correlating with the Host System.
Review and update Transaction Codes, Stock Order Info Upload Codes.
Define Trouble Codes for Appointments, Containers.
Define WIP Codes.
Review the activities available in RWMS and make configuration changes as needed.Defining Activity Rules enables Task Management.
Enable Task Management at the Activity level. Defining Activity Rules further refines Task Management.
Enable Labor Management at the Activity level.
Assign Activities to the Items.
Assign Activities to Locations.Make sure all locations have XYZ coordinates and all reference points are defined.
Assign Activities to Equipment.
Create Activity Groups if utilizing Task Management.
Associate Activity Groups to Users.
Validate Destination download from host completed.
Define Carrier Codes.
Define Routes.
Define Carrier/Service/Routes.
Define Trailers.
