1. Technical Guide
  2. Order Entry
  3. Working with Error Order Batches

Working with Error Order Batches

Topics in this part:

Introducing Order Batches

You can work with the following types of order batches.

Batch Orders and Web Orders

Web orders that fail the order edit: If an order received through the Generic Order Interface (Order API) does not pass the order edit, or if it does not include payment information, it is retained in the Default Batch for E-Commerce Orders in Error (G41). However:

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

To correct web orders in error: You can use batch orders to review, work with, and approve web orders that failed the order edit. Select Edit/Accept on the Work with Error Orders Batches Screen to edit the order batch. The system runs the same order edit that is performed when you receive orders through the Generic Order Interface (Order API). When an order passes the order edit, the system removes the batch number from the order, updates its status to open, performs pick slip preparation, and makes it available in regular order maintenance and inquiry. If an order fails the order edit, the system includes the order on the Print Remote Order Errors Report and retains the order in an error status in the order batch.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Batch Orders and Membership Orders

Membership orders that fail the order edit: If a membership order generated through Generating Membership Orders (EGMO) does not pass the order edit, the order remains in a suspended status and is placed in a generated order batch, using the next number in the Order Batch (A01) number assignment wheel.

To correct membership orders in error: You can use batch orders to review, work with, and approve membership orders that failed the order edit. Select Edit/Accept on the Work with Error Orders Batches Screen to edit the order batch. The system runs the same order edit that is performed when you receive orders through the Generic Order Interface (Order API). When an order passes the order edit, the system removes the batch number from the order, updates its status to open, performs pick slip preparation, and makes it available in regular order maintenance and inquiry. If an order fails the order edit, the system includes the order on the Print Remote Order Errors Report and retains the order in an error status in the order batch.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Working with an Order Batch

Order batching allows you to review, correct, and accept orders received from an external system that are in error.

Web orders: If an order received through the Generic Order Interface (Order API) does not pass the order edit, or if it does not include payment information, the system places the order in an order batch; see Batch Orders and Web Orders. Select Edit/Accept on the Work with Error Orders Batches Screen to edit and approve the batch. Even if the batch is error-free, you will still need to approve it manually.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

In this topic:

Default Values for Orders Screen (Selecting Error Order Batches)

Purpose: Use this screen to advance to the Work with Error Order Batches screen.

About this screen: Each field on this screen is described in Setting Defaults in Order Entry; however, you must select the Error order batches field to select to work with orders in error. Entries to the other fields on this screen are optional.

Work with Error Orders Batches Screen

Purpose: This screen displays the order batches in the system that contain orders in error. The value in the Assigned to user field controls which batches display. If blank, this screen lists all the order batches in the system.

Threshold: The Suspended Batches threshold value controls the length of time in which a suspended order batch remains on the system. Any order batches beyond this threshold are deleted automatically during a periodic process.

User ID: This screen also displays the user ID of the person currently working with an order batch. Only one person can work on a batch.

Screen use: Use this screen to:

  • Work with an order batch. Orders in the batch remain in a suspended status until you accept the batch. For each order batch, you can:
  • Review, work with, and edit orders received through the Generic Order Interface (Order API) that did not pass the order edit or do not include payment information; see Batch Orders and Web Orders.

    For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

  • You can select Edit/Accept to edit the order batch. The system runs the same order edit that is performed when you receive orders through the Generic Order Interface (Order API).

    For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

    When an order passes the order edit, the system removes the batch number from the order, updates its status to open, performs pick slip preparation, and makes it available in regular order maintenance and inquiry. If an order fails the order edit, the system includes the order on the Print Remote Order Errors Report and retains the order in an error status in the order batch.

How to display this screen:

  1. Select Error order batches on the Default Values for Orders Screen (Selecting Error Order Batches).
  2. Select OK to display the Work with Error Order Batches screen.
Field Description

Assigned to user

The user ID of the person who created the order batch.

All order batches display if this field is blank.

The system assigns your default user to orders received through the Generic Order Interface (Order API) that contain errors.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Alphanumeric, 10 positions; optional, assigned by the system.

Batch suspended

