Working with the OTHR_ASYNC Job

The Other ASYNC function updates the system files with purchase order information when purchase orders are entered, maintained, or received.

When purchase orders are entered, maintained, or received, records are sent to the Other data queue for processing. If the Other ASYNC (OTHR_ASYNC) function is active, the records will be processed immediately. If the function is not active when the records are sent, they will be processed as soon as the OTHR_ASYNC function becomes active again. All records are processed in the sequence in which they were sent to the data queue.

If any errors exist, processing for that record stops at the error point. The system begins processing the next record in sequence. The records in error are listed on the P/O Background Job Error Listing, which is printed when the ASYNC jobs are ended. OTHR_ASYNC will continue processing the record when the error has been corrected. You should correct any errors that exist as soon as possible so that your system files are updated properly. SeeWorking with OTHR_ASYNC Status Messages.

The status of each record in the data queue can be viewed at any point by displaying the Display PO Header Data Queue Screen.

In this topic:

• Display Asynchronous Job Screen (Displaying the Other ASYNC Job)

• Display PO Header Data Queue Screen

• Working with OTHR_ASYNC Status Messages

• P/O Background Job Error Listing

• Updates During Background Processing.

Display Asynchronous Job Screen (Displaying the Other ASYNC Job)

Purpose: Use this screen to display the job attributes for each background ASYNC job, including the OTHR_ASYNC job. This screen displays descriptive information about the ASYNC job.

How to display this screen: Enter 5 next to the OTHR_ASYNC job at the Work with Background Jobs Screen.

MSR0240 DISPLAY Display Asynchronous Job 4/15/94 22:13:15 CommercialWare   Data queue name . . . : OTHERDATAQ Job name . . . . . . : OTHR_ASYNC   Description . . . . . : Other Data Queue   Data queue length . . : 24 Library . . . . . . . : CWM10QDTA Wait time . . . . . . : -1 0=No wait, -1=Wait forever   Start . . . . . . . . : 4/15/94 8:01:44 JEANNE_N End . . . . . . . . . : 4/14/94 22:29:15 BRIAN_M   Controlling job ? . . : N (N=No, Y=Yes) System Option ? . . . : Y (N=No, Y=Yes)   Status . . . . . . . : A *ACTIVE   F3=Exit F10=Actions F12=Cancel

Field	Description
Data queue name	The name of the data queue where transactions records are sent for processing by this ASYNC ob. The name of the OTHR_ASYNC data queue is OTHERDATAQ. 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.
Data queue length	The length of the data queue where transactions records for this ASYNC job are processed. The length of the OTHERDATAQ is 24 positions. Alphanumeric, 3 positions; display-only.
Library	The library list where the ASYNC job is defined. Alphanumeric, 10 positions; display-only.
Wait time	The length of time the function will wait for records to be sent for processing before it times out. Valid values are: 0 - No wait. The function ends when there are no records to process. 1 - Wait forever. The function will not time out when there are no records to process. Numeric, 1 position; 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 function controls other ASYNC functions. The controlling ASYNC function starts and ends other ASYNC functions. Valid values are: Y - This is a controlling ASYNC function. N - This is not a controlling ASYNC function. The CNTL_ASYNC job is the only controlling ASYNC job. Alphanumeric, 1 position; display-only.
System Option ?	A flag indicating whether this function is a system function that cannot be deleted by the user. Valid values are: Y - This function cannot be deleted by the user. N - This function can be deleted by the user. Alphanumeric, 1 position; display-only.
Status	The current status of the function. Valid status codes are: A -*ACTIVE I - *INACTIVE E - *ENDPEND J - *JOBQ R - *REORG Alphanumeric, 1 position; display-only

Display PO Header Data Queue Screen

Purpose: This screen displays the records that have been sent to the data queue for processing since the last time the ASYNC function was ended. Records are sent to the data queue when the inventory level for an item is increased.

The status of each record, which indicates if the record has been processed or if any errors exist, displays.

How to display this screen: Enter 10 next to the OTHR_ASYNC job on the Display Asynchronous Job Screen (Displaying the Other ASYNC Job).

MSR0511 DISPLAY Display PO Header Data Queue 4/06/94 11:09:18 Cmp Date Time User B/A Processed PO # Trans ___ _____ ______ ________ _ _____ __ 7 1/18/94 11:36:52 HERB_J 1 Process has Begun 318 PR 7 1/19/94 10:55:30 HERB_J 1 Process has Begun 317 PR 409 2/16/94 12:45:35 LEE_H 1 Process has Begun 13 PE 900 3/21/94 9:30:22 KAREN_M 1 Process has Begun 123 PE 900 3/21/94 9:35:00 KAREN_M 1 Process has Begun 123 PR F3=Exit F10=Actions F12=Cancel

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 on which the transaction was submitted to the data queue for processing. Numeric, 6 positions; display-only.
Time	The time at which the transaction was submitted to the data queue for processing. Numeric, 6 positions; display-only.
User	The User ID of the person who entered the 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 order maintenance transactions. Valid codes are: 0 - The record represents the order information before the transaction was processed. 1 - 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.
PO#	The number of the purchase order for which the record is being processed. Numeric, 7 positions; display-only.
Trans	A code that identifies the function where the transaction originated. Valid status codes are: CF - Confirmation DS - Drop Ship EB - Evaluate Backorders OE - Order Entry OM - Order Maintenance PE - Purchase Order Entry PM - Purchase Order Maintenance PR - Receiving RA - Return Authorization US - Unspecified Alphanumeric, 2 positions, display-only.

