Run Scheduled Job Type

This scheduled job is used to interface input files into the system. These interface files consist of data (.csv) that are input to WMS, processed, and updated in the system.

Run Stage Interface

Job Parameter	User Action
Load Files	Set the value to True, if you want the interface files to be validated first in the stage table and then to master table.
process_stage_tables_flag	Set the value to True to process and validate the data of the input interface before processing to master table.
Stage Entity	Enter the entity name for which you wan to upload the interface file. For example, Item, Purchase Order.
File Pattern/List	If you have only set up one of the extract and will like to copy this info, then the value should be: * Order - ORH (for order header) ORD (for order dtl) * IBLPN - IBH ( iblpn header) IBD (iblpn detail) * IB Shipment - ISH ( Ib shipment header) ISL (ib shipment detail) * Vendor - VEN (no detail) * PO - POH (for PO header) POD (for PO detail) * OBLPNS - LPH ( oblpn header) LPD (oblpn detail) * IB LPNS LOCK - IBLPN_LOCK (no detail) * Inventory History - XIHT * Active Inventory - ACT_INV * Parcel Manifest - OPS (header) OPL (detail) * OB LOAD - OBS (header) OBL (detail) * Item - ITM (no detail) * If you have set up more than 1, and need to copy them you need to set up this value to *
Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.
Interface Folder Path	Enter the directory path from where the interface file is fetched.

This scheduled job runs the wave template mentioned in the job parameter on periodic timelines specified in a defined interval of time.

Run Wave Template

Job Parameters	User Action
Wave Template	Enter the valid wave template.
Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.
Cronname	Provides a logical name for this particular job. Since these are shceduled jobs there is no direct way to stop a particular job from running (once). There is a facility parameter: DISABLE_WAVE_CRON_ONCE which is a PIPE (\|) separated list of these ""cronnames"". If the cronname of the current job is in this facility parameter, the next execution of this JOB will be halted and this cron-name will be removed from facility parameter. The second execution will continue as before. This is typically used in production situations where there is an immediate need to disable one particular wave without affecting the rest of the schedule. Simply providing a cron-name with no entry in facility parameter has no effect.

Job Parameters

User Action

Wave Template

Enter the valid wave template.

Username

Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.

Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

Cronname

Provides a logical name for this particular job. Since these are shceduled jobs there is no direct way to stop a particular job from running (once). There is a facility parameter: DISABLE_WAVE_CRON_ONCE which is a PIPE (|) separated list of these ""cronnames"". If the cronname of the current job is in this facility parameter, the next execution of this JOB will be halted and this cron-name will be removed from facility parameter. The second execution will continue as before. This is typically used in production situations where there is an immediate need to disable one particular wave without affecting the rest of the schedule.

Simply providing a cron-name with no entry in facility parameter has no effect.

This scheduled job runs the work order template mentioned in the job parameter on periodic timelines specified in the mandatory interval.

Run Work Order Wave Template

Job Parameters	User Action
Wave Template	Enter the work order template.
Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.
cronname	Provides a logical name for this particular job. Since these are shceduled jobs there is no direct way to stop a particular job from running (once). There is a facility parameter: DISABLE_WAVE_CRON_ONCE which is a PIPE (\|) separated list of these "cronnames". If the cronname of the current job is in this facility parameter, the next execution of this JOB will be halted and this cron-name will be removed from facility parameter. The second execution will continue as before. This is typically used in production situations where there is an immediate need to disable one particular wave without affecting the rest of the schedule. Providing a cron-name with no entry in facility parameter has no results.

Job Parameters

User Action

Wave Template

Enter the work order template.

Username

Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.

Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

cronname

Provides a logical name for this particular job. Since these are shceduled jobs there is no direct way to stop a particular job from running (once). There is a facility parameter: DISABLE_WAVE_CRON_ONCE which is a PIPE (|) separated list of these "cronnames". If the cronname of the current job is in this facility parameter, the next execution of this JOB will be halted and this cron-name will be removed from facility parameter. The second execution will continue as before. This is typically used in production situations where there is an immediate need to disable one particular wave without affecting the rest of the schedule.

Providing a cron-name with no entry in facility parameter has no results.

This scheduled job executes the replenishment wave template for the configured time interval.

Run Replenishment Template

Job Parameters	User Action
Wave Template	Enter the wave template which you want the replenishment to run. Note: This is a mandatory field. And suports running schedule job for single wave template only.
Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.
Cronname	Provides a logical name for this particular job. Since these are schedule jobs, there is no direct way to stop a particular job from running (once). The facility parameter: DISABLE_WAVE_CRON_ONCE which is a PIPE (\|) separate the list of these ""cronnames"". If the cronname of the current job is in this facility parameter, the next execution of this JOB will be halted and this cron-name will be removed from facility parameter. The second execution will continue as before. This typically is used in production, where there is an immediate need to disable one particular wave without affecting the rest of the schedule. Providing a cron-name with no entry in facility parameter has no results.

Job Parameters

User Action

Wave Template

Enter the wave template which you want the replenishment to run.

Note: This is a mandatory field. And suports running schedule job for single wave template only.

Username

Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.

Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

Cronname

Provides a logical name for this particular job. Since these are schedule jobs, there is no direct way to stop a particular job from running (once). The facility parameter: DISABLE_WAVE_CRON_ONCE which is a PIPE (|) separate the list of these ""cronnames"". If the cronname of the current job is in this facility parameter, the next execution of this JOB will be halted and this cron-name will be removed from facility parameter. The second execution will continue as before. This typically is used in production, where there is an immediate need to disable one particular wave without affecting the rest of the schedule.

Providing a cron-name with no entry in facility parameter has no results.

