Working with the ORDR_ASYNC Job

Purpose: The Order Processing ASYNC job updates system tables with order and demand information as orders are entered and maintained.

As you enter or maintain orders, the system sends the records to the Order Processing data queue for processing. As soon as the Order Processing Data queue receives a record to process, the record is processed immediately, regardless of the status of the Order Processing ASYNC (ORDR_ASYNC) job. The ORDR_ASYNC job processes multiple orders simultaneously.

If there are any records that the job cannot update, it skips that record and continues.

You can review the status of each record in the data queue at any point by displaying the Display Order Ship To Data Queue Screen.

Quotes: The system does not send quotes to the Order Async until the quote is converted to an order; see Entering Pre-Order Quotes for an overview.

Related system control value: The Update Demand for Order Maintenance Transactions (C72) controls how this job processes updates.

Note: While the Order Async job does not need to be active to process records, you should set the Order Async job to active to handle reorganization and cleanup of any transactions that did not process correctly.

In this topic:

• Display Asynchronous Job Screen (Displaying the Order Processing ASYNC Job)

• Display Order Ship To Data Queue Screen

• Updates During Background Processing

Display Asynchronous Job Screen (Displaying the Order Processing ASYNC Job)

Purpose: Use this screen to display the job attributes for each background ASYNC job, including the Order Processing ASYNC job.

How to display this screen: Select Display for an ASYNC job at the Work with Background Jobs Screen.

Field	Description
Process name	The name of the process for this ASYNC job. The name of the order data queue is ORDERDATAQ. Alphanumeric, 10 positions; display-only.
Job name	The name of the ASYNC job. Alphanumeric, 10 positions; display-only.
Description	The description of the ASYNC job. Alphanumeric, 40 positions; display-only.
Start	The date and time the ASYNC job was last started and the User ID of the person who started it. (Date): Numeric, 6 positions; display-only. (Time): Numeric, 6 positions; display-only. (User ID): Alphanumeric; 10 positions; display-only.
End	The date and time the ASYNC job was last ended and the User ID of the person who ended it. (Date): Numeric, 6 positions; display-only. (Time): Numeric, 6 positions; display-only. (User ID): Alphanumeric; 10 positions; display-only.
Controlling job	A flag indicating whether this job controls other ASYNC functions. The controlling ASYNC job starts and ends other ASYNC functions. Valid values are: • Selected - This is a controlling ASYNC job. • Unselected - This is not a controlling ASYNC job. The CNTL_ASYNC job is the only controlling ASYNC job.
System Option	A flag indicating whether this is a system job that cannot be deleted by the user. Valid values are: • Selected - This job cannot be deleted by the user. • Unselected - This job can be deleted by the user.
Status	The current status of the job. Valid status codes are: • *ACTIVE • *INACTIVE • *ENDPEND • *JOBQ • *REORG Display-only.

Display Order Ship To Data Queue Screen

Purpose: Use this screen to review the records that have arrived in the data queue for processing since the last time you ended the ASYNC jobs. Records arrive in the data queue for new orders that are entered and for existing orders that are maintained. The status of each record, indicating if the record has been processed or if any errors exist, displays.

How to display this screen: Select Display Data Queue for the ORDR_ASYNC job at the Work with Background Jobs Screen.

Field	Description
Cmp (Company)	The number of the company for which the transaction was processed. If you are running operations for more than one company, transactions for all companies are submitted to the same data queue. Numeric, 3 positions; display-only.
Date	The date when the transaction was submitted to the data queue for processing. Numeric, 6 positions (in user date format); display-only.
Time	The time when the transaction was submitted to the data queue for processing. Note: The number of seconds might exceed 59 if the ASYNC job processed 60 or more records in a minute. Numeric, 6 position (HH:MM:SS format); display-only.
User	The user ID of the user associated with the order transaction. Alphanumeric, 10 positions; display-only.
B/A	A code indicating whether the record represents a before image or an after image for the transaction. After records are written for all transactions; before records are written for orders that have been maintained. Valid codes are: • B = The record represents the order information before the transaction was processed. • A = The record represents the order information after the transaction was processed. Alphanumeric, 1 position; display-only.
Processed	The status of the record. The record is either not processed, in process, in error, or processed. A status message displays for each step. Alphanumeric, 30 positions; display-only.
Ordr #	The order number of the record. (Order #): Numeric, 8 positions; display-only.
Ordr ship to	The order ship-to number of the record. (Ship to): Numeric, 3 positions, display-only.
Trn	A code identifying the job from which the transaction originated. Valid status codes are: • CF = Confirmation • DS = Drop Ship • EB = Evaluate Backorders • OE = Order Entry • OM = Order Maintenance • PM = Purchase Order Maintenance • PR = Receiving • RA = Return Authorization • US = Unspecified Alphanumeric, 2 positions, display-only.

Changing the Status of ORDR_ASYNC

Purpose: Select Change Status for the ORDR_ASYNC job at the Work with Background Jobs Screen to change its status.

Note: You cannot use the Change Status option to start or stop an individual ASYNC job. You must use the CNTL_ASYNC job to start or stop all the asynchronous jobs simultaneously.

Before you change the status of the async job: Before you change the status of the ORDR_ASYNC job, you should first determine if the async job is actively running; see Determining the Status of the Async Jobs.

How to change the job status: Select Change Status for the job at the Work with Background Jobs Screen.

A pop-up window displays from which you can select the status you want to assign to the async job. Select a status.