Indicates whether the screen lists only suspended batches or all batches. The system suspends a batch if the keyed cash and/or order controls do not match the actual cash and/or order controls.

Valid values include:

  • Selected = (default): Display only suspended (unbalanced) batches.
  • Unselected = Display balanced and unbalanced batches.

The system default is to display only the unbalanced batches because these batches need to be worked on. You must enter (or continue to enter) orders for the batch, adjust the cash or order controls for the batch or correct the orders in the batch to bring the batch into balance. If you select this field, every batch currently on the system is listed.

Note:

A threshold value controls the length of time in which an order batch remains on the system. After this period, the system deletes order batches automatically during a periodic process.

Batch #

The number assigned by the system to a group of orders within an order batch.

Web orders: If an order received through the Generic Order Interface (Order API) does not pass the order edit, or if it does not include payment information, it is retained in the Default Batch for E-Commerce Orders in Error (G41). However:

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

Numeric, 5 positions; display-only, assigned by the system.

Date

The date on which the order batch was created.

Numeric, 6 positions (in user date format); display-only, assigned by the system.

# orders

The number of individual orders assigned to the order batch, regardless of order status and including orders that have been processed and no longer display in the batch. The system includes all orders whose Batch # field in the Order Header table matches the order batch number.

Numeric, 5 positions; display-only.

$ value

The total dollar amount of orders entered for this batch during Order Entry. The system updates this field as you enter and accept each order in the batch.

Numeric, 13 positions with a 2-place decimal.

In use by

The user ID of the person currently working with the batch. Only one person at a time can access a batch.

If the batch is locked by another user because, for example, the user’s session ended unexpectedly, you can use Unlocking a Stranded Order or Batch (MULO) to unlock the batch.

Alphanumeric, 10 positions; display-only, updated by the system.

Screen Option Procedure

Review, delete or enter orders for the batch

Select Work with Orders for a batch to display the Work with Orders within a Batch Screen.

Reject and remove the entire batch

Select Reject for a batch to reject and delete the batch. Select OK at the Confirm Reject Window to perform this action. See Accepting or Rejecting the Order Batch.

Run the order edit batch program and print the Print Remote Order Errors report for an order batch

Select Edit/Accept for an order batch to run the order batch edit and print the Print Remote Order Errors Report.

See Accepting or Rejecting the Order Batch for the updates that occur.

Work with Orders within a Batch Screen

Purpose: Use this option to:

  • Review the orders assigned to the batch
  • Delete an order from the batch
  • Work with an order in the batch
  • Review the order totals for an order in the batch
  • Add an order to the batch

How to display this screen: Select Work with Orders for an order batch at the Work with Error Orders Batches Screen.

Field Description

Batch#

The number assigned by the system to a group of orders within an order batch.

Numeric, 5 positions; display-only, assigned by the system.

Sts

Order status

The status of the order, as assigned by the system.

Batched orders may have a Suspended, Open or Quote status.

Suspended/Error

Batched orders are suspended in an error status until the errors are corrected. When you correct the errors on an order, the status of the order in the batch changes to Open.

Open

Pick slips may be printed for orders in an open status. Additionally, these orders are available for maintenance and inquiry.

Quote

If the Quote field for the order type on the order is selected, the system considers the order a pre-order quote and not a standard order. Quotes in a batch are entered in a Quote status and remain in a Quote status until you convert the quote to an order in Quote Maintenance. See Entering Pre-Order Quotes for an overview.

Other status codes are: Held, Cancelled or Closed.

Alphanumeric, display-only, updated by the system.

Order #

A unique number assigned by the system to identify an order.

Numeric, 8 positions; display-only.

Ord date

The date the order was created.

Numeric, 6 positions (in user date format); display-only.

Sold to

The last name, first name and initial or the company name of the customer who placed the order.

Alphanumeric, 41 positions; display-only.

#Rcp

The number of recipients for this order, which indicates the number of different shipping addresses associated with the order number.

The system assigns a sequential ship-to number to every order, even if the shipping address and the sold-to address are the same.

Numeric, 3 positions; display-only.

Total paid

The dollar amount you received from the customer on all prepaid (cash/check payments) for the order.

