Working with Drop Ship Background Jobs (WPBJ)

Purpose: Use this menu option to work with the CDC Async job used to process transactions between Order Broker’s Supplier Direct Fulfillment module and Order Management System for each company that has the Use OROB Drop Shipping (H13) system control value selected.

Starting and stopping the job: If you are using the Order Broker’s Supplier Direct Fulfillment integration, the CDC async job should be stopped and started each day. If the CDC async job does not have the current date, returns which are sent from Order Broker’s Supplier Direct Fulfillment module do show the current date. See Fulfillment (FUL) Periodic Functions under Scheduling Jobs for information on scheduling the job to start and stop on a daily basis.

Async status: 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 ACTIVE status.

• ENDING = The async is in the process of ending, but it 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.

In this chapter:

• Work with Drop Ship Background Jobs Screen

• Change Delay Time Screen

• Change Status Window

• Troubleshooting the CDC Async Job

Work with Drop Ship Background Jobs Screen

Use this screen to work with the CDC Async job.

How to display this screen: Enter WPBJ in the Fast path field or select Work with Drop Ship Background Jobs from a menu.

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 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 was last started. Numeric, 6 positions in user date format; 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.
Dly (Delay)	The number of seconds the async job waits for another record to process. Numeric, 3 positions; display-only.

Screen Option	Procedure
Change the delay time for the async job	Select Change for the async job to advance to the Change Delay Time Screen.
Start the async job	Select Start for the async job to start it. Periodic function: You can also use the STRCDC periodic function to start the CDC job if it is not currently active. If the job is currently active, or the other conditions described below under Troubleshooting are met, an error in the APP.log indicates: IX_CDC Job not submitted - Previous job not ended. See Logs for background. Troubleshooting: In order to start the async job, either at the screen or through a periodic function: • The Use OROB Drop Shipping (H13) system control value must be selected for at least one company in your Order Management System environment. • The async job must be in INACTIVE status. • There cannot be a Job History record for the IX_CDC job without an end date and time. You can review the records in the Job History table through Display Job History (DJHY). If the job does not end correctly (if, for example, the service stops while the job is running), you might need to update the Job History record in the database. • There cannot be an active procedure record for the FLX0976 program. You can review and, optionally, delete active procedures through Purge Active Procedures Across Users (MACX).
End the async job	Select End for the async job to end it. Periodic function: You can also use the ENDCDC periodic function to end the CDC job. Note: You can end the async job only if it is in ACTIVE status.
Change the status of the async job	Select Change Status for the async job to advance to the Change Status Window.
Work with background jobs	Select Background Jobs to advance to the Work with Background Jobs Screen.
Work with integration layer jobs	Select Integration Layer to advance to the Work with Integration Layer Process Screen.

Change Delay Time Screen

Purpose: Use this screen to change the Delay time for the CDC async job. The Delay time is the number of seconds that the async waits before looking for new records to process.

How to display this screen: Select Change for the CDC async at the Work with Drop Ship Background Jobs Screen.

Note: You can display this screen for the CDC async job only if the Use OROB Drop Shipping (H13) system control value is selected for at least one company in your Order Management System environment.

Change Status Window

Purpose: Use this window to change the status of the CDC async job.

How to display this screen: Select Change Status for the CDC async job at the Work with Drop Ship Background Jobs Screen.

Note: You can display this screen for the CDC async job only if the Use OROB Drop Shipping (H13) system control value is selected for at least one company in your Order Management System environment.

To change: Select the status you wish to assign to the CDC async job.

• Select Active if the CDC async job is running and the status is currently INACTIVE or STARTED.

• Select Inactive if the CDC async job is ended and the status is currently ACTIVE or ENDING.

Troubleshooting the CDC Async Job

There may be a problem with the CDC async if transactions sent from Order Management System to Order Broker’s Supplier Direct Fulfillment module, such as new POs, are being processed, but transactions sent from Order Broker’s Supplier Direct Fulfillment module to Order Management System, such as PO updates, are not being processed.

To solve the problem, stop and restart the CDC async.

If the CDC async job does not end when you stop it: If the CDC async job remains in ENDING status when you try to end it, it might be because there are multiple IX_CDC jobs running in the same Order Management System environment, for example, if the CDC async job was manually changed to INACTIVE and then started again, or if the CDC async ended incorrectly because the server was restarted while the job was running.

To eliminate multiple IX_CDC jobs, use the following steps:

1.	Manually change the status of the CDC async job to INACTIVE.
2.	Verify that the IX_CDC job is not active. You can use the Display Active Batch Jobs Screen to verify that the IX_CDC job is not active. • If the job is not on this screen, the job is not running. • If the job is on this screen, regardless of status, the job is running. To end the job: - Use the User field on the Display Active Batch Jobs Screen to determine the user ID of the person who started the IX_CDC job. - Use the Job Management Screen to end all IX_CDC jobs that are in a RUN or MSG status. You can use the User Name field on this screen to locate the IX_CDC jobs that you need to end. Select End for the job to end it. - Once you end the IX_CDC job, make sure that the job is no longer on the Display Active Batch Jobs Screen. If the job is still on this screen, select End for the CDC async job on the Work with Drop Ship Background Jobs Screen to end it.
3.	Use the Purge Active Procedures Across Users (MACX) menu option to check for active procedures related to Supplier Direct Fulfillment processing. If there are any active procedures related to Order Broker’s Supplier Direct Fulfillment processing, delete them.
4.	Start the CDC async. Once the CDC async is in ACTIVE status, verify that the IX_CDC job is now on the Display Active Batch Jobs Screen and that the My Jobs status for the job is RUN.