This scheduled job generates the reports configured in the report instances UI for a defined interval of time. The run report supports only csv format.

Run report

Job Parameters	User Action
Report Name	Enter the report name that you want the scheduler to run, configured in the Report Instance UI.
WMS Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

This scheduled job is used to run the Cycle Count (CC) task without manually running the cycle count template.

Run CC Task Templet

Job Parameters	User Action
task_creation_template_descr	Enter the description of cycle count task creation. Note: The template type should be of Cycle Count (CC) only.
Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

This scheduled job is used to execute the wave group template for a configured time interval. Only one wave group template should be configured. Each wave group template may consist of one or more wave templates.

Run Wave Group Template

Job Parameters	User Action
Wave Group Name	Enter the wave group name.
Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.
Trigger File Path	Enter a valid file path. Usually this is a file in the client sftp folder. If provided, the scheduled job will wait for "wait minutes for trigger" to find the file before starting the actual wave group. The trigger file mechanism allows client to control exactly when the wave group runs. For e.g. the client may choose the drop the file ONLY after all their orders are successfully interfaced into OCWMS.
Wait Minutes for Trigger	Enter the number of minutes for the system to wait for finding the trigger file. At the end of this wait period the system will behave as per the "Run at end of Wait" parameter. Used only when a trigger file path is specified.
Run at end of Wait	Set the value to True if you want the system to run the wave after the wait period mentioned in the above field is over and the trigger file is still not found. Otherwise, set the value to False and the system does not start the waving logic at the end of wait. By default, the value is set to False. Used only when a trigger file path and wait minutes for trigger is specified.
Trigger Contains Last Order	Valid values are y/yes or n/no. Regardless of value, it is effective only when Trigger File Path and Wait Minutes for Trigger are enabled. If this value is y/yes the system expects to find an order number inside rhe file mentioned in trigger path. The system then waits for "wait minutes for trigger" or until this order is found within WMS (whichever is earlier). At the end of wait, if the order is found the wave will executed. If the order is not found the wave will not execute. Note: Run at end of wait parameter does NOT apply when this is effective.

This schedule job generates the IBLPN report for every defined interval of time.

Run IBLPN Report

Job Parameters	User Action
WMS Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.
Delimiter	You can use this delimiter to seperate the data fields. By default, \| is set as delimiter. You can define your own delimiter. For example: , (comma)
Status	You can define the status of the IBLPN that needs to included in the IBLPN report. By default, IBLPNs in status 10 to 30 is included. You can define IBLPN status code (seperated by comma) to be included in the report. For example: 10,40,30 The supported values are 10,30,40,50,5,7

Job Parameters

User Action

WMS Username

Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.

Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

Delimiter

You can use this delimiter to seperate the data fields. By default, | is set as delimiter. You can define your own delimiter. For example: , (comma)

Status

You can define the status of the IBLPN that needs to included in the IBLPN report. By default, IBLPNs in status 10 to 30 is included. You can define IBLPN status code (seperated by comma) to be included in the report. For example: 10,40,30

The supported values are 10,30,40,50,5,7

This scheduled job moves data from WMS Activity (WMS) tables to WMS Activity Track (WFM tables), and then validates the user, SKU Line, and WMS transaction on each record before consolidating and moving the records to Daily Activity Track (WFM tables).

Run WMS WFM Interface

Job Parameters	User Action
WMS Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.
Number of days	Set the number of days. This parameter would be used by interface to only process (or reprocess) records that fall in the range between current date and (Number of Days = x) past days. An extra day is added to "Number of Days" to take into account any user transaction that could have occurred over midnight traversing between two days. For example, if current date is July 7 and "Number of Days" has been set as 10, the interface should only process/reprocess records that have "Begin time stamp" later than or equal to June 27th (July 7 - 10 days). Note: The max number of days allowed on this parameter would be 60. Leaving the field unpopulated will default the value to 7.

Job Parameters

User Action

WMS Username

Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.

Number of days

Set the number of days.

This parameter would be used by interface to only process (or reprocess) records that fall in the range between current date and (Number of Days = x) past days. An extra day is added to "Number of Days" to take into account any user transaction that could have occurred over midnight traversing between two days.

For example, if current date is July 7 and "Number of Days" has been set as 10, the interface should only process/reprocess records that have "Begin time stamp" later than or equal to June 27th (July 7 - 10 days).

Note: The max number of days allowed on this parameter would be 60. Leaving the field unpopulated will default the value to 7.

This scheduled job generates the web report for every defined interval of time. The output formats supported are CSV/PDF.

Note:

It is recommended that you use the Output interface for generating Web Reports and Web Reports Gen 2. You do not need to use SFTP PUT.
Scheduled Job uses an internal directory path "$LGF_FILES_HOME/interfaces/<COMPANY_CODE>/<FACILITY_CODE>/output/reports" to generate the reports for which the output interface is configured.

Run Web Reports and Web Report Gen-2

Job Parameters	User Action
Web report path	Enter the path of the report that you want to execute. For example: <Folder>/<sub-folder>/<report name>"
WMS Username	Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured. Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.
Web report format	Enter the format you want the output file. For example, csv and pdf. Note: Enter the format in lower case.

Job Parameters

User Action

Web report path

Enter the path of the report that you want to execute.

For example: <Folder>/<sub-folder>/<report name>"

WMS Username

Enter a valid wms username. The username provided should be eligible for the facility/company where the scheduled job is configured.

Note: If the schedule job is run by providing an invalid username or blank value or username name that does not have the eligibility for that particular facility/company, then the job fails.

Web report format

Enter the format you want the output file. For example, csv and pdf.

Note: Enter the format in lower case.