WMS background jobs monitor and process information received from another system into CWDirect, such as information from CWCollaborate, Locate’s Supplier Direct Fulfillment module, a warehouse management system, PkMS, or Carousel.
Background jobs (async jobs) are used to process the non-time sensitive file updates, such as analysis and reporting updates, associated with transactions that are processed throughout the day. These jobs run in the background and process transactions in the order that they are sent to the async.
In this topic:
• Work with WMS Background Jobs Screen
• Starting the Background Jobs
• Change PkMS Async Job Screen
• Work with Carousel Upload Screen
• Display Carousel Interface Detail Screen
• BILLING async: processes shipment confirmations and void/reprint pick slips sent to CWDirect from PkMS; see PkMS BILLING Async Processing.
• CAROUSEL async: validates and processes pick control records uploaded from the Carousel system; see CAROUSEL Async Processing.
• CDC async: processes CDC transaction records for information passed to and from CWDirect and CWCollaborate or Locate’s Supplier Direct Fulfillment module; see CWCollaborate Interface or Locate Supplier Direct Fulfillment Interface.
• FTP async: processes item/SKU, notes, vendor, purchase order, and return information that you are sending to PkMS using FTP processing; see Sending and Receiving WMS Information using FTP Processing.
• PIX async: processes inventory transaction records sent to CWDirect from PkMS or a warehouse management system; see WMS Inventory Transaction Setup.
• PIX_REPROC async: reprocesses inventory transactions in error from the PIX async that contain an R (reprocess) status in the Interface I/T Error file. Records that pass validation are sent back through the PIX async; see PIX_REPROC ASYNC Processing.
• POLAYER async: validates and processes records in the PO Layering Interface file. If records pass validation, this async creates a record in the CWDirect Purchase Order Layering file.
Async statuses: The status of the async indicates whether it can process any information it receives.
• STARTED: The async is starting, but is not yet ACTIVE.
• ACTIVE: The async is up and running. In order to process information, the async must be in an ACTIVE status.
• ENDING: The async is in the process of ending, but is not yet INACTIVE.
• INACTIVE: The async is not running.
When does the async look for records to process? The Delay time controls when the async looks for new records to process. This time determines the amount of time, in seconds, the async waits before looking for new records to process.
Starting and stopping the jobs with periodic functions: You can set up the following commands as periodic functions to stop and start the BILLING, PIX, FTP, and PIX_REPROC jobs:
• Start jobs: Create a periodic function that calls the following command: Call PGM(PKX0052) PARM(' ')
• End jobs with monitoring (to avoid inadvertently shutting down the jobs in a second environment): Create a periodic function that calls the following command: Call PGM(PKX0062) PARM(' ')
Note: Use the command that ends jobs with monitoring if you want to wait until all PkMS processing has ended before starting the next process. For example, if you have both a test and a production environment, you want to avoid shutting down processing in your production environment when you shut down your test environment jobs; the monitoring command cannot distinguish between the two environments, but it detects that there is still processing going on and so does not end the jobs.
• End jobs without monitoring (if you are running the jobs in a single environment): Create a periodic function that calls the following command: Call PGM(PKX0051) PARM(' ')
See Working with Periodic Functions (WPER) for more information on setting up periodic functions.
Work with WMS Background Jobs Screen
How to display this screen: Enter WPBJ in the Fast path field at the top of any menu or select Work with PkMS Background Jobs from a menu.
IXX0004 DISPLAY Work with WMS Background Jobs 1/22/14 16:14:34
Opt Job Status Start Date Start Time Started By Ended By Dly
Type options, press Enter. 2=Change 7=Start 8=End 10=Display Records 11=Change Status
BILLING INACTIVE 4/06/11 17:09:40 SOLSON SOLSON 1 CAROUSEL INACTIVE 9/26/06 17:02:33 EKAPLAN EKAPLAN 30 CDC ACTIVE 1/22/14 9:53:05 EKAPLAN EKAPLAN 300 FTP INACTIVE 2/19/07 16:21:06 MFAYLE MFAYLE 30 PIX INACTIVE 5/13/10 11:15:00 MERICKSON KVUTECH 5 PIX_REPROC INACTIVE 3/25/08 20:31:10 SCARTER SCARTER 10 POLAYER INACTIVE 4/07/08 17:44:14 EBOTELHO EBOTELHO 30
F3=Exit F7=Start All F8=End All F12=Cancel |
Field |
Description |
Job |
The name of the async job. Alphanumeric, 10 positions; optional. |
Status |
The status of the async job. Valid status codes are: STARTED: The async is starting, but is not yet ACTIVE. ACTIVE: The async is up and running. In order to process information, the async must be in an ACTIVE status. ENDING: The async is in the process of ending, but is not yet INACTIVE. INACTIVE: The async is not running. Alphanumeric, 10 positions; display-only. |
Start date |
The date the async job was last started. Numeric, 6 positions; display-only. |
Start time |
The time the async job was last started. Numeric, 6 positions; display-only. |
Started by |
The user ID of the person who last started the async job. Alphanumeric, 10 positions; display-only. |
Ended by |
The user ID of the person who last ended the async job. Alphanumeric, 10 positions; display-only. |
The amount of time, in seconds, a WMS async job waits for another record to process. Numeric, 3 positions; display-only. |
Screen Option |
Procedure |
Change the delay time for a PkMS or CDC async job |
Enter 2 next to the async job to advance to the Change PkMS Async Job Screen. |
Start a PkMS or CDC async job |
Enter 7 next to the async job. See Starting the Background Jobs. |
End a PkMS or CDC async job |
Enter 8 next to the async job. See Ending the Background Jobs. |
Display pick control records uploaded from the Carousel system |
Enter 10 next to the CAROUSEL async to advance to the Work with Carousel Upload Screen. An error message displays if you enter 10 next to an async other than CAROUSEL: 3 Display record option not valid for this background job. |
Change the status of a PkMS or CDC async job |
Enter 11 next to the async job to advance to the Change Status Window. |
Start all WMS async jobs |
Press F7. See Starting the Background Jobs. |
End all WMS async jobs |
Press F8. See Ending the Background Jobs. |
To start a single async job: Enter 7 next to an async job at the Work with WMS Background Jobs Screen. The status of the async job changes to STARTED and then to ACTIVE.
To start all async jobs: Press F7 at the Work with WMS Background Jobs Screen. The status of the async jobs changes to STARTED and then to ACTIVE.
• The BILLING, PIX, and PIX_REPROC ASYNCS only start if the Use PkMS Interface Values (F31) system control value is set to Y. for at least one company in your environment.
• The CAROUSEL async only starts if the Use Carousel Interface (G55) system control value is set to Y. for at least one company in your environment.
• The CDC async starts only if system control value Use CWCollaborate/Locate (H13) on the Drop Ship Integration Values Screen (H20) is set to Y. for at least one company in your environment. If you use a periodic function (program name MSR0949) to start your CWDirect system async jobs, the CDC async will also start when the system async jobs start. See Periodic Functions for the sample periodic function that starts the system async jobs.
Note: In order to start an async job, the async job must be in an INACTIVE status.
To end a single async job: Enter 8 next to an async job at the Work with WMS Background Jobs Screen. The End Asynchronous Jobs pop-up window displays.
End Asynchronous Jobs
Scheduled submit . . N (Y/N) End Time . . . (HH:MM:SS) End date . . . . 22101
F12=Cancel
|
Enter Y in the Scheduled submit field, and enter an End time and End date (the current date defaults, but you can override it) to schedule a date and time when the async job will end. Otherwise, press Enter to end the job immediately. The status of the async job changes to ENDING and then to INACTIVE.
To end all async jobs: Press F8 at the Work with WMS Background Jobs Screen. The status of the async jobs changes to ENDING and then to INACTIVE.
The CDC job must be ended by entering 8 next to the single job; it does not end when you use the F8 option. If you use a periodic function (program name MSR0954) to end your CWDirect system async jobs, the CDC async will also end when the system async jobs end. See Periodic Functions for the sample periodic function that ends the system async jobs.
Note: You cannot end an async job unless the async job is in an ACTIVE status.
To change: Enter 2 next to an async job at the Work with WMS Background Jobs Screen to advance to the Change PkMS async Job screen. You can only change the delay time (in seconds) on this screen. See Work with WMS Background Jobs Screen for field descriptions.
You can access this screen for the CDC async only if system control value Use CWCollaborate/Locate (H13) on the Drop Ship Integration Values Screen (H20) is set to Y for at least one company in your environment.
Purpose: Use this window to change the status of an async job.
How to display this screen: Enter 11 next to an async job at the Work with WMS Background Jobs Screen.
Change Status
Job : BILLING
1=Select
*ACTIVE *INACTIVE
F3=Exit
|
To change: Enter 1 next to the status you want to assign to the background job.
• Select INACTIVE if the background job is ended and the status is currently ACTIVE.
• Select ACTIVE if the background job is running and the status is currently INACTIVE.
You can advance to this screen for the CDC async only if system control value Use CWCollaborate/Locate (H13) on the Drop Ship Integration Values Screen (H20) is set to Y for at least one company in your environment.
Work with Carousel Upload Screen
Purpose: Use this screen to review pick interface upload headers uploaded from the Carousel system. The Carousel system uploads pick interface upload headers to the Pick Interface Upload Header file. Pick interface upload details are uploaded to the Pick Interface Upload Detail file. You can review pick interface upload details on the Display Carousel Interface Detail Screen.
Note: You can send pick control information to the Carousel system during pick slip generation if the Use Carousel Interface (G55) system control value is set to Y.
How to display this screen: Enter 10 next to the CAROUSEL async at the Work with WMS Background Jobs Screen.
IXX0016 DISPLAY Work with Carousel Upload 1/13/00 16:07:16
Sts Pick Pick Order Opt Cmp Cde Cntl# Date Number Ship-To Name
Type options, press Enter. 4=Delete 8=Display details
242 P 2482 0 - 000 242 P 2483 0 - 000 242 P 2484 6/30/99 3437 - 001 CAROUSEL&NONCAROUSEL ITMS, TEST 242 E 2491 0 - 000 242 E 2496 7/13/99 3436 - 001 LULU'S PLACE ATTN: WAGNER-PURDON, W 242 P 2500 7/14/99 3448 - 001 LULU'S PLACE ATTN: WAGNER-PURDON, W 242 E 2503 7/15/99 3452 - 001 COMPANY ATTN: CAROUSEL TESTING, NEW 242 P 2504 7/15/99 3453 - 001 CAROUSEL&NONCAROUSEL ITMS, TEST 242 P 2543 10/01/99 3502 - 001 COMMERCIALWARE ATTN: CAROL INGRIDST 242 P 2552 10/08/99 3505 - 001 CAROUSEL&NONCAROUSEL ITMS, TEST 242 P 2555 10/25/99 3510 - 001 COACHES INCORPORATED ATTN: PURDON +
F3=Exit F12=Cancel |
The CAROUSEL async monitors the Carousel Pick Interface Upload Header file for picks processed by the carousel system.
1. The CAROUSEL async reviews the Pick Interface Upload Header file for any records in an O (open) status.
2. For pick interface upload headers in an O status, the async reads the associated pick interface upload detail records and verifies that the quantity printed equals the actual quantity.
3. If the quantity printed equals the actual quantity, the async changes the status of the pick interface upload header and detail records from O (open) to 3 (post carousel).
4. If the printed quantity does not equal the actual quantity, the system adjusts the pick.
• The system passes the pick detail information to Void/Reprint.
• After all of the pick lines that have a printed quantity that does not equal the actual quantity are passed to Void/Reprint, Void/Reprint assigns a new pick control number to replace the original pick control number.
• The system unreserves the items on the pick that did not ship.
• The pick control status is changed to 3 (post carousel).
• The system writes an order transaction history message indicating the voided pick number and the new pick number.
5. The async then calls the pick print program defined in the Pick Printing Program (C37) system control value for each pick interface upload header and the associated details. You can view the pick slips that printed while the async was ACTIVE, by ending the CAROUSEL async and reviewing the spooled files.
6. Once all of the pick interface upload details for a pick interface upload header have been processed by the CAROUSEL async, the system updates the associated pick control header and pick control details to an O (open) status.
7. Carousel interface upload headers and the associated details are deleted once the pick has been billed.
Carousel upload records in error: The system places any pick interface upload records that contain errors in an E (error) status. Possible pick interface upload errors are:
• actual quantity is greater than the printed quantity
• invalid company code
• invalid pick control number
• invalid pick control line number
The system places a pick interface upload header in an error status if any of the associated pick interface upload details are in error. The system does not process pick interface upload records that are in an error status.
Field |
Description |
Cmp (company) |
The company associated with the pick interface download header record. Numeric, 3 positions; optional. |
Sts cde (status code) |
The status of the pick interface upload header. Valid statuses are: E = The pick interface upload header contains an error. P = The pick interface upload header has been processed. blank = The pick interface upload is waiting to be processed. Alphanumeric, 1 position; optional. |
Pick control # |
The pick control number associated with the pick interface download header. Numeric, 7 positions; optional. |
Pick date |
The date the pick interface upload header was uploaded from the Carousel system. This represents the date the carousel items were picked on the Carousel system. Numeric, 6 positions (MMDDYY format); display-only. |
Order number |
The order number associated with the pick interface upload header. Numeric, 7 positions; display-only. |
Ship to number (unlabeled field next to the order number) |
The ship to number associated with the pick interface upload header. Numeric, 3 positions; display-only. |
Ship to name |
The last name, first name, and middle initial of the ship to customer associated with the order. Alphanumeric, 35 positions; display-only. |
Screen Option |
Procedure |
Delete a pick interface upload header in an error status |
Enter 4 next to a pick interface upload header to delete it. An error message displays if you enter 4 next to a pick interface upload header record that is not in an E (error) status:
Can only delete records in an Error status. |
Review pick interface upload details for the associated pick interface upload header |
Enter 8 next to a pick interface upload header to advance to the Display Carousel Interface Detail Screen. |
Display Carousel Interface Detail Screen
Purpose: Use this screen to review the pick interface upload details associated with a pick interface upload header. The pick interface upload detail identifies carousel picks that are ready for printing.
How to display this screen: Enter 8 next to a pick interface upload header at the Work with Carousel Upload Screen.
IXX0018 DISPLAY Display Carousel Interface Detail 1/13/00 16:28:18
Pick Control # : 2447
Sts Line # Item SKU Tote Printed Actual Cde Number quantity Quantity
O 1 BUN98 1 0 0 E 2 ITXM 9 5 2 P 3 CAROP84R 574 1 1
F3=Exit F12=Cancel |
Field |
Description |
Pick control # |
The pick control number defined for the pick interface download detail. Numeric, 7 positions; display-only. |
Sts cde |
The status of the pick interface upload detail. Valid values are: E = the pick interface upload detail contains errors. P = the pick interface upload detail has been processed. blank = the pick interface upload detail is open and is waiting to be processed. Alphanumeric, 1 position; display-only. |
Line # |
The pick control line number associated with the pick interface download detail. Numeric, 3 positions; display-only. |
Item |
The item number from the pick control detail associated with the pick interface upload detail. Alphanumeric, 12 positions; display-only. |
SKU |
The SKU from the pick control detail associated with the pick interface upload detail. Alphanumeric, 14 positions; display-only. |
Tote number |
The tote number from the Carousel system. The tote number identifies the tote where the operator placed the item. Numeric, 5 positions; display-only. |
Printed quantity |
The printed quantity from the carousel pick download detail. Numeric, 5 positions; display-only. |
Actual quantity |
The quantity of this item picked in the carousel area. If the actual quantity if greater than the printed quantity, the pick interface upload detail is placed in an error status. Numeric, 5 positions; display-only. |
The async job dedicated to CWCollaborate or Locate drop ship transactions is the CDC background job, which you can start only if the Use CWCollaborate/Locate (H13) system control value on the Drop Ship Integration Values Screen (H20) is set to Y for at least one company in your environment.
If you are using CWCollaborate or Locate’s Supplier Direct Fulfillment module, the CDC job should be stopped and started each day. If the async does not have the current date, invoices on drop ship orders which are confirmed, or returns which are sent from CWCollaborate, will not show the current date.
If you are using Locate’s Supplier Direct Fulfillment module, you also need to have the Locate Java Handlers running. See Locate Supplier Direct Fulfillment Interface for background.
In order to have this job process drop ship updates for your company, you must have the Use CWCollaborate/Locate (H13) system control value set to Y, and your company must be flagged as Active in Setting Up Companies (WCMP).
This job also processes A/P invoice uploads. See Working with A/P Invoice Upload Errors (WAPU) for an overview.
Troubleshooting the CDC Async job
If CWCollaborate or Locate drop ship activity is not being processed through the async: If new POs are being transmitted to CWCollaborate or Locate, but PO updates (cancel requests, address changes, and incoming transmissions as well as returns return cancellations from CWCollaborate) are not being processed, there may be a problem with the async. As a first step to solving the problem, stop and start the async. For integration with Locate, you also need to start the Locate Java Handlers before starting the CDC async job, as described below.
If the async job does not end when you stop it: Occasionally, the async job does not stop when you end it; it remains in Ending status. If this happens, it may be because there are multiple IX_CDC jobs running in the same environment, for example, if the async job was manually changed to INACTIVE and then started again, or if the ASYNCS ended hard (for updates to the iSeries or other reason). To eliminate multiple IX_CDC jobs, take the following steps:
1. Manually change the status of the CDC async job to INACTIVE.
2. Check all async jobs to make sure the IX_CDC job is not active. To check:
• Enter at a command line: Wrksbsjob async
• Scan the list for IX_CDC jobs. End the jobs that are in your environment. To determine whether the jobs are in your environment, on each IX_CDC job, enter option 5 and then option 13. Check the library list on the Display Library List screen.
3. Check for active procedures, using the MACX menu option. Purge active procedures that have been running on the CDC async.
4. Start the CDC async. Stop and start again to check that it is working correctly.
Note: You can have multiple IX_CDC jobs running at the same time if each job is in a different environment.
Java helpers for integration with Locate: For integration with Locate Supplier Direct Fulfillment Interface, the Java helper jobs are required. These jobs need to start before the CDC async starts, and end after the CDC async stops. Typically, you use a periodic process to stop and start the Java helpers and CDC async job on a daily basis. See Background Processing for Integration with Locate’s Supplier Direct Fulfillment Module for an explanation of processing for integration with Locate.
See CDC Async and CDC Batch Jobs for CWCollaborate Integration for an explanation of CDC async processing for integration with CWCollaborate.
