5Scheduled Jobs
Scheduled Jobs
WFM shares Scheduled Jobs view with WMS. The Job Type dropdown in this view offers multiple job types. Following are the four job types that are used in WFM.
Process Stage Track Record
This job type is used to schedule the process that picks up clock records from Stage Track Record, validate and move data to Track Record.
Stage Process
This process moves clock data from Stage Track Record to Track Record. The Employee ID corresponds to the ID in the WMS/WFM Users view. If a user with such an ID is not found in the Users view, the status of the record is updated as failed and appropriate error is written in the Error Message field.
The process also validates if the clock in or the clock out requests for a user are recorded in the correct order. For example, If the CICO Timestamp of a F2 (Break clock-in) is earlier than F1 (Facility clock-in) record for a user, the record is marked as failed.
If the CICO Type is F5 or F6 (Work Area clock-in/clock-out), the process validates if the Work Area on the record is valid.
Since facility clock-in is the first clock-in of the user for the day, if the CICO Type is F1 (facility clock-in), the shift is determined based on the CICO Timestamp of F1 record of the user. All other clock-in records for this user inherit shift from the F1 record.
Run WMS WFM Interface
This job type is used to schedule the process that picks up system activities from WMS and move data to WMS Activity Track in WFM. As a second step, the process moves data from WMS Activity Track to Daily Activity Track in WFM. This job accepts two parameters, “Username” and “Number of Days”.
The “Username” parameter needs to be a valid WMS user and should be eligible for the company/facility where the schedule job has been configured.
The “Number of Days” parameter only accepts values between 0 and 60. If no value is provided, it is defaulted to 7.
Interface Process
This interface moves data from WMS Activity (WMS) tables to WMS Activity Track (WFM tables). The next step in the process validates the User, SKU Line and WMS Transaction on each record before consolidating and moving the records to Daily Activity Track (WFM tables). With the WMS-WFM DB merge, since user table is now common between WMS and WFM, User validation is redundant. However, if either the SKU Line or WMS Transaction is not configured in WFM, the record is marked as ERROR and remains in WMS Activity Track.
Reprocessing Records
Records in WMS Activity Track with errors can be reprocessed by ensuring that missing data is first configured in WFM. For example, if a record fails due to missing SKU Line, the corresponding Unknown SKU Line column is populated with the Sku Line that is not configured in WFM. This Sku Line needs to be configured in WFM.
After configuring missing data, there are two ways in which error records can be reprocessed. The first option is to use the “Process WMS Activities” button on WMS Activity Track view. The other option is to just wait for the next scheduled run of the interface. The second step of the interface always tries to re-process error records first before processing new records.
If the reprocessing is triggered due to scheduled interface run, the “Number of Days” parameter is used to determine how many records should be reprocessed. Only records that fall in the range between current date and past “Number of Days” days are picked up for reprocessing. 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 September 21 and "Number of Days" has been set as 10, the interface reprocesses records that have "Begin time stamp" later than or equal to September 10th (September 21 – (10+1) days).
Note: “Number of Days” parameter is only used for reprocessing error records. Also this parameter is only used when the reprocessing is triggered by scheduled job. It is not used when reprocessing is triggered using “Process WMS Activities” button on WMS Activity Track view.
Purge Stage Track Record
This job type is used to schedule the process that purges old data from Stage Track Record. The job accepts a single job parameter “nbr_of_days”.
Purge Process
This process purges data from Stage Track Record that are older than a specified number of days and are either in PROCESSED, FAILED, IGNORED or CANCELLED status. The “nbr_of_days” parameter is used to determine how days worth data needs to be retained in Stage Track Record
For example, if the nbr_of_days parameter is set to 45 on the job, all records older than 45 days from current day will be purged (as long as they are in one of status mentioned above).
If the nbr_of_days parameter is not provided, the value is defaulted to 30
Purge WMS Activity Track
This job type is used to schedule the process that purges old data from WMS Activity Track. This job accepts two parameters, “Username” and “Facility”.
The “Username” parameter needs to be a valid WMS user and should be eligible for the company/facility where the schedule job has been configured.
“Facility” parameter is used to identify the facility for which purge is requested. If no value is provided or if the value provided is invalid (No such facility), then current facility is used.
Purge Process
This process purges data from WMS Activity Track that are older than a specified number of days and are either in SUCCESS or ERROR status.
There are 3 parts to this purge process. The first part mainly focuses on purging records with errors. The following four facility parameters are used for this purge: PURGE_NUMBER_OF_DAYS, PURGE_UNKNOWN_SKU, PURGE_UNKNOWN_TRANSACTION and PURGE_UNKNOWN_USER.
PURGE_NUMBER_OF_DAYS is used to determine how many days worth data needs to be retained in WMS Activity Track Record. PURGE_UNKNOWN_SKU, PURGE_UNKNOWN_TRANSACTION and PURGE_UNKNOWN_USER can accept values Y or N.
- If PURGE_UNKNOWN_SKU is set to Y, then records older than PURGE_NUMBER_OF_DAYS from current date, in ERROR status and a value populated in “Unknown SKU Line” field are purged
- If PURGE_UNKNOWN_TRANSACTION is set to Y, then records older than PURGE_NUMBER_OF_DAYS from current date, in ERROR status and a value populated in “Unknown Transaction” field are purged
- If PURGE_UNKNOWN_USER is set to Y, then records older than PURGE_NUMBER_OF_DAYS from current date, in ERROR status and a value populated in “Unknown User” field are purged.
Note: After the WMS WFM DB merge, it is unlikely that there would error-ed records due to unknown user)
The second part of the purge process focuses on records that moved successfully to Track Record. For this purge, only the PURGE_NUMBER_OF_DAYS facility parameter is used. Records older than PURGE_NUMBER_OF_DAYS from current date and in SUCCESS status are purged.
The third part of purge process focuses on invalid data. Records should either have values in Unknown fields or their counterparts. If a record does not have value in both, it is considered to be invalid data. For example, in the table below, rows 1, 2 and 3 represent valid data. Rows 4, 5 and 6 represent invalid data.
