Go to primary content
Oracle® Retail Warehouse Management System Operations Guide
Release 15.0
E65925-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

4 Batch Management

This chapter describes the batch programs that should be run periodically to remove obsolete data from the system, to schedule locations for cycle counting, and to close appointments that are now reconciled. You should run these programs using the operating system facility (cron) for scheduling jobs for unattended operation.

In the following Table 4-1, the name of the program to run is listed under the column heading Name. The programs are in the $RDM_BIN directory. For each routine, a system parameter exists that specifies the number of days of data to retain. These parameters are maintained on the System Parameter Editor screen.

The OS user must submit the jobs. The user's cron should first execute the .profile to set the environmental variables.

Table 4-1 Batch Programs

Name Purpose Parameters Frequency

automate_wave.sh

To call the automate_wave process.

facility_id, set name, order type (optional)

Every several minutes that meets customer needs

capacity_replen.sh

Releases on-hold replenishments destined for Forward Pick locations.

facility_id

Every several minutes that meets customer needs

insert_distribution_queue.sh

Works with the Automate wave processing.

facility_id

Every several minutes or time that meets customer needs

inv_bal_upload_b.sh

Create an inventory balance upload file for each facility id, part of the facility type.

facility_id

Once daily

maintain_wave_stats.sh

Updates wave statistics.

facility_id

Every 15 minutes

purge_activity_log.sh

Purges all aged records from the ACTIVITY_LOG table

facility_id

Once daily or weekly as per customer needs

run_distribution.sh

Matches inventory to allocation requests, creates pick directives and prints picking packages (if applicable).

facility_id

Manually or every 15 minutes

run_task_priority.sh

Updates correct priority against each Task based on the rules defined.

The script can be run manually through GUI as well.

facility_id

Every several minutes that meets the customer needs

rwms_alter_purge_sec_obj_sch.sh

Changes the schedule of the database job RWMS_PURGE_SECURITY_OBJ. By default this database job is rub every 2 minutes.

Interval in minutes

Manual

schedule_cycle_count_b.sh

Schedules cycle counts (SS) for the DC.

facility_id

Once daily

schedule_rop_distribution.sh

Schedules a Re-Order Point distribution run.

facility_id

Every 5 minutes

unreconciled_appt_monitor.sh

Closes any unreconciled appointments that had all labels scanned or nulled.

facility_id

Hourly

purge_rwms_tables.sh

performs table purges based on data setup on the PURGE_TABLE_SETUP table.

facility_id

Once daily


Security

RWMS Batch programs can be run using wallet alias as the first parameter to the batch command line arguments. This is enabled to prevent the security concerns around exposing database user id and password while running the batch programs. For more information about wallet creation, refer to the Oracle Retail Warehouse Management System Installation Guide.

The wallet and wallet alias creation is a pre-requisite to use batch programs in secured mode. For batch programs, RDMUSR and RDMPWD variables are used. If we assume wallet alias is dvols29_rwms01batch, usage is as follows:

Export TNS_ADMIN = /projects/rwms13.2/dev/forms
PATH=$ORACLE_INSTANCE/bin:/u00/webadmin/rwms13instDAN/base/forms_
scripts:/u00/webadmin/product/10.3.3/WLS_Forms/as_
1/bin:/u00/webadmin/product/10.3.3/WLS_Forms/wlserver_
10.3/server/bin:/u00/webadmin/product/10.3.3/WLS_Forms/modules/org.apache.ant_
1.7.1/bin:/vol.rtk/java/oracle_linux/jdk1.6.0_
18.64bit/jre/bin:/vol.rtk/java/oracle_linux/jdk1.6.0_
18.64bit/bin:/u00/webadmin/product/10.3.3/WLS/jdk1.6.0_
18.64bit/bin:/vol.rtk/java/oracle_linux/java1.5.0_10/bin:.:/vol.rtk/java/oracle_
linux/java1.5.0_
10/bin:.:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/ccs/bin:/usr/ucb:.:/
vol.rtk/tools/bin:/dba/bin:/usr/local/bin:/usr/bin:/etc:/usr/sbin:/usr/ccs/bin:/
usr/ucb:.:/vol.rtk/tools/bin:/dba/bin:/usr/local/bin:/usr/bin:/etc:/usr/sbin:/u00
/webadmin/product/10.3.3/WLS/bin; export PATH
SORTATION_DIR=/u01/app/rdm/hostcomm/sortation;
export SORTATION_DIR
DOWNLOAD_DIR=/u01/app/rdm/hostcomm/download;
export DOWNLOAD_DIR
UPLOAD_DIR=/u01/app/rdm/hostcomm/upload;  
export UPLOAD_DIR
Export RWMS_FORMS_ENV_FILE = /u00/webadmin/product/10.3.2_WLS_64/WLS_64/user_
projects/domains/ClassicDomain/config/fmwconfig/servers/WLS_
FORMS/applications/formsapp_11.1.1/config/develop/rwms132dvwallet.env
Export RMDUSR =
Export RDMPWD = @dvols29_rwms01batch

Note:

The value for fields shown in italics (above) must be set to the value appropriate for the installation.

RWMS batch programs use a concatenation of RDMUSR/RDMPWD to execute the batch programs. When @<wallet_entry> is set as RMDPWD the end result is /@<wallet_entry>.

For wallet alias dvols29_rwms01batch, end result is /@ dvols29_rwms01batch.

Passwords

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.