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 topic:

•         Work with Drop Ship Background Jobs Screen

•         Change Delay Time Screen

•         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.

See Troubleshooting the CDC Async Job for information on correcting the status if necessary.

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 if it is inactive and not currently running on any server.

Periodic function: You can also use the STRCDC periodic function to start the CDC job. If the job is currently active, or the other conditions described below under Troubleshooting are met, an error in the APP.log might indicate: 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 and must not actually be running on any server.

•         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).

See Troubleshooting the CDC Async Job for more information.

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 and is actually running on any server. See Troubleshooting the CDC Async Job for more information.

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.

Troubleshooting the CDC Async Job

There may be a problem with the CDC async job if transactions sent from Order Management System to Order Broker’s Supplier Direct Fulfillment module, such as that 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 use the End option: If the CDC async job does not end correctly, use the JOBCLN periodic function. This periodic function updates the CDC async job as follows:

If the IX_CDC is currently running on any server, the JOBCLN function does the following:

•         If the status is INACTIVE, change it to ACTIVE.

•         If there is not an active procedure, create it.

•         If the status is STARTED or ENDING, do not change the status.

•         If the job is in END, FINISHED or MSG at the Job Management (My Jobs) screen, update it to RUN and update Job History (Display Job History (DJHY)).

If the IX_CDC job is not currently running on any server, the JOBCLN function does the following:

•         If the status is ACTIVE, STARTED, OR ENDING, update it to INACTIVE.

•         If there is an active procedure, delete it.

•         If the job is in any status other than END and FINISHED at the Job Management screen, update it to END and update Job History.

After the JOBCLN function ends, you can restart the job.

See Using the JOBCLN Function to Resolve Job Status Across Servers for more background.

 

________________________________