Numeric, 20 positions with a 2-place decimal; display-only.

Pmt

Indicates whether a payment method exists on the order.

  • Y = A payment method exists on the order.
  • N = A payment method does not exist on the order.
Alphanumeric, 1 position; display-only.

Screen Option Procedure

Delete an order from the batch

Select Delete for the order to delete it. The system writes a record in the Deleted Order Table for the order.

Go into an order in the batch to change or verify order information before you accept the entire batch

Select Ship To’s for an order listed for the batch to advance to Order Entry (in “review” mode). You must accept or reject the order when you are through.

Review the order totals for the order

Select Display order totals for the order to display the Display Order Totals Window.

Enter another order for the batch

Select Create. See Performing Batch Order Entry for more information about the batching process during Order Entry. See also Entering Orders for details on how to enter an order.

Performing Batch Order Entry

Purpose: This topic describes the differences you see during Order Entry when you work with an order in an order batch. This topic identifies the screen differences on each major Order Entry screen during Batch Order Entry. The screens display this way only if you select the Error order batches field at the Default Values for Orders Screen (Selecting Error Order Batches).

Only the fields and command keys that apply to Batch Order Entry are described in this topic.

Refer to Entering Orders for field-by-field descriptions and instructions for performing Order Entry. Whether entering batched or unbatched orders, this process remains the same.

When you complete the Batch Order Entry process, which means that you update and accept each order in the batch, you must accept the entire batch to release these orders on the system. See Accepting or Rejecting the Order Batch if you have completed the orders in the batch and wish to process or delete the batch.

In this topic:

Select Customer Sold To For Order Screen

Purpose: Use this screen to specify the customer for the order in the order batch, by:

  • Entering the customer number, if you know it, or
  • Entering information in any of the scan fields to obtain a list of customers who closely match this information, or
  • Selecting Create to enter an order for a new customer.

How to display this screen: Select Create at the Work with Orders within a Batch Screen.

Note:

If the ORCE Customer Integration (L37) system control value is set to INTERACT, you advance instead to the Customer Scan Screen.

About this screen: This screen is described fully in Selecting Customers in Order Entry; however, in batch order entry the Batch # field is listed at the top of the screen to indicate that you are entering orders for a batch.

Field Description

Batch #

The batch number for which you are entering the current order. The batch number is a number assigned by the system to a group of orders.

Numeric, 5 positions; display-only, assigned by the system.

Screen Option Procedure

Review or update defaults for several Order Entry fields

Select Change Defaults to display the Change Defaults pop-up window. See Setting Defaults in Order Entry.

Enter an order for a new customer

Select Create to advance to the Work with Order screen. See Entering Orders.

Review the orders already entered in the batch

Select Maintain to display the Work with Orders within a Batch Screen.

Work with Order Screen (Batch Order Entry)

Purpose: The following screens identify the differences in the Order Entry screens when batching orders. See Entering Orders for a complete discussion and a sample of these screens.

Field Description

Batch#

The batch number for which you are entering the current order. The batch number is a number assigned by the system to a group of orders.

Numeric, 5 positions; display-only, assigned by the system.

Completing Order Entry

Purpose: You return to the Work with Orders within a Batch Screen when you accept or reject each order in the batch.

Select one of the following options on the Work with Error Orders Batches Screen when you finish working with the orders in the batch:

  • Select Edit/Accept to accept all the orders in the batch.
  • Select Reject to reject and delete the entire batch.

See Accepting or Rejecting the Order Batch if you are through entering the entire batch.

Accepting or Rejecting the Order Batch

Purpose: This topic describes the processes that the system performs when you select Edit/Accept for a batch to accept the entire batch or you select Reject Batch for a batch to reject and delete the batch.

In this topic:

When to accept or reject: You accept or reject a batch of orders when you finish entering the individual orders in a batch; see Performing Batch Order Entry.

Rejecting the Batch

You may want to reject an order batch if the order batch contains orders that you wish to delete.

Select Reject Batch to reject and delete the batch. You advance to the Confirm Reject Window. Select OK to reject the batch.