• If the async job is running: Select *ACTIVE if the async job is running and the status is currently *INACTIVE.

• If the async job is not running: Select *INACTIVE if the async job is not running and the status is currently *ACTIVE. This situation occurs if the ASYNC subsystem is brought down while the background ASYNC jobs are still active; the background ASYNC jobs have really ended, but the status indicates that they are still *ACTIVE.

See Troubleshooting the Async Jobs for more information on the steps you should take if you suspect the async jobs are not running correctly.

Updates During Background Processing

Purpose: The ORDR_ASYNC job updates system tables with order and demand information as orders are entered and maintained. As you enter or maintain orders, the system sends the records to the Order Processing data queue for processing. As soon as the Order Processing Data queue receives a record to process, the record is processed immediately, regardless of the status of the Order Processing ASYNC (ORDR_ASYNC) job. The ORDR_ASYNC job processes multiple orders simultaneously. While the Order Async job does not need to be active to process records, you should set the Order Async job to active to handle reorganization and cleanup of any transactions that did not process correctly.

Related system control value: The Update Demand for Order Maintenance Transactions (C72) system control value controls whether totals update as a result of order maintenance as well as order entry.

Order count and demand updates for retail pickup and delivery orders: If the originating location on a retail pickup or delivery order is Order Management System, the system does not increase the order count that is displayed on the About Application Screen or perform any demand updates for the order. Note: The system identifies the originating location as Order Management System if the request_system_cd in the fulfillment response message matches the system code in the OROB System (K50) system control value and the request_location_cd in the fulfillment response message matches the location in the Originating Location to Pass to OROB (M32) system control value. In this situation, the system prefaces the E-commerce order number in the Order Header Extended table with ORIG#: 9999-001, where ORIG#: indicates the order was created as a result of OROB fulfillment assignment, 9999 is the order number, and 001 is the ship to number. See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for more information.

Table	Updates
Cancel Reason/Offer (CNCNRO)	Date # canceled qty canceled units canceled Creates a record only if the cancel reason code is flagged not to reduce demand.
CC Authorization Backorder (CCATBO)	Create a record for authorization of a fully backordered order if the Preauthorize Backorders (D32) system control value is selected.
Correspondence History (MSCOHS)	Creates a record for each order confirmation email Outbound Email XML Message (CWEmailOut) generated if the Write Outbound Email to Email Repository (H99) system control value is selected. See the Suppress Order Confirmations for Orders in Error (K09) system control value for a discussion of when the ORDR_ASYNC background job generates order confirmations.
Customer Membership (OECSMP)	Create or deactivate customer loyalty memberships based on total order dollars or customer class. See Loyalty Memberships for an overview.
Customer Sold To (OECSSL)	Original and current mail type Original source Current source (if Update of Current Source Code in Customer File (D08) system control value is selected)
Customer Sold To Entity (OECSEP)	Last order date On order $ # orders LTD, $ orders LTD # cancels LTD, $ cancels LTD # soldouts LTD, $ soldouts LTD Last source Current mail type Original mail type Active since date Original source code Last source code Updated if the Track Customer History at Entity Level (F89) system control value is selected.
Customer Sold to Item Class (OECSIC)	# orders LTD, $ ordered LTD # units ordered LTD # units canceled LTD, $ canceled LTD # units soldout LTD, $ soldout LTD Last order date
Customer Sold To Item Class Entity (OEICEP)	Creates records and updates: # orders (not units) # orders LTD, $ orders LTD # cancels LTD, $ cancels LTD # soldouts LTD, $ soldouts LTD Last order date
Customer Sold To Order History (CSTOOH)	On order $ # orders LTD, $ orders LTD # soldouts LTD, $ soldouts LTD # canceled LTD, $ canceled LTD Last CC# Last expiration date Active since date Last order date Last order type Pay type Current source code Last order amount
Flash Report (FLFLSH)	See Reviewing Operations Control Summary (FLSH) for information on order totals tracked.
Item/Sku/Offer (FCISOF)	Start and end dates Quantity ordered, $ ordered
Offer (MSOFFR)	Date of first order
Order Control Summary (MSORSU)	# orders entered, $ orders entered, quantity ordered # orders cancelled, $ orders cancelled, quantity cancelled # orders soldout/closed, $ orders soldout, quantity soldout Note: The Billing Async updates the orders shipped, orders exchanged, and invoices credited fields. The batch order control job updates the operation and merchandising fields in the Order Control Summary table; see Reviewing Operations Control Summary (FLSH).
Order Type/ User (OEOTYU)	# Orders TD, LTD $ Value - TD, LTD # Receipts TD, LTD # Lines TD, LTD
Order/Billing History (OEBHST)	# orders, $ order total, qty ordered # soldout, $ soldout total, qty soldout # canceled, $ canceled, qty canceled
Price override reason (OEPROR)	# of overrides Total discount
SKU (INSKU)	Date of first order Date of last order
SKU Price History (SKUPHT)	# orders (actually updated with the total ordered quantity) $ orders
Soldout Notifications (SONTFY)	Creates records
Source Code (MSSRC)	$ ordered, soldout, canceled # of orders, soldouts, cancels Date of first order Date of last order Response percent
Tickler	Records created based on related configuration. See Workflow Management Overview and Setup for background.
Note: • Entity-level updates take place only if the Track Customer History at Entity Level (F89) system control value is selected. • Order maintenance activity updates demand only if the Update Demand for Order Maintenance Transactions (C72) system control value is selected.