Changing the Status of OTHR_ASYNC

Purpose: You can change the status of an ASYNC job if it has ended, but the status indicates that it is still 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.

If the status is *ACTIVE, the ASYNC jobs cannot be started because the system considers them to be active. To restart the background ASYNC jobs you must change the status of each job to *INACTIVE manually.

Note: The Change Status function should not be used to start or stop an individual ASYNC job. Use the CNTL_ASYNC job to start or stop all of the ASYNC jobs simultaneously.

How to change the ASYNC jobs status:

1. Enter 11 next to the OTHR_ASYNC job at the Work with Background Jobs Screen.

2. A pop-up window displays from which you can select the status you want to assign to the background job. Enter 1.

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

 

Note: The status of each background job must be changed separately. Changing the status of the CNTL_ASYNC job will not change the status of the individual background ASYNC jobs.

Working with OTHR_ASYNC Status Messages

Purpose: The status of each data queue record can be viewed by displaying the data queue. If an error exists, the message will print on the P/O Background Jobs Error Listing that is printed when the ASYNC jobs are ended. The error must be corrected before the transaction can be fully processed.

OTHR_ASYNC status messages: This table lists the status messages that you may see when displaying the PO Header Data Queue, or when reviewing the P/O Background Job Error Listing. The Error Reason/Action Required section of the table below is incomplete as of this writing.

Message	Message ID	Error Reason/Action Required
Processing has begun		None.
All updates complete		None. The record was fully processed.
Error updating buyers	OA21759
Error updating Item/Warehouse	OA21760
Error updating PO Dtl audit	OA21915
Error updating PO Hdr audit	OA21916
Error creating PO layering	OA21897
Error changing PO layering	OA21920
Error creating PO layering	OA21918
Error deleting PO layering	OA21919
Error updating SKU Offer	OA21758
Error updating threshold value	OA22968
Error updating vendor	OA21732
Error updating vendor history	OA21733
Error updating vendor items	OA21766

P/O Background Job Error Listing

Purpose: This report prints when the background ASYNC jobs are ended. The report lists the records that could not be processed and the reason for the error. The record will be processed when the error is corrected.

See Working with OTHR_ASYNC Status Messages for a complete description of the error messages you may encounter and the steps necessary to correct the error.

CWDirect P/O Background Job Error Listing KAREN_M 4/23/94 15:09:33 Page 1 Order # Ship to Order date User Update area Error ID 5956 0 Detail updates complete OA21947

• Order #: The order number for which the error occurred.

• Ship to: The ship-to suffix of the order for which the error occurred.

• Order date: The date on which the order was entered.

• User: The User ID of the operator who entered the order.

• Update area: The message describing the reason for the error. See Working with OTHR_ASYNC Status Messages.

• Error ID: The ID number assigned to the error. See Working with OTHR_ASYNC Status Messages.

Updates During Background Processing

Purpose: The system performs the following field and file updates during the OTHR_ASYNC procedure:

Function	Field
Update the SKU/Offer file
---	• SKU CWI work field • SKU on order for PO Threshold values include: • Number and dollar value for Held POs • Number and dollar value for Units of Suspense Inventory • Number and dollar value for PO Receipts in Suspense
Update the Item/Warehouse file
---	On order quantity
Update PO Layering file Note: The system does not update the PO Layering file for purchase order lines that are in a Held status.
PO Entry PO Approval	Creates the record
PO Maintenance + PO Receipts	Open quantity
PO Receipts	Status Note: If you receive inventory into a pending putaway warehouse, the system keeps the PO layering record in an open status until the inventory is moved out of the pending putaway warehouse. See Pending Putaway Overview.
---	Warehouse
---	Due date
Update the Vendor/Item file
PO Receipts	Shipments - LTD
---	Elapsed days - LTD
---	Late days - LTD
---	Number of late shipments
---	Defects - LTD
---	Underships
---	Overships
---	Units received - LTD
PO Entry + PO Maintenance	Dollar value purchased - LTD
---	Units purchased - LTD
Update Vendor file
---	Dollar value cancelled
---	Dollar value held
---	Dollar value open
---	Number of POs - LTD
---	Number of open POs
Updates Vendor History file
---	Dollar value purchase orders
---	Number of purchase orders
Update the Buyer file
---	Dollar value POs - LTD
---	Number of purchase orders - LTD
Update Vendor Extended file
---	Open A/P
---	Dollar value on order
Update the EC Item Availability File Note: If the E-Commerce Item Availability Download Method (I10) system control value is set to FILE or BOTH, the OTHR_ASYNC job updates this file when you create or maintain a purchase order that includes an item that has been downloaded to the web storefront if its current available quantity is zero or less. See E-Commerce Item Availability Processing for an overview.
PO Entry	Creates the record or update Date Expected
PO Maintenance