The system prints the Rejected Batch Listing, deletes the orders from the system, and deletes the batch itself.

Deleted Order table: The system writes a record in the Deleted Order Table for each purged order.

If the batch includes a retail pickup or delivery order from Order Orchestration, the BROKER process sends a status update rejecting the order; also, it deletes the related Order Orchestration and Order Orchestration History records. See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for an overview.

Accepting the Batch

Select Edit/Accept on the Work with Error Orders Batches Screen to edit the order batch. The system runs the same order edit that is performed when you receive orders through the Generic Order Interface (Order API) and includes any orders in error on the Print Remote Order Errors Report.

For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1).

When an order passes the order edit, the system removes the batch number from the order, updates its status to open, performs pick slip preparation, and makes it available in regular order maintenance and inquiry.

If an order fails the order edit, the system includes the order on the Print Remote Order Errors Report and retains the order in an error status in the order batch. Select Work with Orders for the order batch to advance to the Work with Error Orders Batches Screen where you can review and correct the errors on each order. When you have finished updating each order, select Edit/Accept again to edit and accept the remaining orders in the order batch.

Performing Online Credit Card Authorizations

Online credit card authorization allows you to send and receive electronically the information required to authorize a credit card at the time the order is placed instead of at the time the pick slip is generated for the order.

The system performs online authorization when you accept an order batch after determining if any order in the batch should go on hold.

If an order in the batch is eligible to receive a credit card authorization during batch order entry, the system sends the amount requiring authorization to the authorization service and waits for a response.

There are 3 types of responses you can receive from the authorization service.

  • R = an authorization response was received, such as declined or approved.
  • T = the program timed out before an authorization response was received.
  • U = an undefined response was received.

Additionally, if an authorization response is received, the authorization service sends back an authorization response code, AVS response code (if performing address verification), card security response code (if performing credit card security identification), authorization code, and date.

If a hold reason code has been defined for the vendor response, AVS response, or CID response received, the system places the order on hold.

Credit cards requiring authorizations less than $1.00: If the credit card amount to authorize is less than $1.00 and you have defined an authorization number in the Authorization Number for Authorizations Under $1.00 (I08) system control value, the system does not send the credit card to the service bureau for authorization and instead assigns the authorization number from the system control value to the credit card. If an authorization number is not defined in this system control value, the system sends the credit card to the service bureau for authorization, regardless of the amount that requires authorization.

Performing Online Verification Only: If the Online Auth Verification Only (I96) system control value is selected, the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.

For more information: See Performing Online Credit Card Authorizations for an overview of the online credit card authorization process and the required setup.

Accepting an Order in the Batch

Purpose: The system performs updates to a number of tables to reflect the addition of a new order to the batch. The updates occur:

  • Immediately, as you enter an order to the batch.
  • When you accept the order or accept the order and add a recipient order.
  • During a background processing job (ORDR_ASYNC).

Immediate Updates

The system updates the SKU and Item/Warehouse tables immediately as you enter a new order to the batch.

Process Table Field

Update the Item/Warehouse record for each item ordered

Item/

Warehouse

On hand qty (if express-billed order)

ITW B/O qty

Reserve qty

S/H reserve qty

ITW On order qty

Update the SKU record

SKU

SKU Orders avail pick gen

SKU Open qty

SKU On hold qty

Additionally, the system updates the following tables as you enter a new order:

  • Customer Sold To
  • Customer Sold To Extended Address
  • Customer Sold To Phone #
  • Customer Bill To
  • Customer Bill To Extended Address
  • Customer Bill To Phone #
  • Customer Ship To
  • Customer Ship To Extended
  • Customer Ship To Phone #
  • Customer Action Notes
  • Order Additional Charges
  • Order Detail
  • Order Detail Data Queue
  • Order Free Gift
  • Order Header
  • Order I/T Lines
  • Order Information
  • Order Line History
  • Order Line Messages
  • Order Messages
  • Order Payment Method
  • Order Pending Checks
  • Order Selected Item
  • Order Ship To
  • Order Ship To Address
  • Order Ship To Data Queue
  • Order Special Handling
  • Order Transaction History
  • Reserved Order Lines

Updates at Accept

The system performs these table updates when you accept each order in the batch.

Process Table Field

Reprice order if the Pricing method field in the Source Code record is set to a Reg Plus Reprice

Order Detail

ODT Price

Evaluate free gift eligibility, based on the source code or offer; create order detail records for free gift, if applicable

Order Detail

All fields

Calculate the $ Discount, based on Source or Offer; add a record to the Order Additional Charges table

Order Additional Charges

All fields

Sends balance of updates to background processing job (O/P ASYNC)

    

Order transaction history: When you accept an order that is part of an order batch, the system writes an order transaction history message with a Type of Maintenance indicating the user that accepted the order. The system writes an order transaction history message each time a user accepts the order so that you can track the users that changed the order in the batch prior to accepting the order batch. You can review order transaction history messages on the Display Order History Screen.

An example of the order transaction history message the system creates when a user accepts an order that is part of an order batch is displayed below. The system includes an amount regardless of whether the change updated the order total.

Date Type Transaction Note Amount User

8/14/14

MAINT

Order changed while in unaccepted batch

45.00

SFLYE

Note:

The system does not create an order transaction history message if a user rejects out of an order that is part of an order batch. If a user accepts an order in order maintenance that is no longer part of an order batch, the system writes an order transaction history message indicating: Order was maintained.

Additional updates when you accept the entire batch: The system performs these updates to the individual orders in the batch only when you accept the entire batch (see Accepting the Entire Batch):

  • Perform the credit check processes
  • Evaluate for refund eligibility
  • Update the Flash Report
  • Evaluate and update the order status based on the detail line status, if necessary
  • Update the Online Authorization, Authorization History, and Void Authorization tables if you performed online credit card authorization
  • Applies pick slip preparation to each eligible order; see Applying Pick Slip Preparation to an Order

Updates During Background Processing

The system performs the balance of the field and table updates during a background processing job (O/P ASYNC) that runs after you accept each order in the batch.

Process Table Field

Update the Price Override Reason table, based on price overrides at detail line level

Price Override Reason

POR # of overrides

POR Total discount

Update the SKU record

SKU

Date of first order

Date of last order

Update the SKU/Price History record

SKU Price History

SPH # orders

SPH $ orders

Update the SKU/Offer Page record for offer page analyses

SKU/Offer Page

Dollars ordered CTD

Dollars ordered WTD

Dollars sold out CTD

Dollars sold out WTD

Units ordered CTD

Units ordered WTD

Units sold out CTD

Units sold out WTD

SOP Dollars upsell CTD

SOP Dollars upsell WTD

SOP Units upsell CTD

SOP Units upsell WTD

SOP Units lost CTD

SOP Units lost WTD

Update the Order/Billing History record

Order/Billing History

OBH # Orders

OBH $ Order total

OBH Qty ordered

OBH # Orders sold out

OBH $ Sold out total

OBH Qty sold out

Add a record to the Soldout Notifications table to generate soldout notifications for sold-out items

Soldout Notifications

  

Update the sold-to customer record

Customer Sold To Order History

COH On order $

COH # Orders LTD

COH # Sold outs LTD

COH $ Orders LTD

COH $ Sold outs LTD

COH Last Card Number

COH Active since date

COH Last order date

OTY Order type

PAY Pay type

SRC Source code

Update the ship-to customer record

Customer Ship To Order History

HOH On order $

HOH # Orders LTD

HOH # Sold outs LTD

HOH $ Orders LTD

HOH $ Sold outs LTD

HOH Active since date

HOH Last order date

OTY Order type

PAY Pay Type

SRC Source code

Update operator statistics, based on order type

Order Type/ User

OTU # Orders TD

OTU # Orders LTD

OTU $ Value - TD

OTU $ Value - LTD

OTU # Receipts TD

OTU # Recips LTD

OTU # Lines TD

OTU # Lines LTD

Update operator statistics by accounting period, based on order type

Order Type/ User History

OUH # Orders

OUH $ Value

OUH # Recips

OUH # Lines

Update the source code record with the accumulated order totals

Source

$ Orders

$ Soldouts

# of Orders

# of Soldouts

Accepting the Entire Batch

Purpose: The system updates several tables:

  • When you accept the entire batch
  • During a background processing job that runs automatically after you accept a batch or an order in the batch

See Working with the ORDR_ASYNC Job for more information on the background jobs.

Updates at Accept

The system performs these table updates when you accept the batch. See Performing the Release and Introducing Order Hold Reason Codes for more information about the credit check process that evaluates customers, orders, and payment types and performs record updates if any condition on the order fails a credit check.

Process Table Field

Credit check: sold-to customer unconditional hold

Order Header

SKU

OHD OHR Sys hold reason

SKU On hold qty

Credit check: sold-to customer fraud

Order Header

Order Header

SKU

OHD Order status

OHD OHR Sys hold reason

SKU On hold qty

Credit check: sold-to customer zip code fraud

Order Header

Order Header

SKU

OHD Order status

OHD OHR Sys hold reason

SKU On hold qty

Credit check: bill-to customer unconditional hold

Order Header

SKU

OHD OHR Sys hold reason

SKU On hold qty

Credit check: bill-to customer zip code fraud

Order Header

SKU

OHD OHR Sys hold reason

SKU On hold qty

Credit check: ship-to/ sold-to customer fraud

Order Ship To

Order Header

Order Ship To

SKU

OST OHR Hold reason

OHD OHR Sys hold reason

OST Order status

SKU On hold qty

Credit check: ship-to/ sold-to customer zip code fraud

Order Ship To

Order Header

SKU

OST Order status

OHD OHR Sys hold reason

SKU On hold qty

Credit check: ship-to customer fraud

Order Ship To

Order Header

SKU

OST Order status

OHD OHR Sys hold reason

SKU On hold qty

Credit check: ship-to customer zip code fraud

Order Ship To

Order Header

SKU

OST Order status

OHD OHR Sys hold reason

SKU On hold qty

Credit check: dollar hold

Order Header

SKU

OHD OHR Sys hold reason

SKU On hold qty

Credit check: time hold

Pay Type

Order Header

SKU

OHR Hold reason

OHD OHR Sys hold reason

SKU On hold qty

Credit check: check fraud

Pay Type

Order Header

SKU

OHR Hold reason

OHD OHR Sys hold reason

SKU On hold qty

Credit check: balance due exceeds the $ amount

Order Header

SKU

OHD OHR Sys hold reason

SKU On hold qty

Credit check: pay types

Order Header

SKU

OHD OHR Sys hold reason

SKU On hold qty

Credit check: credit card fraud

Pay Type

Order Header

SKU

OHR Hold reason

OHD OHR Sys hold reason

SKU On hold qty

Credit check: credit card authorization pending status

Pay Type

Order Header

SKU

OHR Hold reason

OHD OHR Sys hold reason

SKU On hold qty

Credit check: outstanding balance due

Pay Type

Order Header

SKU

OHR Hold reason

OHD OHR Sys hold reason

SKU On hold qty

Credit check: email address fraud

Order Header

Order Ship To

SKU

OHR Hold reason

OHD OHR Sys hold reason

SKU On hold qty

Evaluate order for refunds; create refund records for overpayments or balance dues

Refunds

All fields

Update the Operations Control Summary (Flash) Report

Order Control Summary

# Orders entered

$ Orders entered

Quantity ordered

# Orders soldout/clsd

$ Orders soldout

Quantity soldout

$ Open backordered

Quantity backordered

$ Held backordered

Qty held backordered

Update order header and order ship-to status to match status of detail lines if all lines canceled.

Order Header

Order Ship To

OHD Order status

OST Order status

Approved online credit card authorization: Create an online authorization record, authorization history record, and void authorization record if you performed online credit card authorization for a credit card payment method on the order

Online Authorization

Authorization History

Void Authorization

Online Authorization:

company

order #

seq #

auth amount

vendor response 1(auth response)

vendor response 2 (CID response)

auth #

auth date

status: *UPDT

trans seq #

card number

terminal #

AVS result

card security value

ASV auth service

Authorization History:

All fields except Amount Deposited

Void Authorization:

All fields

Declined online credit card authorization: Create an online authorization record and authorization history record if you performed online credit card authorization for a credit card payment method on the order

Online Authorization

Authorization History

Online Authorization:

company

order #

seq #

auth amount

vendor response

status: *SENT

trans seq #

card number

terminal #

ASV auth service

Authorization History:

All fields except Amount Deposited, Auth Date, and Auth #

Undefined online credit card authorization response: Create an online authorization record and authorization history record if you performed online credit card authorization for a credit card payment method on the order

Online Authorization

Authorization History

Online Authorization:

company

order #

seq #

auth amount

vendor response

auth #

auth date

status: *UPDT

trans seq #

card number

terminal #

ASV auth service

Authorization History:

All fields except Amount Deposited

Online credit card authorization communication failure: Create an online authorization record and authorization history record if you performed online credit card authorization for a credit card payment method on the order

Online Authorization

Authorization History

Online Authorization:

company

order #

seq #

auth amount

auth #

auth date

status: *UPDT

trans seq #

card number

terminal #

ASV auth service

Authorization History:

All fields except Amount Deposited, Auth Date, Auth #, and Vendor Response

Clear order batch number: If the order is a membership order, an e-commerce order or a retail order, the system clears the order batch number upon acceptance. Determined by:

Order Header

OBA Batch #

For a retail pickup or delivery order, sends a status update to Order Orchestration to change the status in Order Orchestration to Accepted. Also, change the status of the Order Orchestration record to In process.

See Retail Pickup (including Ship-for-Pickup) or Delivery Orders

Order Orchestration

Status

Create pre-generated picks

Pick Control Header

Pick Control Detail

Pick Control Label

Pick Stored Value Card

See Applying Pick Slip Preparation to an Order for the updates that are performed

Updates During Background Processing

The system performs the balance of the field and table updates during a background processing job (ORDR_ASYNC) that runs after you accept the entire batch.

Process Table Field

Update the Price Override Reason table, based on price overrides at detail line level

Price Override Reason

POR # of overrides

POR Total discount

Update the SKU record

SKU

Date of first order

Date of last order

Update the SKU/Price History record

SKU Price History

SPH # orders

SPH $ orders

Update the SKU/Offer Page record for offer page analyses

SKU/Offer Page

Dollars ordered CTD

Dollars ordered WTD

Dollars sold out CTD

Dollars sold out WTD

Units ordered CTD

Units ordered WTD

Units sold out CTD

Units sold out WTD

SOP Dollars upsell CTD

SOP Dollars upsell WTD

SOP Units upsell CTD

SOP Units upsell WTD

SOP Units lost CTD

SOP Units lost WTD

Update the Order/Billing History record

Order/Billing History

OBH # Orders

OBH $ Order total

OBH Qty ordered

OBH # Orders sold out

OBH $ Sold out total

OBH Qty sold out

Add a record to the Soldout Notifications table to generate soldout notifications for sold-out items

Soldout Notifications

  

Update the sold-to customer record

Customer Sold To Order History

COH On order $

COH # Orders LTD

COH # Sold outs LTD

COH $ Orders LTD

COH $ Sold outs LTD

COH Last Card Number

COH Active since date

COH Last order date

OTY Order type

PAY Pay type

SRC Source code

Update the ship-to customer record

Customer Ship To Order History

HOH On order $

HOH # Orders LTD

HOH # Sold outs LTD

HOH $ Orders LTD

HOH $ Sold outs LTD

HOH Active since date

HOH Last order date

OTY Order type

PAY Pay Type

SRC Source code

Update operator statistics, based on order type

Order Type/ User

OTU # Orders TD

OTU # Orders LTD

OTU $ Value - TD

OTU $ Value - LTD

OTU # Recips TD

OTU # Recips LTD

OTU # Lines TD

OTU # Lines LTD

Update operator statistics by accounting period, based on order type

Order Type/ User History

OUH # Orders

OUH $ Value

OUH # Recips

OUH # Lines

Update the source code record with the accumulated order totals

Source

$ Orders

$ Soldouts

# of Orders

# of Soldouts