5 Customer Service
- Establishing Customer Service Tables
- Setting Up Customer Support Tables
- Creating and Updating Customers
- Order Inquiry
- Performing Order Maintenance
- Order Status Reports and On-line Inquiries
- Managing Declined Authorizations
- Releasing Held Orders
- Managing Returns
- Issuing Refunds
- Working with Catalog Requests
- Managing Soldouts and Backorders
- Processing and Purging Subscriptions
- Memberships
- Email Repository
- Customer Service Appendices
Establishing Customer Service Tables
Topics in this part: The following topics describe how to create and maintain customer support tables that work in conjunction with Order Entry, Order Maintenance, and other Customer Service functions.
-
Establishing Order Types (WOTY) presents the screens you work with to create and maintain order types required for Order Entry.
-
Establishing Price Override Reason Codes (WPOR) presents the screens you work with to create and maintain price override reason codes needed for entering item prices at no charge and for overriding prices in Order Entry and Order Maintenance.
-
Establishing Additional Charge Codes (WADC) describes how to create and maintain codes that let you add additional charges or credits to an order.
-
Establishing Order Hold Reason Codes (WOHR) describes how to create and maintain user-defined reason codes that you apply when you want to place an order on hold.
-
Establishing Cancel Reason Codes (WCNR) describes the screens you work with to create and maintain reason codes for canceling items from an order.
-
Establishing Return Reason Codes (WRTR) describes the screens you work with to create and maintain reason codes for returning items.
-
Establishing Exchange Reason Codes (WEXR) describes the screens you work with to create and maintain reason codes for exchanging items.
-
Establishing Return Disposition Values (WRDV) describes the screens you work with to establish codes that you use to direct returned merchandise to the warehouses and warehouse locations that you have designated to receive returns.
-
Establishing Custom Special Handling Formats (WSHF) describes the screens you work with to design the format of the special handling screen that you use in Order Entry.
-
Establishing Add Reason Codes (WADR) describes the screens you work with to establish codes for tracking the reasons for adding items to orders in Order Maintenance.
-
Working with Order Inquiry Reason Codes (WORC) describes the screens you use to create and maintain reason codes for advancing to order inquiry or order maintenance from the CTI Customer Selection screen.
-
Working with Order/Call Disposition Reject Reason Codes (WWRR) describes the screens you work with to create or maintain order and call disposition reject reason codes.
-
Working with Default Messages (WMSG) describes the screens you use to create and maintain default messages, used to default message text to an order message or order line message on an order.
-
Working with Order Line Activity Codes (WOLA) describes the screens you use to create and maintain order line activity codes.
Establishing Order Types (WOTY)
Purpose: Order type codes identify how you received the order, such as by phone, mail or fax. You can use order type codes for analysis purposes, to control the format of the Order Entry Detail screen, or to indicate whether to:
- display promotional pricing windows.
- display zone date windows for zone reservation (weather-sensitive) items.
- generate soldout notifications for items you sell out through order entry or order maintenance.
- generate immediate backorder notifications.
- perform online credit card authorization and display an authorization response window in order entry.
- generate various types of an email notifications or the Outbound
Email XML Message (CWEmailOut), and whether to include soldout
items on the order confirmation email message.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
- use the Experian Data Quality (EDQ) Address Validate API to standardize addresses.
- treat orders as pre-order quotes instead of regular orders; see Entering Pre-Order Quotes.
- indicate that the order originated from an external system and was assigned to Order Management System for fulfillment via the Order Broker Integration.
- identify a ship-for-pickup order to the Order Broker primarily by its Order Management System order number or its e-commerce order number.
- indicate that the order originated in Order Management System but the customer prefers to pick up the order at a store location that has the inventory available; see Store Pickup Orders.
- use override template text for certain email notification types.
- indicate that the order originated through the ChannelAdvisor integration; see the ChannelAdvisor Order Type (L90) and the ChannelAdvisor Integration Overview.
The order API uses the E-Commerce Order Type (G42) if no order type is specified in the message. If that system control value is also blank, the order is created in error status.
Each order must have an order type.
In this topic:
- Work with Order Types Screen
- Create Order Type Screen
- Order Type Email Selection Screen
- Order Type Email Template Screen
- Change Order Type Email Template Screen
Work with Order Types Screen
How to display this screen: Type WOTY in the Fast path field at the top of any menu, or select Work with Order Types from a menu.
Field | Description |
---|---|
Type |
Identifies how you receive an order. Alphanumeric, 1 position; optional. |
Description |
The description associated with the order type. Alphanumeric, 30 positions; optional. |
Promo |
Determines whether to display promotional pricing windows for orders with this order type. Promotional pricing windows open if the customer orders a specific item or quantity of items, and also display items that the customer can order for a special price. Valid values are:
For more information: See Upselling the Customer in Order Entry for information on promotional pricing, and see Automatically Display Coordinate Items in Order Entry (I53) for more information on adding coordinate items to an order. Optional. |
S/O (soldout) |
Controls whether to generate soldout notifications when an item sells out in order entry or order maintenance. Valid values are:
Optional. |
Mail/Rtl |
Indicates whether this is a mail order or retail order type. Informational only. Valid values are:
Optional. |
Whs |
The warehouse defined for the order type. Used for:
Numeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Create an order type |
Select Create to advance to the Create Order Type Screen. |
Change an order type |
Select Change for an order type to advance to the Change Order Type screen. You can change any information on this screen except the order type code. See Create Order Type Screen for field descriptions. |
Delete an order type |
Select Delete for an order type to delete it. Note: When you delete an order type code you lose:
|
Display an order type |
Select Display for an order type to advance to the Display Order Type screen. You cannot change any information on this screen. See Create Order Type Screen for field descriptions. |
Work with user defined fields |
Select User Field for an order type to advance to the Work with User Fields Screen. |
Suppress generation of individual email notifications for the order type |
Select Email Selection for an order type to advance to the Order Type Email Selection Screen. |
Work with email notification templates for the order type |
Select Email Template for an order type to advance to the Order Type Email Template Screen. |
Create Order Type Screen
Purpose: Use this screen to create an order type.
How to display this screen: Select Create at the Work with Order Types Screen
Field | Description |
---|---|
Type |
Indicates how the order was received, such as from the web storefront, a retail integration, or other methods. Alphanumeric, 1 position Create screen: required. Change screen: display-only. |
Description |
The description of the order type. Alphanumeric, 30 positions; required. |
Promo windows |
Controls whether to display promotional pricing windows for orders with this order type. Valid values are:
You can define promotional pricing to take place at the dollar, group, or item level, including:
If you set this field to Promo, a pop-up window opens in Order Entry when the operator enters an item associated with a promotional pricing promotion. See Upselling the Customer in Order Entry. Required. |
Zone date windows |
Controls whether to display an informational zone reservation date window in order entry when the customer orders a zone reservation-coded item. Zone reservation codes identify weather-sensitive inventory, such as plant stock, which require restricted shipping dates. Valid values are:
Generally, you would select for phone orders, since you can notify the customer of the date the item will ship and deselect for mail orders. See Shipping Zone Reservation Overview for more information. |
Soldout notifications |
Controls whether to generate soldout notifications for items that you sell out through order entry or order maintenance. Valid values are:
Note: This flag does not apply to quote orders. The system does not generate soldout notifications for items sold out in order entry or maintenance for quotes. |
Exclude S/O on order confirmation |
Indicates whether to exclude soldout items on the order confirmation email or the Outbound Email XML Message (CWEmailOut). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Note: The system excludes soldout items from the order confirmation email only if the program in the Order Acknowledgement Program (G50) system control value is based on the ECR0318 or ECR0405 base program.For example, you might wish to exclude soldout items on order confirmations for phone orders, but include soldout items for orders you receive through the order API.
Note: If the soldout item is the only item on the order and you exclude soldout items from the order confirmation, the system does not generate the email.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Mail order/Retail |
Indicates whether to treat the order as a mail order or a retail sale. Informational only. Valid values are:
Required. |
Retail warehouse |
The warehouse defined for the order type. Used for:
In order to enter a warehouse code in this field:
Numeric, 3 positions; optional. |
Immediate B/O notice |
Indicates whether to generate an initial (first) backorder notification card the next time you run Generate Backorder Notices (GBOC). Valid values are:
Typically, you select this setting for mail orders because you do not have an opportunity to inform the customer of the expected delivery date when you enter the order. If you have defined a Number of Days to Delay Initial Backorder Notice (D89), the system does not generate a notice for a backordered item unless the expected ship date is after this number of days.
|
Email notification |
Indicates whether to generate order-related email notifications to the customer. Valid values are:
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Even if this setting is selected, the system generates email notifications only if all the required information is available and if you have not flagged the notification type at the Order Type Email Selection Screen to prevent generation. See Working with E-Mail Notification Templates (WEMT) for an overview of the logic the system uses to determine whether to generate an email notification, and for information on setting up your company to generate email notifications.
|
On-line authorization |
Indicates whether to perform online credit card authorization during order entry and order maintenance. Valid values are:
See Performing Online Credit Card Authorizations for an overview of the online credit card authorization process. This field displays only if the On-line Authorizations (B89) system control value is selected. Required. |
Address standardization |
Controls whether to use the Experian Data Quality (EDQ) Address Validate API for address standardization.
See Experian Data Quality (EDQ) Address Validate API for an overview and required setup. Required. |
Quote |
Indicates whether an order of this order type is a pre-order quote and not a regular order. Valid values are:
Optional. |
Expiration days |
Indicates the number of days a pre-order quote is valid before it expires. When you accept a pre-order quote in order entry, the system updates the Cancel date for the quote based on the quote’s arrival date and the expiration days specified here. The system removes the cancel date when you convert the quote to an order. Example: If the arrival date for a quote is 10/29/11 and the expiration days defined for the quote order type is 30, the system updates the Cancel date for the quote to 11/28/11. Note: If you change the order type for a quote to another order type whose Quote field is also selected, the system recalculates the cancel date for the quote based on the Expiration days field for the new order type. If an Expiration days has not been defined for the new order type, the system removes the cancellation date from the quote.Note: You can enter a value in this field only if the Quote field is selected.Numeric, 3 positions; optional. |
Pay method required |
Indicates whether a pay method is required on a pre-order quote. Valid values are:
If you change the order type for a quote to another order type whose Quote field is also selected, the setting of the Pay method required field for the new order type determines whether to require a payment method. Note: You can select this field only if the Quote field is selected.Optional. |
Order Type Email Selection Screen
Purpose: Use this screen to prevent the system from generating emails or the Outbound Email XML Message (CWEmailOut) for certain types of notifications for an order type.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
You might want to prevent generating certain notices for order types that Order Management System fulfills as part of an integration with an external system. For example, if you create store pickup orders as part of the integration with Order Broker, you might want to suppress generation of shipment confirmation emails, because the customer picks up the order in a store location rather than receiving a shipment, so the shipment confirmation might confuse the customer; however, you might want to continue generating order confirmation emails for that order type, and you require the Email notification flag to be selected so that store pickup notifications are generated.
To suppress all notifications for an order type, deselect the Email notification flag.
Determining whether to generate an notice:
- If the Email notification flag for the order type is unselected, do not generate any notices. Otherwise,
- If the Email notification flag for the order type is selected, is the notification type included in the Order Type Email Selection screen? If not, generate the notice. Otherwise,
- If the Email notification flag for the order type is selected and the notification type is included at the Order Type Email Selection screen, is the notification type set to Yes? If it is, generate the notice. Otherwise,
- If the notification type is set to No at the Order Type Email Selection screen, do not generate the notice.

Things to note:
- Default setting: If the Email notification flag for the order type is selected, each Order Type Email Selection setting is set to Yes by default.
- Screen access: If the Email notification flag for the order type is unselected, you cannot advance to the Order Type Email Selection screen.
- Additional rules: Each notice type is still subject to the additional generation rules described in Working with E-Mail Notification Templates (WEMT). For example, the system checks the customer’s opt-in/out setting and whether there is an email program defined in the related system control value.
- Quotes: The Order Type Email Selection settings (with the exception of the Soldout Notification setting) do not apply to quote order types, regardless of the setting of the Email notification flag for the quote order type. The system does not automatically generate any emails except the soldout notification for quotes you create through interactive order entry until you accept them and change them to non-quote orders, although you can generate the Quote Confirmation or “Contact Us” emails for a quote on demand. See HTML Format Notification Samples and Contents for examples and more information.
- Template selection is separate: The email selection rules you set at this screen operate independently of the rules that govern which template to use for a notification. See the Order Type Email Template Screen for more information on setting up templates.
Narvar: The Send Email setting for the Shipment Confirmation here does not prevent generating shipment notifications through the Narvar Integration.
How to display this screen: Select Email Selection for an order type at the Work with Order Types Screen. This option is available only if the Email notification flag for the order type is selected.
Field | Description |
---|---|
Order type |
The code and description of the order type you selected at the Work with Order Types Screen. Code: alphanumeric, 1 position; display-only. Description: alphanumeric, 30 positions; display-only. |
Notification type |
The type of notification that you would like to generate or suppress for this order type. Only certain notification types are available for selection; the system automatically generates the additional notification types that are not listed at this screen if the Email notification flag for the order type is selected. Available types:
Note: The Shipment Confirmation setting also controls generation of a request with the customer’s actual email address through the Narvar Integration.Automatic generation of other notification types that are not listed: Any additional notification types that are not listed at this screen are generated automatically for the order type if the Email notification flag for the order type is selected and the customer and order are otherwise eligible. These additional notification types are:
See Working with E-Mail Notification Templates (WEMT) for more information on how the system determines whether to generate various types of notifications. |
Send email |
Controls whether to generate this type of notification for the selected order type: Narvar: The Send Email setting for the Shipment Confirmation here does not prevent generating shipment notifications through the Narvar Integration. Yes (default) = Generate the notification type if the customer and order are eligible. No = Do not generate this notification type for the selected order type. |
Completing this screen: When you first advance to this screen, the Send email flags for each notification type are set to Yes by default. Change the setting of the Send email flag for each notification type you would like to update and select OK. Your changes take effect immediately.
Other updates to notification types: See Email Generation Setup for an overview of setup requirements and options, including the hierarchy for notification template text and the “from” email address.
Order Type Email Template Screen
Purpose: Use this screen to work with the template text for the order, shipment, order cancellation, and order line cancellation confirmation notices for a specific order type. You can also change the setting of the XML only? flag if you would like to specify whether to generate an actual email or the Outbound Email XML Message (CWEmailOut).
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Note:
The system does not automatically create an order type template. To create a template for one of the notifications types, you need to select the Change option and complete the Change Order Type Email Template Screen.When does the system use this template? The system uses the text and XML only? setting from the order type if there is no template set up at the order type/entity or entity level. The hierarchy for template selection is:
- Order type/entity level (set up through the Entity Email Override by Order Type Screen)
- Entity (set up through the Work with Entity Email Overrides Screen)
- Order type (set up through this screen, the Order Type Email template screen)
- Company (set up through Work with E-Mail Template Screen)
Note:
Although the screen does not prevent you from setting up templates for a quote order type, the system never generates any of the notifications available at this screen until you accept the quote and change it to a new order type; and, at that time, the templates for the new order type apply.These settings are not used for the generation of shipment notifications through the Narvar Integration.
What about other notification types? You cannot set up email templates at the order type or order type/entity level for any other notification types besides the order, shipment, order cancellation, and order line cancellation notices. For the remaining notification types, the hierarchy is:
- Entity (set up through the Work with Entity Email Overrides Screen)
- Company (set up through Work with E-Mail Template Screen)
Notification type selected for order type? The system does not prevent you from creating or changing an email template whose Send email flag is set to No at the Order Type Email Selection Screen, although in this situation the system does not generate the notification.
Narvar integration: The template settings do not apply to shipment notifications generated through the Narvar Integration.
How to display this screen: Select Email Template for an order type at the Work with Order Types Screen. This option is available only if the Email notification flag for the order type is selected.
Field | Description |
---|---|
Order type |
The code and description of the order type you selected at the Work with Order Types Screen. Code: alphanumeric, 1 position; display-only. Description: alphanumeric, 30 positions; display-only. |
Notification type |
A notification type whose template you can create, change, display, or delete at this screen. Notification types you can set up for an order type:
See Working with E-Mail Notification Templates (WEMT) for more information on when the system generates each notification type and the contents of each. |
Option | Procedure |
---|---|
Create a new email template at the order type level |
In the Action drop down list, select Change for a template to advance to the Change Order Type Email Template Screen, where you can enter template text and optionally select the XML only? flag if you would like to generate the Outbound Email XML Message (CWEmailOut) rather than an actual email. Note: There is no Create option at this screen; use the Change option to create a new template.For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Change an existing email template at the order type level |
In the Action drop down list, select Change for a template to advance to the Change Order Type Email Template Screen, where you can change the template text and optionally change the setting of the XML only? flag if you would like to specify whether to generate an actual email or the Outbound Email XML Message (CWEmailOut). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Display an email template at the order type level |
In the Action drop down list, select Display for a template to advance to the Display Order Type Email Template screen, where you can review an existing template or verify whether the template has been set up. See the Change Order Type Email Template Screen for field descriptions. |
Delete an email template at the order type level |
In the Action drop down list, select Change for a template to advance to the Change Order Type Email Template Screen, where you can delete the contents of the template. |
Change Order Type Email Template Screen
Purpose: Use this screen to:
- create a new order type-level template
- change an existing order type-level template
- delete an existing order type-level template
These settings are not used for the generation of shipment-related emails through the Narvar Integration.
How to display this screen: Select Change for a notification type at the Order Type Email Template Screen.
Field | Description |
---|---|
Notice Type |
The notice type you selected at the Order Type Email Template Screen. Display-only. |
Order Type |
The code and description of the order type you selected at the Work with Order Types Screen. Code: alphanumeric, 1 position; display-only. Description: alphanumeric, 30 positions; display-only. |
XML only? |
Indicates whether to generate the Outbound Email XML Message (CWEmailOut) rather than an actual email notification. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email that includes promotional material. See Outbound Email XML Message (CWEmailOut) for an overview. Valid values are:
Used only if there is text: The system uses the setting of this flag at this level only if there is also text set up for the template at this level. For example, if you select this flag for the order confirmation template for an order type, but do not enter any text, the system continues up the hierarchy and checks the setting for the order confirmation template at the company level (set up through Working with E-Mail Notification Templates (WEMT)). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Text to print above items |
The standard text to include in each email above the information specific to the order. This text is also included in the Outbound Email XML Message (CWEmailOut). Select Dflt Frm Comp to copy the Text to print above items and Text to print below items to the screen from the company-level template, and then edit as needed. Alphanumeric, ten 60-position lines; at least one line required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Text to print below items |
The standard text to include in each email below the information specific to the order. This text is also included in the Outbound Email XML Message (CWEmailOut). Select Dflt Frm Comp to copy the Text to print above items and Text to print below items to the screen from the company-level template, and then edit as needed. Alphanumeric, three 60-position lines; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Completing this screen:
- Create a new template:
-
Optionally, select the XML only? flag to Outbound Email XML Message (CWEmailOut) rather than an actual email notification
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
-
Optionally, select Dflt Frm Comp to copy the Text to print above items and Text to print below items to the screen from the company-level template, and then edit as needed.
-
If you did not default text from the company-level template, enter the Text to print above items. You must define at least one line of text.
-
Optionally, enter the Text to print below items
-
Click OK when you are done to save your changes, or click Exit to exit without saving.
-
- Change an existing template:
-
Optionally, change the setting of the XML only? flag indicating whether to generate the actual email or the Outbound Email XML Message (CWEmailOut)
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
-
Optionally, change the Text to print above items or the Text to print below items, or enter additional text.
-
Click OK when you are done to save your changes, or click Exit to exit without saving.
-
- Delete an existing template:
-
Delete each line of text in the Text to print above items and Text to print below items.
-
Click OK when you are done to delete the template, or click Exit to exit without deleting.
-
Establishing Price Override Reason Codes (WPOR)
Purpose: Price override reason codes let an authorized operator change an item price or enter an item at no charge in Order Entry or Order Maintenance. You need to designate one or more price override reason codes for promotional or upsell items that may be added to an order automatically. When an item is added to the order from a promotion, the system updates the Override field on the order detail line with the default override reason code designated for the type of promotion or upsell so that you can track the discounts by override reason. Price overrides apply only at the line item level.
The Price Override Reason table stores the number of price overrides and the net discount associated with each reason code.
Default Price Override Reasons
You can set up the following default price override reason codes in the System Control table:
- Default Price Override Reason (B35)
- Price Override Code for Promotional Priced Lines (B61) Note: This system control value is not currently implemented. The system applies the Default Price Override Reason (B35) to promotional priced lines.
- Price Override Reason for Same Price Exchanges (D92)
- Price Table Level Override Code (E05)
- Default Price Override Reason for Warranty Items (G01)
- Price Override Reason for E-Commerce (G73)
- Price Override Reason for SVC Refund Item (I74)
- Price Override Reason for Price Matrix Customer Specials (K42)
- Price Override Reason for Promotions (K45)
- Price Override Reason for Quotes (K75)
- Order Broker Price Override (K95)
- Price Override Reason Code for CPG Pricing (L59)
Note:
You cannot apply the Price Override Reason for Price Matrix Customer Specials (K42), Price Override Reason for Promotions (K45), or Price Table Level Override Code (E05) to an order line in order entry; these price override reason codes are reserved for system use.See the description of each system control value for more information.
ChannelAdvisor default: The ChannelAdvisor integration uses a price override reason code of W. You cannot change this default. See ChannelAdvisor Integration Overview and ChannelAdvisor Setup for background.
Secured features: The Price Overrides (A23) secured feature controls the ability to override a price in order entry, and the Override Price Override Limit (A64) controls the ability to exceed the Price Override Limit Percent (E55).
Report: You can use the Printing the Price Override Reason Report (PROR) option to generate a report indicating the number of units, discount amount, and discount percentage applied through price override reason codes. The report does not include price override reason codes whose Exclude from price override report field is selected.
In this topic:
Overriding the Item/SKU Offer Price
The Override item offer price field for a price override reason code indicates whether to use the price override amount entered in order entry as the item/SKU offer price for the order. The item offer price is stored in the Order Detail table for each order line. The following table describes how the system handles various functions depending upon how this flag is set for a price override reason code:
Function | Flag is Selected | Flag is Unselected | For Example, see: |
---|---|---|---|
calculating the discount amount on an order or order detail line |
The discount amount equals the difference between the override price entered and the final selling price; in other words, it equals any additional discounts applied after the price override. When an item is added to the order at no charge (for example, an accompanying item) then the regular offer price is not included in the discount total on the order |
|
The Discount field at the Display Invoice Header Screen |
evaluating the order or order detail line for a minimum coupon dollar amount |
The system uses the price override amount entered to evaluate the order or line for a dollar minimum |
The system uses the regular, single-unit offer price of the item or SKU to evaluate the order or line for a dollar minimum. If there is no offer price, the item cannot qualify for a coupon with a dollar minimum. |
|
highlighting discounted prices if the Display Order Line Discount Messages (F01 )system control value is selected |
The system does not highlight the overridden price. |
The system highlights the overridden price and displays the discount calculation message if an item/SKU offer price exists. |
The Display Order Line Discount Messages (F01) system control value and Discount Calculation Messages |
calculating freight using the By Offer Price freight method for a source code (see for an overview) |
The system uses the actual price to calculate freight charges for the order |
The system uses the original offer price to calculate freight charges for the order |
Work with Price Override Reason Screen
How to display this screen: Enter WPOR in the Fast path field at the top of any menu or select Work with Price Override Reasons from a menu.
Field | Description |
---|---|
Reason |
Represents a reason for overriding a price during order entry or order maintenance. Alphanumeric, 1 position; optional. |
Description |
The description associated with the price override reason code. Alphanumeric, 30 positions; optional. |
Screen Option | Procedure |
---|---|
Create a price override reason code |
Select Create to advance to the Create Price Override Reason Screen. |
Change a price override reason code description |
Select Change for a code to advance to the Change Price Override Reason screen. At this screen, you can change only the description. See Create Price Override Reason Screen for field descriptions. |
Delete a price override reason code |
Select Delete for the code. Note: You can delete a price override reason code at any time. However, you will lose any data associated with the reason code that is stored in the Price Override table. Additionally, if the reason code is defined as a default in the System Control table, deleting the code causes the system to display error messages in order entry. |
Display a price override reason code |
Select Display for a code to advance to the Display Price Override Reason screen. You cannot change any information on this screen. See Create Price Override Reason Screen for field descriptions. |
Create Price Override Reason Screen
Purpose: Use this screen to create price override reason codes for use in Order Entry and Order Maintenance.
How to display this screen: Select Create at the Work with Price Override Reason Screen.
Field | Description |
---|---|
Price override code |
Identifies the reason to override a price during order entry or order maintenance. Alphanumeric, 1 position. Create screen: required. Change screen: display-only. |
Description |
The description associated with the price override reason code. Alphanumeric, 30 positions; required. |
Override item offer price |
This flag indicates whether to use the price override amount entered in order entry as the item/SKU offer price for the order. The item offer price for each order line is stored in the Order Detail table. Valid values are:
See Overriding the Item/SKU Offer Price for an overview of how each setting works. |
Exclude from price override report |
This flag indicates whether to exclude the price override code from the Price Override Reason Report, which you can use to review the price override reason codes used to discount items for a range of dates, and the total discount amounts and percentages applied. Valid values are:
|
Nbr of overrides (Number of overrides) |
This field, displayed only on the Display Price Override Reason Code screen, is no longer implemented as of update 21.0. If a number of overrides was tracked for a price override reason code prior to update 21.0, the total is set to zero when the override reason is first used after applying the 21.0 update. To track the usage of a price override reason, generate the Price Override Reason Report. Numeric, 5 positions; display-only, updated by the system. |
Total discount |
The total discount amount represented by usage of this price override reason code. This number is calculated by subtracting the override price from the offer price, and is not updated for price override reason codes whose Override item offer price field is selected. Note: This field appears on the Display Price Override Reason Code screen only.Numeric, 20 positions with a 2-place decimal; display-only, updated by the system. |
Establishing Additional Charge Codes (WADC)
Purpose: Use additional charge codes to add miscellaneous charges or credits to an order.
You can add an additional charge or credit to an order in order entry or order maintenance by selecting Charges. You can display the same pop-up window in Work with Return Authorizations if you use the streamlined version; see Working with Return Authorizations: Streamlined Process.
You can establish additional charge codes for:
- special handling charges, such as monogramming, engraving, alterations or personalization.
- dollar discounts for an offer or source
- service charges
- shipper additional charges
- credits to offset additional charge codes when processing refunds
- freight credits to apply to Amazon orders
Additionally, use this table to identify whether the additional charge code displays the standard special handling screen, a customized special handling screen, or no special handling screen.
Note:
You can limit the total amount of negative additional charges applied to an order by entering a dollar value in the Negative Additional Charge Limit (E49) system control value.In this topic:
- Examples of Additional Charge Codes
- Special Handling Overview
- Work with Additional Charges Screen
- Create Additional Charges Screen
Related system control values:
- Default Additional Charge Code (C45): The system uses this code to apply a balance due write-off in order entry.
- Negative Additional Charge Limit (E49): You cannot enter negative additional charges on an order whose total will exceed this limit unless you have proper authority, as controlled by the Override Negative Additional Charge Limit (A60) secured feature, described below.
- Restrict Additional Charge Amount if Default Charge (F43): If you set this system control value to Y, you will not be able to enter an additional charge amount at the Enter Additional Charges window in order entry, order maintenance, or Work with Return Authorizations for any additional charge code set up with a default charge amount. This system control value works together with the Enter Amount for Order Additional Charge Code (A80) secured feature, described below.
See Special Handling Overview for additional system control values related specifically to special handling.
Related secured features:
- Additional Charges Access (A24): Controls access to the Enter Additional Charges pop-up window in order entry, order maintenance, or Work with Return Authorizations, accessible by selecting Charges. If a user is prohibited from working with additional charges through this secured feature, this setting overrides the settings of any other secured features.
- Override Negative Additional Charge Limit (A60): Controls the ability to override the negative additional charge limit set with the system control value described above.
- Enter Amount for Order Additional Charge Code (A80): Controls the ability to enter an additional charge amount at the Enter Additional Charges pop-up window in order entry, order maintenance, and Work with Return Authorizations (streamlined version only), accessible by selecting Charges. Works together with the Restrict Additional Charge Amount if Default Charge (F43) system control value described above; see Adding Miscellaneous Charges or Credits in Order Entry for a complete description.
See Special Handling Overview for additional secured features related specifically to special handling.
Examples of Additional Charge Codes
Type of Charge | Example | Defined Where? |
---|---|---|
service charge |
flat charge applied to an order |
Offer or Source Code; see Setting Up Offer Information |
dollar discount |
discount (credit) applied to an order based on merchandise total |
Offer or Source Code; see Setting Up Offer Information |
shipper/item |
additional charge for delivery of oversized or heavy items |
Shipper/Item (using the additional charge code for this purpose is not currently implemented) |
special handling |
charge for monogramming or other personalization, hemming, or dyeing |
Item SKU/Offer; see Special Handling Overview below |
restocking fee |
charge for processing returns |
Ad hoc; Additional Charges pop-up window in Order Entry (Charges) |
long distance phone credit |
credit to customer for phone calls to customer service |
Ad hoc; Additional Charges pop-up window in Order Entry (Charges) |
miscellaneous credits |
credit you apply when processing a return to offset an additional charge added in Order Entry |
Ad hoc; Additional Charges pop-up window in Order Entry (Charges) |
Special Handling Overview
What is special handling? Special handling is any type of item personalization, such as monogramming, alterations, engraving, etc. You can also use a special handling code to automatically add a handling charge to an order when the customer orders a specific item, even if there are no actual handling instructions.
What are the two main types of special handling?
- Standard special handling (the S/H type (Special handling type) is Standard) supports entry of free-form text instructions.
- Custom special handling (the S/H type (Special handling type) is Custom) supports entry of specific fields, with default entries and validation. You use the Establishing Custom Special Handling Formats (WSHF) menu option for format setup.
What makes an item eligible for special handling? The Special handling flag for the item offer or SKU offer controls whether the item is eligible for personalization. If the Special handling flag is selected:
- Default special handling: If there is a S/H code (Special handling code) specified for the item offer or SKU offer, and that code’s Bypass S/H flag is unselected, then this type of special handling defaults for the item. See Bypassing or Suppressing the Special Handling Screens for a discussion of screen flow based on different special handling options.
- Optional special handling: Otherwise, the item receives special handling only if you enter a code in the S/H code field for the item when you are entering the order, select the special handling option for an existing order detail line, or specify a special handling code in order maintenance.
If the Special handling flag for the item offer or SKU offer is unselected, the item is not eligible for special handling.
How much does the special handling cost? The system determines the special handling charge by:
- If a S/H price (Special handling price) is specified for the item offer or SKU offer, use this price; otherwise,
- If a Default price or Default price % is specified for the special handing format, use this price (this option is available for custom special handling only).
See Overriding the Special Handling Charge or Price for a discussion.
Putting the order line on hold: You can flag a custom special handling format to automatically put an order line on hold. See Putting a Line on Hold through a Special Handling Format for a discussion.
Contact Center: You can also review, add, update, or delete special handling for an order line in Contact Center. However, Contact Center does not currently support:
- putting an order line on hold or releasing the line from hold through a special handling format
- bypassing or suppressing special handling screens
System control values: System control values related to special handling include:
- FTC -- # of Days to Add for Special Handling (C67)
- Enter Custom Special Handling in Upper and Lower Case (D65)
- Generate Custom Special Handling File (D66)
- Evaluate Special Handling Charges by Order Line (D67)
- Tax on Handling (B15)
- Display Special Format Response Descriptions in Order Entry (E90)
- Include Spaces in Special Handling Edit for Maximum Characters (F80)
Bypassing or Suppressing the Special Handling Screens
You can set up special handling for an item offer or SKU offer so that you advance automatically to a special handling screen when entering an item; or, you can specify to advance to the screen on demand only; or you can prohibit display of the screen in order entry, but still add the handling charges to the order.
When do you advance to a special handling screen?
- Automatically when you enter an item: When you enter an item in order entry or order maintenance that has a S/H code (Special handling code) specified for the item offer or SKU offer, you automatically advance to the Work with Special Handling Screen or Work with Custom Special Handling Screen (depending on the special handling type) unless:
- if the Suppress S/H window flag for the additional charge code is set to Suppress: The special handling code and any appropriate charges are added to the order without advancement to a special handling screen. In this situation, you cannot advance to a special handling screen in order entry or order maintenance, although you can display the related screen in standard or streamlined order inquiry.
Note:
The Suppress S/H window flag causes the special handling charge to be added to the order automatically when you use interactive order entry. For example, the charge is not added automatically through the generic order message (order API).Note:
You should not select the Suppress S/H window flag for a custom special handling format. Adding an item with this setting to an order causes an error in Contact Center order entry.- if the Bypass S/H flag for the additional charge code is set to Bypass: You do not advance automatically to the Work with Special Handling Screen or Work with Custom Special Handling Screen, although you can display it on demand as described below.
- By specifying a special handling code when you enter an item:
- If no special handling code assigned: When you enter an item in order entry or order maintenance that does not have a S/H code (Special handling code) specified for the item offer or SKU offer, but does have the Special handling flag selected, you can advance automatically to a special handling screen by specifying the S/H code while entering the item. However, if the Suppress S/H window flag is set to Suppress, you cannot actually display the special handling screen, as described above.
- If special handling code is flagged to bypass the screen: If the Bypass S/H flag for the additional charge code is set to Bypass, you can still display the screen when you enter the item in order entry or order maintenance by specifying the S/H code while you enter the item.
- Adding special handling to an existing order detail line: You can also advance to a special handling screen by:
- Selecting Handling for an existing item at the Work with Order Lines Screen (Adding Items to the Order), unless the Suppress S/H window flag is set to Suppress, as described above.
- Selecting Change for an existing item at the Work with Order Lines Screen (Adding Items to the Order) to advance to the Work with Order Line Screen (Changing/Adding an Item), then entering the S/H code and, optionally, S/H charge. Again, you cannot display the special handling screen if the Suppress S/H window is set to Suppress, as described above.
- Selecting Change for an existing item at the Work with Order Lines Screen (Adding Items to the Order) to advance to the Work with Order Line Screen (Changing/Adding an Item), then selecting Special Handling, you have the opportunity to select a special handling code and apply it to the order line, provided the Special handling flag selected.
Removing special handling information for an order line: If special handling is assigned to an item on an order, you can remove it by:
- If the special handling format is not suppressed, you can select Handling for an existing item at the Work with Order Lines Screen (Adding Items to the Order) and then select Delete special handling or Delete all at the special handling screen.
- Otherwise, unless the Suppress S/H window is selected and the additional charge code specifies a custom special handling format, you can delete the special handling instructions and charge by selecting Change for an existing item at the Work with Order Lines Screen (Adding Items to the Order) to advance to the Work with Order Line Screen (Changing/Adding an Item), then clearing the S/H code and the S/H charge.
- If the additional charge code is flagged to suppress special handling and uses a custom special handling format, you cannot delete the special handling from the order line. You will need to delete the order line and re-add it.
Bypassing or suppressing special handling screens is not supported in Contact Center.
Overriding the Special Handling Charge or Price
You can enter a special handling price at the special handling screen or the Work with Order Line Screen if you have the required authority. Two secured features control access:
- Enter or Override Personalization Charge (A40): Controls access to the Charge field when you are working with custom special handling formats in order entry (when the charge is established at the special handling format)
- Enter or Override S/H Price (B12): Controls access to the S/H price field when you are working with custom special handling formats in order entry (when the special handling price is defined for the item/offer or SKU/offer)
Standard special handling: The following chart summarizes how the system controls access for standard special handling formats:

Custom special handling: The following chart summarizes how the system controls access for custom special handling formats:

Summary: The following table summarizes the situations in which you can enter or override the special handling charge or price:
Screen | You can enter or override special handling charge/price if: |
---|---|
Special handling type = standard Authority under the Enter or Override S/H Price secured feature is *ALLOW |
|
Special handling type = standard Display of the special handling screen is not suppressed |
|
Special handling type = custom Display of the special handling screen is not suppressed And:
|
Putting a Line on Hold through a Special Handling Format
You can use the S/H hold flag for a custom special handling format to automatically put an order line on hold. When you create an order line that uses the special handling format, or apply the special handling format to an existing line, the system puts the order line in hold status.
You can release the order line from hold by:
- removing the special handling from the order line by selecting Special Handling at the Work with Order Line Screen (NOTE: Removing the special handling by selecting Special Handling at the Work with Order Line Screen will NOT release the order line from hold); or,
- changing the special handling format to a format that is not flagged for hold; or,
- using the Release option for the order line.
What if the special handling is suppressed? If you select the Suppress flag for the additional charge code associated with the special handling format, you cannot remove the special handling format from an existing order line. You can release the line to remove the hold, or you can delete the line and re-enter it.
Order API: When you create an order through the generic order API rather than interactive order entry, the system also puts the order line in hold status if it uses a special handling format flagged for hold.
Note:
Lines in hold status due to their special handling format are not displayed through the Working with Held Detail Lines (WOHD) menu option.Automatically applying the hold without special handling: You can set up a “dummy” special handling format to automatically place certain items in hold status, even though they do not require any actual special handling. To do so, create a custom special handling format with the S/H hold flag selected, but with no details. When you assign the special handling format to an additional charge code, select the Bypass option so that you do not advance automatically to a special handling screen; also, when you assign the additional charge code to the item offer or SKU offer, do not specify a S/H price.
When you add the item to an order through the order API, use the personalization_id in the inbound order message to specify the additional charge code, but do not include any personalization lines in the message.
Note:
To prevent pick slip preparation from sorting the order line with items that require actual special handling, remove the special handling format from the order line; do not use the Release option in order maintenance.Putting a line on hold or releasing the line from hold through a special handling format is not supported in Contact Center.
Work with Additional Charges Screen
Purpose: Use this screen to work with or review additional charge codes, including charges that you use for special handling. See Establishing Additional Charge Codes (WADC) for an overview.
How to display this screen: Enter WADC in the Fast path field at the top of any menu or select Work with Additional Charges from a menu.
Field | Description |
---|---|
Code |
Represents a type of additional charge or credit. Alphanumeric, 2 positions; optional. |
Description |
The description associated with the additional charge code. Alphanumeric, 30 positions; optional. |
Group |
Groups similar charge types for reporting purposes. Alphanumeric, 3 positions; optional. |
S/H type (Special handling type) |
Defines the type of special handling screen the additional charge code calls in order entry. Valid values are:
Required. |
S/H format (Special handling format) |
This code indicates the format of the custom special handling screen for the additional charge code. Special handling format codes are defined in and validated against the Special Handling Format table. See Establishing Add Reason Codes (WADR). Alphanumeric, 2 positions; optional. |
U/F |
User field; this field is informational only. Alphanumeric, 1 position; optional. |
Screen Option | Procedure |
---|---|
Create an additional charge code |
Select Create to advance to the Create Additional Charges Screen. |
Change additional charge code information |
Select Change for a code to advance to the Change Additional Charges screen. You can change any information on this screen except the additional charge code. See Create Additional Charges Screen for field descriptions. Note: Changing the values in the S/H type (Special handling type) and S/H format (Special handling format) fields will not affect existing orders. |
Delete an additional charge code |
Select Delete for a code. Note: You can delete an additional charge code at any time. However, existing orders will retain the code, but not the description. |
Display an additional charge code |
Select Display for a code to advance to the Display Additional Charges screen. You cannot change any information on this screen. See Create Additional Charges Screen for field descriptions. |
Create Additional Charges Screen
Purpose: Use this screen to create and define the characteristics of an additional charge code.
How to display this screen: Select Create at the Work with Additional Charges Screen.
Field | Description |
---|---|
Code |
Represents the type of additional charges or credits. You may apply additional charges to the source code, to the offer, to special handling of an item, to the item at the ship via level, or you can add them in order entry. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description associated with the additional charge code. Alphanumeric, 30 positions; required. |
Group |
Groups similar charge types for reporting purposes. Alphanumeric, 3 positions; optional. |
S/H type (Special handling type) |
Defines the type of special handling screen that appears in Order Entry or Order Maintenance for the additional charge code. Only additional charge codes with a type of C or S appear when you scan on the Special Handling field in Order Entry or Order Maintenance. Valid values are:
Note: If you specify a special handling type, you cannot enter a default charge amount, below. This is because the system never uses the default charge amount as part of special handling.Optional. |
S/H format (Special handling format) |
This code indicates the format of the custom special handling screen. Special handling format codes are defined in and validated against the Special Handling Format table. See Establishing Custom Special Handling Formats (WSHF). You must enter a a format if you entered Custom in the S/H type (Special handling type) field; otherwise, the system ignores the format entered here if the S/H type field is set to Standard or is blank. Alphanumeric, 2 positions; required if S/H type = Custom. |
S/H exclude tax? |
This flag indicates whether special handling charges are subject to normal tax evaluation. Valid values are:
Selecting this flag is valid only if the additional charge code represents special handling (the S/H type is Custom or Standard). You cannot select this flag if the additional charge does not represent special handling. Alphanumeric, required if S/H type = Custom or Standard. |
User field |
This field is informational only. Alphanumeric, 1 position; optional. |
Default charge |
The charge (positive amount) or credit (negative amount) to apply to an order when you enter this additional charge code at the Enter Additional Charges pop-up window. The system does not use the default charge in any other situation except through this pop-up window, which is available by selecting Additional Charges in order entry, order maintenance, or Work with Return Authorizations. Note: You cannot enter both a default charge amount and a special handling type.The Restrict Additional Charge Amount if Default Charge (F43) system control value and the Enter Amount for Order Additional Charge Code (A80) secured feature control how this field works. Numeric, 13 positions with a 2-place decimal; optional. |
Suppress S/H window |
Indicates whether to suppress the display of the Work with Special Handling Screen or the Work with Custom Special Handling Screen when you add an item with special handling in order entry. You might want to suppress display in order to automatically add a charge to the Handling bucket on an order without requiring the order entry operator to complete or accept the information on the special handling screen. Valid values are:
Not a valid entry for an additional charge code that does not have a Special handling format. |
Additional considerations when suppressing the special handling screens: Displaying special handling screens on demand: If the automatic advancement to the special handling screen is suppressed, you cannot display the screen on-demand. For example, a special handling screen is not available by selecting Special Handling for an item in order entry or order maintenance. However, you can still advance to the Display Special Handling or the Display Custom Special Handling screens in standard order inquiry, or display special handling information in streamlined order inquiry, regardless of the setting of this field. If you would like to prevent the special handling screen automatically but retain the ability to display it on demand, use the Bypass S/H flag instead of the Suppress S/H window flag. Entering returns through order entry: If a special handling format is set to suppress display and applies to the order detail line, then the handling charge will be automatically added to the order as a credit when you create a return by entering a negative quantity in order entry. However, if the special handling format is not set to suppress display, you advance to the special handling screen and have the option of accepting or rejecting the charge. Note: This flag causes the special handling charge to be added to the order automatically when you use interactive order entry. For example, the charge is not added automatically through the generic order message (order API).Does not control screen flow in Contact Center. Optional. |
|
Bypass S/H |
Indicates whether to bypass the automatic display of the Work with Special Handling Screen or the Work with Custom Special Handling Screen when you add an item with special handling in order entry; however, you can still display the special handling screen by:
Valid values are:
Does not control screen flow in Contact Center. Note: You should not have both this flag set to Bypass and the Suppress S/H window flag set to Suppress for an additional charge code in order to have the special handling option work correctly in order entry and order maintenance.Alphanumeric, optional. |
Establishing Order Hold Reason Codes (WOHR)
Purpose: Use the Order Hold Reason Code screens to create and maintain reason codes used to place orders on hold, and to set authority to release orders from hold for specific hold reason codes for a user or user class.
The Order Hold Reason table includes:
- system hold reason codes that are delivered with the system and cannot be changed
- reason codes that you can use to place orders on "user hold" in order entry or order maintenance
- reason codes that identify why a credit card order was declined
- reason codes for the system to apply automatically to orders you send to or receive from the Order Broker (see the Order Broker Integration Overview)
Reason codes in this table are assigned in Order Entry and Order Maintenance, and are also entered in the Vendor Response table to translate the service bureau decline response code into a user defined reason code. See Defining Vendor Response Codes.
You can also assign a hold reason code to an order through the Generic Pick In API (Shipments, Voids, and Backorders).
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
In this topic:
- Work with Order Hold Reason Screen
- Create Order Hold Reason Screen
- Authority Hierarchy
- Work with User Field Authority Screen (Setting Hold Reason Authority for Users)
- Work with User Class Field Authority Screen (Setting Order Hold Reason Authority for User Classes)
For more information: See Introducing Order Hold Reason Codes for a discussion of system-assigned order hold reason codes.
Work with Order Hold Reason Screen
How to display this screen: Enter WOHR in the Fast path field at the top of any menu or select Work with Order Hold Reasons from a menu.
Field | Description |
---|---|
Reason |
Represents:
Alphanumeric, 2 positions; optional. |
Description |
The description associated with the hold reason code. Hold reason codes created through the Generic Pick In API (Shipments, Voids, and Backorders) have a description of AB - AUTO CREATED where the hold_reason passed is AB. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Note: When you scan, your entry must match a full description exactly.Alphanumeric, 50 positions; optional. |
Screen Option | Procedure |
---|---|
Create an order hold reason code |
Select Create to advance to the Create Order Hold Reason Screen. |
Change an order hold reason code description |
Select Change for a hold reason code to advance to the Change Order Hold Reason screen. At this screen, you can change only the description. See Create Order Hold Reason Screen for field descriptions. To change the actual reason code, you must delete the existing record, then create a new one. |
Delete an order hold reason code |
Select Delete for a code. Note: You can delete an order hold reason code that you created at any time. When you delete a code, the code will still appear on customer order records, but no description will display. You will not be able to remove the order from hold through the Release Held Orders menu option; however, you will be able to release the order from hold in order maintenance by deleting the hold reason code. See Performing the Release and Work with Order Screen in Order Maintenance. |
Display order hold reason code detail |
Select Display for a hold reason code to advance to the Display Order Hold Reason screen. You cannot change any information on this screen. See Create Order Hold Reason Screen for field descriptions. |
Work with hold release authority for users |
Select User Release Auth for a hold reason code to advance to the Work with User Field Authority Screen (Setting Hold Reason Authority for Users). |
Work with hold release authority for user classes |
Select User Class Release Auth for a hold reason code to advance to the Work with User Class Field Authority Screen (Setting Order Hold Reason Authority for User Classes). |
Create Order Hold Reason Screen
To create: Use this screen to add an order hold reason code.
How to display this screen: Select Create at the Work with Order Hold Reason Screen.
Field | Description |
---|---|
Reason |
Represents the reason you are placing an order on hold. A reason code may also identify reasons for credit card decline or be a code delivered with the system for use during the credit checking process. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description associated with the hold reason code. Alphanumeric, 50 positions; required. |
Authority Hierarchy
You can use the Work with Order Hold Reason menu option to set user or user class authorities to specific hold reason codes. The settings you enter through this menu option are overrides to defaults set at a higher level.
General guidelines: The order in which the system checks for a user's authority to release an order from hold is described in the table below:
Authority setting | Set up through: |
---|---|
1. user's authority to the specific order hold reason |
Work with User Field Authority Screen (Setting Hold Reason Authority for Users) |
2. user's user class authority to the specific order hold reason |
Work with User Class Field Authority Screen (Setting Order Hold Reason Authority for User Classes) |
3. user's authority to the Order Hold Reason Release Authority (A77) secured feature |
Work with Secure Feature Authority screen in Working with User Records (WUSR) |
4. user's user class authority to the Order Hold Reason Release Authority (A77) secured feature |
Work with User Class Feature Authority screen in Setting Up User Classes (WUCL) (also available by selecting W/W User Classes in Work with Users) |
5. default setting of the Order Hold Reason Release Authority (A77) secured feature |
Work with Secure Features screen in Work with System Values/Features (fast path = WSYS) |
The system checks each setting in the above order, skipping over any blank settings until it finds a *ALLOW or *EXCLUDE setting.
Example One: User SBROWN is assigned to the user class WAREHOUSE. The Order Hold Reason Release Authority (A77) secured feature is set to *ALLOW. The WAREHOUSE user class authority for order hold reason UH is set to *EXCLUDE. SBROWN's user authority for order hold reason UH is set to *ALLOW. The result is that SBROWN can release orders from UH hold, because her user authority overrides the other settings. However, the other users in the WAREHOUSE user class cannot release orders from UH hold, unless they also have an override at the user level.
Example Two: User HBROWN has a Order Hold Reason Release Authority (A77) secured feature setting of *EXCLUDE. However, the user settings for the AA and BB hold reason codes only are set to *ALLOW. This user is not assigned to a user class. The result is that HBROWN can release orders from AA and BB hold only, but is excluded from releasing an order with any other hold reason code.
Releasing a hold in Contact Center: In the case of the Order Holds window in Contact Center, authority to the Selecting Held Orders (ERHO) menu option is also required, except for releasing user holds.
For more information:
- releasing an order through order maintenance: Work with Order Screen in Order Maintenance
- releasing an order through Release Held Orders: Performing the Release
Note:
Order hold reason release authority settings do not prevent a user from releasing an order from recipient hold (available by selecting Display for an order through Release Held Orders) or from a pay type hold (available by selecting User Class Release Auth for an order in Release Held Orders). The authority settings are effective only for header-level holds.Work with User Field Authority Screen (Setting Hold Reason Authority for Users)
Purpose: Use this screen to review or change a user's authority to release an order from hold for a specific hold reason code.
Note:
The authority settings are effective only for header-level holds, not for pay type or recipient holds.How to display this screen: Select User Release Auth for a hold reason code at the Work with Order Hold Reason Screen.
Field | Description |
---|---|
Hold reason |
The hold reason code you selected at the Work with Order Hold Reason Screen. The description displays to the right. Code: alphanumeric, 2 positions; display-only. Description: alphanumeric, 50 positions; display-only. |
User |
The user ID of a person within your company. Alphanumeric, 10 positions; optional. |
Name |
The user's name. Alphanumeric, 30 positions; optional. |
Authority |
The user's authority to release an order from the hold reason code specified. Valid values are:
Optional. |
User class authority |
The authority of the user's class to release an order from the hold reason code specified. Valid values are:
Alphanumeric, 8 positions; optional. |
Resetting User Authority
To delete: Select Delete for a user ID.
If you delete a user's user-level authority, the user class-level authority setting for this order hold reason, if any, will be in effect; if there is no user class setting, the system checks the setting of the Order Hold Reason Release Authority (A77) secured feature at the user, user class, and default levels in order. See Authority Hierarchy.
If the user did not have a user-level authority setting for this order hold reason, the screen does not display an error message; however, no changes take place.
To set to ALLOW: Select Allow for a user ID. The user will be able to release orders with this header-level order hold reason.
If the user already had authority to this order hold reason, the screen does not display an error message; however, no changes take place.
To set to EXCLUDE: Select Exclude for a user ID. The user will not be able to release orders with this header-level order hold reason.
If the user already is excluded from this order hold reason, the screen does not display an error message; however, no changes take place.
Work with User Class Field Authority Screen (Setting Order Hold Reason Authority for User Classes)
Purpose: Use this screen to review or work with the authority settings to a selected order hold reason by user class.
Important:
The authority settings are effective only for header-level holds, not for pay type or recipient holds.How to display this screen: Select User Class Release Auth for an order hold reason code at the Work with Order Hold Reason Screen.
Field | Description |
---|---|
Hold reason |
The hold reason code you selected at the Work with Order Hold Reason Screen. The description displays to the right. Code: alphanumeric, 2 positions; display-only. Description: alphanumeric, 50 positions; display-only. |
Class |
A user class within your company. Alphanumeric, 10 positions; optional. |
Description |
The description of a user class. Alphanumeric, 30 positions; optional. |
Authority |
The user class's authority to release an order from the hold reason code specified. Valid values are:
Alphanumeric, 8 positions; optional. |
Resetting User Class Authority
To delete: Select Delete for a user class.
If you delete a user class's authority, and if there is no user-level setting for the order hold reason, the system checks the setting of the Order Hold Reason Release Authority (A77) secured feature at the user, user class, and default levels in order. See Authority Hierarchy.
If the user class did not have an authority setting for this order hold reason, the screen does not display an error message; however, no changes take place.
To set to ALLOW: Select Allow for a user class. The users in this class can release orders with this header-level order hold reason unless the authority setting for an individual user is set to Exclude.
If the user class already had authority to this order hold reason, the screen does not display an error message; however, no changes take place.
To set to EXCLUDE: Select Exclude for a user class. The users in this class will not be able to release orders with this header-level order hold reason unless the authority setting for an individual user is set to Allow.
If the user class already is excluded from this order hold reason, the screen does not display an error message; however, no changes take place.
Establishing Cancel Reason Codes (WCNR)
Purpose: Use the Cancel Reason Code screens to create and maintain reason codes for item, order, or quote cancellations. You must establish at least one cancel reason code, because order maintenance requires that you enter a cancel reason code when you cancel an order or quote or reduce the quantity ordered. Additionally, the system uses cancel reason codes for automatic backorder cancellations, such as the cancellation of:
- the balance of an order after its first shipment
- backordered items after a specified number of days
- an item from all orders that contain the item (for example, soldout items)
Updates: When you cancel an entire order and enter a cancel reason code, the system assigns the reason code to each open (unshipped) item on the order.
The Cancel Reason table stores history on cancellations by offer, and the system writes transactions to the Order History table whenever you perform a cancellation.
The system also writes cancel reason information to the Refund table for prepaid orders. Prepaid orders include orders paid by check or cash.
Prevent refund? You might designate whether to generate refunds for a cancel reason code, such as when you cancel fraudulent orders. When you use a cancel reason code flagged to prevent a refund, the refund record is still generated, but in a Cancel Pending status. The next time you use Processing Refunds (MREF), the refund is canceled.
Reduce demand? If the cancel reason code is not flagged to reduce demand, and you cancel all items on the order, the order status is set to Canceled; otherwise, if the cancel reason code is flagged to reduce demand, or any items have shipped, the order status is set to Closed.
In this topic:
- Work with Cancel Reason Codes Screen
- Create Cancel Reason Screen
- Display Reason/Offer Screen (Cancel Reason History)
Work with Cancel Reason Codes Screen
How to display this screen: Enter WCNR in the Fast path field or select Work with Cancel Reasons from a menu.
Field | Description |
---|---|
Rsn (Cancel reason) |
Represents a reason for canceling an order or item. Numeric, 2 positions; optional. |
Description |
The description associated with the cancel reason code. Alphanumeric, 30 positions; optional. |
Refund |
Controls whether a refund will be generated for orders or quantities canceled with the cancel reason code. Valid values are:
Optional. |
Reduce |
Indicates whether the system decreases demand figures for cancellations using this cancel reason code. Demand represents the quantity ordered (but not necessarily shipped). Valid values are:
Optional. |
Screen Option | Procedure |
---|---|
Create a cancel reason code |
Select Create to advance to the Create Cancel Reason Screen. |
Change a cancel reason code |
Select Change for a cancel reason to advance to the Change Cancel Reason screen. See Create Cancel Reason Screen for field descriptions. You can change any information on this screen except the cancel reason code. |
Delete a cancel reason code |
Select Delete for a cancel reason code. If the cancel reason code has been used to cancel one or more orders, a pop-up window indicates that history information exists and requires confirmation. The Cancel Reason History record includes information about the number and dollar value of cancellations for that cancel reason by offer. See Display Reason/Offer Screen (Cancel Reason History). You will lose this history if you delete the cancel reason code. |
Display a cancel reason code |
Select Display for a cancel reason code to advance to the Display Cancel Reason screen. You cannot change any information on this screen. See Create Cancel Reason Screen for field descriptions. |
Display cancel reason history by offer |
Select Display Offer for a cancel reason code to advance to the Display Cancel Reason/Offer screen. See Display Reason/Offer Screen (Cancel Reason History). |
Create Cancel Reason Screen
To create: Use this screen below to create a cancel reason code.
How to display this screen: Select Create at the Work with Cancel Reason Codes Screen.
Field | Description |
---|---|
Cancel reason code |
Represents a reason for canceling an order or a quantity on the order. Numeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description associated with the cancel reason code. Alphanumeric, 30 positions; required. |
Generate refund? |
Controls whether a refund will be generated for orders or quantities canceled with the cancel reason code. Valid values are:
Optional. |
Reduce demand |
This flag indicates whether the system decreases demand figures (quantity ordered) for dollar value of orders when you cancel a line using the cancel reason code. Demand figures are tracked in the Source table (MSSRC) as well as the other tables listed under Demand Updates: Affected Tables. Valid values are:
|
|
Display Reason/Offer Screen (Cancel Reason History)
Purpose: Use this screen to display history by offer for a cancel reason code.
How to display this screen: At the Work with Cancel Reason Codes Screen, select Display Offer for a cancel reason code.
How to interpret this screen: This screen displays cancellation history associated with the reason code. Behind each reason code is the Cancel Reason/Offer table, which includes the number of orders and dollars canceled for the reason code.
Updates when? The system updates the History table when you accept a cancellation through Order Maintenance, provided the cancel reason code is not flagged to Reduce Demand.
This screen displays summary data by offer, with cancel counts and dollars for each date when items were canceled. Summaries are listed by offer, then by date. You cannot change any information on this screen.
Field | Description |
---|---|
Cancel reason code |
Represents a reason for canceling an order or a quantity on an order. This is the code you selected at the Work with Cancel Reason Codes Screen. Numeric, 2 positions; display-only. |
Offer |
A code representing a catalog, space or television advertisement from which you accept orders. Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; optional. |
Date |
The date when the cancellation(s) occurred. Numeric, 6 positions (in user date format); optional. |
# cancels |
The number of cancellations performed manually or automatically. Numeric, 3 positions; display-only, updated by the system. |
# units |
The total number of units canceled. Numeric, 3 positions; display-only, updated by the system. |
$ cancels (Dollars canceled) |
The total merchandise dollars canceled. Numeric, 13 positions with a 2-place decimal; display-only, updated by the system. |
Establishing Return Reason Codes (WRTR)
Purpose: Use the Return Reason Code screens to create and maintain reason codes for merchandise returns. You must establish at least one return reason code for receipt and credit of returned merchandise. When you enter returns through return authorizations, order entry, or order maintenance, or when the customer creates a return authorization at the web storefront, a return reason code is required.
The Return Reason table stores history on returns by offer, and the system writes transactions to the Order History table whenever you perform a return. The system also writes return reason history to the Refund table for customer credit.
Download to web storefront: You can download return reason codes to the web storefront if you enable customers to create return authorizations on the storefront. See Downloading E-Commerce Static Tables (ESTF) for more information on the download.
Uploading: You can use the Submit Supporting Data Upload Screen (SDUP) to upload new return reason codes. See Importing Item-Related Supporting Data (SDUP) for an overview.
Report: You can use the Return Reason Report to review the total number of units and dollars returned for a selected time period. See Printing the Return Reason Report (PRRR) for more information.
For more information: See Introducing Return Authorizations (WRTA) for an overview on returns.
In this topic:
- Work with Return Reason Screen
- Create Return Reason Screen
- Display Return Reason/Offer Screen (Reviewing History)
Work with Return Reason Screen
How to display this screen: Enter WRTR in the Fast path field or select Work with Return Reason from a menu.
Field | Description |
---|---|
Rsn (Return reason) |
Represents a reason for returning an item. Numeric, 3 positions; optional. |
Description |
The description associated with the return reason code. Alphanumeric, 30 positions; optional. |
Def (Defective) |
Indicates whether the return is defective. This field is informational only. Valid values:
|
Rtv (Return to vendor) |
Indicates whether you send the returned merchandise back to the vendor. Valid values:
|
Whs (Warehouse) |
Represents a warehouse to receive the returned merchandise. Warehouse codes are defined in and validated against the Warehouse table. Numeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Create a return reason code |
Select Create to advance to the Create Return Reason Screen. |
Change a return reason code |
Select Change for a code to advance to the Change Return Reason screen. You can change any information except the return reason code. See Create Return Reason Screen for field descriptions. To change the actual code, delete the record and create a new one. |
Delete a return reason code |
Select Delete for a code to delete it. If the return reason code has been used to return one or more items, a pop-up window indicates that history exists and requires confirmation. You will lose this history if you delete the return reason code. |
Display return reason code detail |
Select Display for a code to advance to the Display Return Reason screen. You cannot change any information on this screen. See Create Return Reason Screen for field descriptions. |
Display return reason history by offer |
Select Display Offers for a code to advance to the Display Return Reason/Offer Screen (Reviewing History). |
Create Return Reason Screen
To create: At the Work with Return Reason Screen, select Create.
Field | Description |
---|---|
Return reason code |
Represents a reason for returning merchandise. Numeric, 3 positions. Create screen: required. Change screen: display-only. |
Description |
The description associated with the reason code. Alphanumeric, 30 positions; required. |
Defective? |
This flag indicates whether the item is defective. This setting is informational only. Valid values:
|
Return to vendor |
This flag indicates whether you send the returned merchandise back to the vendor. Valid values:
|
Warehouse |
Represents the warehouse to receive the returned merchandise. This field is not currently implemented; the warehouse is determined by the return disposition value used on the return. See Establishing Return Disposition Values (WRDV). Numeric, 3 positions; optional. |
Display Return Reason/Offer Screen (Reviewing History)
Purpose: Use this screen to display return history by offer for a reason code.
How to display this screen: At the Work with Return Reason Screen, select Display Offers for a return reason.
How to interpret this screen: This screen displays return history associated with a reason code. Behind each reason code is a history table that indicates the number of items and dollars returned for the reason code. The History table matches each return with an offer (for example, a catalog) and the date of the return transaction.
About returns: The system updates this history each time you complete the return processing (that is, credit the return). Processing a return involves creating the return authorization, receiving the return into inventory, and processing the credit so that you can refund the customer, if necessary. When you process a return in order entry or order maintenance, these three steps occur at once “behind the scenes.” You can also break this process out into the three separate steps when you process returns through the e-commerce interface or the return authorizations options. See Introducing Return Authorizations (WRTA).
The information on this screen changes whenever the history table is updated. This screen displays summary data with return counts and dollars for each date on which item returns were processed. Summaries are listed by offer, then by date. You cannot change any of the information on this screen.
Field | Description |
---|---|
Return reason code |
Represents a reason for returning merchandise. Numeric, 3 positions; display-only. |
Offer |
Represents a catalog, space or television advertisement from which you accept orders. Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; optional. |
Date |
The date when the return processing was completed. Numeric, 6 positions (in user date format); optional. |
Number |
The number of units returned and credited. Numeric, 3 positions; display-only. |
Dollars |
The total value of returned merchandise. Alphanumeric, 13 positions with a 2-place decimal; display-only. |
Establishing Exchange Reason Codes (WEXR)
Purpose: Use the Exchange Reason Code screens to create and maintain reason codes for merchandise exchanges. The Return Authorization and Order Maintenance functions require an exchange reason code when you exchange merchandise.
The Exchange Reason table stores history by offer, and the system writes transactions to the Order History table whenever you perform an exchange.
Uploading: You can use the Submit Supporting Data Upload Screen (SDUP) to upload new exchange reason codes. See Importing Item-Related Supporting Data (SDUP) for an overview.
Report: You can use the Exchange Reason Report to review the total number of units and dollars returned for exchange in a selected time period. See Printing the Exchange Reason Report (PERR) for more information.
In this topic:
- Work with Exchange Reason Screen
- Create Exchange Reason Screen
- Display Exchange Reason/Offer Screen (Reviewing History)
Work with Exchange Reason Screen
How to display this screen: Enter WEXR in the Fast path field or select Work with Exchange Reasons from a menu.
Field | Description |
---|---|
Rsn (Exchange reason code) |
Represents a reason for exchanging merchandise. Numeric, 3 positions; optional. |
Description |
The description associated with the exchange reason code. Alphanumeric, 30 positions; optional. |
Def (Defective) |
Indicates whether the merchandise returned for exchange is defective or damaged. Valid values:
Optional. |
Rtv (Return to vendor) |
Indicates whether you send the returned merchandise back to the vendor. Valid values:
Optional. |
Whs (Warehouse) |
Represents a warehouse. Numeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Create an exchange reason code |
Select Create to advance to the Create Exchange Reason Screen. |
Change an exchange reason code |
Select Change for a code to advance to the Change Exchange Reason screen. See Create Exchange Reason Screen for field descriptions. To change the reason code, delete the record and create a new one. |
Delete an exchange reason code |
Select Delete for a code. If the exchange reason code has been used to exchange one or more items, a pop-up window indicates that there is history for the exchange reason code, containing information on number and dollar value of returns for that return reason by offer. See Display Exchange Reason/Offer Screen (Reviewing History). You will lose this history if you delete the exchange reason code. |
Display an exchange reason code |
Select Display for a code to advance to the Display Exchange Reason screen. You cannot change any information on this screen. See Create Exchange Reason Screen for field descriptions. |
Display exchange reason code history by offer |
Select Display Offers for a code to advance to the Display Exchange Reason/Offer Screen (Reviewing History). |
Create Exchange Reason Screen
To create: At the Work with Exchange Reason Screen, select Create.
Field | Description |
---|---|
Exchange reason code |
Represents a reason for exchanging merchandise. Numeric, 3 positions. Create screen: required. Change screen: display-only. |
Description |
The description associated with the exchange reason code. Alphanumeric, 30 positions; required. |
Defective |
Indicates whether the returned item is defective or damaged. Valid values:
|
Return to vendor? |
Indicates whether to return the merchandise back to the vendor. Valid values:
|
Warehouse |
Represents the warehouse to receive the returned merchandise. Warehouse codes are defined in and validated against the Warehouse table. This field is not currently implemented; the warehouse is determined by the return disposition value used on the return. See Establishing Return Disposition Values (WRDV). Numeric, 3 positions; optional. |
Display Exchange Reason/Offer Screen (Reviewing History)
Purpose: Use this screen below to display exchange reason/offer records.
How to display this screen: At the Work with Exchange Reason Screen, select Display Offers for an exchange reason code.
How to interpret this screen: This screen displays exchange history associated with a reason code.
Behind each reason code is a History table that indicates the number of units and dollar total in exchanges for the code. The system updates this History table whenever you accept an exchange through Order Maintenance or Return Authorization. The History table matches each exchange with an offer (for example, a catalog) and the date of the exchange transaction.
The information on this screen changes whenever the History table is updated. This screen displays summary data with exchange counts and dollars for each date on which exchanges were processed. Summaries are listed by offer, then by date. You cannot change any information on this screen.
Field | Description |
---|---|
Exchange reason code |
Represents a reason for exchanging merchandise. Numeric, 3 positions; display-only. |
Offer |
Represents a catalog, space or television advertisement from which you accept orders. Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; optional. |
Date |
The date when the exchange transaction occurred. Numeric, 6 positions (in user date format); display-only. |
Number |
The number of units exchanged. Numeric, 3 positions; optional. |
Dollars |
The value of exchanged merchandise. Numeric, 13 positions with a 2-place decimal; display-only. |
Establishing Return Disposition Values (WRDV)
Purpose: Use return disposition values to identify how a returned item will be handled by the system when you process a return through Return Authorizations, Order Entry or Order Maintenance.
- Does the return affect inventory? If the return disposition code affects inventory, the merchandise will be returned into active inventory and the system updates the on hand quantity for the specified location.
- Is the merchandise returned to its primary location? The system checks for a primary location and warehouse in the Item table. If a location and warehouse is defined in the Item table, the system returns the item automatically to this warehouse location. If a location has not been defined in the Item table or if the return disposition value is not set up to receive returns to the primary location, the system receives the return in the warehouse and location defined for the return disposition value.
- Does the user have authority to this return disposition value? You can set up authority to a specific return disposition value for a user or user class. If the user has authority to the return disposition code, the system processes the return. If the user does not have authority to the return disposition value, an error message indicates when you try to process the return.
In this topic:
- Work with Return Disposition Values Screen
- Create Return Disposition Screen
- Authority Hierarchy
- Work with User Field Authority Screen (Return Disposition Authority for Users)
- Work with User Class Field Authority Screen (Return Disposition Authority for User Classes)
Work with Return Disposition Values Screen
How to display this screen: Enter WRDV in the Fast path field at the top of a menu or select Work with Return Disposition Values from a menu.
Field | Description |
---|---|
Return code |
A code that identifies how the returned merchandise will be handled by the system, in terms of whether the return updates inventory and the warehouse and location to which the merchandise will be returned. Alphanumeric, 2 positions; optional. |
Description |
The description of the return disposition value. Alphanumeric, 30 positions; optional. |
Affect inv (Affect inventory) |
Determines whether the return affects the on-hand quantity. Valid values:
Optional. |
Use primary |
Indicates whether the item should be returned to its primary location. Valid values:
Optional. |
W/H (Warehouse) |
A code that identifies the warehouse where the item will be returned. Warehouse codes are defined in and validated against the Warehouse table. See Creating and Maintaining Warehouses (WWHS). Numeric, 3 positions; optional. |
Location |
A code that identifies the location within the warehouse where you place the item. Location codes are defined in and validated against the Location table. See Creating and Maintaining Locations (WLOC). Alphanumeric, 7 positions; optional. |
Screen Option | Procedure |
---|---|
Create a return disposition code |
Select Create to advance to the Create Return Disposition Screen. |
Change return disposition information |
Select Change for a return disposition value to advance to the Change Return Disposition screen. You can change any information on the Change Return Disposition screen except the disposition code itself. See Create Return Disposition Screen for field descriptions. To change the actual disposition code, you must delete the existing record and create a new one. |
Delete a return disposition code |
Select Delete for a return disposition value. |
Display a return disposition code |
Select Display for a return disposition value to advance to the Display Return Disposition screen. You cannot change any information on this screen. See Create Return Disposition Screen for field descriptions. |
Work with return disposition authority for users |
Select User Authority for a return disposition value to advance to the Work with User Field Authority Screen (Return Disposition Authority for Users). |
Work with return disposition authority for user classes |
Select User Class Authority for a return disposition value to advance to the Work with User Class Field Authority Screen (Return Disposition Authority for User Classes). |
Create Return Disposition Screen
Purpose: Use this screen to create a return disposition value.
How to display this screen: At the Work with Return Disposition Values Screen, select Create.
Field | Description |
---|---|
Code |
Represents the return disposition value. Return disposition values identify how returned merchandise will be handled by the system, in terms of whether the return updates inventory and the warehouse and location to which the merchandise will be returned. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the return disposition value. Alphanumeric, 30 positions; required. |
Affect inventory |
This flag identifies whether the returned merchandise will be returned into active inventory and update the on hand quantity in the specified location. Valid values are:
Note: If you deselect this setting, you must deselect the Use primary location setting. Also, you cannot enter values in the Warehouse or Location fields or the system displays the following message:Warehouse & location not required for Disp. code . |
Use primary location |
This flag indicates whether to return items to their primary locations. Valid values are:
|
Warehouse |
The default warehouse used for returns with this Return Disposition code. You must define a default warehouse if you selected the Affect inventory field. Note: The system uses this warehouse automatically if the Use primary location field is selected, but no primary warehouse is defined for the item/SKU.Warehouse codes are defined in and validated against the Warehouse table. See Creating and Maintaining Warehouses (WWHS). Numeric, 3 positions; required when Affect inventory field is selected. |
Location |
The default location used for returns with this Return Disposition code. You must define a default location if you selected the Affect inventory flag. Note: The system uses this location automatically if the Use primary location field is selected, but no primary location is defined for the item/SKU.Location codes are defined in and validated against the Location table. See Creating and Maintaining Locations (WLOC). Alphanumeric, 7 positions; required when Affect inventory field is selected. |
Authority Hierarchy
Purpose: You can use the Work with Return Disposition Values menu option to set user or user class authorities to specific return disposition values. The settings you enter through this menu option are overrides to defaults set at a higher level.
General guidelines:
Authority Setting | Set Up Through: |
---|---|
1. user's authority to the specific return disposition value |
Work with User Field Authority Screen (Return Disposition Authority for Users) |
2. user's user class authority to the specific return disposition value |
Work with User Class Field Authority Screen (Return Disposition Authority for User Classes) |
3. user's authority to the Return Disposition Code Authority (A83) secured feature |
Work with User Class Field Authority Screen (Return Disposition Authority for User Classes) in Work with User Classes (fast path = WUCL); also available by selecting W/W User Classes in Work with Users |
4. user's user class authority to the Return Disposition Code Authority (A83) secured feature |
Work with User Class Field Authority Screen (Return Disposition Authority for User Classes) in Work with User Classes (fast path = WUCL); also available by selecting W/W User Classes in Work with Users |
5. default setting of the Return Disposition Code Authority (A83) secured feature |
Work with System Features screen in Work with System Values/Features (fast path = WSYS) |
The system checks each setting in the above order, skipping over any blank settings until it finds a Allow or Exclude setting.
Example One: User BMIRANDA is assigned to the user class WAREHOUSE. The Return Disposition Code Authority (A83) secured feature is set to Allow. The WAREHOUSE user class authority for return disposition value 4A is set to Exclude. BMIRANDA's user authority for return disposition value 4A is set to Allow. The result is that BMIRANDA can process a return using the 4A return disposition value, because her user authority overrides the other settings. However, the other users in the WAREHOUSE user class cannot process a return user the 4A return disposition value, unless they also have an override at the user level.
Example Two: User TBROWN has a Return Disposition Code Authority (A83) secured feature setting of Exclude. However, the user settings for the 4A and 4B return disposition values only are set to Allow. This user is not assigned to a user class. The result is that TBROWN can process a return using return disposition values 4A and 4B only, but is excluded from processing a return using any other return disposition values.
Work with User Field Authority Screen (Return Disposition Authority for Users)
Purpose: Use this screen to review or change a user's authority to a specific return disposition value.
How to display this screen: Select User Authority for a return disposition value at the Work with Return Disposition Values Screen.
Field | Description |
---|---|
Return disposition |
The return disposition value you selected at the Work with Return Disposition Values Screen. The description displays to the right. Value: alphanumeric, 2 positions; display-only. Description: alphanumeric, 30 positions; display-only. |
User |
The user ID of a person within your company. Alphanumeric, 10 positions; optional. |
Name |
The user's name. Alphanumeric, 30 positions; optional. |
Authority |
The user's authority to process a return using the return disposition value specified. Valid values are:
Optional. |
User class authority |
The authority of the user's class to process a return using the return disposition value specified. Value values are:
Optional. |
Resetting User Authority
To delete: Select Delete for a user ID.
If you delete a user's user-level authority, the user class-level authority setting for this return disposition value, if any, will be in effect; if there is no user class setting, the system checks the setting of the Return Disposition Code Authority (A83) secured feature at the user, user class, and default levels in order. See Authority Hierarchy.
If the user did not have a user-level authority setting for this return disposition value, the screen does not display an error message; however, no changes take place.
Set to ALLOW: Select Allow for a user ID. The user will be able to process a return using the specified return disposition value.
If the user already had authority to this return disposition value, the screen does not display an error message; however, no changes take place.
Set to EXCLUDE: Select Exclude for a user ID. The user will not be able to process a return using this return disposition value.
If the user already is excluded from this return disposition value, the screen does not display an error message; however, no changes take place.
Work with User Class Field Authority Screen (Return Disposition Authority for User Classes)
Purpose: Use this screen to review or work with the authority settings to a selected return disposition value by user class.
How to display this screen: Select User Class Authority for a return disposition value at the Work with Return Disposition Values Screen.
Field | Description |
---|---|
Return disposition |
The return disposition value you selected at the Work with Return Disposition Values Screen. The description displays to the right. Value: alphanumeric, 2 positions; display-only. Description: alphanumeric, 30 positions; display-only. |
Class |
A user class within your company. Alphanumeric, 10 positions; optional. |
Description |
The description of a user class. Alphanumeric, 30 positions; optional. |
Authority |
The user class's authority to process a return using the return disposition code specified. Valid values are:
Optional. |
Resetting User Class Authority
To delete: Select Delete for a user class.
If you delete a user class's authority, and if there is no user-level setting for the return disposition value, the system checks the setting of the Return Disposition Code Authority (A83) secured feature at the user, user class, and default levels in order. See Authority Hierarchy.
If the user class did not have an authority setting for this return disposition value, the screen does not display an error message; however, no changes take place.
To set to ALLOW: Select Allow for a user class. The user in this user class will be able to process a return using this return disposition value, unless the authority setting for an individual user is set to Exclude.
If the user class already had authority to this return disposition value, the screen does not display an error message; however, no changes take place.
Set to EXCLUDE: Select Exclude for a user class. The users in this class will not be able to process a return using this return disposition value, unless the authority setting for an individual user is set to Allow.
If the user class already is excluded from this return disposition value, the screen does not display an error message; however, no changes take place.
Establishing Custom Special Handling Formats (WSHF)
Purpose: Use the Special Handling Format table to define the contents of the custom special handling screen that displays in Order Entry. Custom special handling differs from standard special handling in that you can define required fields, offer additional features with a special charge, and specify valid values for input fields that the system will validate in Order Entry.
Overview: To display the custom special handling screen in Order Entry, you must first define the format. You then associate the format with an additional charge code. You can then define that additional charge code for the Item/Offer or Item/SKU/Offer.
See Special Handling Overview for more information on how special handling works.
Setup: There are three basic steps to setting up a custom special handling format:
- Select Create on the Work with Special Handling Format Screen to define the new format.
- Select Work with details for the new format to define the fields to display in Order Entry, then select Create to create each field.
- Enter valid responses for each field that you want the system to validate in Order Entry. Later, you can designate a default response by using the Change option on the Work with Special Handling Format Detail Screen.
Suppressing screen display in order entry: You can use the Suppress S/H window for the additional charge code to prevent the Work with Custom Special Handling Screen from opening automatically in order entry. You might want to suppress display in order to automatically add a charge to the Handling bucket on an order without requiring the order entry operator to complete or accept the information on the special handling screen.
Sending custom special handling instructions in the order API: See the personalization_line element in the CWOrderIn message for information on how to pass custom special handling instructions through the order API in the Web Services Guide on My Oracle Support (ID 2149144.1).
In this topic:
- Work with Special Handling Format Screen
- Create Special Handling Format Screen
- Work with Special Handling Format Detail Screen
- Create Special Handling Format Detail Screen
- Work with Special Format Response Screen
- Work with Special Format Rules Screen
For more information:
- Special Handling Overview
- associating a custom special handling format with an additional charge code or suppressing the display of the special handling screen in order entry: Establishing Additional Charge Codes (WADC)
- working with item offers and item/SKU offers: Performing Initial Item Entry (MITM)
- system control values that affect special handling:
- Secured features:
- entering an item with custom special handling on an order: Work with Special Handling Screen
Work with Special Handling Format Screen
How to display this screen: Enter WSHF in the Fast path field at the top of any menu, or select Work with Special Handling Format from a menu.
Field | Description |
---|---|
Code |
This code identifies the special format. Alphanumeric, 2 positions; optional. |
Description |
The description of the special format. Alphanumeric, 30 positions; optional. |
Status |
A code used to indicate whether the special format is active. Valid codes are:
The system issues a message in Order Entry when you enter an item that uses an inactive special handling format and it will not accept the item on the order. Required. |
Extract |
Controls whether the system will include items to receive this type of special handling in extract files. If an outside service performs special handling for you, you might want to use these tables to transmit the information to them. The system generates these tables when you generate pick slips. In order to generate the tables for custom special handling items, both this field and the Generate Custom Special Handling File (D66) system control value must be selected. Valid values:
Optional. |
Hold |
Indicates whether to automatically put an order line on hold when it uses this special handling format. YES = When you create an order line using this format, or apply this format to an existing order line, the system puts the order line on hold. NO = The system does not automatically put an order line on hold when it uses this special handling format. See Putting a Line on Hold through a Special Handling Format. |
Screen Option | Procedure |
---|---|
Create a special handling format |
Select Create to advance to the Create Special Handling Format Screen. |
Change a special handling format |
Select Change for a special handling format to advance to the Change Special Handling Format screen. You can change any information on this screen except the format code. See Create Special Handling Format Screen for field descriptions. You can change or delete a special handling format at any time without affecting existing orders. |
Delete a special handling format |
Select Delete for a special handling format. |
Display a special handling format |
Select Display for a special handling format to advance to the Display Special Handling Format screen. You cannot change any information on this screen. See Create Special Handling Format Screen for field descriptions. |
Change, delete, display or create the actual screen format, or define appropriate responses for fields on the custom special handling screen |
Select Work with details for a special handling format to advance to the Work with Special Handling Format Detail Screen. |
Create Special Handling Format Screen
Purpose: At this screen, you can create and define the characteristics of a custom special handling screen.
How to display this screen: Select Create at the Work with Special Handling Format Screen.
Field | Description |
---|---|
S/H format code (Special handling format code) |
A code to identify the special format. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the special format. Alphanumeric, 30 positions; required. |
Status |
This code indicates if the special format is active. Valid values:
The system issues a message in Order Entry when you enter an item that uses an inactive special handling format and it will not accept the item on the order. Required. |
S/H extract |
This flag controls whether the system will include items to receive this type of special handling in extract files. If an outside service performs special handling for you, you might want to use these tables to transmit information to them. The system generates these tables when you generate pick slips. In order to generate the tables for custom special handling items, both this field and the Generate Custom Special Handling File (D66) system control value must be selected.
|
S/H hold |
Indicates whether to automatically put an order line on hold when it uses this special handling format. Selected = When you create an order line using this format, or apply this format to an existing order line, the system puts the order line on hold. Unselected = The system does not automatically put an order line on hold when it uses this special handling format. See Putting a Line on Hold through a Special Handling Format. |
Work with Special Handling Format Detail Screen
Purpose: Use this screen to create, change, display, or delete the actual format of a custom special handling screen or to define appropriate responses for fields on the screen.
How to display this screen: Select Work with details for a special handling format at the Work with Special Handling Format Screen.
Field | Description |
---|---|
Special format code |
A code used to identify the special format, carried over from the Work with Special Handling Format Detail Screen. You enter this code in the S/H format field in the Additional Charge Code table to link a custom special handling format screen to a type of special handling. The description associated with the special handling format appears to the right of the code. Alphanumeric, 2 positions; display-only. |
Field label |
The name of the input field as it appears on the Work with Custom Special Handling Screen in Order Entry. Alphanumeric, 15 positions; display-only. |
Valid responses |
The valid values you have defined for the input field. If the field will accept any response in Order Entry without validation, this field will be blank on the Work with Special Handling Format Screen. Responses appear on this screen separated by commas. The Work with Special Handling Format screen may not display all responses if there is not sufficient room. Alphanumeric, 45 positions; display-only. |
Default response |
The value to appear automatically in the input field on the special handling screen in Order Entry. Enter the same response in the Valid responses field, above. You can override the default value in order entry. Alphanumeric, 25 positions; display-only. |
F/O (Feature option) |
Indicates whether the input field is a feature option. A feature option is an extra feature that can be added to the item, possibly for an additional charge. Define the price and cost for the custom special handling in a required feature option field to add the base price of the special handling to the order and the base cost to the drop ship purchase order. You can also define additional feature options, with or without additional costs; the price and/or cost will be added to the order as long as you enter a valid value in the input field in order entry.
Display-only. |
Req (Required) |
Indicates whether entry in the input field is required in Order Entry.
Display-only. |
Default text |
This code allows you to select text from the Customer Sold-to table to default onto a Custom Special Handling Detail Line in Order Entry/Order Maintenance. Each code is associated with specific text. For example, selecting code 4 will default the first name, middle initial and last name of the sold-to customer onto a special handling detail line. The first 14 characters of the description appear to the right of the default text code. Any default text overrides valid responses. You cannot use default responses. Valid values are:
|
Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number on screens and reports.Display-only. |
Screen Option | Procedure |
---|---|
Add a field to the custom special handling format screen |
Select Create to advance to the Create Special Handling Format Detail Screen. |
Change a field on the custom special handling format screen |
Select Change for a field to advance to the Change Special Handling Format Detail screen. You can change any information on this screen except the format code. See Create Special Handling Format Detail Screen for field descriptions. |
Delete a field on the custom special handling format screen |
Select Delete for a field. |
Display a field on the custom special handling format screen |
Select Display for a field to advance to the Display Special Handling Format Detail screen. You cannot change any information on this screen. See Create Special Handling Format Detail Screen for field descriptions. |
Change, delete, display or create the appropriate responses for a field on the custom special handling screen |
Select Responses for a field to advance to the Work with Special Format Response Screen. |
Change, delete, display, or create rules that control the application of special handling details for an item on an order |
Select Rules for a field to advance to the Work with Special Format Rules Screen. |
Adjust the sequence of the fields on the custom special handling screen |
Select Resequence to update the structure of the custom special handling screen based on the specified sequence. |
Create Special Handling Format Detail Screen
Purpose: At this screen, you can define the characteristics of a field that appears on the custom special handling screen.
How to display this screen: At the Work with Special Handling Format Detail Screen, select Create.
Field | Description |
---|---|
Special format code |
A code used to identify the special format, carried over from the Work with Special Handling Format Detail Screen. You enter this code in the S/H format field in the Additional Charge Code table to link a custom special handling format screen to a type of special handling. The description associated with the special handling format appears to the right of the code. Alphanumeric, 2 positions; display-only. |
Display sequence |
This code controls the order in which the input fields display on the Work with Custom Special Handling Screen in order entry. The fields display in ascending numeric sequence. Numeric, 3 positions; required. |
Field label |
The name of the input field as it appears on the Work with Custom Special Handling Screen in order entry. Alphanumeric, 15 positions; required. |
Required field |
This flag indicates whether entry in the input field is required in order entry.
|
Feature option |
This flag indicates whether the input field is a feature option. A feature option is an extra feature that can be added to the item, possibly for an additional charge. Define the price and cost for the custom special handling in a required feature option field to add the base price of the special handling to the order and the base cost to the drop ship purchase order. You can also define additional feature options, with or without additional costs; the price and/or cost will be added to the order as long as you enter a valid value in the input field in order entry.
|
Default price |
Use this field to define the unit price to charge the customer for the feature option. This amount defaults to the Work with Custom Special Handling Screen in order entry if the Feature option flag is selected. Except in the case of an override as listed below, the system adds this price to the total handling charge on the order if the customer purchases the feature option. You can override the default price:
|
Note: The Evaluate Special Handling Charges by Order Line (D67) system control value controls whether the handling charge added to the order is based on the number of order lines with special handling or on the total unit quantity.You can enter a price only if the Feature option flag is selected and the Default price % field is blank. This is not a required field, even for feature options. Numeric, 13 positions with a 2-place decimal; optional. |
|
Default price % |
Use this field to define the percentage used to calculate the price of the feature option. Except in the case of an override as listed below, the system adds this price to the total handling charge on the order if the customer purchases the feature option. The percentage is calculated based on the selling price of the item. You can override the default price:
Note: The Evaluate Special Handling Charges by Order Line (D67) system control value controls whether the handling charge added to the order is based on the number of order lines with special handling or on the total unit quantity.You can enter a price percentage only if the Feature option flag is selected and the Default price field is blank. Numeric, 13 positions with a 2-place decimal; optional. |
Default cost |
The unit cost of the feature option for drop ship purchase orders. This cost does not display in order entry or on pick slips; it is the amount that you pay the vendor for the special handling. Note: When a special handling format is set to suppress display in order entry, the system creates a purchase order detail line for the special handling only if there is a default response specified for the special handling detail line.You can complete this field only if the Feature option flag is selected and the Default cost % field is blank. Numeric, 13 positions with a 4-place decimal; optional. |
Default cost % |
A percentage used to compute the cost of the item for drop ship purchase orders, determined as follows: Cost percentage * Item cost = Unit cost This cost does not display in order entry or on pick slips; it is the amount that you pay the vendor for the special handling. Note: When a special handling format is set to suppress display in order entry, the system creates a purchase order detail line for the special handling only if there is a default response specified for the special handling detail line.You can complete this field only if the Feature option flag is selected and the Default cost field is blank. Numeric, 5 positions with a 2-place decimal; optional. |
Default text |
Allows you to select text from the customer record to default onto a custom special handling detail line in order entry. Each code is associated with specific text. For a list of the codes and the default text associated with each code, see Work with Special Handling Format Detail Screen. Optional. |
Max # characters |
Indicates the maximum number of characters allowed for this special handling detail line. You can define any number from 0 to 45. If you define 0 as the maximum number, it is treated as a blank field and allows the maximum 45 characters to be used. The value you select will display to the right of this field. Text cannot exceed the maximum number of characters allowed in the special format detail table. A message similar to the following displays if your entry exceeds the maximum number of characters allowed in the special format detail table: Exceeds Maximum Characters Allowed If the Include Spaces in Special Handling Edit for Maximum Characters (F80) system control value is selected, the system includes spaces in the edit to determine the maximum number of characters allowed for a custom special handling input field. |
Example: When this system control value is selected, the Exceeds Maximum Characters Allowed error message indicates if a user enters Paws and Claws Limited Supplies in an input field that is set up with a maximum character length of 30 positions. If this system control value is unselected, the system would not display the error message since the number of characters not including spaces is 27. Numeric, 2 positions; optional. |
|
Cross reference |
A code used to cross reference between the special handling format detail in Order Management System and the element's code on the manufacturing system. The manufacturing system records this cross reference code in the Order Special Format table when a special format defined with this code is used in order entry. Alphanumeric, 3 positions; optional. |
Work with Special Format Response Screen
Purpose: Use this screen to create, change or delete valid responses of fields that appear on the custom special handling screen.
You need to enter responses only if you want the system to validate responses for this field in order entry. Any default text used overrides valid responses in Order Entry/Order Maintenance. Otherwise, this screen displays only free-form entry fields for valid responses. Enter one response per line.
How to display this screen: This screen appears automatically after you create a Special Handling Format Detail record. You can also display this screen by selecting Responses for an existing Detail record at the Work with Special Handling Format Detail Screen.
Defining responses: To create valid responses for a field on the custom special handling screen, enter one desired response(s) per line. A second line, labeled desc, is available under the first line for entry of the description of the valid response. This description is displayed in order entry if the Display Special Format Response Descriptions in Order Entry (E90) system control value is selected.
Entering response descriptions is helpful if you use codes to represent valid responses. For example, if you identify the color black with the code 8859, order entry operators can identify code 8859 as black by referring to the valid response description field.
Note:
If the Enter Custom Special Handling in Upper and Lower Case (D65) system control value is selected, you can enter case-sensitive responses in this field in Order Entry.You can define an unlimited number of responses for a field by selecting Next to display additional input fields on the Work with Special Format Response screen (not all responses may appear, however, on the Work with Special Format Detail screen).
If you enter any valid responses on this screen, the system validates responses in Order Entry against your entries here.
Responses for feature options: When defining responses for a feature option, remember that the system adds the price defined for the feature option to the order if you enter any valid response in Order Entry.
You can use a required feature option to add the price of the basic special handling to the order. You can then add additional feature options if desired, with or without associated prices.
Identifying a default response: You can define a default response for the field by selecting Change for the detail record. Enter the desired default in the Default response field on the Change Special Format screen. The system validates your entry against the responses you have previously defined for the field.
Displaying responses: Select Responses for a Detail record at the Work with Special Handling Format Detail Screen to review the valid responses for a field on the custom special handling screen.
Changing or deleting: Select Resequence at the Work with Special Format Response Screen to update or delete a response.
Type over the existing value to update the response or Tab through the response to delete it.
Work with Special Format Rules Screen
Purpose: Use this screen to work with rules to validate the custom special handling instructions for order lines that use a particular custom special handling format.
Why set up rules? Setting up rules for a complex special handling format helps you prevent the customer or CSR from entering special handling instructions that are inconsistent, impractical, or otherwise invalid. For example, for if monogramming is optional, but there are additional requirements when monogramming is selected, setting up rules can help prevent problems in creating the special handling instructions.
What do rules consist of? Each rule includes:
- an IF statement that identifies whether the rule applies, for example: If the pocket style for a shirt is equal to “no pocket”
- a THEN statement that specifies the rule to apply, for example: then the monogram location cannot be “pocket”
More rule examples:
- If the cuff type for a shirt is any value (not blank), then the sleeve length must not be 0 (short sleeve)
- If the cuff type for a shirt is blank (no cuff style specified), then the sleeve length must be 0 (short sleeve)
- If the monogram for a shirt is any value (not blank), then the monogram style must also be any value (not blank)
What if the special handling format violates a rule?
- Order entry: When you select Accept at the Work with Custom Special Handling Screen, the screen displays an error message such as MGM LOCATION - center pocket response is not valid for POCKET - no pocket. You need to fix the error before accepting the special handling for the item. If there are multiple errors, the screen displays each error individually, and you need to fix each error before accepting.
- Order API: If the special handling instructions do not conform to a rule, the order line is put in error status with an error code of GA: SH Resp fail defined rule.
Note:
All existing validation, such as maximum number of characters, still occurs when you use special handling format rules.Setting up rules is optional.

Field | Description |
---|---|
Special format code |
The code and description of the special handling format that you selected from the Work with Special Handling Format Screen. Code: alphanumeric, 2 positions; display-only. Description: alphanumeric, 30 positions; display-only. |
IF statement |
The IF statement determines whether to apply the rule. |
If special handling detail |
The Field label for the special handling detail you selected at the Work with Special Handling Format Detail Screen. The IF statement must be based on the selected detail. Alphanumeric, 15 positions; display-only. |
IS |
The test you are using to evaluate whether the special handling rule applies. Possible tests are: Any Value = Apply the rule if the entry for the special handling detail for the order line is not blank Blank = Apply the rule if there is no entry for the special handling detail on the order line Not Equal To = Apply the rule unless the entry for the order line matches the value for the IS statement Equal To = Apply the rule if the entry for the order line matches the value for the IS statement |
Value |
The response you are using to qualify the special handling rule based on whether the special handling entry matches or does not match a particular value. You can specify a response value only if the IS operator is set to Not Equal To or Equal To. Typically, you use this field to select one of the responses you set up at the Work with Special Format Response Screen. Example: Apply the rule if the pocket style is equal to “no pocket,” where:
You cannot enter a value here if the IS operator is set to Any Value or Blank.
|
THEN statement |
The THEN statement defines the rule to apply. |
Then special handling detail |
Select the Field label for the special handling detail that is affected by the rule. Example: If the font is blank, then the monogram must be blank, where:
You can select the Field label for any of the special handling details set up for the custom special handling format you are working with except for the IF special handling detail. |
MUST BE |
The operator that applies to the entry for the Then special handling detail. Possible operators are: Any Value = The entry for the Then special handling detail cannot blank Blank = The entry for the Then special handling detail must be blank Not Equal To = The entry for the Then special handling detail must not match the value for the THEN statement Equal To = The entry for the Then special handling detail must match the value for the THEN statement |
Value |
The response that either must match (Equal To) or cannot match (Not Equal To) the response on the order. If the MUST BE operator is set to Not Equal To or Equal To, use this field to select one of the responses you set up at the Work with Special Format Response Screen. Example: The cuff style must be equal to “no cuff” where:
You cannot select a value here if the IS operator is set to Any Value or Blank.
|
Establishing Add Reason Codes (WADR)
Overview: Use the Add Reason Code table to establish codes for tracking the reasons you add items to orders in Order Entry or Order Maintenance. Examples of reasons for adding items to an order include:
- mis-shipments
- exchanges
- allowing the customer to select a different item or SKU for a backordered item
- the item is a warranty part
You might want to track this information to identify problem areas, and focus your training or quality control efforts.
Required when? The system requires an add reason code if the:
- Require Reason for Lines Added in Order Maintenance (D75) system control value is selected, or
- Required reason code flag for the item offer or SKU offer is selected.
Pop-up window: When an operator adds an item by selecting Create, entering an exchange, or adding a mis-ship to an order in order maintenance, the Enter Add Reason Window pop-up window opens.
Note:
When the item is added automatically to an order through the order API, the add reason code is not required. For example, an item might be added to an order automatically if it is set up as a free gift by source code.Report: You can review add reason codes assigned to new order lines with the Order Addition Audit Report.
In this topic:
For more information:
- reviewing the add reason code for an order line: Display Order Line History Screen
- adding an item to an order: Adding an Item in Order Maintenance
Work with Add Reason Screen
How to display this screen: Enter WADR in the Fast path field at the top of any menu or select Work with Add Reason Codes from a menu.
Field | Description |
---|---|
Reason |
This code represents the reason for adding an item to an order in order entry or order maintenance. Alphanumeric, 5 positions; optional. |
Description |
The description of the add reason. Alphanumeric, 30 positions; optional. |
Screen Option | Procedure |
---|---|
Create an add reason code |
Select Create to advance to the Create Add Reason Screen. |
Change an add reason code |
Select Change for an add reason code to advance to the Change Add Reason screen. You can change only the reason description. See Create Add Reason Screen for field descriptions. |
Delete an add reason code |
Select Delete for an add reason code. |
Display an add reason code |
Select Display for an add reason code to advance to the Display Add Reason screen. You cannot change any information on this screen. See Create Add Reason Screen for field descriptions. |
Create Add Reason Screen
Purpose: Use this screen to create an add reason code.
How to display this screen: Select Create at the Work with Add Reason Screen.
Field | Description |
---|---|
Order addition reason code |
A code to identify the reason for adding an item reason code to an order in order entry or order maintenance, such as a mis-ship or exchange. Alphanumeric, 5 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the add reason. Alphanumeric, 30 positions; required. |
Working with Order Inquiry Reason Codes (WORC)
Purpose: Order inquiry reason codes allow you to define the reason why a CTI operator advanced to standard order inquiry or order maintenance from the Customer Selection Screen.
You can use order inquiry reason codes to determine why customers are inquiring about their orders or requesting maintenance on their orders. For example, if customers are inquiring about when they can expect to receive the merchandise on their orders, you can train your order entry operators to inform the customers of the expected delivery date.
Note:
You can enter an order inquiry reason code only if you advance to standard (not streamlined) order inquiry or order maintenance from the Customer Selection Screen, and system control value Require Reason in CTI (G98) is selected. In this case a window displays requiring an order inquiry reason code when you return to the CTI Customer Selection screen after using order inquiry or order maintenance. If you advance to order inquiry from the Order Inquiry Scan Screen or you advance to order maintenance from the Select Customer Sold To For Order Screen, the system will not allow you to enter an order inquiry reason code.You must set up Order Inquiry Reason codes before advancing to the Order Inquiry Reason code window. If you advance to this window and have no valid Order Inquiry Reason codes to enter, you will not be able to exit the window.
About CTI Customer Selection screen: This screen allows you to review a customer’s address information and order history before entering, maintaining, or reviewing an order. In order to advance to this screen:
- the Use Computer Telephony Integration (F26) system control value must be selected
- the CTI user flag in Working with User Records (WUSR) is selected
- the CTI default screen field in Work with User Records (WUSR) is set to Always display CTI screen or Display CTI scrn w/call.
How do order inquiry reasons relate to the order? When you define an order inquiry reason code after maintaining or reviewing an order, the system does not assign the order inquiry reason code to the order. Instead, the system tracks the number of times a specific user maintained or reviewed an order or orders associated with a specific line of business for a specific date and a specific order inquiry reason. You can review order inquiry reason history at the Order Inquiry Reason History Screen.
In this topic:
- Order Inquiry Reason Codes Window
- Work with Order Inquiry Reason Screen
- Create Order Inquiry Reason Screen
- Order Inquiry Reason History Screen
Order Inquiry Reason Codes Window
Purpose: Use this window to enter the reasons why the order was maintained or reviewed. You can enter up to five order inquiry reason codes.
How to display this window: If the Require Reason in CTI (G98) system control value is selected and you do not have authority to the Bypass CTI Reason Code (B24) secured feature, the system displays the Order Inquiry Reason Codes window when you return to the Customer Selection Screen from order inquiry or order maintenance.
Note:
You can prompt on a reason code field by clicking the Prompt arrow to display valid reason codes, but you cannot create a reason code at the selection screen. To create reason codes, you must use the Create Order Inquiry Reason Screen.Field | Description |
---|---|
Order inquiry reason codes |
A code to define the reason why a CTI operator advanced to order inquiry or order maintenance from the CTI Customer Selection screen. A message displays if you do not enter at least one order inquiry reason code: At least one field must be entered to continue. Order inquiry reason codes are defined in and validated against the Order Inquiry Reason Code table. Alphanumeric, five 3-position fields; required. |
Work with Order Inquiry Reason Screen
Purpose: Use this screen to work with order inquiry reason codes.
How to display this screen: Enter WORC in the Fast path field at the top of a menu or select Work with Order Inquiry Reason from a menu.
Field | Description |
---|---|
Reason code |
A code to define the reason why a CTI operator advanced to order inquiry or order maintenance from the CTI Customer Selection screen. Order inquiry reason codes are defined in and validated against the Order Inquiry Reason Code table. Alphanumeric, 3 positions; optional. |
Description |
A description of the order inquiry reason. Alphanumeric, 30 positions; optional. |
Cost |
The cost to your company for the CTI operator to review or maintain the order. This field is informational only. Numeric, 13 positions with a 4-place decimal; display-only. |
Screen Option | Procedure |
---|---|
Change an order inquiry reason code |
Select Change for a code to advance to the Change Order Inquiry Reason screen. At this screen, you can change every field except the Order inquiry reason code field. See Create Order Inquiry Reason Screen for field descriptions. |
Delete an order inquiry reason code |
Select Delete for a code to delete it. Note: The system allows you to delete an order inquiry reason code even if order inquiry reason history exists. If you delete the code, you will lose the history related to this order inquiry reason. |
Display an order inquiry reason code |
Select Display for a code to advance to the Display Order Inquiry Reason screen. You cannot change any fields on this screen. See Create Order Inquiry Reason Screen for field descriptions. |
Review order inquiry reason history |
Select History for a code to advance to the Order Inquiry Reason History Screen. |
Create an order inquiry reason code |
Select Create to advance to the Create Order Inquiry Reason Screen. |
Create Order Inquiry Reason Screen
Purpose: Use this screen to create an order inquiry reason code.
How to display this screen: Select Create at the Work with Order Inquiry Reason Screen.
Field | Description |
---|---|
Order inquiry reason code |
A code to define the reason why a CTI operator advanced to order inquiry or order maintenance from the CTI Customer Selection screen. Order inquiry reason codes are defined in and validated against the Order Inquiry Reason Code table. Alphanumeric, 3 positions. Create screen: required. Change screen: display-only. |
Description |
A description of the order inquiry reason. Alphanumeric, 30 positions; required. |
Cost |
The cost to your company for the CTI operator to review or maintain the order. This field is informational only. Numeric, 13 positions with a 4-place decimal; display-only. |
User field |
An informational field where you can enter additional order inquiry reason information. Alphanumeric, 3 positions; optional. |
Order Inquiry Reason History Screen
Purpose: Use this screen to review history for a specific order inquiry reason code.
You can review:
- each day this reason code was used for an order or orders
- the CTI operator who entered the reason
- the number of times this operator reviewed or maintained an order or orders for a specific date and line of business
- the line of business associated with the order or orders for a specific date and CTI operator
How to display this screen: Select History for an order inquiry reason code at the Work with Order Inquiry Reason Screen.
Field | Description |
---|---|
Order inquiry reason code |
The code and description for the reason why a CTI operator advanced to order inquiry or order maintenance from the CTI Customer Selection screen. Order inquiry reason codes are defined in and validated against the Order Inquiry Reason Code table. Code: Alphanumeric, 3 positions; display-only. Description: Alphanumeric, 30 positions; display-only. |
Date |
The date when this code was used as the reason for maintaining or reviewing an order(s). Numeric, 6 positions (in user date format); optional. |
User |
The user ID of the person who maintained or reviewed the order(s) and used this order inquiry reason code. Alphanumeric, 10 positions; display-only. |
Number |
The number of times an order(s) was maintained or reviewed on a specific date by a specific user for this order inquiry reason code. Numeric, 5 positions; display-only. |
LOB (line of business code) |
The line of business code associated with the order(s) maintained or reviewed on a specific date by a specific user for this order inquiry reason code. A line of business represents a client or business unit in Order Management System. These codes contain assignments that represent a specific entity, division, or offer, or a combination of these values. Each order is assigned a specific line of business, based on the entity, division, and offer associated with the order. See Working with Lines of Business (WLOB). Alphanumeric, 3 positions; optional. |
Working with Order/Call Disposition Reject Reason Codes (WWRR)
Purpose: Order/call disposition reject reason codes allow you to define the reason why an order entry operator rejected an order an ended a call received from an external order call center before an order was placed.
You can use the order/call disposition reject reason codes to determine why the order or call was rejected.
To assign an order/call disposition reject reason code to an order or call: The setting of the Capture Order/Call Disposition (K03) system control value controls when the system requires an order/call disposition reject reason code.
- If set to ORDER, the system requires you to enter an order/call disposition reject reason code at the Confirm Order/Call Disposition Window when you reject from an order in interactive Order Entry. Note: Interactive order entry in this situation does not include batch order entry, web orders, or membership orders.
- If set to ALL, the system requires you to enter an order/call disposition reject reason code at the Confirm Order/Call Disposition Window when you:
- reject from an order in interactive Order Entry.
- end a call received from an external order call center or select Exit at the Select Customer Sold To For Order Screen if a Universal call ID has been captured for the call in the Order Disposition table.
- If set to NONE or blank, you cannot assign an order/call disposition reject reason code to an order.
To view the reject reason assigned to an order or call: When you assign an order/call disposition reject reason code to an order or call, the system creates a record in the Order Disposition table. Note: You cannot view the information in the Order Disposition table from any Order Management System screen; see Order Disposition Table for a description of the fields in this table.
Work with Reject Reason Screen
Use this screen to work with order/call disposition reject reason codes.
How to display this screen: Enter WWRR in the Fast path field at the top of a menu or select Work with Reject Reasons from a menu.
Field | Description |
---|---|
Reason |
A code to define the reason why an order entry operator rejected an order an ended a call from an external order call center before an order was placed. Order/call disposition reject reason codes are defined in and validated against the Reject Reason table. Enter a reason code and select OK to display reason codes in alphanumeric sequence, beginning with your entry. Alphanumeric, 2 positions; optional. |
Description |
A description of the order/call disposition reject reason. Enter a full or partial description and select OK to display reject reasons that contain your entry. Alphanumeric, 30 positions; optional. |
Screen Option | Procedure |
---|---|
Create an order/call disposition reject reason |
Select Create to advance to the Create Reject Reason Screen. |
Change an order/call disposition reject reason |
Select Change for an order/call disposition reject reason to advance to the Change Reject Reason screen. At this screen, you can change the Description. See Create Reject Reason Screen for field descriptions. |
Display an order/call disposition reject reason |
Select Display for an order/call disposition reject reason to advance to the Display Reject Reason screen. You cannot change any fields on this screen. See Create Reject Reason Screen for field descriptions. |
Delete an order/call disposition reject reason |
Select Delete for an order/call disposition reject reason to delete it. The system allows you to delete an order/call disposition reject reason even if it has been assigned to an order or call. |
Create Reject Reason Screen
Purpose: Use this screen to create an order/call disposition reject reason code.
How to display this screen: Select Create at the Work with Reject Reason Screen.
Field | Description |
---|---|
Order reject reason code |
A code to define the reason why an order entry operator rejected an order an ended a call from an external order call center before an order was placed. Order/call disposition reject reason codes are defined in and validated against the Reject Reason table. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
A description of the order/call disposition reject reason. Alphanumeric, 30 positions; required. |
Working with Default Messages (WMSG)
Default messages are standard order or gift messages that you enter on orders on a regular basis. Instead of requiring users to retype a standard message on each eligible order, you can have the user select the message from a list of standard messages to default to the order, allowing you to avoid typographical errors that can occur when the message is manually added to the order. You can create default messages for order level messages and line level messages. When a user selects a default message to add to an order, the message text defined for the default message defaults to the Message field and the print code defined for the default message defaults to the Print field; however, the user can still override the default message text and the print code or add to the default message text. For example, if a user selects to default Happy Birthday, the user may wish to modify the message line to read .
Default message examples: An example of the type of messages you may wish to default are listed below.
- Happy Birthday
- Happy Anniversary
- Congratulations
- Merry Christmas
- Happy Holidays
- Season’s Greetings
- Best Wishes
- Thinking of You,
- With Deepest Sympathy,
- Use discount code PR5 to receive 5% off your next order.
Selecting Default Messages in Contact Center
The Print Code setting for default messages controls whether they are available for selection in Contact Center:
- Order Messages: Default order messages are available for selection in Contact Center based on the Print Code setting:
- Nowhere: Can apply to an order message in Contact Center. Only these default messages are available for selection as message templates in Contact Center order entry.
- Picks: Can apply to a pick message (under Customer Messages) in Contact Center, including Contact Center order entry.
- Gift: Can apply to a gift message (under Customer Messages) in Contact Center, including Contact Center order entry.
- Quote: Can apply to a quote message (under Customer Messages) in Contact Center.
- Ref Chk Cust: Can apply to a refund check message (under Customer Messages) in Contact Center.
- Order Line Messages: Default order line messages are available for selection in Contact Center, including Contact Center order entry, regardless of the Print Code setting.
Order and order line default messages with any other print code settings are not available in Contact Center.
In this topic:
- Work with Default Messages Screen
- Create Default Message Screen
- Change Default Message Screen
- Select Default Message Screen
For more information:
- Adding Order Messages
- Work with Order Line Messages Screen (in Order Entry/Maintenance)
- Item Availability Screen (in Order Inquiry)
Work with Default Messages Screen
Use the Work with Default Messages screen to review default messages. From this screen, you can also create, change, or delete a default message.
Default messages display on this screen in message type, message code sequence.
How to display this screen: Enter WMSG in the Fast path field at the top of a menu or select Work with Default Messages from a menu.
Column sort: You can sort on any column on this screen by clicking on the column name. An arrow pointing up displays next to the field to indicate the values for the field display in ascending sequence; an arrow pointing down displays next to the field to indicate the values for the field display in descending sequence.
Default messages initially display on this screen alphanumerically by message type, message code sequence.
Field | Description |
---|---|
Message Type |
A code that indicates whether the default message text is used for order level messages or order line level messages. Valid values:
Search: Select a message type to display default messages that match your entry. Alphanumeric; Optional. |
Message Code |
A unique code used to identify the default message. Note: The message code must be unique within the message type; however, you can use the same message code for an Order Message and an Order Line Message message type. For example, you may wish to define a default message of Happy Birthday at the order message level and at the order line message level.Search: Select a Message Type and enter a full or partial message code to display default messages in alphanumeric sequence within message type, starting with your entry. Alphanumeric, 2 positions; Optional. |
Default Message |
The text you wish to automatically default to the message line when a user selects this default message. The system defaults the message text to the message line; however, the user can override the default message text or add to the default message text. For example, if a user selects to default Happy Birthday, the user may wish to modify the message line to read Happy Birthday, Mom! Search: Enter text in this field to display default messages that contain the text you entered. Alphanumeric, 60 positions; Optional. |
Print Code |
A code that indicates where, if at all, the message displays. The print code you define defaults to the Print field on the Work with Order Messages Screen or Work with Order Line Messages Screen. Valid values for Order Message:
Valid values for Order Line Message:
Search: Select a Message Type and enter a valid print code to display default messages that match your entry. Contact Center: See Selecting Default Messages in Contact Center for information on default messages available for selection in Contact Center, based on Print Code setting. Alphanumeric; Optional. |
Screen Option | Procedure |
---|---|
Create a default message. |
Select Create to advance to the Create Default Message Screen. |
Change a default message. |
In the Action field, select Change for a default message to advance to the Change Default Message Screen. |
Delete a default message. |
In the Action field, select Delete for a default message to advance to the Confirm Delete window. Select Yes to confirm the delete or select No to cancel the delete. |
Create Default Message Screen
Purpose: Use this screen to create a new default message record.
How to display this screen: Select Create at the Work with Default Messages Screen.
Field | Description |
---|---|
Message Type |
A code that indicates whether the default message text is used for order level messages or order line level messages. Valid values:
Alphanumeric; Required. |
Message Code |
A unique code used to identify the default message. Note: The message code must be unique within the message type; however, you can use the same message code for an Order Message and an Order Line Message message type. For example, you may wish to define a default message of Happy Birthday at the order message level and at the order line message level.Alphanumeric, 2 positions; Required. |
Default Message |
The text you wish to automatically default to the message line when a user selects this default message. The system defaults the message text to the message line; however, the user can override the default message text or add to the default message text. For example, if a user selects to default Happy Birthday, the user may wish to modify the message line to read Happy Birthday, Mom! Alphanumeric, 60 positions; Required. |
Print Code |
A code that indicates where, if at all, the message displays. The print code you define defaults to the Print field on the Work with Order Messages Screen or Work with Order Line Messages Screen. Valid values for Order Message:
Valid values for Order Line Message:
Contact Center: See Selecting Default Messages in Contact Center for information on default messages available for selection in Contact Center, based on Print Code setting. Alphanumeric; Required. |
Change Default Message Screen
Purpose: Use this screen to change a default message record.
How to display this screen: Select Change for a default message at the Work with Default Messages Screen.
Field | Description |
---|---|
Message Type |
A code that indicates whether the default message text is used for order level messages or order line level messages. Alphanumeric; Display-only. |
Message Code |
A unique code used to identify the default message. Alphanumeric, 2 positions; Display-only. |
Default Message |
The text you wish to automatically default to the message line when a user selects this default message. The system defaults the message text to the message line; however, the user can override the default message text or add to the default message text. For example, if a user selects to default Happy Birthday, the user may wish to modify the message line to read Happy Birthday, Mom! Alphanumeric, 60 positions; Required. |
Print Code |
A code that indicates where, if at all, the message displays. Valid values for Order Message:
Valid values for Order Line Message:
Contact Center: See Selecting Default Messages in Contact Center for information on default messages available for selection in Contact Center, based on Print Code setting. Alphanumeric, Required. |
Select Default Message Screen
Purpose: Use this screen to review and select a standard message that you wish to default to an order. When you select a default message to add to an order, the message text defined for the default message defaults to the Message field and the print code defined for the default message defaults to the Print field; however, you can still override the default message text and the print code or add to the default message text. For example, if a user selects to default Happy Birthday, the user may wish to modify the message line to read Happy Birthday, Mom! Love, Alex and Beth.
How to display this screen: Select the prompt arrow for the Messages field on one of the following screens:
- Item Availability Screen (Order Inquiry) Note: Only default messages identified as Message type Order Line Message display on this screen.
- Work with Order Line Messages Screen (Order Entry/Maintenance) Note: Only default messages identified as Message type Order Line Message display on this screen.
- Work with Order Messages Screen Note: Only default messages identified as Message type Order Message display on this screen.
Contact Center: Default messages are also available for selection in Contact Center, depending on the Print Code setting. See Print Code, above, for background.
Field | Description |
---|---|
Code (Message code) |
A code used to identify a default message. Default message codes are defined in and validated against the Default Message table. Enter a full or partial message code to display default messages in alphanumeric sequence, starting with your entry. Alphanumeric, 2 positions; optional. |
Message (Default text) |
The message text to default to the Message field on one of the following screens:
Once you default the message text, you can still modify the message line. Enter text in this field to display default messages in alphanumeric sequence that contain your entry. Alphanumeric, 60 positions; optional. |
Print Code |
The code that indicates where, if at all, the message displays. Valid values for Order Message:
Valid values for Order Line Message:
Contact Center: See Selecting Default Messages in Contact Center for information on default messages available for selection in Contact Center, based on Print Code setting. Alphanumeric; display-only. |
Screen Option | Procedure |
---|---|
Select a default message |
Select the Code (Message code) field to default the associated Message (Default text) and Print Code to the Messages and Print field on the following screens:
|
Working with Order Line Activity Codes (WOLA)
Order line activity codes define the type of activity, such as a shipment or return, performed against an item on an order line. You can review the activity performed against an item on an order line on the Display Order Line History Screen. You can use the Work with Order Line Activity Codes (WOLA) menu option to review system-delivered order line activity codes and to also create user-defined order line activity codes.
In this topic:
- System Delivered Order Line Activity Codes
- Work with Order Line Activity Codes Screen
- Create Order Line Activity Code Screen
System Delivered Order Line Activity Codes
The system automatically creates the system delivered order line activity codes in the Order Line Activity table and displays them on the Work with Order Line Activity Codes Screen.
Activity Code | Description |
---|---|
A |
Add; the order line is added to the order during order maintenance or exchange, or through a system process, such as Process Item Substitutions (PSUB). |
B |
Express Bill; the order line is express billed. |
C |
Cancel; a quantity of the item on the order line is cancelled during order maintenance or through a system process, such as Process Item Substitutions (PSUB). This includes canceling or reducing quantity using a cancel reason code flagged not to reduce demand. |
D |
Discount; a discount is applied to the order line after shipment. |
E |
Exchange; the order line is added to the order as an exchange item during return processing. |
G |
Change; the order line is changed during order maintenance. This includes changes that don’t affect quantity, in addition to canceling or reducing quantity using a cancel reason code flagged to reduce demand. |
J |
Item Hold; the order line was put on hold. |
O |
Sold Out; a quantity of the item on the order line has been sold out.
|
P |
Item Partially Shipped; a partial quantity of the item was shipped. |
R |
Return; a quantity of the item on the order line has been returned. |
S |
Shipment; a quantity of the order line has been shipped. |
X |
This code is not currently implemented. |
8 |
Order Line Message Added; an order line message was added. |
9 |
Item Unreserved: the item was unreserved through Work with Void/Reprint Picks, Interactive Reservation, or the Picking message. This record is not created through the Void Pick Batch option. |
# |
Item Partially Cancelled; a partial quantity of the order line was canceled through the Cancel option. |
+ |
Item Released from Hold; the line was released from held status. |
Work with Order Line Activity Codes Screen
Use this screen to work with system delivered and user defined order line activity codes.
When you first advance to this screen, order line activity codes display on the screen in activity code sequence.
How to display this screen: Enter WOLA in the Fast path field at the top of any menu or select Work with Order Line Activity Codes from a menu.
Field | Description |
---|---|
Activity Order line activity code |
A code for the type of update against the item on an order line. See System Delivered Order Line Activity Codes to review a list of the system delivered order line activity codes and a description of each. Search: Enter an activity code to display the order line activity code that matches your entry. Column sort: Click the column name. An arrow pointing up displays next to the field when the values for the field display in ascending sequence; an arrow pointing down displays next to the field when the values for the field display in descending sequence. Alphanumeric, 1 position; optional. |
System Option |
Defines whether the order line activity code is a system delivered code or a user defined code. Valid values:
Search: Enter a valid system option to display order line activity codes whose System Option setting matches your entry. Alphanumeric, 1 position; optional. |
Description |
A description of the order line activity. Search: Enter a full or partial description to display order line activity codes whose description contains your entry. Alphanumeric, 25 positions; optional. |
Screen Option | Procedure |
---|---|
Create a user defined order line activity code |
Select Create to advance to the Create Order Line Activity Code Screen. |
Delete a user defined order line activity code |
In the Action column, select Delete for an order line activity code to advance to the Confirm Delete window. Select Yes to confirm the delete; otherwise, select No to cancel the delete. Note: You cannot delete a system delivered order line activity code (the System Option field for the order line activity code is Y). |
Create Order Line Activity Code Screen
Purpose: Use this screen to create a user defined order line activity code.
How to display this screen: Select Create at the Work with Order Line Activity Codes Screen.
Field | Description |
---|---|
Activity Order line activity code |
A code for the type of update against the item on an order line. See System Delivered Order Line Activity Codes to review a list of the system delivered order line activity codes and a description of each. Alphanumeric, 1 position; required. |
Description |
A description of the order line activity. Alphanumeric, 25 positions; required. |
System Option |
N defaults, indicating the order line activity code is a user defined code. Alphanumeric, 1 position; display-only. |
Setting Up Customer Support Tables
The following topics describe how to create and maintain tables that support Order Entry and Customer Service activities:
-
Setting Up the Country Table (WCTY) describes the screens you use to create, change, delete, and display country codes.
-
Setting Up the Zip/City/State (Postal Code) Table (WZIP) describes the screens you work with to create tables that support address and tax information associated with postal and zip codes.
-
Setting Up Customer Profiles (WPFL) describes the screens you use to define demographics categories and their data options for profiling your customer base.
-
Setting Up the Customer Class Table (WCCL) describes the Work with Customer Class screens you use to establish codes to group customers for reporting and other purposes.
-
Setting Up Match Codes (MMCH) describes how to view or change the match code structure.
-
Setting Up User-Defined Fields (WUDF) describes how you can “design” a screen with user-defined numeric, text or date fields, which you can link to another table (such as the Customer table).
-
Working with Postal Code Formats (WPCF) describes how to define the formats of zip and postal codes, so that they will print correctly on pick slips and gift acknowledgments.
-
Working with Mail/Call Codes (WMCC) describes how to create codes that define when and under what circumstances you call or send mail to your customers.
-
Working with Customer Action Reason Codes (WCAR) describes how to create codes that allow you to define and track the types of issues your customers raise.
-
Working with Customer Note Types (WNTY) describes how to create codes that allow you to flag certain types of customer notes to appear automatically in order entry, or define text to default into the note field.
-
Working with Language Codes (WLAN) describes the screens you use to create, change and delete language codes.
Setting Up the Country Table (WCTY)
Purpose: Setting up the country table consists of creating identifying codes for each country where your customers or vendors reside. You can also create information related to a country, such as:
- any duty rates that apply to shipments to the country
- the telephone number formats for each country
- valid states for each country, and whether they are subject to VAT
- whether a state or a postal code is required for a customer address
- whether a valid SCF/ship via is required for the ship via and shipping address on an order
- a default VAT or tax rate for the country
Default country: Use the Default Country for Customer Address (B17) system control value to specify this default.
In this topic:
- Work with Countries Screen
- Work with Duty Rates Screen
- Work with Telephone Number Format Screen
- Work with States Screen
Work with Countries Screen
How to display this screen: Enter WCTY in the Fast path field at the top of any menu or select Work with Countries from a menu.
Field | Description |
---|---|
Country |
A code representing a country. Alphanumeric, 3 positions; optional. |
Description |
The name of the country. Alphanumeric, 30 positions; optional. |
Require state |
Controls whether a state is required in Order Entry, Customer Maintenance, and when setting up item restrictions by country/state. See Entering Additional Item Information, for more information on item country/state restrictions. Valid values are:
Optional. |
Country prefix |
The country's international telephone prefix. Numeric, 3 positions; optional. |
ISO code |
A code representing the international standard code used to identify a country. If you use the Experian Data Quality (EDQ) Address Validate API, the system sends the ISO country code instead of the country code as part of the address sent to EDQ for standardization. See Country ISO Codes for a list of country ISO codes supplied by EDQ. If you are using the ChannelAdvisor integration, you need to specify a 2-position ISO code for each country where you ship orders. See ChannelAdvisor Integration Overview and ChannelAdvisor Setup for more information. Alphanumeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Create a country code |
Select Create to display the Create Country Screen. |
Change a country code |
Select Change for a country code to display the Change Country screen. See Create Country Screen for field descriptions. You can change any information except the country code. |
Delete a country code |
Select Delete for a country. |
Display a country code |
Select Display for a country code to advance to Display Country screen. You cannot change any information on this screen. See Create Country Screen for field descriptions. |
Work with duty rates for a country |
Select Duty Rates for a country code to display the Work with Duty Rates Screen. |
Work with telephone number formats for a country |
Select Phone Format for a country code to display the Work with Telephone Number Format Screen. |
Work with state codes for a country |
Select States for a country code to display the Work with States Screen. |
Work with user defined fields |
Select User Options for a country code to advance to the Work with User Fields Screen. |
Create Country Screen
Purpose: Use this screen to create a country code.
How to display this screen: Select Create at the Work with Countries Screen.
Field | Description |
---|---|
Country |
A code to identify a country. Invoice currency: If you want the system to record the currency rate in effect for orders at the time they are billed in the Invoice Currency table, the country code must match a code from the Currency table. You must also have the Track Invoice Currency (D68) system control value selected. Note: This is a separate type of tracking than that related to multi-currency by offer. See Setting Up Order Entry Values for more information on defining Order Entry values.Alphanumeric, 3 position. Create screen: required. Change screen: display-only. |
Description |
A description of the country. This is the description that prints on pick slips, for example. Alphanumeric, 30 positions; required. |
Require state? |
This flag controls whether a state code is required for customer addresses, or for item country/state restrictions that you set up through the Work with Items menu option. Valid values are:
You can define state codes for a country by selecting States for a country at the Work with Countries Screen. Item restrictions: If a country does not require state codes, you can set up item country/state restrictions for the entire country. Item country restrictions prevent you from entering an order for items which cannot be shipped to this country. See Entering Additional Item Information. |
Require postal code? |
Indicates whether a postal code is required for customer addresses for the country. Valid values are:
Brokered backorders: When the system submits a brokered backorder for fulfillment, the Order Broker rejects it if the shipping address does not include a postal code. In this situation, the backorder returns to standard backorder processing in the warehouse. See Brokered Backorders for more information on brokered backorders. |
Perform ship via edit? |
Indicates whether to validate the SCF and ship via on an order or order line against the SCF Ship Via table. Valid values are:
Note: If the Require postal code? flag is unselected for a country, no ship via edit takes place in order entry regardless of the setting of the Perform ship via edit? flag.Use Working with SCF Codes (WSCF) to create the SCF record of # for the country, and then use Working with SCF/Ship Via Values (WSHV) to create the SCF/ship via record for each valid ship via for the country. |
Phone country code |
A valid international telephone prefix for the country. You can define a telephone number format for a country by selecting Phone Format for next to a country at the Work with Countries Screen. See Telephone Number Layout Screen (Create Mode). Numeric, 3 positions; optional. |
VAT percent (Value added tax percentage) |
The default VAT or tax percentage for the country. The system uses this value in two different ways, depending on how the Tax Included in Price (E70) system control value is set: If this system control value is selected this means that you charge the tax-inclusive price for items you ship to certain states or provinces; instead of including an amount in the Tax bucket on the order, the tax is “hidden” in the item price. To determine the hidden tax amount, the system first checks the SKU record to determine if there is a unique hidden tax amount or percentage defined for the item; if there is no hidden tax information for the item, the system uses the VAT percentage defined for the country where you are shipping the order. If there is no VAT percentage for the customer's country, and if there is no hidden tax information for the SKU, no hidden tax will be charged. Only shipments to states flagged as subject to VAT (the VAT exempt flag is unselected) use tax-inclusive pricing and hidden tax. See Work with States Screen. The system never checks the VAT percentage for orders subject to regular taxing rather than VAT; instead, the system first checks the customer's postal code record, then the customer's SCF, for the tax rate on the order. |
If this system control value is unselected, this means that any tax on the order is included in the Tax bucket and you never charge a tax-inclusive price or hidden tax. If an item on an order is subject to tax, the system multiplies the item price by the VAT percentage for the customer's country and adds this amount to the Tax bucket on the order. If there is no VAT percentage defined for the customer's country, the system next checks the customer's postal code, then the customer's SCF, to find an applicable tax percentage. See How Hidden Tax is Calculated by Percentage for more information. Numeric, 6 positions; optional. |
|
ISO code |
A code representing the international standard code used to identify a country. If you use the Experian Data Quality (EDQ) Address Validate API, the system sends the ISO country code instead of the country code as part of the address sent to EDQ for standardization. See Country ISO Codes for a list of country ISO codes supplied by EDQ. Alphanumeric, 3 positions; optional. |
Work with Duty Rates Screen
Purpose: Use this screen to create, change, delete or display duty rates for international orders. The system consults these rates to determine whether to add duty to orders you are shipping to this country.
Overview: Duty is a tax you can add to orders you are shipping to customers in certain countries. The system performs the following checks to determine whether to charge duty for an item in Order Entry:
- Is the shipper exempt from duty? If the field for the shipper on the order header is selected, the system will not add any duty to the order. This flag must be unselected for the system to evaluate the order for duty charges.
- Does the item's harmonize code match a duty rate defined for the country? The system compares the harmonize code defined for the item or SKU with the harmonize codes associated with the duty rates. If it finds a match in harmonize code, the system computes duty for the item and adds this charge to the order. Two blank records are a match; that is, if both the item's and the duty rate's harmonize codes are blank, the system will add the duty to the order. You can define harmonize codes for items through Performing Initial Item Entry (MITM) or Updating Harmonize Codes (UPHC).
If you use an external tax system and want to pass the duty information, you must create a product table record for duty.
Reviewing duty charges: Duty appears on the order totals in the Handling bucket, but appears separately on the Display Order Detail Screen (Reviewing Order Line Detail) in standard Order Inquiry and the Work with Order Line Screen (Changing/Adding an Item) in Order Entry and Order Maintenance. The system writes an order line message when an item has a duty charge. You can also review duty charges on an invoice at the Invoice Detail Charges screen, available by selecting Invoices in standard Order Inquiry and advancing to the invoice detail level.
Note:
Duty does not appear on your pick slip without customization. Contact your Order Management System representative for more information.How to display this screen: Select Duty Rates for a country at the Work with Countries Screen.
Field | Description |
---|---|
Country |
The code representing the country where the duty rates apply. Alphanumeric, 3 positions; display-only. |
Description |
The description associated with the country code. Alphanumeric, 25 positions; display-only. |
Harmonize code |
The code that associates an item with a duty rate. The system applies duty to an order if the ship-to address is in this country, and if the harmonize code defined for the item or SKU matches a harmonize code defined for a duty rate. If both the item's and the duty rate's harmonize codes are blank, the system considers this a match, and applies the duty rate. You can define harmonize codes for items through Performing Initial Item Entry (MITM) or Updating Harmonize Codes (UPHC). Alphanumeric, 16 positions; optional. |
Duty amount |
The amount of duty to add to the order for the item. The system multiplies this amount by the unit quantity. You can define either a duty amount or a percentage. Numeric, 13 positions with a 2-place decimal; display-only. |
Duty percent |
The percentage of duty to add to the order for the item. The system adds the percentage of the extended price for the item line. Numeric, 5 positions with a 2-place decimal; display-only. |
Screen Option | Procedure |
---|---|
Change a duty rate |
Select Change for a duty rate to advance to the Change Duty Rates screen. You can change only the Duty percent or Duty amount fields on this screen. See Create Duty Rates Screen for field descriptions. |
Delete a duty rate |
Select Delete for a duty rate. |
Display a duty rate |
Select Display for a duty rate to advance to the Display Duty Rates screen. You cannot change any information on this screen. See Create Duty Rates Screen for field descriptions. |
Create a duty rate |
Select Create to create a new duty rate. See Create Duty Rates Screen. |
Create Duty Rates Screen
Purpose: Use this screen to create a duty rate.
How to display this screen: Select Create at the Work with Duty Rates Screen.
Field | Description |
---|---|
Country |
The code representing the country where the duty rates apply. Alphanumeric, 3 positions; display-only. |
Harmonize code |
The code that associates an item with a duty rate. The system applies duty to an order if the ship-to address is in this country, and if the harmonize code defined for the item or SKU matches a harmonize code defined for a duty rate. If both the item's and the duty rate's harmonize codes are blank, the system considers this a match, and applies the duty rate; for this reason, a blank harmonize code is a valid value. You can define harmonize codes for items through Performing Initial Item Entry (MITM) or Updating Harmonize Codes (UPHC). Alphanumeric, 16 positions. Create screen: required. Change screen: display-only. |
Duty percentage |
The percentage of duty to add to the order for the item. The system adds the percentage of the extended price for the item line. You can define either a duty amount or a percentage. Numeric, 5 positions with a 2-place decimal; required if no duty amount is defined. |
Duty amount |
The amount of duty to add to the order for the item. The system multiplies this amount by the unit quantity. You can define either a duty amount or a percentage. Numeric, 13 positions with a 2-place decimal; required if no duty percentage is defined. |
Work with Telephone Number Format Screen
Purpose: Use this screen to define the format for phone numbers. Telephone number formats are defined by country, but each country can have more than one telephone number format.
When an operator enters a phone number, the system compares the number of numeric characters in the phone number with the telephone number formats you have defined. In order to match a format, the phone number must have the same number of numeric positions as a telephone number format. If the system cannot find a match, the phone number does not map to a telephone number format and displays as it was entered by the operator. For this reason, it is useful to consider the different telephone number formats your operators typically use and define a format to cover each.
Telephone Number Format Examples
Example: Telephone number format with a numeric length of 7: 1 2 3 - 4 5 6 7
-
7 position phone number: 5550100
-
5550100 formats to 555 - 0100
Example: Telephone number format with a numeric length of 10: ( 1 2 3 ) 4 5 6 - 7 8 9 10
-
10 position phone number: 5085550100
-
5085550100 formats to (508) 555 - 0100
Example: Telephone number format with a numeric length of 11: 1 ( 2 3 4 ) 5 6 7 - 11 10 9 8
-
11 position phone number: 15085550100
-
15085550100 formats to 1 (508) 555 - 0100
How to display this screen: Select Phone Format for a country.
Field | Description |
---|---|
Country |
The country code and description associated with the phone format. Country code: Alphanumeric, 3 positions; display-only. Country description: Alphanumeric, 30 positions; display-only. |
Code length |
The number of numeric characters in the phone number. Numeric, 3 positions; optional. |
Format (Telephone number format) |
The telephone number format, illustrated by arranging numbers from 1 to 14 in the same order and position as the numbers in a phone number would display. Enter special characters, such as hyphens or parenthesis, where you would like them to display. Example: The telephone number format used in the United States to represent an area code and a local phone number is: (508) 555-0100 When an operator enters a phone number containing 10 numbers (as in the example), the phone number changes to the format defined for 10 numbers, regardless of how the operator entered it into the system. Alphanumeric, fourteen 2-position fields; display-only. |
Screen Option | Description |
---|---|
Change a telephone number format |
Select Change for a telephone number format to advance to the Telephone Number Layout screen in Change mode. You can change the Formatted telephone number positions fields on this screen only. See Telephone Number Layout Screen (Create Mode) for field descriptions. |
Delete a telephone number format |
Select Delete for a telephone number format. |
Display a telephone number format |
Select Display for the telephone number format to advance to the Telephone Number Layout screen in Display mode. You cannot change any information on this screen. See Telephone Number Layout Screen (Create Mode) for field descriptions. |
Create a telephone number format |
Select Create. See Telephone Number Layout Screen (Create Mode). |
Map existing phone numbers to the telephone number formats defined. |
Select Submit Reformat. See Revising Telephone Number Formats. |
Telephone Number Layout Screen (Create Mode)
Purpose: Use this screen to create a telephone number format for a country.
How to display this screen: Select Create at the Work with Telephone Number Format Screen.
Field | Description |
---|---|
Country |
The country associated with the telephone number format you are creating. Alphanumeric, 3 positions; display-only. |
Length |
The number of numeric characters in the phone number. The maximum number is 14. Numeric, 3 positions. Create screen: required. Change screen: display-only. |
Formatted telephone number positions |
The order and positions of each of the numbers for a phone number format, including any special characters such as hyphens or parentheses. The first number of the phone number will display where you enter a 1, the second number will display where you enter a 2, etc. Example: Create a United States phone number containing an area code and local phone number as: ( 1 2 3 ) 4 5 6 - 7 8 9 10 A message similar to the following indicates if you enter a telephone number format that includes a numeric length already defined for that country: Telephone Number Format already exists. Note: If an operator enters a phone number containing a length that has not been defined in a telephone number format, the system will not format the phone number and it will display as it was entered by the operator.Alphanumeric, fourteen 2-position fields; optional. |
Instructions:
- Enter the numeric length of the telephone number format in the Length field.
- Enter the telephone number format in the Formatted telephone number positions fields, indicating where each number of the phone number should display. Include any special characters, such as hyphens or parentheses in the format. Use the Unformatted Telephone Number Positions fields as a guideline. See the field descriptions for examples.
Revising Telephone Number Formats
Submitting reformat: Select Submit Reformat at the Work with Telephone Number Format Screen to submit a batch program. This program revises existing phone numbers to the telephone number formats defined on the screen. You must confirm the submission at the Confirm Accept pop-up window.
Only phone numbers containing the same length as a telephone number format will be revises. For example, if a telephone number format with a length of 10 is defined as: ( 1 2 3 ) 4 5 6 - 7 8 9 10, any telephone number with a length of 10 will be revised so that the first 3 positions are in parentheses and a hyphen is between the sixth and seventh numbers.
Work with States Screen
Purpose: Use this screen to define the state codes for a country. The system prevents you from entering a customer address if the state and country do not match, based on your entries here.
How to display this screen: Select States for a country at the Work with Countries Screen.
Field | Description |
---|---|
Country |
The country code associated with the states. Alphanumeric, 3 positions; display-only. |
State |
A code that defines a state within a country. Alphanumeric, 2 positions; optional. |
Description |
The name of the state. Alphanumeric, 25 positions; display-only. |
VAT exempt flag |
This flag controls whether shipments to this state are exempt to VAT only if the Tax Included in Price (E70) system control value is selected; in this case, the system uses the tax-inclusive price for an item and adds a Hidden tax, if applicable, to the order line. If this system control value is unselected, or if the state is exempt from VAT, the system adds tax to the order in the Tax bucket, and does not check this field when determining whether to charge tax on an order. Valid values are:
This setting defaults to unselected if there is a VAT percent (Value added tax percentage) defined for the country; otherwise, it defaults to selected. Display-only. |
Screen Option | Description |
---|---|
Change the description or VAT exempt flag for a state |
Select Change for a state to display the Change State screen. You can change only the Description and VAT exempt flag fields on this screen. See Create State Screen for field descriptions. |
Delete a state |
Select Delete for a state. |
Create a state |
Select Create to display the Create State Screen. |
Create State Screen
Purpose: Use this screen to create a state code for a country.
How to display this screen: Select Create at the Work with States Screen.
Field | Description |
---|---|
Country |
The country associated with the state. Alphanumeric, 3 positions; display-only. |
State code |
A code that defines a state within the country. For countries that do not require states, you should create one state record with a state code of **. Then, when you create SCF and postal codes for the country, you assign each to this state code. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the state you are creating. Alphanumeric, 25 positions; required. |
VAT exempt flag |
Controls whether shipments to this state are exempt from VAT. The system checks this flag only if the Tax Included in Price (E70) system control value is selected; in this case, the system uses the tax-inclusive price for an item subject to VAT and adds a Hidden tax, if applicable, to the order line. If this system control value is unselected, or if the state is VAT-exempt, the system adds any applicable tax to the order in the Tax bucket, and does not check this field when determining whether to charge tax on an order. Valid values are:
This field defaults to unselected if there is a VAT percent (Value added tax percentage) defined for the country; otherwise, it defaults to selected. |
Note:
When you create a state, you must also define an SCF code and postal code for the state or Order Entry, Maintenance and Catalog Requests display an error message similar to the following:Invalid state (FL) for zip. Valid states are: (MA)
See Working with SCF Codes (WSCF) for more information on SCF's, and Setting Up the Zip/City/State (Postal Code) Table (WZIP) for more information on postal codes.
Setting Up the Zip/City/State (Postal Code) Table (WZIP)
Purpose: The Zip/City/State (postal code) table includes the city, state or province, country, tax rates, and geographic zone for postal areas. The city and state or province you enter for a customer in Order Entry or Order Maintenance are validated against this table.
Creating postal code records: You can use the Work with Postal Codes function to enter the information yourself, or purchase it from the U.S. Postal Service to build the table in your database. If you purchase the information from the U.S. Postal Service, use the Load USPS Zip Code File (LZPS) option to upload the data to the Zip/City/State table.
Note:
The Load USPS Zip Code File (LZPS) option does not create Zip/City/State Tax Rate records; it only creates Zip/City/State (postal code) records.Tax rates: You need to set up this table to set up tax rates and, for Canadian addresses, tax calculation methods, if you do not use an external tax system. Even if you use an external tax system, you might still want to establish the Zip/City/State table to help reduce other application errors or to provide an alternative means of calculating tax when there is a communication problem. See About Tax Rates.
Note:
The City name must be all upper case in order for the tax rate to apply.Geographic zones: The Zip/City/State table can be used to identify the geographic zone of a shipping address. Geographic zones are used to divide the country into shipping regions for the purpose of restricting the shipment of weather-sensitive inventory such as plant stock. See Shipping Zone Reservation Overview.
Delivery codes: Some shippers, such as UPS, charge different rates based on the type of delivery address on an order. For example, shipping to a business address is cheaper than shipping to a residential address. You can define the delivery code for a postal area to insure that the best possible rate is charged for shipping an order.
The information you enter through this menu option is not unique to a particular company; it applies to all companies on your system.
Postal code required? The Require postal code? flag in the Country table controls whether a postal code is required for customer addresses. See Setting Up the Country Table (WCTY) for background.
In this topic:
- Work with Postal Codes Screen
- Create Postal Code Screen
- About Tax Rates
- Work with Zip Tax Rates Screen
- Update Postal Codes by Range Screen
Not in this topic:
- Automatic fill-in of city and state in order entry: If you set the Use Zip/City/State Defaulting? (B13) system control value to Y, the system fills in a customer's city and state in Order Entry or Order Maintenance based on the postal code you enter.
- Tax jurisdictions: You can track tax activity for tax jurisdictions within states. You define a tax jurisdiction as a range of postal codes. See Working with Tax Jurisdiction (WTXJ).
- Postal code formats for pick slips: In order for a postal code to print on pick slips or gift acknowledgments, you must first define the postal code format. See Working with Postal Code Formats (WPCF).
Work with Postal Codes Screen
How to display this screen: Enter WZIP in the Fast path field at the top of any menu or select Work with Postal Codes from a menu.
Field | Description |
---|---|
Postal code |
The postal code or zip code representing a delivery area. Alphanumeric, 10 positions; optional. |
City |
The city where the customer receives mail or shipments. Alphanumeric, 25 positions; optional. |
State |
The state or province where the customer receives mail or shipments. States are defined in and validated against the State table, which is accessible through the Work with Country Table menu option; see Work with States Screen. Alphanumeric, 2 positions; optional. |
Description |
The description of the state, as set up through the Work with States Screen. Alphanumeric, 25 positions; display-only. |
Delivery code |
A code representing the type of delivery address for a postal code. Valid values are:
Some shippers, such as UPS, charge different rates based on the type of delivery address on an order. For example, shipping to a business address is cheaper than shipping to a residential address. You can define the delivery code for a postal area to insure that the best possible rate is charged for shipping an order. |
The system uses the following logic to default a delivery code to a customer address on an order:
Alphanumeric, 1 position; display-only. |
Screen Option | Procedure |
---|---|
Change postal code information |
Select Change for a postal code to advance to the Change Postal Codes screen. See the Create Postal Code Screen for field descriptions. |
Delete a postal code |
Select Delete for a postal code. |
Display a postal code |
Select Display for a postal code to advance to the Display Postal Code screen. You cannot change any information on this screen. See the Create Postal Code Screen for field descriptions. |
Work with tax rates |
Select Work with tax rates for a postal code to advance to the Work with Zip Tax Rates Screen. |
Create a postal code |
Select Create to advance to the Create Postal Code Screen. |
Update a postal code range |
Select Updt Pst Cd Range to advance to the Update Postal Codes by Range Screen. |
Create Postal Code Screen
Purpose: Use this screen to create a postal code.
How to display this screen: Select Create at the Work with Postal Codes Screen.
Field | Description |
---|---|
Postal code |
The postal code or zip code representing a delivery area. The first three positions of your entry must match a valid SCF for the state and country. See Working with SCF Codes (WSCF) for background. Alphanumeric, 10 positions. Create screen: required. Change screen: display-only. |
City |
The city where a customer receives mail or shipments. The City name must be all upper case in order for the tax rate from the Work with Zip Tax Rates Screen to apply. Alphanumeric, 25 positions. Create screen: required. Change screen: display-only. |
State |
The code representing the state where the customer receives mail or shipments. State codes are defined in and validated against the State table, accessible at the Work with States Screen through the Work with Countries menu option. This code is required if the Require state? flag for the country is selected. The system validates that your entry is a state assigned to the SCF derived from the first three positions of the postal code. See Working with SCF Codes (WSCF). Alphanumeric, 2 positions. Create screen: may be required. Change screen: display-only. |
Country |
A code representing a country. Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). The system defaults the Default Country for Customer Address (B17). Alphanumeric, 3 positions; required. |
Delivery code |
A code representing the type of delivery address for a postal code. Valid values are:
Some shippers, such as UPS, charge different rates based on the type of delivery address on an order. For example, shipping to a business address is cheaper than shipping to a residential address. You can define the delivery code for a postal area to insure that the best possible rate is charged for shipping an order. |
When the system defaults a delivery code to a customer address on an order, it uses: 1. The delivery code for the postal code on the address if any; otherwise, 2. The delivery code from the Customer table, if any; otherwise; 3. The Default Delivery Code for New Order Entry Customers (D13). Optional. |
|
Geographic zone |
A code representing a geographic region. Geographic zones are used to divide the country into shipping regions for the purpose of restricting the shipment of weather-sensitive inventory such as plant stock. Geographic zones are used in conjunction with zone reservation codes, assigned to items or SKUs, to control item reservation in order entry. Zone reservation coded items/SKUs are not reserved during order entry; instead they are reserved during pick generation, at an optimal time for shipping. Zone reservation logic requires:
See Shipping Zone Reservation Overview for a discussion. Alphanumeric, 3 positions; optional. |
Store tax code |
The cross-reference to the corresponding tax code in a point-of-sale system. This field is available only if you have defined a Default Location for ORCE Integration (K69). Alphanumeric, 8 positions; optional. |
About Tax Rates
Purpose: The basic steps that the system takes in calculating tax are outlined below. Also presented below are a summary of the places where you can define tax rates, methods, and exemptions.
The system follows two basic paths in evaluating each order for tax depending on whether you process orders that are subject to VAT.
VAT is a taxing method that applies in only certain states in countries. When an order is subject to VAT, the customer is charged a tax-inclusive price, and the tax amount is “hidden” on the order detail line for the item, not included in the Tax bucket for the order.
Note:
You cannot use both an external tax system and tax-inclusive pricing (VAT) in the same company.Tax-inclusive pricing? If the Tax Included in Price (E70) system control value is selected, the system follows the steps presented below in determining how to calculate tax on an order.

If the Tax Included in Price (E70) system control value is unselected, the system follows the steps presented below in determining how to calculate tax:

The system follows the steps above only if you are not using an external tax system.
Tax exemptions: Any of the following tax exemptions might prevent an order or an item from being taxed:
- customer tax exemptions or overrides (see Working with Customer Tax Status)
- the VAT exempt flag for the item/SKU (see Working with Existing Items (MITM))
- item tax exemptions and exceptions for U.S. states (see Working with Item Tax Exemptions (WITX))
- GST and PST item exemptions and exceptions for Canadian provinces (see Working with GST Tax Exemption Status (MGTX))
- the S/H exclude tax? field for a special handling format (see Establishing Additional Charge Codes (WADC))
Note:
VAT does not apply to an order unless a tax rate is specified for the SCF for the shipping address.Upper and lower case? The City name must be all upper case in order for the tax rate to apply.
Work with Zip Tax Rates Screen
Purpose: Use this screen to work with tax information for shipments to a postal code.
How to display this screen: Select Work with tax rates for a postal code at the Work with Postal Codes Screen.
Note:
- The system does not consider the settings at this screen if you use an external tax system unless the Use Standard Tax Calc if Tax Interface Communication Fails (J13) system control value is selected and the integration with the external tax system fails.
- The system automatically creates a zip tax rate record if you update postal codes by range (Updt Pst Cd Range at the Work with Postal Codes Screen). The zip tax rate’s effective date is the date when you process this update. See Update Postal Codes by Range Screen.
- Uploading postal code information through the Load USPS Zip Code File (LZPS) option does not automatically create zip tax rate records.
- The City name must be all upper case in order for the tax rate to apply.
Field | Description |
---|---|
Effect date (Effective date) |
The date when this tax information became effective for orders in this postal code. Whenever you perform pick slip preparation, bill, or maintain the order, the system calculates tax based on the tax rates in effect when the order was first entered. Numeric, 6 positions; optional. |
Tax rate |
The tax rate for the postal code. Numeric, 5 positions with a 2-place decimal; optional. |
GST rate |
The rate of Canadian Goods and Services tax for this province. If there is not a GST rate defined for the postal code, but a GST/PST tax method is defined, the system uses the default GST Rate (A90). Numeric, 5 positions with a 2-place decimal; optional. |
PST rate |
The rate of the Canadian Provincial Services tax for this province. Numeric, 5 positions with a 2-place decimal; optional. |
GST/PST method |
A code that determines the method of calculating total tax on goods shipped to Canadian provinces. This calculation method varies depending on the province where you are shipping the order. Valid codes for this field are:
Calculation (where O = the order total subject to tax): O * GST rate = GST amount GST amount + ((GST amount + O) * PST rate) = order tax Example: The order total subject to tax = $10.00 GST rate = 10% PST rate = 5% $10 * 10% = $1.00 GST amount $1 GST amount + (($1 + $10) * 5%) = $1 + ($11 * 5%) = $1.60 |
Calculation (where O = the order total): O * PST rate = PST amount PST amount + ((PST amount + O) * GST rate) = order tax Example: The order total subject to tax = $10.00 GST rate = 10% PST rate = 5% $10 * 5% = $.50 PST amount $.50 PST amount + (($.50 + $10) * 10%) = $.50 + ($10.50 * 10%) = $1.55 |
|
Calculation (where O = the order total) S = (O * GST) + (O * PST) Example: The order total subject to tax = $10.00 GST rate = 10% PST rate = 5% ($10 * 10%) + ($10 * 5%) = $1 + $.50) = $1.50 Optional. |
|
Tax freight |
Indicates whether the shipping charges on the order are taxed (Frt and Frt+ amounts). Valid values are:
Note: This flag acts as an override to the Tax on Freight (B14) system control value if the system control value is selected. If the order uses the tax rate for the postal code, but the Tax on Freight (B14) field is unselected, the system uses the value from the System Control table. If the system control value is unselected, you cannot override this value by selecting it here. |
Tax handling |
Indicates whether handling charges on the order are taxed (special handling, guaranteed service charges, and other handling charges).
This flag acts as an override to the same setting for the SCF; see Working with SCF Codes (WSCF), and the Tax on Handling (B15) system control value if the system control value is selected. If the order uses the tax rate for the postal code, but the Tax on Handling (B15) field is unselected, the system uses the value from the System Control table. If the system control value is unselected, you cannot override this value by selecting it here.
|
Screen Option | Procedure |
---|---|
Change existing tax rate information |
Type over the information you want to change, or just delete existing information. You can change any field but the Effect date (Effective date). |
Delete tax rate information |
Select Delete for a tax rate record. |
Switch to ADD Mode |
Select Add. |
Update Postal Codes by Range Screen
Purpose: Use this screen to update postal code information, such as delivery code and tax information, for a range of postal codes.
How to display this screen: Select Updt Pst Cd Range at the Work with Postal Codes Screen.
Field | Description |
---|---|
Country |
A code representing a country. Country codes are defined in and validated against the Country table. The system defaults the Default Country for Customer Address (B17). Alphanumeric, 3 positions; required. |
Postal code range |
The range of postal codes you wish to update. Enter the beginning postal code in the From range field and ending postal code in the To range field. An error message similar to the following indicates if you enter a postal code in the To field that is greater than the postal code in the From field: From zip (01601) is greater than to zip (01600). Numeric, 5 positions; required. |
The system requires entry in one of the following fields: | |
Delivery code |
A code representing the type of delivery address for the range of postal codes. Valid values are:
Some shippers, such as UPS, charge different rates based on the type of delivery address on an order. For example, shipping to a business address is cheaper than shipping to a residential address. You can define the delivery code for a postal area to insure that the best possible rate is charged for shipping an order. |
The system uses the following logic to default a delivery code to a customer address on an order:
Optional. |
|
Tax rate |
The tax rate for the postal code. Numeric, 5 positions with a 2-place decimal; optional. |
GST rate |
The rate of Canadian Goods and Services tax for this province. If there is not a GST rate defined for the postal code, but a GST/PST tax method is defined, the system uses the default GST Rate (A90). Numeric, 5 positions with a 2-place decimal; optional. |
PST rate |
The rate of the Canadian Provincial Services tax for this province. Numeric, 5 positions with a 2-place decimal; optional. |
GST/PST method |
A code that determines the method of calculating total tax on goods shipped to Canadian provinces. This calculation method varies depending on the province where you are shipping the order. Valid codes for this field are:
See GST/PST method for an example of each GST/PST method. Optional. |
Tax freight? |
Indicates whether the shipping charges on the order are taxed (Frt and Frt+ amounts). Valid values are:
Note: This flag acts as an override to the Tax on Freight (B14) system control value if the system control value is selected. If the order uses the tax rate for the postal code, but the Tax on Freight (B14) field is unselected, the system uses the value from the System Control table. If the system control value is unselected, you cannot override this value by selecting it here. |
Tax handling? |
Indicates whether special handling charges on the order are taxed (special handling, guaranteed service charges, and other handling charges).
|
Geographic zone |
A code representing a region of the country. Geographic zones are used to divide the country into shipping regions for the purpose of restricting the shipment of weather-sensitive inventory such as plant stock. Geographic zones are used in conjunction with zone reservation codes, assigned to items or SKUs, to control item reservation in order entry. Zone reservation coded items/SKUs are not reserved during order entry; instead they are reserved during pick generation, at an optimal time for shipping. |
Zone reservation logic requires:
Alphanumeric, 3 positions; optional. |
Setting Up Customer Profiles (WPFL)
Customer profiles let you define the demographics you want to capture for your customer base and define the valid responses for these categories. You can also establish default codes that represent the most common profile characteristics of your customer base. For example, assume that a profile for marital status includes married, single, divorced, etc., as valid options, and that the majority of people who place orders are single. If you set a profile default for the single option, this value appears on new customer orders. You would then need to perform data entry in the marital status field for new customers only if the customer were not single.
Mandatory categories: If there is a profile category that you want to capture for each new customer, you can define that category as mandatory. When you enter an order for a customer who has not provided you with this information, the Work with Customer Profile Screen appears automatically when you select Accept or Accept/Add Rcp to accept the order.
Note:
If the Alternate ID Required for Displaying Customer Profile (K87) system control value is selected, you automatically advance to the Work with Customer Profile screen in order entry and maintenance only if an Alternate customer number is defined for the sold to customer on the order.Sending profile data to Oracle Retail Customer Engagement:
- Customer Engagement Customer Integration: The customer’s profile data is included in the information synchronized between Order Management System and Oracle Retail Customer Engagement, provided the Send Profile Data to ORCE (L51) system control value is selected and you have completed the setup described under Order Management System Customer Profile > Customer Engagement Attribute Definition.
- Customer Engagement Batch Customer and Sales Integration. The customer’s profile data is included in the information sent to Oracle Retail Customer Engagement provided you have completed the setup described under Order Management System Customer Profile > Customer Engagement Attribute Definition. The Send Profile Data to ORCE (L51) system control value does not apply to the sales integration.
In this topic:
- Work with Profile Categories Screen
- Create Profile Screen (Creating a Category)
- Work with Profile Data Screen (Category Responses)
- Create Profile Data Screen (Category Responses)
Work with Profile Categories Screen
How to display this screen: Enter WPFL in the Fast Path field at the top of a menu, or select Work with Demographic Profiles from a menu.
Field | Description |
---|---|
Code |
A number you assign to a demographic profile category. Numeric, 3 positions; optional. |
Description |
The description of the demographic profile category. Alphanumeric, 20 positions; optional. |
Mandatory |
This flag indicates whether to prompt the operator to complete this field in Order Entry if the customer has not yet provided you with this information. Valid values are:
The system also prompts you in Order Maintenance if the Prompt for Mandatory Demographics in Order Maintenance (E60) system control value is selected. Optional. |
Screen Option | Procedure |
---|---|
Create a profile category |
Select Create to advance to the Create Profile Screen (Creating a Category). |
Change a profile category |
Select Change for a profile category to advance to the Change Profile screen. You can change only the description and the mandatory flag. See Create Profile Screen (Creating a Category) for field descriptions. |
Delete a profile category |
Select Delete for a profile category. |
Work with valid profile responses |
Select Profile Options for a profile category to advance to the Work with Profile Data Screen (Category Responses). |
Create Profile Screen (Creating a Category)
How to display this screen: At the Work with Profile Categories Screen, Select Create.
Field | Description |
---|---|
Profile code |
A number that represents a demographic profile category. Numeric, 3 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the demographic profile category. The system does not prevent you from creating more than one profile code with the same description. Alphanumeric, 20 positions; required. |
Mandatory |
This flag indicates whether to prompt Order Entry operators to collect this information if the customer has not already provided it. Valid values are:
The system will also advance to the Work with Customer Profile Screen automatically in Order Maintenance if the Prompt for Mandatory Demographics in Order Maintenance (E60) system control value is selected. Note: The system does not prompt you for a mandatory profile category if you define a default response for the category; instead, the system will update the customer record with the default value automatically, behind the scenes. |
Work with Profile Data Screen (Category Responses)
Purpose: Use this screen to create, change, or delete valid responses for a profile category.
How to display this screen: Select Profile Options for a profile category at the Work with Profile Categories Screen.
Field | Description |
---|---|
Code |
A number from 1 through 9 that you assign to a profile response. Alphanumeric, 1 position; optional. |
Description |
The description of the profile response. Alphanumeric, 20 positions; optional. |
Default? |
A flag that determines whether the system defaults this response automatically when you create or change demographic information for a customer. You can override this default value.
|
Screen Option | Procedure |
---|---|
Create a response code |
Select Create to advance to the Create Profile Data Screen (Category Responses). |
Delete a response code |
Select Delete for a code. |
Change a response code |
Select Change for a code to advance to the Change Data Option screen. You can change the description or the default flag for a profile data option. See Create Profile Data Screen (Category Responses) for field descriptions. |
Create Profile Data Screen (Category Responses)
Purpose: Select Create at the Work with Profile Categories Screen.
Field | Description |
---|---|
Profile code |
A number that represents a demographic profile category for which you are creating a valid response code. Numeric, 3 positions; display-only. |
Profile data code |
A user-defined code that represents a valid response for the profile category. For example, if the profile code were income, the profile data code might be 1, representing income less than $20,000. Alphanumeric, 1 position. Create screen: required. Change screen: display-only. |
Description |
Text that describes the profile data response. Example: For the profile category of Income level, you might create profile data codes such as the following: 1 = less than $30,000 2 = $20,000-$69,000 3 = $30,000-$89,000 4 = $40,000-$109,000 5 = more than $149,000 Alphanumeric, 30 positions; required. |
Default? |
This flag identifies whether to default this code for the profile category. When you establish a default code by selecting this setting, the default code appears when you advance to the Work with Customer Profile Screen in Order Entry, Order Maintenance, and Customer Maintenance. You can designate only one default response code for each profile category. If you designate a default response for a mandatory category, the system will default this value for customers automatically behind the scenes in Order Entry if the customers have not already supplied you with the correct information; the Work with Customer Profile screen will not display (unless there is an additional mandatory category without a default value designated). The same condition is true for Order Maintenance if the Prompt for Mandatory Demographics in Order Maintenance (E60) field in the System Control file is selected.
|
Setting Up the Customer Class Table (WCCL)
Purpose: Use customer classes to create high level groupings of customers. You can use customer class codes to:
- direct offerings to a limited customer group
- restrict item sales to a group of customers (for example, restricting the sale of guns to minors)
- exclude a group of customers from a particular pay type
- set a default for bypassing item reservation for a group of customers
- generate a list of customers for reporting purposes, or segment reports by class code
- trigger a prompt in order entry to complete a user-defined field for customers based on their class
Related system control values: You can define a Default Customer Class in Order Entry (D63) in the System Control table for the system to assign automatically to all new customers created through Order Entry. Also, you can use the Require Customer Class in OE, WCAT, and WCST (H85) system control value to require the customer class in order entry, order maintenance, catalog requests, and customer maintenance.
Secured feature: The Maintenance of Customer Class Field (B07) controls the authority to enter or change the customer class in order entry, order maintenance, catalog requests, and order maintenance.
Important:
If you set the Require Customer Class in OE, WCAT, and WCST (H85) system control value to Y, a user who does not have authority to the customer class field will not be able to enter or maintain an order or a catalog request, or perform customer maintenance for any customer that does not already have a customer class assigned.In this topic:
- Work with Customer Classes Screen
- Create Customer Class Screen
- Exclude Pay Types by Customer Class Screen
- Create Pay Type Exclusions/Customer Class Screen
For more information:
- Change Cust Sold to Name & Address Screen
- Work with Order Screen
- Expand Name/Address Screen
- catalog requests: Create Catalog Request Screen
- customer maintenance:
Work with Customer Classes Screen
How to display this screen: Enter WCCL in the Fast path field at the top of any menu, or select Work with Customer Classes from a menu.
Field | Description |
---|---|
Class |
A code you can use to group customers. Alphanumeric, 2 positions; optional. |
Description |
The description of the code. Alphanumeric, 30 positions; optional. |
Bypass reservation |
This code indicates whether customers in this class are restricted to interactive reservation. Valid values are:
Note: Use this flag only if the Use OROB for Fulfillment Assignment (M31) system control value is unselected. This system control value uses the Bypass reservation flag to send orders to Order Broker for fulfillment assignment.Optional. |
Screen Option | Procedure |
---|---|
Create a customer class |
Select Create to advance to the Create Customer Class Screen. |
Change customer class information |
Select Change for a class to advance to the Change Customer Class screen. At this screen you can change the description or the bypass reservation code. See Create Customer Class Screen for field descriptions. |
Delete a customer class |
Select Delete for a class. |
Establish a pay type exclusion |
Select Pay Type Exclusions for a class to advance to the Exclude Pay Types by Customer Class Screen. |
Create Customer Class Screen
To create: Select Create at the Work with Customer Classes Screen.
Field | Description |
---|---|
Class |
The code you use to categorize customers at a high level for reporting purposes. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the class. Alphanumeric, 30 positions; required. |
Bypass reservation |
This flag indicates whether customers in the class are restricted to interactive reservation, in which you manually assign inventory to orders. Valid values are:
Note: Use this flag only if the Use OROB for Fulfillment Assignment (M31) system control value is unselected. This system control value uses the Bypass reservation flag to send orders to Order Broker for fulfillment assignment. |
Exclude from Rewards |
Not implemented. |
Exclude Pay Types by Customer Class Screen
Purpose: Use this screen to work with any pay type(s) the customer class is prohibited from using. If you attempt to enter an excluded pay type on an order for a customer in this class, the system displays a message such as the following:
Customer class (99) has been excluded from using pay type (4).
How to display this screen: Select Pay Type Exclusions for a class at the Work with Customer Classes Screen.
Field | Description |
---|---|
Pay Type |
Represents the method of payment on an order. See Working with Pay Types (WPAY). Numeric, 2 positions; optional. |
Screen Option | Procedure |
---|---|
Create a new pay type exclusion for this customer class |
Select Create to advance to the Create Pay Type Exclusions/Customer Class Screen. |
Delete a pay type exclusion for a customer class |
Select Delete for a pay type exclusion. |
Create Pay Type Exclusions/Customer Class Screen
To create: Use this screen to create a new pay type exclusion for a customer class.
How to display this screen: Select Create at the Exclude Pay Types by Customer Class Screen.
To complete this screen: Enter the code representing the pay type from which the class should be excluded. See Working with Pay Types (WPAY).
Setting Up Match Codes (MMCH)
Match codes are unique customer identification codes that consist of selected portions of a customer name, company name, and address information. The system generates a match code for each customer based on positional field contents you include in a match code schematic or algorithm. You can create up to four match codes per customer, including a standard match code and three fraud identification match codes.
The standard match code identifies duplicate customers any time you create a customer through Order Entry, Customer Maintenance, Order Maintenance, or the Catalog Request table. The three fraud match codes identify customers you have included in Working with Customer Fraud Tables (WCFD).
Note:
To avoid duplicate addresses in the system, you must define the standard match code. To identify a customer as a fraud customer, define the three fraud match codes; the system checks for matches in the Fraud table based on three different algorithms.The system includes an industry standard match code schematic. You can rearrange the fields and modify the field portions that the match code logic draws from to generate a match code. You can also limit the length of the resulting match code display by leaving match code positions blank. However, you cannot exceed the length of the match code algorithm itself, which is 15 positions.
In this topic:
- Change Match Codes Screen (Maintaining Match Codes)
- Display Match Code Summary Screen
- Change Match Code Screens
- Test Match Code Screen
Change Match Codes Screen (Maintaining Match Codes)
How to display this screen: Enter MMCH in the Fast Path field at the top of a menu or select Change Customer Match Codes from a menu.
Field | Description |
---|---|
Match code |
An algorithm that generates a unique customer identifier comprised of selected portions of the customer name, company name, and address. You can generate up to four match code types:
Required. |
Screen Option | Procedure |
---|---|
Select a match code for review |
Select a code in the Match code field. You advance to the Display Match Code Summary Screen. If no match code has been defined, this screen displays only the title and field headings. |
Display Match Code Summary Screen
Purpose: Use this screen to review the pattern and structure of a match code. This screen presents the current algorithm, including the field names and field positions that comprise the match code.
How to display this screen: Select a match code value at the Change Match Codes Screen (Maintaining Match Codes).
Field | Description |
---|---|
Match code position |
Identifies the position in the match code that each field element occupies. Example: In the sample screen above, match code positions 1-3 consist of elements from the customer's first name. Positions 4-6 in the match code consist of elements from the customer's last name. Positions 7-9 in the match code consist of elements from the street address. Positions 10-14 consists of elements from the postal code. Position 15 consists of an element from the customer' s prefix. |
Name/address |
The name of the field from which the system extracts the match code element. See Change Match Code Screens for complete field descriptions, including attributes. You can use:
The second line is available for entering an extended address, for use when street address alone is insufficient. |
Note: This format differs from the zip code format you use in other situations. In most other tables, you include the hyphen when entering an extended zip code (format = xxxxx-xxxx). However, when creating a match code, you disregard the hyphen (format = xxxxxxxx).
|
|
Field position used |
This graphic illustrates the field length and identifies which field positions the match code includes. The ruler at the top of the screen lets you identify the length of any field and the positional values from that field that the match code includes. The words “Position not used” indicate that you did not define positional values for the related match code positions. |
Example:
Using this algorithm, the system assembles the match code shown below for a customer named John Brown whose street address is 10 Sample Street, and whose zip or postal code is 01609 JOHBRO10S01609M See Change Match Code Screens for complete field descriptions, including atttributes. |
Screen Option | Procedure |
---|---|
Change the match code contents |
Select Change to change the match code. You advance to the first of the Change Match Code Screens. |
Test the match code |
Select Test to advance to the Test Match Code Screen. |
Change Match Code Screens
Purpose: You use four Change Match Code screens to define or modify a match code.
Important:
Changing a Match Code algorithm results in a complete regeneration of every Sold-to, Ship-to, and Bill-to customer's match code in the Customer Maintenance Table. This process is extremely time consuming and prevents your access to tables until it is complete.How to display this screen: Select Change at the Display Match Code Summary Screen.
How to interpret this screen: There are 4 screens that display the fields you can select when changing a match code. The subsequent screens are identical to the first, except that the field names and positions change from screen to screen.
One screen provides two rows per field to accommodate the maximum number of field positions available in any given field. However, you identify the positions available within the field by the number of spaces shown.
Field | Description |
---|---|
Match code |
The type of match code you are defining. You can define the standard match code, or one of three fraud match codes. Alphanumeric, 30 positions; display-only. |
Prefix |
A title (such as "Ms." or "Dr.") that belongs before the customer's name. Alphanumeric, 3 positions; optional. |
First Name |
The customer's first name. Alphanumeric, 15 positions; optional. |
Initial |
The customer's middle initial. Alphanumeric, 1 position; optional. |
Last Name |
The customer's last name. Alphanumeric, 25 positions; optional. |
Suffix |
An addition to the customer's full name (such as "M.D.", "Fr.", or "III"). Alphanumeric, 3 positions, optional. |
Company name |
The name of the company placing the order Alphanumeric, 30 positions; optional. |
Street Address |
The name and number of the customer's street address. Alphanumeric, 32 positions; optional. |
Address Line 2 |
The second line available for entering an address, used when street address alone is insufficient. Alphanumeric, 30 positions; optional. |
Apartment |
The Apartment number or Suite number of the delivery address. The format of this field should always include the abbreviation for apartment (Apt.) or Suite (Ste.) followed by the number. Alphanumeric, 10 positions; optional. |
Postal code |
The postal or zip code for this customer. The postal code field allows for entry of a maximum 9-digit code. When using a zip code, you may select up to 9 digits of the extended zip code, excluding hyphen. Note: This format differs from the zip code format you may use in other areas. In most other tables, you include the hyphen when entering an extended zip code (format = xxxxx-xxxx). However, when creating a match code, you disregard such formatting (format = xxxxxxxx).Alphanumeric, 9 positions; optional. |
City |
The name of the city where the customer lives, or receives mail or shipments. Alphanumeric, 25 positions; optional. |
St |
The state or province where the customer lives, or receives mail or shipments (See Setting Up the Zip/City/State (Postal Code) Table (WZIP)). Alphanumeric, 2 positions; optional. |
Instructions:
# | Step |
---|---|
1. |
Select a field from those available. Select Next or Prev to move forward or backward between the four screens. |
2. |
Determine which match code positions you want the field positions to hold. Enter the number of the match code position in the blank provided for the field position. For example, if you want the first three match code positions to consist of the first, third, and fourth positions of the Postal code field, then advance to the screen that displays this field, and enter 1 in the first blank, 2 in the third blank, and 3 in the fourth blank of this field. |
3. |
When you complete the field selection and position numbering process, select OK. The screen displays a warning: The match code algorithm has changed. Are you sure you want to proceed? If you confirm the change, you return to the Display Match Code Summary Screen. When you exit this screen, another pop-up window prompts you to confirm the change again. Important: When you select OK to confirm the change at the second pop-up window, the system will proceed to modify every match code on file. |
4. |
If you select Exit at this second pop-up window, the system displays a warning: The match code algorithm has changed. To avoid a discrepency, regenerate all customer match codes, or return the algorithm to its original values. |
Note:
Whether you select OK or Exit, you return to the Change Match Codes Screen (Maintaining Match Codes) and must repeat the process to correct changes made to the algorithm or to regenerate the match codes.Test Match Code Screen
Purpose: Use this screen to test a new match code pattern.
How to display this screen: Select Test at the Display Match Code Summary Screen.
Field | Description |
---|---|
Match code type |
The standard match code the system uses to flag duplicate customers. There are four match code types:
Display-only. |
Name |
The following 5 fields are available for you to enter the customer's full name: PrefixA title that belongs before the customer's name, such as "Mrs." or "Dr. The prefix value will print on labels, reports, etc. Alphanumeric, 3 positions; optional. First NameThe customer's first name. Alphanumeric, 15 positions; optional. InitialThe initial of the customer's middle name. Alphanumeric, 1 position; optional. Last NameThe customer's last name. Alphanumeric, 25 positions; required if Company name is not present SuffixAn addition to the customer's full name (such as "M.D.", "Fr.", or "III"). Alphanumeric, 3 positions; optional. |
Company name |
The name of the company placing the order. Alphanumeric, 30 positions; required if Last name is not present |
Address |
The customer's full street address. Alphanumeric, 32 positions; optional. |
Apartment |
The Apartment number or Suite number of the delivery address. To enter an apartment or suite address:
Alphanumeric, 10 positions; optional. |
Postal code/city/st |
Three fields are available for you to enter the customer's postal code, city, and state. Postal codeThe postal code or zip code for this customer. Alphanumeric, 9 positions; optional. CityThe city where the customer lives. Alphanumeric, 25 positions; optional. StateThe state or province where the customer lives, or receives mail or shipments. Alphanumeric, 2 positions; optional. |
Match code |
When you select OK, the system generates the match code for the address you entered above. Alphanumeric, 25 positions; display-only. |
Setting Up User-Defined Fields (WUDF)
Purpose: Use Work with User Defined Fields to design a screen containing the information you want to collect for a variety of types of records in Order Management System. For example, you can specify information to capture from customers during order entry or through customer maintenance. User-defined fields are available for:
- different customer types
- items, offers, and related tables
- users, companies, and countries
- divisions and entities
- pay types, ship vias, and warehouses
A complete listing is provided in this topic.
Process overview: Before defining the individual user-defined fields, you must first use Work with User Defined fields to create a link to the related table. You can then enter the detailed information that specifies the type of information you want to collect. Then, you can enter information for individual records in the table.
Example: You want to track the language of each country to which you ship orders. To do so:
- Select Create at the Work with User Defined Fields Screen to create the link to the Country table.
- When you advance to the Create User Defined Field Screen, select a table code of CST (Customer Sold To) and enter a description.
- Select Work with details for the record at the Work with User Defined Fields screen to advance to the Work with User Defined Field Detail Screen (Defining the Fields).
- Select Create to advance to the Create User Defined Field Detail Screen, where you create a record for “language.”
Prompting in order entry: In the case of sold-to customers, you can have this screen open automatically when you enter an order for new or existing customers. See Prompting in Order Entry. For most other types of user-defined fields, you can display this screen by selecting Work with user fields for a record at a “Work with” screen. For example, to work with however, the Order Header User Field table is not available through any screen.
In this topic:
- Prompting in Order Entry
- Work with User Defined Fields Screen
- Work with User Defined Field Detail Screen (Defining the Fields)
Prompting in Order Entry
The system uses the following two system control values to determine when to prompt for user-defined information for a sold-to customer in order entry:
- User-defined Field Prompting for Existing Customers (D33)
- Customer Class for User Defined Field Prompting (G04)
These two system control values work together as follows:
User Defined Field Prompting in Order Entry set to: | Customer Class for User Defined Field Prompting set to: | Result |
---|---|---|
a valid customer class |
prompts for any new or existing customer in the class who has not yet provided the user-defined information |
|
blank |
prompts for any new or existing customer, regardless of class, who has not yet provided the user-defined information |
|
N |
a valid customer class |
prompts for a new customer in the class only if you assign the class before completing the header information and selecting OK Note: If the Default Customer Class in Order Entry (D63) system control value is set to this same customer class, each new customer you create will be assigned to the class automatically, and you will always advance to the prompt screen |
N |
blank |
prompts for any new customer |
For more information: See:
- Entering user-defined field information: Work with User Fields Screen
- Completing user-defined fields in order entry: Entering User Fields
Work with User Defined Fields Screen
How to display this screen: Enter WUDF in the Fast path field at the top of any menu, or select Work with User Defined Fields from a menu.
Field | Description |
---|---|
Cde(Code) |
A code that identifies the table linked to the user-defined fields. Valid values are:
|
Optional. |
|
Description |
The description associated with the table code. Alphanumeric, 25 positions; optional. |
Screen Option | Procedure |
---|---|
Create a user defined field |
Select Create. See Create User Defined Field Screen. |
Change the description of the link to the Customer Sold To table |
Select Change for a code to advance to the Change User Defined Field screen. At this screen, you can change only the description. See Create User Defined Field Screen for field descriptions. See for information on changing the type of information stored in user defined fields. |
Review the code and description of the link |
Select Display for a code to advance to the Display User Defined Field screen. You cannot change any information at this screen. See Create User Defined Field Screen for field descriptions. See Work with User Defined Field Detail Screen (Defining the Fields) for information on reviewing the type of information stored in user defined fields. |
Create, change, delete or display individual user-defined fields |
Select Work with details for a code to advance to the Work with User Defined Field Detail Screen (Defining the Fields). |
Create User Defined Field Screen
To create: Use this screen to link a user-defined field to appear on the Work with User Fields Screen.
How to display this screen: Select Create at the Work with User Defined Fields Screen.
Field | Description |
---|---|
File code |
Identifies the table linked to the user-defined fields. Valid values are:
|
|
|
Create screen: required. Change screen: display-only. |
|
File description |
The description associated with the table code. Alphanumeric, 25 positions; required. |
Note:
You cannot delete the user-defined field link once you create it.See Work with User Defined Field Detail Screen (Defining the Fields) for more information on setting up the individual fields.
Work with User Defined Field Detail Screen (Defining the Fields)
Purpose: Once you create the link to a table, you need to define and sequence the fields available on the new screen. Use this screen to work with the individual fields.
How to display this screen: Select Work with details for the link at the Work with User Defined Fields Screen.
Field | Description |
---|---|
File code |
The code representing the table to which the user-defined fields are linked. Alphanumeric, 3 positions; display-only. |
File description (Unlabeled field to the right of the File code field) |
The description associated with the table code. Alphanumeric, 25 positions; display-only. |
Seq (Sequence) |
A value you assign to a field to control its placement on the screen. Typically, you would assign a sequence number of 10 to the field that should appear first, a sequence number of 20 to the field that should appear second, and so on. Note: This display sequence number differs from the other sequence number field in the User Defined Field Detail table; this other sequence number is not displayed on any screen, although the system can use it to identify user defined field record types.Numeric, 3 positions; optional. |
Field label |
The field label to appear on the user-defined field screen in order entry or customer maintenance. Note: To support passing user-defined fields through the order API, the field label should be in upper case, and should be passed in the Inbound Order XML Message (CWORDERIN) in upper case as well.For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 15 positions; optional. |
Typ (Type) |
A code that identifies the type of field. Valid codes are:
On the Enter User Fields Screen (displayed during Order Entry or from the Sold To Customer table), numeric fields appear on the left side of the screen, text fields appear in the center of the screen, and date fields appear on the right side of the screen. Optional. |
Usage |
A code that identifies whether you are collecting the field information on the user-defined field screen for sold-to customers in order entry. Valid values are:
Optional. |
Screen Option | Procedure |
---|---|
Create a new user defined detail field to use when collecting customer information |
Select Create to advance to the Create User Defined Field Detail Screen. |
Change the sequence, description or characteristics of a field |
Select Change for a field to advance to the Change User Defined Field Detail. See Create User Defined Field Detail Screen for field descriptions. |
Delete a field |
Select Delete for a field. The Confirm Delete window indicates that customer fields have been created, and that you will lose this information if you continue. Select Enter to continue, or select Exit to cancel. |
Review a field |
Select Display for a field to advance to the Display User Defined Field Detail screen. You cannot change any information on this screen. See Create User Defined Field Detail Screen for field descriptions. |
Create User Defined Field Detail Screen
Purpose: Use this screen to specify a new field you will use to collect information.
How to display this screen: Select Create at the Work with User Defined Field Detail Screen (Defining the Fields).
Field | Description |
---|---|
File code |
The code representing the table to which the user-defined fields are linked. Alphanumeric, 3 positions; display-only. |
Seq (Sequence) |
A value you assign to a field to control its placement on the screen. Typically, you would assign a sequence number of 10 to the field that should appear first, a sequence number of 20 to the field that should appear second, and so on. Note: This display sequence number differs from the other sequence number field in the User Defined Field Detail table; this other sequence number is not displayed on any screen, although the system can use it to identify user defined field record types.Numeric, 3 positions; required. |
Field label |
The field label to appear on the user-defined field screen. Alphanumeric, 15 positions; required. |
Typ (Type) |
A code that identifies the type of field. Valid codes are:
Note: On the Enter User Fields Screen (displayed during Order Entry or from the Sold To Customer table), numeric fields appear on the left side of the screen, text fields appear in the center of the screen, and date fields appear on the right side of the screen.Create screen: required. Change screen: display-only. |
Usage |
A code that identifies whether you are collecting the field information on the user-defined field screen for sold-to customers in order entry. Valid values are:
Required. |
Working with Postal Code Formats (WPCF)
Purpose: Use the Work with Postal Code Format function to define the format for printing postal codes on pick slips or gift acknowledgments. Postal codes are defined by country, but each country can have more than one postal code format.
When you print pick slips, the system compares each customer's postal code with the postal code formats you have defined through this function. In order to match a format, the postal code should have the same number of positions and conform in the placement of filler characters, such as hyphens. If the system cannot find a match, no postal code prints on the pick slip. For this reason, it is useful to consider the different postal code formats your operators typically use in Order Entry and define a format to cover each.
In this topic:
Work with Postal Code Format Screen
Purpose: Use this screen to work with the formats you have defined for printing postal codes on pick slips or gift acknowledgments.
How to display this screen: Enter WPCF in the Fast path field or select Working with Postal Code Formats (WPCF) from a menu.
Field | Description |
---|---|
Country |
A code to represent the country for the postal code format. Country codes are defined in and validated against the Country table. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; optional. |
Country description (Unlabeled field to the right of the country) |
The description of the country. Alphanumeric, 30 positions; display-only. |
Code length |
The number of characters in the postal code. Numeric, 3 positions; optional. |
Format postal code |
The postal code format, illustrated by arranging the ten letters of the word "postalcode" in the same order and position as the characters of the postal code will print on the pick slip. Example: The "zip plus 4" postal code used in the United States is represented on this screen as: POSTA-LCOD When printed on the pick slip or gift acknowledgment, this postal code would appear in the following format: 01609-1039 Alphanumeric, 10 positions; display-only. |
Screen Option | Procedure |
---|---|
Change a postal code format |
Select Change for a postal code format to advance to the Postal Code Layout screen in Change mode. You can change only the Formatted postal code positions fields. See Postal Code Layout Screen for field descriptions. |
Delete a postal code format |
Select Delete for a postal code format. |
Display a postal code format |
Select Display for a postal code format to advance to the Postal Code Layout screen in Display mode. You cannot change any information on this screen. See Postal Code Layout Screen for field descriptions. |
Add a new postal code format for a country |
Select Create. See Postal Code Layout Screen. |
Postal Code Layout Screen
To create: Select Create at the Work with Postal Code Format Screen.
Field | Description |
---|---|
Country |
A code to represent the country for the postal code format. Country codes are defined in and validated against the Country table. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required. |
Code length |
The number of characters in the postal code. The maximum number is ten. Numeric, 3 positions; required. |
Formatted postal code positions |
The order and position of each of the postal code digits for pick slips or gift acknowledgments, including any hyphens or other "filler" characters. The first digit of the postal code will print where you enter a 1, the second digit will print where you enter a 2, and so on, up to the tenth digit, which will print where you enter a 0. Example: Create a United States five-digit postal code format as: 1 2 3 4 5 Create a United States "zip plus 4" postal code format as: 1 2 3 4 5 - 7 8 9 0 Create a Canadian postal code format as: 1 2 3 4 5 6 Alphanumeric, 10 positions; required. |
Zip spaces |
This field is not currently implemented. Numeric, 1 position; optional. |
Zip position |
This field is not currently implemented. Valid values:
Optional. |
Instructions:
- Complete the Country field and the Code length field.
- Enter the postal code format in the Formatted postal code positions fields, indicating where each digit of the postal code should print. Include any hyphens or other “filler” characters in your count. See the Formatted postal code positions fields for an example.
Working with Mail/Call Codes (WMCC)
Purpose: Use the Mail/Call Code table to define codes that specify how often, and under what conditions, you will call or send mail to customers.
You can define mail and call codes for sold-to and ship-to customers. See Creating and Updating Customers for more information on working with different customer types.
Note:
The system defaults the value in the Mail flag field (either Y or N) to the Mail code field when you create or change a sold-to customer. (The Mail flag setting itself defaults from the Default Mail Name (D10) system control value.) For this reason, you should define Y and N as valid mail codes in the Mail/Call Code table, so that the system will accept the default as a valid value in the Mail code field.In this topic:
Work with Mail/Call Code Screen
How to display this screen: Enter WMCC in the Fast path or select Work with Mail/Call Codes from a menu.
Field | Description |
---|---|
Mail/call code |
This code defines when, and under what circumstances, you should send mail to or call the customer. The system distinguishes mail codes from call codes by the value in the Type field. Alphanumeric, 3 positions; optional. |
Description |
The description associated with the mail or call code. Alphanumeric, 40 positions; display-only. |
Type |
Indicates whether this is a mail or call code. Valid values are:
Optional. |
Screen Option | Procedure |
---|---|
Change a mail or call code |
Select Change for a mail or call code you want to change to advance to the Change Mail/Call Code screen. You can change only the Description and the Type fields. See Create Mail/Call Code Screen for field descriptions. |
Delete a mail or call code |
Select Delete for a mail or call code. |
Display a mail or call code |
Select Display for a mail or call code to advance to the Display Mail/Call Code screen. You cannot change any information on this screen. See Create Mail/Call Code Screen for field descriptions. |
Add a new mail or call code |
Select Create. See Create Mail/Call Code Screen. |
Create Mail/Call Code Screen
Purpose: Use this screen to create a new mail code or call code.
To create: Select Create at the Work with Mail/Call Code Screen.
Field | Name |
---|---|
Mail/call code |
This code indicates when and under what circumstances to call or send mail to the customer. You cannot use the same code for both a mail code and a call code. The system distinguishes mail codes from call codes based on the value in the Type field. Alphanumeric, 3 positions. Create screen: required. Change screen: display-only. |
Description |
The description associated with the mail or call code. Alphanumeric, 40 positions; required. |
Type |
Indicates whether this is a mail code or a call code. Valid values are:
Required. |
Working with Customer Action Reason Codes (WCAR)
Customer action notes are messages about a customer issue or problem that you need to resolve. You use customer action reason codes to identify and group the issues or problems in customer action notes or track when and how often customers report certain issues or problems.
In this topic:
For more information: See About Customer Action Notes.
Work with Customer Action Reasons Screen
How to display this screen: Enter WCAR in the Fast path field at the top of any menu or select Work with Customer Action Reasons from a menu.
Field | Description |
---|---|
Reason code |
This code represents the reason behind the customer issue or problem. Alphanumeric, 2 positions; optional. |
Description |
A description of the reason code. Alphanumeric, 40 positions; display-only. |
Screen Option | Procedure |
---|---|
Change a reason code |
Select Change for a reason code to advance to the Change Customer Action Reason screen. At this screen, you can change only the customer action reason description. See Create Customer Action Reason Screen for field descriptions. |
Delete a reason code |
Select Delete for the reason code to delete it. |
Display a reason code |
Select Display for a reason code to advance to the Display Customer Action Reason Code screen. You cannot change any information on this screen. See Create Customer Action Reason Screen for field descriptions. |
Create a reason code |
Select Create to advance to the Create Customer Action Reason Screen. |
Create Customer Action Reason Screen
Purpose: Use this screen to create a reason code.
How to display this screen: Select Create at the Work with Customer Action Reasons Screen.
Field | Description |
---|---|
Customer action (Customer action reason code) |
This code reason represents the reason behind the customer issue or problem. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
A description of the reason code. Alphanumeric, 40 positions; required. |
Working with Customer Note Types (WNTY)
Purpose: Use this menu option to set up types of customer notes and the special actions or defaults associated with each. You can review or enter customer notes at the Edit Customer Notes Screen, available through Work with Customers or through order entry, order maintenance or standard order inquiry.
The features you can assign to a note type include:
- Automatic display in order entry: a pop-up window displays when you select the customer in order entry, or when you maintain the customer's order in order maintenance.
- Default text: this text will default into the Note field when you select the note type for a customer. You can override the default if desired.
Note:
The pop-up window displays only when you select the customer as the Sold-to customer on an order, not when the customer is a shipment recipient only (by selecting Sold To/Rcp. or Accept/Add Rcp.).How might you use note types? You might use a note type to alert operators to a customer whose payment history may be fraudulent, or any other information about the customer that warrants special attention, such as purchase habits. You can also use the default text feature to save keystrokes when entering "boilerplate" notes for a customer, or to group customers for reporting purposes.
In this topic:
For more information:
- customer notes: Displaying More Options in OIOM
- how customer note information displays in a pop-up window in order maintenance: Selecting an Order for Maintenance
- how customer note information displays in a pop-up window when you select a customer in order entry: Selecting Customers in Order Entry
Work with Customer Note Type Screen
How to display this screen: Enter WNTY in the Fast path field at the top of any menu or select Work with Customer Note Types from a menu.
Field | Description |
---|---|
Typ (Type) |
The code representing the type of customer note. Alphanumeric, 1 position; optional. |
Description |
A description of the type code. Alphanumeric, 30 positions; display-only. |
Screen Option | Procedure |
---|---|
Create a note type |
Select Create to advance to the Create Customer Note Type Screen. |
Change a note type |
Select Change for a note type to advance to the Change Customer Note Type screen. At this screen, you can change any field but the note type code. For a description of the fields on this screen, see Create Customer Note Type Screen. |
Delete a note type |
Select Delete for a note type to delete it. |
Display a note type |
Select Display for a note type to advance to the Display Customer Note Type screen. You cannot change any information on this screen. For a description of the fields on this screen, see Create Customer Note Type Screen. |
Create Customer Note Type Screen
Purpose: Use this screen to create a note type.
How to display this screen: Select Create at the Work with Customer Note Type Screen.
Field | Description |
---|---|
Type |
A code representing the type of customer note. Alphanumeric, 1 positions. Create screen: required. Change screen: display-only. |
Description |
A description of the type code. Alphanumeric, 30 positions; required. |
Default message |
The text that should default into the customer note field when you add a note of this type at the Edit Customer Notes Screen. This text defaults only if you do not enter any other text into the note field, and you can override or delete defaulted text. You can use the default message text to save keystrokes when entering notes. Alphanumeric, 50 positions; optional. |
O/E message |
This flag indicates whether the note should display automatically when you select the customer in order entry. The note will also display when you select one of the customer's order for order maintenance. Possible settings are:
|
Working with Language Codes (WLAN)
Purpose: Use this menu option to create, change, or delete a language code. You can assign a language to a customer in Creating and Updating Sold-to Customers (WCST).
Note:
The Work with Language Codes menu option is informational only and is not supported by any functionality in Order Management System.In this topic:
Work with Language Codes Screen
Use this screen to review language codes.
How to display this screen: Enter WLAN in the Fast path field or select Work with Language Codes from a menu.
Field | Description |
---|---|
Language |
A code that represents a language. Enter a full or partial language code and select OK to display language codes in alphanumeric order starting with your entry. Alphanumeric, 3 positions; optional. |
Description |
A description of the language. Alphanumeric, 30 positions; display-only. |
Screen Option | Procedure |
---|---|
Create a language code |
Select Create to advance to the Create Language Code Screen. |
Change a language code |
Select Change for a language code to advance to the Change Language Code Screen. |
Delete a language code |
Select Delete for a language code to advance to the Confirm Delete window. Select Delete to delete it; otherwise, select Exit to cancel. |
Create Language Code Screen
Purpose: Use this screen to create a language code.
How to display this screen: Select Create at the Work with Language Codes Screen.
Field | Description |
---|---|
Language |
A code that represents a language. Alphanumeric, 3 positions; required. |
Description |
A description of the language. Alphanumeric, 30 positions; required. |
Change Language Code Screen
To change: Select Change at the Work with Language Codes Screen to advance to the Change Language Code screen. At this screen, you can change the language description. See the Create Language Code Screen for field descriptions.
Work with Customers (WCST)
For information on: | See: |
---|---|
The different types of customers in Order Management System; background and overview |
|
Different scanning and selection options when you select customers for maintenance or review |
|
The screens you use to create or update name, address, and other basic information about a sold-to customer in the Customer table |
|
Reviewing and working with ship-to customers |
|
Reviewing and working with bill-to customers |
|
Establishing contract pricing for a customer |
|
Working with customer tax status, including standard taxes and exemptions |
|
Applying payment method exclusions for a customer |
|
Reviewing customer mail, item, and order history |
|
Working with user-defined fields for customers |
|
Reviewing customer address change history |
|
Reviewing and working with items shipped to customers at no charge in fulfillment of a warranty |
|
Reviewing and working with customer email addresses |
|
Reviewing and working with information on products that the customer owns |
|
Reviewing and working with alternate customer numbers used to cross-reference a customer record in Order Management System with records from external systems |
Creating and Updating Customers
Topics in this part: The following topics describe how to create and maintain customer information on the system through the Customer Maintenance module:
- Understanding Customer Types describes the three types of customers you work with throughout the Customer Maintenance module.
- Selecting Customers explains how to use the Customer Maintenance Selection Screen to search for existing customer records.
- Creating and Updating Sold-to Customers (WCST) describes the Work with Customers screens you use when creating and updating sold-to customers.
- Creating and Updating Ship-to Customers (WCST) describes the screens you use when creating and updating ship-to customers.
- Creating and Updating Bill-to Customers (WCBT) describes the screens you work with when creating and updating bill-to customers.
- Work with Contract Price Screen describes how to establish special contract pricing opportunities for a customer.
- Working with Customer Tax Status describes the tax status that you can apply to customers, including standard taxes and exemptions.
- Working with Pay Type Exclusions describes how to apply payment method exclusion codes to a customer.
- Reviewing Customer History describes how to view a customer's mail history, item history, and order summary and detail history.
- Work with User Fields Screen describes how to change, delete, or display information for user-defined fields.
- Reviewing Customer Address Changes describes how to display address changes that you enter for your customers.
- Printing the Customer Exposure Report (PCER) describes how to print a report listing customer action notes entered and customer action reason codes used on each.
- Printing the Customer Detail Exposure Report (PCAR) describes how to print a report listing customer action notes, including details on the customer.
- Working with Customer Warranty Information (WCST) describes the screens you use to review and work with items you shipped to customers at no charge, in fulfillment of a warranty.
- Working with Customer Email Addresses describes how the system stores and validates email addresses for sold-to customers, and presents the screens you use to work with email addresses.
- Working with Customer Ownership describes how to create and update information about the products a customer owns.
- Working with Alternate Customer Number Cross-References describes the screens you use to work with additional alternate customer numbers assigned to a customer.
- Generic Customer API describes how to create or update
customers through a generic XML message.
For more information see the Web Services Guide on https://support.oracle.com My Oracle Support (ID 2149144.1).
- Customer Engagement Customer Integration describes how to keep customer information in sync with Oracle Retail Customer Engagement when Oracle Retail Customer Engagement is the system of record for customer data.
Creating and Updating Bill-to Customers (WCBT)
Purpose: A bill-to customer represents the person or company that is billed for an order. The system creates a bill-to customer record automatically only when the person being billed for the order is different from the customer who placed the order.
The system stores information on the bill-to customer related to payment arrangements and history; unlike the sold-to customer record, the bill-to customer table does not contain order history information.
Bill-to/sold-to association: Each customer who places orders (the customer sold-to) can be associated with no more than one bill-to customer, but each bill-to customer can be associated with more than one sold-to customer. If a bill-to customer is specified in the Bill to field for a sold-to customer, that bill-to will be added to each order that the sold-to customer places, regardless of payment method. See the system control values listed below for more information on the situations when the system automatically updates the Bill to field for the sold-to customer.
Related system control values:
- Create/Assign Bill To Customers in Order Entry (A76): determines whether you can assign existing bill-to customers to sold-to customers through Order Entry as well as through Customer Maintenance.
- Update Bill-to Address with Sold-to Address Changes (E13): controls whether to prompt the operator whenever you change a sold-to address to see if the bill-to address should receive the same updates.
In this topic:
- Work with Bill To Customers Screen
- Create Bill-to Customer Screen
- Display Duplicate Bill To Window
- Change Bill-to Customer Screen
- Work with Bill To Phone Numbers Screen
- Create Bill To Phone Number Screen
- Work with Bill To Notes Screen
- Work with Ticklers Screen (bill-to customer view)
Related system control values: The following system control values control how the system creates new bill-to customers:
- Create/Assign Bill To Customers in Order Entry (A76) controls whether the system allows you to assign a bill-to customer to a sold-to customer in Order Entry. In this case, the system uses the sold-to customer information for the new bill-to customer.
- Allow Order for New Bill-to Without Order Hold (D84) controls whether orders associated with a new bill-to customer, created automatically by the system in Order Entry, go on UB (unreferenced bill-to) hold.
For more information: On order hold reason codes: see Introducing Order Hold Reason Codes.
Work with Bill To Customers Screen
How to display this screen: Enter WCBT in the Fast path field at the top of any menu or select Work with Bill To Customers from a menu.
Field | Description |
---|---|
Acct # |
A unique number assigned by the system to identify the bill-to customer. Numeric, 7 positions; optional. |
Name (Last/Company) | Last Name The customer's last name. Enter a full or partial last name to list customers who match your entry alphanumerically. Alphanumeric, 25 positions; optional. CompanyThe name of the company placing the order. Alphanumeric, 30 positions; optional. |
First name |
The customer’s first name. Enter a full or partial last name to list customers whose names follow your entry alphanumerically. Enter a full or partial last name and first name to list customers with last names and first names that follow your entry alphanumerically. Alphanumeric, 15 positions; optional. |
St (State) |
The state or province in which the customer lives or receives mail or shipments. See Setting Up the Country Table (WCTY) for more information on state codes. Alphanumeric, 2 positions; optional. |
Postal code |
The postal or zip code for this customer. Alphanumeric, 10 positions; optional. |
Screen Option | Procedure |
---|---|
Create a bill-to customer |
Select Create to advance to the Create Bill-to Customer Screen. |
Change bill-to customer information |
Select Change for a customer to advance to the Change Bill-to Customer Screen. |
Delete a bill-to customer |
Select Delete for a customer to delete it. When you delete a bill-to customer, you lose the customer's billing account history. Note: You cannot delete a bill-to customer that is associated with any unpurged orders or assigned to any sold-to customers. |
Display a bill-to customer |
Select Display for a customer to advance to the First Display Customer Bill To screen. See Create Bill-to Customer Screen for descriptions of the fields on this screen. |
Work with bill-to phone numbers |
Select Phone #’s for a customer to advance to the Work with Bill To Phone Numbers Screen. |
Review customer notes |
Select Notes for a customer to advance to the Work with Bill To Notes Screen. |
Work with ticklers associated with the bill-to customer |
Select Ticklers for a customer to advance to the Work with Ticklers Screen (bill-to customer view). |
Review email correspondence history |
Select Email history for a customer to advance to the Work with Email by Customer Bill To Number Screen. |
Work with user defined fields |
Select User Field for a customer to advance to the Work with User Fields Screen. |
Create Bill-to Customer Screen
Purpose: At the Work with Bill To Customers Screen, select Create to advance to this screen.
Duplicate bill to customer: The Display Duplicate Bill To Window displays if you try to create a bill to customer whose name and address matches an existing bill to customer.
Field | Description |
---|---|
Account # |
A unique number to identify a customer billing account. Numeric, 7 positions; display-only, assigned by the system. |
Hold/bypass/fraud |
Determines the type of credit checking to apply to this customer. Valid values are:
Entering the customer's name in the Fraud table does not by itself add Fraud to this field, although the system still holds all of the customer's orders for fraud. See Working with Customer Fraud Tables (WCFD). Optional. |
Match code |
A code used to identify duplicate customers based on a match on the customer's address. The system assembles a match code for each new customer, and updates the match code when you change any of the related components. Match codes are defined in the Match Code table, and may consist of components of the bill-to customer's name, company name, address and postal code. See Setting Up Match Codes (MMCH). Alphanumeric, 15 positions; display-only. |
Name |
The following 5 fields are available for you to enter the Bill-To customer's full name: PrefixA title (such as "Mrs." or "Dr.") that belongs before the customer's name. The prefix prints on labels, reports, etc. Alphanumeric, 3 positions; optional. First NameThe bill-to customer's first name. Alphanumeric, 15 positions; optional. InitialThe customer's middle initial. Alphanumeric, 1 position; optional. Last NameThe customer's last name. Alphanumeric, 25 positions; required if company name is not present. SuffixAn addition to the customer's full name (such as "M.D.", "Fr.", or "III"). Alphanumeric, 3 positions, optional. |
Company |
The name of the customer's company. Alphanumeric, 30 positions; required if last name is not present. |
Street |
The customer's street address or the number of the customer's post office box (entered as P.O. Box ###). This is the primary delivery address. Alphanumeric, 32 positions; required. |
Apt/suite (Apartment/suite) |
The apartment or suite number of the delivery address. To enter an apartment or suite address: Type APT to indicate an apartment or STE to indicate a suite. Insert a space and type the number of the apartment or suite, for example: APT 4 or STE 116. Alphanumeric, 10 positions; optional. |
Address |
The customer's expanded address. Alphanumeric, three 30-position fields; optional. |
Postal code |
The postal or zip code for the customer. Required only if the Require postal code? flag is selected for the country. See Setting Up the Country Table (WCTY) for background. Validated against the Zip/City/State (Postal Code) table only if postal code is required. Alphanumeric, 10 positions; required or optional based on country. |
City |
The city where the customer lives or receives mail or shipments. Alphanumeric, 25 positions; required. |
St (State) |
The state or province where the customer lives or receives mail or shipments. Required only if the Require state? flag is selected for the country. If you enter a state, it is validated against the State table (accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY)) even if state is not required for the country. If state is required for the country, the system validates that the state you enter is assigned to the SCF for the postal code. Alphanumeric, 2 positions; required or optional based on country. |
Country |
The code for the customer's country. Country codes are defined in and validated against the Country table. Alphanumeric, 3 positions; required. |
Delivery code |
Identifies a business (commercial) or residential address and is used to calculate shipping charges by carriers who use different rate tables when shipping to homes and businesses, such as UPS. Valid values:
Only Business and Residential are valid values for U.P.S. The system defines the shipper on an order as U.P.S. if the Type field in the Ship Via table = U; see Working with Ship Via Codes (WVIA). Optional. |
PO box |
Identifies the address as a post office box. If the address is a post office box, you must use Parcel Post to ship the orders. Valid values are:
|
Language code |
The language code, if any, specified for the bill-to customer. Defined in and validated against the Language table; see Working with Language Codes (WLAN), Informational only. |
Fax |
Indicates whether you can fax this customer. Valid values are:
This field is not currently implemented. |
EDI |
This field is not currently implemented. |
Currency code |
The currency code, if any, specified for the bill-to customer. Defined in and validated against the Currency Code table; see Working with Currency (WCUR). Informational only. Alphanumeric, 3 positions; optional. |
Email address |
The email address where the system sends purchase orders. See Purchase Order Emails for more information. See Email Address Validation for information on how the system verifies that your entry is formatted correctly. Fraud checking: An order associated with this bill-to customer (or whose sold-to customer is assigned to this bill-to customer) goes on EB hold if this email address matches an email address in the Miscellaneous Fraud table; see Working with Miscellaneous Frauds (WMFF). Alphanumeric, 50 positions; optional. |
OptIn |
Indicates the preferred method of correspondence for the bill-to email address. Not currently implemented for bill-to customers’ email addresses. Valid values are:
Defaults from the Default Opt In/Opt Out Flag (G97) system control value, but you can override it. Note: The above value uses the letter O, not the number 0 (zero).Required. |
Phone # (Day, Eve, Fax or Mobile) |
The bill-to customer's day, evening and fax numbers.
|
Telephone Number Format Examples An operator enters a phone number containing 10 numbers: 5085550100 The telephone number format used in the United States to represent an area code, local exchange and local phone number is: (508) 555-0100 When an operator enters a phone number containing 10 numbers (as in the example), the phone number displays so that the first 3 positions are in parenthesis and a hyphen is between the sixth and seventh numbers, regardless of how the operator entered it into the system. If an operator enters a phone number containing 6 numbers, for example 5550100 and no format exists for 6 numbers, the phone number would display as it was entered (5550100). See Work with Telephone Number Format Screen. Alphanumeric, one 14-position field (phone number) and one 4-position field (phone extension); optional. |
Display Duplicate Bill To Window
This window displays if you try to create a bill to customer whose name and address matches an existing bill to customer on the system. The system determines this by assembling a match code for each bill to customer address on the system. A match code is made up of parts of the customer’s name, address, and postal code. The match is a user-defined code defined in the Match Code table.
This window displays the new bill to customer’s name and address and the matching bill to customer(s) on the system. You can:
- Select Display for the matching bill to customer to review additional name and address information to determine whether you should use the exiting bill to customer or create a new bill to customer.
- Select an existing bill to customer and select Select Exist to select an existing bill to customer instead of creating a new bill to customer.
- Select Accept Dup to create the new bill to customer.
Change Bill-to Customer Screen
To change: At the Work with Bill To Customers Screen, select Change for a bill-to customer to advance to this screen. If you change any of the information that the system extracts for the match code, the system updates the match code also. See Create Bill-to Customer Screen for remaining field descriptions.
Customer Workflow Management window: The Customer Workflow Management Window automatically displays when you select Change for a customer if open or in use ticklers exist for the bill to customer. Select Ticklers at this window to advance to the Work with Ticklers Screen (bill-to customer view) where you can review and work with ticklers associated with the bill to customer.
Work with Bill To Phone Numbers Screen
Purpose: Use this screen to review or work with phone numbers for a bill-to account.
How to display this screen: Select Phone #s for a customer at the Work with Bill To Customers Screen.
For more information: See Work with Ship To Phone Numbers Screen and Work with Bill To Customers Screen for field descriptions.
Screen Option | Procedure |
---|---|
Create a new phone number |
Select Create to advance to the Create Bill To Phone Number Screen. |
Change a phone number |
Select Change for a phone number to advance to the Change Bill To Phone Numbers screen. See Work with Bill To Customers Screen and Work with Ship To Phone Numbers Screen for field descriptions. |
Delete a phone number |
Select Delete for a phone number to delete it. |
Create Bill To Phone Number Screen
Purpose: Use this screen to create a phone number for a bill-to account. How to display this screen: Select Create at the Work with Bill To Phone Numbers Screen.
About this screen: See Work with Bill To Customers Screen and Work with Ship To Phone Numbers Screen for field descriptions.
Work with Bill To Notes Screen
Purpose: Use this screen to enter or review notes about the customer's billing account.
How to display this screen:
- Select Notes for a customer billing account at the Work with Bill To Customers Screen.
- Select Notes at the Change Bill-to Customer Screen or Work with Bill To Phone Numbers Screen.
If you Use Workflow Management (H96):
- select Notes for a tickler whose Note type is B (bill to notes) at the Work with Tickler Screen (user/group view) or Workflow Management Screen.
- select OK at the Create Tickler Screen.
- select Notes at the Change Tickler Screen or Display Tickler Screen.
Field | Description |
---|---|
Notes |
Fields where you can view, enter, or delete customer messages. If you need more space, select Next to display additional entry fields. Alphanumeric, 60 positions per line. |
Date |
The date when the note was entered. Numeric, 6 positions (in user date format); display-only, updated by the system. |
Screen Option | Procedure |
---|---|
Enter a new note |
Enter your message in the first Note field and continue until you are done, pressing Tab to advance to the next line if necessary. |
Change an existing note |
Select Add/Change to switch to CHANGE mode. The previously entered note fields will be enterable; you can type over them as necessary. |
Switch back to ADD mode |
Select Add/Change. |
Work with Ticklers Screen (bill-to customer view)
Purpose: Use this screen to review, work with, and resolve ticklers associated with the bill-to customer.
Secured feature: If you do not have authority to the Update All Ticklers (B09) secured feature, you cannot update a tickler that is not assigned to you or your tickler groups or an error message indicates: Not authorized to change.
This secured feature controls updating a tickler by:
- selecting Change for a tickler to change it.
- selecting Delete for a tickler to delete it.
- selecting In process for a tickler to assign the tickler to yourself.
- selecting Resolve for a tickler to resolve it.
If you do not have access to this feature, you can update only ticklers assigned to you or your tickler groups. However, you can still release an order associated with the tickler from hold.
See Workflow Management Overview and Setup for an overview and required setup for workflow management processing.
How to display this screen:
- select Ticklers for a bill to customer at the Work with Bill To Customers Screen.
- select Ticklers at the Customer Workflow Management Window (which displays when you advance to the Change Bill-to Customer Screen screen).
Field | Description |
---|---|
Bill to |
The number and description of the bill to customer associated with the ticklers on the screen. Bill to number: Numeric, 9 positions; display-only. Bill to description: Alphanumeric, 40 positions; display-only. |
S (tickler status) |
The status of the tickler. Valid values:
Optional. |
P (tickler priority) |
The priority of the tickler, indicating how important the issue associated with the tickler is to resolve (1 is the lowest priority and 9 is the highest priority). Numeric, 1 position; optional. |
Assigned (assign date) |
The date the tickler was assigned to the user or tickler user group. Numeric, 7 positions (in user date format); optional. |
Ev (tickler event code) |
The code for the tickler event that created the tickler. Valid values:
See System Delivered Tickler Events. Alphanumeric, 2 positions; optional. |
Cat (tickler category) |
The tickler category assigned to the tickler. Tickler categories are defined in and validated against the Tickler Category table; see Working with Tickler Category (WTCT). Alphanumeric, 3 positions; optional. |
Tickler# |
The tickler number assigned to the tickler, from the Tickler Number number assignment record. Numeric, 9 positions; optional. |
User group |
The group ID code of the tickler user group assigned to the tickler. Tickler user groups are defined in and validated against the Tickler User Group table; see Working with Tickler User Groups (WTUG). Tickler group ID: Alphanumeric, 10 positions; display-only. |
User |
The user ID of the user assigned to the tickler. Users are defined in and validated against the User table; see Working with User Records (WUSR). Alphanumeric, 10 positions; display-only. |
Sts (Status) |
The status of the order associated with the tickler. Valid values:
Alphanumeric, 1 position; display-only. |
Order# |
The order associated with the tickler. Numeric, 9 positions; display-only. |
Sold to |
The sold to customer associated with the tickler. Numeric, 9 positions; display-only. |
Screen Option | Procedure |
---|---|
Change a tickler |
Select Change for a tickler to advance to the Change Tickler Screen. |
Delete a tickler |
Select Delete for a tickler to delete it. You can only delete MN (manually created) ticklers. |
Display a tickler |
Select Display for a tickler to advance to the Display Tickler Screen. See the Change Tickler Screen for field descriptions. |
Release the order associated with the tickler from hold |
Select Release for a tickler to advance to the Release Reason Prompt Pop-Up Window (order header hold), Release Recipient Hold Reason Pop-Up Window (recipient hold), and/or Release Order Payment Method Window (pay type hold). If you release an order from hold for an HO (held order) tickler, the system automatically resolves the tickler. Also, the system evaluates any other ticklers associated with the order to determine if they can be resolved. |
If you select Release for a tickler not associated with a held order, an error message indicates: Order not on hold. If you select Release for a tickler not associated with an order, an error message indicates: Tickler not eligible for this option. Note: You must have authority to the Release Held Orders (ERHO) menu option to release the order from hold. |
|
Select a tickler to work on |
Select In process for a tickler to change the status of the tickler from open to in process. You can only select to work with a tickler that is in an open status; if you select In process for a tickler that is in an in process or resolved status, an error message indicates: Tickler status cannot be changed - resolved or already in process. Selecting this option automatically assigns the tickler to the user and creates a tickler history record. |
Enter or review tickler work notes |
Select Notes for a tickler to advance to the work notes screen, based on the note type defined for the tickler. Note type A advances you to the Edit Customer Actions Window. Note type B advances you to the Work with Bill To Notes Screen. Note type O advances you to the Work with Order Messages Screen. Note type S advances you to the Edit Customer Notes Screen. Note type T advances you to the Work with Tickler Notes Screen. |
Review the tickler source |
Select Detail for a tickler to advance to the source screen, based on the tickler event associated with the tickler. BO, CO, HO, NO, OO, SO, UP, VP, and WF ticklers advance you to the Order Inquiry Header Screen. You cannot view the source for MN ticklers: Requested tickler has no source reference. |
Review tickler history |
Select History for a tickler to advance to the Work with Tickler History Screen. |
Resolve a tickler |
Select Resolve for a tickler to advance to the Resolve Tickler Window. |
Review procedures for a tickler |
Select Procedure for a tickler to advance to the Work with Tickler Event Rule Procedure Screen. You cannot add or change tickler procedures when you advance from the Work with Tickler screen. You cannot review procedures for MN ticklers. |
Create a tickler for the MN (manually created) tickler event |
Select Create to advance to the Create Tickler Screen. Note: To create a MN tickler, you must have authority to the Create Manual Tickler (B13) secured feature. |
Review the number of ticklers in the work queue, based on the selection criteria you have defined |
Select Count to advance to the Current Tickler Count Window window. |
Toggle between displaying open and in use ticklers or resolved ticklers |
Select Open/Resolved. The system toggles between displaying:
|
Printing the Customer Exposure Report (PCER)
Purpose: The Customer Exposure Report tells you the numbers of customer action notes entered in your company within a given date range, sorted by the reason for the note or the person who entered it. The report includes totals for each reason code, including the quantity of notes entered, in process, resolved, and remaining.
A customer action note is a message about a customer issue or problem that you need to resolve. You can enter or resolve customer action notes in:
- order entry, standard order inquiry, or order maintenance by selecting Options to advance to the Display More Options Screen and selecting Customer Action Notes (you can also use this option in quote entry, inquiry, or maintenance)
- Work with Customers by selecting Customer Actions or selecting Customer Actions for a customer at a selection screen; see Selecting Customers or Creating and Updating Sold-to Customers (WCST)
Pop-up window: Until the note is resolved, a window will pop up in quote entry/maintenance or order entry/maintenance when you select a quote or order to remind you of the open issue. The window will also pop up in Work with Return Authorizations if the Display Customer Action Notes/Messages in RA (F64) system control value is selected.
You can assign customer action reason codes to action notes to help you track common issues your customers raise.
Menu option: You can also work with customer action issues through Work with Email by Order Number Screen.
In this topic:
- Customer Exposure Report Selection Screen
- Customer Exposure Report by Reason Code
- Customer Exposure Report by User
For more information: See Working with Customer Action Reason Codes (WCAR).
Customer Exposure Report Selection Screen
How to display this screen: Enter PCER in the Fast path field at the top of any menu or select Customer Exposure Report from a menu.
Field | Description |
---|---|
Date from |
The beginning date for including notes on the report. The current date defaults. Numeric, 6 positions (in user date format); required. |
Date to |
The ending date for including notes on the report. The current date defaults. Numeric, 6 positions (in user date format);required. |
Sort by fields: | |
Customer exposure by reason code |
Select this field to print the Customer Exposure Report by Reason Code. |
Customer exposure by user |
Select this field to print the Customer Exposure Report by User. |
Instructions:
- Optionally, enter a different beginning or end date in the Date from or Date to fields.
- Select the Customer exposure by reason code field to produce the Customer Exposure Report by Reason Code. Select the Customer exposure by user field to produce the Customer Exposure Report by User.
- Select OK. The system validates your entries and highlights any fields you need to correct. Correct any fields and select OK again.
- Select Accept. The system submits the job CUSTEXRPT1 to print the Customer Exposure Report by Reason Code or the CUSTEXRPT2 job to print the Customer Exposure Report by User.
Printing the Customer Detail Exposure Report (PCAR)
Purpose: The Customer Detail Exposure Report by Reason Code gives you a description of the customer for whom the action note was entered within a given date range, sorted by the reason code and status of the action note. The report includes information about the customer, including the customer's address and phone numbers.
A customer action note is a message about a customer issue or problem that you need to resolve. You can enter or resolve customer action notes in order entry, inquiry, or maintenance, quote entry, inquiry, or maintenance, or through Work with Customers. Until the note is resolved, a window will pop up in order entry and quote entry to remind you of the open issue.
You can assign customer action reason codes to action notes to help you track common issues your customers raise.
Note:
If there are multiple customer action notes for a customer, the report lists just the first note.For more information: See Working with Customer Action Reason Codes (WCAR), and Work with Email by Order Number Screen.
Print Customer Detail Exposure Report Screen
How to display this screen: Enter PCAR in the Fast path field at the top of any menu or select Customer Detail Exposure Report from a menu.
Field | Description |
---|---|
Date from |
The beginning date for including notes on the Customer Detail Exposure Report by Reason Code. The current date defaults. Numeric, 6 positions (in user date format); required. |
To (Date to) |
The ending date for including notes on the report. The current date defaults. Numeric, 6 positions (in user date format); required. |
Reason code |
The reason behind the customer action note. You can type in a specific code for this report or leave the field blank in order to view all the reason codes that have been entered for notes with the date range you have selected. Alphanumeric, 2 positions; optional. |
Status to include |
The status of the customer action issue. Valid status codes are:
Required. |
Instructions:
- Optionally, enter a different beginning or end date in the Date from or Date to fields.
- Enter a valid reason code in the Reason code field or leave this field blank to print all valid reason codes.
- Enter a valid status code in the Status to include field or leave this field blank to include all action notes.
- Select OK. The system validates your entries and highlights any fields you need to correct. Correct any fields and select OK again.
- Select Accept. The submitted job generates the Customer Detail Exposure Report by Reason Code.
Working with Customer API (WCAI)
Purpose: Use this menu option to review, work with, delete, or resubmit customer API requests that are in error.
The CWCustomer or CWMessageIn Web Service receives and processes the Inbound Customer Message (CWCustomerIn) and creates or updates a customer, based on the information in the inbound message. If the request is in error for any reason, the system saves the information from the request in the Customer API Work table. If the request also includes email or user-defined field information, this additional information is stored in the Customer API E-mail Work table and the Customer API UDF Work table.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Error reasons: See Error Checking for Add Requests.
For more information: See Generic Customer API, including Adding a Customer using the Customer API, Changing a Customer using the Customer API, and the Inbound Customer Message (CWCustomerIn).
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
In this topic:
- Work with Customer API Screen
- Change Customer API Screen
- Work with Customer API User Field Screen
- Change Customer API User Field Screen
- Work with Customer API Email Screen
- Change Customer API Email Screen
Work with Customer API Screen
How to display this screen: Enter WCAI in the Fast path field at the top of any menu, or select Work with Customer API from a menu.
Field | Description |
---|---|
Date |
The date when the Customer API Work table record was created. Numeric, 6 positions (in user date format); optional. |
Time |
The time when the Customer API Work table record was created. Numeric, 6 positions (HHMMSS format); optional. |
Act (Action) |
The requested action from the cst_action_type in the Inbound Customer Message (CWCustomerIn). If the cst_action_type is D, the system places the message in error with the error reason Invalid Action Type. The system ignores any other value; see Determining Whether to Add or Change a Customer for more information on the logic the system uses to determine whether to create a new customer or change an existing one. Display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Status |
The status of the request. E (error) = The Customer request is in error. blank = The Customer request is ready to reprocess. Alphanumeric, 1 position; display-only. |
Customer# |
The customer number affected by the request.
Numeric, 9 positions; display-only. |
Alternate# |
The cst_interface_cust_nbr, if any, specified in the Inbound Customer Message (CWCustomerIn). No alternate customer number is displayed if the Assign Alternate Customer # (I88) system control value is selected; in this situation, the system assigns the alternate customer number when it actually creates the customer. Alphanumeric, 15 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Rsn |
Not currently implemented. Select Change for the customer API record to advance to the Change Customer API Screen; when you select OK on this screen, the system displays a message indicating the reason why the Customer API record is in error. Alphanumeric, 1 position; display-only. |
Option | Procedure |
---|---|
Change a customer API request record |
Select Change for a customer API request record to advance to the Change Customer API Screen. |
Delete a customer API request record. |
Select Delete for a customer API request record to delete it. |
Work with user-defined fields for a customer API request record |
Select User defined fields for a customer API request record to advance to the Work with Customer API User Field Screen. |
Work with email information for a customer API request record |
Select Email for a customer API request record to advance to the Work with Customer API Email Screen. |
Reprocess a customer API request record |
Select Reprocess for a customer API request record to submit it for processing. The system reprocesses the record only if it is error-free. See Adding a Customer using the Customer API for more information. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Reprocess all customer API requests |
Select Reprocess to submit all eligible request records for processing. See Adding a Customer using the Customer API for more information. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Change Customer API Screen
Purpose: Use this screen to work with customer API requests that are in error based on the information passed in the CustSoldTo element of the Inbound Customer Message (CWCustomerIn).
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
How to display this screen: Select Change for a customer API record in error.
Field | Description |
---|---|
Date |
The date when the Customer API Work table record was created. Numeric, 6 positions (in user date format); display-only. |
Action |
The requested action from the cst_action_type in the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Possible actions are:
Note: You can only create or update a customer; the system does not allow you to delete a customer through the Generic Customer API. See Determining Whether to Add or Change a Customer or the logic the system uses to determine whether to create a new customer or change an existing one.Display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Entered on |
The cst_entry_date from the Inbound Customer Message (CWCustomerIn). Numeric, 6 positions (in user date format); optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Lng (Language) |
The cst_language from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 3 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Class |
The cst_cust_class from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 2 positions; optional (required if the Require Customer Class in OE, WCAT, and WCST (H85) system control value is selected). |
Time |
The time when the Customer API Work table record was created. Numeric, 6 positions (HHMMSS format); display-only. |
Status |
The status of the customer API request. Possible statuses are:
Display-only. |
Created by |
The cst_create_user from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Note: Regardless of the user you select for this field, the system defaults the user ID of the user updating the Customer API record.Alphanumeric, 10 positions; optional. |
Cur (Currency) |
The cst_currency from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 3 positions; optional. |
Comp Cd (Company code) |
The cst_cust_company from the Inbound Customer Message (CWCustomerIn). Numeric, 3 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Customer# |
The cst_cust_nbr from the Inbound Customer Message (CWCustomerIn), or assigned by the system if this is an Add request. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Numeric, 9 positions; display-only. |
Changed by |
The cst_change_user from the Inbound Customer Message (CWCustomerIn). Note: Regardless of the user you select for this field, the system defaults the user ID of the user updating the Customer API record.Alphanumeric, 10 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Typ (Type) |
The cst_cust_type from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 3 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Mail Cd (Mail code) |
The cst_mail_code from the Inbound Customer Message (CWCustomerIn) Not to be confused with the Mail flag. Alphanumeric, 3 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Account# |
The cst_account_nbr from the Inbound Customer Message (CWCustomerIn). Numeric, 7 positions; optional. |
Commer (Commercial) |
The Inbound Customer Message (CWCustomerIn) flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Alt# (Alternate customer #) |
The cst_interface_cust_nbr cst_interface_cust_nbr from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Note: No alternate customer number is displayed if the Assign Alternate Customer # (I88) system control value is selected; in this situation, the system assigns the alternate customer number when it actually creates the customer.Alphanumeric, 15 positions; optional. |
Call Cd (Call code) |
The cst_call_code from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 3 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Name |
The customer’s name from the Inbound Customer Message (CWCustomerIn), consisting of:
Alphanumeric, 47 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Inact (Inactive) |
The cst_inactive flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Company |
The cst_company_name from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; required if no last name is specified. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Apt |
The cst_apt from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 7 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
PO Box |
The cust_po_box flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Suppr Sls Email (Suppress salesman email) |
The cst_suppress_sales_rep_email from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Street |
The cst_street_addr from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 32 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Delivery code |
The cst_delivery_type from the Inbound Customer Message (CWCustomerIn). Valid values:
Required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
The cst_mail_name flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
|
Address |
The cst_addr_line_2, cst_addr_line_3, and cst_addr_line_4 from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 32 positions each; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Deliverable cde (Deliverable code) |
The cst_deliverable flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Rent |
The cst_rent_name flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Orig mail type (Original mail type) |
The cst_orig_mail_type from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Valid values:
Optional. |
Seed |
The cst_seed_name flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. |
Curr mail type (Current mail type) |
The cst_curr_mail_type from the Inbound Customer Message (CWCustomerIn). Valid values:
Optional. |
H/B/F |
The cst_hold_bypass_ fraud flag from the Inbound Customer Message (CWCustomerIn). Valid values:
Optional. |
Postal code |
The cst_orig_mail_type from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 10 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
City |
The cst_city from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 25 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
State |
The cst_state from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 10 positions; required if specified for country. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Country |
The cst_country from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 3 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Job title |
The cst_job_title flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 10 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Exempt status |
The cst_tax_exempt flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 positions optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Cert# (Certificate number) |
The cst_exempt_ certificate from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Day phone |
The cst_day_phone and cst_day_ext from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 14 positions (phone number) and 4 positions (extension); optional. |
Expiry date |
The cst_exempt_expiry from the Inbound Customer Message (CWCustomerIn). Labeled the Second Create Customer Sold To Screen. Numeric, 8 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
VAT |
The cst_vat_nbr from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 20 positions; optional. |
Eve phone (Evening phone) |
The cst_eve_phone and cst_eve_ext from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 14 positions (phone number) and 4 positions (extension); optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Orig source (Original source) |
The cst_original_source from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 9 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Email sts (Email status) |
The cst_email_status from the Inbound Customer Message (CWCustomerIn). The value specified in the Default Opt In/Opt Out Flag (G97) system control value defaults here if no status was specified in the inbound message. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Note: The system displays an error message at this screen if the email status is missing or invalid for the email address specified for the Add or Change request. See Work with Customer API Email Screen.Alphanumeric, 2 positions; optional. |
Assoc (Associate) |
The cst_associate flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. |
Fax |
The cst_fax_phone and cst_fax_ext from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number here, and on reports and other screens.Alphanumeric, 14 positions (phone number) and 4 positions (extension); optional. |
Curr source (Current source) |
The cst_current_source from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 9 positions; optional. |
Rent email |
The cst_rent_email flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Can BO (Cancel backorder) |
The cst_cancel_bo flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Byp rsv (Bypass reservation) |
The cst_bypass_reservation flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Discount% |
The cst_discount_pct from the Inbound Customer Message (CWCustomerIn). Numeric, 5 positions with a 2-place decimal; optional. |
Sls # (Salesrep #) |
The cst_salesman_nbr from the Inbound Customer Message (CWCustomerIn). Numeric, 7 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Do not fax |
The cst_do_not_fax flag from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. |
Col (Column) |
The cst_price_column from the Inbound Customer Message (CWCustomerIn). Numeric, 2 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Item track |
The cst_item_hist_ tracking flag from the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Valid values:
Optional. |
User 1-4 |
The cst_user_field_1, cst_user_field_2, cst_user_field_3, and cst_user_field_4 from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 10 positions each; optional. |
Relate Id |
The cst_relate_id from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 32 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Pop up 1-2 |
The cst_pop_window_1 and cst_pop_window_2 from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 20 positions each; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Reserve Warehouse |
The cst_reserve_warehouse from the Inbound Customer Message (CWCustomerIn).The warehouse must be an allocatable warehouse (the Allocatable flag for the warehouse is selected). Warehouse codes are defined in and validated against the Warehouse table. See Creating and Maintaining Warehouses (WWHS). Numeric, 3 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Pop up 3-4 |
The cst_pop_window_3 and cst_pop_window_4 from the Inbound Customer Message (CWCustomerIn). Alphanumeric, 20 positions each; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Van Route |
The cst_van_route from the Inbound Customer Message (CWCustomerIn).The van route must be a valid van route for the Reserve warehouse. You cannot enter a van route if a Reserve warehouse is not specified. Van routes are defined in and validated against the Warehouse Van Route table.See Work with Van Routes Screen. Alphanumeric, 4 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Van Sequence # |
The cst_van_route_seq from the Inbound Customer Message (CWCustomerIn) You cannot enter a van sequence number if a Van route is not specified. Numeric, 4 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Completing this screen: Complete or correct each required field. See Inbound Customer Message (CWCustomerIn) for more information on how each field is derived and validated.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Note:
- The system displays an error message at this screen if there is an error with the Customer API UDF Work table or the Customer API E-mail Work table. See below for more information on how to advance to the correct screens to correct these errors.
- The system displays the Display Duplicate Sold To window if the customer information in an Add request matches an existing customer. See Adding a Customer using the Customer API for more information.
- For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Option | Procedure |
---|---|
Work with user-defined fields for the customer API request |
Select User fields to advance to the Work with Customer API User Field Screen. |
Work with email addresses for the customer API request |
Select Email to advance to the Work with Customer API Email Screen. |
Work with Customer API User Field Screen
Purpose: Use this screen to review or work with customer user-defined field information passed in the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn).
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
How to display this screen: Select User defined fields for a record at the Work with Customer API Screen, or select User fields at the Change Customer API Screen.
Field | Description |
---|---|
Customer |
The cst_cust_nbr from the Inbound Customer Message (CWCustomerIn), or assigned by the system if this is an Add request. The name of the customer is displayed to the right. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Number: numeric, 9 positions; display-only. Name: alphanumeric, 41 positions; display-only. |
Seq |
The cst_udf_seq from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). This sequence number identifies the type of user-defined field required. See Work with User Fields Screen for more information. Numeric, 9 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Text |
The cst_udf_text from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Number |
The cst_udf_nbr from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Date |
The cst_udf_date from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Option | Procedure |
---|---|
Change user-defined field information |
Select Change for a user-defined field to advance to the Change Customer API User Field Screen. |
Delete user-defined field information |
Select Delete for a user-defined field to delete it. |
Change Customer API User Field Screen
Purpose: Use this screen to review or change the user-defined field information in a customer API Add or Change request.
Correcting user-defined field information: The user-defined field information passed in the Inbound Customer Message (CWCustomerIn) must match the type (text, number, or date) based on the sequence number for the user-defined field detail, or the customer API Add or Change request will be in error. Each customer API user field record must include one of these types of data. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).Work with User Fields Screen for more information.
How to display this screen: Select Change for a record at the Work with Customer API User Field Screen.
Field | Description |
---|---|
Customer |
The cst_cust_nbr from the Inbound Customer Message (CWCustomerIn), or assigned by the system if this is an Add request. The name of the customer is displayed to the right. Number: numeric, 9 positions; display-only. Name: alphanumeric, 41 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Just one of the following fields must be completed. The type of field must match the sequence number for the user-defined field detail. See Work with User Fields Screen for more information. |
|
Text |
The cst_udf_text from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Number |
The cst_udf_nbr from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Date |
The cst_udf_date from the CustUserDefinedField element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 30 positions; optional. v |
Work with Customer API Email Screen
Purpose: Use this screen to review the email addresses included in the CustEmail element of the Inbound Customer Message (CWCustomerIn), or to select an email address for review or update.
How to display this screen: Select Email for an Add or Change request at the Work with Customer API Screen or select Email at the Change Customer API Screen.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Field | Description |
---|---|
Customer |
The cst_cust_nbr from the v, or assigned by the system if this is an Add request. The name of the customer is displayed to the right. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Number: numeric, 9 positions; display-only. Name: alphanumeric, 41 positions; display-only. |
Email address |
The cst_email_address from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 50 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Status |
The cst_email_status from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 2 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Fmt (Format) |
The cst_email_format from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Prm (Primary) |
The cst_email_primary flag from the CustEmail element of the Inbound Customer Message (CWCustomerIn). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 1 position; display-only. |
Option | Procedure |
---|---|
Change an email address in an Add or Change request |
Select Change for an email address to advance to the Change Customer API Email Screen. |
Delete an email address in an Add or Change request |
Select Delete for an email address to delete the email address from the Add or Change request. |
Change Customer API Email Screen
Purpose: Use this screen to review or change the email address information included in a customer API Add or Change request.
How to display this screen: Select Change for an email address at the Work with Customer API Email Screen.
Field | Description |
---|---|
Customer |
The cst_cust_nbr from the Inbound Customer Message (CWCustomerIn), or assigned by the system if this is an Add request. The name of the customer is displayed to the right. Number: numeric, 9 positions; display-only. Name: alphanumeric, 41 positions; display-only. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Email address |
The cst_email_address from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Subject to the email address format edits described under Email Address Validation. Alphanumeric, 50 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Email status |
The cst_email_status from the CustEmail element of the Inbound Customer Message (CWCustomerIn). If no status is specified here, the cst_email_status from the CustSoldTo element defaults; and if no status is specified there, then the value from the Default Opt In/Opt Out Flag (G97) system control value defaults to both. Alphanumeric, 2 positions; required. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Email format |
The cst_email_format from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Display name |
The cst_display_name from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 50 positions; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Primary |
The cst_email_primary flag from the CustEmail element of the Inbound Customer Message (CWCustomerIn). Alphanumeric, 1 position; optional. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). |
Order Inquiry/Maintenance (OIOM)
Note:
You can also review and work with orders in Modern View.For information on: | See |
---|---|
Order Inquiry |
|
Selecting an order for inquiry; different scan options |
|
Reviewing order header information such as name, address, phone number, and source code |
|
Reviewing order detail information (items on the order) |
|
The various additional options available from the order inquiry header and detail screens |
|
Reviewing financial information about the order, such as invoices, refunds, payment methods, and order totals |
|
Reviewing order properties |
|
Reviewing history for an order line |
|
Reviewing history for the order |
|
Track package shipments |
|
Order Maintenance |
|
Order maintenance features and restrictions |
|
Selecting an order for inquiry; different scan options |
|
Possible updates you can make to the order header, including conditions and restrictions |
|
Possible updates you can make to an order detail line, including conditions and restrictions |
|
How to add an order detail line to an order |
|
How to increase or decrease the unit quantity of an order detail line |
|
How to cancel an order detail line |
|
How to cancel an order |
|
How to return or exchange items through order maintenance |
|
How to work with payment methods |
|
How to add an additional shipping address |
Order Inquiry
In this part: Order inquiry spans the breadth of the system's functions, giving you access to customer, order, line, and item summary and detail information. This part presents the screens you use to review this information.
- Using the Order Inquiry Scan Screens (OIOM) shows you how to find an order based on the information available to you.
- Reviewing the Order Inquiry Header Screen presents the Order Inquiry screen, which contains information about the customer, such as name, address, phone number and source code.
- Reviewing Order Inquiry Detail Information presents the Order Inquiry screen containing information on the items the customer has ordered.
- Reviewing Order Details presents the screens you use to review detail related to a specific item on an order.
- Options Available in Order Inquiry presents a table of the functions available from the Order Inquiry Header or Detail screens, and refers you to topics containing more information on the use of these functions.
- Reviewing Financial Information on an Order presents screens that display information pertaining to charges and credits, such as invoices, refunds, and order totals. The topic also includes a discussion of order payment methods.
- Reviewing Order-Level Properties explains how to review order properties.
- Display Order Line History Screen explains how to review all activity performed on a particular item on an order.
- Display Order History Screen explains how to review all activity performed on an entire order.
- Display Package Information Screen describes the screen that lists all tracking numbers associated with shipments for the order and provides live links to shipment tracking pages when available.
- Streamlined Order Inquiry (DORI) describes a consolidated order inquiry option with simplified search options.
- Customer Engagement Purchase History Integration presents the Display Purchase History screen, which contains a customer’s completed sales and return transactions across multiple channels, such as retail, call center, and e-commerce. This purchase history information is from Oracle Retail Customer Engagement.
Streamlined Order Inquiry (DORI)
Purpose: Streamlined order inquiry provides a one-screen snapshot of an order for efficient order inquiry. This option includes a subset of the information available through standard order inquiry, so that you can quickly answer the most frequently asked questions about an order.
When would you use standard order inquiry? You might use standard rather than streamlined order inquiry if you need:
- additional search options (for example, search by customer number, order type, or purchase order number)
- more extensive information related to the customer, order, invoices, payment methods, and items (for example, order detail pricing methods, additional charge codes applied, customer warranty information, pick slips, customer action notes, subscriptions, price override reasons, or deferred billing information)
- the ability to advance to order maintenance and maintain or cancel the order
Standard order inquiry is the default: When you select Order Inquiry within another menu option, you advance to standard order inquiry.
Modern View option: You can also review and work with orders through Modern View.
In this topic:
- First Streamlined Order Inquiry Screen (Find Order or Customer)
- Second Streamlined Order Inquiry Screen (Search Results)
- Third Streamlined Order Inquiry Screen (Order Summary)
- Pop-Up Windows
First Streamlined Order Inquiry Screen (Find Order or Customer)
Purpose: Use this screen to select an order for inquiry, or to search for an order based on information you know about the customer or the order.
How to display this screen: Enter DORI in the Fast path field at the top of any menu, or select Streamlined Order Inquiry from a menu.
Field | Description |
---|---|
Enter Order | |
Order # |
Enter a valid order number (without including the ship-to number) to advance directly to the Third Streamlined Order Inquiry Screen (Order Summary), displaying information on that order. No ship-to number: You cannot search on the ship-to number, just the order number. For example, enter 1234 rather than 1234-1. Multiple ship-tos? If the order number you enter has multiple recipients, you cannot advance directly to one of these ship-tos. For example, if order 1234 has three ship-tos (1234-1, 1234-2, and 1234-3), to review the third ship-to:
If the order number you enter is invalid, you need to enter other search criteria in order to review the order. Cannot combine: You cannot use the order number together with other criteria to search. Order number: numeric, 8 positions. |
or Find Customer |
Enter information about the sold-to customer to display the Customer Results Fields (Select Customer from List Below) so you can identify the customer who placed the order. After you use the Customer Results Fields (Select Customer from List Below) to select the customer, you can then use the Order Results Fields to select a particular order for inquiry. More than 100 matches? If there are more than 100 customers that match your search criteria, the Customer Results Fields (Select Customer from List Below) display just the first 100. In this situation, you need to further refine your search criteria to make sure that the correct customer is included in the search results. Note: Ghost customers are omitted from the search results. |
Postal code |
Enter a full or partial postal or zip code to display customers whose postal codes begin with your entry. Can combine: You can use the Postal code in combination with the Last name or Company name to search for customers. Sort order for search results: When you search based on Postal code, the Customer Results Fields (Select Customer from List Below) are initially sorted in ascending order by postal code (lowest postal code first). Within a postal code, results are sorted in ascending order by customer number. Alphanumeric, 10 positions. |
Last name |
Enter a full or partial last name to display customers whose last names begin with your entry. Note: If a customer record that matches your entry also has a company name specified, the company name is listed before the last name in the search results.Can combine: You can use the Last name in combination with the Postal code or Company name to search for customers. Sort order for search results: When you search based on Last name, the Customer Results Fields (Select Customer from List Below) lists customers as follows:
The screen does not use any other fields, such as middle initial or company name, when sorting customers by name. Alphanumeric, 25 positions. |
Company name |
Enter a full or partial company name to display customers whose company names begin with your entry. Can combine: You can use the Company name in combination with the Last name or Postal code to search for customers. Sort order for search results: When you search based on Company name, the Customer Results Fields (Select Customer from List Below) are initially sorted in ascending alphabetical order by company name. If more than one customer has the same company name, results are sorted in ascending order by customer number. Alphanumeric, 30 positions. |
Phone number |
Enter a full phone number to display customers with that day, evening, or third (fax or mobile) phone number.
Cannot combine: You cannot use phone number together with other criteria to search. Sort order for search results: If more than one customer has a matching phone number, the Customer Results Fields (Select Customer from List Below) are sorted in ascending order by customer number. Alphanumeric, 14 positions. |
Email address |
Enter a full or partial email address to display customers with a matching record in the Customer Sold To Email table.
The Customer Results Fields (Select Customer from List Below) list customers matching your entry in numeric order by customer number. Cannot combine: You cannot use the email address together with other criteria to search. Sort order for search results: If more than one customer has a matching email address, the Customer Results Fields (Select Customer from List Below) are initially sorted in numeric order by customer number. Alphanumeric, 50 positions. |
or Find Order |
Cannot combine: You cannot combine any of the following criteria to search. More than 100 matches? If there are more than 100 orders that match your search criteria, the Order Results Fields display just the first 100. In this situation, you need to further refine your search criteria to make sure that the correct order is included in the search results. |
Customer # |
Enter a valid sold-to customer number to display orders placed by that customer. Sort order for search results: The Order Results Fields list orders placed by the customer in ascending order by order number (most recent first). Numeric, 9 positions. |
Web order # |
Enter a valid web order number to display orders whose E-Commerce order number in the Order Header Extended table matches your entry. In the case of a retail pickup or delivery order assigned through the Order Broker Integration, the web order number is the order number in the system originating the order. If the originating system is Order Management System, the system prefaces this number with the text ORIG#:. For example: ORIG#: 9999-001, where ORIG#: indicates the order originated in Order Management System, 9999 is the original order number in Order Management System, and 001 is the ship to number. Important: Searching by a partial web order number is not supported. If you wish to review a retail pickup or delivery order whose originating system is Order Management System, you must enter ORIG#: 9999-001, where 9999 is the order number and 001 is the ship to number. Sort order for search results: If there is more than one order with the specified alternate order number, the Order Results Fieldslist matching orders in reverse chronological sequence (most recent orders first). Alphanumeric, 35 positions. |
Order date |
Enter or select an order date to display orders matching your entry. The order date might differ from the entered date for an order if, for example, you did not create the order on the system the same day it was received, and wanted to back-date the order so it would receive appropriate priority for reservation and backorder purposes. Sort order for search results: The Order Results Fieldslist orders for the specified date in reverse chronological sequence (most recent orders first). Numeric, 6 positions (in user date format). |
User |
Select the user ID of the person or process that entered or created the order. Sort order for search results: The Order Results Fields list matching orders in reverse chronological sequence (most recent orders first). |
Option | Procedure |
---|---|
Search for customers or orders |
Use the fields described above to search for a sold-to customer or for a particular order, and click Search to display the Customer Results Fields (Select Customer from List Below) or the Order Results Fields. |
Clear data from the screen |
Select Clear to clear your search criteria and previous search results from the screen. Note: If you have removed any columns from the results as described under Sort and Expand Column Options, the deleted columns remain hidden when you search based on new results. |
Second Streamlined Order Inquiry Screen (Search Results)
Purpose: Use this screen to review the results of your search from the First Streamlined Order Inquiry Screen (Find Order or Customer). From the:
- Customer Results Fields (Select Customer from List Below): Select a customer to display the Order Results Fields.
- Order Results Fields: Select an order to advance to the Third Streamlined Order Inquiry Screen (Order Summary).
Field and sort options are described below:
- Customer Results Fields (Select Customer from List Below)
- Order Results Fields
- Sort and Expand Column Options
Maximum 100 results: Search results are limited to the first 100 matching customers or orders, based on your search criteria. For example, if your search results display orders in descending sequence by order number, only the 100 most recent orders are displayed. To see additional customers or orders, you must use different search criteria.
How to display this screen: Complete any of the fields under or Find Customer or or Find Order and click Search.
Customer Results Fields (Select Customer from List Below)
Customer-related search results are described below. The screen displays these results when your search was based on the criteria available under or Find Customer.
Select a customer: You can click a customer number to display the Order Results Fields for that customer, and then select an order.
Field | Description |
---|---|
Customer # |
The number identifying a sold-to customer who matches the search criteria you entered under or Find Customer. Click the customer number to display the Order Results Fields for that customer. Numeric, 9 positions. |
Name |
The customer’s:
Company name: alphanumeric, 30 positions. Last name: alphanumeric, 25 positions. First name: alphanumeric, 15 positions. Middle initial: alphanumeric, 1 position. |
Address |
The first line of the customer’s street address. Alphanumeric, 32 positions. |
City |
The customer’s city. Alphanumeric, 25 positions. |
State |
The customer’s state. Alphanumeric, 2 positions. |
Postal code |
The customer’s postal or zip code. Alphanumeric, 10 positions. |
Order Results Fields
Order-related search results are described below. The screen displays these results when your search was based on the criteria available under or Find Order, or when you select a customer from the Customer Results Fields (Select Customer from List Below).
Note:
The order results fields do not display orders if the selected customer was the order recipient.Select order: You can click an order number to advance to the Third Streamlined Order Inquiry Screen (Order Summary).
If no orders displayed: You can click Search again without clearing your search criteria in order to re-display the same list of customers from your previous search and select a different customer.
Group option: The group option is available for the following fields. See Sort and Expand Column Options for more information.
Field | Description |
---|---|
Order # |
The number identifying an order that matches the search criteria you entered under or Find Order. Click the order number to display the Third Streamlined Order Inquiry Screen (Order Summary) for that order. Numeric, 8 positions. |
Status |
The order status. Possible statuses are:
Header and Ship To status different? If the status for the Order Header is different from the status for the Order Ship To, the Order Ship To status is displayed, unless:
|
Date |
The order date. This date might differ from the entered date if, for example, you did not create the order on the system the same day it was received, and wanted to back-date the order so it would receive appropriate priority for reservation and backorder purposes. Numeric, 6 positions; in user date format. |
Customer |
The sold to customer’s:
Company name: alphanumeric, 30 positions. Last name: alphanumeric, 25 positions. First name: alphanumeric, 15 positions. Middle initial: alphanumeric, 1 position. |
Recipient |
The order recipient’s:
The recipient can be a one-time shipping address; a permanent shipping address; a different sold-to customer; or the sold-to customer’s own address. Company name: alphanumeric, 30 positions. Last name: alphanumeric, 25 positions. First name: alphanumeric, 15 positions. Middle initial: alphanumeric, 1 position. |
Sort and Expand Column Options
Default sort: The initial sort of the search results is based on the search criteria you entered at the First Streamlined Order Inquiry Screen (Find Order or Customer). See the field descriptions (under or Find Customer and or Find Order) for more information.
Displaying more than the first 100 results: Regardless of how you sort or group the information in the search results, the screen does not display any records that are not among the first 100 results based on your search criteria. For example, if your search criteria display orders in descending sequence by order number, only the 100 most recent orders are displayed. To see additional customers or orders, you must use different search criteria.
Options:
Sorting by a Column
Click the column name to sort the displayed search results by the information in that column in either ascending or descending order.
For example, click the Order # column to sort the search results by order number.

If the search results are currently sorted in ascending order (for example, by date), the arrow points up:

If the search results are currently sorted in descending order (for example, by date), the arrow points down:

Expanding a Column
To expand a column so that you can see more information, position your cursor on the border between the column you want to expand and the column to its right until you see a double-pointed arrow; then drag the arrow to the right.
Third Streamlined Order Inquiry Screen (Order Summary)
Purpose:
Note:
Depending on the user’s authority to credit card information, the system may write a record to the Credit Card Audit table when this screen is displayed. See Logging Credit Card Data Access in the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information.How to display this screen: Select an order from the Order Results Fields.
Screen Header
This area of the Third Streamlined Order Inquiry Screen (Order Summary) screen includes:

Field | Description |
---|---|
Order summary information |
Key information to briefly identify the order is in the upper left corner of the Third Streamlined Order Inquiry Screen (Order Summary) screen. |
Order # |
A unique number the system assigns to identify a quote or order. The ship-to number follows the order number, separated by a hyphen; this number identifies each separate shipping address for the order. Order: numeric, 8 positions. Ship-to: numeric, 3 positions. |
Date |
The order date. This date might differ from the entered date if, for example, you did not create the order on the system the same day it was received, and wanted to back-date the order so it would receive appropriate priority for reservation and backorder purposes. Numeric, 6 positions; in user date format. |
Status |
The order ship-to status. Possible statuses are:
Header and Ship To status different? If the status for the Order Header is different from the status for the Order Ship To, the Order Ship To status is displayed, unless:
|
Ship via |
The code for the shipper who delivers the merchandise to your customer. The description of the ship via is to the right. Ship via codes are defined in and validated against the Ship Via table. See Working with Ship Via Codes (WVIA). Ship via: numeric, 2 positions. Description: alphanumeric, 30 positions. |
Order type |
A code that identifies how the quote or order was received, such as by phone or through the order API. You can also use the order type to identify special kinds of orders, such as those you generate as part of a membership program. Order types are defined in and validated against the Order Type table. See Establishing Order Types (WOTY). Alphanumeric, 1 position. |
Entered by user |
The user ID of the person or process who entered the order. Alphanumeric, 10 positions; display-only. |
Web order # |
The order number, if any, defined in the E-Commerce order number field in the Order Header Extended table. This is the web order that was passed through the Generic Order Interface (Order API) and used to identify the order in an external system. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). In the case of a retail pickup or delivery order assigned through the Order Broker Integration, this is the order number in the system originating the order.
See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for more information. Alphanumeric, 30 positions. |
Order totals |
The totals for the Order Ship To are in the center top of the Third Streamlined Order Inquiry Screen (Order Summary) screen, to the left of the Navigation options and to the right of the Order summary information. |
Merchandise |
The total value of the items on the quote or order, excluding freight, additional charges, service charges, tax (but including hidden tax if the order is subject to VAT), handling, and duty. The merchandise total does not include items that are canceled, sold out, or returned. Note: If you create a return by entering an order for a negative quantity, the merchandise total and the other totals are negative amounts.Numeric, 20 positions with a 2-place decimal. |
Tax |
The total sales tax for the quote or order, based on the value of the merchandise and, optionally, freight and special handling charges. If the order is subject to VAT, tax is generally included in the item price rather than in the Tax field. Use standard order inquiry to review the hidden tax for order lines. Numeric, 20 positions with a 2-place decimal. |
Freight |
The total charge for shipping the quote or order, not including additional freight charges. You can define additional freight charges for a carrier to include standard freight; in this case, the freight charges are 0.00. This field also includes service charges by ship via, if any, or order weight charges based on the ship via defined for each ship to customer on the order. See Working with Ship Via Codes (WVIA). The system calculates freight charges based on the freight method defined for the source code. If the system calculates freight as a percentage of the merchandise charges, there might be a penny variation in total freight amount due to rounding differences. Numeric, 20 positions with a 2-place decimal. |
Add’l freight |
The total dollar amount for freight charges, in addition to the base freight charge for the quote or order. Additional freight charges are defined in the Ship Via table. Examples of additional freight charges are overnight shipping or second day delivery. The Add'l freight field here corresponds to the Frt+ field in Order Entry. Numeric, 20 positions with a 2-place decimal. |
Handling |
The cost of any special handling on the quote or order, such as personalizing, monogramming, or engraving, and any gift wrapping charges. If there are any duty charges on the order, they are included in the Handling total. See Work with Duty Rates Screen. You can review the special handling instructions and charges for items at the Order Detail Window. Numeric, 20 positions with a 2-place decimal. |
Add’l charge |
This field can include charges or credits. Additional charges might include: Additional source code chargeAn additional charge for services that apply to the source code or offer. The system applies the additional charge to the quote or order based on the total dollar value of the merchandise. CreditsA credit you apply to the customer's order, such as reimbursement for long distance telephone charges or a promotion discount that is not applied to the merchandise, freight charges, or additional freight charges. Additional shipper/item chargeAn additional charge that applies to the item based on the shipper. Such charges might apply when the item exceeds established shipping rates, such as for oversized items. Dollar discountsA credit applied based on the total dollar value of the merchandise. You can define dollar discounts by source code or offer. If the Prorate Dollar Discounts and Coupons (D90) system control value is selected, the dollar discounts are applied to the detail lines on the quote or order rather than appearing as a negative additional charge. The Add'l charges field displayed here corresponds to the Chg field in Order Entry. Numeric, 13 positions with a 2-place decimal. |
Total |
The total amount the customer owes for the quote or order, including:
The total does not include charges for canceled, returned or sold out items. Numeric, 20 positions with a 2-place decimal. |
Discount |
The total discount applied to the order shipping address. The total discount is calculated by comparing the selling price of merchandise with the item/SKU offer price. If you use a price override on any of the detail lines:
Note: The setting of the Override item offer price field has no effect on orders you receive through the e-commerce interface. If there is a price override reason code in the new order message, the system always processes these orders as if the field is unselected.See Overriding the Item/SKU Offer Price for an overview of the Override item offer price field. Note: This field is not included if the Display Discount on Order Recap Screen (D38) system control value is unselected or if no discount applies to the order.Any dollar discounts by source code or offer appear as a negative additional charge if the Prorate Dollar Discounts and Coupons (D90) system control value is selected. Numeric, 20 positions with a 2-place decimal. |
Shipment tracking |
Information on each order shipment is below the Order summary information. This information is from the Manifest Upload Audit table, and is not available if the order was shipped as a brokered backorder through integration with Order Broker. The screen displays a maximum of 20 shipments. |
Ship via |
The description of the ship via used for the shipment. Ship via: numeric, 2 positions. Description: alphanumeric, 30 positions. |
Tracking number |
The shipping tracking number, as reported by the PC manifesting station, through the Generic Pick In API (Shipments, Voids, and Backorders), or through Manually Confirming Shipments (MCON). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Live link? The tracking number is a live link:
Shipment tracking is disable for company 123 Unable to construct shipment tracking URL for order 456 Where 123 is the company number and 456 is the order number. Error displayed: Also, if the tracking URL is not defined, when you click on the tracking number link at the screens mentioned above, an error window indicates: Tracking information not available. Check Narvar Order Error Export screen for failures. However, a Narvar Order Error Export record is not created because the tracking number link could not be created correctly if there are no other issues with the order request to Narvar. Alphanumeric, 30 positions. |
Date and time shipped |
The date and time when the package was scanned for shipment, as reported by the PC manifesting station, through the Generic Pick In API (Shipments, Voids, and Backorders), or through Manually Confirming Shipments (MCON). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Date: numeric, 6 positions; in user date format. Time: numeric, 6 positions (HH:MM:SS format). |
Option | Procedure |
---|---|
Review order history |
Select History to open the History Window. Note: This option is available only if there is at least one Order Transaction History message on the order. |
Review or enter order messages |
Select Messages to open the Order Messages Window. The word Messages is blue if there are already any messages on the order. |
Advance to order maintenance |
Select Maintain to advance to the Work with Order Screen in Order Maintenance. Authority:
Note: When you return to Streamlined Order Inquiry (DORI) from Order Maintenance, the system displays the First Streamlined Order Inquiry Screen (Find Order or Customer) before displaying the information for the order you just maintained. Do not select any options until the system displays the order you maintained; any updates you made in Order Maintenance will be reflected on the Third Streamlined Order Inquiry Screen (Order Summary). |
Review loyalty account information for a customer that is registered in the Oracle Retail Customer Engagement Loyalty program |
Select Loyalty. When you select this option, the system retrieves the sold to customer’s information from Oracle Retail Customer Engagement.
Note: This option displays only if the Use ORCE Loyalty (M06) system control value is selected and a Relate ID is defined for the sold to customer in the Customer Sold To table; see Customer Engagement Loyalty Integration. |
Review the customer’s purchase history from Oracle Retail Customer Engagement |
Select Purch Hist. When you select this option, the system retrieves the sold to customer’s information from Oracle Retail Customer Engagement and advances you to the Display Purchase History Screen where you can review the completed sales and returns transactions from Oracle Retail Customer Engagement. If a connection could not be made to Oracle Retail Customer Engagement, the system displays an error message similar to the following: Unable to connect to ORCE. Note: This option displays only if the ORCE Customer Integration (L37) system control value is set to INTERACT; see Customer Engagement Purchase History Integration. |
Return to your search results |
Select Exit to return to the Second Streamlined Order Inquiry Screen (Search Results). |
Review order properties |
Select Properties or scroll down to display the Properties area. |
Review payment information |
Select Payment or scroll down to display the Payment area. Note: This option is displayed even if there are no payment methods on the order. |
Review invoices |
Select Invoices or scroll down to display the Invoices area. Note: This option is available only if there is at least one Invoice for the order. |
Review carton contents |
Select Carton Contents or scroll down to display the Carton Contents area. Note: This option is available only if there is at least one Carton Contents record for the order. |
Review refunds |
Select Refunds or scroll down to display the Refunds area. Note: This option is available only if there is at least one refund record for the order. |
Products
Purpose: This area of the Third Streamlined Order Inquiry Screen (Order Summary) screen provides information on each item on the order.
Field | Description |
---|---|
Line # |
A number the system assigns to each item as it is added to the order. A quote or order can have up to 999 lines. Numeric, 3 positions. |
Item |
A code that identifies a unit of inventory. Item codes are defined in and validated against the Item table. Note: The code displayed is the item alias if the customer ordered using an alias and the Display Item Alias (D56) system control value is selected.Alphanumeric, 12 positions. |
SKU |
An item's unique characteristics, such as its size and color. Note: The first 14 positions of the SKU description is displayed instead of the SKU elements if the Display SKU Description in place of SKU Element (F25) system control value is selected.Alphanumeric, three 4-position fields or one 14-position field. |
Name |
The first 30 positions of the description of the item. This is the base item description if the item has SKU’s. Alphanumeric, 30 positions. |
S (Status) |
A one-position code indicating the current status of the item on the order. Possible statuses are:
See Managing Soldouts and Backorders for background.
|
B (Order Broker) |
This field is set to B if the order is fulfilled through integration with the Order Broker, regardless of whether this is a ship-for-pickup, store pickup, delivery, or retail pickup order, if the order line is a brokered backorder, or the order status. See the Order Broker Integration for more information. |
Price |
The actual unit price of the item after applying any discounts, breaks, or overrides. Discounted or overridden item prices are highlighted if the Display Order Line Discount Messages (F01) system control value is selected. Numeric, 13 positions with a 2-place decimal. |
Qty ordered |
The number of units of the item that the customer ordered. Numeric, 5 positions. |
Qty reserved |
The number of units of the item that are currently reserved from stock. The system does not reserve stock on quotes until they are converted to standard orders; see Converting Quotes to Orders. The reserved quantity is reduced when an item is canceled, confirmed for shipment, or unreserved using Interactive Reservation. The system updates this quantity at billing. Numeric, 5 positions. |
Qty printed |
The number of units included on a printed pick slip. Pre-generated picks: The system does not update this field when you create a pre-generated pick for the order line during pick slip preparation; the system updates this quantity when you generate a pick slip . See Applying Pick Slip Preparation to an Order and Performing Pick Slip Generation. Voiding a pick slip: The system reduces the printed quantity if you void the pick slip and don't reprint, or when shipment of the item is confirmed. Order Broker? If the order line has been assigned to the Order Broker for fulfillment (brokered backorder) or if the customer is picking up the order at a store (store pickup), the print quantity here is equal to the ordered quantity. In the case, the Drop ship flag at the Order Detail Window is set to D, although for a brokered backorder, the BO warehouse indicates your distribution center. See Brokered Backorders or Store Pickup Orders for background. Numeric, 5 positions. |
Qty shipped |
The number of units that have shipped. The system updates this quantity at billing. This quantity is negative for a return processed by entering a negative quantity in order entry. Place your cursor over the shipped quantity to display the most recent shipment date for the item on the order. The text No Ship Date Found displays if the system could not find a shipment date for the item on the order. Numeric, 5 positions. |
Qty returned |
The number of units that the customer has returned. This quantity is zero for a return processed by entering a negative quantity in order entry. Numeric, 5 positions. |
Expected date |
Backordered item: The date a purchase order for this backordered item is expected. Note: This field is not displayed for a reserved item, a brokered backorder item, or if there are no open purchase orders for the item.Finished good item: This field indicates when a finished good item created through work order processing will be ready for sale, if the Use Work Order Processing (E37) system control value is selected. See Finished Good Work Order Processing (WWOR) for more information on work orders. Drop ship item: This date is displayed for drop ship items if the Assign Drop Ship Expected Ship Date (I59) system control value is selected. See that system control value for more information. Numeric, 6 positions; in user date format. |
Total |
The extended price of the line, calculated as: Unit price * Order quantity = Extended price Numeric, 20 positions with a 2-place decimal. |
Option | Procedure |
---|---|
Review more information about the order detail line |
Click the icon ( |
Review or enter order detail messages |
Click the icon ( |
Customers
This area of the Third Streamlined Order Inquiry Screen (Order Summary) screen provides the name, address, phone number(s), and email address of:
- the sold-to customer who placed the order
- the shipping address for the order
- the bill-to customer, if any, associated with the order
Note:
If the name and address for the bill-to customer and sold-to customer are identical, the bill-to customer is not displayed.Field | Description |
---|---|
Sold To Information |
The sold-to information identifies the customer who placed the order. |
Name |
Last name, first name, and middle initial of the customer placing the order. Last name: alphanumeric, 25 positions. First name: alphanumeric, 15 positions. Middle initial: alphanumeric, 1 position. |
Company |
The name of the company associated with the customer placing the order. Alphanumeric, 30 positions. |
Address |
Up to four lines indicating the street address and apartment or suite number. First address line: alphanumeric, 32 positions. Apartment or suite: alphanumeric, 10 positions (to the right of the first address line). Address lines 2-4: alphanumeric, 30 positions each. |
City |
The city where the customer lives or receives mail and shipments. Alphanumeric, 25 positions. |
State |
The state where the customer lives or receives mail and shipments. State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Alphanumeric, 2 positions. |
Postal code |
The postal or zip code for the customer’s address. Alphanumeric, 10 positions. |
Country |
The three-position code identifying the customer’s country. Included only if the country does not match the Default Country for Customer Address (B17). Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). Alphanumeric, 3 positions. |
Phone numbers |
The customer’s daytime and evening phone numbers, including any formatting set up through the Work with Telephone Number Format Screen. The mobile phone number is also displayed if the Phone Numbers (D15) system control value is set to MOBILE; however, if this system control value is set to FAX, the fax number is not displayed. Also, any extensions are not displayed. Alphanumeric, 14 positions each. |
Email address |
The order-level email address, if any. See Working with an Order-Level Email Address for information on how the system determines the email address to assign to an order. Alphanumeric, 50 positions. |
OptIn |
The opt-in/opt-out setting for the email address. Possible settings are:
|
Ship to information |
The ship-to information identifies the shipping address of the order, which can be an order ship-to, a permanent ship-to address for the sold-to customer, or a recipient who is another sold-to customer. |
Name |
The last name, first name, and middle initial of the ship-to. Last name: alphanumeric, 25 positions. First name: alphanumeric, 15 positions. Middle initial: alphanumeric, 1 position. |
Company |
The name of the company associated with the ship-to. Alphanumeric, 30 positions. |
Address |
Up to four lines indicating the street address and apartment or suite number. First address line: alphanumeric, 32 positions. Apartment or suite: alphanumeric, 10 positions (to the right of the first address line). Address lines 2-4: alphanumeric, 30 positions each. |
City |
The city where you ship the order. Alphanumeric, 25 positions. |
State |
The state where you ship the order. State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Alphanumeric, 2 positions. |
Postal code |
The postal or zip code for the shipping address. Alphanumeric, 10 positions. |
Country |
The three-position code identifying the country for the shipping address. Included only if the country does not match the Default Country for Customer Address (B17). Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). Alphanumeric, 3 positions. |
Phone numbers |
The customer’s daytime and evening phone numbers, including any formatting set up through the Work with Telephone Number Format Screen. The mobile phone number is also displayed if the Phone Numbers (D15) system control value is set to MOBILE; however, if this system control value is set to FAX, the fax number is not displayed. Also, any extensions are not displayed. Note: The system stores a single phone number for an order ship-to.Alphanumeric, 14 positions each. |
Email address |
The email address associated with the shipping address. If there is not a separate shipping address, this is the sold-to customer’s primary email address. Alphanumeric, 50 positions. |
Bill to information |
Bill-to information is included if the sold-to customer is associated with a bill-to account and the names and addresses for the two records are not identical. |
Name |
The last name, first name, and middle initial of the bill-to account. Last name: alphanumeric, 25 positions. First name: alphanumeric, 15 positions. Middle initial: alphanumeric, 1 position. |
Company |
The company name for the bill-to. Alphanumeric, 30 positions. |
Address |
Up to four lines indicating the street address and apartment or suite number. First address line: alphanumeric, 32 positions. Apartment or suite: alphanumeric, 10 positions (to the right of the first address line). Address lines 2-4: alphanumeric, 30 positions each. |
City |
The city where the bill-to is located. Alphanumeric, 25 positions. |
State |
The state where the bill-to is located. State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Alphanumeric, 2 positions. |
Postal code |
The postal or zip code for the bill-to address. Alphanumeric, 10 positions. |
Country |
The three-position code identifying the country for the bill-to address. Included only if the country does not match the Default Country for Customer Address (B17). Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). Alphanumeric, 3 positions. |
Phone numbers |
The bill-to customer’s daytime and evening phone numbers, including any formatting set up through the Work with Telephone Number Format Screen. The mobile phone number is also displayed if the Phone Numbers (D15) system control value is set to MOBILE; however, if this system control value is set to FAX, the fax number is not displayed. Also, any extensions are not displayed. Alphanumeric, 14 positions each. |
Email address |
The bill-to customer’s email address. Alphanumeric, 50 positions. |
Properties
This area of the Third Streamlined Order Inquiry Screen (Order Summary) screen provides additional information about the order as a whole.
Field | Description |
---|---|
Source |
The source code from the order header. Source codes are unique codes used to identify segments of your customer base or a rented list. Each source code is assigned to one offer and one division. Source codes control the freight and pricing method used on an order. Alphanumeric, 7 positions. |
Entered date |
The date when the order was created. Numeric, 6 positions; in user date format. |
Entered time |
The time of day the order was originally created. Numeric, 6 positions (HH:MM:SS format). |
Ship complete |
Determines whether all the items on an order must ship together. Valid values are:
|
Arrival date |
The date the customer requests to receive the order. The arrival date defaults to the order date, but you can override this default. Numeric, 6 positions; in user date format. |
Purchase order # |
The purchase order number under which the order was placed. From the ref_transaction_no if the order is a retail pickup or delivery order received from the Order Broker. See Building the Retail Pickup (including Ship-for-Pickup) or Delivery Order for more information. Alphanumeric, 15 positions. |
Cancel BO |
Identifies whether to automatically cancel items that are unavailable (backordered) with the first shipment on the order. Valid values are:
If this field is selected, any unshipped line on an order is canceled during billing using the Auto Soldout Cancel Reason (C20), provided this system control value specifies a valid cancel reason code. |
Cancel date |
The date, if any, the customer wants the order canceled if it has not been shipped. The order is not canceled automatically, but is listed on the Order Cancellation List. You can cancel the order manually or contact the customer to extend the deadline. Numeric, 6 positions; in user date format. |
BO priority |
A code that determines the priority for order fulfillment on a backordered item. Defaults from the B/O priority (Backorder priority), if any, specified for the source code; in this case, the header-level value defaults to the Priority field on the order detail line. Priority codes range from 0-9, where: 0 = Low priority. 9 = High priority. |
Calculate freight |
Determines whether the system calculates and adds freight charges and any service charges by ship via to the order:
|
Weight |
The total shipping weight of the items on the order. Numeric, 20 positions with a 3-place decimal. |
Freight override |
Indicates the freight charges for the Order Ship To if they were applied as an override. Numeric, 13 positions with a 2-place decimal. |
Gift |
If this field is selected, this is a gift order, which means:
|
Tax code |
The code and description of the tax status on the order. Valid values are:
See Working with Customer Tax Status for more information. |
Tax identification |
The customer’s tax identification number, typically the certificate that identifies the customer as a reseller or tax exempt; otherwise, the tax identification number does not control taxability. This number is required when the customer's tax code is R (Reseller) or E (Exempt). Alphanumeric, 30 positions. |
Warehouse |
A code that identifies the warehouse from which merchandise on the order ships. A value appears in this field only if it was entered during order entry or order maintenance or was passed through the Order Broker Integration for a retail pickup or delivery order. The warehouse description is to the right. Warehouse code: numeric, 3 positions; display-only. Warehouse description: alphanumeric, 30 positions; display-only. |
Quote origin |
If this field is selected, the order originated from a pre-order quote. See Entering Pre-Order Quotes for an overview and the required setup. |
Broker delivery type |
Indicates whether the order is being fulfilled through the Order Broker Integration. Possible settings are:
|
Batch # |
The system-assigned number for a group of orders. Orders you receive through the order API are assigned to the Default Batch for E-Commerce Orders in Error (G41) if they are in error; similarly, retail pickup or delivery orders that are in error are assigned to the Order Broker Error Batch Number (K90). The system removes the batch number when you accept the batch if the order is error-free. Numeric, 5 positions; display-only. |
Payment
This area of the Third Streamlined Order Inquiry Screen (Order Summary) screen provides summary information about the payment methods used on the order.
Note:
This screen does not include complete payment method details, such as information on deferred or installment billing.Additional options for credit card payment methods: A plus sign next to a credit card payment method indicates that there is additional information available.

Click the plus sign to display any authorization and deposit history. See Credit Card Authorization and Deposit History for field descriptions.

Note:
If you move your cursor over a payment method, it changes color; however, this color change does not indicate that the payment method is an active link.Field | Description |
---|---|
Payment category |
Indicates the category that defines the basic rules for processing a payment. Each payment type is assigned to a payment category. Possible categories are:
See Working with Pay Types (WPAY) for background. |
Pay type description |
The description of the pay type is to the right of the description of the payment category. Alphanumeric, 30 positions. |
Credit card number |
Credit card pay types only: The credit card number the customer used on the order. Masking: If you do not have authority to the Display Full Credit Card Number (B14) secured feature, the credit card number is displayed in the format specified at the Credit Card Number Layout Screen for the associated pay type. For example, ************1443 may display instead of the entire credit card number. See Credit Card Number Format for an overview. View authority: If you do not have authority to the Restrict Access to Credit Card Numbers in OI and OM (A88) secured feature, no credit card number is displayed. Alphanumeric, 20 positions; display-only. |
Expiration |
Credit card pay types only: The date the credit card is no longer active. The expiration date might be zero if the Require expiration date flag for the pay type is not selected. For example, a stored value card credit card type typically does not require an expiration date. If you do not have authority to the Restrict Access to Credit Card Numbers in OI and OM (A88) secured feature, this field is blank. Numeric, 4 positions (MMYY format); display-only. |
CC last 4 |
The last four positions of the credit card number. From the CC Last 4 field in the Order Payment Method table. Alphanumeric, 4 positions; display-only. |
Amount to charge |
The amount to charge this payment method. Always 0.00 for the “catch-all” payment method on an order, meaning any dollar amount not assigned to another payment method applies to this one. Note: If this is a prepay amount, and part of the prepayment total was applied to a membership program, only the remaining amount appears as the amount to charge or amount billed. For example, if the customer sent a check for 100.00 and 80.00 was applied to the membership program, 20.00 appears here. See Membership Overview.Numeric, 20 positions with a 2-place decimal. |
Credit Card Authorization and Deposit History
The information described below is available in the Payment area of the Third Streamlined Order Inquiry Screen (Order Summary) screen by clicking the arrow next to a credit card payment method.
Field | Description |
---|---|
Authorization history |
The authorization history is flagged with a letter H. See Display Authorization History Screen for background. |
Auth history status |
A description of the status of the authorization as updated by the system. Possible statuses are:
|
Amount authorized |
The amount submitted for authorization and approved by the credit card authorization service. Numeric, 20 positions with a 2-place decimal. |
Auth number |
A number assigned by the authorization service for the authorization transaction. Alphanumeric, 16 positions. |
Auth date |
The date the authorization service approved the amount to be charged. Numeric, 6 positions; in user date format. |
Sent date |
The date you transmitted the authorization to the authorization service. Numeric, 6 positions; in user date format. |
Amount deposited |
The amount deposited to the bank for the charge. Numeric, 20 positions with a 2-place decimal. |
Vendor response 1 |
A code indicating the response, if any, from the authorization service. Although the response can be up to 10 positions, only the first four positions are displayed. Alphanumeric, 4 positions. |
Vendor response 2 |
A code indicating the credit card security response, if any, from the authorization service. Although the response can be up to 10 positions, only the first four positions are displayed. Alphanumeric, 4 positions. |
AVS response |
A code indicating the address verification response, if any, from the authorization service. Although the response can be up to 10 positions, only the first four positions are displayed. Alphanumeric, 4 positions. |
Deposit history |
See Display Deposit History Screen for background. |
Deposit history status |
The status of this deposit:
|
Invoice # |
The number the system assigns to a customer's bill or credit. The system generates an invoice during billing. Numeric, 7 positions. |
Type |
Indicates the type of deposit:
Alphanumeric, 10 positions. |
Deposit date |
The date when this deposit history record was created. This is the date when the invoice pay method was deposited. Numeric, 6 positions; in user date format. |
Deposit amount |
The amount deposited. The amount is negative for a return. For a flexible payment option, calculated as follows:
Numeric, 20 positions with a 2-place decimal. |
Response |
The response code from the Credit Card Deposit History table. Alphanumeric, 10 positions. |
Invoices
This area of the Third Streamlined Order Inquiry Screen (Order Summary) screen provides summary information about the shipment or credit invoices billed against the order.
Field | Description |
---|---|
Invoice # |
The number the system assigns to a customer's bill. Assigned when? If the Generate Invoice Number at Pick Gen (H80) or Generate Invoice # at Pick Gen without Address Match (K81) system control value is selected, the system assigns the invoice number at pick slip generation if the order is eligible; otherwise, it assigns the invoice number at billing. Numeric, 7 positions. |
Date |
The date the invoice record was created by billing. Numeric, 6 positions; in user date format. |
Type |
Indicates the type of invoice:
The system does not consolidate credit invoices with other credits or with debit invoices. Alphanumeric, 1 position. |
Merch |
The total dollar value of the merchandise. Merchandise amount does not include tax (with the exception of hidden tax, or VAT), handling, additional charges, or freight. Numeric, 20 positions with a 2-place decimal. |
Freight |
The freight charges for the invoice. This amount may not be equal to the total of all the line-level freight charges. Numeric, 20 positions with a 2-place decimal. |
Tax |
The sales tax for the invoice. This field includes GST and PST, if any. This field does not include hidden tax. Numeric, 20 positions with a 2-place decimal. |
Handling |
The cost of any special handling billed or credited on the invoice. Examples include personalizing, monogramming, or engraving, and any gift wrapping charges. Any duty charges on the invoice are also included in this total. Numeric, 20 positions with a 2-place decimal. |
Add’l charge |
The total additional charges billed or credited on the current invoice. See Add’l charge for examples. Numeric, 20 positions with a 2-place decimal. |
Add’l freight |
The total dollar amount for freight charges exceeding the order's base freight charge. This is a shipper-level charge directly associated with the order, as opposed to the line item. Additional freight is defined for the shipper in the Ship Via table. Examples of additional freight charges that might apply include charges for overnight shipping, second day delivery, or padded van. Additional freight charges may include the standard freight charges, depending on how you have set up the ship via. If you set up a ship via this way, the Freight field is blank. Numeric, 20 positions with a 2-place decimal. |
Total |
The total amount billed or credited, including all related merchandise charges, freight, tax, handling, additional charges, and additional freight. Numeric, 20 positions with a 2-place decimal. |
Option | Procedure |
---|---|
Print order receipts for each ship-to on the order |
Click the order receipt icon to generate the order receipt: ![]()
|
Review the invoice detail records related to the items shipped or returned on the order. |
Click the icon ( |
Carton Contents
This information can come from the Generic Pick In API (Shipments, Voids, and Backorders) or from the PC manifesting station.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Field | Description |
---|---|
Pick # |
A unique number assigned by the system to identify the pick slip. Numeric, 7 positions. |
Carton # |
Identifies the carton number containing the items shipped on the pick slip. Set to 1 unless you used multiple cartons to ship the pick slip. Numeric, 3 positions. |
Item |
The code identifying the item shipped. Alphanumeric, 12 positions. |
SKU |
The item’s unique characteristics, such as its color or size. Included only if the item has SKUs. Alphanumeric, three 4-positions fields. |
Qty |
The quantity of the item shipped in this carton. Numeric, 3 positions. |
Pack date |
The date when the carton was packed or shipped. From the shipment date passed through the pick in API or through PC manifesting. Numeric, 6 positions; in user date format. |
Pack time |
The time when the carton was packed or shipped. From the shipment time passed through the pick in API or through PC manifesting. Numeric, 6 positions (HH:MM:SS format). |
Packer |
The packer passed through the pick in API or through PC manifesting. Alphanumeric, 10 positions. |
Refunds
This area of the screen provides information on any refunds that have been generated for the order. See Issuing Refunds for background.
Field | Description |
---|---|
Pay type |
The code identifying the pay type to be refunded. This pay type might be different from the payment method used to pay for the order if the pay type has an alternate refund type or alternate refund category; see Working with Pay Types (WPAY) for background. Numeric, 2 positions. |
Pay type desc |
The description of the pay type to be refunded. Alphanumeric, 30 positions. |
Status |
The status of the refund. Possible statuses are:
|
Deposit |
Indicates whether the refund has been deposited. A deferred or installment payment plan can prevent the system from depositing a refund in order to offset the deferred or installment amount. For example, if the order payment amount of 60.00 is deferred for 30 days and the customer receives a refund for 20.00, instead of refunding the customer 20.00, the system subtracts the refund amount from the order payment amount. The customer will then pay 40.00 at the end of the 30 days. Valid values are:
|
Current category |
The description of the payment category for the pay type to be refunded. Possible categories are:
|
Original category |
The payment category of the original payment method used on the order. Possible categories are:
|
Amt collected |
The amount that you are refunding to the customer. Numeric, 20 positions with a 2-place decimal. |
Date created |
The date the refund was generated through order activity such as a return. Numeric, 6 positions; in user date format. |
Date processed |
The date, if any, when the refund was processed, written off, or canceled. Numeric, 6 positions; in user date format. |
Manual hold |
Indicates whether you applied a manual hold against the refund through Working with Refunds, Writeoffs and Balances Due (WREF): Y = Manual hold applies N = No manual hold applies |
Hold until |
The date when the refund is eligible for processing. Numeric, 6 positions; in user date format. |
Pop-Up Windows
Purpose: The pop-up windows available at the Third Streamlined Order Inquiry Screen (Order Summary) are:
History Window
Purpose: Use this window to review the activity that has taken place related to the order since it was created. This is the same information available at the Display Order History Screen.
How to display this window: Click History in the Navigation area at the top of the Third Streamlined Order Inquiry Screen (Order Summary).
Field | Description |
---|---|
Date |
The date when the order activity occurred. Numeric, 6 positions; in user date format; display-only, updated by the system. |
Time |
The time when the order activity occurred. Numeric, 6 positions (HH:MM:SS format); display-only, updated by the system. |
Type |
A code for a type of update against the order. Valid values are:
|
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Narvar notices: When you use the Narvar Integration, the Letter notification type for a shipment email can be:
For more information: See Narvar Troubleshooting.
|
|
|
|
Transaction note |
The description of the activity related to the transaction, such as:
|
Special character? If there are any special characters in an Order Transaction History message, the system replaces the special character, excluding any underscores, with a space when you display the message at the Display Order History Screen; however, the History Window might display the special character as a series of alphanumeric characters, such as \u000F. Alphanumeric, 40 positions; display-only. |
|
Amount |
The total order amount following the order activity, including merchandise, freight, tax, handling, etc. No amount is associated with issuing a subscription, as the system bills the customer for the entire amount of the subscription when billing the order. Numeric, 20 positions with a 2-place decimal; display-only. |
User |
The user ID of the person who performed this activity against the order. If the system performs the activity automatically, such as releasing prepaid orders on time hold, the user ID is the name of the person who started the ASYNC processing program (background jobs). If the activity took place through a system process or an API, the user ID indicates the process or API; otherwise, the system uses your default user. Alphanumeric, 10 positions; display-only. |
Order Messages Window
Purpose: Use this window to review or work with free-formatted order-level messages. These are the same messages you can work with at the Work with Order Messages Screen.
See Adding Order Messages for background on working with order messages, including the print requirements and limitations of including messages on different forms; however, important differences between the Work with Order Messages screen and the Order Messages window are:
- Default messages: At the Work with Order Messages Screen, you can apply a message set up through Working with Default Messages (WMSG); however, this option is not available through Streamlined Order Inquiry (DORI).
- Message sequence: At the Work with Order Messages Screen, you can select whether to display the messages in LIFO or FIFO sequence; however, in Streamlined Order Inquiry (DORI), messages are always listed in FIFO sequence.
Change or delete existing messages? The Modify Existing Messages (A30) secured feature controls the ability to change or delete an existing order message. If you have authority to this secured feature, double click on a line to change or delete it; see Working with existing message lines for instructions.
How to display this window: Click Messages in the Navigation area at the top of the Third Streamlined Order Inquiry Screen (Order Summary). The word Messages is in blue rather than black if there are any existing order messages.
Field | Description |
---|---|
Entering new message lines |
Optionally, use the upper part of the window to enter new order messages. |
New message |
Use this field to enter new free-form text messages. If your entry exceeds 60 positions and you do not press Enter to start a new line, the system splits the text into separate lines of up to 60 positions each, using the last occurring blank space before position 60 as a line break. |
Highlight the print option to the right of the New message field. Available options are:
|
|
Click Add when you are done to save your changes. |
|
Working with existing message lines The lower part of the window displays existing order messages. You can review, change, or delete these messages. |
To change:
You can also change the Print option next to a message line. To delete:
|
Message |
A message related to the order. Alphanumeric, 60 positions. |
Available options are:
|
|
Date |
The date when the message was written. Numeric, 6 positions; in user date format. |
Time |
The time when the message was written. Numeric, 6 positions (HH:MM:SS format). |
User |
The user ID identifying the person who wrote the message. Alphanumeric, 10 positions. |
Note:
Depending on your screen resolution, if there are multiple message lines the Exit button might not be visible. In this case, press F12 to exit the window and return to the Third Streamlined Order Inquiry Screen (Order Summary).Order Detail Window
Purpose: Use this window to display additional information about an item on the order.
How to display this window: Click the icon
() in the Detail column next to an
item in the Products area of the Third Streamlined Order Inquiry Screen (Order Summary) screen.
Field | Description |
---|---|
Item |
The item you selected in the Products area of the Third Streamlined Order Inquiry Screen (Order Summary). Note: The code displayed is the item alias if the customer ordered using an alias and the Display Item Alias (D56) system control value is selected.Alphanumeric, 12 positions. |
SKU |
The item's unique characteristics, such as its size and color. Note: The first 14 positions of the SKU description is displayed instead of the SKU elements if the Display SKU Description in place of SKU Element (F25) system control value is selected.Alphanumeric, three 4-position fields or one 14-position field. |
Desc |
The first 30 positions of the description of the item. This is the base item description if the item has SKU’s. Alphanumeric, 30 positions. |
Qty ordered |
The number of units of the item that the customer ordered. Numeric, 5 positions. |
Price |
The actual unit price of the line after applying any discounts, breaks, or overrides. Discounted or overridden item prices are highlighted if the Display Order Line Discount Messages (F01) system control value is selected. Numeric, 13 positions with a 2-place decimal. |
Source |
The source code assigned to the detail line, if any. There might not be a source code on the order detail line if the Use Source Code from Order Header When Creating Order Lines (D73) is not selected. The source code at the line level controls demand and sales information/posting for that item, while the source code on the order controls how to price items and calculate freight. Alphanumeric, 9 positions. |
Offer |
A code for the catalog, space or television advertisement from which you accept quotes and orders. The offer defined for the quote or order controls how to calculate shipping and price items. However, if you override the offer for an item (if the customer is ordering from more than one catalog, for example), demand for the item is attributed to the offer associated with the item rather than the order. Demand represents the number and dollar value of orders placed against an offer. Note: The system automatically overrides the offer for an item if Override Offer on Order Detail Line (D49) system control value is selected and the item is not sold in the offer used on the order.Offers are defined in and validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions. |
Offer price |
The item price as defined for the offer. If the order was subject to VAT and tax-inclusive pricing, in which any tax is included in the Hidden tax field rather than the Tax bucket on the order, the offer price presented here is the tax-inclusive offer price. Note: When a price override reason applies to the order line (whether you enter an override reason manually, or if the system applies the override automatically), the override reason’s Override item offer price setting controls whether to use the regular offer price. See Overriding the Item/SKU Offer Price for a discussion.Numeric, 13 positions with a 2-place decimal. |
G/W |
If this flag is selected, it indicates that the item is gift wrapped. |
Freight |
The charge for shipping the item. This total does not include additional freight charges, and is blank if the freight is calculated for the entire order instead of item-by-item. Numeric, 13 positions with a 2-place decimal. |
Add’l freight |
The dollar amount of shipper/item charges, as defined for the shipper and item at the Work with Ship Via/Item Screen. Numeric, 13 positions with a 2-place decimal. |
Quantities | |
Qty reserved |
The number of units of the item that are currently reserved from stock. The system does not reserve stock on quotes until they are converted to standard orders; see Converting Quotes to Orders. The reserved quantity is reduced when an item is canceled, confirmed for shipment, or unreserved using Interactive Reservation. The system updates this quantity at billing. Numeric, 5 positions. |
Qty printed |
The number of units included on a printed pick slip. Pre-generated picks: The system does not update this field when you create a pre-generated pick for the order line during pick slip preparation; the system updates this quantity when you generate a pick slip. See Applying Pick Slip Preparation to an Order and Performing Pick Slip Generation. Voiding a pick slip: The system reduces the printed quantity if you void the pick slip and don't reprint, or when shipment of the item is confirmed. Order Broker? If the order line has been assigned to the Order Broker for fulfillment (brokered backorder) or if the customer is picking up the order at a store (store pickup), the print quantity here is equal to the ordered quantity. In the case, the Drop ship flag at the Order Detail Window is set to D, although for a brokered backorder, the BO warehouse indicates your distribution center. See Brokered Backorders or Store Pickup Orders for background. Numeric, 5 positions. |
Qty shipped |
The number of units that have shipped. The system updates this quantity at billing. This quantity is negative for returns processed by entering a negative quantity in order entry. Numeric, 5 positions. |
Qty returned |
The number of units that the customer has returned. This quantity is zero for a return created by entering a negative quantity in order entry. Numeric, 5 positions. |
Qty canceled |
The number of units that have been canceled. Numeric, 5 positions. |
Qty sold out |
The number of units that have been sold out, either automatically or manually. Numeric, 5 positions. |
Expected ship date |
Backordered item: the date a purchase order for this backordered item is expected. Note: This field is not displayed for a reserved item, a brokered backorder, or if there are no open purchase orders for the item.Finished good item: This field indicates when a finished good item created through work order processing will be ready for sale if the Use Work Order Processing (E37) system control value is selected. See Finished Good Work Order Processing (WWOR) for more information on work orders. Drop ship item, including brokered item: This date is displayed for drop ship items if the Assign Drop Ship Expected Ship Date (I59) system control value is selected. See that system control value for more information. Numeric, 6 positions; in user date format. |
Next BO date |
The next date when the order line is eligible to generate a backorder notice. See Generate Backorder Notices (GBOC) for more information. Numeric, 6 positions; in user date format. |
Entered date |
The date when the order was created, or when the item was added to the order. Numeric, 6 positions; in user date format. |
Arrival date |
The date when the customer wants to receive this item. The arrival date entered here overrides the arrival date defined for the order. The arrival date for each item is initially set to the current date; however, you can enter some future date in order entry or maintenance to delay shipment of the item. The system defaults a future arrival date to an item with a future ship status if the item's status code matches the Future Orders Item Status (E52). The future arrival date that defaults for this item comes from the Default Future Orders Arrival Date (E53). The arrival date controls:
The arrival date for the item controls whether to reserve inventory as follows: Arrival date - Reservation Lead Days (B27) = Date |
The system does not reserve inventory if the result is a future date. In this case, the item is flagged as a future order and assigned a backorder status. When you run the Evaluate Future Orders process (typically, every evening) it evaluates each item flagged as a future order and reruns the arrival date calculation. When the result is no longer in the future, the process reserves the inventory. See Scheduling Jobs for more information. Influence on Pre-Generated PicksThe item's arrival date also controls whether the system creates pre-generated pick. The system uses this calculation: Arrival Date from Order Line (or Order Ship To) - (Pick Processing Days (B37) + Ship Via Lead Days in WSHV) < or = Today's Date The system creates a pre-generated pick for the order line if this system-calculated date is less than or equal to today's date; otherwise, the system does not create a pre-generated pick for the order line until the date is within the allotted time frame. See Selecting Order Lines for Pick Slip Preparation. |
|
Zone reservation rules: For items subject to zone reservation, this date is:
See Shipping Zone Reservation Overview for a complete discussion. You can use an order line's Arrival date as a selection criterion in pick slip generation. For zone reservation coded inventory such as plant stock, this selection insures that the item will ship at a date suitable for planting at its destination. Numeric, 6 positions; in user date format. |
|
Cancel date |
The date when the customer wants to cancel the item if it has not shipped. Numeric, 6 positions; in user date format. |
Inventory | |
Drop ship |
Set to D for a drop ship item, or for a brokered backorder or store pickup order. In the case of a brokered backorder or store pickup, there is a printed quantity; for a brokered backorder, the BO warehouse indicates your distribution center. Alphanumeric, 1 position. |
Warehouse |
The warehouse shipping the item. Typically set to 0. Some reasons why an order line might be assigned to a specific warehouse:
Warehouse code: numeric, 2 positions. Warehouse description: alphanumeric, 30 positions. |
BO warehouse |
A code that identifies the warehouse assigned to ship a backordered item. Note: This field appears only if there is a backordered quantity of the item.Warehouse code: numeric, 2 positions. Warehouse description: alphanumeric, 30 positions. |
Future order |
This flag indicates that the arrival date for the item is too far in the future to reserve stock. The item is reserved when the current date reaches the requested arrival date minus lead days for picking and shipping. Valid values are:
See the Arrival date for a discussion. |
Affect inventory |
Indicates whether the quantity available to sell (on-hand quantity) of the item is reduced during order entry. Valid values are:
|
Bypass reservation |
Indicates whether to reserve this item during order entry if inventory is available.
Valid values are:
This setting defaults from the Item table if the item is set up to bypass reservation, because it is available in a limited quantity or it is a limited edition. |
Special Handling |
This area of the window provides information on custom or standard special handling for the item. See Special Handling Overview for background. |
Special handling |
The special handling code and description identifying the type of work to be performed on the item. Special handling codes are defined in and validated against the Additional Charges table. Code: alphanumeric, 2 positions. Description: alphanumeric, 30 positions. |
Special handling charge |
The charge for special handling of an item. See Special Handling Overview for background. Numeric, 13 positions with a 2-place decimal. |
Handling information |
One or more lines of free-form text describing the handling for the item. Alphanumeric, 30 positions each line. |
The following lines provide information custom special handling. |
For more information on custom special handling information, see:
|
Label |
A special handling option defined for this custom special handling format. Alphanumeric, 15 positions. |
Input |
The response selected for each special handling option available in the custom special handling format. These fields might be blank if, for example, you use the special handling format only to add a charge to the Handling bucket on the order. The Suppress S/H window field for the additional charge code allows you to suppress the automatic display of the special handling screen in order entry if you use a special handling code for this purpose. Alphanumeric, 45 positions. |
Description |
The description of the response, as specified at the Work with Special Format Response Screen when you set up the valid responses for the format. Alphanumeric, 45 positions. |
Charge |
The charge associated with an option in the custom special handling format. This charge is added to the Handling bucket of the order totals. Numeric, 13 positions with a 2-place decimal. |
Activity |
This area of the window displays order line history. See Display Order Line History Screen for background. |
Activity |
A code for a type of update against this item detail line. Valid values are:
|
Description |
The description of the activity. See above. |
Date |
The date when the activity occurred. Numeric, 6 positions; in user date format. |
Qty |
The quantity of the item affected by this activity. For example, 3- indicates that three units of the item were canceled. Activities that do not affect the order quantity, such as changing the pricing of the order line, do not display a quantity here. This quantity is displayed differently depending on how the item was sold out; see Processing Auto Soldout Cancellations (MASO) for details. Numeric, 5 positions. |
Exc reason |
Represents a reason for the customer to exchange one item for another. Exchange reasons are defined in and validated against the Exchange Reasons table; see Establishing Exchange Reason Codes (WEXR). Numeric, 3 positions. |
Can reason |
The reason for canceling the units or reducing the quantity. A cancel reason code is not displayed for soldout cancellations, whether you sell out the item by selecting Sold-out in order entry or order maintenance, or through Processing Auto Soldout Cancellations (MASO). Cancel reason codes are defined in and validated against the Cancel Reason table; see Establishing Cancel Reason Codes (WCNR). Numeric, 2 positions. |
Rtn reason |
Represents a reason for the customer to return an item. Return reasons are defined in and validated against the Return Reason table; see Establishing Return Reason Codes (WRTR). Numeric, 2 positions. |
Add reason |
Represents a reason for adding an item to the order. The system requires an add reason code if:
Add reason codes are defined in and validated against the Add Reason table; see Establishing Add Reason Codes (WADR). Alphanumeric, 5 positions. |
User |
The user ID of the person who performed the activity. No user is listed if you sold out a line through Processing Auto Soldout Cancellations (MASO). Alphanumeric, 10 positions. |
Note:
Depending on your screen resolution and the contents of this window, the complete contents and the Exit button might not be visible. In this case, press F12 to exit the window and return to the Third Streamlined Order Inquiry Screen (Order Summary). You can review the order line information in standard order inquiry, or increase your screen resolution; see How do I display the Order Management System screens correctly on a laptop?Order Detail Messages Window
Purpose: Use this window to review or work with free-formatted order-detail-level messages. These are the same messages you can work with at the Work with Order Line Messages Screen.
Note:
You cannot apply a message set up through Working with Default Messages (WMSG) through this window; to do so, you can use the Work with Order Line Messages Screen.Change or delete existing messages? The Modify Existing Messages (A30) secured feature controls the ability to change or delete an existing order line message.
How to display this window: Click the
icon () in the Msg column next
to an item in the Products area of the Third Streamlined Order Inquiry Screen (Order Summary) screen.The icon is blue (
)if there are any existing order line messages.
Field | Description |
---|---|
Item |
The item and SKU you selected at the Third Streamlined Order Inquiry Screen (Order Summary). Item: alphanumeric, 12 positions. SKU: alphanumeric, three 4-position fields. |
Entering new message lines | Optionally, use the upper part of the window to enter new order line messages. |
New messages |
Use this field to enter new free-form text messages. If your entry exceeds 60 positions and you do not press Enter to start a new line, the system splits the text into separate lines of up to 60 positions each, using the last occurring blank space before position 60 as a line break. |
Highlight the print option to the right of the New message field. Available options are:
|
|
Click Add when you are done. |
|
Working with existing message lines |
The lower part of the window displays existing order detail messages. You can review, change, or delete these messages. To change:
You can also change the Print option next to a message line. To delete:
Secured feature: The Modify Existing Messages (A30) secured feature controls the ability to change or delete an existing order line message. |
Message |
A message related to the order line. Alphanumeric, 60 positions. |
Available options are:
|
|
Date |
The date when the message was written. Numeric, 6 positions; in user date format. |
User |
The user ID identifying the person who wrote the message. Alphanumeric, 10 positions. |
Invoice Detail Window
Purpose: Use this window to review the invoice details for each item on the order that has been billed or credited.
How to
display this window: Click the icon () in the Detail column next to an item in
the Invoices area of the Third
Streamlined Order Inquiry Screen (Order Summary) screen.
Note:
This icon is available only if Invoice Details exist; it is not available for a credit invoice created by applying a negative additional charge to an order.Field | Description |
---|---|
Line # |
The number of the invoice line for the item. Numeric, 3 positions. |
Item |
The code identifying the item that shipped or was returned. Alphanumeric, 12 positions. |
SKU |
The item’s unique characteristics, such as its color or size. Included only if the item has SKUs. Alphanumeric, three 4-position fields. |
Ship qty |
The shipped quantity of the invoiced item. The quantity is negative in the case of a credit invoice created for a return. Numeric, 5 positions. |
Price |
The actual unit price of the shipped or returned item. Numeric, 13 positions with a 2-place decimal. |
Ship date |
The date the invoice line shipped or the return was processed. Numeric, 6 positions; in user date format. |
Return qty |
The quantity of the item returned on this invoice. Numeric, 5 positions. |
Return date |
The most recent date when the customer returned any quantity of the item billed on this invoice. Numeric, 6 positions; in user date format. |
Performing Order Maintenance
In this part: These topics describe how to update an existing order on the system:
- Introducing Order Maintenance describes how to access Order Maintenance to update an existing order and lists the features and restrictions of this program.
- Selecting an Order for Maintenance describes how to identify the order you wish to update or how to locate a particular order from a scan of orders.
- Work with Order Screen in Order Maintenance lists the fields you can update on the Work With Order screen, describes the results of your updates, and identifies any conditions or restrictions for updating each field.
- Changing Item Detail Line Information in Order Maintenance lists the fields you can update on the Work With Order Line screen, describes the results of your updates, and identifies any conditions or restrictions for updating each field for a specific item on the order.
- Adding an Item in Order Maintenance describes how to add an item to an existing order or how to reopen a closed or canceled order when you add an item.
- Increasing the Quantity Ordered in Order Maintenance describes how to increase or decrease the number of units ordered of an item and describes how to account for the item cancellation when you reduce the quantity ordered.
- Canceling an Item in Order Maintenance describes how to cancel a single, unshipped order detail line on an existing order and describes how to account for the item cancellation from the order.
- Canceling an Order through Order Maintenance describes how to cancel an entire order and describes how to account for the item cancellations resulting from the order cancellation.
- Returning and Exchanging Items in Order Maintenance describes how to perform an item return or exchange by first creating a return authorization, receiving the merchandise return, and crediting the customer.
- Enter Payment Methods Screen in Order Maintenance describes how to add a payment method to the order to release it from hold or how to change or delete payment information already defined for the order.
- Adding a Recipient Order in Order Maintenance describes how to enter an additional order to an existing order that will ship to a different address.
- Maintaining Quotes in Order Maintenance describes the updates you can apply to a pre-order quote before converting it to a regular order.
- Converting Quotes to Orders describes how to convert a pre-order quote to a regular order and the updates that the system performs.
- Order Line History In API allows you to receive order line history from an external system.
- Order Maintenance API allows you to remove a user hold or update the arrival date for an order line.
- Order Maintenance API allows you to update the arrival date, remove a user hold, or both.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Order Status Reports and On-line Inquiries
In this part: This part presents the reports and on-line inquiries you use to monitor order activity for your company according to a variety of criteria.
- Order Status and Activity Reports provides examples of the reports related to researching an order through Order Inquiry, including order cancellation reports, backorder reports, sales journals, shipment analyses, and prepaid orders lists.
- Displaying Open Orders by Item (DOOI) describes several on-line inquiry functions that can help you evaluate your order activity.
- Ship Via/Item Inquiry (SVII) describes how to review the shippable orders for different shippers, broken out by item.
- Printing Backorder Reports by Descending Dollars (PBOD) describes how to generate the Backorder Report by Descending Dollars and provides a sample report
- Reviewing Operations Control Summary (FLSH) allows you to review operations and merchandising summary information.
- Reviewing Pending Orders (DOSS) describes how to review orders requiring further processing or action.
- Sales Summary (DSSS) describes a screen you can use to review sales numbers and amounts for the current date, week, and month, as well as sales for the current date broken out by order type and entity.
- Printing the Order Type Summary by Delivery Type Report (PDTS) describes how to generate the Order Type Summary by Delivery Type Report and provides a sample report.
Submit Order Cancellation List Screen (POCL)
Purpose: Use this screen to print the Order Cancellation List, a list of orders that have impending cancellation dates due to soldout items, automatic backorder cancellation, and other cancel conditions. This information gives you the option to contact customers before canceling their orders.
Quotes: The Order Cancellation List also includes quotes that contain items whose Cancel date in the Order Detail table are older than the date you generate the report. See Cancelling a Quote through Order Maintenance for more information on how to cancel a quote.
How to display this screen: Enter POCL in the Fast path field at the top of any menu or by selecting this option from a menu.
Printing Backorder Reports (PBOR)
Purpose: Use this function to obtain various types of backorder reports, which give you visibility into your backorder situation, based on an item, warehouse or vendor. You may run these report for the base items only (at the model level) or for each backordered SKU.
Quotes: Items that are on backorder on quotes do not print on the backorder reports; the system includes the items on the backorder reports when the quote is converted to an order. See replace for an overview and Converting Quotes to Orders.
Print Backorder Report Selection Prompt Screen
The system submits a series of backorder reports if you make multiple selections on this screen.
How to display this screen: Enter PBOR in the Fast path field at the top of any menu or select this option from a menu.
Field | Description |
---|---|
By item |
Determines whether the system will generate a backorder report that is sorted by item number. Valid values are:
If both this field and the Print SKU detail field are Yes, the system also generates the Backorder Report by Item with SKU Details. |
By whse/item (By warehouse/item) |
Determines whether the system will generate a backorder report that is sorted by warehouse. Valid values are:
Optionally, you may enter a valid warehouse code in the next field to run the report for a particular warehouse; if you set this field to No, the system runs the report for all warehouses. If both this field and the Print SKU detail field are Yes, the system also generates the Backorder Report by Warehouse with SKU Details. |
Warehouse (Unlabeled field to the right of the By whse/item field) |
The warehouse for which you want to run this report. Leave this field blank if you want to run the report for all warehouses; otherwise, enter a valid warehouse code to run the report for the specified warehouse. Warehouse codes are defined in and validated against the Warehouse table. See replace. Numeric, 3 positions; optional |
By vendor |
Determines whether the system will generate a backorder report that is sorted by vendor number. Valid values are:
Optionally, you may type a vendor code in the next field to run the report for a particular vendor; otherwise, the system runs the report for all vendors. If both this field and the Print SKU detail field are Yes, the system also generates the Backorder Report by Vendor with SKU Details. |
Vendor number (Unlabeled field to the right of the By vendor field) |
Represents the supplier of an item you sell. Leave this field blank if you want to run the report for all vendors; otherwise, enter a valid vendor code to run the report for the specified vendor. Vendor codes are defined in and validated against the Vendor table. See replace. Numeric, 7 positions; optional. |
By vendor w/PO |
Determines whether the system will generate a backorder report that is sorted by vendors with open (unreceived or partially received) purchase orders. Valid values are:
Optionally, you may type a vendor code in the next field to run the report for a particular vendor; otherwise, the system runs the report for all vendors. No backordered items will be listed on this report if there are no open POs for these items. If both this field and the Print SKU detail field are Yes, the system also generates the Backorder Report by Vendor/SKU/PO. |
Vendor number (Unlabeled field to the right of the By vendor w/PO field) |
Represents the supplier of an item you sell. Leave this field blank if you want to run the report for all vendors; otherwise, enter a valid vendor code to run the report for the specified vendor. Vendor codes are defined in and validated against the Vendor table. See replace. Numeric, 7 positions; optional. |
Print SKU detail |
Determines whether the backorder report(s) will list the backordered items at the base item (model) level or at the SKU level. Valid values are:
An example of a base item is SILK DRESS. SKUs may exist for this item to identify the various styles in which the item is sold, such as PETITE/RED; PETITE/BLUE; PETITE/WHITE, etc. If you do not print the SKU detail, the system will identify the backorder level at the top level (SILK DRESS); otherwise, if you print the SKU detail, the system will list the backorder level only for each backordered SKU of the item. |
Printing the Sales Journal (PDSJ)
Purpose: Use this option to specify the date range, and optionally, the division for which you want to print a Sales Journal. This report provides a detailed audit trail of all sales transactions for the specified date range (and division, if specified), including all shipments, returns, credits and no charge sales transactions. The system registers a sales transaction when a shipment occurs.
This report provides a detailed listing of sales activity for the specified invoice date range.
Understanding this report: This report is divided into two halves; the left half provides sales information relating to each invoice and the right half provides information about how each sale was posted. The invoice totals on the report are from the Invoice Ship To record.
Out-of-Balance Invoices
If an invoice is out of balance: An invoice is flagged as out of balance on the Sales Journal and Sales Journal by Division if the total Merchandise, Freight, Additional freight, Tax, Handling, and Additional charge for all Invoice Pay Method records do not equal the corresponding totals for the Invoice Ship To record. If the Invoice Pay Method total is higher than the Invoice Ship To total, the out-of-balance amount is negative; otherwise, if the Invoice Pay Method total is lower than the Invoice Ship To total, the out-of-balance amount is positive.
How can an invoice be out of balance? Invoices should ordinarily never be out of balance, but sometimes it is possible for this situation to occur if, for example, there is a rounding difference in the tax calculation on an order with multiple payment types.
Error report: Use the Printing Sales Journal Errors (PSJE) menu option to print a report listing just the out-of-balance invoices for a time period.
Fixing an out-of-balance invoice: Contact your Order Management System representative for assistance in fixing an out-of-balance invoice.
Reporting by Division
When you run the report, you can choose to run it by division. If so, the report lists all sales transactions for the division and starts a new page for each division. The division code is determined by the source code used on the order header.
If you do not print the report by division, the report lists sales transactions in invoice number/date sequence.
How to display this screen: Enter PDSJ in the Fast path field at the top of any menu or select Print Daily Sales Journal from a menu.
Field | Description |
---|---|
Invoice date from |
The beginning date to include on the report. The invoice date represents the date when the shipment or return credit occurred. This field defaults to the current date. Numeric, 6 positions (in user date format); required. |
Invoice date to |
The ending date to include on the report. The invoice date represents the date when the shipment occurred. This field defaults to the current date. Numeric, 6 positions (in user date format); required. |
Print by division |
Indicates whether you want to sort, subtotal, and page break the report by sales division. If not, the report lists all sales transactions sorted by invoice date/number. Valid values are:
|
Instructions:
- Enter or verify the date range you want to include on the Sales Journal. The system defaults the current date in the Invoice date from and Invoice date to fields.
- Select the Division field if you want to print sales transactions grouped by sales division (the Sales Journal by Division); otherwise, the report lists sales transactions by invoice number/date (the Standard Sales Journal).
- Select OK to accept your entries.
- Select Accept to print or reprint the Sales Journal for the specified invoice date.
Printing the Sales Journal by Pay Type (PSJP)
Purpose: Use this option to print the Sales Journal by Pay Type, a detailed audit trail of all sales transactions for the specified date range, including all shipments, returns, credits and no charge sales transactions, grouped by payment method and payment plan type. The system registers a sales transaction when a shipment occurs.
This report provides:
- a detailed listing of sales activity for the specified invoice date range
- totals for each pay type
- a grand total for all paytypes
Understanding this report: This report provides information about the individual charges on each invoice, grouped by pay type. The totals on this report are from the Invoice Pay Method records.
The individual order charges in the Merchandise, Freight, Add'l frt, Tax, Handling, and Add'l charge columns on the left side of the report are totaled in the Total invoice field on the right side of the report.
This report provides totals for the number of credits (refunds) and invoices (shipments) for each payment plan type, each pay type and page breaks between each pay type. A grand total is provided at the end of this report.
How to display this screen: Enter PSJP in the Fast path field at the top of any menu or select Print Sales Journal by Pay Type from a menu.
Field | Description |
---|---|
Invoice date range |
The date range for which you want to run this report. The invoice date range represents the dates on which shipments occurred. Both fields default to the current date. Numeric, 6 positions (in user date format); required. |
To print the report:
Enter or verify the date range for which you want to print the Sales Journal by Pay Type. The current date defaults to the Invoice from and Invoice to fields.
Printing the Sales Journal Summary (PSJM)
Purpose: Use this report as an audit trail of consolidated sales information for an entity, offer, period, or invoice date. This report summarizes all invoice records by offer or invoice date for a month and shows how these invoices were posted.
This report shows your cost for the items sold, the price at which you sold these items, and the corresponding gross profit dollars and gross profit percentage you realized from these sales. The totals on this report are from the Invoice Ship To records.
This report is typically used by the Accounting department to reconcile the month's sales figures.
How to display this screen: Enter PSJM in the Fast path field at the top of any menu or select Print Sales Journal Summary from a menu.
Field | Description |
---|---|
Start date |
The earliest date for which you want to print sales figures on this report. Only invoices printed on this date, and up to the date in the End date field will be included. This field defaults to the current date. Numeric, 6 positions (in user date format); required. |
End date |
The last date for which you want to print sales figures on this report. Only invoices printed up to this date, starting from the date in the Start date field will be included. This field defaults to the current date. Numeric, 6 positions (in user date format); required. |
By period |
Controls whether to print the Sales Journal Summary by Period. This report sorts in offer code sequence within period, and provides consolidated sales information for each offer, in relation to accounting period. Totals are provided for each period, and a grand total of sales for all periods is provided at the bottom of the report. Valid values are:
|
By offer |
Controls whether to print the Sales Journal Summary by Offer. This report provides consolidated sales information for each offer. A grand total of sales for all offers is provided at the bottom of the report. This report is sorted in alphanumeric offer code sequence. Valid values are:
|
By merch$ (By merchandise dollars, descending) |
Controls whether to print the Sales Journal Summary by Descending Dollars. This report sorts in descending (highest-to-lowest) dollar order for each offer within each period, and provides consolidated sales information for each offer, within each accounting period. A grand total of sales for all periods is provided at the bottom of the report. Valid values are:
|
By invoice date |
Controls whether to print the Sales Journal Summary by Invoice Date. This report sorts by invoice date and division, and provides consolidated sales information for each offer. A grand total of sales for all periods is provided at the bottom of the report. Valid values are:
|
By entity/offer |
Controls whether to print the Sales Journal Summary by Entity/Offer. This report sorts in offer code sequence within entity, and provides consolidated sales information for each offer, in relation to entity. Totals are provided for each entity, and a grand total of sales for all entities is provided at the bottom of the report. Valid values include:
|
Note:
You must select at least one of the sort selection fields described above (By period; By offer; By merch$ descending; By invoice date; By entity/offer). A report prints for each sort selected.Instructions
-
Verify or enter the range of dates for which you want to report sales information.
-
Select the desired report by selecting the By period, By offer, By merch$ descending, By invoice date and/or By entity/offer field(s).
-
Select OK to submit the report(s) for printing.
Printing Sales Journal Errors (PSJE)
Purpose: Use the Sales Journal Errors Report to identify invoice records that are out of balance. Invoices that are out of balance are also flagged on the Standard Sales Journal and Sales Journal by Division.
How can an invoice be of balance? Invoices should ordinarily never be out of balance, but sometimes it is possible for this situation to occur if, for example, there is a rounding difference in the tax calculation on an order with multiple payment types.
If an invoice is out-of-balance: An invoice is flagged as out-of-balance if the total Merchandise, Freight, Additional freight, Tax, Handling, and Additional charge for all Invoice Pay Method records do not equal the corresponding totals for the Invoice Ship To record. If the Invoice Pay Method total is higher than the Invoice Ship To total, the out-of-balance amount is negative; otherwise, if the Invoice Pay Method total is lower than the Invoice Ship To total, the out-of-balance amount is negative.
Fixing out of balance invoices: Contact your Order Management System representative for assistance if any invoices are out of balance.
Print Sales Journal Errors Screen
How to display this screen: Enter PSJE in the Fast path field at the top of any menu, or select Print Sales Journal Errors from a menu.
Completing this screen: Confirm that the Start date and the End date are correct, or override the dates if needed, then select Submit. Both fields default to the current date.
Printing the Order Shipment Analysis (POSA)
Purpose: Use this screen to obtain the Order Shipment Analysis Report, a list of the shipments for the specified date.
How to display this screen: Enter POSA in the Fast path field or select this option from a menu.
Note:
The system uses program CSR0604 to print this report.Field | Description |
---|---|
Date |
The date for which you want to review shipment activity. Numeric, 6 positions (in user date format); required. |
Printing the Open Prepaid Order List (POPP)
Purpose: Use the Open Prepaid Order List to see relevant balance and payment information on all open prepaid orders. This report also shows refund or balance due figures where applicable. The report sorts in ascending customer number order.
To print the report, enter POPP in the Fast path field at the top of any menu, or select this option from a menu. There is no prompt screen to complete.
Print the Order Addition Report (PAAR)
Purpose: Use the Order Addition Audit Report to review the add reason codes used to add items to orders in order entry or order maintenance.
If the replace system control value is selected, the system requires an add reason code each time you add an item to an order in order maintenance.
If the Require reason code field for an item offer or SKU offer is selected, the system requires an add reason code each time an operator adds an item to an order in order entry or order maintenance.
You can use add reason codes to track the reasons for adding items to orders; for example, mis-shipments, exchanges, or to replace an item or SKU that is backordered.
You specify the period you want to include in the report; also, you can include a specific add reason code or all codes.
Note:
You can also define this report as a periodic function to include in your periodic processing. To do so, you should first use replace to create the function, using the program name CSR0646. You then use replace to add the function to your daily process.When the report runs as part of your daily process, it includes all add reason codes for that day.
How to display this screen: Select Print Order Addition Audit Report from a menu or enter PAAR in the Fast path field at the top of any menu.
Field | Description |
---|---|
Add reason |
The reason for adding an item to an order in order entry or order maintenance. Add reasons are defined in and validated against the Add Reason table; see Establishing Add Reason Codes (WADR). Numeric, 5 positions; optional. |
To |
The last date of the period you want to include in the report Numeric, 6 positions; required |
From |
The first date of the period you want to include in the report. Numeric, 6 positions (in user date format); required. |
Instructions:
- Enter an add reason code if you want to print a report for this reason alone.
- Enter beginning and ending dates for the report in the From and To fields.
- Select OK. The system validates your entries and highlights any fields you need to correct. Correct the entries again.
- The system submits the job PRT_OAAR, which produces the Order Addition Audit Report, and returns you to the previous screen.
Printing the Sales Tax Report by State (PSTX)
Purpose: Use the State Tax Report to review tax, GST, and PST totals by state for all debit invoices and credit invoices within a given date range.
Determining the shipping address:
- If there is a shipping address recorded in the Invoice Address table, the system uses this address to calculate the tax for the invoice. The system saves the shipping address in this table if the replace system control value is selected.
- If there is no shipping address in the Invoice Address table,
the system determines the shipping address as follows:
-
If there is an order-level (temporary) shipping address, use this address.
-
If the order shipped to a Customer Sold To or to a permanent Customer Ship To, use the address that was in effect at the time of the shipment, based on any address changes recorded in the Customer Address Change table. See Reviewing Customer Address Changes for more information on address change history. If there is no record of an address change since the date of the shipment, the current address provides the information for tax calculation.
-
How to display this screen: Enter PSTX in the Fast path field at the top of a menu or select Print Sales Tax Report by State from a menu.
Field | Description |
---|---|
Starting date |
The first date to include on the report. Invoices and credits processed on this date or later will be included. The starting date cannot be later than the ending date. Numeric, 6 positions (in user date format); required. |
Ending date |
The last date to include on the report. Invoices and credits processed on this date or earlier will be included. The ending date cannot be later than the current date. Numeric, 6 positions (in user date format); required. |
Printing the State Tax Detail Report (PSTD)
Purpose: Use the State Tax Detail Report to review invoices and credits by state for a given period, including details such as shipping and handling as well as state taxes and customer tax status.
Determining the shipping address:
- If there is a shipping address recorded in the Invoice Address table, the system uses this address to calculate the tax for the invoice. The system saves the shipping address in this table if the replace system control value is selected.
- If there is no shipping address in the Invoice Address table,
the system determines the shipping address as follows:
-
If there is an order-level (temporary) shipping address, use this address.
-
If the order shipped to a Customer Sold To or to a permanent Customer Ship To, use the address that was in effect at the time of the shipment, based on any address changes recorded in the Customer Address Change table. See Reviewing Customer Address Changes for more information on address change history. If there is no record of an address change since the date of the shipment, the current address provides the information for tax calculation.
-
How to display this screen: Enter PSTD in the Fast path field at the top of any menu or select Print State Tax Detail Report from a menu.
Field | Description |
---|---|
Country |
The country for which you want to run the report. Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required. |
State |
The state or province for which you want to run the report. The report will include invoices for customers whose shipping address matches the state you enter. The state you enter must be valid for the country you selected, above. Alphanumeric, 2 positions; required. |
Currency |
The currency associated with the source code specified on the order header. Currency codes are defined in and validated against the Currency table; see Working with Currency (WCUR). The default local currency specified in the System Control table appears here. The description of the currency appears to the right. This field appears only if the replace system control value is selected. Alphanumeric, 3 positions; required |
Starting date |
The first date to include on the report. Invoices and credits processed on this date or later will be included. The starting date cannot be later than the ending date. Numeric, 6 positions (in user date format); required. |
Ending date |
The last date to include on the report. Invoices and credits processed on this date or earlier will be included. The ending date cannot be later than the current date. Numeric, 6 positions (in user date format); required. |
Printing the Order Demand/Sales Reports (PSSR)
Purpose: Use these reports to review order and demand information such as order number, merchandise total and gross margin for orders within a given date range. Available reports are:
- Salesman Demand Report by Date: open, held and shipped orders within the given date range and is sorted by salesman number.
- Salesman Shipped Report by Date: shipped and partially shipped orders within the given date range and is sorted by salesman number.
- Source Demand Report by Date: open, held and shipped orders within the given date range and is sorted by source code.
- Source Shipped Report by Date: shipped and partially shipped orders within the given date range and is sorted by source code.
Quotes: The system includes quotes in these reports. Q displays in the Order Status field for orders flagged as quotes. The Quantity Returned, Quantity Reserved, and Quantity Shipped totals are always 0 for quotes. See replace for more information.
How to display this screen: Enter PSSR in the Fast path field at the top of any menu or select Print Demand/Shipped Report from a menu.
Field | Description |
---|---|
Date from |
The starting date from which you want to run this report. Orders entered on or after this date display on the report. You must enter a valid date that is not later than the ending date. Numeric, 6 positions (in user date format); required. |
Date to |
The ending date from which you want to run this report. Orders entered on or before this date display on the report. You must enter a valid date that is not earlier than the start date. Numeric, 6 positions (in user date format); required |
Report option |
The type of Order Demand/Sales report you wish to generate. Valid values are:
Required |
Item Purchase and Sales Aging Report (LIPS)
Purpose: Use the Item Purchase and Sales Aging Report to review purchase and sales history, such as open purchase order quantity and on hand quantity for items in a selected warehouse. This report places sales and receipt quantities into weekly aging buckets.
How to display this screen: Enter LIPS in the Fast path field at the top of any menu or select Item Purchase and Sales Aging Report from a menu.
Field | Description |
---|---|
Selected warehouse |
The warehouse containing the items whose purchase and sales history you wish to review. Warehouse 1 defaults in this field. If you leave this field blank, the system displays purchase and sales information for items located in warehouse 0. Numeric, 3 positions; optional. |
Select vendor |
The vendor whose purchase and sales history you wish to review. Leave this field blank if you wish to review purchase and sales information for all vendors. Numeric, 7 positions; optional. |
On hand only |
Identifies whether you want to review purchase and sales information for items containing an on hand quantity only. Valid values are:
|
Print Order Control Report (POCT)
Purpose: Use the Operations Control Report to review the flow of order activity and merchandising activity for a period of time. This report provides a high-level overview of the fulfillment process, identifies potential bottlenecks or problem areas, and delivers an audit trail of order activity.
The system uses the Order Control Summary table to track the total figures used to build this report; see Reviewing Operations Control Summary (FLSH).
Periodic function to update backorder totals: You must include the PFR0062 periodic function as part of your periodic processing to have correct and up-to-date ending order balance totals on the report. This periodic function must be run at the end of the day, when the background jobs have ended. In addition to performing this update to the table, the periodic function also submits the ORDSUM job, which generates the Order Control Report using the current date.
Order Control Report Screen
How to display this screen: Enter POCT in the Fast path field at the top of any menu, or select Print Order Control Report from a menu.
Field | Description |
---|---|
Start date |
The first date to include on the report. Numeric, 6 positions (in user date format); required. |
End date |
The last date to include on the report. Numeric, 6 positions (in user date format); required. |
Note:
Both dates must be earlier than the current date. The information on the report would be incomplete if you did not run the periodic process to update backorder totals. See above.Completing this screen: Complete the start and end date fields and select Submit. The system submits the job ORD_CONTRL, which generates the Operations Control Report.
Printing the Held Order Report (PHOR)
Purpose: Use this option to print the Held Order by Reason Code Report, which lists held orders in your company. You can restrict the report to a particular hold reason code, pay type, or ship via priority.
Quotes: This report does not include held quotes.
Option in Modern View: You can also generate this report by selecting Print Held Orders at the Manage Held Orders page in Modern View.
Print Held Orders Report Screen
How to display this screen: Enter PHOR in the Fast path field at the top of any menu, or select Print Held Orders Report from a menu.
Field | Description |
---|---|
Reason code |
Optionally, enter the code identifying the reason why an order is on hold, or leave this field blank to include held orders regardless of reason. Hold reason codes are defined in and validated against the Order Hold Reason Code table; see Establishing Order Hold Reason Codes (WOHR). Note: The Awaiting Credit Card Auth (CW) hold reason is not included on the report.Alphanumeric, 2 positions; optional. |
Pay type |
Optionally, enter the code identifying the payment type used on the order, or leave this field blank to include held orders regardless of payment type. Pay types codes are defined in and validated against the Pay Type table; see Working with Pay Types (WPAY). Numeric, 2 positions; optional. |
Ship via priority |
Optionally, enter the code identifying the Priority (Ship via priority) assigned to the ship via on the order, or leave this field blank to include held orders regardless of ship via priority. Numeric, 1 position; optional. |
Completing this screen: Select Submit after completing any of the optional fields to submit the HELD_ORDS and HO_RPT jobs, which generate the Held Order by Reason Code Report.
Printing the Daily Business Status Report (DBST)
Purpose: Use this report to review a high-level summary of sales, cash, inventory, order activity, and shipments.
Daily Business Status Screen
To print: Enter a processing date in the Enter processing date field and select Submit to generate the Daily Business Status Report. The current date defaults in the Enter processing date field, but you can override it to a prior date.
Periodic function: You can also run the Daily Business Status Report periodic function (program name ACR0178) to generate this report; in this case, the report date is the current date.
How to display this screen: Enter DBST in the Fast path field at the top of a menu or select Daily Business Status Report from a menu to advance to the Daily Business Status screen.
Printing the Order Reconciliation Report (PORS)
Purpose: Use this menu option to print the Order Reconciliation Report, which summarizes the total number of orders, units, and merchandise dollars by status in your company.
Order Reconciliation Report Screen
How to display this screen: Enter PORS in the Fast path field at the top of any menu, or select Order Reconciliation Report from a menu.
Field | Description |
---|---|
Start date |
The first date to include on the report. Numeric, 6 positions (in user date format); required. |
End date |
The last date to include on the report. Numeric, 6 positions (in user date format); required. |
Completing this screen: Select Submit after completing the date fields to submit the ORD_SUMMRY job, which generates the Order Reconciliation Report.
Printing the Sales Journal by Currency Report (PSJC)
Purpose: Use this menu option to print the Sales Journal by Currency Report based on a selected invoice date range and optionally currency code. This report provides a detailed audit trail of all sales transactions for a specified invoice date range, including all shipments, returns, credits, and no charge sales transactions, grouped by currency, invoice date, pay plan type, and pay type. The system registers a sales transaction when a shipment occurs.
This report provides:
- a detailed listing of sales activity for a specified invoice date range and currency.
- totals for each currency, pay type, pay plan type, and invoice date in the local currency and the alternate (foreign) currency.
- a grand total across all pay types and currencies in the local currency.
Understanding this report: This report provides information about the individual charges on each invoice, grouped by currency, invoice date, payment plan, and pay type.
The individual order charges in the Merchandise, Freight, Additional freight, Tax, Handling, and Additional charge columns on the left side of the report are totaled in the Total invoice field on the right side of the report.
This report provides totals for the number of credits (refunds) and invoices (shipments) for each currency, invoice date, payment plan type, pay type combination. A page break occurs between each currency, invoice date, payment plan type, pay type combination. A grand total displays at the end of the report.
Print Sales Journal by Currency Screen
Use this screen to select the invoice date range and currency code(s) to print on the Sales Journal by Currency report. If you do not select a currency code, the system prints the report for all currencies based on the invoice date range you define.
How to display this screen: Enter PSJC in the Fast path field at the top of a menu or select Print Sales Journal by Currency from a menu.
Field | Description |
---|---|
Invoice date range |
The date range for which you wish to run this report. The invoice date range represents the dates on which shipments occurred. Both fields default to the current date. Numeric, 6 positions (in user date format); required. |
Currency code |
The currency associated with the invoices you wish to print on the report. Only invoices and invoice credits associated with the currency you select, print on the report. Leave this field blank if you wish to print the report for all currencies, based on the invoice date range you define. The currency associated with the invoice is defined in the Order Header Extended table. The conversion rate is also stored in this table. If the currency code and conversion rate in the Order Header Extended table are blank, the invoice is for the local currency. Currency codes are defined in and validated against the Currency table. Alphanumeric, 3 positions; optional. |
Enter or verify the date range for which you wish to print the Sales Journal by Currency Report. The current date defaults. Select Submit to generate the report. A message indicates that the job has been submitted.
Printing the Held Orders by Pay Type Report (PHOP)
Purpose: Use the Held Order by Pay Type Report to obtain a list of the orders that are on hold for the specified payment type.
Print Held Orders by Pay Type Prompt Screen
How to display this screen: Enter PHOP in the Fast Path field at the top of any menu or select the Print Held Orders by Pay Type option from a menu.
Field | Description |
---|---|
Pay type |
A code that represents the method by which the customer paid for the order. Pay type codes are defined in and validated against the Pay Types table. Enter the appropriate pay type code to submit the Held Order by Pay Type Report. The system checks the status of each open order that uses this pay type and includes only those orders in a DH (dollar hold) status in this report. Numeric, 2 positions; required. |
Printing the Exchange Reason Report (PERR)
Purpose: Use this screen to generate the Exchange Reason Report, which you can use to review exchanges processed using various reason codes for a range of dates, including total units exchanged and dollar value. Your options in generating the report include:
- restricting the report to one exchange reason code, or including all codes
- listing the items that were exchanged
The report lists the total dollars exchanged based on the actual selling prices of the items returned for exchange. It does not indicate the prices of the replacement items.
Report based on order line history: When you generate the report, you need to specify a date range for selection. The report includes exchanges processed within the date range you enter, regardless of when the order was first created or when you ship the replacement item. The exchange date is determined by the Order Line History record for the exchange. You can review order line history at the Display Order Line History Screen.
Note:
If you use Working with Return Authorizations (WRTA), it is possible to create, receive, and credit an exchange on different dates. In this case, the date range is based on the date you receive the return, because that is when the Order Line History record is created.Print Exchange Reason Report Screen
How to display this screen: You can display this screen by entering PERR in the Fast path field at the top of a menu, or by selecting Print Exchange Reason Report from a menu.
Field | Description |
---|---|
Start date |
Enter the first order date to include on the report. Must be on or before the End date, below. The report includes exchanges processed on that date or later, regardless of when the order was originally created. Based on the Date from the Order Line History table; see the Display Order Line History Screen for more information. Note: If you use Working with Return Authorizations (WRTA), this is the date you receive the exchange, which might differ from the date you create or credit the return authorization for the exchange, or ship the replacement item.Numeric, in user date format; required. |
End date |
Enter the last order date to include on the report. Must be on or after the Start date. See the discussion of the Start date, above, for more information. Numeric, in user date format; required. |
Exchange reason |
Optionally, enter an exchange reason code to limit the report to that code. If you leave this field blank, all exchange reason codes are eligible for inclusion on the report. Exchange reason codes are defined in and validated against the Exchange Reason table; see Establishing Exchange Reason Codes (WEXR) for more information. Alphanumeric, 1 position; optional. |
Include item |
Optionally, select this flag to have the report list the items exchanged.
|
Completing this screen: To generate the Exchange Reason Report:
- Complete the Start date and End date to specify the range of dates to include on the report.
- Optionally, select an Exchange reason or the Include item flag.
- Select Print Report to submit the EXCH_RSN job, which generates the report.
Note:
If there are no order lines that meet the selection criteria you enter, the job does not produce a report. No empty report is generated.See the field descriptions above for more information.
Printing the Price Override Reason Report (PROR)
Purpose: Use this screen to generate the Price Override Reason Report, which you can use to review the price override reason codes used to discount items for a range of dates, and the total discount amounts and percentages applied. Your options in generating the report include:
- restricting the report to one price override reason code, or including all codes whose Exclude from price override report field is unselected
- listing the ID’s of the users who applied the price overrides, listing the items whose prices were overridden, or listing both user ID’s and items
Report based on order date, not price override date: When you generate the report, you need to select a date range for selection. The report includes orders that originated within the date range you enter, although the price override might not have been applied within that date range (for example, if you changed, added, or returned an order line at a later date).
Excluding price override reason codes: The system excludes any price override reason codes whose Exclude from price override report field is selected; for example, you may wish to exclude system-assigned price override reason codes, such as Default Price Override Reason (B35), from the report; see Default Price Override Reasons for a list of system-assigned codes specified in system control values. You can also limit the report to a single code by completing the Price override reason field at the Print Price Override Reason Report Screen.
Discount amount and percentage based on item offer: The discount amounts and percentages listed on the report are determined by comparing the Item offer price from the Order Detail table with the actual price after applying the price override. If the Override item offer price flag for a price override reason code is selected, the system changes the Item offer price in the Order Detail table to be the same as the actual selling price; as a result, the discount amount and percentage in this case are both zero.
The report does not list any discounts that were not applied using a price override reason code.
In this topic:
Identifying the User who Applied the Price Override
To identify the user who applied the price override, the system checks:
1. Order Line History? If there is no Order Line History record for the order line, this indicates that the price override was applied at initial order creation, so use the User ID on the Order Header. Otherwise, if there are any Order Line History records:
2. D (Discount) Order Line History? If there is an Order Line History record indicating that a discount was applied after shipment, use the User ID for that record; otherwise,
3. W (Price override) Order Transaction History message? If there is one or more Order Transaction History messages indicating a price override for the order line (for example, User price override - Order line 2), use the User ID associated with the first Order Transaction History message.
Example: User EJOHNSON changes the price of an order line using price override reason code Z. Later that day, user HBROWN changes the price again, using price override reason W. The report lists the current reason code of W and the first user ID of EJOHNSON.
Note:
- The system writes a price override Order Transaction History message whenever a user makes any change to an order in order maintenance if there is already a price override reason applied to an order line.
- The line number specified in the Order Transaction History message indicates the order line sequence number, and this is the number used to identify the order line for the price override. This sequence number is typically the same as the order line number, but might differ depending on updates made to the order.
Otherwise, if there is no Order Transaction History message for a price override,
4. A (Add) Order Line History but no subsequent changes? If there is an Order Line History record indicating that the order line was added after initial order creation, use that User ID; otherwise,
5. G (Change) Order Line History? If there are any Change Order Line History records indicating that the order line was changed after creation, use that User ID.
Print Price Override Reason Report Screen
How to display this screen: Enter PROR in the Fast path field at the top of any menu, or select Print Price Override Reason Report from a menu.
Field | Description |
---|---|
Start date |
Enter the first order date to include on the report. Must be on or before the End date, below. The report includes orders that were originally created on that date or later, regardless of when the price override was applied. Based on the Order date from the Order Header. Numeric, in user date format; required. |
End date |
Enter the last order date to include on the report. The report includes orders that were originally created on that date or earlier, regardless of when the price override was applied. Based on the Order date from the Order Header. Numeric, in user date format; required. |
Price override reason |
Optionally, enter a price override reason code to limit the report to that code. An error message displays if you enter a price override reason code whose Exclude from price override report field is selected: Reason is currently flagged to be excluded from reports - select another. If you leave this field blank, all price override reason codes whose Exclude from price override report field is unselected are eligible for inclusion on the report. Price override reason codes are defined in and validated against the Price Override Reason table; see Establishing Price Override Reason Codes (WPOR) for more information. Alphanumeric, 1 position; optional. |
Include users |
Optionally, select this flag to have the report list the users who applied price overrides.
|
Include items |
Optionally, select this flag to have the report list the item that received the price override.
|
Completing this screen: To generate the Price Override Reason Report:
- Complete the Start date and End date to specify the range of original order dates to include on the report.
- Optionally, select a Price override reason, or the Include users or Include items flags.
- Select Print Report to submit the PRC_OVR job, which generates the report.
Note:
If there are no order lines that meet the selection criteria you enter, the job does not produce a report. No empty report is generated.See the field descriptions above for more information.
Printing the Return Reason Report (PRRR)
Purpose: Use this screen to generate the Return Reason Report, which you can use to review returns processed using various reason codes for a range of dates, including total units returned and dollar value. Your options in generating the report include:
- restricting the report to one return reason code, or including all codes
- listing the items that were returned
Report based on order line history: When you generate the report, you need to specify a date range for selection. The report includes returns processed within the date range you enter, regardless of when the order was first created. The return date is determined by the Order Line History record for the return. You can review order line history at the Display Order Line History Screen.
Note:
If you use Working with Return Authorizations (WRTA), it is possible to create, receive, and credit a return on different dates. In this case, the date range is based on the date you receive the return, because that is when the Order Line History record is created.Print Return Reason Report Screen
How to display this screen: You can display this screen by entering PRRR in the Fast path field at the top of a menu, or by selecting Print Return Reason Report from a menu.
Field | Description |
---|---|
Start date |
Enter the first order date to include on the report. Must be on or before the End date, below. The report includes returns processed on that date or later, regardless of when the order was originally created. Based on the Date from the Order Line History table; see the Display Order Line History Screen for more information. Note: If you use Working with Return Authorizations (WRTA), this is the date you receive the return, which might differ from the date you create or credit the return authorization.Numeric, in user date format; required. |
End date |
Enter the last order date to include on the report. Must be on or after the Start date. See the discussion of the Start date, above, for more information. Numeric, in user date format; required. |
Return reason |
Optionally, enter a return reason code to limit the report to that code. If you leave this field blank, all return reason codes are eligible for inclusion on the report. Return reason codes are defined in and validated against the Return Reason table; see Establishing Return Reason Codes (WRTR) for more information. Alphanumeric, 1 position; optional. |
Include item |
Optionally, select this flag to have the report list the items that were returned.
|
Completing this screen: To generate the Return Reason Report:
- Complete the Start date and End date to specify the range of dates to include on the report.
- Optionally, select a Return reason or the Include item flag.
- Select Print Report to submit the RET_RSN job, which generates the report.
Note:
If there are no order lines that meet the selection criteria you enter, the job does not produce a report. No empty report is generated.See the field descriptions above for more information.
Displaying Open Orders by Item (DOOI)
Purpose: Use this on-line inquiry to identify orders that contain a specific item and to evaluate item statistics such as quantities ordered and reserved for that item.
You can also use this option to advance to standard Order Inquiry for a specific order, or to find out about pending purchase orders for a backordered item.
Quotes: This menu option also allows you to review item statistics on quotes; see Entering Pre-Order Quotes.
In this topic:
- Open Orders by Item Screen (Selecting an Item for Review)
- Display Open Orders by Item Screen
- Display Open Purchase Orders Screen
Open Orders by Item Screen (Selecting an Item for Review)
Use this screen to select the item you would like to research for open orders or purchase order information.
How to display this screen: Enter DOOI in the Fast path field or select this option from a menu.
Note:
You must enter complete and accurate information in both the Item and the SKU fields if applicable.Field | Description |
---|---|
Item |
Represents a unit of inventory. Alphanumeric, 12 positions; required. |
SKU (Stock keeping unit; an unlabeled field to the right of the item number) |
The style of the item, such as its color and size. Alphanumeric, three 4-position fields; required for any item with a SKU. |
Display Open Orders by Item Screen
Use this screen to evaluate open orders for a specific item by quantity, age, and reason for backorder. You can also advance from this screen to standard Order Inquiry for a specific order or display open purchase orders for the item. How to display this screen: Enter a complete item code and SKU, if any, at the Display Open Orders by Item Screen.
Field | Description |
---|---|
Description (Unlabeled field to the right of the SKU field) |
Text that describes the item. Alphanumeric, 120 positions; display-only |
Order # |
A unique number that the system assigns each order. Numeric, 7 positions; display-only. |
St # (Ship To Number) |
The number of the shipping address for the order. The system assigns a ship to suffix for each shipping address on an order. Numeric, 3 positions; display-only. |
Ln # (Line number) |
The item's order detail line number. Numeric, 3 positions; display-only. |
Days old |
The age of the order in days. Numeric, 5 positions; display-only |
Quantity |
Three status fields for the order detail line. These fields are: OrderedThe quantity of the item on the order line. Numeric, 7 positions; display-only. ReservedThe total reserved quantity of the item on the order line. Numeric, 7 positions; display-only. ShippedThe total quantity of the item on the order line that has shipped to date. Numeric, 7 positions; display-only. |
Rsn cde (Reason code) |
Represents the reason the item is on backorder. Valid values are:
The system will not “tie-up” inventory that can be matched to current orders if the order will not ship for a period of time. The system uses the following calculation to identify future orders: Arrival date - Reservation lead days = Date The system will not reserve inventory if the system-calculated date is greater than today's date. Normally, the Evaluate Future Orders program runs each evening during a periodic process to evaluate each order detail line identified as a “future” order. The system reruns the arrival date calculation and reserves inventory if the system-calculated date is less than or equal to today's date.
|
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 1 position; display-only. |
|
Description |
Text that explains the meaning of the backorder reason code. Alphanumeric, 25 positions; display-only |
Screen Option | Procedure |
---|---|
Display an order |
Select Display for an order to advance to Order Inquiry Header Screen or the Order Inquiry Detail Screen, depending on the setting of the Default Version for Order Inquiry (C34) system control value. |
Display open purchase orders for an item |
Select Display Open POs to advance to the Display Open Purchase Orders Screen. |
Display Open Purchase Orders Screen
Use this screen to obtain information about the unreceived or partially received purchase orders for an item. This screen includes the purchase order numbers, vendors, quantities and expected delivery dates for the item.
How to display this screen: Select Display Open POs at the Display Open Orders by Item Screen.
Field | Description |
---|---|
Whs (Warehouse) |
The warehouse to which the item will be delivered. Numeric, 3 positions; display-only. |
PO# |
The number of the purchase order on which the item was ordered from the vendor. Numeric, 7 positions; display-only |
Ln# (Line number) |
The line number of item on the purchase order. Numeric, 3 positions; display-only |
Vendor # |
A code to identify the supplier of the item. Vendor codes are defined in and validated against the Vendor table. See Working with Vendors (WVEN). Numeric, 7 positions; display-only. |
Name |
The name of the vendor associated with the vendor number. Alphanumeric, 30 positions; display-only. |
Qty due (Quantity due) |
The number of units of the item expected in the shipment. Numeric, 7 positions; display-only. |
Date |
The date when the shipment of the item is expected. Numeric, 6 positions (in user date format); display-only. |
Display Held Order Summary (DHOS)
Purpose: Use this function to review the total held number of orders and unbilled dollar totals for each order hold reason code.
Update summary table: The Held Order Summary table stores held order totals. You must submit a batch program to update this table with current totals. The totals that display on the Held Order Summary screen are only as current as the last time you ran this batch update.
Quotes: The # Orders and Dollars totals in this menu option does not include quotes that are on hold.
Modern View option: See the Modern View online help for information on the Held Order Summary page available in Modern View. Authority to the Held Order Summary page in Modern View is also controlled by the DHOS fast path.
Held Order Summary Screen
How to display this screen: Enter DHOS in the Fast path field at the top of any menu, or select Display Held Order Summary from a menu.
Note:
Each field on this screen is blank if you have not yet submitted the batch update to the Held Order Summary table.Field | Description |
---|---|
Date last updated |
The date and time when you most recently updated the Held Order Summary table. The totals provided for each hold reason code are current as of this date and time. Date: numeric, 6 positions (in user date format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. |
Hold reason |
The reason code that identifies why the order is held. Hold reason codes are defined in and validated against the Order Hold Reason table; see Establishing Order Hold Reason Codes (WOHR). Alphanumeric, 2 positions; optional. |
System hold |
Indicates whether the orders were held automatically by the system, or a user put the orders on hold. Valid values are:
If your operators use a code that the system also uses automatically, there will be two totals for the hold reason: one for all system-assigned holds, and one for non-system-assigned (that is, user) holds. See Introducing Order Hold Reason Codes. |
Description |
The description of the order hold reason code. This field is blank for an order hold reason code if the system has assigned it to orders automatically, but you have not built the reason code in the Order Hold Reason Code table. Alphanumeric, 50 positions; display-only. |
# orders |
The total number of orders on hold with this hold reason code. Each held order increases this total by one, regardless of the number of recipients. Numeric, 8 positions; display-only. |
Dollars |
The total value of orders on hold with this hold reason code. This total includes merchandise, freight, tax, handling, additional charges, and any other charges (such as additional freight and duty) that make up the order total). Note: If you process orders in multiple currencies (the Multi Currency by Offer (E03) system control value is selected), the order total will be converted into your local currency.Numeric, 20 positions with a 2-place decimal; display-only. |
Screen Option | Procedure |
---|---|
Review orders held for a particular hold reason code |
Select Disp Orders for a hold reason code to advance to the Release Held Orders by User Hold Screen (if you select a user hold) or the Release Held Orders by System Hold Screen (if you select a system hold). See Selecting Held Orders (ERHO). |
Submit the batch update to the Held Order Summary table |
Select Submit Update to submit the HLDORD_SUM job, which updates the table with current held order totals. |
Ship Via/Item Inquiry (SVII)
Purpose: The Ship Via/Item Inquiry menu option allows you to review how many shippable orders you currently have for a shipper, broken out by item. You might use this information to determine whether a bulk mailing may be appropriate for certain items.
Batch job: You must run a batch job to collect information on the current number of available order lines for each item/ship via combination in your company before you can review or print the information. You can run this batch job through the Ship Via/Item Inquiry menu option, or by adding the periodic function SUMVIA to your periodic processing, using the program name OER1024.
Summary tables: The batch job populates the Ship Via/Item Summary Header (OESVIH) and Ship Via/Item Summary Detail (OESVID) tables. For a brief period during this process, you will be locked out of the Ship Via/Item Inquiry menu option while the system updates the summary information. If someone is already using the inquiry menu option when the system is ready to complete the batch job and update the summary tables, the batch job will go into a “delay” status, checking every 15 seconds to see if the user has exited the inquiry screens so that the update can be processed.
Review summary information: Use the Ship Via/Item Inquiry menu option to review the total open orders, shippable units, and oldest arrival dates for each item with a particular ship via assigned. An additional screen, where you can review the number of orders and units for each arrival date, is also available.
Reporting: You can print a report listing all shippable items by ship via code, or the items assigned to a particular ship via code only.
Which order lines are included? Ship Via/Item Inquiry and the related reports include any order line quantity that is reserved and unprinted. Both open and held order lines are included. The system uses the ship via code on the order header, unless there is a ship via override for the order line.
In this topic:
- First Inquiry by Ship Via/Item Screen
- Second Inquiry by Ship Via/Item Screen
- Third Inquiry by Ship Via/Item Screen
First Inquiry by Ship Via/Item Screen
Purpose: Use this screen to:
- populate the Ship Via/Item Summary tables with up-to-date information
- advance to the Second Inquiry by Ship Via/Item Screen so you can review shippable items for a particular ship via
- generate the Ship Via/Item Header Report for all ship via codes in your company.
See Ship Via/Item Inquiry (SVII).
How to display this screen: Enter SVII in the Fast path field at the top of any menu or select Ship Via/Item Inquiry from a menu.
Field | Description |
---|---|
Ship via |
A code to identify a shipper who delivers merchandise for you to your customers. Enter a valid ship via code to advance to the Second Inquiry by Ship Via/Item Screen. Ship via codes are defined in and validated against the Ship Via table; see Working with Ship Via Codes (WVIA). Numeric, 2 positions; required to advance to the second Inquiry by Ship Via/Item screen. |
Last update (Last update information) |
The date and time when the Ship Via/Item Summary tables were last updated, and the user ID of the person who generated the batch update. If these fields are blank, the batch job to populate the summary tables has never been run in your company. Date: numeric, 6 positions (in user date format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. |
Summary table update: If the UPDSVITM batch job to update the summary tables is running, you will not be unable to advance to the Second Inquiry by Ship Via/Item Screen or print the Ship Via/Item Header Report during the time it takes to copy the updated information into the summary tables. Instead, an error message indicates:
The summary files are being updated and cannot be viewed or printed. When the file update is complete, you will be able to advance to the second screen or print a summary report.
Screen Option | Procedure |
---|---|
Update the Ship Via/Item Summary tables |
Select Update Summary File to generate the UPDSVITM batch job, which populates the Ship Via/Item Summary Header and Detail tables with up-to-date information. |
Print a list |
Select Print List (all ship via) to print the Ship Via/Item Header Report. |
Second Inquiry by Ship Via/Item Screen
Purpose: Use this screen to review the total number of shippable orders and units, and the oldest order arrival date, for all items assigned to a particular ship via.
How to display this screen: Complete the Ship via field at the First Inquiry by Ship Via/Item Screen.
Field | Description |
---|---|
Ship via |
The ship via code you entered at the First Inquiry by Ship Via/Item Screen. The ship via description appears to the right. Ship via: numeric, 2 positions; display-only. Ship via description: alphanumeric, 30 positions; display-only. |
Item |
A code representing the unit of inventory that you sell. The items that display are either on orders with the selected ship via assigned at the header level, or have a ship via override for this particular item on the order. Alphanumeric, 12 positions; optional. |
SKU |
The item's unique characteristics, such as color or size. The labels that appear above the SKU field(s) are defined in the Split SKU Values (B32) system control values. Alphanumeric, three 4-position fields; optional. |
Total orders |
The total number of orders containing reserved, unprinted units of this item or SKU that are assigned to the ship via code you selected at the First Inquiry by Ship Via/Item Screen. Numeric, 5 positions; optional. |
Total units |
The total number of reserved, unprinted units of this item or SKU that are assigned to the ship via code you selected at the First Inquiry by Ship Via/Item Screen. Numeric, 7 positions; optional. |
Oldest arrival (Oldest arrival date) |
The earliest arrival date for all shippable orders of the item or SKU. The arrival date is when the customer wants to receive this item. The current date defaults in order entry; however, you can override the default and enter a future date. The system performs a calculation that projects the total processing and shipping time to determine when it will need to reserve the items and make them available for pick slip preparation. See Working with Items on the Order. Numeric, 6 positions (in user date format); optional. |
Description (Unlabeled field below the item code field) |
The description of the item. Alphanumeric, 120 positions; optional. |
Screen Option | Procedures |
---|---|
Display order totals |
Select Display Totals for an item or SKU to advance to the Third Inquiry by Ship Via/Item Screen. |
Print a report |
Select Print List to print the Ship Via/Item Header Report. |
Third Inquiry by Ship Via/Item Screen
Purpose: Use this screen to review the total shippable orders and units for an item or SKU/ship via combination, broken out by arrival date.
How to display this screen: Select Display Totals for an item or SKU at the Second Inquiry by Ship Via/Item Screen.
Field | Description |
---|---|
Ship via |
The ship via code you entered at the first Inquiry by Ship Via/Item screen. The ship via description appears to the right. Ship via: numeric, 2 positions; display-only. Ship via description: alphanumeric, 30 positions; display-only. |
Item |
The item you selected at the Second Inquiry by Ship Via/Item Screen. Alphanumeric, 12 positions; display-only. |
SKU |
The item's unique characteristics, such as color or size. Alphanumeric, three 4-position fields; display-only. |
Item description |
The description of the item. Alphanumeric, 120 positions; display-only. |
Arrival date |
The date when the customer wants to receive this item. The current date defaults in order entry; however, you can override the default and enter a future date. The system performs a calculation that projects the total processing and shipping time to determine when it will need to reserve the items and make them available for pick slip preparation. See Working with Items on the Order. Numeric, 6 positions (in user date format); optional. |
Total orders |
The total number of orders with the arrival date indicated. An order may be counted more than once if there is an override arrival date for one or more of the same order lines for the selected item. Numeric, 5 positions; optional. |
Total units |
The total number of units with the arrival date indicated. Numeric, 7 positions; optional. |
Screen Option | Procedure |
---|---|
Print a report |
Select Print List to print the Ship Via/Item Detail Report. |
Printing Backorder Reports by Descending Dollars (PBOD)
Purpose: Use this screen to define the selection criteria you wish to use to print one of the Backorder Reports by Descending Dollars. These reports print the total number of orders with at least one order detail line on backorder, based on the selection criteria you defined. You can use these reports to determine the total value of backorders in each entity, division, offer, or warehouse.
Quotes: These reports do not include backorders on quotes; see Entering Pre-Order Quotes.
Backorder Reports by Descending Dollars:
- Backorder Report by Descending Dollars by Entity/Warehouse (sorts in entity/warehouse/item/descending dollar sequence and displays backordered order detail lines for each entity).
- Backorder Report by Descending Dollars by Division/Warehouse (sorts in division/warehouse/item/descending dollar sequence and displays backordered order detail lines for each division).
- Backorder Report by Descending Dollars by Offer/Warehouse (sorts in offer/warehouse/item/descending dollar sequence and displays backordered order detail lines for each offer).
- Backorder Report by Descending Dollars by Warehouse (sorts in warehouse/item/descending dollar sequence and displays backordered order detail lines for each warehouse).
Backorder Report by Descending Dollars Screen
How to display this screen: Enter PBOD in the Fast path field at the top of any menu or select Print B/O Reports by Descending Dollars from a menu.
Field | Description |
---|---|
Select offer for pricing |
The code for the offer you wish to use to determine the selling price of an item on this report. The last offer entered defaults. Offer codes are validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; required. |
By entity/whse |
Indicates if you wish to print the Backorder Report by Descending Dollars By Entity/Warehouse. Valid values are:
The last value entered defaults. |
Entity (unlabeled field to the right of the |
A code for the entity for which you wish to generate the Backorder Report by Descending Dollars By Entity/Warehouse. Enter an entity code in this field if you wish to only include backorder information associated with this entity. Leave this field blank if you wish to include backorder information for all entities. The last entity entered, if any, defaults. Entity codes are validated against the Entity table. Numeric, 3 positions; optional. |
By division/whse |
Indicates if you wish to print the Backorder Report by Descending Dollars by Division/Warehouse. Valid values are:
The last selected setting defaults. |
Division (unlabeled field to the right of the |
A code for the division for which you wish to generate the Backorder Report by Descending Dollars by Division/Warehouse. Enter a division code in this field if you wish to only include backorder information associated with this division. Leave this field blank if you wish to include backorder information for all divisions. The last division entered, if any, defaults. Division codes are validated against the Division table. Alphanumeric, 2 positions; optional. |
By offer/whse |
Indicates if you wish to print the Backorder Report by Descending Dollars by Offer/Warehouse. Valid values are:
The last value entered defaults. |
Offer (unlabeled field to the right of the |
A code for the offer for which you wish to generate the Backorder Report by Descending Dollars by Offer/Warehouse. Enter an offer code in this field if you wish to only include backorder information associated with this offer. Leave this field blank if you wish to include backorder information for all offers. The last offer entered, if any, defaults. Offer codes are validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; optional. |
By warehouse |
Indicates if you wish to print the Backorder Report by Descending Dollars by Warehouse. Valid values are:
The last value entered defaults. |
Warehouse (unlabeled field to the right of the |
A code for the warehouse for which you wish to generate the Backorder Report by Descending Dollars by Warehouse. Enter a warehouse code in this field if you wish to only include backorder information associated with this warehouse. Leave this field blank if you wish to include backorder information for all warehouses. The last warehouse entered, if any, defaults. Warehouse codes are validated against the Warehouse table. See Creating and Maintaining Warehouses (WWHS). Alphanumeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Generate the Backorder Report by Descending Dollars, based on the selection criteria you defined. |
Select Accept. |
Reviewing Operations Control Summary (FLSH)
Purpose: Use the Operations Control Summary screens to review order and merchandising summary information for a selected date; you can review the flow of orders from entry through shipment to determine the health of your business. This menu option provides a high-level overview of the fulfillment process, identifies potential bottlenecks or problem areas, and delivers an audit trail of order activity.
Quotes: This menu option does not include information on quotes; see Entering Pre-Order Quotes.
Modern View page: The Operations Summary page in Modern View displays much of the same totals as the First Operations Control Summary Screen, as well as average values for each type of activity and bar charts illustrating the percentages of units, orders, and merchandise value represented for each activity.
This Modern View page is also controlled by access to the FLSH menu option, and is available from the Modern View Home page.
See the Modern View online help for more information.
In this topic:
- Defining Thresholds
- Updating Operations and Merchandising Summary Totals
- Display Operations Control Summary Screen
- First Operations Control Summary Screen
- Second Operations Control Summary Screen
You can review the number, units, and amount totals for the following information:
- orders:
-
entered
-
cancelled
-
soldout
-
shipped
-
returned
-
exchanged
-
held
-
suspended; also the number of suspended batches
-
open backordered
-
held backordered
-
open printed
-
held printed
-
open reserved
-
held reserved
-
- pending pick slips
- pending RA:
-
receipts
-
credits
-
- pending refunds
- backordered items
- purchase orders:
-
open
-
held
-
docked
-
open past due
-
held past due
-
docked past due
-
- inventory in:
-
suspense receipt
-
pending putaway
-
staging warehouse
-
Screen flow: The screen that opens when you first enter the Operations Control Summary menu option varies, depending on whether the Batch Order Control job was submitted for the day. See Updating Operations and Merchandising Summary Totals for more information on the Batch Order Control job.
- If the Batch Order Control job has not yet been submitted for the day, the Display Operations Control Summary Screen opens when you first enter the Operations Control Summary menu option.
- If the Batch Order Control job has already been submitted for the day, the First Operations Control Summary Screen opens when you first enter the Operations Control Summary menu option.
Defining Thresholds
You can define thresholds to monitor the numbers and/or amounts of operational and merchandising summary totals. The system compares the actual number and/or amount for the threshold against the threshold number and/or amount you defined; if the threshold you have defined is breached, the system generates the Threshold Monitor Breach Email.
Example: One of the system delivered thresholds is Backorders (BO). This threshold monitors the number of open orders and held orders that contain at least one unit on backorder and/or the merchandise amounts of backordered units on open or held orders. You can set this threshold to send an email to the warehouse supervisor when the number of open and held orders that contain at least one unit on backorder is greater than 100. Once the actual number of open and held orders containing a backordered item is 101, the system sends an email to the warehouse supervisor.
For more information: See Working with Threshold Values (WTHR) for more information on system delivered thresholds and how to define your own thresholds.
Updating Operations and Merchandising Summary Totals
Updating order activity totals for the selected date and accounting period: The system updates the information on the top part of the First Operations Control Summary Screen (order activity by date and accounting period) as changes occur in order activity and are processed through the Order Async and Billing Async. You can select Refresh screen to update the order activity totals displayed on the screen with any changes that may have occurred since you first entered the screen.
The system interactively updates the number, units, and amounts totals of the following order activity information:
orders:
- entered
- cancelled
- soldout
- shipped
- returned
- exchanged
Totals display for the selected date and accounting period.
- Drop ship items update the order activity totals as well as items that you ship from your warehouse.
- Non-inventory items: The setting of the Demand Update for Non-Inventoried Items (E59)system control value does not affect how the system calculates the order activity totals; non-inventory items update each total regardless of this setting.
- Update demand for order maintenance: The setting of the Update Demand for Order Maintenance Transactions (C72) system control value does not affect how the system calculates the order activity totals.
- Excluded from totals: Retail pickup and delivery orders that fulfill orders originating in Order Management System and submitted to Order Broker for assignment are excluded from these totals. These are orders whose Alt ord indicates an originating order number, and whose Broker delivery type is Delivery or Retail Pickup.
- Currency: Totals are displayed in the Local Currency Code (A55).
Updating operations control summary totals: The Batch Order Control job (ORD_CONTRL) updates the operations and merchandising summary totals. You can review operations totals on the bottom part of the First Operations Control Summary Screen and the Second Operations Control Summary Screen.
The Batch Order Control job updates the number, units, and amounts totals of the following operations and merchandising information:
- orders:
-
open
-
held
-
suspended (also the number of suspended batches)
-
open backordered
-
held backordered
-
open printed
-
held printed
-
open reserved
-
held reserved
-
- pending pick slips
- pending RA:
-
receipts
-
credits
-
- pending refunds
- backordered items
- purchase orders:
-
open
-
held
-
docked
-
open past due
-
held past due
-
docked past due
-
- inventory in:
-
suspense receipt
-
pending putaway
-
staging warehouse
-
Submitting the Batch Order Control job: The system submits the Batch Order Control job when:
- you select Update current totals on the First Operations Control Summary Screen, Second Operations Control Summary Screen, or Display Operations Control Summary Screen in the Operations Control Summary (FLSH) menu option.
- you submit a periodic process that:
-
includes the Order Summary (ORDSUM) periodic function (program name PFR0062), OR
-
includes the Threshold (THRESHD) periodic function (program name PFTHRESHMO).
-
Note:
You can schedule a periodic process to run at a specified time; see Executing Periodic Processes (EPRO) for more information on defining a job schedule for a periodic process.Batch Order Control processing: The Batch Order Control job:
- updates all of the fields in the Order Control Summary table for the current transaction date.
- generates the Operations Control Report, which displays the most recent operations and merchandising summary totals; the system generates the report only if you submit the Batch Order Control job from the Operations Control Summary menu option.
- updates the actual value fields and Last updated fields in the Threshold Values table; see Updating Threshold Actual Values for more information on the updates the batch order control job performs for threshold values.
Note:
The system does not update or use the Flash Report table to capture operations and merchandising summary information; instead, the system updates and uses the Order Control Summary table.Display Operations Control Summary Screen
Updates to this screen: This screen displays operations control summary information for the dates when:
- you have executed order, cancellation, sold out, shipping, return or exchange transactions, or
- you have run the Batch Order Control job; see Updating Operations and Merchandising Summary Totals.
Order Control Report: When you update current totals by selecting Update current totals, or execute the periodic function ORDSUM (program name PFR0062), the system prints the Operations Control Report for the current (today’s) date.
How to display this screen:
- select Display All Days at the First Operations Control Summary Screen, or
- If you have not yet run the Batch Order Control job or processed information through the Order Async or Billing Async for the current day:
- enter FLSH in the Fast path field or select this option from a menu.
- Select Dsp Flash Rpt at the Streamlined Pick Slip Generation Screen.
Field | Description |
---|---|
Date |
The date when the displayed order activity took place. Numeric, 6 positions, in user date format; display-only. |
The totals listed on the Display Operations Control Summary screen are accurate as of the time you refreshed the screen for the current date. | |
Ordered |
The number of orders and merchandise amounts for orders entered for the selected date and accounting period. Note: The order totals include order lines added to an existing order through order maintenance, regardless of the setting of the Update Demand for Order Maintenance Transactions (C72) system control value.The number of orders entered, including:
This does not include batch orders that have not yet been accepted. This is the Orders entered number in the Order Control Summary table. The system adds the Orders entered number value for each transaction date in the accounting period to determine the number of orders entered for the accounting period. |
Amount The merchandise amount total of orders entered, including merchandise amount total of sold out items or non-inventory items. This does not include:
This is the Orders entered dollars in the Order Control Summary table. The system totals the Orders entered dollars value for each transaction date in the accounting period to determine the merchandise amount total of orders entered for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Cancelled |
The number of orders and merchandise amounts for orders cancelled for the selected date and accounting period. Note: These totals include orders, items, or merchandise amount only if the Reduce demand? flag for the cancel reason is unselected.The number of orders cancelled (orders in Cancelled status; all order lines have been cancelled). This is the Orders cancelled number in the Order Control Summary table. The system totals the Orders cancelled number value for each transaction date in the accounting period to determine the total number of orders cancelled for the accounting period. AmountThe merchandise amount total of cancelled items. This total updates when you cancel an entire order or one or more lines on an order. This is the Orders cancelled dollars in the Order Control Summary table. The system totals the Orders cancelled dollars value for each transaction date in the accounting period to determine the merchandise amount total of cancelled items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
Soldout |
The number of orders and merchandise amounts for orders soldout for the selected date and accounting period. The system considers an order line sold out if:
The total number of soldout orders, including orders for which all order lines are sold out, or at least one order line is sold out and all other order lines have been cancelled using any cancel reason code. This does not include order lines that are sold out if other order lines exist on the order that are not sold out or cancelled.
|
Amount The merchandise amount total of soldout items. This is the Orders soldout dollars in the Order Control Summary table. The system totals the Orders soldout dollars value for each transaction date in the accounting period to determine the merchandise amount total of soldout items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Shipped |
The number of orders and merchandise amounts for orders shipped for the selected date and accounting period. These totals are not decreased by returns or exchanges. OrdersThe total number of shipped orders. This is the Orders shipped number in the Order Control Summary table. The setting of the Order Control Summary Shipment Update Method (I55) system control value determines how the system updates the shipped totals in the Order Control Summary table. The system totals the # Orders shipped value for each transaction date in the accounting period to determine the total number of shipped orders for the accounting period. |
Amount The merchandise amount total of shipped items. This is the Orders shipped dollars in the Order Control Summary table. The system adds the Orders shipped dollars value for each transaction date in the accounting period to determine the merchandise amount total of shipped items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Returned |
The number of orders and merchandise amounts for orders returned for the selected date and accounting period. You can enter a return in:
These totals include simple returns only, as opposed to exchanges. See Returning and Exchanging Items in Order Maintenance. OrdersThe total number of return transactions processed and credited, regardless of whether the returns are on the same order. For example, an order with 2 returned order lines processed separately updates this total by 2; however, if the same 2 returned order lines on a single order are processed in the same transaction, the total updates by 1. This is the Invoices credited number in the Order Control Summary table. The system totals the Invoices credited number value for each transaction date in the accounting period to determine the total number of return transactions processed and credited for the accounting period. |
Amount The merchandise amount total of returned items. This is the Invoices credited dollars in the Order Control Summary table. The system totals the Invoices credited dollars value for each transaction date in the accounting period to determine the merchandise amount total of returned items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
Screen Option | Procedure |
---|---|
Display operations control summary information for a selected date. |
Select Display for a date to advance to the First Operations Control Summary Screen, which displays information for the selected date. |
Update totals for order recap information on the Operations Control Summary screen and print the Order Control Report for the current date. |
Select Update current totals to submit the ORD_CONTRL job, which updates the information in the lower part of the First Operations Control Summary Screen. After the batch job is completed, you must exit the screen and re-display it to view the changes. This batch job also prints the Operations Control Report for the current date. |
First Operations Control Summary Screen
Purpose: Use this screen to review:
- order activity information for the selected date and accounting period, such as the number, quantity, and amount totals of orders entered, cancelled, soldout, shipped, returned, and exchanged. The top half of the screen displays order activity information.
- order summary information as of the selected date, such as the number, quantity, and amount totals of orders open, held, suspended, open backordered, held backordered, open printed, held printed, open reserved, and held reserved. Operations summary information is on the lower half of the screen.
Updating totals: See Updating Operations and Merchandising Summary Totals for more information on how the system updates the totals on this screen.
Note:
If you advance to this screen for a date when you did not update the totals, the bottom half of the screen does not display any information.Additional operations summary information: Select OK to advance to the Second Operations Control Summary Screen.
How to display this screen:
- Select a date at the Display Operations Control Summary Screen to display information for a selected date, or
- If the batch order control job has already run for today’s date, or the Order Async is active and you have processed order information for the current day:
- enter FLSH in the Fast path field or select Display Operations Control Summary from a menu.
- select Dsp Flash Rpt at the Streamlined Pick Slip Generation Screen.
Field | Description |
---|---|
Information for selected date and accounting period: | |
Date(Unlabeled field at top left of screen) |
The current date, or the date you have selected at the Display Operations Control Summary Screen. The order activity information displayed below this date reflects total ongoing activity for the date. Numeric, 6 positions, in user date format; display-only. |
Accounting period and year(Unlabeled field at top right of screen) |
The accounting period which includes the date displayed in the Date field. The order activity information displayed below the month and year reflects total activity for the accounting period up to the selected date. Alphanumeric, 7 positions; display-only. |
Ord (Orders) |
The number of orders, number of units, and merchandise amounts for orders entered for the selected date and accounting period as of the time you refreshed the screen. Note: The order totals reflect initial order entry only. These totals do not include order lines added to an existing order through order maintenance, regardless of the setting of the Update Demand for Order Maintenance Transactions (C72) system control value.The number of orders entered, including:
This total does not include:
This is the Orders entered number in the Order Control Summary table. The system adds the Orders entered number value for each transaction date in the accounting period to determine the number of orders entered for the accounting period. |
Units The number of units ordered, including:
This total does not include:
This is the Quantity ordered in the Order Control Summary table. The system totals the Quantity ordered value for each transaction date in the accounting period to determine the number of units ordered for the accounting period. |
|
Amount The merchandise amount total of orders entered, including merchandise amount total of sold out items or non-inventory items. This total does not include:
This is the Orders entered dollars in the Order Control Summary table. The system totals the Orders entered dollars value for each transaction date in the accounting period to determine the merchandise amount total of orders entered for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
The following fields display totals for transactions processed on the selected date, or in the selected accounting period, regardless of whether the original order was processed on the selected date or in the selected accounting period. | |
Can (Cancelled) |
The number of orders, number of units, and merchandise amounts for orders cancelled for the selected date and accounting period as of the time you refreshed the screen. Note: These totals include orders, items, or merchandise amount only if the Reduce demand? flag for the cancel reason is unselected.The number of orders cancelled (orders in Cancelled status; all order lines have been cancelled). This is the Orders cancelled number in the Order Control Summary table. The system adds the Orders cancelled number value for each transaction date in the accounting period to determine the total number of orders cancelled for the accounting period. UnitsThe total number of units cancelled. This total updates when you cancel an entire order or one or more lines on an order. This is the Quantity cancelled in the Order Control Summary table. The system adds the Quantity cancelled value for each transaction date in the accounting period to determine the total number of units cancelled for the accounting period. |
Amount The merchandise amount total of cancelled items. This total updates when you cancel an entire order or one or more lines on an order. This is the Orders cancelled dollars in the Order Control Summary table. The system adds the Orders cancelled dollars value for each transaction date in the accounting period to determine the merchandise amount total of cancelled items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
S/O (Sold out) |
The number of orders, number of units, and merchandise amounts for orders soldout for the selected date and accounting period as of the time you refreshed the screen. The system considers an order line sold out if you:
The total number of soldout orders, including orders for which all order lines are sold out, or at least one order line is sold out and all other order lines have been cancelled using any cancel reason code. This does not include order lines that are sold out if other order lines exist on the order that are not sold out or cancelled. This is the Orders soldout/closed number in the Order Control Summary table. The system adds the Orders soldout/closed number value for each transaction date in the accounting period to determine the total number of soldout orders for the accounting period. |
Units The total number of soldout units. This is the Quantity soldout in the Order Control Summary table. The system adds the Quantity soldout value for each transaction date in the accounting period to determine the total number of soldout units for the accounting period. AmountThe merchandise amount total of soldout items. This is the Orders soldout dollars adds in the Order Control Summary table. The system adds the Orders soldout dollars value for each transaction date in the accounting period to determine the merchandise amount total of soldout items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Shp (Shipped) |
The number of orders, number of units, and merchandise amounts for orders shipped for the selected date and accounting period as of the time you refreshed the screen. These totals are not decreased by returns or exchanges. OrdersThe total number of shipped orders. This is the # Orders shipped in the Order Control Summary table. The setting of the Order Control Summary Shipment Update Method (I55) system control value determines how the system updates the # Orders shipped field in the Order Control Summary table:
The system totals the # Orders shipped value for each transaction date in the accounting period to determine the total number of shipped orders for the accounting period. |
Units The total number of shipped units, including:
This total does not include:
This is the Quantity shipped in the Order Control Summary table. The system adds the Quantity shipped value for each transaction date in the accounting period to determine the total number of shipped units for the accounting period. |
|
Amount The merchandise amount total of shipped items, including:
This total does not include:
This is the Orders shipped dollars in the Order Control Summary table. The system totals the Orders shipped dollars value for each transaction date in the accounting period to determine the merchandise amount total of shipped items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Units The total number of returned units. This is the Quantity credited in the Order Control Summary table. The system totals the Quantity credited value for each transaction date in the accounting period to determine the total number of returned units for the accounting period. AmountThe merchandise amount total of returned items. This is the Invoices credited dollars in the Order Control Summary table. The system totals the Invoices credited dollars value for each transaction date in the accounting period to determine the merchandise amount total of returned items for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Rtn (Returns) |
The number of orders, number of units, and merchandise amounts for orders returned for the selected date and accounting period as of the time you refreshed the screen. You can enter a return in:
These totals include simple returns only, as opposed to exchanges. See Returning and Exchanging Items in Order Maintenance. OrdersThe total number of return transactions processed and credited, regardless of whether the returns are on the same order. For example, an order with 2 returned order lines processed separately updates this total by 2; however, if the same 2 returned order lines on a single order are processed in the same transaction, the total updates by 1. This is the Invoices credited number in the Order Control Summary table. The system totals the Invoices credited number value for each transaction date in the accounting period to determine the total number of return transactions processed and credited for the accounting period. |
Exc (Exchanges) |
The number of orders, number of units, and merchandise amounts for items returned in exchange transactions for the selected date and accounting period as of the time you refreshed the screen. These totals include quantities and merchandise amount of the items returned in exchange transactions, not units and merchandise amount of items ordered in exchange. See Returning and Exchanging Items in Order Maintenance. You can enter an exchange in:
The total number of exchange transactions processed, regardless of whether the exchanges are on the same order. For example, an order with 2 exchanged order lines processed separately updates this total by 2; however, if the same 2 exchanged order lines on a single order are processed in the same transaction, the total updates by 1. This is the Exchanges number in the Order Control Summary table. The system totals the Exchange number value for each transaction date in the accounting period to determine the total number of exchange transactions processed for the accounting period. |
Units The total number of units returned in exchange transactions. This is the Quantity exchanged in the Order Control Summary table. The system totals the Quantity exchanged value for each transaction date in the accounting period to determine the total number of units returned in exchange transactions for the accounting period. AmountThe merchandise amount total of returned items in exchange transactions. This is the Exchanged dollars in the Order Control Summary table. The system totals the Exchanged dollars value for each transaction date in the accounting period to determine the merchandise amount total of returned items in exchanged transactions for the accounting period. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Information for order recap totals: Totals display only if you have run the Batch Order Control job; these totals are cumulative up to the date and time of the last update. | |
Opn (Open) |
Total number of open orders, open units, and total amount of open order lines. OrdersThe total number of open orders; this is the number of orders in an open status. This is the Open orders number in the Order Control Summary table for the most recent transaction date. UnitsThe total number of open units; this is the total number of units on open order lines, including units on backorder and regardless if the units are printed or unprinted. This also includes units on order lines that are in a held status. This is the total of the Open backordered quantity, Open printed quantity, and Open unprinted quantity in the Order Control Summary table for the most recent transaction date. |
Amount The merchandise amount total of open order lines, including open order lines containing backordered units and regardless if the units are printed or unprinted. This also includes the merchandise amount for order lines that are in a held status. This is the total of the Open backordered dollars, Open printed dollars, and Open unprinted dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Hld (Held) |
Total number of held orders, held units, and total amount of order lines on held orders. OrdersThe total number of held orders; this is the number of orders in a held status. This is the Held orders number in the Order Control Summary table for the most recent transaction date. UnitsThe total number of held units; this is the total number of units on held orders, including units on backorder and regardless if the units are printed or unprinted. This does not include units on held order lines if the order is not held. This is the total of the Held backordered quantity, Held printed quantity, and Held Unprinted quantity in the Order Control Summary table for the most recent transaction date. |
Amount The merchandise amount total of held orders, including order lines containing backordered units and regardless if the units are printed or unprinted. This does not include merchandise amounts for held order lines if the order is not held. This is the total of the Held backordered dollars, Held printed dollars, and Held unprinted dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Sus (Suspended) |
Total number of suspended orders, suspended units, and total amount of suspended orders, regardless if the order is batched. OrdersThe total number of suspended orders; this is the number of orders in a suspended status or error status as defined in the Order Header table. This is the Orders suspended number in the Order Control Summary table for the most recent transaction date. UnitsThe total number of units on suspended orders, including orders in a suspended status and error status. The system uses this calculation over the Order Detail table to determine the suspended units: quantity ordered - quantity cancelled - quantity shipped - quantity soldout = suspended units. This is the Orders suspended quantity in the Order Control Summary table for the most recent transaction date. |
Amount The merchandise amount total of suspended orders, including orders in a suspended status and error status. This is the sum of the merchandise amounts for suspended and orders in error in the Order Ship To table. This is the Orders suspended dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
OBO (Open/backordered) |
Total number of open backordered orders, open backordered units, and total merchandise amount of open backordered units. The system determines if an item is on backorder using this calculation: open quantity on order line - reserved quantity on order line = backorder quantity. The system uses this calculation to determine the open quantity: order quantity - shipped quantity - cancelled quantity - soldout quantity = open quantity. OrdersThe total number of open orders that contain at least one unit on backorder, including the total number of ship-to addresses for orders with multiple ship-to’s. For example, an order with two ship-to addresses updates the number of orders total by 2. This is the Future use 1 number in the Order Control Summary table for the most recent transaction date. UnitsThe total number of backordered units on open orders. This is the Quantity backordered in the Order Control Summary table for the most recent transaction date. |
Amount The total merchandise amounts of backordered units on open orders. This is the Open backordered dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
HBO (Held/backordered) |
Total number of held backordered orders, held backordered units, and total merchandise amount of held backordered units. The system determines if an item is on backorder using this calculation: open quantity on order line - reserved quantity on order line = backorder quantity. The system uses this calculation to determine the open quantity: order quantity - shipped quantity - cancelled quantity - soldout quantity = open quantity. OrdersThe total number of held orders that contain at least one unit on backorder, including the total number of ship-to addresses for orders with multiple ship-to’s. For example, an order with two ship-to addresses updates the number of orders total by 2. This is the Future use 2 number in the Order Control Summary table for the most recent transaction date. UnitsThe total number of backordered units on held orders. This is the Quantity held backordered in the Order Control Summary table for the most recent transaction date. |
Amount The total merchandise amount of backordered units on held orders. This is the Held backordered dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
|
Opn/Prt (Open/Printed) |
Total number of units on open orders for which pick slips have been printed and total merchandise amount of units on open orders for which pick slips have been printed. UnitsThe total number of printed units on open orders. The total number of open printed units is the Open printed quantity in the Order Control Summary table for the most recent transaction date. AmountThe total merchandise amount of printed units on open orders. This is the Open printed dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
Hld/Prt (Held/printed) |
Total number of units on held orders for which pick slips have been printed and total merchandise amount of units on held orders for which pick slips have been printed. UnitsThe total number of printed units on held orders. This is the Held printed quantity in the Order Control Summary table for the most recent transaction date. AmountThe total merchandise amount of printed units on held orders. This is the Held printed dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
Opn/Rsv (Open/reserved) |
Total number of units on open orders which are reserved and total merchandise amount of units on open orders which are reserved. UnitsThe total number of reserved units on open orders. This is the Open unprinted quantity in the Order Control Summary table for the most recent transaction date. AmountThe total merchandise amount of reserved units on open orders. This is the Open unprinted dollars in the Order Control Summary table for the most recent transaction date. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
Hld/Rsv (Held/reserved) |
Total number of units on held orders which are reserved and total merchandise amount of units on held orders which are reserved. UnitsThe total number of reserved units on held orders. This is the Held unprinted quantity in the Order Control Summary table. AmountThe total merchandise amount of reserved units on held orders. This is the Held unprinted dollars in the Order Control Summary table. Number fields: numeric, 9 positions; display-only. Amount fields: numeric, 20 positions with a 2-place decimal; display-only. |
General information | |
Last updated on/at |
The date and time when the Batch Order Control job was last run, updating the operations and merchandising totals. Date: numeric, 6 positions, in user date format; display-only. Time: numeric, 6 positions, HH:MM:SS format; display-only. |
Suspended batches |
The total number of order batches that are in a suspended status. The system determines the number of order batches in a suspended status by totaling the number of orders in the Order Batch table whose Batch suspended field is selected. This is the Batches suspended number in the Order Control Summary table. Numeric, 9 positions; display-only. |
Screen Option | Procedure |
---|---|
Review operations summary information on the second Operations Control Summary screen. |
Select OK to advance to the Second Operations Control Summary Screen. |
Update the operation totals on the screen |
Select Refresh screen to update the operations totals. |
Review order summary information by date or select a date for which you want to view detailed order summary information |
Select Display all days to advance to the Display Operations Control Summary Screen. |
Update current totals for open/held order recap information and print the Order Control Report for the current date. |
Select Update current totals to submit the batch job ORD_CONTRL, which will update the information in the lower part of the screen (Order Recap information). After the batch job is completed, you must select Refresh screen to view the changes. This batch job will also print the Operations Control Report for the current date. Note: This option is not available when you display this screen for dates other than the current date. If you try to use this option for past dates, the screen displays the following error message: Update cannot be submitted for a prior date. |
Review merchandising summary information for the date you are currently reviewing |
Select Merchandising to advance to the Merchandising Control Summary screen. |
Second Operations Control Summary Screen
Purpose: Use this screen to review operations control summary information, such as the number, quantity, and amount total of pending pick slips, pending RA receipts, pending RA credits, and pending refunds.
Updating totals: See Updating Operations and Merchandising Summary Totals for more information on how the system updates the totals on this screen.
If you display this screen for a date when you did not update the totals, there is no information on this screen.
How to display this screen: Select OK at the First Operations Control Summary Screen.
Field | Description |
---|---|
Date (unlabeled field at the center top of the screen) |
The current date, or the date you have selected at the Display Operations Control Summary Screen. The operations summary information displayed below this date reflects total ongoing activity for the date. Numeric, 6 positions, in user date format; display-only. |
Totals display only if you have run the Batch Order Control job; these totals are cumulative up to the date and time of the last update. | |
Pick slips |
The number of pending pick slips, number of units on pending pick slips, and merchandise amounts for pending pick slips. Pending pick slips are pick slips that have been printed but not yet billed, not including pick slips voided, waiting for authorizations, or suspended. The system increases the pending pick slip number, units, and amounts for drop ship orders if the drop ship output defined for the vendor is drop ship pick slip; if the drop ship output defined for the vendor is drop ship purchase order or collaborative shipping, the system only increases the total units and total amounts pending and does not increase the total number pending. NumberThe total number of pick slips pending. This is the Pending picks number in the Order Control Summary table. UnitsThe total number of units on pending pick slips. This is the total of the Open printed quantity and Held printed quantity in the Order Control Summary table for the most recent transaction date. |
Amount The merchandise amount total of items on pending pick slips. This is the total of the Open printed dollars and Held printed dollars in the Order Control Summary table. Number fields: numeric, 9 positions; display-only. Amount field: numeric, 20 positions with a 2-place decimal; display-only. |
|
RA receipts |
The number of pending return authorization receipts, number of units on pending return authorization receipts, and merchandise amounts for pending return authorization receipts. Pending return authorization receipts are return authorizations that have been entered, but not yet received. You can only enter a pending RA receipt using non-streamlined return authorizations (the Use Streamlined Return Authorizations (F44) system control value is selected. These totals include quantities and merchandise amount of the items returned in return transactions and items returned in exchange transactions, not units and merchandise amount of items ordered in exchange. See Returning and Exchanging Items in Order Maintenance. |
Number The total number of pending return authorization receipts, regardless of whether the returns are on the same order. For example, an order with 2 pending RA receipt order lines processed separately updates this total by 2; however, if the same 2 pending RA receipt order lines on a single order are processed in the same transaction, the total updates by 1. The system determines the number of pending RA receipts by totaling the number of RA header records whose date received is 0. This is the Pending RA receipt number in the Order Control Summary table. UnitsThe total number of units on pending return authorization receipts. The system determines the number of units on pending RA receipts by looking at the RA detail records whose quantity returned is less than the quantity to return and totaling the unreceived quantity. This is the Pending RA receipt quantity in the Order Control Summary table. |
|
Amount The merchandise amount total of items on pending return authorization receipts. The system determines the merchandise amounts of items on pending RA receipts by multiplying the unreceived quantity by the order detail price. This is the Pending RA receipt dollars in the Order Control Summary table. Number fields: numeric, 9 positions; display-only. Amount field: numeric, 20 positions with a 2-place decimal; display-only. |
|
RA credits |
The number of pending return authorization credits, number of units on pending return authorization credits, and merchandise amounts for pending return authorization credits. Pending return authorization credits are return authorizations that have been received, but not yet credited. You can only enter a pending RA credit using non-streamlined return authorizations (the Use Streamlined Return Authorizations (F44) system control value is selected). These totals include quantities and merchandise amount of the items returned in return transactions and items returned in exchange transactions, not units and merchandise amount of items ordered in exchange. See Returning and Exchanging Items in Order Maintenance. |
Number The total number of pending return authorization credits, regardless of whether the returns are on the same order. For example, an order with 2 pending RA credit order lines processed separately updates this total by 2; however, if the same 2 pending RA credit order lines on a single order are processed in the same transaction, the total updates by 1. The system determines the number of pending RA credits by totaling the number of RA header records whose date received is greater than 0 and date credited is 0. This is the Pending RA credit number in the Order Control Summary table. UnitsThe total number of units on pending return authorization credits. The system determines the number of units on pending RA credits by looking at the RA detail records whose quantity credited is less than the quantity to credit and totaling the uncredited quantity. This is the Pending RA credit quantity in the Order Control Summary table. |
|
Amount The merchandise amount total of items on pending return authorization credits. The system determines the merchandise amounts of items on pending RA credits by multiplying the uncredited quantity by the order detail price. This is the Pending RA credit dollars in the Order Control Summary table. Number fields: numeric, 9 positions; display-only. Amount field: numeric, 20 positions with a 2-place decimal; display-only. |
|
Refunds |
The number of pending refunds, number of units on pending refunds, and merchandise amounts for pending refunds. Pending refunds are refunds in an open or held status that have not yet been processed; these totals do not include refunds that are in a pending canceled, canceled, pending write off, write off, or processed status. NumberThe total number of unprocessed refunds. This is the Refunds pending number in the Order Control Summary table. AmountThe merchandise amount total of items on unprocessed refunds. This is the Refunds pending dollars in the Order Control Summary table. Number field: numeric, 9 positions; display-only. Amount field: numeric, 20 positions with a 2-place decimal; display-only. |
Last updated on/at |
The date and time when the Batch Order Control job was last run, updating the operations and merchandising totals. Date: numeric, 6 positions, in user date format; display-only. Time: numeric, 6 positions, HH:MM:SS format; display-only. |
Screen Option | Procedure |
---|---|
Review operations summary information on the first Operations Control Summary screen. |
Press Page Up to advance to the First Operations Control Summary Screen. |
Update the operation totals on the screen |
Select Update current totals. |
Review order summary information by date or select a date for which you want to view detailed order summary information |
Select Display all days to advance to the Display Operations Control Summary Screen. |
Update current totals for open/held order recap information and print the Order Control Report for the current date. |
Select Update current totals to submit the batch job ORD_CONTRL, which will update the information in the lower part of the screen (Order Recap information). After the batch job is completed, you must select Refresh screen to view the changes. This batch job will also print the Operations Control Report for the current date. Note: This option is not available when you display this screen for dates other than the current date. If you try to use this option for past dates, the screen displays the following error message: Update cannot be submitted for a prior date. |
Reviewing Pending Orders (DOSS)
Purpose: Use this option to review current totals of orders that require shipment or other processing or action, broken out by the type of action or processing required. The information displayed includes:
- order queue classification: quote, error, suspended, held, backordered, printed, pickup, or reserved
- for each queue:
-
total number of orders and total dollar value
-
oldest and newest order date
-
You can select an order queue to advance to a subsequent screen listing the individual orders in that queue and providing information about each order, such as merchandise total, source code, hold reason, and sold-to customer. At this screen, you can select an order for inquiry.
In this topic:
- Assignment Hierarchy for Pending Order Queues
- Pending Order Summary Screen
- Pending Order Details Screen
Assignment Hierarchy for Pending Order Queues
The system uses the following hierarchy to assign each order to a pending order queue:
- If the Quote field for the order type on the order is selected and the order is not in error, assign to the Quote queue; otherwise,
- If the order header status is Error, assign to the Error queue; otherwise,
- If the order header status is Suspended, assign to the Suspended queue; otherwise,
- If the order is a store pickup order, assign to the Pickup queue; otherwise,
- If the order ship-to status is Held, or if any of the ship-tos on a multi-recipient order is Held, assign to the Held queue; otherwise,
- If any of the order lines on any of the ship-tos is backordered, assign to the Backordered queue; otherwise,
- If any of the order lines on any of the ship-tos is printed on a pick slip, assign to the Printed queue; otherwise,
- Assign to the Reserved queue.
Considerations when determining queue assignment:
- Orders whose status is Canceled or Closed are not included in the pending orders screens.
- For non-quote orders, order lines are considered backordered if the reserved quantity is less than the quantity ordered - the quantity canceled - the quantity sold out - the quantity shipped.
- Brokered backorders are included in the Backordered queue.
- For non-quote orders, order lines for drop-ship items, non-inventory items, membership items, gift cards, and main set items are considered reserved, not backordered.
- Orders that include held order lines are not automatically assigned to the Held order queue. The system evaluates this status at the order ship-to level, not at the order line level.
- Order lines are considered printed if they are included on a regular pick slip, a drop ship pick slip, or a drop ship purchase order.
- For non-quote orders, the status of order lines controls the queue assignment even if the order line is “no charge.” For example, if all the items on an order are reserved except for a “no charge” item that is backordered, the order is assigned to the Backordered queue rather than the Reserved queue.
- Quote orders that are suspended are included in the Quote queue rather than the Suspended queue; however, quote orders that are in error are included in the Error queue. A quote order received through the order API might be in error if the Pay method required field is selected for the quote order type and there was no payment method on the order, or if any other information in the CWOrderIn message was invalid.
Determining the order count: The Order count at the Pending Order Summary Screen is based on the order header for multi-recipient orders, not the individual order ship-tos. For example, an order with 3 recipients increases the Order count by 1, not 3.
Determining the order amount:
- The $ on orders total at the Pending Order Summary Screen and the Order amount at the Pending Order Details Screen include total merchandise value based on actual selling price only. The totals do not include tax, freight, additional freight, or additional charges, and do not reflect offer prices before applying discounts or price overrides.
- Only order lines whose status is open, held, error, or closed are included in the $ on orders total at the Pending Order Summary Screen or the Order amount at the Pending Order Details Screen. Canceled and soldout lines are not included in the total.
- The extended value of all eligible order lines (open, held, error, or closed) is included in the displayed total, even if the order line status does not correspond to the queue status. For example, if any lines on the order are backordered, the entire merchandise total for the order is included, even though some of the lines might be reserved or closed.
- Negative order line values (which can occur when you process a return by entering a negative quantity) are subtracted from the total order value.
Pending Order Summary Screen
Purpose: Use this screen to review the total pending orders broken out by queue assignment. See Reviewing Pending Orders (DOSS) for a discussion.
Reviewing Pending Orders (DOSS)How to display this screen: Enter DOSS in the Fast path field at the top of any menu, or select Pending Orders from a menu.
Field | Description |
---|---|
Queue |
The queue assignment, indicating the type of action you need to take to process the order. Each order is assigned to a queue as follows:
See Assignment Hierarchy for Pending Order Queues for an overview. Note: If there are no orders meeting the criteria for a particular queue, the screen does not display that queue.See Assignment Hierarchy for Pending Order Queues for a discussion. Click on a queue name to advance to the Pending Order Details Screen. |
Oldest date |
The oldest Order date of all orders in the queue. This is the Date displayed on the order header screen in standard order inquiry. Numeric, 6 positions (in user date format); display-only. |
Newest date |
The newest Order date of all orders in the queue. This is the Date displayed on the order header screen in standard order inquiry. Numeric, 6 positions (in user date format); display-only. |
Order count |
The total number of orders in the queue. Increased by 1 for a multi-recipient order. See Assignment Hierarchy for Pending Order Queues for a discussion of how orders are assigned to a particular queue. Numeric, no pre-defined maximum length; display-only. |
$ on orders |
The total merchandise dollar value of orders assigned to the queue. This total includes merchandise value based on actual selling price only, and does not include tax, freight, additional freight, or additional charges, and does not reflect offer prices before applying discounts or price overrides. Also, only order lines whose status is open, held, error, or closed are included in the total; canceled and soldout lines are not included.
Numeric, no pre-defined maximum length, with a 2-position decimal; display-only. |
Options at this screen:
Option | Procedure |
---|---|
Review orders within a queue |
Click the queue name to advance to the Pending Order Details Screen, where you can review the orders in that queue. |
Change the order in which queues are sorted on the screen |
Click a column heading to sort the queues by that column. For example, click Order count to sort the queues in ascending sequence by total order count. Once you have sorted by a column, you can click the column heading again to reverse the sort. For example, click Order count again to reverse the sort from ascending to descending sequence. |
Pending Order Details Screen
Purpose: Use this screen to review the individual orders within a pending order queue.
How to display this screen: Select a queue at the Pending Order Summary Screen.
When you first advance to this screen, orders display in ascending order number sequence.
Maximum number of records to display: The system displays the first 500 records in the queue that meet your search criteria. The following message displays if there are more than 500 records to display:
The maximum number of records was exceeded. Please refine search criteria. Showing records 1-500.
You can use the Order # and Date fields on this screen to refine the pending order details you wish to review. In order to refine the records that display you must select OK after you enter your search criteria.
Field | Description |
---|---|
Queue |
The queue selected at the Pending Order Summary Screen. |
Order # |
An order number assigned to the queue. See Assignment Hierarchy for Pending Order Queues for background. You can click the order number to advance to standard order inquiry for that order. Numeric, 8 positions; optional. |
Date |
The order date. This is the Date displayed on the order header screen in standard order inquiry. Numeric, 6 positions (in user date format); optional. |
Customer # |
The sold-to customer who placed the order. Numeric, 9 positions; display-only. |
Rcp (recipient) |
The number of shipping addresses on the order. Numeric, 3 positions; display-only. |
Order type |
The description of the order type, as set up through Establishing Order Types (WOTY). Alphanumeric, 30 positions; display-only. |
Order amount |
The total merchandise dollar value of the order. This total includes merchandise value based on actual selling price only, and does not include tax, freight, additional freight, or additional charges, and does not reflect offer prices before applying discounts or price overrides. Also, only order lines whose status is open, held, error, or closed are included in the total; canceled and soldout lines are not included.
Numeric, no pre-defined maximum length, with a 2-position decimal; display-only. |
Source code |
The source code from the order header. Alphanumeric, 9 positions; display-only. |
Hold reason |
The hold reason code, if any, assigned to the order header. Hold reasons assigned to an order ship-to might differ from the reason code at the header. This field is used only when you are reviewing orders in the Held order queue. See Introducing Order Hold Reason Codes for an overview. Alphanumeric, 2 positions; display-only. |
Ship via |
The ship via code assigned to the order. If the order has more than one ship to, this is the ship via code for the order from the Order Ship To table with the lowest numeric number, regardless of the status of the ship to order. Numeric, 2 positions; display-only. |
Scanning and display sequence options: Click a column name to sort the displayed orders in ascending or descending sequence by that field. For example, click the Hold reason column name once to display orders in alphanumeric sequence by hold reason code; click the Hold reason column name again to display orders in reverse alphanumeric sequence.
Current display sequence indicated: An arrow next to a column heading indicates that the orders are currently displayed in sequence based on that column.
For example, the upward-pointing arrow indicates that orders are displayed in ascending sequence by order value:

The downward-pointing arrow indicates that orders are displayed in descending sequence:

Combining display sequence with scan fields: You can also scan on the Date field to restrict the displayed orders by date. For example, if you enter a date and then click the Customer # column heading, the screen displays orders for that date or later in customer number sequence.
Retaining display sequence: When you change the display sequence for an order queue, then return to the Pending Order Summary Screen and select a different queue for review, the screen retains the display sequence. For example, you review held orders and click the Order amount field to display orders in ascending sequence by dollar value. If you then exit the screen and select reserved orders for review, the screen displays reserved orders in ascending sequence by dollar value.
Note:
Sorting by order number is not supported.Options at this screen:
Option | Procedure |
---|---|
Select an order for inquiry |
Click an order number to advance to standard order inquiry for that order. See Order Inquiry for a discussion. |
Change the display sequence on the screen |
See above for a discussion. |
Refresh the list of orders |
Select Reset to refresh the order information displayed on the screen and to clear the information in the Order # and Date scan fields. |
Sales Summary (DSSS)
Purpose: Use the Sales Summary screen to view the number and dollar value of shipments processed:
- for the current day, week, and month
- broken out by order type and entity
Updated continuously: The totals displayed are based on the Invoice Ship To records created when you ship orders. When the BILL_ASYNC job is running, it creates these records as part of initially billing an order. These updates are not deferred based on the setting of the Delay Billing Updates (K85) system control value.
Modern View option: A Sales Summary page is also available in Modern View, including tiles at the top of the page, with totals are broken out by order type below, and bar charts illustrating the percentages of merchandise value billed for each order type. If your company supports fulfilling orders through integration with Order Broker, totals are broken out by delivery type as well, including store pickup, delivery, retail pickup, and ship-for-pickup. Orders that were not fulfilled through the Order Broker integration are listed as direct delivery. See the Sales Summary page in the Modern View online help for more information.
In this topic:
Calculations
Which invoices are included? The totals displayed on this screen include Invoice Ship To records for regular (debit) invoices and their merchandise totals only. This screen does not include:
- Returns, credits, or discounts applied after shipment
- Freight, tax, handling, or other charges
- Any invoice with a merchandise total of $0.00
How is the invoice date determined? This screen organizes shipments based on the Invoice date from the Invoice Ship To record. This date is from the Start date from the BILL_ASYNC job. If the background jobs are running using a previous date because they are not stopped and restarted daily, then the invoices billed today are included under that previous date, not under Today.
How is the number of sales calculated? The total number of sales for a period, order type, or entity is from the total number of Invoice Ship To records billed. This total:
- Excludes (is not net of) credit invoices, such as an invoice created by processing a return. For example, if you process 1000 shipments, 50 returns, and 10 discount credits after shipment, the total displayed here is still 1000.
- Does not include any invoice with a merchandise total of $0.00.:
For more information: See Consolidated Invoice (B49) for a discussion on the factors that control how many invoices are generated for orders that include multiple shipments on the same day.
Important:
In Order Management System 21.0 or higher, you cannot select the Consolidated Invoice system control value if it is not already selected. If the system control value is currently selected (set to Y) and you deselect it (change it to N or blank), you cannot then change it back to selected. The option to consolidate invoices will be removed at a later date.How is the sales amount calculated? The total sales amount for a period, order type, or entity is from the total dollar value of merchandise billed for the period, based on actual selling price. This total:
- Excludes (is not net of) returns, credits, or discounts applied after shipment.
- Does not include freight, tax, handling, or other charges.
- Includes a two-position decimal.
Sales Summary Screen
How to display this screen: Enter DSSS in the Fast path field at the top of any menu, or select the Sales Summary option from a menu.
Field | Description |
---|---|
Current day, week, and month totals |
The top portion of the screen displays totals for the current day, week, and month. |
Period |
Periods are: Today = The current date. This week = The current week runs from Monday through Sunday, and the totals displayed include all days so far for this period. Note: The calculation of totals for This week occurs regardless of whether a new month starts during the week.Example: Today is Sunday June 3. The totals displayed under This week include Monday May 28 through the current date. This month = The totals for the current month to date. Note: See the note above on how invoice date is determined. |
Number |
See the Calculations above for a discussion. |
Amount |
See the Calculations above for a discussion. |
Order Type totals for today |
The Order Type tab lists the current day’s total number of Invoice Ship To records and dollar amounts for each order type in your company, except for quote order types. Note: See the note above about how invoice date is determined. |
Order type |
The code identifying the order type. The description of the order type follows, separated by a hyphen. Order types are defined in and validated against the Order Type table. See Establishing Order Types (WOTY) for more information. Quote order types are not listed here, since it is not possible to bill merchandise for a quote. See Entering Pre-Order Quotes for background. |
Number |
See the Calculations above for a discussion. |
Amount |
See the Calculations above for a discussion. |
Entity totals for today |
The Entity tab lists the current day’s total number of Invoice Ship To records and dollar amounts for each entity in your company. Note: See the note above on how invoice date is determined. |
Entity |
The code identifying a business entity within your company. The description of the entity follows, separated by a hyphen. Entities are defined in and validated against the Entity table. See Working with Entities (WENT) for more information. |
Number |
See the Calculations above for a discussion. |
Amount |
See the Calculations above for a discussion. |
Printing the Order Type Summary by Delivery Type Report (PDTS)
Purpose: Use this menu option to print the Order Type Summary Report by Delivery Type, which provides a summary of order information by order type and delivery type for a specified date range. This is useful if you want to review a snapshot of orders for today.
Order Delivery Type Summary Screen
Use this screen to define the selection criteria you wish to use to print the Order Type Summary by Delivery Type Report.
How to display this screen: Enter PDTS in the Fast path field at the top of any menu or select Order Type Summary by Delivery Type Report from a menu.
Field | Description |
---|---|
Start date |
The first order date to include on the report. The system includes orders whose Order date in the Order Header table is equal to or greater than this date. The From date cannot be greater than the To date. The date cannot be greater than the current date. If you enter a From date, you must also enter a To date. Numeric, 6 positions (in user date format); required. |
End date |
The last order date to include on the report. The system includes orders whose Order date in the Order Header table is equal to or earlier than this date. The From date cannot be greater than the To date. The date cannot be greater than the current date. If you enter a From date, you must also enter a To date. Numeric, 6 positions (in user date format); required. |
Screen Option | Procedure |
---|---|
Generate the Order Type Summary by Delivery Type Report |
Enter a date range and select Submit. The system submits the MSR1174RPT job to generate the report and returns you to the main menu. |
Managing Declined Authorizations
In this part: This part presents the functions available to cancel orders that are declined by an authorization service, and includes the following topic:
- Working with Credit Card Cancellations (WCCC) shows you how to cancel orders flagged for cancellation due to credit card decline.
Working with Credit Card Cancellations (WCCC)
Purpose: Use the Work with Credit Card Cancellations function to cancel orders whose credit cards have been declined by the authorization service.
In this topic:
Overview
You can define different actions to take for each vendor response code you receive from an authorization service. For example, if the service declines an authorization because the card is over its credit limit, you could set up the system to put the order on hold for five days and reattempt authorization after that time. You have the option of setting up a vendor response so that the system will flag the order for cancellation, either when the credit card is first declined or after a given number of attempts.
Determining when to flag for cancellation: The system determines that an order should be flagged for cancellation based on the number of declines received from the authorization service. You can set up the maximum number of declines in two ways:
- vendor response code: Specify the maximum number of attempts for an individual vendor response code. For example, a vendor response code that indicates credit card fraud might trigger cancellation after one authorization attempt; a vendor response code that indicates insufficient credit limit might trigger order cancellation after four or more attempts. Some response codes might be set up to attempt authorization an unlimited number of times, and never trigger a cancellation.
- system control value: The Maximum Number of Retries on Credit Card Orders (E74) system control value specifies the number of times to attempt reauthorization across all vendor responses. Overrides the limits you set up for individual response codes; in other words, if you specify you will attempt authorization 15 times for a vendor response code, but the system control value is set to 10, the system will not exceed 10 attempts.
The counter for authorization attempts is reset when you receive an authorization.
Example: An order:
- fails authorization three times
- is authorized
- you make a partial shipment
- the order fails authorization again
This last decline counts as response number one.
What happens when an order is flagged for cancellation? The system creates a record in the Backorder Cancellation Pending table (BOCANP). These records are assigned a type of C, to distinguish them from orders flagged for cancellation due to a backorder. In addition, the system writes:
- an Order History message, which you can review in standard or streamlined order inquiry by selecting Messages; see Display Order History Screen
- a cancel date on the order detail line, which you can review in standard order inquiry by selecting Display for an item or in streamlined order inquiry by selecting the Detail option; see Reviewing Order Details.
If an order is flagged for cancellation but is not on hold, it will still be submitted for authorization.
Once an order is flagged for cancellation, you cannot exclude it when you cancel credit cards. Deleting the cancel date on the order detail line will not prevent the order from being canceled by this function. The system cancels every order flagged with a C in the Backorder Cancellation Pending table, and there is no visibility into this table through a Order Management System menu option.
What happens when you cancel orders? You can use the Work with Credit Card Cancellations menu option to cancel all orders flagged for cancellation due to credit card decline, or you can select all orders within a given range of cancel dates. The system:
- Cancels each flagged order, using the cancel reason specified for the vendor response code that triggered the cancellation. If the order is cancelled because it exceeded the maximum number of declines defined in the System Control table, the system uses the cancel reason code for the most recent vendor response that has a cancel reason code assigned. If none of the responses in the order's authorization history is assigned a cancel reason code, the system uses the default cancel reason defined in the Auto Soldout Cancel Reason (C20) system control value.
- Produces the Credit Card Order Cancellation List.
- Writes an order line history message for all canceled items (available by selecting Message for the item in standard or streamlined order inquiry) specifying the quantity canceled and the cancel reason code.
- Removes any pick slip preparation that has been applied to the order; see Preparing Orders for Pick Slip Generation.
Note:
If the cancel reason code set up to reduce demand, the order status after cancellation will be X; otherwise, the order status after cancellation will be C.Cancellation email: The system generates an order cancellation email or to the customer if:
- you have specified an Order Cancellation Email Program (K78), and
- there have not been any shipments on the order, and
- the cancel reason code you use does not match the Cancel Reason Code to Suppress Email (L08), and
- the customer is eligible to receive email notifications; see When Does the System Generate an Email Notification?
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
If there have been any shipments on the order, the system generates the order line cancellation email even if all the remaining order lines are now canceled.
See the Order Cancellation Confirmation Email Sample and Contents and the Order Line Cancellation Confirmation Email Sample and Contents for more information.
Stored value card authorization reversal: If a stored value card payment with an open, unused authorization amount exists on the order, the system also generates a stored value card authorization reversal; see Stored Value Card Authorization Reversal.
Periodic function: You can also set up credit card cancellations to run as part of your periodic processing, using function BOR0029. In this case, you would not be able to specify a range of dates; all flagged orders would be canceled.
Cancellation email: The system generates an order or order line cancellation email to the customer if:
- you have specified an Order Cancellation Email Program (K78) or Order Line Cancellation Email Program (K79), and
- the cancel reason code you use does not match the Cancel Reason Code to Suppress Email (L08), and
- the customer is eligible to receive email notifications; see When Does the System Generate an Email Notification?
See the Order Cancellation Confirmation Email Sample and Contents and the Order Line Cancellation Confirmation Email Sample and Contents for more information.
What happens if the order includes a membership item? If you use this menu option to cancel an order that includes a membership item, the order cancellation process does not automatically cancel the customer membership created by the membership item. You need to use Working with Customer Memberships (WWCM) in order to cancel the customer membership. See Membership Overview for background on customer memberships.
For more information:
- vendor response codes and an overview of the authorization process: Defining Vendor Response Codes
- Establishing Cancel Reason Codes (WCNR)
- Establishing Order Hold Reason Codes (WOHR)
- Maximum Number of Retries on Credit Card Orders (E74) system control value
- reviewing authorization history for an order: Reviewing Financial Information on an Order
- setting up periodic processing: Working with Periodic Functions (WPER)
Cancel Credit Card Order Cancellation Screen
How to display this screen: Enter WCCC in the Fast path field at the top of any menu or by selecting Work with Credit Card Cancellations from a menu.
Field | Description |
---|---|
Beginning date |
The earliest cancel date to include when selecting credit card orders for cancellation. You cannot enter a beginning date without also entering an ending date. Numeric, 6 positions (in user date format); optional. |
Ending date |
The latest cancel date to include when selecting credit card orders for cancellation. You cannot enter an ending date without also entering a beginning date. Numeric, 6 positions (in user date format); optional. |
Instructions:
- Optionally, complete the beginning and ending dates.
- Select OK. The system validates your entries and highlights any field you need to correct. Correct any fields and select OK again.
- Select Accept.
- If you have entered a range of dates, the system submits the job CC_CANCELS.
- If you have not entered a range of dates, the system displays the Confirm Cancellation of Orders window. At this window, select OK to confirm that you want to cancel all credit card orders flagged for cancellation; otherwise, select Exit to cancel.
The CC_CANCELS job cancels each order flagged for cancellation using the cancel reason code associated with the vendor response code received from the vendor. This job also generates the Credit Card Order Cancellation List.
Releasing Held Orders
Topics in this part: The following sections describe how to review and release held orders:
- Introducing Order Hold Reason Codes describes system-assigned hold reason codes and their application to orders, and presents the screens you work with to create user-assignable hold reason codes.
- Working with Customer Fraud Tables (WCFD) discusses the process of creating, changing, and deleting fraudulent customers based on customer name and address.
- Working with Miscellaneous Frauds (WMFF) discusses the process of creating, changing, and deleting fraudulent customers based on postal or zip code, credit card, and check.
- Selecting Held Orders (ERHO) describes the screens that provide your initial point of access to held orders display and release tables.
- Displaying Order Hold Information presents the customer screens you can use to investigate customer detail on a held order, and the Order Inquiry function you can use to review order status.
- Performing the Release presents a pictorial map of screen relationships between the Release Held Order scan screen and the Release Recipients screens, and discusses release functions you use to release orders by recipient, payment method, and order number.
Working with Customer Fraud Tables (WCFD)
Purpose: You can build several fraud tables on the system to evaluate customers to see if they are frauds, based on their:
- Names
- Addresses
- Postal codes
- Credit cards
- Checks
The system checks for fraudulent customers whenever you process a new order during order entry, or when you create a new customer through the Customer Maintenance table. When the system detects a fraud customer, based on the criteria you enter into the Customer Fraud table, the system places the customer's orders on hold and assigns a fraud reason code to the order.
Quotes: The system does not check for fraudulent customers until you convert a quote to an order; see Entering Pre-Order Quotes and Converting Quotes to Orders.
To create a customer fraud record: There are several ways you can create a customer fraud record:
- create a record using the Create Fraudulent Customer Screen.
Note:
Adding a customer to the Customer Fraud table does not by itself add a “fraud” flag to the customer's Hold/bypass/fraud field. You can add a flag to this field through order entry, order maintenance, or by working with the Customer Sold To or Customer Bill To table (See Creating and Updating Sold-to Customers (WCST) and Creating and Updating Bill-to Customers (WCBT)).- enter F in the Hold/bypass/fraud field for a sold to customer. If you flag a sold to customer as fraud, the system creates a customer fraud record for the sold to customer and a separate customer fraud record for each ship to customer associated with the sold to customer.
- enter F in the Hold/bypass/fraud field for a bill to customer. If you flag a bill to customer as fraud, the system creates a customer fraud record for the bill to customer only.
In this topic:
Work with Fraudulent Customers Screen
How to display this screen: Enter WCFD in the Fast path field at the top of any menu or select Work with Fraudulent Customers from a menu.
Field | Description |
---|---|
Match code |
A user-defined code that includes parts of the customer's name, company name, and address, which is used to identify duplicate (and fraud) customers. The structure of the match code is defined in the Match Code table; see Setting Up Match Codes (MMCH). Enter a full or partial match code and select OK to display customer fraud records in ascending match code order, beginning with your entry. Alphanumeric, 15 positions; optional. |
First name |
The customer's first name. Alphanumeric, 15 position; display-only. |
Last name |
The customer's last name. Enter a full or partial last name and select OK to display customer fraud records in ascending last name order, beginning with your entry. Alphanumeric, 25 positions, optional. |
Screen Option | Procedure |
---|---|
Create a fraudulent customer |
Select Create to advance to the Create Fraudulent Customer Screen. |
Change fraudulent customer information |
Select Change for a fraudulent customer to advance to the:
Note: If you change the address of a fraudulent customer here, the system updates the corresponding Sold To Customer record automatically.
|
Delete fraudulent customer information |
Select Delete for a fraudulent customer to delete it. Note: If you delete a customer from the Sold To Customer table, the system also deletes the corresponding record from the Customer Fraud table; however, if you delete a customer from the Customer Fraud table, the Sold To Customer record remains in the Customer table, but without the fraud status. |
Display fraudulent customers |
Select Display for a fraudulent customer to advance to the Display Fraudulent Customers Screen.You cannot change any information on this screen. See Create Fraudulent Customer Screen for field descriptions. |
Create Fraudulent Customer Screen
Purpose: Use this screen to add a customer to the Customer Fraud table.
How to display this screen: At the Work with Fraudulent Customers Screen, select Create.
Field | Description |
---|---|
Seq # (Sequence number) |
A number the system assigns to each fraudulent customer you create. Numeric, 7 positions; display-only. |
Match code |
A code that includes elements of the customer's name and address, which is used to identify duplicate or fraud customers. The system generates a match code when you finish creating a new customer fraud record. Alphanumeric, 15 positions; display-only. |
Fraud code 1 |
The first of three match codes, defined in the Customer Fraud table, that identifies the customer as fraudulent. A fraud match code exists for every customer in the Customer Fraud table. The system checks this table during order entry for the sold-to and bill-to addresses, and when you create a customer through customer maintenance. Alphanumeric, 15 positions; display-only. |
Fraud code 2 |
The second of three user-defined match codes that identifies the customer as fraudulent. A fraud match code exists for every customer in the customer Fraud table. The system checks this table during Order Entry for the sold-to and bill-to addresses. Alphanumeric, 15 positions; display-only. |
Fraud code 3 |
The third of three user-defined match codes that identifies the customer as fraudulent. A fraud match code exists for every customer in the customer Fraud table. The system checks this table during Order Entry for the sold-to and bill-to addresses. Alphanumeric, 15 positions; display-only. |
Name |
The following 5 fields are available for you to enter the customer's full name: PrefixA title that belongs before the customer's name (such as "Mrs." or "Dr."). Alphanumeric, 3 positions; optional. First NameThe customer's first name. Alphanumeric, 15 positions; optional. InitialThe initial of the customer's middle name. Alphanumeric, 1 position; optional. |
Last Name The customer's last name. Alphanumeric, 25 positions; optional. SuffixAn addition to the customer's full name (such as "M.D.", "Fr.", or "III"). Alphanumeric, 3 positions; optional. |
|
Company name |
The name of the company associated with the order. Alphanumeric, 30 positions; optional. |
Address |
The customer's full street address. Alphanumeric, 4 lines of 32 positions; optional. |
Apartment |
The apartment number or suite number of the delivery address. To enter an apartment or suite address: 1.Type APT to indicate an apartment or type STE to indicate a suite. 2.Insert a space and type the number of the apartment or suite; for example APT 4 or STE 116. Alphanumeric, 10 positions; optional. |
Zip/city/state |
Three fields are available for you to enter the customer's postal code, city, and state. ZipThe postal code or zip code for this customer. Alphanumeric, 10 positions; optional. CityThe city in which the customer lives, or receives mail or shipments. Alphanumeric, 25 positions; optional. StateThe state or province in which the customer lives, or receives mail or shipments. Note: The system does not validate this address in the same way it validates a customer’s address, as in order entry. For example, it does not validate that the state is associated with the SCF for the postal code.Alphanumeric, 2 positions; optional. |
Country |
The country where the customer lives. Alphanumeric, 3 positions; optional. |
Notes |
Three fields are available for you to enter additional notes about this fraudulent customer, such as why the customer is a fraud. If the fraudulent customer record was created by placing F in the Hold/bypass/fraud field in the Customer Sold to table or Customer Bill To table, you do not advance to the Change Fraudulent Customers screen when you wish to change fraudulent customer information; instead the system advances you to the Change Customer Screen (sold to fraud), Change Ship To Screen (ship to fraud) or Change Customer Bill To Screen (bill to fraud). If you wish to enter notes about a fraudulent customer created by placing F in the Hold/bypass/fraud field, you must enter the notes using the Edit Customer Notes Screen or Work with Bill To Notes Screen. Alphanumeric, three 60-position fields; optional. |
Working with Miscellaneous Frauds (WMFF)
Purpose: You can establish miscellaneous frauds based on postal code, check, credit card, email address, or IP address.
The system checks the Miscellaneous Fraud table only if the Fraud Checking (A68) system control value is selected. Quotes: The system does not check the Miscellaneous Fraud table until you convert a quote to an order; see Entering Pre-Order Quotes and Converting Quotes to Orders.
Defining miscellaneous frauds: The Type field indicates the type of information that is evaluated for fraud. Once you define the Type, enter the information that is fraudulent in the Code field.
Fraud Type | Results |
---|---|
C Credit Card |
The system compares the credit card number on a credit card pay type against the credit card numbers in the Miscellaneous Fraud table. If the credit card number on a credit card pay type matches a credit card number in the Miscellaneous Fraud table, the system places the order pay type on hold with a hold reason of CF (credit card fraud). Note: If you Use Credit Card Encryption (I97) or credit card tokenization, you cannot define miscellaneous fraud based on credit card. |
E Email Address |
The system compares the email addresses related to the order against the email addresses in the Miscellaneous Fraud table. Depending on which email address related to the order matched an email in the Miscellaneous Fraud table, the system puts the order on hold as follows:
|
Setting up a fraud email address: When setting up a fraud email address, you can define a specific email address or you can use the asterisk (*) as a wildcard match. Options are:
|
|
I IP Address |
When creating an order through the generic order API, the system updates the IP address in the Order Header Extended table if an ip_addr is provided in the Inbound Order XML Message (CWORDERIN). The system then compares the IP address for the order with the IP addresses in the Miscellaneous Fraud table. IP address matching is based on a full or partial IP address specified in the Miscellaneous Fraud table, which permits asterisks to be used as “wild cards.” For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Example: If the Miscellaneous Fraud record is 1.2.*.*, then any IP addresses that begin with 1.2 will cause orders to go on hold (1.2.3.4, 1.2.99.7, etc.). About IP address: The IP (internet protocol) address identifies where an order originates. The IP address is expressed as a series of four numbers separated by three periods (for example, 192.168.255.255). Each number in the series must be from 1 to 255. Depending on the type of network where the customer is logged in, the first one, two, or three numbers between the periods typically represent the hosting network itself. The remainder of the IP address can be permanently assigned to the user’s location (static IP address), or can be temporarily assigned each time the user logs in (dynamic IP address). In the case of a dynamically assigned IP address, creating a Miscellaneous Fraud record for the entire address would not be helpful, because the last portion of the address will be different every time. In this case, you can create a Miscellaneous Fraud record for the beginning portion(s) of the IP address, because this portion of the IP address identifies the hosting network. If the ip_addr matches the Miscellaneous Fraud record, the system puts the order on IP (IP address) hold and writes a message such as SYS HLD---IP ADDRESS HOLD (where IP ADDRESS HOLD is the description of the hold reason code) to the Order Transaction History table. |
K Check |
The system compares the micra number (routing number) on a check pay type against the micra numbers in the Miscellaneous Fraud table. If the micra number on the check pay type matches a micra number in the Miscellaneous Fraud table, the system places the order pay type on KF (check fraud) hold. |
Z Zip Code |
The system compares the postal code defined for a customer address against the postal codes in the Miscellaneous Fraud table. Setting up a fraud zip code: If you enter a 5-digit postal code in the Miscellaneous Fraud table, the system considers a postal code a match if the first 5 positions of the postal code defined for a customer address match the postal code in the Miscellaneous Fraud table. Example: if you enter 96624 in the Miscellaneous Fraud table, the system considers a customer address with postal code 96624 or postal code 96624-1620 as fraud. If the postal code for a customer matches a postal code in the Miscellaneous Fraud table, the system:
|
For more information: See Introducing Order Hold Reason Codes for more information on defining fraudulent hold reason codes.
In this topic:
Work With Miscellaneous Frauds Screen
How to display this screen: Enter WMFF in the Fast Path field at the top of any menu or select this option from a menu.
Note:
Depending on the user’s authority to credit card information, the system writes a record to the Credit Card Audit table when this screen is displayed. See Logging Credit Card Data Access in the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information.Field | Description |
---|---|
Type |
Indicates the type of information that is evaluated for fraud. Valid values are:
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Define a Type and select OK to display miscellaneous fraud records that match your entry. Optional. |
Code |
The information that is considered fraudulent, based on the code defined in the Type field. Check codeThe micra number located on the check. The micra number is also referred to as a routing number. Alphanumeric, 15 positions, optional. Credit card codeThe credit card number defined for a credit card pay type. Masking: If you do not have authority to the Display Full Credit Card Number (B14) secured feature, the credit card number displays in the default format specified at the Credit Card Number Layout Screen. For example, ************1443 may display instead of the entire credit card number. See Credit Card Number Format for an overview. Alphanumeric, 20 positions, optional. |
Email address The email address defined for an order or customer (sold to, bill to, or ship to). Alphanumeric, 50 positions; optional. IP addressThe full or partial IP address received for an order API (e-commerce) order. The IP address specified here can include asterisks (*) for “wild card” matching. For example, if the Miscellaneous Fraud record is 1.2.*.*, then any IP addresses that begin with 1.2 will cause orders to go on hold (1.2.3.4, 1.2.99.7, etc.). Zip codeThe postal code defined for the customer’s address. You can enter an extended, non-hyphenated code, or the initial 5 digits of the postal code. Define a Type and Code and select OK to display miscellaneous fraud records that match your entry. Alphanumeric, 9 positions, optional. |
Screen Option | Procedure |
---|---|
Create a miscellaneous fraud customer |
Select Create to advance to the Create Miscellaneous Fraud Screen. |
Change miscellaneous fraud information |
Select Change for a fraudulent customer to advance to the Change Miscellaneous Fraud Screen. At this screen you can only change fraud information. See Create Miscellaneous Fraud Screen for field descriptions. Note: Depending on the user’s authority to credit card information, the system writes a record to the Credit Card Audit table when this screen is displayed for a C (credit card) fraud record. See Logging Credit Card Data Access in the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information. |
Delete a miscellaneous fraud record |
Select Delete for a fraudulent customer to delete it. |
Display a miscellaneous fraud |
Select Display for a fraudulent customer to advance to the Display Miscellaneous Fraud Screen. You cannot change any information on this screen. See Create Miscellaneous Fraud Screen for field descriptions. Note: Depending on the user’s authority to credit card information, the system writes a record to the Credit Card Audit table when this screen is displayed for a C (credit card). See Logging Credit Card Data Access in the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information. |
Create Miscellaneous Fraud Screen
To create: Use this screen to add a fraudulent postal code, check, email address, or credit card to the Miscellaneous Fraud table.
How to display this screen: At the Work With Miscellaneous Frauds Screen, select Create.
Field | Description |
---|---|
Fraud type |
Indicates the type of information that is evaluated for fraud. Valid values are:
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Required. |
Fraud information |
The information that is considered fraudulent, based on the code defined in the Type field. Check codeThe micra number located on the check. The micra number is also referred to as a routing number. Alphanumeric, 15 positions, optional. Credit card codeThe credit card number defined for a credit card pay type. Masking: If you do not have authority to the Display Full Credit Card Number (B14) secured feature, the credit card number displays in the default format specified at the Credit Card Number Layout Screen. For example, ************1443 may display instead of the entire credit card number. See Credit Card Number Format for an overview. Alphanumeric, 15 positions, required for a check or credit card type. |
Email address The email address defined for an order or customer (sold to, bill to, or ship to).When setting up a fraud email address, you can define a specific email address or you can use the asterisk (*) as a wildcard match. Options are:
Alphanumeric, 50 positions; required for an email address type. |
|
IP address The full or partial IP address received for an order API order. The IP address specified here can substitute asterisks (*) as “wild cards” for one or more of the four numbers that make up the IP address. For example, if the Miscellaneous Fraud record is 1.2.*.*, then any IP addresses that begin with 1.2 will cause orders to go on hold (1.2.3.4, 1.2.99.7, etc.). The system validates that your entry includes four numbers between 1 and 255, separated by three periods. Matching begins at the first number of the series and works back, which means that one or more numbers in the series can consist of a “wild card” asterisk; however, once the IP address includes an asterisk, the remainder of the IP address cannot include any more numbers. The system displays an error message if your entry:
Alphanumeric, 15 positions; required for an IP address type. Zip codeThe postal code defined for the customer’s address. You can enter an extended, non-hyphenated code, or the initial 5 digits of the postal code. When setting up a fraud zip code, if you enter a 5-digit postal code in the Miscellaneous Fraud table, the system considers a postal code a match if the first 5 positions of the postal code defined for a customer address match the postal code in the Miscellaneous Fraud table. Example: if you enter 96624 in the Miscellaneous Fraud table, the system considers a customer address with postal code 96624 or postal code 96624-1620 as fraud. Alphanumeric, 9 positions; required for a postal code type. |
Selecting Held Orders (ERHO)
Purpose: You gain access to a list of held and suspended orders from the Release Held Orders scan screen. You can then use the subsequent screens to continue your scan for held orders, or to select individual orders for review or release.
Quotes: Held quotes are not included in the Release Held Orders (ERHO) menu option; you can use quote maintenance to remove the hold reason on the Work with Order screen from the quote; see Maintaining Quotes in Order Maintenance.
In this topic:
Release Held Order Scan Screen
Purpose: You can find held orders in two ways: by entering a specific customer number in the Customer number field, or by reviewing a list of orders by scanning on any other field on this screen. Optionally, you can display the Held Order Summary Screen, and select a hold reason for working with held orders.
How to display this screen: Enter ERHO in the Fast path field or select Release Held Orders from a menu.
Field | Description |
---|---|
Order # |
A number the system assigns to identify an order. Enter a valid order number in this field to advance to the Release Held Orders Screen (Working with Releases). Numeric, 8 positions; optional. |
Customer # |
A number to identify a customer who places an order. Enter a valid customer number to advance to the Release Held Orders Screen (Working with Releases). Numeric, 9 positions; optional. |
System hold reason |
A code that identifies the reason the system put an order on hold. See Introducing Order Hold Reason Codes. Enter a system hold code in this field to advance to the Release Held Orders Screen (Working with Releases). Note: You cannot search based on the Awaiting Credit Card Auth (CW) hold reason.Alphanumeric, 2 positions; optional. |
User hold reason |
A hold reason code assigned by an operator in Order Entry or Order Maintenance, or through the Generic Pick In API (Shipments, Voids, and Backorders). See Establishing Order Hold Reason Codes (WOHR). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Enter a user hold code in this field to advance to the Release Held Orders Screen (Working with Releases). Alphanumeric, 2 positions; optional. |
Order date |
The date an order was entered. Enter a date in this field ato advance to the Release Held Orders Screen (Working with Releases). Numeric, 6 positions (in user date format); optional. |
Ship via |
Represents a carrier who delivers merchandise to your customers. Enter a valid code in this field to display the Release Held Orders Screen (Working with Releases). Numeric, 2 positions; optional. |
Release Held Orders Screen (Working with Releases)
Purpose: This screen is your point of access to held orders.
How to display this screen: Enter valid criteria in one of the fields at the Release Held Order Scan Screen, or select a hold reason at the Held Order Summary Screen.
Using this screen: Use this screen to:
- Gain access to specific held order and customer information
- Perform releases at the bill-to record level
- Perform a global release on all orders listed
- Display hold reason codes
The appearance of this screen will vary depending on your selection criteria at the Release Held Order Scan Screen.
Additional fields: The fields not described under Release Held Order Scan Screen are:
Field | Description |
---|---|
New cust (New customer) |
Indicates if the customer associated with the held order is a new customer, based on purchase history.
|
Pay |
This code indicates whether an order is on hold because of pay type. Valid values are:
|
Rcp (Recipient) |
This code indicates whether an order is on hold for reasons related to the recipient customer. Valid values are:
|
Screen Option | Procedure |
---|---|
Release held orders by recipient |
Select Recipients for an order to advance to the Release Order Recipients Screen. |
Release an order from all holds |
Select Release for an order to release holds without advancing to another screen. See Performing the Release. |
Release held order payment method |
Select Payments for an order to advance to the Release Held Order Payment Methods Screen. |
Display customer information |
Select Cust Info for an order to advance to the First Display Customer Screen. |
Display order hold reason codes |
Select Hold reasons for an order to display a Held Order Reasons Pop-Up Window (Displaying Hold Reason Codes). |
Advance to standard Order Inquiry |
Select Order Inquiry for an order to advance to the Order Inquiry Header Screen or the Order Inquiry Detail Screen, depending on the setting of the Default Version for Order Inquiry (C34) system control value. See Using the Order Inquiry Header Screen to Review Held Orders for a discussion on relevant information on the header screen in standard order inquiry. |
Display order messages |
Select Messages to advance to the Work with Order Messages Screen. |
Working with Return Authorizations (WRTA)
For information on: | See: |
---|---|
The stages of creating, receiving, and issuing credit for merchandise returns; background |
|
Selecting orders for return authorization and different scanning and selection options |
|
Standard return authorization processing through Work with Return Authorizations |
|
Streamlined return authorization processing through Work with Return Authorizations |
Managing Returns
In this part:
- Introducing Return Authorizations (WRTA) discusses the three stages of creating, receiving, and issuing credit for merchandise returns.
- Selecting Orders for Return (WRTA) shows you how to use the Select Order for Return Authorization screen to select an order for return authorization through the Work with Return Authorizations menu option.
- Working with Return Authorizations: Standard Process describes how to create or work with a return authorizations using the standard process, which involves creating, receiving, and crediting returns in separate steps.
- Working with Return Authorizations: Streamlined Process describes how to create or work with return authorizations using the streamlined process, which involves automatically processing the return authorization as far as your authority extends.
- Receiving Returns (WRAR) shows you how to receive returns into your warehouse using a separate menu option.
- Crediting Returns (WRAC) shows you how to credit returns using a separate menu option.
- Processing Credits by Line of Business (MCLB) describes how to process credits for a specific line of business and dollar amount.
- Work with Return Interface Errors (WRIE) describes the screens you use to review or delete return records which went into error status when received from an outside return system.
- Inbound Return API describes using the generic returns
API (RETURNS_IN process) to create and process a return against an
order detail line, based on XML messages from an external system.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Receiving Returns (WRAR)
Purpose: Use the Work with Return Authorization Receiving menu option to perform the receipt phase of processing a return authorization. This phase consists of updating the order and posting the receipt into inventory. If the return includes an exchange, the exchange item is added to the order at this time.
Additional uses: You can also use this menu option to review information, or to change settings on the return authorization before processing the receipt. Additionally, you can advance to the Work with Return Authorization Detail Screen.
Note:
This screen is available regardless of whether you use the standard or streamlined process in Work with Return Authorizations.Authority: You must have authority to Enter Return Authorization (A28) and Receive Return Authorization (A29) to use this menu option.
Other options: You can also use the Work with Return Authorizations menu option to perform each step of a return authorization, or you can use order maintenance to perform all steps of the return “behind the scenes.” You might choose to use the Work with Return Authorization Receiving menu option instead of these other options because it allows staff to process a series of receipts efficiently.
Pick slip preparation: When you select a return authorization to receive, the system removes any pick slip preparation from the order. When you accept or reject the return authorization receipt, the system determines if the order qualifies for pick slip preparation and reapplies it to the order. If you add an exchange item to the order, the system performs pick slip preparation for the exchange item when you receive the return authorization. See Preparing Orders for Pick Slip Generation.
In this topic:
For more information: See Introducing Return Authorizations (WRTA) for an overview of return authorizations.
Receive Returns Screen
This screen displays all return authorizations with pending merchandise returns.
How to display this screen: Enter WRAR in the Fast path field of any menu or select this option from a menu.
Field | Description |
---|---|
RA # (Return authorization number) |
A number that identifies the return authorization, order, and shipping address. On this screen, this number is made up of three segments separated by hyphens: Order numberA number to identify an order. Numeric, 7 positions; optional. Ship-to numberThe number of the shipping address on the order. Numeric, 3 positions; optional. Return authorization numberThe number of the return authorization against this order number and shipping address. Returns for the same order number and shipping address will appear as separate return authorizations if they were created separately. See Working with Return Authorizations: Standard Process for more information on return authorization header and detail structure. Numeric, 3 positions; optional. |
Qty entered |
The total quantity of the item(s) being returned on this return authorization. Numeric, 5 positions; display-only. |
Date entered |
The date the return authorization was created. Return authorizations can have multiple lines, each entered on separate dates; if so, the most recent date displays. The date entered appears beneath the quantity entered. Numeric, 6 positions (in user date format); display-only. |
Qty received (Quantity received) |
The total number of units received against the return authorization. Numeric, 5 positions; display-only. |
Date received |
The date that the return authorization line was received. Return authorizations can have multiple lines, each received on separate dates; if so, the most recent date displays. The date received appears beneath the quantity received. Numeric, 6 positions (in user date format); display-only. |
Qty credited (Quantity credited) |
The number of received units for which a credit was issued. Numeric, 5 positions; display-only. |
Date credited |
The date that a credit was issued. Return authorizations can have multiple lines, each credited on separate dates; if so, the most recent date displays. The date credited appears beneath the quantity credited. Numeric, 6 positions (in user date format); display-only. |
Customer number |
This number identifies the customer who placed the order. Scanning on this field is not currently implemented. Numeric, 9 positions; optional. |
Customer name |
The name of the customer. Alphanumeric, 30 positions; display-only. |
Screen Option | Procedure |
---|---|
Receive one or more items |
Select Receive detail for a return authorization to advance to the Work with Return Authorization Detail Screen. |
Receive all returns |
Select Receive all for a return authorization. See Receiving Returned Items. |
Receiving Returned Items
Overview: You can receive returned items through the Receive Returns Screen in the following ways:
- Receive All from First Screen, select Receive all for a return authorization
- Receive Item, select Receive detail for a return authorization to advance to the Work with Return Authorization Detail Screen, where you can select one or more items for receipt
- Receive All from Second Screen, select Receive detail for a return authorization to advance to the Work with Return Authorization Detail Screen, where you can select Receive All to receive all items on the return authorization
Exchange item: You will need to enter an exchange item when processing a receipt if the return has an exchange reason code, and the Require Exchange Item at Time of Receipt (F42) system control value is selected. See Entering an Exchange Item.
Receive All from First Screen
Use this option if you do not need to review the items on the return authorization before processing the receipt.
Select Receive all for a return authorization at the Receive Returns Screen to display the Confirm Accept pop-up window.
If you select OK, all items on the return authorization will be received, and the return authorization will be removed from the Receive Returns screen.
Important:
You cannot undo the receipt once you select OK.Receive Item
Use this option if you would like to review the items on the return authorization before receiving them, to receive one or more individual items, or to change settings on the return before processing the receipt.
- Select Receive detail for a return authorization at the Receive Returns Screen to advance to the Work with Return Authorization Detail Screen.
- Review: Optionally, select Receive detail for any item you would like to review to advance to the RA Exchange Item Window (Review Exchange) and the RA Exchange Item Window (Review Exchange) for an exchange.
- Change: Optionally, select Change for any item you would like to change to advance to the Change RA Detail Screen.
- select Receive all for each item that you want to receive to advance to the Receive RA Items Screen (Receiving Detail).
You can also display this screen by selecting Receive all for an item at the Work with Return Authorization Detail Screen through Working with Return Authorizations: Standard Process.
To complete the Receive RA Items screen: You can change the Quantity returned, Disposition code, Warehouse, or Location fields.
Pop-up windows: If the item does not have a primary location, the system displays an informational pop-up window when you select OK if the Display "No Primary Location" Message in Returns (G46) system control value is selected.
Field descriptions: See Working with Return Authorizations: Standard Process.
Receive All from Second Screen
Use this option if you want to review the items on the return authorization before processing the entire receipt.
- Select Receive detail for a return authorization at the Receive Returns Screen to advance to the Work with Return Authorization Detail Screen.
- Review: Optionally, select Receive detail for any item you would like to review to advance to the RA Exchange Item Window (Review Exchange) and the RA Exchange Item Window (Review Exchange) for an exchange.
- Change: Optionally, select Change for any item you would like to change to advance Change RA Detail Screen.
- Select Receive All to receive all unreceived items on the return authorization. All items are removed from the screen.
- Select Accept to accept your entries; otherwise, Select Reject to cancel.
When you select Accept, you return to the Receive Returns Screen. The receipt for each item is processed, and the return authorization is removed from the screen.
Error message: You cannot process two returns against the same Item Location in a warehouse at the same time. However, if you use the standard process, it is possible to have two returns created that point to the same Item Location, because no updates take place at the time you create the return authorization, only at the time of receipt. For this reason, the screen might display an error message at the time you attempt to receive all the items on a return authorization at once:
Multiple returns not allowed for same Item/Whse/Loc.
To correct, you can change the location to receive one or more of the returns, or process one of the returns completely before processing the other.
Entering an Exchange Item
If the Require Exchange Item at Time of Receipt (F42) system control value is selected, you will need to enter exchange item information for all exchanges when you process the receipt. The Enter Exchange Item Screen or window displays, depending on the steps you took to process the receipt; the fields on both the screen and the window are the same.
If the exchange item you enter is associated with any item comments, you advance to the Work with Item/SKU Comments Window.
Create a Return Authorization/Misship
You can select Create at the Work with Return Authorization Detail Screen in the Work with Return Authorization Receiving menu option to advance to the R/A Select Order Detail Pop-Up Window. At this window, you can:
Standard processing:
- Create new return authorization: If there are additional unreturned items on the order, you can select it and create a new return authorization.
- Enter misship: select Exit at this window to create and receive a misship return.
Streamlined processing: Advance directly to the Create RA Detail Screen. At this screen, you can add a misship item to the return authorization. You cannot create a new return authorization for a shipped item from the order.
About misships: The misship will be created and received when you accept.
Crediting Returns (WRAC)
Purpose: Use the credit return authorization function to process credits for return authorizations that have already been created and received. You can use this menu option regardless of whether you use the standard or streamlined process.
Note:
Misship returns do not display in this menu option, and are not available for crediting.Additional uses: You can also use this menu option to review information on the return authorization before processing the credit.
Authority: You must have authority to create, receive, and credit a return authorization to use this menu option. The Credit Return Authorization (A34) secured feature controls this authority.
Other options: You can also use the Work with Return Authorizations menu option to perform each step of a return authorization. Also, you can use order maintenance to perform all steps of the return "behind the scenes." You might choose to use the Work with Return Authorization Credits menu option instead of these other options because it allows staff to process a series of credits efficiently.
See Introducing Return Authorizations (WRTA) for an overview of return authorizations.
Important:
You cannot change any of the settings on the return authorization through the Work with Return Authorization Credits menu option; instead, you should use Work with Return Authorizations if you wish to make any changes before processing the credit.In this topic:
For more information:
- Working with Return Authorizations: Standard Process
- Working with Return Authorizations: Streamlined Process
First Process RA Credits Screen
This screen displays return authorizations that contain one or more RA detail lines with an uncredited quantity (the quantity returned - the quantity credited is greater than zero).
Use this screen to:
- select a return authorization to credit, either in full or for selected items only
- review additional information about return authorizations that have been received into your warehouse but not yet credited
Each return authorization that has been received but not yet fully credited is listed.
How to display this screen: Enter WRAC in the Fast path field at the top of any menu or select Process Return Authorization Credits from a menu.
Field | Description |
---|---|
RA # (Return authorization number) |
A number that identifies the return authorization, order, and shipping address. On this screen, this number is made up of three segments separated by hyphens: Order numberA number to identify an order. Numeric, 7 positions; optional. Ship-to numberThe number of the shipping address on the order. Numeric, 3 positions; optional. Return authorization numberThe number of the return authorization against this order number and shipping address. Returns for the same order number and shipping address will appear as separate return authorizations if they were processed separately. Numeric, 3 positions; optional. |
Qty entered (Quantity entered) |
The quantity of the item(s) being returned on this return authorization. Numeric, 5 positions; display-only. |
Date entered |
The date the return authorization was created. Return authorizations can have multiple lines, each entered on separate dates; if so, the most recent date displays. The date entered appears beneath the quantity entered. Numeric, 6 positions (in user date format); display-only. |
Qty received (Quantity received) |
The total number of units received against the return authorization. Numeric, 5 positions; display-only. |
Date received |
The date that the return authorization line was received. Return authorizations can have multiple lines, each received on separate dates; if so, the most recent date displays. The date received appears beneath the quantity received. Numeric, 6 positions (in user date format); display-only. |
Qty credited (Quantity credited) |
The number of received units for which a credit was issued. Numeric, 5 positions; display-only. |
Date credited |
The date that a credit was issued. Return authorizations can have multiple lines, each credited on separate dates; if so, the most recent date displays. The date credited appears beneath the quantity credited. Numeric, 6 positions (in user date format); display-only. |
Customer number |
This number identifies the customer who placed the order. Scanning on this field is not currently implemented. Numeric, 9 positions; optional. |
Customer name |
The name of the customer. The customer's name, or company name and contact, appear beneath the customer number. Alphanumeric, 30 positions; display-only. |
Screen Option | Procedure |
---|---|
Credit return authorization detail lines separately |
Select Credit Detail for a return authorization to advance to the Second Process RA Credits Screen. |
Credit the entire return authorization |
Select Credit All for a return authorization to credit all lines on the return authorization. See Processing Credits. |
Second Process RA Credits Screen
Purpose: Use this screen to issue credit for one or more lines returned against an order. This screen displays items that you have received into your warehouse for the return authorization shown. Items on the return authorization but not yet received do not display.
Issuing credit to return authorizations line-by-line enables you to review item detail on the return authorization before selecting which lines to credit.
How to display this screen: Select Credit Detail for a return authorization at the First Process RA Credits Screen. You can also display this screen by selecting a return authorization to credit using Working with Return Authorizations: Standard Process.
Field | Description |
---|---|
RA # (Return authorization number) |
A number that identifies the return authorization, order, and shipping address. On this screen, this number is made up of three segments separated by hyphens: Order number A number to identify an order. Numeric, 7 positions; display-only. Ship-to number The number of the shipping address on the order. Numeric, 3 positions; display-only. Return authorization number The number of the return authorization against this order number and shipping address. Returns for the same order number and shipping address will appear as separate return authorizations if they were processed separately. Numeric, 3 positions; display-only. |
Customer number |
This number identifies the customer who placed the order. Numeric, 9 positions; optional. |
Customer name |
The name of the customer. The customer's name, or company name and contact, appear to the right of the customer number. Alphanumeric, 30 positions; display-only. |
Ln # (Line number) |
The line number on the return authorization. Numeric, 3 positions; optional. |
Item |
A code representing a unit of inventory. Alphanumeric, 12 positions; optional. |
SKU (Stock keeping unit) |
The unique characteristics of an item, such as its size or color. Note: This field appears as one 14-position field; to scan, enter the complete SKU information, separating each SKU element with a space.Alphanumeric, 14 positions; optional. |
Qty rtn'd (Quantity returned) |
The number of units that have been returned to date. Numeric, 5 positions; optional. |
Rtn rsn (Return reason) |
Represents the reason for returning the item. Return reason codes are defined in and validated against the Return Reason table. See Establishing Return Reason Codes (WRTR). Numeric, 3 positions; optional. |
Xch rsn (Exchange reason) |
Represents the reason for exchanging the item. Exchange reason codes are defined in and validated against the Exchange Reason table. See Establishing Exchange Reason Codes (WEXR). Numeric, 3 positions; optional. |
Merchandise value |
The dollar value of the items returned, excluding freight, handling, tax, or additional charges. Numeric, 20 positions with a 2-place decimal; display-only. |
Screen Option | Procedure |
---|---|
Display return authorization detail |
Select Display for a return authorization to advance to the Display RA Detail Screen. |
Credit the return authorization line |
Select Credit Line for a returned item to credit it. See Processing Credits. |
Credit all items on the return |
Select Credit All to credit all displayed items. See Processing Credits. |
Accept your entries |
Select Accept to accept your entries and exit the screen. See Processing Credits. |
Reject your entries |
Select Reject to reject your entries and exit the screen. See Processing Credits. |
Exit the screen and return to the First Process RA Credits Screen |
Select Exit. Note: This option is available only if you have not selected any items on the screen to process; otherwise, you must select Accept or Reject to exit. |
Processing Credits
Overview: You can process credits though the Crediting Returns (WRAC) menu option in the following ways:
- Credit All from First Screen: select Credit Line for a return authorization at the First Process RA Credits Screen
- Credit Item select Credit Line for an item at the Second Process RA Credits Screen
- Credit All from Second Screen: select Credit All at the Second Process RA Credits Screen
Credit All from First Screen
Use this option if you do not need to review the return authorization before crediting.
Select Credit Line for a return authorization at the First Process RA Credits Screen to display the Confirm Accept pop-up window:.
Select OK at this window to process the credit. All received items on the return authorization will be credited, and the return authorization will be removed from the first Process RA Credits screen.
Important:
You cannot undo the credit once you select OK.Credit Item
Use this option if you want to select an individual item (or items) from the return authorization to credit.
- Select Display for a return authorization at the First Process RA Credits Screen to advance to the Second Process RA Credits Screen.
- Optionally, select Display for any item you would like to review to advance to the RA Exchange Item Window (Review Exchange) and the RA Exchange Item Window (Review Exchange) for an exchange.
- Select Credit Line for each item that you want to credit. The item is removed from the screen.
- Select Accept to accept your entries; otherwise, select Reject to cancel.
When you select Accept, you return to the First Process RA Credits Screen. The credit for each selected item is processed, and the return authorization is removed from this screen if all items on the return authorization have been credited.
Credit All from Second Screen
Use this option if you want to review the items on the return authorization before crediting the entire return.
- Select Display for a return authorization at the First Process RA Credits Screen to advance to the Second Process RA Credits Screen.
- Optionally, select Display for any item you would like to review to advance to the RA Exchange Item Window (Review Exchange) and the RA Exchange Item Window (Review Exchange) for an exchange.
- Select Credit All to credit all received items on the return authorization. All items are removed from the screen.
- Select Accept to accept your entries; otherwise, select Reject to cancel.
When you select Accept, you return to the First Process RA Credits Screen. The credit for each item is processed, and the return authorization is removed from the screen.
Processing Credits by Line of Business (MCLB)
Purpose: Use Process Credits by Line of Business to release a batch of credits for a certain line of business and dollar amount.
Note:
In order to process credits by line of business, you must have authority to the Enter Return Authorization (A28), Receive Return Authorization (A29), and Credit Return Authorization (A34) secured features. If you do not have authority to one or all of these secured features, the system displays an error message.When you process credits by line of business and dollar amount, the system selects the oldest credit associated with the line of business first, using the return entered date.
Maximum dollar amount: The system does not know the amount of the credit until the credit is created. Because of this, the system may release a dollar amount that exceeds the maximum dollar amount you specified. Once the system creates a credit that meets or exceeds the dollar amount specified, the system stops crediting, but includes the last credit that caused the dollar amount to go over.
Once the system stops crediting, the system generates the Batch Release Summary Report, which lists the orders associated with the credits released and the dollar amount of each credit.
Process Credits by Line of Business Screen
Purpose: Use this screen to release a batch of credits for a certain line of business and dollar amount.
How to display this screen: Enter MCLB in the Fast path field at the top of any menu or select Process Credits by Line of Business from a menu.
Field | Description |
---|---|
Line of business to credit |
The code for the line of business you wish to credit. The system selects the oldest credit associated with the line of business first, using the return entered date. Line of business codes are defined in and validated against the Line of Business table. See Working with Lines of Business (WLOB). Alphanumeric, 3 positions; required. |
Amount to credit |
The maximum amount you wish to credit for the line of business you selected. The system does not know the amount of the credit until the credit is created. Because of this, the system may release a dollar amount that exceeds the maximum dollar amount you specified. Once the system creates a credit that meets or exceeds the dollar amount specified, the system stops crediting, but includes the last credit that caused the dollar amount to go over. If you leave this field blank, the system processes all available credits for the line of business you selected. Numeric, 10 positions; optional. |
Completing this screen: Select Process Once the CREDITLOB job completes, the system generates the Batch Release Summary Report.
Work with Return Interface Errors (WRIE)
Purpose: Use this menu option to review errors that occurred when processing a return from an external system.
Order Management System can receive returns from an external system through:
- the RETURNS_IN process in Working with Integration Layer Processes (IJCT). See Inbound Return API for an overview.
- the ORDER_IN process in Working with Integration Layer Processes (IJCT). However, the system does not post errors to this menu option. See Generic Order Interface (Order API) for an overview.
- For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
In this topic:
Return Interface Errors
A list of errors that may occur when processing a return from an external system is presented below.
Error description | Reason |
---|---|
Invalid Company |
The company code specified for the return was not a valid Order Management System company code. |
Invalid item/SKU for Order Detail Line |
The item information specified for the return is not located on the specified order line. |
Invalid Loc for Return |
The location for the return or the location associated with the Default Return Disposition Code for Inbound Returns (H65) is not a valid location for the warehouse specified. |
Invalid Order Detail Line |
The system:
|
Invalid Order Header |
The system could not locate an order to return against. |
Invalid Order Ship To |
The system could not locate a ship to order to return against. |
Invalid RA Detail |
The return authorization number for the return does not match the Line # field in the RA Detail table for the specified Order Management System order number, ship to number, and item. |
Invalid RA Header |
The return authorization number for the return does not match a return authorization number for the specified ship to order line. |
Invalid Return Quantity |
The return quantity does not match the quantity available to return for the order line. If you are returning against an RA, the quantity passed must match the quantity to return that was created on the RA. |
Invalid Return Reason |
The return reason specified is not a valid return reason code. Return reason codes are defined in and validated against the Return Reason table. |
Invalid Rtn Disposition |
The return disposition code is blank and a disposition code is not defined in the Default Return Disposition Code for Inbound Returns (H65) system control value. |
Invalid Sales Order Line Number |
The order line number specified does not exist on the specified order. |
Invalid Sales Order Number |
The system could not locate the order to return against. |
Invalid Whs for Return |
The warehouse for the return is not a valid warehouse. |
Line not eligible to be returned - quantity shipped is equal to 0 |
The specified order line has not been shipped. |
Missing Company |
The return did not specify a Order Management System company code. |
Missing Default Charge Code (H64) for misc credit |
A credit amount was specified for the return and an additional charge code was not defined in the Default Additional Charge Code for Inbound Returns (H64) system control value to assign to the charge. |
Missing Return Reason |
The return reason is blank and a return reason code is not defined in the Default Return Reason Code for Inbound Returns (H63) system control value. |
No Active Paytypes |
This message could indicate that the payment method was deactivated for some reason, such as that it is a retail pickup or delivery order. See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for background on retail pickup and delivery orders. |
No primary location defined for item |
The return disposition code specifies to return the item to its primary location and a primary location has not been defined for the item. |
Order Detail line already returned |
The item passed has already been returned for the available quantity. |
Quantity returned exceeds quantity remaining |
The quantity that is available to return on the specified order line is less than the requested quantity to return. |
Quantity returned exceeds quantity shipped |
The quantity shipped on the specified order line is less than the requested quantity to return. |
Return Already Processed |
The quantity available to return against the order line has already been returned and processed. |
Return not allowed for Retail Pickup/Delivery Orders. |
The order specified is a retail pickup or delivery order, and the Suppress Returns for Retail Pickup/Delivery (L88) system control value is selected. See that system control value for background. |
Return not allowed for Ship for Pickup Orders. |
The order specified is a ship-for-pickup order, and the Payment at POS for Ship for Pickup Orders (L60) system control value is selected. See that system control value for background. |
Work with Return Errors Screen
This screen displays all records in the Return Error table (CSRTER). This table is not company-specific; return errors for all companies in an environment display.
How to display this screen: Enter WRIE in the Fast path field at the top of any menu or select Work with Return Errors from a menu.
Field | Description |
---|---|
Co# (company) |
Order Management System company code. Enter the code for any company in the current environment to display return errors in that company. Numeric, 3 positions, optional. |
Item |
A code for item associated with the return. Item codes are defined in and validated against the Item table. Alphanumeric, 12 positions, display-only. |
SKU |
The SKU code for the item associated with the return. Alphanumeric, three 4-position fields; required if the item has SKUs. |
Qty (quantity) |
The number of units of the item being returned. Numeric, 5 positions, display-only. |
Whs (warehouse) |
A code for the warehouse to which the item will be returned, specified on the return authorization, or defaulted from the return disposition code on the return authorization. For returns received from an outside system without a return authorization, the return disposition code may default from system control value Default Return Disposition Code for Inbound Returns (H65). For items with a return disposition code which specifies that the item not be returned to inventory, the warehouse code is 0. Numeric, 3 positions, display-only. |
Location |
The warehouse location to which the item will be returned. Alphanumeric, 7 positions, display-only. |
Order #/Line # |
The order number, ship-to number, and line number of the Order Management System order associated with the return. Order number: numeric, 8 positions, display-only. Ship to number: numeric, 3 positions; display-only. Line number: numeric, 5 positions, display-only. |
Error message (unlabeled field) |
A brief description of the reason for the error. See Return Interface Errors for a list of possible errors. Alphanumeric, 25 positions, display-only. |
Screen option | Procedure |
---|---|
Delete an error record from the Return Error table (CSRTER) |
Select Delete for an error record to delete it. The record will be deleted from the Return Error table and will no longer display on the screen. |
Display return error details |
Select Display for an error record to advance to the Display Return Error Screen. |
Display Return Error Screen
Purpose: Use this screen to review details of a return error record.
How to display this screen: Select Display for an error record at the Work with Return Errors Screen.
Field | Description |
---|---|
Sequence # |
A number assigned by the system to the error record. Sequence numbers are assigned sequentially as errors are received, and are not reassigned when you delete a record. Numeric, 8 positions, display-only. |
Company # |
The code for the company. Numeric, 3 positions, optional. |
Item/SKU |
Item: a code for an existing unit of inventory. Item codes are defined in and validated against the Item table. SKU: a code that further defines an item's color, size, width, or any other type of user-defined attribute. Item: alphanumeric, 12 positions, display-only. SKU: three 4-position fields; display-only if the item has SKUs. |
Return quantity |
The number of units of the item which are being returned. Numeric, 5 positions, display-only. |
Warehouse/Location |
The warehouse and location to which the item will be returned, specified on the return authorization, or defaulted from the return disposition code on the return authorization. For returns received from an outside system without a return authorization, the return disposition code may default from system control value Default Return Disposition Code for Inbound Returns (H65). For items with return disposition code which specifies that the item not be returned to inventory, the warehouse code is 0. Warehouse: numeric, 3 positions, display-only. Location: alphanumeric, 7 positions, display-only. |
Return reason |
The return reason and description for the item, specified on the return authorization. For returns received from an outside system without a return authorization, the return reason code may default from system control value Default Return Reason Code for Inbound Returns (H63). Reason: alphanumeric, 3 positions, display-only. Description: alphanumeric, 30 positions, display-only. |
Return disposition |
The return disposition code and description for the item, specified on the return authorization. The return disposition code determines whether the item being returned will affect inventory, and can specify the warehouse and location where the item will be returned, or that the item will be returned to its primary location. For returns received from an outside system without a return authorization, the return disposition code may default from system control value Default Return Disposition Code for Inbound Returns (H65). Code: alphanumeric, 2 positions, display-only. Description: alphanumeric, 30 positions, display-only. |
Order #/Line # |
The order number, ship-to number, and line number of the sales order. Order number: numeric, 8 positions, display-only. Line number: numeric, 5 positions, display-only. |
RA #/Line # |
A number representing the return authorization, used as a suffix with the order number/ship to number of the order to identify a return authorization. Return authorization number: numeric, 3 positions; display-only. Line number: numeric, 3 positions; display-only. |
Refund freight |
A value indicating whether freight charges on the order will be refunded for a return. Specified on the return authorization. For returns received from an outside system without a return authorization, the Refund freight value may default from system control value Refund Freight Default for Inbound Returns (H59). Alphanumeric, 1 position; display-only. |
Refund handling |
A value indicating whether handling charges on the order will be refunded for a return. Specified on the return authorization. For returns received from an outside system without a return authorization, the Refund handling value may default from system control value Refund Handling Default for Inbound Returns (H61). Alphanumeric, 1 position; display-only. |
Refund charges |
A value indicating whether additional charges on the order will be refunded for a return. Specified on the return authorization. For returns received from an outside system without a return authorization, the Refund charges value may default from system control value Refund Additional Charge Default for Inbound Returns (H60). Alphanumeric, 1 position; display-only. |
Refund duty |
A value indicating whether duty charges on the order will be refunded for a return. Specified on the return authorization. For returns received from an outside system without a return authorization, the Refund duty value may default from system control value Refund Duty Default for Inbound Returns (H62). Alphanumeric, 1 position; display-only. |
Misc credit amount |
A credit amount passed from the outside system. Numeric, 13 positions with a 2-place decimal. |
Called from |
The outside system from which the return was received. |
Error date/time |
The date and time the record in error was received into Order Management System. Date: numeric, 6 positions, in user date format; display-only. Time: numeric, 6 positions, military time HH:MM:SS format; display-only. |
Error message |
A brief description of the reason for the error. See Return Interface Errors for a list of possible errors. Alphanumeric, 25 positions, display-only. |
Issuing Refunds
Topics in this part:
- Introducing the Refund Process presents an overview of the refund process, including a discussion of situations that can cause a refund, refund types and reason codes.
- Printing and Interpreting Refund Due Lists (MRDU) explains how to print the Refund Due List and use this report to verify and document the changes you make to refunds prior to processing.
- Working with Refunds, Writeoffs and Balances Due (WREF) shows you how to research refunds, change a refund's type, place a refund on hold indefinitely or until a specific date, release a refund from hold, or change the refund's status so it will be canceled or written off when you next process refunds.
- Processing Refunds (MREF) shows you how to print and reprint refund checks and process credits and write-offs.
- Printing the Processed Refund Register (PPRR) explains how to generate the Processed Refund Register.
- Processing Refunds by Order Number (MRFO) explains how to generate refunds for selected orders only.
Printing and Interpreting Refund Due Lists (MRDU)
Purpose: The Refund Due List provides information about refunds and the orders associated with these refunds.
Use this report:
- as a guide for contacting customers to resolve outstanding balances due.
- to review refunds before processing refund checks and credits.
- to monitor writeoffs and refund aging.
You can print this report sorted by refund type or by order number:
- Refund Due List by Type. This report sorts refunds by refund type.
- Refund Due List by Order #. This report sorts refunds by order number.
The Selection criteria you define on the Print Refund Due List Screen controls the type of refunds that display on the report.
- All = The report includes all refunds, including balance dues and writeoffs.
- Refunds Only = The report includes refunds, excluding balance dues and writeoffs.
- Balance Dues Only = The report includes balance dues only.
- Writeoffs Only = The report includes writeoffs only.
Identifying a refund as a balance due: The system considers a refund a balance due if the Refund reason field for the refund is set to B (Balance due).
Identifying a refund as a write off: The system considers a refund a write off if the Refund status field for the refund is set to W (Write off pending).
Note:
If a refund is flagged as both a balance due and a write off, the write off setting will take precedence over the balance due setting. In this situation, if you select to generate the report for Balance Dues Only, the system will not include the refund on the report. If you select to generate the report for Writeoffs Only, the system will include the refund on the report.Important:
If you generate the Refund Due List during a time when refunds are being processed, the totals and amounts on the report may not tie out correctly because the refunds that were being processed at the time the report was generated may not be reflected accurately on the report. You should generate the Refund Due List during a time when refunds are not being processed.In this topic:
Print Refund Due List Screen
How to display this screen: Enter MRDU in the Fast path field or select Print Refund Due List from a menu.
Field | Description |
---|---|
By refund type |
Controls whether the system prints the Refund Due List sorted by refund type. Valid values are:
|
By order # |
Controls whether the system prints the Refund Due List sorted by order number. Valid values are:
|
Selection criteria |
Controls the type of refunds included on the Refund Due List. Valid values are:
Identifying a refund as a balance due: The system considers a refund a balance due if the Refund reason field for the refund is set to B (Balance due). Identifying a refund as a write off: The system considers a refund a write off if the Refund status field for the refund is set to W (Write off pending). Note: If a refund is flagged as both a balance due and a write off, the write off setting will take precedence over the balance due setting. In this situation, if you select to generate the report for Balance Dues Only, the system will not include the refund on the report. If you select to generate the report for Writeoffs Only, the system will include the refund on the report. |
Instructions:
- Select the By refund type check box if you wish to generate the Refund Due List by Type, which sorts refunds by refund type.
- Select the By order # check box to generate the Refund Due List by Order #, which sorts refunds by order number.
- You can select both check boxes to generate both versions of the Refund Due List. If you do not select one of the check boxes, the system does not generate the Refund Due List.
- Use the Selection criteria drop down box to select the type of refunds you wish to include on the Refund Due List.
- Select OK to generate the report.
- If you select to generate the Refund Due List by Type or both versions of the Refund Due List, a message similar to the following displays: Job (REFDUE_TYP) has been submitted to batch.
- If you select to generate the Refund Due List by Order #, a message similar to the following displays: Job (REFDUE_ORD) has been submitted to batch.
Working with Refunds, Writeoffs and Balances Due (WREF)
Purpose: Use Work with Refunds to review refunds and change their status or type. For example, you could use this function to:
- place a refund on hold
- cancel a refund to a fraudulent customer
- review a refund record to find out its original payment type
- change a refund from a check to a stored value card refund
- release a held refund for processing
- writeoff an uncollectible balance due from a customer
- advance to Order Inquiry to research an order with a balance due
Order transaction history: The system creates an order transaction history message with a Type of Refund when you change a refund. The table below indicates the order transaction history message the system creates, based on the change made to the refund.
Refund Change | Order Transaction History Note |
---|---|
Place a refund on hold by selecting Hold for a refund |
Refund has been held |
Cancel a refund by selecting Cancel for a refund |
Refund changed to cancel pending |
Release a refund from hold by selecting Release for a refund |
Refund has been released |
Change a writeoff to a refund by selecting Refund for a refund in a pending writeoff status |
Refund chg from writeoff pend to open |
Change a refund to a writeoff by selecting Write off next to a refund |
Refund changed to writeoff pending |
Release all held refunds by selecting Release All Held |
Refund has been released (the system writes this message for each refund that was released from hold) |
Place a refund on manual hold by selecting the Manual hold field on the Change Refund Screen Release a refund from manual hold by deselecting the Manual hold field on the Change Refund Screen |
Refund Manual Hold has been changed |
Enter or update the date in the Hold until date field on the Change Refund Screen Remove the date in the Hold until date field on the Change Refund Screen |
Refund Hold Until Date has been changed |
Change the Pay type field on the Change Refund Screen |
Refund paytype has been changed |
The system also creates an order transaction history message when you process refunds; see Processing Refunds (MREF).
Note:
The system does not create an order transaction history message when the system changes a refund during processing or when you access a refund without making any changes.Sample order transaction history: You can review order transaction history messages on the Display Order History Screen.
Date | Type | Transaction Note | Amount | User |
---|---|---|---|---|
7/31/14 |
REFUND |
Refund has been released |
TBROWN |
In this topic:
- Work with Refunds Screen
- How Pay Type Determines Refund Type
- Change Refund Screen
- Changing the Refund Status
- Work with Refunds By Order# Screen
Work with Refunds Screen
Purpose: After reviewing the Refund Due List, you may need to review or change some refunds before processing. Use the Work with Refunds screen to hold, release, cancel, writeoff, review, or change the type of refund a customer will receive.
Note:
A processed refund remains on this screen until you purge the order containing the refund.How to display this screen: Enter WREF in the Fast path field or select Work with Refunds from a menu.
Refunds display on this screen in ascending refund status sequence; select Display By Order to display refunds in ascending order number sequence; see Work with Refunds By Order# Screen.
Field | Description |
---|---|
Ref Sts (Refund status) |
The current status of the refund. Valid values are:
A second refund status in parentheses indicates that the system will evaluate the first status field when you process refunds and, if appropriate, process the refund based on the second status field. For example, a refund will be released from hold, if appropriate, and written off when you process refunds if it has a status of H (W). Enter a refund status and select OK to display refunds is ascending refund status sequence, beginning with your entry. Alphanumeric, 1 position; optional. |
Order # |
A unique number to identify an order. Enter a valid order number and select OK to display refunds that match your entry. Numeric, 7 positions; optional. |
Ord sts (Order status) |
The current status of the order containing the refund. Valid values are:
Note: As long as a refund's Ord sts = H (that is, the order is held), the refund will not be processed.Alphanumeric, 1 position; display-only. |
Net |
An asterisk indicates whether the refund is eligible for Credit Card Net Exchange Billing. |
Type (Refund type) |
Represents a type of refund. Valid values are:
Select a refund type and select OK to display refunds that match your entry. See How Pay Type Determines Refund Type. Optional. |
Ref date (Refund date) |
The date the transaction that resulted in a refund occurred. Enter a date and select OK to display refunds that match your entry. Numeric, 6 positions (in user date format); optional. |
Trn dt (Refund transaction date) |
The date of the most recent transaction associated with the refund. Enter a date and select OK to display refunds that match your entry. Numeric, 6 positions (in user date format); optional. |
Hold |
Indicates whether the refund is on hold. A refund may be on hold because:
Valid values are:
Select Yes or No and select OK to display refunds that match your entry. |
Hold date (Hold until date) |
The date when the system will release a refund from hold. Enter a date and select OK to display refunds that match your entry. Numeric, 6 positions (in user date format); optional. |
Reason (Refund reason) |
The reason for the refund. Valid values are:
Enter a reason code and select OK to display refunds that match your entry. Alphanumeric, 1 position; optional; assigned by the system. |
Amount |
The dollar amount to be refunded. The tax amount included in the refund amount is based on the tax rate that was effective when the item was shipped. A negative sign indicates a balance due from the customer. If you accept orders in foreign currencies, the system displays the amount in the foreign currency indicated by the Bank code. Enter an amount and select OK to display refunds whose amount is equal to or greater than your entry. Numeric, 13 positions with a 2-place decimal; optional. |
Bank |
The bank associated with the source code on the order. You associate a source code with a bank by specifying a division when you create the source code, because each division is associated with a bank. When you generate refund checks, the system uses the next check number indicated for the bank in the Bank table. See Working with Banks (WBNK). If the Multi Currency by Offer (E03) system control value is selected, you must define the currency to be used for each offer. Each currency you define on the system must be associated with a unique bank, so the bank code that appears on this screen indicates the currency of the order. If you use multi currency, the prices and other amounts on an order appear in the currency of the offer, but the system converts the figures into your local currency for order billing history. Similarly, the refund amount indicated is in the currency used on the order, indicated by the bank code. When you process the refund, the system uses the currency conversion rate that was in effect when the order was billed. Enter a bank code and select OK to display refunds that match your entry. Alphanumeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Change a refund record |
Select Change for a refund to advance to the Change Refund Screen. |
Place a refund on hold |
Select Hold for the refund. See Changing the Refund Status. |
Cancel a refund |
Select Cancel for the refund. See Changing the Refund Status. |
Display a refund |
Select Display for a refund to advance to the Display Refund Screen. You cannot change any information on this screen. See Change Refund Screen for field descriptions. |
Release a refund from hold |
Select Release for the refund. See Changing the Refund Status. |
Change a writeoff to a refund |
Select Write Off for the refund in pending writeoff status. See Changing the Refund Status. |
Change a refund to a writeoff |
Select Refund for the refund. See Changing the Refund Status. |
Advance to Order Inquiry for the order containing the refund |
Select Ord Inq for a refund. |
Display refunds in ascending order number sequence |
Select Display By Order to advance to the Work with Refunds By Order# Screen. Note: If you advance to this screen and select Exit, the system returns you to the main window and not the Work with Refunds Screen. |
Release all held refunds |
Select Release all held. See Changing the Refund Status. |
Print the Refund Due List |
Select Print list. |
How Pay Type Determines Refund Type
Overview: The pay type that a customer uses on an order determines the type of refund received, depending on how you have defined the pay type.
Payment category: When you create a pay type, you must assign it to one of five payment categories. Each payment category automatically produces a certain refund type, as follows.
Payment Category | Produces Refund Type |
---|---|
Cash/check (1) |
Check |
Credit card (2) |
Credit card credit |
See the field descriptions at the Change Refund Screen for more information on each of the refund types.
Alternate refund type: When you define an alternate refund type for a pay type, the system automatically generates refunds of the alternate refund type.
The system accepts only stored value card or cash/check alternate refund types.
Alternate refund category: When you define an alternate refund category for a pay type, you give yourself the option of changing the refund to the type that corresponds to this category.
The system accepts only cash/check alternate refund categories. However, you can change any type of refund to a stored value card credit at the Change Refund Screen.
Stored Value Card Refunds
The system generates a stored value card refund when:
- The alternate refund type defined for a pay type is a stored value card.
- You process a return outside the Return Grace Period (B52) and the Alternate Pay Type (B51) is a stored value card pay type.
- You change a refund to a stored value card refund in Work with Refunds (WREF).
Note:
If you process a return against a stored value card pay type that does not have an alternate pay type or alternate refund category defined, the system generates a credit card credit refund against the original stored value card pay type, allowing you to reimburse the original stored value card instead of sending the customer a new card. However if the customer no longer has the original stored value card, you can change the credit card credit refund to a stored value card refund by changing the Type field on the Change Refund Screen to V (stored value card refund); by doing this, the system sends a new stored value card to the customer for the refund amount.For more information: See Generating Stored Value Card Refunds for an overview and required setup.
Changing a Refund
You can change a refund at the Change Refund Screen by entering a new pay type in the Pay type field. If you do this, the system updates the refund type based on the pay category of the new pay type. For example, if you change the pay type to a check pay type, the system updates the refund type to Check Credit.
The system allows you to change the original pay type defined for the refund to another pay type, if:
- The new pay type is the same pay category as the original pay type associated with the refund. For example, if the original pay type is a credit card pay type, the system allows you to change the pay type to another credit card pay type. In this example, the refund type does not change.
- The new pay type is the same pay category as the alternate refund type defined for the original pay type associated with the refund. For example, if the original pay type is a credit card with an alternate pay type of cash/check, the system allows you to enter a cash/check pay type in the Pay type field. In this example, the refund type changes based on the pay category of the pay type.
- The new pay type is the same pay category as the alternate refund category defined for the original pay type associated with the refund. For example, if the original pay type is a credit card with an alternate pay category of cash/check, the system allows you to enter a cash/check pay type in the Pay type field.
- The new pay type is a stored value card pay type. In this scenario, the system updates the refund type to V (stored value card).
Eligible refund changes: The table below indicates the type of pay type you can enter in the Pay type field, based on the original pay type (and its alternate refund type/category) associated with refund.
Note:
You can always change the pay type defined for the refund to a stored value card pay type; this updates the refund type to V (stored value card credit)If original pay type is: | And alternate refund type or category is: | You can change the pay type defined for the refund to: |
---|---|---|
cash check |
blank or cash/check |
cash/check pay type (refund type Check Credit) |
credit card |
blank |
original pay type for the refund (refund type CC Credit) |
cash/check |
original pay type for the refund (refund type CC Credit) cash/check pay type (refund type Check Credit) |
|
Note: The system does not allow you to change a credit card credit to another credit card pay type. |
Stored value card pay types: If the original pay category and current pay category associated with the refund is a stored value card pay type (pay category Credit Card) and Card type Stored Value), the system allows you to change the refund by entering a different refund type in the Type field. You can only change the refund type to a credit card credit or stored value card credit.
- If the refund is a credit card credit, the system adds the refund amount to the original stored value card on the order.
- If the refund is a stored value card credit, the system generates a new stored value card for the refund amount.
Change Refund Screen
Purpose: Use this screen to review a refund, change the type of refund, place a refund on hold, release a refund from hold, or enter a date on which to release the refund from hold.
To change a refund: See Changing a Refund for an explanation of the options available when changing a refund.
To place a refund on hold: Select the Hold field and optionally, enter a date in the Hold until date field. If you enter a hold until date, the system automatically releases the refund from hold on that date.
To release a refund from manual hold: Deselect the Hold field.
How to display this screen: Select Change for a refund at the Work with Refunds Screen.
Note:
You cannot change a refund once it has been processed.Field | Description |
---|---|
Order # |
A unique number the system assigns to identify an order. Numeric, 7 positions; display-only. |
Sold to (Sold to customer number) |
The number of the customer or company that placed the order. The customer's or company's name appears as an unlabeled field to the right of the customer number. Numeric, 9 positions; display-only. |
Bill to (Bill-to customer number) |
The number of the customer or company responsible for paying for the order. The bill-to customer number appears only if there is a bill-to customer associated with the order producing the refund; in this situation, the refund check will be generated for the bill-to customer rather than the sold-to customer. The bill-to customer's and/or company's name appears as an unlabeled field to the right of the bill-to customer number. Numeric, 7 positions; display-only. |
Amount |
The dollar amount to be refunded. The tax amount included in the refund amount is based on the tax rate that was effective when the item was shipped. A negative sign indicates a balance due. Numeric, 20 positions with a 2-place decimal; display-only. |
*NET BILLING |
The text *NET BILLING displays to the right of the Amount if the refund is associated with Credit Card Net Exchange Billing. In this situation, the Pay type field is display-only on this screen. |
Status (Refund status) |
The current status of the refund. Valid values are:
The description associated with the status appears as an unlabeled field to the right. Display-only. |
Type (Refund type) |
Represents the kind of refund the customer will receive. The description associated with the type appears as an unlabeled field to the right. Valid values are:
The system allows you to change the refund by entering a pay type in the Pay type field; see Changing a Refund. See How Pay Type Determines Refund Type. Display-only. |
Manual hold |
Indicates whether the refund is on hold because:
Valid values are:
|
Hold until date |
The date when the system will release a refund from hold. Note: Entering a date in this field does not by itself hold the refund; the refund status must be Held or the value in the Manual hold field must be selected to hold the refund until this date.Numeric, 6 positions (in user date format); optional. |
Current category |
The current payment category of the refund. The current category may change if you change the pay type of the refund. See the description of the Pay type field. Valid values are:
Display-only. |
Original category |
The category of the payment type used on the order. May differ from the current category if there is an alternate refund type or alternate refund category. Valid values are:
Display-only. |
Refund date |
The date when the transaction that resulted in a refund occurred. Numeric, 6 positions (in user date format); display-only. |
Trans date (Transaction date) |
The date of the most recent transaction associated with the refund. Numeric, 6 positions (in user date format); display-only. |
Refund reason |
Identifies the reason for the refund. Valid values are:
Display-only. |
Pay type |
A code for the payment method of the refund. Pay types are defined in and validated against the Pay Type table. See Working with Pay Types (WPAY). The system creates the refund in the same pay type used on the order. However, if an Alternate refund type is defined for that pay type, the system creates the refund in the alternate type. The system allows you to change the pay type of the refund to another pay type; see Changing a Refund for the available options. The description associated with the pay type appears as an unlabeled field to the right. Note: This field is display-only if the refund is associated with Credit Card Net Exchange Billing (the text *NET BILLING displays to the right of the Amount field).Numeric, 2 positions; optional. |
RA# (Return authorization number) |
The number the system assigns to a return authorization on an order. You can create a return authorization in Order Maintenance when you are expecting a customer to return an item. Using return authorizations help you control of the process of receiving and crediting returns. A value other than zero appears here if a return authorization caused the refund. Numeric, 3 positions; display-only. |
Changing the Refund Status
How to change the status of a refund: To change the status of a refund, enter the appropriate option number next to the refund at the Work with Refunds Screen. Each option number works with only certain refund statuses. The table below outlines valid combinations. If you attempt an invalid status change, the system displays an error message.
Process | Option | Works on current status of | Result |
---|---|---|---|
Hold refund |
Hold |
O (open) N (cancel pending) |
The Ref sts (refund status) field changes to H to indicate that the refund is held; it now appears in order number sequence among held refunds. The Manual hold field changes to selected. The refund will not be affected the next time you process refunds. |
Cancel refund |
Cancel |
H (held) O (open) W (writeoff pending) |
The Ref sts (refund status) field changes to unselected to indicate that a cancel is pending; the refund now appears in order number sequence among refunds pending cancellation. The refund will be canceled the next time you process refunds. |
Release refund |
Release |
H (held) N (cancel pending) |
The Ref sts (refund status) field changes to O to indicate that the refund is open for processing; it now appears in order number sequence among open refunds The refund will be processed the next time you process refunds.3 |
Change writeoff to refund |
Writeoff |
W (writeoff pending)1 |
The Ref sts (refund status) field changes to O to indicate that the refund is open for processing; it now appears in order number sequence among open refunds The refund will be processed the next time you process refunds. |
Writeoff a refund |
Refund |
H (held N (cancel pending) O (open)2 |
The Ref sts (refund status) field changes to W to indicate that a writeoff is pending on the refund; the record now appears in order number sequence among pending writeoffs The refund will be written off the next time you process refunds |
1 Writeoffs must have a positive refund amount to be changed to refunds.
2 Refunds must be prepaid payment types to be written off.
3 A refund will remain on hold as long as the order containing the refund is on hold (Ord sts = H)
Release all held refunds: You can also release all held refunds at once by selecting Release all held. The system displays a pop-up window indicating that held refunds are about to be released.
Work with Refunds By Order# Screen
Purpose: Use this screen to review and work with refunds in ascending order number sequence.
Note:
To review and work with refunds in ascending refund status sequence, use the Work with Refunds Screen.Note:
A processed refund remains on this screen until you purge the order containing the refund.How to display this screen: Select Display By Order on the Work with Refunds Screen.
Field | Description |
---|---|
Ref Sts (Refund status) |
The current status of the refund. Valid values are:
A second refund status in parentheses indicates that the system will evaluate the first status field when you process refunds and, if appropriate, process the refund based on the second status field. For example, a refund will be released from hold, if appropriate, and written off when you process refunds if it has a status of H (W). Alphanumeric, 1 position; display-only. |
Order # |
A unique number to identify an order. Enter a valid order number and select OK to display refunds in ascending order number sequence, beginning with your entry. Numeric, 7 positions; optional. |
Ord sts (Order status) |
The current status of the order containing the refund. Valid values are:
Note: As long as a refund's Ord sts = H (that is, the order is held), the refund will not be processed.Alphanumeric, 1 position; display-only. |
Net |
An asterisk indicates whether the refund is eligible for Credit Card Net Exchange Billing. |
Type (Refund type) |
Represents a type of refund. Valid values are:
Select a refund type and select OK to display refunds that match your entry. See How Pay Type Determines Refund Type. Optional. |
Ref date (Refund date) |
The date the transaction that resulted in a refund occurred. Enter a date and select OK to display refunds that match your entry. Numeric, 6 positions (in user date format); optional. |
Trn dt (Refund transaction date) |
The date of the most recent transaction associated with the refund. Enter a date and select OK to display refunds that match your entry. Numeric, 6 positions (in user date format); optional. |
Hold |
Indicates whether the refund is on hold. A refund may be on hold because:
Valid values are:
Select Yes or No and select OK to display refunds that match your entry. |
Hold date (Hold until date) |
The date when the system will release a refund from hold. Enter a date and select OK to display refunds that match your entry. Numeric, 6 positions (in user date format); optional. |
Reason (Refund reason) |
The reason for the refund. Valid values are:
Enter a reason code and select OK to display refunds that match your entry. Alphanumeric, 1 position; optional; assigned by the system. |
Amount |
The dollar amount to be refunded. The tax amount included in the refund amount is based on the tax rate that was effective when the item was shipped. A negative sign indicates a balance due from the customer. If you accept orders in foreign currencies, the system displays the amount in the foreign currency indicated by the Bank code. Enter an amount and select OK to display refunds whose amount is equal to or greater than your entry. Numeric, 13 positions with a 2-place decimal; optional. |
Bank |
The bank associated with the source code on the order. You associate a source code with a bank by specifying a division when you create the source code, because each division is associated with a bank. When you generate refund checks, the system uses the next check number indicated for the bank in the Bank table. See Working with Banks (WBNK). If the Multi Currency by Offer (E03) system control value is selected, you must define the currency to be used for each offer. Each currency you define on the system must be associated with a unique bank, so the bank code that appears on this screen indicates the currency of the order. |
If you use multi currency, the prices and other amounts on an order appear in the currency of the offer, but the system converts the figures into your local currency for order billing history. Similarly, the refund amount indicated is in the currency used on the order, indicated by the bank code. When you process the refund, the system uses the currency conversion rate that was in effect when the order was billed. Enter a bank code and select OK to display refunds that match your entry. Alphanumeric, 3 positions; optional. |
Screen Option | Procedure |
---|---|
Change a refund record |
Select Change for a refund to advance to the Change Refund Screen. |
Place a refund on hold |
Select Hold for the refund. See Changing the Refund Status. |
Cancel a refund |
Select Cancel for the refund. See Changing the Refund Status. |
Display a refund |
Select Display for a refund to advance to the Display Refund Screen. You cannot change any information on this screen. See Change Refund Screen for field descriptions. |
Release a refund from hold |
Select Release for the refund. See Changing the Refund Status. |
Change a writeoff to a refund |
Select Write Off for the refund in pending writeoff status. See Changing the Refund Status. |
Change a refund to a writeoff |
Select Refund for the refund. See Changing the Refund Status. |
Advance to Order Inquiry for the order containing the refund |
Select Ord Inq for a refund. |
Print the Refund Due List |
Select Print list. |
Processing Refunds (MREF)
Purpose: Use the Process Refunds function to:
- print refund checks
- generate credit card credits, including credits to a stored value card
- process writeoffs
- process refund cancellations
- print credit card credit acknowledgements and/or generate email notices
- generate stored value card credits (issue a new stored value card for the credit amount)
You can process any one refund type or a combination of refund types. You can also process all open refunds of a selected type, or you can specify a dollar limit to process for each. The function generates a register for each refund type and for writeoffs, including amounts, customer names, and order numbers. At this time, any refunds in unselected (cancel pending) status will be canceled, but no report is produced.
Which orders and refunds are eligible for processing? To determine whether to process a refund for an order, or to cancel or writeoff the refund if appropriate, the system checks:
- order status: The Ord sts (Order status) must be open, closed (X), or canceled (C). The system will not generate a refund if the order is held (H), or suspended (S).
- refund status: The Ref Sts (Refund status) must be open (O), cancel pending (N), or writeoff pending (W). The refund status cannot be held (H), processed (P), canceled (C) or written off (T). If the refund has a separate status in parentheses (for example, O (H)), then the status in parentheses applies.
- manual hold: If the Manual hold flag for the refund is selected, the refund will not be processed.
- bank: The order must have the same Bank as the one you specify at the Process Refunds Screen.
If there is more than one refund eligible for processing on a single order, all eligible refunds will be processed.
Generating refunds for selected orders: You can use the Process Refunds by Order Screen to generate refunds for selected orders only. See Processing Refunds by Order Number (MRFO).
Multiple currency by offer: If you use Multiple Currencies by Offer, each refund you generate will be in the currency used on the order.
Suppressing refunds: You can suppress refund processing:
- For orders you receive through the Generic Order Interface (Order API). In this situation, the refund is generated in a N (cancel pending) status. See Suppressing Deposits and Refunds for an overview.
- For orders associated with a return you receive through the Inbound Return API. In this situation, the refund is generated in a N (cancel pending) status. See Suppressing Refunds for an overview.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
ChannelAdvisor refunds: If any of the refunds eligible for processing are for orders whose order type matches the ChannelAdvisor Order Type (L90), the refund generation program submits a refund request to ChannelAdvisor and does not actually generate the refund. See ChannelAdvisor Integration Overview for more information, especially Submitting Refunds for ChannelAdvisor Orders.
In this topic:
- Multiple Currencies by Offer
- Refund Check Messages
- Process Refunds Screen
- Summary of Refund Processing Updates and Reports
- Refund Reports and Standard Programs
- Refund Check
- Refund Check Register
- Refund Writeoff Register
- Credit Card Credit Acknowledgment
- Credit Card Credit Register
For more information: See Reprint Refunds Screen (MREP).
Not in this topic: This topic does not explain how different types of refunds are generated or how you evaluate and change refunds before processing them. See Printing and Interpreting Refund Due Lists (MRDU), and Working with Refunds, Writeoffs and Balances Due (WREF).
Multiple Currencies by Offer
If you take orders in multiple currencies, then you will need to process refunds in these currencies as well. When you process refunds, you must indicate the bank code; since each currency is associated with a unique bank, this tells the system the currency of the refunds to generate. You can process refunds for only one currency at a time. (To take orders in multiple currencies, you must have the Multi Currency by Offer (E03) system control value selected.)
The dollar limit for foreign currencies: You can specify a dollar limit for each refund type if you are generating refunds in a foreign currency. The system interprets the limit in your local currency, but generates refunds in the foreign currency. For example, your local currency is U.S. dollars, and you are generating refund checks to your Canadian customers. You specify a dollar limit of $1,000. The system uses the currency conversion rate in effect for each order at the time it was billed to calculate each refund amount in U.S. dollars. The first refund, for $50 in Canadian currency, was on an order billed at a currency conversion rate of 1.29. The system calculates the value of the refund in your local currency as $38.76 (50/1.29). This leaves a maximum of $961.24, converted into your local currency, left to generate.
The system continues to process refunds in chronological order by refund date, stopping before it exceeds the dollar limit you defined in your local currency. The refund checks, however, will always be in the currency used on the order.
Refund Check Messages
You can enter up to three message lines to print on a refund check if your refund check print program supports them. You specify the print program in the Refund Check Print Program (D23) system control value. The base print program is REFCHECK.
To enter messages, you use the Work with Order Messages Screen, available by selecting Messages in order entry, order maintenance, or standard or streamlined order inquiry.
Process Refunds Screen
Purpose: Use this screen to process:
- refund checks
- credit card credits
- stored value card credits
- writeoffs
How to display this screen: Enter MREF in the Fast path field or select Process Refunds from a menu.
Field | Description |
---|---|
Generate refund checks |
Determines whether to generate refund checks; see Refund Check for a sample and a description of its contents. Valid values are:
The system produces the Refund Check Register. The system also prints checks for refunds that are eligible for processing and have a check refund type. Refund checks are written to the Refund Reconciliation table. |
Amount to generate (Refund check amount to generate) |
The maximum total dollar amount that you want to disburse in refund checks. The system prints checks for all eligible refunds in ascending chronological order based on refund date, and stops before exceeding this amount. If you are processing refunds in a foreign currency, the system evaluates the amount to generate in your local currency by converting the refund amount, using the conversion rate in effect when you billed the order. The refund check, however, will be in the foreign currency. If you leave this field blank, the system processes all eligible refund checks. Numeric, 10 positions; optional. |
Bank |
The bank associated with the source code on the order. You associate a bank with a source code by selecting a division for the source code; each division is associated with a bank. The system determines the next sequential check number to use by adding 1 to the Last check number defined in the Bank table. If you process orders in multiple currencies, the bank also indicates the currency of the refunds, since each currency on your system is associated with a unique bank. The bank you specify at this screen indicates the currency of all refund checks, credits, or writeoffs that you process at this screen. Bank codes are defined in and validated against the Bank table. See Working with Banks (WBNK). Alphanumeric, 3 positions; required. |
Generate credit card credits |
Determines whether to generate refunds in the form of credit card credits. This setting includes refunds to a stored value card where the credit amount is applied back to the original stored value card; to issue a new stored value card for the credit amount you must use the Generate SVC credits option. Valid values are:
Select this field to process credit card credits. The system generates a Credit Card Credit Register that identifies the amount, customer name, and order number of each credit processed. The system also produces either a Credit Card Credit Acknowledgment (if the Print Credit Card Credit Acknowledgments (C35) system control value is selected) or an email notification when the Credit Card Credit Acknowledgement E-Mail Program (H08) is set to CCCNOTF, (regardless of the setting of the Print Credit Card Credit Acknowledgments (C35) value) for each credit as appropriate; see When Does the System Generate an Email Notification? Email template: You can use the Working with Entities (WENT) menu option to create an entity-level email template, and the Working with E-Mail Notification Templates (WEMT) menu option to create a default company-level credit card credit template. The template specifies the text to print above and below the standard credit card credit information. Note: If the XML Only checkbox is selected, the Sample Credit Card Credit Acknowledgement XML Message is generated and the system does not create an email.For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). The system does not process a credit card credit against an installment or deferred billing order before the deposit has been processed. This ensures that you do not credit the customer's credit card before the card has been charged. Note: Sales Journal and deposit summary records may differ depending on how often you process credit card credits.Scheduling: You can schedule the generation of credit card credits using the REFCCCR Process Credit Card Credit Refunds periodic function. |
Amount to generate (Credit card credit amount to generate) |
The maximum total dollar amount that you want to process in credit card credits. The system issues credits for all eligible refunds in ascending chronological order based on refund date, and stops before exceeding this amount. If you are processing refunds in a foreign currency, the system evaluates the amount to generate in your local currency by converting the refund amount, using the conversion rate in effect when you billed the order. The credit, however, will be in the foreign currency. If you leave this field blank, the system processes all eligible credit card credits. Numeric, 10 positions; optional. |
Generate SVC credits |
Determines whether to generate stored value card credits. Valid values are:
When you generate stored value card credits, the system issues a new stored value card to the sold to customer for the refund amount. The system:
You can then follow the normal process of activating, billing, and shipping the stored value card to the customer. See Generating Stored Value Card Refunds for an overview. Scheduling: You can schedule the generation of stored value card credits using the REFSVCR Process SVC Credit Refunds periodic function. |
Note: The system can process stored value cards in the US currency only. If the order is for a currency other than US, you should generate a refund type other than stored value card for the order.The Process Refunds Screen displays an error message if you select to generate stored value card credits and the Default SVC Refund Item Number (I73) and/or Price Override Reason for SVC Refund Item (I74) system control values are unselected: Sys Con Values I73 & I74 must be populated first. |
|
Amount to generate (Stored value card credit amount to generate) |
The maximum total dollar amount that you want to process in stored value card refunds. The system issues credits for all eligible refunds in ascending chronological order based on refund date, and stops before exceeding this amount. Note: Stored value cards are only allowed in US currency.If you leave this field blank, the system processes all eligible stored value card credits. Numeric, 10 positions; optional. |
Process writeoffs |
Determines whether the system processes refunds to be written off. Valid values are:
The system produces the Refund Writeoff Register. The system updates the writeoff amount for the customer. You can apply positive writeoff balances as credits and negative writeoff balances as charges against a new order placed by the customer. |
Prior to date |
Enter a date to specify that only writeoffs with a Refund created date earlier than the date you enter will be processed. If you leave this field blank, the system will process all refunds to be written off. |
Instructions:
- Select the Generate refund field for each type of refund you want to process.
- Enter maximum amounts for each type of refund, if needed.
- Specify the bank code associated with the refunds you wish to generate.
- If you are processing refund checks, a pop-up window appears displaying the next available check number. You can accept the check number displayed, change the check number, or select Exit to close the window and cancel the action.
- If you are generating unlimited credit card credits, a pop-up window displays confirming that you are not restricting these credits to a specific dollar amount. Again, you can accept or select Exit to close the window and cancel the action.
- The system submits the batch job REF_PROC, which processes the refunds up to the specified dollar limits.
Note:
The system displays an error message if you select to generate stored value card credits and the Default SVC Refund Item Number (I73) and/or Price Override Reason for SVC Refund Item (I74) system control values are unselected: Sys Con Values I73 & I74 must be populated first; see Generating Stored Value Card Refunds.Summary of Refund Processing Updates and Reports
Update refunds: The status of each refund is updated, as well as the Trn dt (Refund transaction date).
Update order history: The system writes a message to the Order History table for each order being refunded such as the following:
- refund check: 7/20/06 F Refund check# 212 created 49.50 EJOHNSON
- writeoff: 7/20/06 F Refund type K has been cancelled 17.48- EJOHNSON
- credit card credit: 7/20/06 F CC Crd for inv# 3918 processed 52.50 EJOHNSON. If the credit card credit generates an email notification, the system also writes: 7/20/06 L C/C Ack to ejohnson@example.com.
- stored value card credit: 5/27/06 F Stored Value Card refund created 12.99 KBROWN
You can review Order History at the Display Order History Screen, available in standard order inquiry. This information is also available in streamlined order inquiry by selecting History.
Checks, registers, and acknowledgements: Depending on your selections, this job produces the:
- Refund Check
- Refund Check Register
- Refund Writeoff Register
- Credit Card Credit Acknowledgment (Note: The acknowledgment can also be sent by email; see When Does the System Generate an Email Notification?)
- Credit Card Credit Register
- Stored Value Card Credit Register
The system does not generate a register of canceled refunds.
ChannelAdvisor: See Submitting Refunds for ChannelAdvisor Orders for an overview of the refund process for ChannelAdvisor orders.
For more information: See Refund Reports and Standard Programs.
Refund Reports and Standard Programs
Purpose: The reports and print programs related to refunds, the standard program values, and the system control values you use to define them, are:
Report | Standard Program | System Control Value Name (Value) |
---|---|---|
Checks | ||
REFCHECK |
Refund Check Print Program (D23) (program name) |
|
CSR0385 |
||
Writeoffs | ||
CSR0390 |
||
Credit Cards | ||
CSR0559 |
Credit Card Credit Acknowledgment Print Program (D22) (program name) Print Credit Card Credit Acknowledgments (C35) (Selected/Unselected) |
|
Credit Card Credit Acknowledgement Email |
CSR0258 |
Credit Card Credit Acknowledgement E-Mail Program (H08) (program name) Note: The Print Credit Card Credit Acknowledgments (C35) system control value does not control email acknowledgments. |
CSR0397 |
||
Stored Value Card Register |
CSR1405 |
Reprint Refunds Screen (MREP)
Purpose: Use this screen when you encounter a problem printing refund checks or credits and you need to reprint them.
Note:
Because the reprint program uses information from the Check Reconciliation table, the reprint process picks up only unreconciled, unvoided checks within the check range you specify.How to display this screen: Enter MREP in the Fast path field at the top of any menu or select this option from a menu.
Field | Description |
---|---|
Check # (Check number) |
The check numbers of the first and last checks to reprint. From The check number of the first check to reprint. Numeric, 7 positions; optional. To The check number of the last check to reprint. Numeric, 7 positions; optional. New # Indicates whether to assign new check numbers to the reprinted checks/credits or use the same check numbers again. |
Valid values are:
The system does not reprint voided check numbers. |
|
New # (New check number) |
Indicates whether to assign a new check number to the reprinted check. Valid values are:
|
Bank # (Bank) |
The bank associated with the source code used on the orders. Bank codes are defined in and validated against the Bank table. See Working with Banks (WBNK). Alphanumeric, 3 positions; required. |
Completing this screen: If you select checks, a pop-up window appears displaying the next available check number. You can accept the check number, change the number, or select Exit to close the window and cancel the action. The system submits a batch job called REF_RPRT. This program reprints all the refunds you have specified. See Refund Reports and Standard Programs.
The system also writes a message to the Order History table that identifies the original check number, a reprint message, and the new check number, if applicable. You can view Order History through standard or streamlined order inquiry.
Reconciling Checks (MREC)
Purpose: Each refund check you print produces a record in the Refund Reconciliation table. You can use the Work with Check Reconciliation function to:
- reconcile refund checks that you receive back from the bank
- void refund checks in order to write them off
- void refund checks so that you can issue new refund checks
- unreconcile refund checks that were reconciled in error
In this topic:
- Work with Check Reconciliation Screen
- Display Check Screen
- Reconciling and Unreconciling Checks
- Correcting Refund Check Errors
- Print Reconcile List Prompt Screen
- Check Reconciliation List
- Check Reconciliation List by Bank
For more information: See Purge Refund Checks Screen (MPRF).
Work with Check Reconciliation Screen
Purpose: Use this screen to display, reconcile, unreconcile, writeoff, void or reinstate refund checks. This screen lists all refund checks. Reconciled, voided and written off refunds remain on this screen until you use the Purge Refund Checks Screen (MPRF).
How to display this screen: Enter MREC in the Fast path field at the top of any menu or select Work with Check Reconciliation from a menu.
Field | Description |
---|---|
Bank |
The bank associated with the source code on the order. You associate a source code with a bank through its division. If you process orders in multiple currencies, the bank indicates the currency of the refund check, since each currency on your system is associated with a unique bank. Bank codes are defined in and validated against the Bank table. See Working with Banks (WBNK). Alphanumeric, 3 positions; optional. |
Check number |
The number of the refund check. Numeric, 7 positions; optional. |
Chk Dt (Check date) |
The date the system generated the refund check. Numeric, 6 positions (in user date format); optional. |
Amount |
The amount of the refund check. If you process orders in multiple currencies, this amount is in the currency used on the order. Numeric, 13 positions with a 2-place decimal; optional. |
Recon (Date reconciled) |
The date you reconciled the check. Reconciliation does not necessarily occur the same day you receive the check from the bank. Numeric, 6 positions (in user date format); optional. |
Voided |
The date you voided the refund check. Numeric, 6 positions (in user date format); optional. |
Customer name |
The name of the customer to receive the refund. Alphanumeric, 25 positions; display-only. |
Screen Option | Procedure |
---|---|
Display a refund |
Select Display for a refund to advance to the Display Check Screen. |
Reconcile a refund check |
Select Reconcile for the refund to reconcile the check. See Reconciling and Unreconciling Checks. |
Unreconcile a refund |
Select Unreconcile for the refund to unreconcile the check. See Reconciling and Unreconciling Checks. |
Void/writeoff a refund |
Select Void/Write-off for a refund to void/writeoff the refund. See Correcting Refund Check Errors. |
Void/reinstate a refund |
Select Void/Reinstate for a voided refund to reinstate the refund. See Correcting Refund Check Errors. |
Display refunds by check date or by check number |
Select By Check Date to display the refunds in ascending order by check date. Select By Check Date again to display refunds in ascending order by check number. |
Reconcile by check or date range |
Select Batch Reconcile to reconcile refunds by check or date range. See Reconciling and Unreconciling Checks. |
Print a list of refunds |
Select Print List to advance to the Print Reconcile List Prompt Screen. |
Display Check Screen
Purpose: Use this screen to review the details of a refund check.
How to display this screen: At the Work with Check Reconciliation Screen, select Display for the check you want to review.
Field | Description |
---|---|
Check number |
The number of the refund check. Numeric, 7 positions; display-only, assigned by the system. |
Amount |
The total dollar amount of the refund. If you take orders in multiple currencies, the amount is in the currency used on the order. Numeric, 20 positions with a 2-place decimal; display-only. |
Date printed |
The date you printed the refund check. Numeric, 6 positions (in user date format); display-only. |
Date voided |
The date you voided the refund check. Numeric, 6 positions (in user date format); display-only. |
Date reconciled |
The date you reconciled the refund check. Numeric, 6 positions (in user date format); display-only. |
Received from bank |
Indicates whether you have received the canceled refund check from the bank. Valid values are:
The system updates this field to selected when you reconcile the check. See Reconciling and Unreconciling Checks. |
Order number |
The order that produced the refund. Numeric, 8 positions; display-only, assigned by the system. |
Customer number |
The number of the customer receiving the refund. Numeric, 9 positions; display-only, assigned by the system. |
Customer name (Unlabeled field to the right of the customer number) |
The name of the customer receiving the refund. Alphanumeric, 41 positions; display-only. |
Bill to (Bill-to customer number) |
The number of the bill-to customer associated with the order. Bill-to customer information appears only if there is a bill-to customer associated with the order. Numeric, 7 positions; display-only. |
Bill-to customer name (Unlabeled field to the right of the bill-to customer number) |
The name of the bill-to customer and company associated with the order. Alphanumeric, 42 positions; display-only. |
Bank |
The bank associated with the source code on the order. You associate a source code with a bank through its division. Bank codes are defined in and validated against the Bank table . See Working with Banks (WBNK). If you process orders in multiple currencies, each currency on your system is associated with a unique bank. Alphanumeric, 3 positions; display-only. |
Bank name (Unlabeled field to the right of the bank code) |
The description associated with the bank. Alphanumeric, 30 positions; display-only. |
Reconciling and Unreconciling Checks
Purpose: From the Work with Check Reconciliation Screen, you can reconcile individual canceled refund checks or you can reconcile a group (batch) of canceled checks by check number or by date range.
Note:
You cannot reconcile or unreconcile a voided check.Reconcile a single check: Select Reconcile for the refund check. The current date appears in the Recon field to indicate that the check has been reconciled.
Unreconcile a single check: Select Unreconcile for a reconciled refund check that you want to unreconcile. The reconciled date disappears from the screen to indicate that the check is still unreconciled.
You cannot unreconcile a voided check.
Reconcile a batch of checks: Select Batch Reconcile to display the Batch Reconciliation pop-up window.
To reconcile a batch of canceled refund checks, enter the necessary information. You can:
- Reconcile canceled checks by check number by entering the first and last check numbers in the Starting check # and the Ending check # fields, or
- Reconcile canceled checks by batch by entering the first date and the final date of the checks in the Starting check date and Ending check date fields
Correcting Refund Check Errors
Void and writeoff a refund check: Select Void/Write-off for the refund at the Work with Check Reconciliation Screen.
When you accept the void/writeoff, the system:
- displays the void date
- voids the check record
- puts the refund in writeoff pending status so it can be written off the next time you process refunds
- writes a transaction message at the Display Order History Screen.
Void and reinstate: Select Void/Reinstate for the refund.
Using the void/reinstate option:
- places the refund on hold so that it won't be processed the next time you process refunds
- writes a transaction message at the Display Order History Screen, which you can view through standard Order Inquiry. This information is also available through streamlined Order Inquiry by selecting History.
Print Reconcile List Prompt Screen
Purpose: Use the Check Reconciliation List when reconciling refund checks against your account. You can include checks within a specific range of dates and also a specific bank; this may be useful if you are preparing a report for a specific accounting period.
How to display this screen: At the Work with Check Reconciliation Screen, select Print List.
Field | Description |
---|---|
Print unreconciled checks with a check date from and to |
The first and last dates of the period for which you want to review unreconciled refund checks. Numeric, 6 positions (in user date format) each field; required if reconciled date range is not specified. |
Print reconciled checks with a reconciled date from and to |
The first and last dates of the period for which you want to review reconciled refund checks. Numeric, 6 positions (in user date format) each field; required if unreconciled date range is not specified. |
To print the Check Reconciliation List, enter dates in each field for unreconciled, reconciled or both.
Purge Refund Checks Screen (MPRF)
Purpose: Use this screen to purge refund check records once you have reconciled or voided the checks.
How to display this screen: Enter MPRF in the Fast path field at the top of any menu or select Purge Refund Checks from a menu.
To purge checks, select OK. Select the confirmation prompt that appears at the bottom right corner of the screen to purge refund checks; otherwise, select Exit to return to a menu.
The system submits the PURG_REFCHK batch job, which purges all reconciled and voided refund checks. .
The system also produces the Check Reconciliation List. Although identical in layout to the Check Reconciliation List, this version of the list includes all voided and reconciled refund checks that have been purged by the Purge Refund Check program.
Printing the Processed Refund Register (PPRR)
Purpose: Use the Processed Refund Register to view a detailed listing of refunds processed, written off, or canceled within a selected date range. You can flag a refund for writeoff or cancellation in Working with Refunds, Writeoffs and Balances Due (WREF). Once the refunds are flagged they can be processed in Process Refunds, provided they match the bank at the Process Refund screen.
This report includes detail information such as refund status, refund type, amount, customer name, and totals.
For more information:
In this topic:
Processed Refund Register Screen
Purpose: Use this screen to select the dates to include on the Processed Refund Register and to print the report.
How to display this screen: Enter PPRR in the Fast path field at the top of any menu or select Print Processed Refund Register from a menu.
Field | Description |
---|---|
Start date |
The first date to include on the report. The system determines the information to include on the report based on the refund process date, not the create date of the refund. Numeric, 6 positions (in user date format); required. |
End date |
The last date to include on the report. Numeric, 6 positions (in user date format); required. |
Instructions: Enter the date range in the start date and end date fields. Select Accept to submit your entries and generate the Processed Refund Register.
Processing Refunds by Order Number (MRFO)
Purpose: Use Process Refunds by Order Number to generate refunds for selected orders only. This option differs from Processing Refunds (MREF); this option allows you to generate all available refunds by selected refund type for a specified bank, limiting the total dollar value of refunds if desired.
Which refunds are eligible? See Processing Refunds (MREF) for an overview of how the system determines which refunds to process, cancel, or write off.
ChannelAdvisor integration: You cannot generate refund notifications to ChannelAdvisor using Process Refunds by Order Number, and must use Processing Refunds (MREF) instead for these orders. See the ChannelAdvisor Integration Overview, including Submitting Refunds for ChannelAdvisor Orders, for background.
Process Refunds by Order Screen
Purpose: Use this screen to generate refunds for selected orders.
How to display this screen: Enter MRFO in the Fast path field at the top of any menu, or select Process Refunds by Order from a menu.
Field | Description |
---|---|
Bank |
The bank associated with the source code on the order. You associate a bank with a source code by selecting a division for the source code; each division is associated with a bank. The system determines the next sequential check number to use by adding 1 to the Last check number defined in the Bank table. If you process orders in multiple currencies, the bank also indicates the currency of the refunds, since each currency on your system is associated with a unique bank. The bank you specify at this screen indicates the currency of all refund checks, credits, or writeoffs that you process at this screen. Bank codes are defined in and validated against the Bank table. See Working with Banks (WBNK). Alphanumeric, 3 positions; required. |
Orders |
Enter each order number that should have a refund processed, canceled, or written off. The system verifies that there is a refund for each order that is eligible for processing; see below for details. Numeric, fifteen 8-position fields; required. |
Completing this screen:
# | Step |
---|---|
1. |
Enter the bank associated with the refund(s). |
2. |
Enter each order number to have a refund processed, canceled, or written off. Optionally, select Work with Refunds to advance to the Work with Refunds Screen to review refunds eligible for generation. Note: If you Select OK before entering any order numbers, you can enter any order number and Select OK again in order to exit the screen. |
3. |
Select OK. The system validates your entries and highlights any order numbers in error. Possible errors are: |
Sample error message | Explanation |
---|---|
All refund records on hold for order 2464 1 of 3 refunds for order 2192 are on hold |
The Ref Sts (Refund status) is held (H) or the Manual hold flag for the refund is selected. |
Bank not valid for order 2465 |
The bank for the order is not the same as the Bank you entered. |
Order 2605 not valid for processing |
The Ref Sts (Refund status) is processed (P), canceled (C), or written off (T). |
Order 3865 is not eligible for refund processing |
The Ord sts (Order status) is held (H) or suspended (S). |
No refunds exist for order 5845 |
There are no refunds for the order. |
# | Step |
---|---|
4. |
After correcting any errors, select Submit. If there are any refund checks to generate, a pop-up window appears displaying the next available check number. You can accept the check number displayed, change the check number, or select Exit to close the window and cancel the action. |
5. |
The system submits the job REFORD_PRC. This job processes the same updates and reports as the Processing Refunds (MREF) menu option; see Summary of Refund Processing Updates and Reports. |
Working with Catalog Requests
In this part:
- Entering Catalog Requests (WCAT) shows you how to use the Catalog Request screens to create catalog requests for new and existing customers, and to change, delete, or display catalog request records.
- Processing Catalog Requests (PCAT) shows you how to use the Process Catalog Requests screen, discusses printing options, and shows you how to reset printed requests so that you can reprint labels, if needed.
- Deleting All Printed Catalog Requests (DCAT) discusses the screen you use to delete all printed catalog requests at one time.
- Working with the Catalog Request Interface (WCRU) discusses processing catalog requests you receive through an interface with Order Management System.
Entering Catalog Requests (WCAT)
Purpose: Use catalog requests to capture inquiries and manage requests for catalogs from new or existing customers. Creating catalog requests lets you track inquiry information, report on trends with respect to requests for specific catalogs, and quickly print labels in response to those requests.
You use the Work with Catalog Requests Screen when you want to create, change, delete, or display specific catalog requests or when you want to display or print a list of catalog customers whose names are still in the Catalog Request table.
Note:
You can also receive catalog requests through the catalog request interface. See Working with the Catalog Request Interface (WCRU).Catalog request history: The system tracks the total number of catalog requests by source code and date in the Catalog Request History table. This information is available for reporting purposes, such as on the Campaign Performance Report; see Print Campaign Performance Reports (PCPR) for more information. See Catalog Request History Options for additional menu options related to the Catalog Request History table.
Oracle Retail Customer Engagement customer integration: When you use the Oracle Retail Customer Engagement customer integration, if you create a customer through a catalog request, Order Management System sends the customer information to Oracle Retail Customer Engagement so that the customer records in the two systems are synchronized. See the Customer Engagement Customer Integration for more information.
E-Commerce Catalog Requests
The CWServiceIn web service allows an external system to post the E-Commerce Catalog Request Message (CWCatRequest) directly to Order Management System and receive responses without the need of any queues. My Oracle Support
- If the E-Commerce Catalog Request Message (CWCatRequest) passes validation, a catalog request record is created. See the Web Services Guide on My Oracle Support (ID 2149144.1). You can review and change the catalog request at the Work with Catalog Requests Screen.
- If the E-Commerce Catalog Request Message (CWCatRequest) does not pass validation, a catalog request interface record is created. See the Web Services Guide on My Oracle Support (ID 2149144.1). You can review and correct the catalog request through Working with the Catalog Request Interface (WCRU).
Catalog request response: You can also send an E-Commerce Catalog Request Response Message (CWCatreqResponse) to the web storefront. See the Web Services Guide on My Oracle Support (ID 2149144.1). The catalog request response message indicates the customer number used to create the catalog request. If the customer number in the catalog request response message is blank, the catalog request did not process correctly and needs to be corrected through Working with the Catalog Request Interface (WCRU). Note: The e-commerce customer updates response message is available for XML messages only, not name/value pair messages.
The response_required field in the catalog request message indicates if a catalog request response message is sent to the web storefront.
- A value other than Y indicates a catalog request response message is not sent to the web storefront.
- Y indicates a catalog request response message is sent to the web storefront.
Customer updates: Additionally, if the customer associated with the catalog request does not exist, the system will create a new customer; see Customer Creation/Update Logic in E-Commerce Catalog Requests. In this case, it is useful to send a catalog request response message to the web storefront indicating the newly assigned customer number.
Oracle Retail Customer Engagement customer integration: When you use the Oracle Retail Customer Engagement customer integration, if you create a customer through an e-commerce catalog request, Order Management System sends the customer information to Oracle Retail Customer Engagement so that the customer records in the two systems are synchronized. See the Customer Engagement Customer Integration for more information.
See E-Commerce Catalog Requests in the Web Services Guide on My Oracle Support (ID 2149144.1).for additional processing information.
In this topic:
Work with Catalog Requests Screen
How to display this screen: Enter WCAT in the Fast path field at the top of any menu or select Work with Catalog Request from a menu.
Field | Description |
---|---|
Customer |
A unique number the system assigns to each Sold-to customer on creation of the customer through Order Entry, Customer Maintenance, or catalog requests. Ghost customers: If you enter the customer number of a ghost customer, the scan screen does not display any catalog requests; this is because a merge/purge has assigned any catalog requests using that customer number to the “target” customer. You can identify a ghost customer by the setting of the Ghost flag. Numeric, 9 positions; optional. |
Ofr (Offer) |
Represents the advertising medium that you use to present merchandise to your customers. Your entry is validated against the Offer table. Alphanumeric, 3 positions; optional. |
Source |
A code that identifies a list of customers. The source code drives marketing, pricing, and freight information on an order. A source code will appear here only if a source code was entered when the catalog request was created. Alphanumeric, 9 positions; optional. |
Request date |
The date the catalog request was created. Numeric, 6 positions (in user date format); display-only. |
Printed |
A flag that indicates whether you have printed a catalog for the customer. No displays in this field next to a request until the catalog label is printed. Once the catalog label is printed, this value changes to Yes. Records remain on this list, regardless of their printed status, until you delete them selectively, or in batch mode. Values are:
Optional. |
Screen Option | Procedure |
---|---|
Create a catalog request |
Select Create to advance to the Create Catalog Request Screen. |
Change a catalog request |
Select Change for a catalog request to advance to the Change Catalog Request Screen. |
Delete one or more catalog request records |
Select Delete for a catalog request to display a pop-up window containing deletion options. You can delete a request using this method regardless of whether the label has been printed. |
Display catalog request records |
Select Display for a catalog request to advance to the Display Catalog Request Screen. You cannot change any information on this screen. See Change Catalog Request Screen for a sample screen and field descriptions. |
Catalog Request Creation Options

E-commerce catalog requests: If the customer associated with an e-commerce catalog request does not exist, the system will create a new customer; see Customer Creation/Update Logic in E-Commerce Catalog Requests in the Web Services Guide on My Oracle Support (ID 214914.1)
Ghost customers: If you enter the customer number of a ghost customer, the system displays the Ghost Customer Warning Window.
Create Catalog Request Screen
Purpose: Use this screen to create a catalog request for a new or existing customer.
How to display this screen: At the Work with Catalog Requests Screen, select Create.
Note:
You can also display this screen by selecting Catalog Request from the Select Customer Sold To For Order Screen or at the Customer Selection Screen in Order Entry.Note:
If you are creating a catalog request for an existing customer, do not complete the following fields; instead, select Select Customer to select an existing customer, then complete the Offer, Item, Source, and # of copies fields. See Catalog Request Creation Options for an overview.Ghost customers: If you enter the customer number of a ghost customer, the system displays the Ghost Customer Warning Window.
Field | Description |
---|---|
Name |
The following five fields can hold the sold-to customer's full name: PrefixA title that belongs before the customer's name (such as "Mrs." or "Dr."). The prefix will print on labels. Alphanumeric, 3 positions; optional if you are creating a new customer, or display-only if you select an existing customer. First NameThe customer's first name. Alphanumeric, 15 positions; optional if you are creating a new customer, or display-only if you select an existing customer. InitialThe initial of the customer's middle name. Alphanumeric, 1 position; optional if you are creating a new customer, or display-only if you select an existing customer. Last NameThe customer's last name. Alphanumeric, 25 positions; required if company name is not present and you are creating a new customer, or display-only if you select an existing customer. SuffixAn addition to the customer's full name (such as "M.D.," "Fr.," or "III"). Alphanumeric, 3 positions, optional if you are creating a new customer, or display-only if you select an existing customer. |
Company |
The name of the company to which the catalog should be mailed, if applicable. Alphanumeric, 30 positions; required if last name is not present and you are creating a new customer, or display-only if you select an existing customer. |
M/F (Male/Female code) |
A code that identifies the customer's gender. Alphanumeric, 1 position; optional. |
This flag indicates whether the customer wants to receive future catalog mailings from your company. Not to be confused with the Mail code, a three-position, alphanumeric field. Valid values are:
May default from the Default Mail Name (D10) system control value, but you can override it. |
|
Rent |
Indicates whether you can sell this customer's name to another company for their catalog mailings. Valid values are:
May default from the Default Rent Name (D11) system control value, but you can override it. |
Address |
The customer's street address. This is the primary delivery address. Shipping to a Post Office BoxTo ship to a Post Office Box, enter POST OFFICE BOX, POST BOX, or any variation of PO BOX (with or without spaces or non-alphabet characters, such as P.O. BOX), and the box number in the customer’s street address. During order processing, the system validates that the carrier can ship to a post office box (as defined in the Ship Via table). Example: Enter P.O. Box 9999 in the Street field to indicate delivery to a post office box instead of a home or company address. Note: If you type POST OFFICE BOX, POST BOX, or any variation of PO BOX in the customer’s street address during order entry or through the Order API, the system automatically selects the PO box field for the customer. However, if you remove this text from the customer’s street address, the system does not automatically deselect the PO box flag.Note: When you create a customer outside of order processing, you need to select the PO box field manually.Alphanumeric, 32 positions; required if you are creating a new customer, or display-only if you select an existing customer. |
Apt./suite |
The apartment number or suite number of the delivery address. To enter an apartment or suite address: 1.Enter APT to indicate an apartment or STE to indicate a suite. 2.Insert a space and enter the number of the apartment or suite (for example, APT 4 or STE 116). Field contents must conform to United States Parcel Service (USPS) address formatting Field Description standards. Always precede the apartment or suite number with the applicable abbreviation (such as APT or STE), to meet USPS regulations and correctly identify this information on labels or reports. Alphanumeric, 10 positions; optional if you are creating a new customer, or display-only if you select an existing customer. |
Address lines 2-4 (Unlabeled fields directly beneath the street address) |
Additional entry fields for the customer's address. The contents of address line 2 of the address must conform to United States Postal Service (USPS) formatting standards. For example, if the address represents a post office box, you must enter P.O. Box on this line to meet USPS regulations and correctly identify this information on labels. Alphanumeric, 30 positions; optional if you are creating a new customer, or display-only if you select an existing customer. |
Postal code |
The postal or zip code for this customer. Required only if the Require postal code? flag is selected for the country. See Setting Up the Country Table (WCTY) for background. If a postal code is required for the country, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP). Scan length: The Postal Code Scan Length (F61) system control value controls how many characters of the postal code to use when searching for a customer. See that system control value for a discussion. Note: If postal codes have been entered into the Postal Code/City/State table, the postal code indicates the City and State to default. If you enter a valid postal code that does not correspond to the city or state you entered, the system changes the city or state information to correspond with the zip code you entered.Numeric, 10 positions; required or optional based on country if you are creating a new customer, or display-only if you select an existing customer. |
City |
The city where the customer lives, or receives mail or shipments. The system will complete this field for you when you enter a valid postal code if the postal code exists in the Postal Code/City/State table. Alphanumeric, 25 positions; required if you are creating a new customer, or display-only if you select an existing customer. |
St (State) |
The state or province where the customer lives, or receives mail or shipments. The system validates that the state you enter is assigned to the SCF in the first three positions of the postal code. State codes are defined in and validated against the State table, which is accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Required only if the Require state? flag is selected for the country. The system completes the state field automatically when you enter a valid postal code if the postal code exists in the Postal Code/City/State table. Alphanumeric, 2 positions; required or optional based on country if you are creating a new customer, or display-only if you select an existing customer. |
Country |
The code for the customer's country. May default from the Default Country for Customer Address (B17) system control value; however, you can override it. Country codes are defined in and validated against the Country table. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required if you are creating a new customer, or display-only if you select an existing customer. |
Delivery code |
This code identifies the address as a business or residential address. This code is used by shippers who charge different rates when shipping to a business or home. Valid values are:
This field may default based on the Default Delivery Code for New Order Entry Customers (D13) system control value, but you can override it. Required. |
Customer class |
A code that categorizes the consumer environment at a high level for reporting purposes. You can use a customer class code to:
|
If you enter a new customer class code in this field, the system updates the Customer Sold To table with the code you entered. Required? The Require Customer Class in OE, WCAT, and WCST (H85) system control value defines whether this field is required. Secured? The Maintenance of Customer Class Field (B07) secured feature defines whether you can enter or maintain the customer class field at this screen. Note: If the Require Customer Class in OE, WCAT, and WCST (H85) is selected and the customer does not have a customer class code assigned, a user who does not have authority based on the Maintenance of Customer Class Field (B07) secured feature will not be able to enter a catalog request.See Setting Up the Customer Class Table (WCCL) for information on working with customer classes. Numeric, 2 positions; optional. |
|
Phone |
The customer's daytime, evening, and fax or mobile telephone numbers. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number.Alphanumeric, one 14-position field (phone number) and one 4-position field (phone extension); optional if you are creating a new customer, or display-only if you select an existing customer. |
Email address |
The customer's primary email address. This address, along with any other email addresses for the customer, is stored in the Customer Sold To Email table. A plus sign (+) indicates that there are additional email addresses on record for the customer. See Email Address Validation for information on how the system verifies that your entry is formatted correctly. Entering a new email address: If you overwrite the existing email address in this field, the system flags your entry as the primary email address for the customer, but retains the previous email address in the Customer Sold To Email table. In order to delete the previous email address, you need to prompt to display the Select Customer Email Address Screen and delete the previous email address there. See Working with Customer Email Addresses for an overview. Deleting the email address: Similar to entering a new email address, if you delete the email address from this field, the system removes the primary email flag for the address but retains the address in the Customer Sold To Email table. Email notifications: See When Does the System Generate an Email Notification? for an overview. Alphanumeric, 50 positions; optional. |
Opt in |
Determines the preferred method of correspondence for the sold-to customer email address. Valid values are:
Defaults from the Default Opt In/Opt Out Flag (G97) system control value, but you can override it. Note: The above values use the letter O, not the number 0 (zero).The system updates this field when you change the setting of the Opt in/Opt out value at any other screen, such as order entry, order maintenance, or customer maintenance. |
Email notifications: See When Does the System Generate an Email Notification? for an overview. Alphanumeric, 2 positions; required. |
|
# of copies |
The number of catalogs the customer wants to receive; controls the number of labels printed when you use Processing Catalog Requests (PCAT). For example, if you enter 5 here, the system prints 5 labels for the customer. If you do not have authority to the Allow Number of Copies to Maintain in Catalog Request (A75) secured feature, this field is display-only. Tracking catalog request history: When you print the catalog request label, the system uses the total number of requests rather than the total number of copies when tracking catalog request history in the Source Code table and in the Catalog Request History table. For example, if a customer requests 3 copies of a catalog, the system increases the total by 1, not by 3. You can review the total number of catalog requests for a source code at the Source Code History Screen and on the Campaign Performance Report (PCPR). Numeric, 2 positions; required. |
Source |
A code that identifies a list of names for this catalog mailing. The source code drives marketing, pricing, and freight information on an order. Note: You can prompt to view a list of the source codes you can use. Only those source codes set to display in Order Entry and catalog requests appear in the Select Source pop-up window.The first source code you enter on this screen will default for any other catalog requests you create so you can enter them quickly. Once you exit this screen, the Source field will clear. The source code will default in the Source field for alternate address and standard address format. Source codes are defined in and validated against the Source Code table. See Working with Source Codes (WSRC). Alphanumeric, 7 positions; required. |
Offer |
The code for the catalog that the customer is requesting. Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR). The first offer code you enter on this screen will default for any other catalog requests you create so you can enter them quickly. This field clears when you exit the screen. The offer code will default in the Offer field for alternate address and standard address format. Note: You must enter an offer code or an item/SKU.Numeric, 3 positions; required unless you complete the Item field. |
Item (Item number) |
The code for the item you are sending to the customer with the catalog. Examples would be swatches of material or promotional items printed with your company name. Item numbers are defined in and validated against the Item table. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; optional. |
SKUs |
A code for the style of the item, such as its color or size. Alphanumeric, three 4-position fields; required if entering an item that has SKUs. |
Catalog Request Customer Updates
When you create a new customer here, the system creates the new customer in the Customer Sold To table. The current and original mail type fields are set to C (catalog request). If the Track Customer History at Entity Level (F89) system control value is selected, the system also creates a Customer Entity record for the entity associated with the source code.
Oracle Retail Customer Engagement customer integration: If the ORCE Customer Integration (L37) system control value is set to INTERACT, when you create a new customer at this screen, the customer is also created in Oracle Retail Customer Engagement, and the two customer records are synchronized. See the Customer Engagement Customer Integration for more information.
If you select an existing customer and change the value of an existing field, such as the Opt in/opt out field or the Customer class, the system updates the customer table. See Creating and Updating Sold-to Customers (WCST).
When the catalog request label is printed, the Customer Mail History table is updated through the catalog request. The Original source field is updated if you added a new customer. See First Create Sold To Customer Screen.
If the customer you enter already exists: The system displays the Duplicate Customer window if the customer information you enter matches an existing customer in the Sold To Customer table. The system displays this window based on match code.
You can use the existing customer information and cancel the creation of the new customer, or you can override this message and create the additional customer. You might use the duplicate customer information, for example, if two different people with the same name, such as John Smith, live at addresses that are so similar that the system thinks they are the same person.
If the customer's catalog request already exists: The system displays the Display Duplicate Sold To pop-up window if the customer and offer/item information you enter at the Create Catalog Request Screen matches an existing customer sold to, based on match code. A match code is made up of parts of the customers name, address, and postal code. The match code is a user-defined code defined in the Match Code table; See Setting Up Match Codes (MMCH).
Note:
If you do not set up a match code in the Match Code table, the system displays the first sold to customer, based on sold to customer number, as a duplicate each time you enter a new address.Duplicate catalog requests: The system uses the Edit for Duplicate Catalog Requests (E46) system control value to update duplicate catalog requests. If this value is selected, the system checks for a duplicate when you create a new catalog request; if there is a match, the system replaces the existing request with the new one. If this value is unselected, the system creates a new catalog request without checking the existing records.
When you print the catalog request label, the system uses the total number of requests rather than the total number of copies when tracking catalog request history in the Source Code table and in the Catalog Request History table. For example, if a customer requests 3 copies of a catalog, the system increases the total by 1, not by 3. You can review the total number of catalog requests for a source code at the Source Code History Screen and on the Campaign Performance Report (PCPR).
Screen Option | Procedure |
---|---|
Enter a catalog request for a new customer |
Complete the fields as described under Create Catalog Request Screen. See Catalog Request Creation Options for an overview. |
Select an existing customer |
Select Customer to advance to the Select Customer for Catalog Request Screen. See Catalog Request Creation Options for an overview. Note: If the ORCE Customer Integration (L37) system control value is set to INTERACT, you advance instead to the Customer Scan Screen. See that screen for more information. |
Work with products a customer owns |
Select Cust Ownership.
|
Add notes for the customer |
Select Notes to advance to the Edit Customer Notes Screen. |
Select Customer for Catalog Request Screen
Purpose: In addition to creating catalog requests for people who are not yet customers, you can also create catalog requests for existing customers from the Create Catalog Request Screen.
When creating a catalog request for an existing customer, the system copies customer information from the Sold To Customer directly into the catalog request. See Catalog Request Creation Options for an overview.
How to display this screen: At the Create Catalog Request Screen, select Select Customer.
Note:
If the ORCE Customer Integration (L37) system control value is set to INTERACT, you advance instead to the v. See that screen for more information.How to use this screen: Use this screen to advance to scan screens that let you locate existing customer records. If the customer exists, you can select the customer and the system will copy information from the customer into the customer fields on the Create Catalog Request Screen.
Field | Description |
---|---|
Customer |
A unique number the system assigns to each customer on creation of the customer through Order Entry, Customer Maintenance, or catalog requests. Ghost customers: If you enter the customer number of a ghost customer, the system displays the Ghost Customer Warning Window. Numeric, 9 positions; optional. |
Postal code |
The postal or zip code that identifies the customer's geographic location. Enter a full or partial code to advance to the Scan Sold To by Postal Code/Company screen. This screen lists all customers by postal code in ascending (lowest to highest) numeric sequence, beginning with the code you entered. If you enter a postal code, last name, and first name, you advance to the Scan Customer Sold To by Postal Code screen, which lists all customers alphabetically beginning with the postal code you entered. Alphanumeric, 10 positions; optional. |
Last name |
The sold-to customer's last name. Enter a last name, first name, and postal code to advance to the Scan Customer by Postal Code/Last Name screen, positioned to the customer with the last name, first name, and postal code you entered. Enter a full or partial name to advance to a Scan Cust Sold To By Last Name screen, which lists all customers alphabetically beginning with the name you entered. You can also include a full or partial first name along with a full (not partial) last name to restrict the scan further. Alphanumeric, 25 positions; optional. |
First name |
The sold-to customer’s first name. Enter the last name, first name, and postal code to advance to the Scan Customer Sold To by Postal Code screen, which lists all customers alphabetically beginning with the postal code you entered. You can also enter just the full (not partial) last name and full or partial first name to advance to the Scan Cust Sold To By Last Name screen. Note: First name must be used in conjunction with Postal code, Last name for scanning. You cannot scan on first name alone, or on first name, last name.Alphanumeric, 15 positions; optional. |
Company |
The name of the company placing the catalog request. Alphanumeric, 30 positions; optional. |
Telephone # |
The customer's daytime, evening, or third (fax or mobile) telephone number. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number.Note: Your entry should include any formatting specified by the telephone number format for the country; for example, if the telephone number format for the United States is (111) 111-111, your entry should include the parentheses and hyphen. See Setting Up the Country Table (WCTY), for more information on telephone number formats by country.Alphanumeric, 14 positions; optional. |
Alternate customer number |
A number to identify the customer, such as an old customer number from a system conversion. Enter an alternate customer number to advance to a subsequent scan screen that lists customers by alternate customer number. Display Alternate Customer Cross Reference Window (I84) for more information. Alternate Customer Number Label DescriptionThe field label on this screen is based on the name you enter in the Alternate Customer Number Label Description (H95) system control value; if you do not enter a name in this system control value, the field label is Alt cust. Example: If you enter the field label name MEMBER# in the system control value, the field label on this screen is MEMBER#. Note: Scanning by the alternate customer number of a ghost customer is not currently implemented if the Display Alternate Customer Cross Reference Window (I84) system control value is selected.Alphanumeric, 15 positions; optional. |
Email Address |
An email address for the customer. When you enter a full or partial email address, you advance to the Scan Customer by Email Address screen, where you can scan by any email address on file for a customer. This field is not case sensitive; an email address of abc@example.com matches an entry of ABC@EXAMPLE.COM, and vice versa. Alphanumeric, 30 positions; optional. |
Option | Procedure |
---|---|
Select a customer for a catalog request |
Click a customer name to return to the Create Catalog Request Screen with that customer’s name and address defaulted. |
Change a customer’s name and address information |
Select Change for a customer to advance to the Change Cust Sold to Name & Address Screen. |
Display a customer’s name and address information |
Select Display for a customer to advance to the Display Customer Sold To screen. See the See the First Create Sold To Customer Screen for field descriptions. |
Create a catalog request for a new customer |
Select Create to return to the Create Catalog Request Screen without selecting a customer. |
Ghost Customer Warning Window
A ghost customer is a customer whose records have been merged with the records of a matching customer through a merge/purge. The ghost customer was the source customer in the merge; records for this customer were merged with the records for a matching target customer. When performing the merge you can elect to flag a source customer as a Ghost. Ghost customer records are retained in the Customer Sold To table for informational purposes, but they do not represent the most recent customer order information from the merged (target customer) records.
When you enter the number of a ghost customer, the pop-up Warning Window presents the information on the ghost customer and target.
Select Continue to advance to the Create Catalog Request Screen with the target customer number entered on the screen. For example, if you enter 202, a ghost customer, the system will display this window informing you that customer 202 has been merged into customer 137. When you continue with the catalog request process, customer 137 will default on the Create Catalog Request screen.
Note:
The Ghost Customer Warning pop-up window does not display when you use the Customer Selection Screen.See Working with Merge/Purge Sold-to Names (MMCS) for more information on the merge/purge function.
Canceling the creation: Once you select a customer from the Select Customer for Catalog Request Screen, you return to the Create Catalog Request Screen, which displays the information from the request you selected. If, on review, you learn that the customer information is incorrect, you can remove it from the screen without creating a catalog request.
Select Create to erase the selected customer information from the Create Catalog Request Screen. The system clears your entries and you can begin again.
Change Catalog Request Screen
Purpose: Use this screen to change the offer number, item number, SKU, source code, or the number of copies for a catalog request.
How to display this screen: At the Work with Catalog Requests Screen, select Change for a catalog request.
Additional fields at this screen:
Field | Description |
---|---|
Printed |
A code that identifies whether the catalog mailing label has been printed for a catalog request. The system updates this value when you process the catalog requests; see Processing Catalog Requests (PCAT). If you deselect this flag after the catalog request label is printed, the system decreases the Requests mailed total for the source code. Once you print the label again, the system increases the total again. You can review this total at the Source Code History Screen and on the Campaign Performance Report (PCPR) Values are: selected = The catalog label has been printed. unselected = The catalog label has not been printed. |
Date printed |
The date the catalog label was printed. Numeric, 6 positions (in user date format); display-only. |
Catalog requested on |
The date and time of the catalog request. Date: numeric, 6 positions (in user date format); updated by the system. Time: numeric, 6 positions; HHMMSS (hour/hour, minute/minute, second/second) format, updated by the system. |
Catalog requested by |
The name of the system user who entered or processed the catalog request. Alphanumeric, 10 positions; display-only. |
See Create Catalog Request Screen for a description of the other fields on this screen.
Note:
Changing a catalog request from one source code to another does not affect the total quantity for each source code tracked in the Catalog Request History file, or tracked on reports such as the Campaign Performance Report (see Print Campaign Performance Reports (PCPR) for more information).Processing Catalog Requests (PCAT)
Purpose: Once you have created catalog requests, you process them by printing the catalog mailing labels. You can format the labels in rows of two or three addresses each.
Reprint: You can reprint catalog requests if the labels become jammed in the printer by using the Reset Printed Catalog Request Screen (RCAT) and then the Process Catalog Requests Screen (PCAT).
Related system control values: Use the Label 2-Up Printing Program (C83) and Label 3-Up Printing Program (C84) system control values to specify which program to use when printing catalog request labels.
History updates: When you print catalog request mailing labels, the system updates:
- Customer mail history: see Display Customer Mail History Screen
- Last source and Last mail date in customer order history: see Display Customer Order History Screen
- Source code: see the Source Code History Screen
- Catalog request history: see the Campaign Performance Report (PCPR)
Note:
You cannot print catalog requests if another person has submitted the job and it is currently running.In this topic:
- Process Catalog Requests Screen (PCAT)
- Catalog Mailing Labels (MSR0613 or MSR0614)
- Labels Printed by Item Report
- Labels Printed by Source Report
- Labels Printed by Zip Report
For more information: See Reset Printed Catalog Request Screen (RCAT).
Process Catalog Requests Screen (PCAT)
Purpose: At this screen you can print labels for the catalogs you want to mail. You can:
- print directly to a printer
- specify the number of labels to print
- print labels for selected source codes and/or items
Note:
For best results, do not select the Shrink to Fit option when printing labels.How to display this screen: Enter PCAT in the Fast path field on any menu screen or select Process Catalog Requests from a menu.
Field | Description |
---|---|
Number of labels ready to print |
The number of catalog mailing labels eligible to be printed for catalog requests. The number of unprinted catalog requests appears here. Represents the total number of copies requested for the catalogs if a customer requested multiple copies. Numeric, 5 positions; display-only. |
Nbr of labels to print (Number of labels to print) |
The number of labels that you want to print. This field defaults to the same number as in the Nbr of labels ready to print field, but you can override it. Numeric, 5 positions; required. |
Select source codes |
Use this field if you want to print catalog mailing labels only for one or more specific source codes. Selecting multiple source codes: Click on the arrow in this field to advance to the Select Multiple Sources screen. At this screen, you can select a source by Selecting it. You can deselect a source by selecting Deselect for it. Select Exit to return to the Process Catalog Requests screen. If you have selected more than one source code, (MULTIPLE SELECTED) appears to the right of this field. Leave this field blank to select all eligible catalog requests regardless of source code. Alphanumeric, 9 positions; optional. |
Select items |
Use this field if you want to print catalog mailing labels only for one or more specific items. You can identify an item, such as a promotional item with your company's logo or a swatch of material that should be sent along with the catalog. If an item is specified with a catalog request, the item code prints on the catalog mailing label. Selecting multiple items: click on the arrow in this field to advance to the Select Multiple Items screen. At this screen, you can select an item by Selecting it. You can deselect an item by Deselecting it. Select Exit to return to the Process Catalog Requests screen. If you have selected more than one source code, (MULTIPLE SELECTED) appears to the right of this field. Leave this field blank to select all eligible catalog requests regardless of item. Alphanumeric, 12 positions; optional. |
Print option |
The code to print the catalog mailing labels. Printer indicates the mailing labels will be printed on a printer. Required. |
Label type |
Controls how many labels to print in a row. Valid values are:
The Label 2-Up Printing Program (C83) and Label 3-Up Printing Program (C84) system control values specify which formats to use when printing labels. Required if Print option field is set to Printer. |
Sort labels |
Identifies how to sorts the catalog mailing labels. Valid values are:
Required if Print option field is set to Printer. |
Delete request |
Controls whether to delete all catalog requests whose Printed fields are selected, regardless of whether these records were included in the current print job. Example: If you entered 20 in the Nbr of labels to print field, but there are additional printed catalog requests in the Catalog Request table, the system will delete the requests you included in your current print number plus every catalog request whose Printed field is selected. Valid values are:
|
Screen Option | Procedure |
---|---|
Display the Work with Catalog Requests Screen |
Select W/W Requests. |
Reset Printed Catalog Request Screen (RCAT)
Purpose: Use the Reset Printed Catalog Requests function to change the status of all printed request records to “unprinted.” This reset might be useful if there is a problem with the catalog mailing labels you just printed, such as if the labels jammed when printing.
This screen displays the number of printed catalog requests that will be reset.
How to display this screen: Enter RCAT in the Fast path field at the top of any menu, or select Reset Printed Catalog Requests from a menu.
Reset all printed catalog requests: Select OK without entering a date range to reset the status of all printed catalog requests from selected to unselected to make them eligible for reprinting. Optionally, you can also select a company (by number) to reset catalog requests in a different company; your current company defaults.
Reset specific catalog requests:
- Enter a date range to reset the status of all catalog requests printed within the dates you specify. Optionally, you can select a company (by number) to reset catalog requests in a different company; your current company defaults.
- Select Work with Requests to advance to the Work with Catalog Requests Screen, where you can review printed requests before you reset the print status of all printed catalog requests. From this screen, you can also select Change for a catalog request to advance to the Change Catalog Request Screen, where you can reset the Printed field for a specific request.
Screen Option | Procedure |
---|---|
Advance to the Work with Catalog Requests Screen |
Select Work with Requests. |
Deleting All Printed Catalog Requests (DCAT)
Purpose: Once you have created and printed catalog requests, you can delete them individually or as a group.
Delete Printed Catalog Requests Screen
How to display this screen: Enter DCAT in the Fast path field on any menu or select Delete Printed Catalog Requests from a menu.
To delete printed catalog requests: Enter a date range to delete catalog request records printed within the dates you specify. Optionally, you can also enter a company (by number) to delete catalog requests in a different company; your current company defaults.
To delete all printed catalog requests: Select OK at this screen without entering a date range to delete all printed Catalog Request records.
Note:
You cannot reprint deleted catalog request records.Review printed catalog requests: Select Work with Requests to advance to the Work with Catalog Requests Screen, where you can view printed requests to verify the global deletion.
For more information: Entering Catalog Requests (WCAT) and Processing Catalog Requests (PCAT).
Working with the Catalog Request Interface (WCRU)
Purpose: Use the Work with Catalog Request menu option to review the records that have been uploaded to the Catalog Request Interface table (IXCRIN), to correct any errors, and to generate catalog requests from the interface records. You might use the Catalog Request Interface table as a means to collect catalog requests you receive from various sources, and make sure that you have complete information for each of them before you attempt to create the catalog requests in Order Management System.
The catalog request interface also creates new customer sold to records, and you can use the interface to create a customer record without actually processing a catalog request.
Use the following steps to create a catalog request from an external system.
# | Step |
---|---|
1 |
Create a text file that contains the records to upload to the Catalog Request Interface table. You can use the sample data below to create records in the upload text file. 34 SAMPLE STREET|APT123|ADDRESS LINE 2|ADDRESS LINE 3|ADDRESS LINE 4|WESTBOROUGH|01581||MA|US|5085550100||thomasbrown@example.com|O1|R|COMPANY NAME|SOURCE7|7|1150417|207|5085550101||5085550102||MS.|MARY|M|JOHNSON||MARYJOHNSON@EXAMPLE.COM||5085550104|5085550105|5085550106|1|1|O1 Note: If you wish to leave any field in the upload file blank, pass a space in an alphanumeric field and a 0 in a numeric field so that the file can be processed without errors. Leaving a field with no space or 0 is interpreted as null in the database and causes errors. |
2 |
Populate the Catalog Request Interface table by:
|
3 |
Select Submit at the Work with Catalog Request Interface Screen to process the requests. When you process:
|
4 |
Once the catalog requests are generated, you can process and print them like any other requests. See Entering Catalog Requests (WCAT). |
E-Commerce catalog requests: You can use this menu option to review and correct catalog requests received through the e-commerce catalog request process that are in error. If a catalog request received through the e-commerce catalog request process does not contain errors, you can review and process the catalog request using the Work with Catalog Requests menu option; see Entering Catalog Requests (WCAT).
Note:
If you receive a catalog request from e-commerce that has errors, and customer ownership information has been defined for the sold to customer on the catalog request, the system does not retain the customer ownership information when you correct the errors and reprocess the catalog request.Oracle Retail Customer Engagement customer integration: When you use the Oracle Retail Customer Engagement customer integration, if you create a customer through the catalog request interface, Order Management System sends the customer’s name, address, email address, phone numbers, and contact permissions to Oracle Retail Customer Engagement so that the customer records in the two systems are synchronized. See the Customer Engagement Customer Integration for more information.
In this topic:
- Work with Catalog Request Interface Screen
- Change Catalog Request Screen
- Processing Requests
- Catalog Request Interface Errors
- Catalog Request Related System Control Values
- Creating a New Customer
- Print Request Interface Report
- Print Catalog Request Interface Errors Report
Work with Catalog Request Interface Screen
How to display this screen: Enter WCRU in the Fast path field on any menu or select Work with Catalog Request Interface from a menu.
Field | Description |
---|---|
Type |
Indicates the source of the catalog request. Note: If this field is blank, the catalog request is in error status and you cannot change it through this menu option. You need to delete the record and recreate it, either by populating the Catalog Request Interface table directly or by entering the catalog request through Entering Catalog Requests (WCAT).E-Commerce catalog requests: Catalog requests received through the e-commerce catalog request process have a type of PHR0062. Alphanumeric, 10 positions; optional. |
Source |
The source code assigned to the catalog request, indicating how the customer came to contact you. If the source code is not specified in the Catalog Request Interface table, the system assigns the Default Source Code for Batch Catalog Requests (D37) system control value when you select Submit to submit the interface records for processing. Alphanumeric, 9 positions; optional. |
Name |
The customer's last and first names, separated by a column. Last name: alphanumeric, 25 positions; display-only. First name: alphanumeric, 15 positions; display-only. |
Date |
The date specified in the Catalog Request Interface table indicating when the request was received. Numeric, 6 positions (in user date format); optional. |
St (Status) |
Indicates the current status of the catalog request. Valid values are:
Alphanumeric, 1 position; optional. |
Screen Option | Procedure |
---|---|
Change a catalog request interface record |
Select Change for a record to advance to the Change Catalog Request Screen. |
Delete a catalog request interface record |
Select Delete for a record to delete it. |
Display a catalog request interface record |
Select Display for a record to advance to the Display Catalog Request Screen. |
Submit the catalog request records for processing |
Select Submit. See Processing Requests. |
Change Catalog Request Screen
Purpose: Use this screen to change a record in the Catalog Request Interface table and to correct errors. When you select OK, the system validates the entries on the screen and highlights the field that contains an error.
Once you correct the errors on this screen, the record’s status changes from E to blank, and it is eligible for processing.
How to display this screen: Select Change for a catalog request record at the Work with Catalog Request Interface Screen.
Note:
If the Type field for the catalog request record is blank, you advance first to a key screen and you cannot correct any other errors for the record. You need to delete the record and recreate it (for example, using Entering Catalog Requests (WCAT)).Field | Description |
---|---|
Name |
The following fields are available for the customer's full name: Prefix A title (such as “Mrs.” or “Dr.”) that precedes the customer's name. The prefix prints on labels, reports, etc. Alphanumeric, 3 positions; optional. First Name The Sold-to customer's first name Alphanumeric, 15 positions; optional. Initial The initial of the customer's middle name. Alphanumeric, 1 position; optional. Last Name The customer's last name. Alphanumeric, 25 positions; required if company name is not specified. Suffix An addition to the customer's full name (such as “M.D.,” “Fr.,” or “III”). The suffix prints on labels, reports, etc., but is not accessible to scans. Errors: The record is in error status if both the last name and the company field are blank. Alphanumeric, 3 positions, optional. |
Company |
The name of the company associated with the customer placing the order. Errors: The record is in error status if both the last name and the company field are blank. Alphanumeric, 30 positions; required if last name is not specified. |
Street |
The customer's street address. This is the primary delivery address. Errors: The record is in error status if this field is blank. Alphanumeric, 32 positions; required. |
Apt./suite (Apartment/suite) |
The apartment number or suite number associated with the customer's delivery address. Follow these steps to enter an apartment or suite address:
Addresses must conform to United States Parcel Service (USPS) address formatting field description standards. For example, always precede the apartment or suite number with the appropriate abbreviation (for example, APT or STE). Alphanumeric, 10 positions; optional. |
Address |
Three additional lines of the customer's delivery address. If the address represents a post office box, you must enter P.O. Box on the first line to meet USPS delivery regulations. Alphanumeric, three 30-position lines; optional. |
Postal code |
The postal or zip code for this customer. This code represents a delivery area. Required? A postal code is required only if the Require postal code? flag for the country is selected; see Setting Up the Country Table (WCTY). Postal code validation: If a postal code is required, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP). Errors: The record is in error status if the Require postal code? flag for the country is selected and the SCF of the postal code is blank or invalid, or if the postal code does not match the state. See Catalog Request Interface Errors. Alphanumeric, 10 positions; required or optional based on country. |
City |
The city where the customer lives or receives mail or shipments. Alphanumeric, 25 positions; required. |
St (State) |
The state or province where the customer lives or receives mail or shipments. Defined where? State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Required? A state is required only if the Require state? flag for country is selected. See Setting Up the Country Table (WCTY). SCF validation: If the Require postal? flag for the country is selected, the system validates that the state you enter is assigned to the SCF associated with the postal code. See Working with SCF Codes (WSCF) for background. Errors: The record is in error status if the Require state? flag for country is selected and there is not a valid state code. State codes must be in uppercase. Alphanumeric, 2 positions; required or optional based on country. |
Country |
The code for the customer's country. Country codes are defined in and validated against the Country table. The Default Country for Customer Address (B17) system control value defaults here when you submit the catalog request for processing if the country code was not already specified for the record. Errors: The record is in error status if there is not a valid country code. Country codes must be in uppercase. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required. |
Delivery code |
Identifies a business (commercial) or residential address. Used to calculate shipping charges for shippers that use rate tables (such as U.P.S.).
Errors: The record is in error if the delivery code is blank or invalid. Delivery codes must be in uppercase. Required. |
Phone numbers |
The customer's day, evening, and third (fax or mobile) phone numbers. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number.Alphanumeric, 14 positions each; optional. |
Ext (Extension) |
The extension of the customer's day, evening, and third (fax or mobile) phone number. Note: The extension for the third phone number is not updated through the catalog request upload process.Numeric, 4 positions; optional. |
Email address |
The customer's email address. Alphanumeric, 30 positions; optional. |
OptIn (Opt in/opt out) |
Indicates the preferred method of correspondence for the customer email address. Valid values are:
Defaults from the Opt in/opt out field for the sold-to customer, and if blank, defaults from the Default Opt In/Opt Out Flag (G97) system control value, but you can override it. Note: The above value uses the letter O, not the number 0 (zero).Required. |
Create catalog request? |
Indicates whether to create a catalog request. Valid values are:
Regardless of the setting in this field, the system may still create a new customer sold to; see the Perform duplicate check field. Errors: The record is in error status if this field is not set to a valid value. |
Perform duplicate check? |
Indicates whether to perform a match code check to determine whether the catalog request represents a new customer. Valid values are:
Errors: The record is in error status if this field is not set to a valid value. See Setting Up Match Codes (MMCH) for more information on match codes and duplicate checking. |
File type |
Indicates the source of the catalog request. This information is not validated against any tables in Order Management System. Errors: The record is in error status if this field is blank. In this case, you cannot correct the record at this screen; instead, you can delete the record and recreate it, or update the table directly. Alphanumeric, 10 positions; display-only. |
Request date |
The date when you received the request. The system does not update this field. If a date was indicated in the catalog request interface record, it appears here; however, you can change it. Numeric, 6 positions (in user date format); optional. |
Source |
A code that identifies a list of names for this catalog mailing. The source code drives marketing, pricing, and freight information on an order. Overrides: When you submit the requests for processing, the system assigns the Default Source Code for Batch Catalog Requests (D37)system control value if a valid source is not specified for the catalog request. In this situation, the offer for the record is reset, if necessary, to match the default source code. Source codes are defined in and validated against the Source Code table. See Working with Source Codes (WSRC). Alphanumeric, 9 positions; required. |
Offer |
The code for the catalog that the customer is requesting. Overrides: The system defaults or overrides the offer in the catalog request record when you submit the requests for processing so that it matches the source code. If the offer is not specified, the job defaults the offer associated with the source code. If the offer does not match the source code, the job replaces this offer with the offer associated with the source code. Errors: The record is in error status if both source code and offer are blank when you submit the records for processing. However, the record is corrected the next time you submit records for processing. The reason this correction occurs is that, the first time you submit the records, the job sets the source code field to the Default Source Code for Batch Catalog Requests (D37) The second time you submit the records, the job updates the Offer field to match the assigned source code. Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR) for more information. Alphanumeric, 3 positions; required. |
Entity |
The business unit in your company associated with the catalog request. If the Track Customer History at Entity Level (F89) system control value is selected: When you submit the requests for processing, the system creates a Customer Sold To Entity record for the entity specified for the catalog request, if any. If no entity is specified for the catalog request, the system creates a Customer Entity record for the entity associated with the Default Source Code for Batch Catalog Requests (D37) system control value. (An entity is associated with a source code through the division assigned to the source code.). Errors: The record is in error status if this field is not set to a valid entity. If the entity is not specified for the record, the system resets the entity to match the source code. Entity codes are defined in and validated against the Entity table. See Working with Entities (WENT). Numeric, 3 positions; required. |
Display Catalog Request Screen
To display: Select Display for a record at the Work with Catalog Request Interface Screen to advance to the Display Catalog Request screen. You cannot change any information on this screen. See Change Catalog Request Screen for field descriptions.
Processing Requests
Purpose: Select Submit at the Work with Catalog Request Interface Screen to submit requests for processing. The system submits the job CATALOGREQ, which:
- Checks each open record in the Catalog Request Interface table for errors. Each record that has an error is flagged with an error status (E).
- Checks for duplicates:
-
If the record's Perform duplicate check? flag is selected, the job checks the catalog request against existing customer sold to records based on match code. If the catalog request's match code is the same as an existing customer's, the job does not create a new customer; instead, it uses the existing customer. (If more than one customer record has the same match code, the job uses the first matching customer it finds.) See Setting Up Match Codes (MMCH).
-
If the record's Perform duplicate check? flag is unselected, or if no customer records match the catalog request, the job creates a new sold to customer. See Creating a New Customer.
-
- Creates the catalog request. The job creates a catalog request only if the record's Create catalog request? flag is selected. You can review or process these catalog requests through the Work with Catalog Request menu option; see Entering Catalog Requests (WCAT).
- Creates the Print Request Interface Report and the Print Catalog Request Interface Errors Report.
- Deletes each processed record from the Catalog Request Interface table.
Catalog Request Interface Errors
The following conditions put a catalog request in an error (E) status:
- Type field is blank
- Invalid postal code or SCF, or postal code does not match state
- State is not valid, or does not match country
- Country code is invalid
- Both last name and company name are blank
- No street address
- Entity is invalid
- Delivery code is invalid or blank
- Create catalog request? flag is invalid or blank
- Perform duplicate check? flag is invalid or blank
- Both offer and source code are blank (but this error is corrected when you next submit the records for processing if the Default Source Code for Batch Catalog Requests (D37) is assigned to the record)
- Offer is invalid
- Source is invalid
Certain errors, such as a missing source code, country, or entity, are corrected by the batch job during processing based on system control value defaults. See Change Catalog Request Screen.
Catalog Request Related System Control Values
System Control Value | Description |
---|---|
Default Country for Customer Address (B17) |
If a country code is missing from the catalog request, Order Management System defaults the country code defined in this system control value to the catalog request. |
Default Delivery Code for New Order Entry Customers (D13) |
If a delivery code is missing from the catalog request, Order Management System defaults the delivery code defined in this system control value to the catalog request. |
Default Source Code for Batch Catalog Requests (D37) |
If both a source code and offer code have not been defined for the catalog request, Order Management System defaults the source code defined in this system control value to the catalog request. The source code indicates the offer (catalog) to mail to the customer. |
Edit for Duplicate Catalog Requests (E46) |
Defines whether Order Management System checks for duplicate records when you create a new catalog request. If a duplicate is found, Order Management System does not create a new catalog request and instead uses the existing request, resetting the Printed flag to No if necessary. |
Defines whether a catalog request received through the e-commerce qualifies as a match to an existing record based on match code, even if the first name is not exactly the same. |
|
Defines the value that defaults to the Opt-in/Opt-out field for the catalog request and customer sold to record. The opt-in flag indicates whether e-mail is the preferred method of correspondence for a customer. If the catalog request includes a value in the bill_to_opt_in flag, the system defaults this value to the catalog request and the customer sold to record. If the customer sold to record already has an opt-in value, the system overrides this value with the opt-in value passed in the catalog request. If the catalog request does not contain a value in the sold_to_opt_in flag, the system defaults the value defined in the Default Opt In/Opt Out Flag (G97) system control value. |
|
If the Require Customer Class in OE, WCAT, and WCST (H85) system control value is selected, this customer class is assigned to new customers you create through the catalog request interface. |
Creating a New Customer
If the catalog request does not match an existing customer based on match code, or if match code duplicate checking was not selected for the catalog request, the system creates a new sold to customer based on the information in the catalog request. The system uses the following information to create the new customer:
From the catalog request:
- Name and address information
- Delivery code
- Daytime, evening, and third (fax or mobile) phone numbers, and the extensions for the daytime and evening numbers
- Mail code and mail flag: from the allow_mail setting
- Rent flag: from the allow_rent setting
- Opt in/opt out: from the bill_to_opt_in setting
The country and source code may have defaulted from the Default Country for Customer Address (B17) and Default Source Code for Batch Catalog Requests (D37) settings in the System Control table.
Additional defaults from the System Control table:
- Associate flag: uses the setting from the Default Associate Code (D09) system control value
- Mail flag: uses the setting from the Default Mail Name (D10) system control value if it was not specified in the catalog request
- Rent flag: uses the setting from the Default Rent Name (D11) system control value if it was not specified in the catalog request
- Mail code: uses the setting from the Default Mail Name (D10) system control value if the allow_mail setting was not specified in the catalog request
- Opt-in/opt-out flag: uses the setting from the Default Opt In/Opt Out Flag (G97) system control value if it was not specified in the catalog request
- Customer class: uses the setting from the Default Customer Class in Order Entry (D63) system control value if the Require Customer Class in OE, WCAT, and WCST (H85) is selected
The Current mail type and Original mail type fields are set to C (catalog request).
Oracle Retail Customer Engagement customer integration: When you use the Oracle Retail Customer Engagement customer integration, if you create a customer through the catalog request interface, Order Management System sends the customer’s name, address, email address, phone numbers, and contact permissions to Oracle Retail Customer Engagement so that the customer records in the two systems are synchronized. See the Customer Engagement Customer Integration for more information.
Purge Catalog Request History (PCRH)
Purpose: Use this option to delete outdated records from the Catalog Request History table. This table provides an historical record of catalog requests within your company, even after you have purged outdated catalog requests. You can include this information in reports, such as the Campaign Performance Report; see Print Campaign Performance Reports (PCPR) for more information.
How to display this screen: Enter PCRH in the Fast path field at the top of any menu, or select Purge Catalog Request History from a menu.
Completing this screen:
- Complete the Purge date field to indicate the earliest date for which you want to retain Catalog Request History records. Any records for catalog requests created earlier than this date will be purged.
- Select Accept to submit the PRG_CATHST job, which purges the records.
Managing Soldouts and Backorders
In this part:
- Working with Soldout Controls (WSLD) shows you how to create, change, delete, and display soldout controls in the Soldout Control table.
- Processing Auto Soldout Cancellations (MASO) presents the screen you use to cancel soldout items from those orders that contain them.
- Generating Soldout Notifications (MSON) shows you how to use the Print Soldout Notifications screen to produce soldout notifications that you send to your customers.
- Purchase Order Layering and Backorder Notifications shows you how to use the Generate Backorder Cards function to print backorder notification cards and the Backorder Cancellation Register.
- Working with Held Detail Lines (WOHD) shows you how to use the Work with Order Hold Detail screen. You use this screen to work with items that were held because they were coordinate grouped with items canceled through Process Auto Soldouts.
- Working with Backorders Pending Cancellation (WBPC) shows you how to use this menu option to continue to work with backorders once you have generated a second notice if the FTC--second notice output system control value is set to FILE or FILE/PRINT.
- Processing Item Substitutions (PSUB) shows you how to cancel all open, unreserved order lines for a particular item and add a substitute item to each order.
Working with Soldout Controls (WSLD)
Soldout control codes define which calculation the system uses to determine when to sell out an item. When a customer orders a soldout item in order entry or order maintenance, the order line is automatically closed with a status of Soldout. The soldout units and dollars are updated in the Item table, Item/Offer table, Source Code table and order history tables. You can define a soldout control code for an item in the S/O control field on the second item screen in item maintenance, or on the SKU screen if the item has SKUs. If you do not define a soldout control code for an item or SKU, it will never sell out automatically in order entry/maintenance.
Brokered backorders? If you use the Order Broker to fulfill backordered items, then unavailable items are otherwise eligible for brokering are submitted to the Order Broker rather than selling out. See Brokered Backorders for a general overview, and see Brokering Items with Soldout Control Codes for details.
Pre-orders: Pre-order processing sells out brokered backorders automatically if the pre-order calculation indicates that there will not be a sufficient quantity of the item received on purchase orders for Order Broker to fulfill the orders. See Enterprise Order Integration (Future Receipts and Active PO/Pre-Order Processing) for more information.
In this topic:
- Soldout Calculation
- Soldout Calculation for Eligible Warehouses
- What Happens when you Sell Out an Item in Order Entry?
- Process Auto Soldouts
- Disregarding Soldout Controls for Non-Allocatable Warehouses
- Projected Returns
- Work with Soldout Control Screen
- Create Soldout Control Screen
Soldout Calculation
The Status field for the soldout control code defines the calculation the system uses to determine when to sell out the item if it is not eligible for fulfillment through the Order Broker Integration; see Brokered Backorders for an overview.
Status | Description |
---|---|
Sell Out Immediately |
Sell out immediately, regardless of available on-hand stock. You would use this status code if you have open orders for an item that you now determine is sold out. Only items with this status are eligible for cancellation through Processing Auto Soldout Cancellations (MASO). |
Include On Order Quantity in Soldout Calculation |
Sell out when the available quantity is less than or equal to zero, including the on order quantity and projected returns in the soldout calculation: (On-order + on-hand + projected returns) - reserved < 0 The system includes projected returns if you specify a quantity in the Projected return field for an item or SKU; see Projected Returns. The system includes the on-order quantity for pending putaway detail records that are associated with a pending putaway warehouse whose “final destination” warehouse is allocatable in this calculation; see Pending Putaway Overview. |
Exclude On Order Quantity in Soldout Calculation |
Sell out when the available quantity is less than or equal to zero, excluding the on order quantity and projected returns in the soldout calculation: On-hand - reserved < 0 |
Soldout Calculation for Eligible Warehouses
When the system sells out an item with a soldout control code of 2 or 3, the system limits the soldout calculation to the eligible warehouses instead of all allocatable warehouses.
- If you define a warehouse override for the order or order line, the system limits the soldout calculation to that warehouse.
- If a warehouse list is associated with the SCF for the order ship to, the system limits the soldout calculation to the warehouses for the selected warehouse list and the item’s primary warehouse.
- If a warehouse override has not been defined, or the SCF for the order ship to is not associated with a warehouse list, the soldout calculation includes all allocatable warehouses.
Note:
When the system sells out an item with a soldout control code of 1, the soldout calculation includes all allocatable warehouses.Example 1: Item SO10 exists in the following warehouses.
Warehouse | Open PO Qty | PO# | On Hand | Reserved | Available |
---|---|---|---|---|---|
206 |
20 |
112 |
10 |
5 |
5 |
207 |
0 |
201 |
20 |
20 |
-5 |
You add item SO10 to an order for 10 units. A warehouse override has been defined for the order for warehouse 207. The soldout code assigned to item SO10 is 2, which means the system uses this calculation to determine when to sell out the item:
(On-order + on-hand + projected returns) - reserved < 0
Because a warehouse override has been defined, the system only includes warehouse 207 in the soldout calculation:
(0 + 20 + 0) - 20 = 0
Because the quantity is not greater than 0, the system sells out the item.
If a warehouse override had not been defined, the system would have reserved the item because the soldout calculation would have included warehouses 206 and 207:
(20 + 30 + 0) - 25 = 25
Example 2: Item SO20 exists in the following warehouses.
Warehouse | Open PO Qty | PO# | On Hand | Reserved | Available |
---|---|---|---|---|---|
206 |
20 |
112 |
10 |
5 |
5 |
207 |
0 |
201 |
20 |
20 |
-5 |
601 |
25 |
356 |
30 |
20 |
10 |
602 |
40 |
475 |
40 |
25 |
15 |
You add item SO20 to an order for 1 unit. The SCF for the order ship to on the order is associated with a warehouse list containing warehouses 601 and 602. The soldout code assigned to item SO10 is 3, which means the system uses this calculation to determine when to sell out the item:
On-hand - reserved < 0
Because a warehouse list has been defined, the system only includes warehouses 601 and 602 and the item’s primary warehouse 206 in the soldout calculation:
80 - 50 = 30
Because the quantity is greater than 0, the system does not sell out the item.
Example 3: Item SO30 exists in the following warehouses.
Warehouse | Open PO Qty | PO# | On Hand | Reserved | Available |
---|---|---|---|---|---|
206 |
20 |
112 |
10 |
5 |
5 |
207 |
0 |
201 |
20 |
20 |
-5 |
601 |
25 |
356 |
30 |
20 |
10 |
602 |
40 |
475 |
40 |
25 |
15 |
You add item SO30 to an order for 1 unit. A warehouse override is not defined and the SCF for the order ship to is not associated with a warehouse list. The soldout code assigned to item SO30 is 3, which means the system uses this calculation to determine when to sell out the item:
On-hand - reserved < 0
Because a warehouse override and a warehouse list has not been defined, the system includes all allocatable warehouses in the soldout calculation:
100 - 70 = 30
Because the quantity is greater than 0, the system does not sell out the item.
What Happens when you Sell Out an Item in Order Entry?
When you enter an item in order entry that is sold out, the system:
- adds the item with a status of Soldout
- does not increase the order totals
- does not display an ordered quantity or extended price (although the unit price does appear)
The soldout units and dollars are updated in the Item table, Item/Offer table, Source Code table and Order History tables.
If a partial quantity of the item is sold out on the order line, the appropriate quantities and prices display. For example, if the customer orders 10, 8 units reserve or go on backorder, and 2 units sell out, the totals for the order line reflect 8 units. The order line status will be open.
See Working with Items on the Order.
Accompanying items: If an accompanying item is associated with a soldout item, the system also sells out the accompanying item.
Promotional pricing incentives: If a soldout item has promotional pricing incentives associated with it, the incentives will still be offered to the customer during Order Entry.
Set items: See Reserving Inventory for Set Orders for a discussion of how the system handles soldout control codes assigned to set items and their components.
Process Auto Soldouts
Use the Process Auto Soldouts menu option to cancel orders for items that have become sold out since the time you entered them.
When you process auto soldouts, you have the option of updating the soldout control code in the SKU table automatically for each backordered item. See Processing Auto Soldout Cancellations (MASO).
Note:
You can define a soldout control code in the Default Soldout Control Code (D72) system control value. This code will default when you create items and SKUs, although you can override it.Disregarding Soldout Controls for Non-Allocatable Warehouses
If the Disregard Soldout Controls for Non-Allocatable Warehouses (J27) system control value is selected, the system disregards soldout control rules for inventory reserved against a non-allocatable warehouse.
- When you enter an item in order entry, the system reserves the item against the non-allocatable warehouse, regardless of the soldout control code defined for the item. If the item cannot be reserved, the system backorders the item in the non-allocatable warehouse.
- When you process auto soldouts, the system bypasses any order associated with a non-allocatable warehouse. The system considers an order associated with a non-allocatable warehouse if:
- A non-allocatable warehouse is defined for one or more lines on the order, or
- A non-allocatable warehouse is defined as the backorder warehouse for one or more lines on the order, or
- A non-allocatable warehouse is defined on the order header.
You can reserve items against a non-allocatable warehouse if the Reserve from Non-Allocatable Warehouse (J25) system control value is selected.
Brokered backorders: Even when the item’s OROB eligible field is selected, the item reserves against the non-allocatable (retail) warehouse if the order type is associated with that warehouse.
Projected Returns
If you expect to be able to fulfill a certain number of backorders for an item using returns from your customers, you can prevent that number of orders from selling out automatically. For example, if you currently did not have any of item AA100 on hand, but you project at least 10 units will be returned, you can put the next 10 units ordered on backorder instead of having them sell out; then, when you receive the returned units from the customers, you can fulfill these backorders.
How to set the projected return total: Use the Projected returns field to specify the number of units you expect to receive in customer returns toward the fulfillment of backorders. This field appears on the Create SKU 1 of 2 (With Overrides) Screen, the Create SKU 2 of 2 (With Overrides) Screen, or the Create Item (Base Information) Screen for non-SKU’ed items.
When a return is processed, the system automatically subtracts the number of units returned from the number you initially entered in the Projected returns field. The number will never be less than 0, however. For example, if you initially enter a value of 10 in this field, and 11 units of this item are returned, the Projected returns field will show a value of 0 when the returns are processed. Updating this field does not affect any orders already entered.
Note:
The system checks this field only if the item has a soldout control value of Include On Order Qty in Sold Out Calculation. If the item has a soldout control value of Sell Out Immediately or Exclude On Order Qty in Sold Out Calculation, the system does not retain any units from selling out based on projected returns. The system does not consider this field when determining whether a backordered line is eligible for fulfillment through the Order Broker; see Brokered Backorders for background.Projected return calculation: If you specify a number of units in the Projected returns field, this number is included in the total number of units that the system will backorder before selling out the item. When an item has a soldout control value of 2, this total includes:
- on-order quantity (on unreceived purchase orders)
- projected return quantity
For example, item AA100 has
- {on-hand quantity 5}
- on-order quantity = 20
- projected return quantity = 10
- {total quantity to reserve = 5}
- total quantity to backorder =30
If you enter an order for 35 units or fewer, the item will be backordered and not sold out. However, if there were already a backordered quantity of 20, only orders for 15 units or fewer would be backordered and not sold out.
Brokered backorders: The system does not consider the projected returns quantity when determining whether to assign the item to the Order Broker for fulfillment. See Brokered Backorders for an overview, and Brokering Items with Soldout Control Codes for details.
Work with Soldout Control Screen
Purpose: Use this screen to create, change, delete, and display these codes.
How to display this screen: Enter WSLD in the Fast Path field at the top of a menu or select Work with Soldout Controls from a menu.
Field | Description |
---|---|
Code |
Represents the item soldout control. Alphanumeric, 2 positions; optional. |
Description |
The description of the soldout code. Alphanumeric, 30 positions; optional. |
Status |
Represents the soldout status. Valid Values:
Optional. |
Screen Option | Procedure |
---|---|
Create a soldout control |
Select Create to advance to the Create Soldout Control Screen. |
Change a soldout control |
Select Change for a soldout control to advance to the Change Soldout Control Screen. At this screen you can change any information except the soldout control code. See Create Soldout Control Screen for field descriptions. |
Delete a soldout control |
Select Delete for a soldout control to delete it. Delete soldout control records with caution. The soldout control code is assigned at the item level. When the control applies to a item on an order, the status of the item remains open if you delete the control code before notifying the customer. You may wish to generate a report identifying the orders that might be affected before deleting the code. See Processing Auto Soldout Cancellations (MASO). Note: You can delete this code even if it is assigned to an item. The next time you maintain the item you will receive a message indicating that the code assigned to the item is not found. |
Display a soldout control |
Select Display for a soldout control to advance to the Display Soldout Control Screen. You cannot change any information on this screen. See Create Soldout Control Screen for field descriptions. |
Create Soldout Control Screen
Purpose: Use this screen to create soldout control codes.
How to display this screen: At the Work with Soldout Control Screen, select Create.
Field | Description |
---|---|
Code |
A code that defines the type of soldout handling that applies to an item. You enter this code in the S/O control field on the second item screen in item maintenance, or on the SKU screen if the item has SKUs. If you do not enter a soldout control code for an item or SKU, it will never sell out automatically in Order Entry or Order Maintenance. You can define a soldout control code for:
See the Sts (Status) field. Alphanumeric, 2 positions. Create screen: required. Change screen: display-only. |
Description |
Text that describes the code. Alphanumeric, 30 positions; required. |
Sts (Status) |
A number that directs the system whether to close a soldout line item during Order Entry or Order Maintenance. Valid values are:
If you specify a quantity in the Projected return field for an item or SKU, this quantity is also included in the calculation above. See Projected Returns. The system includes the on-order quantity for pending putaway detail records that are associated with a pending putaway warehouse whose “final destination” warehouse is allocatable in this calculation; see Pending Putaway Overview.
Required. |
Processing Auto Soldout Cancellations (MASO)
Purpose: Process auto soldout cancellations when you want to automatically cancel soldout items that were ordered before the item sold out, or to print a list of all such items.
Overview: When you process auto soldout cancellations, the system:
- Reads every item or SKU that has a soldout control status of 1 (sell out immediately).
- Checks the setting of the Auto Soldout Cancel Reason (C20) system control value.
- Locates every matching open, fully backordered, unreserved line item on open or held orders. Also, locates every matching open, unreserved line item on quotes.
- Looks at the setting of the Disregard Soldout Controls for Non-Allocatable Warehouses (J27) system control value. If this system control value is selected, the system bypasses any order that is associated with a non-allocatable warehouse.
- Cancels each of the selected items.
- Automatically recalculates freight and tax.
- Removes any duty charge from the Handling field that is associated with the soldout item.
- Optionally, closes any positive or negative additional charges on orders where processing auto soldouts has the effect of closing the order (if you select the Open charges if order closes field when you process auto soldouts).
- Writes a record, displayed at the Display Order Line History Screen, indicating that the item has been cancelled.
- Generates notification records that you can use to generate soldout cards, emails, or XML messages using the Print Soldout Notifications function (See Generating Soldout Notifications (MSON)).
- Generates the Auto Soldout Register.
Note:
- Orders that are suspended at the time you process auto soldout cancellations do not sell out. You can sell out the items on these orders at a later time, either by processing auto soldouts again or through Order Maintenance.
- Order lines that are partially reserved are not automatically cancelled by this process.
Stored value card authorization reversal: If a stored value card payment is associated with a cancelled item and has an open, unused authorization amount, the system generates a stored value card authorization reversal; see Stored Value Card Authorization Reversal.
Retail pickup or delivery order: If you sell out an order line on a retail pickup or delivery order received from the Order Broker, the system sends a status update to the Order Broker indicating the order was Rejected. The Order Broker then attempts to reassign the order to another location for fulfillment. The Order Broker record’s status in Order Management System changes to Rejected. See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for an overview.
Pick slip preparation: When you process auto soldout cancellations, the system performs pick slip preparation:
- The system REMOVES any pick slip preparation from the order.
- Once the system processes auto soldout cancellations, the system EVALUATES the order to determine if it is eligible for pick slip preparation.
- If the order is eligible for pick slip preparation after the changes to the order have been made, the system RE-APPLIES pick slip preparation to the order.
See Preparing Orders for Pick Slip Generation for processing details.
Reviewing order history: When you review a soldout line in Order Inquiry, you can determine how the item was sold out through the Display Order Line History Screen (select Order History) as follows:
- If the item was sold out through Sell Out, the quantity is negative and the name of the user who sold out the item is listed
- If the line sold out automatically in Order Entry because there was a soldout control code assigned to the item, the line history has a positive quantity, and the name of the user who entered the order is listed
- If the line was sold out through Process Auto Soldouts, the quantity is negative and no user name is listed
Note:
When you sell out an item, the system also writes a message, visible on the Display Order History Screen, indicating that the order was maintained.Holding coordinate grouped items: You have the option of placing any items coordinate grouped with sold out items on hold at the time you process auto soldouts, if you select the Hold related coordinate group lines field. In this case, the system also generates the Order Hold Detail Report. You can use this report to contact the customers and see if they still want the coordinate grouped items.
Retaining items from sellout: You have the option of retaining a quantity of an item from selling out if you expect to receive some units in the near future that you can use to fulfill these orders. For example, if you expect a certain number of returns on an item, you might choose to keep an appropriate number of order lines open when you process auto soldouts. In this case, the system uses the Sold out retention method system control value to determine whether to retain your oldest or newest orders containing the backordered item. The system also produces the Auto Sold Out Retained Order Register. See Retaining Item Quantities for an overview of this process and more information.
Unfulfillable through Order Broker? If a backordered item is brokered to Order Broker’s Order Broker, but the Order Broker cannot fulfill the item, the item might sell out automatically.
Example: An item is unavailable in the warehouse, so the system assigns it to the Order Broker for fulfillment; however, the Order Broker cannot find a location to fulfill the item, and rejects the item as unfulfillable. In Order Management System, the item is assigned a soldout control value indicating to include the on-order quantity of any open purchase orders before selling out the item, but there are no open purchase orders. As a result, the unfulfillable item sells out automatically after it is rejected by the Order Broker.
When you use the Process Auto Soldouts option, any unfulfillable items that have sold out automatically after rejection by the Order Broker are listed on the Auto Soldout Register, regardless of whether the items are assigned a soldout control value to sell out immediately.
After you have used the Process Auto Soldouts option, the item is then eligible to have a soldout notification generated through the Generating Soldout Notifications (MSON) option, even if you did not select the Update orders option at the Process Auto Sold Outs Screen.
The same process applies if the Order Broker returns an error for a brokered backorder.
See Brokered Backorders for background on fulfilling backorders through integration with Order Broker’s Order Broker.
In this topic:
Process Auto Sold Outs Screen
Purpose: Use this screen to cancel all lines for sold out items on quotes and orders. The order must be open or held and the item must be backordered (unreserved).
Notifications: You must generate soldout notifications as a separate step after you run Auto Soldouts. See Generating Soldout Notifications (MSON).
How to display this screen: Enter MASO in the Fast path field at the top of any menu or select Process Auto Soldouts from a menu.
Field | Description |
---|---|
Update orders |
Controls whether the system cancels order lines for sold out items. Valid values are:
|
Hold related coordinate group lines |
Controls whether the system places items on hold if they are on the same order with a sold out item and share a coordinate group code. The system does not create pre-generated picks for held items; see Selecting Order Lines for Pick Slip Preparation. You assign a coordinate group code to items or SKUs if they are related, such as a blouse and skirt, or a plate, cup and bowl. Your customers can order each item individually, but if coordinate grouped items are on the same order, the system forces these items to ship together. The system lists any held coordinate grouped items on the Order Hold Detail Report, produced when you process auto soldouts. You can then work with the held lines either through Order Maintenance or the Work with Order Hold Detail Function; see Working with Held Detail Lines (WOHD). Valid values are:
|
Delete open charges if order closes |
Controls whether the system deletes any additional charges, either positive or negative, if processing auto soldouts closes the order completely. The system does not write order history to indicate if additional charges were deleted in this way and simply removes the charges from the order. Valid values are:
|
Soldout control code to update SKUs |
Use this field to specify a soldout control code to assign to each item or SKU with a backorder quantity when you process auto soldouts. Assigning a soldout control code through this field might be useful to you if you use the Enter Quantity to Retain Screen to keep orders open for certain items. See Retaining Item Quantities for more information on how you might use this field. The soldout control code most recently entered in this field when you processed auto soldouts defaults, but you can override it. Soldout control codes are defined in and validated against the Soldout Control Code table. See Working with Soldout Controls (WSLD). Alphanumeric, 2 positions; optional. |
Instructions: Use the following steps to process auto soldouts:
- Complete each field on this screen and select OK.
- If you want to retain any item quantities, select Review Items to advance to the Enter Quantity to Retain Screen. You cannot advance to this screen unless the Update orders field is selected and you have selected a Sold Out Retention Method (E63). See Retaining Item Quantities.
- If you are not retaining item quantities, select Accept. If you selected the Update orders field, the system submits a batch job called AUTO_SO, which cancels the items on quotes and orders and generates the Auto Soldout Register. Each sold out order line has a status code of S. If you also selected the Hold related coordinate group lines field, the system also submits a batch job called ORD_HOLD, which places items coordinate grouped with the sold out items on hold and generates the Order Hold Detail Report. Each held order line has a status code of H. If you selected both fields, the system generates the Auto Soldout Register only.
Note:
If an order has more than one item that needs to be canceled because it is sold out, the system produces one soldout card per item, and writes one message line per item to the Order Line History table. Each message line indicates that the item was canceled because it was sold out.Screen Option | Procedure |
---|---|
Review items and specify quantities to retain from selling out |
select Review Items. See Retaining Item Quantities. |
Process auto soldouts |
Select Accept. |
Retaining Item Quantities
Process overview: When you process auto soldouts, you can prevent certain items or SKUs from selling out completely. For example, you might have sold all of your remaining stock of item AB100 and don't plan to order any more. However, based on this item's history you can expect to receive about 15 units as returns. In this case, you can use the Enter Quantity to Retain Screen to keep orders for 15 units of AB100 open when you process auto soldouts.
When you process auto soldouts, you have the option of resetting the soldout control code for each backordered item or SKU to the value you specify at the Process Auto Sold Outs Screen. Typically, you would reset the soldout control code to one with a status of Include On Order Qty in Sold Out Calculation or Exclude On Order Qty in Sold Out Calculation, since only items assigned a soldout control code with a status of Sell Out Immediately are eligible to be sold out by Process Auto Soldouts. Resetting the soldout control codes for the items and SKUs prevents them from appearing on the Enter Quantity to Retain Screen or being inadvertently sold out while you attempt to fulfill the retained orders.
When you no longer expect to receive any additional units of an item, you may still have retained orders on your system that you are not able to fulfill. In this case, you could change the soldout control code for the item or SKU back to a code with a status of Sell Out Immediately. You can then sell out the item completely the next time you process auto soldouts.
Which orders to retain? The sequence in which the system selects orders to retain is controlled by the Sold out retention method system control value. Valid settings for this field are:
- FIFO: oldest orders are selected for retention first
- LIFO: newest orders are selected for retention first.
The system selects an order line for retention only if it can retain the entire backordered quantity of the item on the line. For example, if you set a retention quantity of 3, and the first order line the system evaluates has a backordered quantity of 5, the system skips this order line and evaluates the next. The order line with the quantity of 5 is sold out.
Another example:
Item AB100 has a quantity to retain of 5 units and the soldout retention method being used is LIFO. The orders on the system, from newest to oldest, are:
Order Number | Units |
---|---|
2000 |
1 |
1999 |
5 |
1998 |
3 |
1997 |
3 |
1996 |
1 |
1995 |
1 |
The system evaluates the orders as follows:
- Order 2000 with 1 unit is evaluated first, and the order is retained.
- Order 1999 with 5 units is evaluated next, but there are just 4 units available for retention. The order is sold out.
- Order 1998 with 3 units is evaluated next, and the order is retained.
- Order 1997 with 3 units is evaluated next, but there is just one unit available for retention. The order is sold out.
- Order 1996 with 1 unit is evaluated next, and the order is retained.
- Order 1995 is sold out.
If there are no open order lines that meet the evaluation criteria (that is, the backorder quantity is less than or equal to the retention quantity), no orders are retained.
Enter Quantity to Retain Screen
Purpose: Use this screen to review the quantities of items eligible to be sold out when you submit the Process Auto Soldouts job, and to specify any item quantities you want to retain from selling out. The selected number of order lines remain open so that if, for instance, you expect to receive that quantity of returns, you can fulfill the orders using the returned items.
How to display this screen: Select Review Items at the Process Auto Sold Outs Screen. You can display this screen only if:
- you have selected a valid retention method in the Sold Out Retention Method (E63) system control value, and
- you have selected the Update orders field on the Process Auto Sold Outs Screen.
Note:
This screen displays each item or SKU assigned a soldout control code with a value of 1, which may include discontinued items for which you are not taking any more orders. To prevent such an item from appearing on this screen, you can change its soldout control code to one with a value of 2 or 3.Field | Description |
---|---|
Item |
The unit of inventory currently eligible for selling out. Each item or SKU assigned a soldout control code with a value of 1 appears on this screen. Alphanumeric, 12 positions; optional. |
SKU |
The item's unique characteristics, such as its color and size. Alphanumeric, three 4-position fields; optional. |
Qty to retain (Quantity to retain) |
The quantity of the item or SKU to prevent from selling out. You cannot enter a number greater than the backorder quantity. Numeric, 8 positions; optional. |
Qty/BO (Quantity on backorder) |
The total number of units of the item that is currently backordered. Numeric, 8 positions; display-only. |
Status |
The status of the item specified in the item or SKU table. The item status appears for SKU’d items if no status code is specified at the SKU level. Alphanumeric, 1 position; display-only. |
Instructions: Follow the steps below to complete this screen:
- Optionally, enter a quantity to retain for any selected items or SKUs. The system does not allow you to retain a quantity of an item that is greater than the backordered quantity.
- Select Accept to process auto soldouts. If you cancel from this screen, the system clears your entries in the retained quantities fields.
When you process auto soldouts from this screen, the system produces the Auto Sold Out Retained Order Register in addition to the Auto Soldout Register and the Order Hold Detail Report.
Generating Soldout Notifications (MSON)
Purpose: Use the Print Soldout Notifications function when you want to notify customers about soldout items being canceled from their orders.
Order type and sellouts in order entry and order maintenance: The order type and the way in which you sell out the item determines whether a customer receives a soldout notification. For example, you might set up phone orders so that the customer does not receive a notification when you sell out an item in order entry, because you can advise the customer during the phone call. However, you might choose to print a soldout notification for orders you receive through the mail or from the web storefront. The Soldout notifications field in the Order Type table determines whether to generate a notification for items that are sold out in order entry and order maintenance.
Processing auto soldouts: The Processing Auto Soldout Cancellations (MASO) menu option generates a notification for each item it sells out, regardless of order type.
Periodic function: You can use the PFSDOUT periodic function (program name: CSSDOUT) to generate soldout notifications. See Scheduling Jobs.
Email or XML notifications: The system sends an email notice to the customer rather than generating a document for printing if the order is eligible. See When Does the System Generate an Email Notification? for an overview. If the order is eligible for an email notification but the XML only? flag on the soldout notification email template is selected, the system generates the Outbound Email XML Message (CWEmailOut) instead of sending an email. See the Credit Card Credit Acknowledgement Email Sample and Contents and the Sample Soldout Notification XML Message for examples.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Email template: You can use the Working with Entities (WENT) menu option to create an entity-level soldout notification email template, and the Working with E-Mail Notification Templates (WEMT) menu option to create a default company-level soldout notification template. The template specifies the text to print above and below the standard soldout notification information. Also, the Soldout Notification E-Mail Program (G96) system control value defines the format of the notification email.
Save in email repository? The Write Outbound Email to Email Repository (H99) system control value controls whether email notifications are stored in correspondence history. See this system control value for more information on identifying and reviewing outbound emails for a customer.
Unfulfillable through Order Broker? If a backordered item is brokered to Order Broker’s Order Broker, but the Order Broker cannot fulfill the item, the item might sell out automatically.
Example: An item is unavailable in the warehouse, so the system assigns it to the Order Broker for fulfillment; however, the Order Broker cannot find a location to fulfill the item, and rejects the item as unfulfillable. In Order Management System, the item is assigned a soldout control value indicating to include the on-order quantity of any open purchase orders before selling out the item, but there are no open purchase orders. As a result, the unfulfillable item sells out automatically after it is rejected by the Order Broker.
When you use the Process Auto Soldouts option, any unfulfillable items that have sold out automatically after rejection by the Order Broker are listed on the Auto Soldout Register, regardless of whether the items are assigned a soldout control value to sell out immediately.
After you have used the Process Auto Soldouts option, the item is then eligible to have a soldout notification generated through the Generating Soldout Notifications (MSON) option, even if you did not select the Update orders option at the Process Auto Sold Outs Screen.
This same process applies if the Order Broker returns an error for a brokered backorder.
See the Brokered Backorders for background on fulfilling backorders through integration with Order Broker’s Order Broker.
In this topic:
Print Soldout Notification Screen
How to display this screen: Enter MSON in the Fast path field at the top of any menu or select the Print Soldout Notifications option from a menu.
Instructions: Follow these steps to print soldout notification cards, or to generate notification emails or the XML message (see When Does the System Generate an Email Notification?):
- Select OK to submit the print job; otherwise, select Exit to cancel.
- This submits the batch job SLDOUT_PRT. This job generates the Soldout Notification Card, soldout notification email (see Credit Card Credit Acknowledgement Email Sample and Contents), or the outbound XML message (see Sample Soldout Notification XML Message).
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
Note:
In order to generate soldout notifications, you need to specify a program in the Soldout Notification Print Program (E75) system control value. If no program is specified, the screen displays an error message:No soldout print program has been defined in SCV E75.
Order history message: The system also writes a message such as the following, which is visible on the Display Order History Screen:
S/O card generated-line 1
If the system sent an email notification or XML message to the customer rather than generating a PDF soldout notification, it also writes a message such as the following:
S/O Notice to ejohnson@example.com
Generate Backorder Notices (GBOC)
Use the Generate Backorder Notifications function to generate notices (cards, emails, or the Outbound Email XML Message (CWEmailOut)) informing customers when backordered items are expected to ship. The function automatically generates an initial (first) backorder notice if you select the Immediate B/O notice field at the Create Order Type Screen.
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
If you have defined a Number of Days to Delay Initial Backorder Notice (D89) in the System Control table, the system does not generate a notice for a backordered item unless you do not expect to ship the item until after the defined delay period.
Note:
Once an expected delivery date for a backordered item is expired or changed, the system automatically generates a backorder notice, regardless of the value in the Immediate B/O notice field.Typically, you would want to notify customers immediately about backordered items if they place an order through the mail or fax; you can inform customers who order by phone at the time you take their orders if an item they want is currently backordered.
Order Broker: If an order line is assigned to the Order Broker for fulfillment, this option does not generate backorder notices for the order line while the Order Broker request is in process; however, if the Order Broker cannot fulfill the order, the order line returns to standard backorder processing and is eligible for backorder notice generation.
See the Order Broker Integration for background.
Generate notice if purchase order changes? The FTC - Suppress Backorder Notice for Due Date Changes (L65) system control value controls whether to generate a backorder notice if you change the due date for the next expected purchase order to a later date, or cancel the purchase order.
Quotes? The system does not generate backorder notification emails for quotes; see Entering Pre-Order Quotes for an overview.
Instructions:
- Enter GBOC in the Fast path field at the top of any menu, or select Generate Backorder Cards from a menu.
- The system submits the BO_CARDS job and displays a confirmation message at the bottom of the screen.
- The job generates:
-
first, second, and continuing backorder cards (depending on the settings in the System Control table) using the Backorder Card Print Program (D04); see Backorder Card
-
first, second, and continuing email backorder notifications or the Outbound Email XML Message (CWEmailOut) rather than generating document notices for printing for certain customers; see When Does the System Generate an Email Notification?
- For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
-
- The job writes a message to the Order History table, such as:
1st B/O--line 2, ship date 11/15/06
Also, in the case of an email notification, the system writes an Order History message such as:
BO 1st Ntf to ejohnson@example.com.
This message indicates the user ID of the person who submitted the BO_CARDS job.
If using backorders pending cancellation: If the FTC--Second Notice Output (E68) system control value is set to FILE/PRINT or FILE, and the FTC -- Action after Second Notification (C70) value is set to CANCEL, the job creates records in the Backorder Cancellation Pending table (BOCANP) for each second notice. You can use Working with Backorders Pending Cancellation (WBPC) to continue to work with these orders. Your options include:
- advancing to order maintenance or standard order inquiry
- accepting a backorder delay
- canceling a group of backorders
- generating backorder notices
You can generate backorder notices through the Work with Backorders Pending Cancellation menu option only if the FTC--Second Notice Output (E68) system control value is set to FILE. The system submits the job SEC_NOTICE when you generate notices through this menu option. In this situation, the system writes two order history messages: one when you write the record to the Backorder Cancellation Pending table, and one when you actually generate the notice. Both messages are identical.
For more information:
Working with Held Detail Lines (WOHD)
Purpose: Use the Work with Order Hold Detail function to review or release coordinate grouped items that were held by Processing Auto Soldout Cancellations (MASO).
The Process Auto Soldouts function cancels all open, unreserved lines for any item with a soldout control code of “sellout immediately” defined in the Item table. If the item is coordinate grouped with other items, you have the option of placing the related items on hold at the time you process auto soldouts. Coordinate groups, identified by a code in the Item table, include items that you can sell separately, but should be shipped together when they appear on the same order. An example would be a matching skirt and blouse, or a cup, plate and bowl set.
You can use the Work with Order Hold Detail function to release held coordinate group items, or to advance to Order Maintenance. In Order Maintenance, you have the option of releasing the items, canceling them, selling them out or maintaining the order in any other way. When you release, cancel, or sell out the held item, you remove it from the Order Hold Detail table.
Note:
- The system places coordinate grouped items on hold only when related items are soldout through Processing Auto Soldout Cancellations (MASO), not when you sell out an item through Order Entry by selecting Sell Out, and not when an item sells out in Order Entry automatically because of a soldout control code in the Item table.
- This menu option does not display order lines put in hold status manually, or through a special handling format; see Putting a Line on Hold through a Special Handling Format.
In this topic:
For more information:
- Processing Auto Soldout Cancellations (MASO)
- Changing Item Detail Line Information in Order Maintenance
- Working with Existing Items (MITM) for more information on assigning coordinate groups or soldout controls to items.
Work with Order Hold Detail Screen
Purpose: Use this screen to review held coordinate group items, release the items, or advance to Order Maintenance.
How to display this screen: Enter WOHD in the Fast path field at the top of any menu or select Work with Order Hold Detail from a menu.
Field | Description |
---|---|
Batch |
The batch number assigned by the system when you processed auto soldouts. The system may reuse a batch number if all the items in the batch have been released or canceled. Numeric, 7 positions; optional. |
Order |
The number of the order that includes the soldout and held items. Numeric, 8 positions; optional. |
Seq |
The line number of the item on the order. Numeric, 5 positions; display-only. |
CG (Coordinate group) |
The coordinate group code assigned to the item in the Item table. Numeric, 3 positions; optional. |
Item no. |
This code represents a unit of inventory that you sell. Item codes are defined in and validated against the Item table. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; optional. |
Clr size wdth (SKU codes) |
The item's unique characteristics, such as its color and size. The SKU column headings defined in the System Control table display here. Alphanumeric, three 4-position fields; display-only. |
Description |
The description associated with the Item. Alphanumeric, 25 positions; display-only. |
Customer first name (Unlabeled field below the coordinate group code) |
The first name of the customer who placed the order. Alphanumeric, 15 positions; display-only. |
Customer last name (Unlabeled field below the SKU fields) |
The last name of the customer who placed the order. Alphanumeric, 25 positions; display-only. |
Phone number (Unlabeled field below the item description) |
The daytime phone number of the customer who placed the order. Alphanumeric, 14 positions; display-only. |
Screen Option | Procedure |
---|---|
Release an item |
Select Release for an item to release it. See Releasing Items. |
Advance to Order Maintenance |
Select Order Maintenance for an item to advance to Order Maintenance, where you can release the item, cancel it, sell it out, or maintain the order in other ways. When you cancel, release, or sell out the item, you remove it from the Order Hold Detail table. See Changing Item Detail Line Information in Order Maintenance. |
Batch release |
Select Batch Release. See Releasing Items. |
Print a list |
Select Print List to print the Order Hold Detail Report, listing all held coordinate group items. |
Releasing Items
Release an item: Select Release for an item at the Work with Order Hold Detail Screen to release it. The item disappears from the screen, and the status of the order line changes to open. The item is now eligible to print on a pick slip.
Release a batch: Select Batch Release at the Work with Order Hold Detail Screen to release an entire batch. You might need to release an entire batch at once if you processed an auto soldout inadvertently, or if you determine that the held items in the batch can be shipped alone without notifying customers.
Enter the number of the batch you want to release in this pop-up window. The system releases the batch, and all the held items within the batch disappear from the Work with Order Hold Detail Screen.
Pick slip preparation: When you release an item or batch from hold, the system determines whether the order is eligible for pick slip preparation; see Preparing Orders for Pick Slip Generation.
Working with Backorders Pending Cancellation (WBPC)
Purpose: Use the Work with Backorders Pending Cancellation menu option to work with orders and order lines that have been flagged for cancellation due to backordered items.
Options: The options available through this function are:
- order maintenance or standard order inquiry
- Inquiring into Item Availability (DIAV)
- changing the backorder dates for orders where the customer has accepted the delay
- canceling orders or order lines
- flagging an order to suppress or unsuppress generation of backorder notices
- generating backorder notices
- printing the Order Cancellation List by Item. You can also print this report through the Printing the Order Cancellation List (PBRI) menu option.
When available? The system creates records in the B/O Cancellation Pending table for order lines flagged for cancellation when you generate backorder notices through Generate Backorder Notices (GBOC) if:
- the FTC--Second Notice Output (E68) system control value is set to FILE or FILE/PRINT (If this system control value is set to PRINT, the system generates the backorder notices and does not save records in this file); and
- the FTC -- Action after Second Notification (C70) system control value is set to CANCEL.
Important:
Orders that are flagged for cancellation due to credit card decline but also would be eligible for cancellation due to backordered items are not visible or accessible through Working with Credit Card Cancellations (WCCC).Drop ship items: Drop ship items are not included in the B/O Cancellation Pending table.
Quotes: Orders flagged as pre-order quotes are not included in the B/O Cancellation Pending table; the system includes quotes once they are converted to an order; see Entering Pre-Order Quotes for an overview and required setup.
Cancellation email: The system generates an order or order line cancellation email or Outbound Email XML Message (CWEmailOut) to the customer if:
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
- you have specified an:
-
Order Line Cancellation Email Program (K79), if there is still at least one open line on the order and no order lines have shipped, or
-
Order Cancellation Email Program (K78), if you are canceling the last open line on the order, and
-
- the cancel reason code you use does not match the Cancel Reason Code to Suppress Email (L08), and
- the customer is eligible to receive email notifications; see When Does the System Generate an Email Notification?
See the Order Cancellation Confirmation Email Sample and Contents and the Order Line Cancellation Confirmation Email Sample and Contents for more information.
Retail pickup and delivery orders: If you cancel a retail pickup or delivery order received from the Order Broker, the system sends the Order Broker a status update indicating that the order has been canceled. This status indicates to the Order Broker that it should not attempt to find another location to fulfill the order. See Retail Pickup (including Ship-for-Pickup) or Delivery Orders for an overview.
Pick slip preparation: When you cancel an order, the system removes any pick slip preparation that has been applied to the order. When you cancel order lines, the system removes any pick slip preparation that has been applied to the order and then reevaluates the order for pick slip preparation; see Preparing Orders for Pick Slip Generation.
In this topic:
- Work with Backorders Pending Cancellation Screen
- Display Backorder Notice Screen
- Suppressing and Unsuppressing Notices
- Accepting the Delay
- Cancel Backordered Lines Window
For more information: See Printing the Order Cancellation List (PBRI).
Work with Backorders Pending Cancellation Screen
How to display this screen: Enter WBPC in the Fast path field at the top of any menu or select Work with Backorders Pending Cancellation from a menu.
Field | Description |
---|---|
Order # |
The number of the order flagged for cancellation due to the backordered item. Numeric, 8 positions; optional. |
Date |
The date you entered the order. Numeric, 6 positions (in user date format); display-only. |
SKU |
The item's unique characteristics, such as its color and size. Enter a valid SKU code to display orders that match your entry. Note: You can scan on SKU code with or without entering an item code.Alphanumeric, three 4-position fields; optional. |
Item |
The code representing the unit of inventory that is backordered. Alphanumeric, 12 positions; optional. |
B/O (Next backorder date) |
The next date when the order is eligible for a backorder notice. Numeric, 6 positions (in user date format); display-only. |
Cancel (Cancel date) |
The date when the order line is eligible for cancellation due to backorder. This date also appears on the order detail line (available by selecting Display for the item in standard order inquiry, or Change for the item in order maintenance, or by selecting the Detail option in streamlined order inquiry). See Cancel Backordered Lines Window. Numeric, 6 positions (in user date format); optional. |
Prt (Printed?) |
Indicates whether you have already generated a backorder notice (printed, emailed, or in the Outbound Email XML Message (CWEmailOut)) for this item. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Valid values are:
If the FTC--Second Notice Output (E68) system control value is set to FILE/PRINT, this field will be selected. If the system control value is set to FILE, this field will be unselected. (If the system control value were set to PRINT, you would not be able to use the Work with Backorders Pending Cancellation menu option to review orders.) |
Sup (Suppress printing?) |
Indicates whether to generate a backorder notice when you select Print Notices. Valid values are:
You can switch this flag from suppressed to unsuppressed, or vice versa, by selecting Suppress/Unsuppress Notice for the item. You select Print Notices to generate each unsuppressed notice. However, the FTC--Second Notice Output (E68) system control value must be set to FILE in order for you to generate notices this way; if not, a message indicates: E68 must be set to file. |
Screen Option | Procedure |
---|---|
Display complete backorder notice details |
Select Display for an item to advance to Display Backorder Notice Screen. |
Advance to standard order inquiry |
Select Order Inquiry for an item. See Order Inquiry. |
Advance to order maintenance |
Select Order Maintenance for an item. See Changing Item Detail Line Information in Order Maintenance. |
Advance to item inquiry |
Select Item Inquiry for an item. See Using Inventory Inquiry (DINI). |
Change the Suppress notice flag for an item |
Select Suppress/Unsuppress Notice for an item to unsuppress notice generation if it is currently suppressed, or to suppress notice generation if it is currently unsuppressed. The backorder notice will be eligible for generation when you select Print Notices. See Suppressing and Unsuppressing Notices. |
Remove the cancel date from an item because the customer accepts the delay |
Select Customer Accepts Delay for an item. See Accepting the Delay. |
Cancel a group of order lines based on cancellation date or item |
Select Cancel Group to display the Cancel Backordered Lines Window. |
Accept the delay for all order lines with the same item |
Select Accept Delay to display the Accept Delay for All Customers Pop-Up Window. |
Generate backorder notices and the Backorder Cancellation Register |
Select Print Notices. This option is available only if the FTC--Second Notice Output (E68) system control value is set to FILE. See Purchase Order Layering and Backorder Notifications, for report and notice samples and more information on generated emails. |
Print the Order Cancellation List |
Select Print Report to print the Order Cancellation List by Item. |
Unsuppress a group of notices by date range or item |
Select Unsuppress Group to display the Unsuppress Notices Window. |
Display Backorder Notice Screen
Purpose: Use this screen to review details about a backorder notice.
How to display this screen: Select Display for an item at the Work with Backorders Pending Cancellation Screen.
Field | Description |
---|---|
Order number |
The number of the order containing the backordered item. The ship-to number is separated from the order number by a hyphen. If there is only one ship-to address, the ship-to number will be 1. Order number: numeric, 8 positions. Ship-to number: numeric, 3 positions. |
Order line |
The line on the order where the backordered item appears. Numeric, 3 positions. |
Generation date |
The date when the backorder notice was generated; or, if the FTC--Second Notice Output (E68) system control value is set to FILE, the date when the record was written to the file. Numeric, 6 positions (in user date format). |
Cancellation date |
The date when the order is flagged for cancellation. The system writes this date to the Backorder Cancellation Pending table when you generate backorders. Note: This date does not update automatically based on changes to the Cancel date on the order detail line.Numeric, 6 positions (in user date format). |
Expected ship date |
The Due date from the next purchase order you expect to be able to fulfill the order. The system writes this date to the Backorder Cancellation Pending table at the time you generate backorder cards; it is not updated if you run Batch PO Layering afterward. In this situation, the Expected ship date that appears on the order detail line in standard or streamlined order inquiry may differ from the date that appears here. Numeric, 6 positions (in user date format). |
Printed |
Indicates whether the backorder notice has been generated (printed, emailed, or sent through the Outbound Email XML Message (CWEmailOut)). For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Valid values are:
|
Print date |
The date when the notice was generated. This field is blank if you have not yet generated the notice. Numeric, 6 positions (in user date format). |
Suppress notice |
Indicates whether the notice is eligible for generation when you select Print Notices. In order for notices to be eligible for generation, the FTC--Second Notice Output (E68) system control value must be set to FILE. Valid values are:
|
Suppressing and Unsuppressing Notices
Purpose: The system creates each backorder pending cancellation record with the Sup (Suppress?) flag selected, so that generating backorder notices is suppressed. If the FTC--Second Notice Output (E68) system control value is set to FILE, you have the option of unsuppressing notice generation for these records, either individually or by group, and generating these notices.
Why are notices suppressed? The notices are created in a suppressed status so that you can avoid generating notices unnecessarily. For instance, you might generate backorder cancellation records in advance of their backorder dates so that you can review and work with backorder notices before generation (based on the FTC--Number of Days Prior to Next Backorder Date to Generate Second Notice (E67) system control value).
If you determine that you will actually be able to fulfill orders in a reasonable time, you can use the accept delay option for an individual order or for a group of orders. Accepting the delay allows you to reserve and fulfill the order. See Accepting the Delay.
Unsuppress a notice individually: To unsuppress an individual notice for generation, select Suppress/Unsuppress Notice for the item at the Work with Backorders Pending Cancellation Screen. The Sup flag changes from Y to N.
You can also unsuppress notices by group through the Unsuppress Notices Window.
Suppress a notice: Similarly, you can suppress a notice that has been unsuppressed by select Suppress/Unsuppress Notice for the item at the Work with Backorders Pending Cancellation Screen. The Sup flag changes from N to Y.
You cannot suppress notices by group.
Unsuppress Notices Window
Select Unsuppress Group at the Work with Backorders Pending Cancellation Screen to unsuppress a group of notices for generation.
Field | Description |
---|---|
Generation date range |
The beginning and ending dates to include when unsuppressing backorder notifications for generation. Each backorder pending cancellation record created on or between these dates is unsuppressed. Two fields, numeric, 6 positions (in user date format); optional. |
Item |
The code representing the item whose backorder notifications you want to unsuppress for generation. If the item has SKUs, all SKUs are unsuppressed. Alphanumeric, 12 positions; optional. |
Completing this screen: Select Accept to submit the unsuppress. A message indicates that the notices have been unsuppressed based on date range or item (if you selected both, the messages specifies unsuppressing by item). Optionally, select Exit to cancel.
The Sup flag for each selected backorder record changes to N.
If you completed both the generation date range fields and the Item field, only backorder records that meet both criteria are unsuppressed. In other words, if you select a range of dates between July 1 and August 1, and the item AB100, only backorder records for AB100 between those dates is unsuppressed; a backorder record for AB100 generated on August 2 remains suppressed.
Accepting the Delay
Purpose: You can remove an order line from a cancellation pending status through the Work with Backorders Pending Cancellation Screen. You might want to do so if a customer has communicated a willingness to accept the delay for the item, or if you determine that you will receive the item and be able to fulfill orders within a reasonable amount of time. You can accept delay for an individual order or for all order containing a specific item.
What happens when you accept the delay? The system:
- deletes the backorder record from the Backorder Cancellation Pending table (and the line disappears from the Work with Backorders Pending Cancellation Screen);
- deletes the cancellation date from the order detail line (visible by selecting Display for the item in standard order inquiry, Detail for the item in streamlined order inquiry, or Change for the item in order maintenance)
- writes an order transaction history message indicating that the customer has accepted the delay for the item (visible by selecting Messages in standard or streamlined order inquiry)
- adds the amount of days specified in the Number of Days to Add for Accepted Delays (E69) system control value to the next backorder date visible by selecting Display for the item in standard order inquiry, Detail for the item in streamlined order inquiry, or Change for the item in order maintenance). The order line will be eligible for pending backorder cancellation again if you are not able to fulfill the order by that date.
The order line is then eligible for reservation and fulfillment when you receive a purchase order containing the item.
Accepting the delay for a single order: Select Customer Accepts Delay for an item at the Work with Backorders Pending Cancellation Screen to accept the delay for the item on that order only. Select OK at the confirmation window to confirm the acceptance. If you accept, the system performs the updates described above for the order.
Accept Delay for All Customers Pop-Up Window
Select Accept Delay at the Work with Backorders Pending Cancellation Screen to accept the delay for all orders containing a specific item and SKU.
Instructions:
- Enter the item code for which you are accepting the delay and any SKU codes.
- Select Accept to accept the delay, or select Exit to cancel. If you accept, a message indicates:
Accept delay for all customers processed.
If you select Accept, the system performs the updates described under Accepting the Delay for each backorder pending cancellation for this item and SKU.
Cancel Backordered Lines Window
Purpose: Use this window to cancel order lines if you do not expect to receive the items in time to fulfill the orders. Using this option may be more efficient than canceling the order lines individually through order maintenance.
To cancel: Select Cancel Group at the Work with Backorders Pending Cancellation Screen.
Note:
You cannot cancel an item that is reserved through this pop-up window; you need to use order maintenance.Field | Description |
---|---|
Select orders...(Number of days past cancellation date) |
Indicates how many days it must be past the order line's cancellation date for the order line to be included in the cancellation request. This field defaults to 0 (any order whose cancellation date is earlier than or the same as the current date will be canceled). Numeric, 3 positions; required. |
Item |
Indicates the item to select for cancellation. If the item has SKUs, you must also enter SKU information. Item: alphanumeric, 12 positions; required. SKU: three 4-position fields; required if the item has SKUs. |
Cancel reason |
The cancel reason to use when canceling the orders containing this backordered item. Cancel reason codes are defined in and validated against the Cancel Reason Code table. If the cancel reason you enter is set to reduce demand, the order status will be X (closed) when the order is canceled; otherwise, the order status will be C (canceled). See Establishing Cancel Reason Codes (WCNR). Numeric, 2 positions; required. |
Recalculate freight? |
Indicates whether to reduce the freight charge on the orders to reflect the item cancellation. Valid values are:
The Recalculate Freight Default (F62) system control value controls the default setting of this field, but you can override this default. |
Completing this window: Complete each field and select Accept Cancel Request to process the cancel request; otherwise, select Exit to cancel. A message displays informing you that the cancellation was processed. You can enter information for an additional cancel request, or select Exit to return to the Work with Backorders Pending Cancellation Screen.
The system cancels each order line (or the entire order, if the backordered item was the last open line on the order) using the cancel reason selected, and produces the Orders Canceled After Second Notice Report.
In addition, if a stored value card payment with an open, unused authorization amount exists on the order, the system generates a stored value card authorization reversal; see Stored Value Card Authorization Reversal.
Pick slip preparation: When you cancel an order, the system removes any pick slip preparation that has been applied to the order. When you cancel order lines, the system removes any pick slip preparation that has been applied to the order and then reevaluates the order for pick slip preparation; see Preparing Orders for Pick Slip Generation.
Printing the Order Cancellation List (PBRI)
Purpose: Use the Order Cancellation List by Item to review the order lines flagged for cancellation due to backorder.
You can select one of the fields on this screen, or leave these fields blank to include all orders pending cancellation for backorder on the report.
Select Items for B/O Cancellation Report Screen
How to display this screen: Select Print Report at the Work with Backorders Pending Cancellation Screen, enter PBRI in the Fast path field at the top of any menu, or select Print Backorder Cancellation Report from a menu.
Field | Description |
---|---|
Select vendor |
The vendor whose purchase order was open when the item(s) first became backordered. Vendor codes are defined in and validated against the Vendor table; see Working with Vendors (WVEN). Numeric, 7 positions; optional. |
Select buyer |
The buyer associated with the purchase order(s) that were open when the item(s) first became backordered. Buyer codes are defined in and validated against the Buyer table; see Working with Buyers (WBUY). Alphanumeric, 3 positions; optional. |
Select item |
The item that is backordered. You need to enter only the base item code for SKUed items. Item codes are defined in and validated against the Item table; see Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; optional. |
Completing this screen: After completing any desired fields, select Accept to generate the report. The job BO_CN_LIST produces the Order Cancellation List by Item.
Processing Item Substitutions (PSUB)
Purpose: Use the Process Substitute Items menu option to cancel any order lines for a given item and add a substitute item to each order.
Overview: When you use this menu option, you specify the item to cancel, the item to add, and the cancel reason to use for the substitution. Only open, unreserved order lines are eligible for item substitution. Items that reserve automatically, such as membership items, are not eligible. Also, order lines that have been submitted to the Order Broker for fulfillment are not eligible; see Order Broker Integration for more information.
Optionally, you can also:
- select only orders with certain shippers
- set a maximum number of units to substitute
- use a different price for the substitute item or add it at no charge
- recalculate freight
- add pick slip messages for the orders
This menu option generates a batch job which processes the item substitution and produces a report listing each affected order.
Quotes: Order lines that are on quotes are not eligible for item substitution; see Entering Pre-Order Quotes for an overview and required setup.
Retail pickup or delivery orders: Order lines are not eligible for item substitution if they are on retail pickup or delivery orders from the Order Broker. See the Order Broker Integration for more information.
Cancellation email: The system generates an order or order line cancellation email or Outbound Email XML Message (CWEmailOut) to the customer if:
- you have specified an Order Line Cancellation Email Program (K79), and
- the cancel reason code you use does not match the Cancel Reason Code to Suppress Email (L08), and
- the customer is eligible to receive email notifications; see When Does the System Generate an Email Notification?
For more information see the Web Services Guide on My Oracle Support (ID 2149144.1).
See the Order Cancellation Confirmation Email Sample and Contents and Order Line Cancellation Confirmation Email Sample and Contents for more information.
In this topic:
Process Substitute Items Screen
How to display this screen: Enter PSUB in the Fast path field at the top of any menu or select Process Substitute Items from a menu.
Field | Description |
---|---|
Item/SKU (Item/SKU to be canceled) |
Enter the item and SKU that should be canceled by the batch job. Only open or held, unreserved order lines are eligible for cancellation; if the line is partially reserved and partially backordered, or if it is sold out, the batch job will not cancel it. If the item you select for cancellation has a ship via override, the system will not add the substitute item with the same ship via override, unless the override ship via is specified in the Item table. If you do not enter a valid item code and SKU (if the item has SKUs), the screen displays an error message. See Performing Initial Item Entry (MITM) for more information on creating and working with items. Note: Substituting a set item will not cancel its component items.Item: 12 positions, alphanumeric; required. SKU: three 4-position fields; required if the item has SKUs. |
Cancel reason code |
Enter the cancel reason code to use when canceling the item. Cancel reason codes control whether you update demand for cancellations. If the cancel reason code reduces demand, the canceled order line will have a status of X (closed); otherwise, the line will have a status of C (canceled). Cancel reason codes are defined in and validated against the Cancel Reason Code table. See Establishing Cancel Reason Codes (WCNR). Numeric, 2 positions; required. |
Substitute item/SKU |
Enter the item and SKU that should be added to the order as a substitute for the canceled item. The system does not validate that the substitute item you enter is available in sufficient quantity to fulfill the orders updated by the batch job. You can substitute a non-SKU’ed item with a SKU’ed item, or a SKU’ed item with a non-SKU’ed item, if necessary. If you do not enter a valid item code and SKU (if the item has SKUs), the screen displays an error message. See Performing Initial Item Entry (MITM) for more information on creating and working with items. If the substitute item is restricted from shipment to a country or state, the substitution will not be performed on orders with ship to addresses in the restricted area(s). See Entering Additional Item Information for more information on item country/state restrictions. Note: If you enter a substitute item that has restricted SKUs (the Restrict field at the Create SKU 1 of 2 (With Overrides) Screen is selected), the system displays an error message:Cannot take orders for this item/SKU (xxxxxx xxxx). Item: 12 positions, alphanumeric; required. SKU: hree 4-position fields; required if the item has SKUs. |
Used canceled item's price |
Indicates whether to apply the unit price of the canceled item to the substitute item. Valid values are:
|
Add item at no charge |
Indicates whether to add the substitute item to the order at no charge. Valid values are:
|
Substitute item price |
The unit price to use for the substitute item, if you are not simply using the canceled item's price or offering the substitute item at no charge. You cannot enter a substitute item price unless both the Use canceled item's price field and the Add item at no charge field are unselected; in this situation, the substitute item price is required. If the order total changes, the order will be subject to a credit check and may go on hold if, for instance, the customer paid by check and there is now a balance due for the new total. Numeric, 13 positions with a 2-place decimal; required if not using the canceled item price or no charge. |
Price override (Price override reason code) |
Enter the price override reason code to use when adding the substitute item to the order. Price override reason codes are defined in and validated against the Price Override Reason table; see Establishing Price Override Reason Codes (WPOR). Alphanumeric, 1 position; required. |
Recalculate freight |
Indicates whether to recalculate freight on the order based on the item substitution. Valid values are:
The Recalculate Freight Default (F62) system control value controls the default setting of this field, but you can override this default. Tax: The system recalculates tax regardless of the setting of this field. |
Maximum number of substitute items to process |
Enter the total number of units of the original item to cancel and replace with the substitute item. The system will cancel each complete order line for the item in chronological order by order date until it reaches this maximum. If the system cannot cancel a complete order line quantity on an order without exceeding the maximum you enter here, it skips that order line and selects the next available order line that will not exceed the maximum. For example, if there are two units remaining to cancel before exceeding the maximum, and the next order line is for five units, the system skips this order line and cancels the next order line for the item for a quantity of two or fewer. If each open order line for the original item exceeds the maximum number you specify here, the system does not cancel any of the order lines. Numeric, 5 positions; optional. |
Pick message line 1 and 2 |
Up to two lines of messages to appear on pick slips for shipment of the substitute item. These messages are added to the order line messages for each updated order. You can review order line messages by selecting Messages for an item in order inquiry; see Work with Order Line Messages Screen. Alphanumeric, 40 positions each; optional. |
Completing this screen: If you select Accept to submit the item substitution batch job, the system submits the job MASS_SUB. This job cancels each order line with the original item and adds the substitute item using the settings you entered on this screen. This job also produces the Substitute Item Processing List.
Order Updates
In addition to canceling the original item and adding the substitute item, the batch job updates each affected order as follows:
Order history: An order history message displays on the Display Order History Screen:
LINE 003 SUBSTITUTED FOR LINE 002
The user ID of the person who ran the item substitution batch job displays next to the message.
If the order goes on hold as a result of the new item price, order history messages will be available for review:
3/05/06 H SYS HLD---BALANCE DUE HOLD - SYSTEM HOLD HTRUMAN
3/05/06 W User price override - Order line 11 100.00 HTRUMAN
3/05/06 M Order was maintained 341.00 HTRUMAN
Order line history: The ADD and CANCEL transactions for each affected line display on the Display Order Line History Screen. The user ID of the person who ran the item substitution batch job displays next to the transaction.
Order line messages: Any pick slips messages you entered at the Process Substitute Items screen display on the Work with Order Line Messages screen. You can display this screen by selecting Messages for an item in order inquiry; see Work with Order Line Messages Screen.
Pick slip preparation: The system removes any pick slip preparation from the order and once the item substitution updates are complete, reevaluates the order for pick slip preparation; see Preparing Orders for Pick Slip Generation.
Stored value card authorization reversal: If a stored value card payment with an open, unused authorization amount exists on the order, the system may generate a stored value card authorization reversal; see Stored Value Card Authorization Reversal.
Processing and Purging Subscriptions
In this part:
- Generating the Subscription Extract Table (WGSE) describes the process of identifying the issue number of the subscriptions you want to send and creating a file of customers who should receive this issue.
- Purging Subscriptions (MPCS) describes how to purge closed (expired) or canceled subscriptions from the Customer Subscription table.
Generating the Subscription Extract Table (WGSE)
Purpose: The Generate Subscription Extract file function creates a table of customers who should be sent an issue of a subscription.
A record is created in the Customer Subscription table when you generate pick slips for a customer order containing a subscription item. See Displaying More Options in OIOM for more information on working with customer subscriptions.
Before you can sell subscriptions, you must first define a subscription item in the Item table and in the Item Subscription table. See Working with Item Subscriptions (WISB) for more information on working with subscription items.
When you generate the Subscription Extract Table (CSSBEX), you have the option of selecting all open subscriptions, or you can select specific subscription items by issue number.
In this topic:
- First Generate Subscription Extract File Screen
- Generate All Open Subscriptions
- Second Generate Subscription Extract File Screen (Selecting Issue Numbers)
- Subscription Extract Table (CSSBEX)
First Generate Subscription Extract File Screen
Purpose: At this screen you have the option of writing all open Customer Subscription records to the Subscription Extract table, or selecting subscription items by issue number.
How to display this screen: Enter WGSE in the Fast path field at the top of any menu or select Generate Subscription Extract File from a menu.
Screen Option | Procedure |
---|---|
Select issue numbers for subscription generation |
Select By Item for the Selected subscription items or all open? field to advance to the Second Generate Subscription Extract File Screen (Selecting Issue Numbers) |
Generate all open subscriptions |
Select All open for the Selected subscription items or all open? field. See Generate All Open Subscriptions. |
Accept your entries and generate all open subscriptions |
Select Submit. See Generate All Open Subscriptions. |
Generate All Open Subscriptions
Follow these steps to select all open Customer Subscription records. To select specific issues of subscription items, see Second Generate Subscription Extract File Screen (Selecting Issue Numbers).
- Select All open for the Selected subscription items or all open? field at the First Generate Subscription Extract File Screen.
- Select Submit. If records currently exist in the Subscription Extract Table (CSSBEX), this window prompts you to confirm the reset.
- deselect if you would like to clear all previous records from the Subscription Extract Table (CSSBEX). Select if you would like to append new records to the end of the Subscription Extract table without clearing the table.
- Select OK to continue with the extract. The system submits the job SUBSCR_EXT by selecting all open records from the Customer Subscription table (status = O). It then writes these records to the Subscription Extract table.
Note:
If you use All Open to select all open subscriptions, the system will change the status of the record in the Customer Subscription table to X (Closed) and will not record the first or last issue numbers or dates as they display at the Work with Subscriptions Screen. You might choose this option if you are turning over the Subscription Extract table to another service provider rather maintaining the subscription using Order Management System. If would like the record status to remain open and want to track first and last issue numbers and dates, you must use By Item to select subscriptions by issue number; see Second Generate Subscription Extract File Screen (Selecting Issue Numbers).Second Generate Subscription Extract File Screen (Selecting Issue Numbers)
Purpose: Use this screen to select issue numbers of subscription items to include in the Subscription Extract table.
How to display this screen: Select By Item for the Select subscription items or all open? field at the First Generate Subscription Extract File Screen.
Once you have selected a Customer Subscription record using All Open for all open items, the system changes the status of the record to X (Closed). This means that the record will no longer be selected when you generate the Subscription Extract table.
Field | Description |
---|---|
Iss (Issue) |
The issue of the subscription you want to include in the Subscription Extract table. Numeric, 3 positions. |
Item |
The item code of the subscription item. Items are defined in and validated against the Item table. Subscription items have a selected Subscription and Non/inv (non-inventory) fields in the Item and Item/SKU tables. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; display-only. |
SKU |
The unique characteristics associated with the item, such as its color, size, width, etc. SKUs are defined in and validated against the Item/SKU table. Alphanumeric, three 4-position fields; display-only. |
Description |
The description of the subscription item, as defined in the Item records. Note: Extracting a subscription with a description longer than 40 positions is not currently implemented.Alphanumeric, 120 positions; display-only. |
Sel (Selected?) |
This field identifies whether you requested an issue of the subscription item. An asterisk (*) appears in the Sel column to the right of the selected subscription items. Alphanumeric, 1 position; display-only. |
Instructions:
- Enter the issue number next to a subscription item you want to select for the Subscription Extract table. An asterisk (*) appears in the Sel column to the right of the subscription item, and the subscription item moves to the top of the screen.
- Repeat the above step for each subscription item you want to select by issue number. Selected subscription items appear in alphanumeric order at the top of the screen.
- To reset your selections, select Reject. A pop-up window prompts you to confirm the reset.
Select OK to remove the issue number from each subscription item.
- When you have entered all the issue numbers you would like to select, select Accept. If records currently exist in the Subscription Extract Table (CSSBEX), a pop-up window prompts you confirm the reset.
- Deselect if you would like to clear all previous records from the Subscription Extract table. Select if you would like to append new records to the end of the Subscription Extract table without clearing the table.
- Select OK to continue with the extract. The system submits the job SUBSCR_EXT by selecting all records in the Customer Subscription table that match your selections. It then writes these records to the Subscription Extract Table (CSSBEX).
Subscription Extract Table (CSSBEX)
For more information on individual fields, see Creating and Updating Sold-to Customers (WCST) and Working with Item Subscriptions (WISB).
Field | Attributes | Comments |
---|---|---|
Company code |
3 positions, numeric |
|
Order date |
7 positions, numeric |
|
Sequence number |
7 positions, numeric |
|
Customer sold to number |
9 positions, numeric |
|
Sold to prefix |
3 positions, alphanumeric |
|
Sold to first name |
15 positions, alphanumeric |
|
Sold to initial |
1 position, alphanumeric |
|
Sold to last name |
25 positions, alphanumeric |
|
Sold to company name |
30 positions, alphanumeric |
|
Sold to street address |
32 positions, alphanumeric |
|
Sold to apartment number |
10 positions, alphanumeric |
|
Sold to address line 2 |
32 positions, alphanumeric |
|
Sold to address line 3 |
32 positions, alphanumeric |
|
Sold to address line 4 |
32 positions, alphanumeric |
|
Sold to city |
25 positions, alphanumeric |
|
Sold to state |
2 positions, alphanumeric |
|
Sold to zip code |
10 positions, alphanumeric |
|
Sold to PO Box |
1 position, alphanumeric |
Y or N |
Sold to delivery code |
1 position, alphanumeric |
B (business), R (residential), or N (no distinction) |
Sold to suffix |
3 positions, alphanumeric |
|
Recipient customer number |
9 positions, numeric |
The recipient on an order can be a sold to address, customer ship to address, or order ship to address. |
Recipient prefix |
3 positions, alphanumeric |
|
Recipient first name |
15 positions, alphanumeric |
|
Recipient initial |
1 position, alphanumeric |
|
Recipient last name |
25 positions, alphanumeric |
|
Recipient company name |
30 positions, alphanumeric |
|
Recipient street address |
32 positions, alphanumeric |
|
Recipient apartment number |
10 positions, alphanumeric |
|
Recipient address line 2 |
32 positions, alphanumeric |
|
Recipient address line 3 |
32 positions, alphanumeric |
|
Recipient city |
25 positions, alphanumeric |
|
Recipient state |
2 positions, alphanumeric |
|
Recipient zip code |
10 positions, alphanumeric |
|
Subscription start date |
7 positions, numeric |
Default start date is the order date |
Date sent to service |
7 positions, numeric |
Set to zero |
Source code |
6 positions, alphanumeric |
|
Quantity |
5 positions, numeric |
The quantity is always 1 |
Price |
13 positions with a 2-place decimal; numeric |
|
Item code |
12 positions, alphanumeric |
|
Item description |
120 positions, alphanumeric |
Extracting a subscription with a description longer than 40 positions is not currently implemented. |
SKU |
14 positions, alphanumeric |
|
Subscription status |
1 position, alphanumeric |
|
Number of intervals |
3 positions, numeric |
|
Rent name? |
1 position, alphanumeric |
Y or N |
Mail name? |
1 position, alphanumeric |
Y or N |
Issue number |
3 positions, numeric |
|
Expiring issue number |
3 position, numeric |
|
Option taken at Subscription Extract screen |
5 positions, numeric |
Valid values: 1 or 2 |
Purging Subscriptions (MPCS)
Purpose: The Purge Customer Subscriptions is a “housekeeping” routine that you can use to delete any expired or canceled subscription records from the Customer Subscription table. This is necessary because these records remain on file until they are purged.
Purge Customer Subscriptions Screen
How to display this screen: Enter MPCS in the Fast path field at the top of any menu or select this option from a menu.
Instructions:
- Enter the date through which you want to cancel subscriptions.
- Select the Confirm prompt (that appears in the lower right of your screen). The system submits the PURGE_SUBS job and generates the Purge Customer Subscription List.
Memberships
In this part:
- Membership Overview provides a high-level overview of creating membership programs, assigning them to customers, and generating membership orders.
- Working with Membership Types (WWMT) describes the menu option you use to set up membership types for tracking, sorting, and revision control.
- Working with Membership Programs (WWMP) describes the menu option you use to set up membership programs in which you can enroll customers.
- Working with Customer Memberships (WWCM) describes the menu option you use to work with customer memberships, including creating, changing, working with included items, and changing status.
- Generating Membership Orders (EGMO) describes the menu options you use to create orders for customer memberships.
- Printing the Expected Membership Orders Report (PEMO) describes the menu option you use to generate this report and provides a sample.
- Update Customer Memberships (MMCM) describes how to update the source code and replace an item on existing customer memberships and, optionally, membership programs.
Working with Membership Types (WWMT)
Purpose: Use the Work with Membership Type menu option to define membership type codes. You can use these codes to group and identify membership programs for informational or reporting purposes, or as selection criteria when you are generating membership orders. See Membership Overview.
Loyalty memberships? The membership type also controls whether a membership program is a standard membership that you sell or create, or a loyalty membership, in which the system automatically evaluates whether each customer placing an order qualifies for the loyalty program based on order history.
You use different screens in Working with Membership Programs (WWMP) and Working with Customer Memberships (WWCM) for loyalty membership programs vs. standard programs.
Allow changes? For standard membership programs, the membership type also controls whether you can change any of the default settings from the membership program for individual customer memberships.
Which information cannot be changed? The information controlled by this setting includes the items included on generated orders, any discount, and the criteria the system uses to determine shipment intervals. If the membership program is assigned to a type that does not permit changes, this information is display-only for customer memberships you create and cannot be changed.
Note:
If a membership program is flagged to not allow changes, then it is important to specify a ship via code at the Membership Program Screen to default to customer memberships; otherwise, you will not be able to create customer memberships in Working with Customer Memberships (WWCM), because there will be no ship via code, and the ship via code is a required field.Which information can be changed? You will be able to change only:
- the customer membership's status
- the next release date for orders
- the alternate shipping address or recipient customer
- pay type information
Note:
Even if a membership program is flagged not to allow changes, you can still process updates through the Update Customer Memberships (MMCM) option.In this topic:
Work with Membership Type Screen
How to display this screen: Enter WWMT in the Fast path field at the top of any menu or select Work with Membership Type from a menu.
Field | Description |
---|---|
Type |
A code representing a type of membership program. Alphanumeric, 2 positions; optional. |
Description |
The description of the membership type. Alphanumeric, 30 positions; optional. |
Loyalty |
Valid values:
Standard memberships can be used to generate membership orders, or they can be discount-only memberships. See Loyalty Memberships for an overview. |
Screen Option | Procedure |
---|---|
Create a new membership type |
Select Create to advance to the Membership Type Screen in Create mode. |
Change a membership type |
Select Change for a membership type to advance to the Membership Type screen in Change mode. At this screen, you can change the description or the Change customer membership flag, but not the type code itself. See Membership Type Screen for field descriptions. |
Delete a membership type |
Select Delete for a membership type to delete it. You cannot delete a membership type if it is assigned to any membership programs. |
Display a membership type |
Select Display for a membership type to advance to the Membership Type screen in Display mode. You cannot change any information on this screen. See Membership Type Screen for field descriptions. |
Membership Type Screen
Purpose: Use this screen in Create mode to create a new membership type.
How to display this screen: Select Create at the Work with Membership Type Screen.
Field | Description |
---|---|
Membership type |
A code to identify a type of membership program. You can use these codes to group and identify membership programs for informational or reporting purposes, or as selection criteria when you are generating membership orders. Also, you use the membership type to distinguish standard membership programs from loyalty programs. Alphanumeric, 2 positions. Create mode: required. Change mode: display-only. |
Description |
The description of the membership program. Alphanumeric, 30 positions; required. |
Change customer membership |
Indicates whether the settings that default from a membership program of this type to each customer membership you create can be changed on an individual customer membership. Valid values are:
See Working with Membership Types (WWMT) for a discussion of the type of information you can or cannot change for a customer membership, depending on the setting of this field.
|
Loyalty |
Indicates whether membership programs of this type are standard membership programs or loyalty memberships. Valid values are:
See Loyalty Memberships for an overview. |
Working with Membership Programs (WWMP)
Purpose: Use the Work with Membership Programs menu option to create, review, or work with the templates for customer memberships.
Loyalty programs or standard memberships programs: The membership program Type assigned to a membership program identifies whether it is a loyalty program or a standard membership. In the case of loyalty memberships, the background jobs automatically evaluate whether each customer placing an order qualifies for the loyalty program based on order history and customer class. In the case of a standard membership program, you can create customer memberships by selling a membership item in order entry, or creating the customer membership one manually using the Working with Customer Memberships (WWCM) menu option. Standard membership programs can generate new orders for the customer on a periodic basis, or they can be discount-only.
You use different screens in Work with Membership Programs and Working with Customer Memberships (WWCM) for loyalty membership programs vs. standard programs.
Standard membership programs: The membership program specifies settings such as:
- Order creation and/or discount: You can set up membership programs in order to create orders periodically for participating customers, and/or to apply a discount to all orders for participating customers. A membership program can include either or both functions.
- Template for customer membership: The information you define for a membership program defaults when you create a new customer membership. This information can include shipment intervals, source code, ship via, and any specific items to include on the generated membership orders.
- Ability to change customer membership: If you assign a membership program to a membership type that permits changes, you can override the defaults for specific customer memberships. If the membership type does not permit changes, all of the membership program settings default and cannot be overridden. These settings include shipment interval or date, discount, and included items. See Working with Customer Memberships (WWCM), for descriptions of each field.
Loyalty membership programs: The membership program specifies settings such as:
- Date range: Use the Effective start date to indicate how far back to go when evaluating a customer’s order or sales totals for loyalty membership qualification. For example, you can set the start date to January 1 if you would like to include order or sales dollars for the current calendar year only.
- Dollar value requirement: You can set up loyalty membership based on total merchandise dollars ordered or total dollars sold (that is, shipped), and specify the required dollar value. You can also specify whether to subtract additional order activity, such as returns, cancellations, and soldouts, from the total merchandise dollar value. Depending on the type of dollar totals (order, sales, external) used to evaluate customers for loyalty membership, the evaluation takes place at during ORDR_ASYNC processing or BILL_ASYNC processing.
- Customer class: You can set up a customer class as a qualification for a loyalty program, either alone or in combination with a total dollar value.
- Discount percentage and other benefits: In addition to indicating a discount percentage to apply to the customer’s orders, you can specify additional benefits, such as free freight, assignment of a special customer class, or a backorder priority. You can also enter a special message line to print on pick slips for customers in the loyalty program.
For more information: See Membership Overview for more information on how loyalty programs and standard membership programs work, and about required setup.
In this topic:
Work with Memberships Screen
Purpose: Use this screen to review the membership programs in your company, to create a new membership program, or to work with an existing membership program.
How to display this screen: Enter WWMP in the Fast path field at the top of any menu or select Work with Membership Program from a menu.
Field | Description |
---|---|
Membership ID |
A code representing the membership program. Alphanumeric, 12 positions; optional. |
Description |
The description of the membership program. Alphanumeric, 30 positions; optional. |
Start dt (Start date) |
The first date when you can begin creating customer memberships for this membership program, or to include when calculating the customer’s total order or sales to date in order to determine whether the customer qualifies for this loyalty program. Numeric, 6 positions (in user date format); optional. |
End dt (End date) |
The last date when you can create new customer memberships for this membership program. Numeric, 6 positions (in user date format); optional. |
Type |
The code representing the membership type of a program. You can use the membership type to identify loyalty programs, to further identify or group membership programs, or to indicate that membership settings are compulsory and cannot be changed for specific customers. See Working with Membership Types (WWMT) for an overview. Alphanumeric, 2 positions; optional. |
Screen Option | Procedure |
---|---|
Create a new membership program |
Select Create to advance to the Enter Membership Program Window. |
Change header information for a membership program |
Select Change for a membership program to advance to:
Note: Changing a membership program does not update any existing customer memberships or their generated orders.
Note: Changing a membership program does not update any existing customer loyalty memberships. |
Delete a membership program |
Select Delete for a membership program to delete it. Note: You cannot delete a membership program associated with any active customer memberships. Instead, the system displays a message:Active Customer Memberships exist - cannot delete. |
Display a membership program |
Select Display for a membership program to advance to:
|
Work with items for a membership program |
Select Work with details for a membership program to advance to the Work with Membership Program Detail Screen. Note: This option is not available for a loyalty membership program type. |
Enter Membership Program Window
Purpose: Use this window to specify the name, description, and type of the membership program you are creating. Based on the membership type you select, the system determines whether to advance next to the Membership Program Screen if it is a standard membership program type, or the Loyalty Membership Program Screen, if it is a loyalty membership program type.
Differences between standard and loyalty membership programs: The background jobs assign loyalty memberships automatically to customers based on the customer’s order history, while you can sell standard membership programs in order entry or through the Working with Customer Memberships (WWCM). Standard memberships can be used to generate membership orders, or they can be discount-only memberships.
How to display this screen: Select Create at the Work with Memberships Screen.
Field | Description |
---|---|
Membership ID |
Enter the unique code to identify a membership program. The code you enter cannot be assigned to an existing membership program. Matching a membership program with an item for order entry: You can create standard customer memberships through order entry by adding an item whose Membership flag is selected to the order. When you add the membership item to an order, the system displays a pop-up window for you to enter the membership ID. You can save a step in order entry by assigning the same name to both the membership program and the item; if there is a membership program whose name matches the membership item, this name defaults in the window. Example: You can create a membership program with an ID of MEMB01 and also create a membership item named MEMB01. When you enter the item MEMB01 in order entry, the correct membership ID defaults into the pop-up window. Alphanumeric, 12 positions; required. |
Description |
Enter the description of the membership program. You can change the description, if needed, on the next screen. Alphanumeric, 30 positions; required. |
Type |
Enter the membership type code that identifies:
Membership types are defined in and validated against the Membership Type table; see Working with Membership Types (WWMT). Alphanumeric, 2 positions; required. |
Completing this screen: Complete each of the fields as described above and click OK to advance to the Membership Program Screen (for standard membership programs) or the Loyalty Membership Program Screen (for loyalty membership programs).
Membership Program Screen
Purpose: Use this screen in Create mode to create a new standard membership program, which you sell or create in order to generate periodic membership orders and/or to provide a discount. See Membership Overview for more information, including the difference between standard and loyalty membership programs.
If the membership type you specify at the Enter Membership Program Window is flagged as a loyalty type, you advance instead to the Loyalty Membership Program Screen. See Membership Overview for more information on different types of membership programs.
How to display this screen: Click OK at the Enter Membership Program Window after specifying a membership program type that does not have the Loyalty flag set. See Membership Program Screen for the screen you use to create a loyalty membership program.
Field | Description |
---|---|
Membership ID |
A unique program to identify a membership program. See the Enter Membership Program Window for more information. Change screen: display-only. |
Description |
The description of the membership program. Your entry from the Enter Membership Program Window defaults, but you can override it. Alphanumeric, 30 positions; required. |
Type |
The type of membership program. You can use the membership type code to further identify or group membership programs. See the Enter Membership Program Window for more information. Alphanumeric, 2 positions; display-only. |
Effective start date |
The first date when you can begin creating customer memberships for this membership program. If you enter a start date, you must also specify an end date. Numeric, 6 positions (in user date format); optional. |
Effective end date |
The last date when you can create a new customer membership for this membership program. This field does not control the duration of customer memberships you create for the membership program. If you enter an end date, you must also specify an start date. Numeric, 6 positions (in user date format); optional. |
Delay initial shipment |
Indicates whether to delay the Next release date for customer memberships by the Shipment interval, or to use the current date as the Next release date. The Next release date indicates when to start generating membership orders for the customer through Generating Membership Orders (EGMO). Example: You create a customer membership on June 28, and the Shipment interval is set to 30 days. If the Delay initial shipment flag is selected, the Next release date for the customer membership is set to July 28, and the membership generation program will not generate an order for the membership until then. If the Delay initial shipment flag is unselected, the Next release date for the customer membership is set to June 28, and you can generate an order for the membership the next time you use the membership generation program. Valid values:
Note: This flag applies only to regular (non-loyalty) membership programs that generate orders, and only if the membership program specifies a Shipment interval rather than a Fixed shipment day. |
Shipment interval |
The minimum interval, in number of days, that the Generate Customer Membership Orders program should wait between generating orders for active customer memberships. The system uses this value to determine the Next release date to assign a customer membership after generating a new order. Example: If a customer membership's shipment interval is set to 30, the Release date will be set to 30 days in the future after you generate an order. You cannot specify both a shipment interval and a fixed shipment day for a membership program. Numeric, 3 positions; required if you do not specify a Fixed shipment day. |
Fixed shipment day |
The day of the month when the Generating Membership Orders (EGMO) program should consider active customer memberships eligible for order generation. Example: If you set a membership program's fixed shipment day to 15, the system initially sets a new customer membership's release date as follows:
Each time you generate a new order for the customer membership, the Generate Customer Membership Orders program resets its Release date. You cannot specify both a shipment interval and a fixed shipment day for a membership program. Note: Your entry cannot be greater than 28, to make sure that the customer memberships will be eligible for order generation during each month of the year.Numeric, 2 positions; required if you do not specify a shipment interval. |
Discount percent |
The percentage discount to apply to all orders for the customer who purchased the membership. The membership status must be active, and the Discount end date must not have been reached yet for the discount to apply (see Discount duration). This discount percentage defaults to the order header each time you enter a new order for the customer. If you create the customer membership by adding a membership item in order entry, this discount percentage applies to the price of the membership item itself, unless you flag the item as nondiscountable (select the Discountable flag for the item). See Membership Overview for a discussion of how membership discounts apply to orders. Also, see Working with Customer Memberships (WWCM) for more information on discounts. Numeric, 5 positions with a 2-place decimal; optional. |
Discount duration |
The number of months that the discount percentage will apply to customer orders. The system calculates the discount end date when you create a customer membership based on the current date. Applies to active memberships only: Regardless of the discount start and end dates on a customer membership, the system applies a discount to orders only if the customer membership is currently active. Numeric, 2 positions; optional. |
Default source code |
The source code to default onto orders created from customer memberships. The source code you enter here defaults onto customer memberships you create, but you can override it there if the membership type allows it. You can also update the source code for existing customer memberships and the membership program itself through the Update Customer Memberships (MMCM) option. If this source code matches the source code in the Default Unknown Source Code (I58) system control value, the system updates the source code on the order header to the source code associated with the offer on the first order detail line; see Default Unknown Source Code Logic. Source codes are defined in and validated against the Source Code table. See Working with Source Codes (WSRC). Alphanumeric, 9 positions; required. |
Ship via |
The ship via to default onto orders you create through customer memberships. The ship via code you enter here defaults onto customer memberships you create, but you can override it there if the membership type allows it. If you do not specify a ship via code here:
Note: If you do not specify a ship via code here and if you use a membership type that does not allow changes, then you will not be able to create customer memberships in Working with Customer Memberships (WWCM), because there will be no way to specify the ship via to use.Auto-selection of best way ship via: If the ship via for the customer membership matches the Best Way Ship Via for Auto-Assignment (J67), the system automatically selects the “best way” ship via with the lowest overall shipping costs when you generate a membership order. However, in this situation, the Order Total Window (Reviewing the First Order Total) displayed in order entry or in Working with Customer Memberships (WWCM) does not include any shipping charges. See the Best Way Ship Via for Auto-Assignment (J67) system control value for a discussion on auto-assignment. Ship via codes are defined in and validated against the Ship Via table. See Working with Ship Via Codes (WVIA). Numeric, 2 positions; optional. |
Order type |
The order type to default onto orders you create through customer memberships. The Generate Customer Membership Orders program will use the order type specified in the Default Order Type (B28) system control value if you do not enter an order type code here. You cannot override the order type for specific customer memberships. Order type codes are defined in and validated against the Order Type table. See Establishing Order Types (WOTY). Alphanumeric, 1 position; optional. |
Ship complete |
Identifies whether all items on an order you create through a customer membership must ship together. Valid values are:
The Default ship complete flag system control value does not control the default setting of this field. |
Note:
If you select Exit at this screen, you do not create the new membership program.Loyalty Membership Program Screen
Purpose: Use this screen to create a loyalty membership. The system uses the information you enter at this screen to determine whether to automatically assign a customer to a loyalty membership; also, your entries here determine the benefits of the loyalty program. See Membership Overview for more information, including the difference between standard and loyalty membership programs.
How to display this screen: Click OK at the Enter Membership Program Window after specifying a membership program type that has the Loyalty flag set. See Membership Program Screen for the screen you use to create a standard membership program.
Field | Description |
---|---|
Membership ID |
The membership ID you entered at the Enter Membership Program Window. Alphanumeric, 12 positions; display-only. |
Description |
The description of the program. Your entry from the Enter Membership Program Window defaults, but you can override it. Alphanumeric, 30 positions; required. |
Type |
The membership type code you entered at the Enter Membership Program Window. The description is to the right. Alphanumeric, 2 positions; display-only. |
Effective start date |
Indicates the earliest date to include when determining whether the customer has a sufficient order or sales dollar total to qualify for the loyalty membership for a loyalty program. Evaluating order or sales history:
Adding dollar totals: The system bases its evaluation on the records of order activity in the Order Billing History table. See the Order Billing History Detail Screen for more information on how the system updates this table. Also, see Loyalty Memberships for an overview of how customers are evaluated for loyalty membership. If you leave this field blank, the system does not restrict its evaluation by an effective start date; all order activity in the Order Billing History table is considered. Numeric, 6 positions (in user date format); optional. |
Effective end date |
The last date when the system should evaluate customers for loyalty memberships. If you leave this field blank, the system does not automatically stop evaluating customers for the loyalty program. Numeric, 6 positions (in user date format); optional. |
Qualifying Values | |
Customer class |
The customer class, if any, that qualifies a customer for the loyalty program. If the customer is already assigned to this class and has exceeded the LTD dollars, if any, specified for the loyalty program, the system creates a loyalty membership for the customer. Customer classes are defined in and validated against the Customer Class table; see Setting Up the Customer Class Table (WCCL) for more information. Also, see the First Create Sold To Customer Screen for more information on assigning a customer class to a customer.
Alphanumeric, 2 positions; optional (required if no LTD dollars amount is specified). |
LTD dollars (life-to-date dollars) |
The total merchandise dollar value of all orders or all shipments (based on the setting of the Orders/Sales/External field at this screen) required to qualify for the loyalty membership. If the Net returns/exchanges, Net cancels, or Net soldouts flags are selected, the total merchandise dollar value of these activities are subtracted from the total merchandise order or sales dollars when evaluating the customer. Start date for qualifying dollar value: The system uses the Effective start date for the loyalty program to determine the order activity to include in the qualifying dollar total. See Loyalty Memberships for a complete discussion. Merchandise only: The system includes the merchandise value, based on the actual selling price, when calculating the total order or sales dollar value. Additional charges, freight, tax, additional freight, and special handling are not included. Numeric, 13 positions with a 2-place decimal; optional (required if there is not a qualifying Customer class). |
Orders/Sales/External |
Indicates the evaluation method to use in order to determine whether a customer qualifies for the loyalty membership program. Valid values are:
Note: See Loyalty Memberships for a discussion of loyalty program evaluation and examples.Typically, you would use only one evaluation method for all loyalty programs in effect within a company. Required. |
Net returns/exchanges |
Indicates whether to subtract the total merchandise dollar value of returns or exchanges from the total order or sales merchandise total when evaluating whether a customer qualifies for a loyalty membership. Valid values are:
|
Return activity against orders before the Effective start date: Return or exchange activity is evaluated based on the date of the return or the exchange itself, rather than the date of the original order. For example, you process a return of $50 in merchandise on January 31 against an order that was entered on December 30. The system is evaluating the customer for a loyalty program with an effective start date of January 1. The value of the $50 return is subtracted from the total dollar value since January 1, even though the order was originally entered before that date. |
|
Exchange activity: If this value is unselected and you process an exchange, the dollar value of the exchange, or replacement, item is included in the calculation of loyalty eligibility. For example, if the customer exchanges an item with a selling price of $50 for an item with the same selling price, this activity effectively increases the customer’s total merchandise value to date by $50 if you do not net returns and cancellations. |
|
Net cancels |
Indicates whether to subtract the total merchandise dollar value of cancellations from the total order or sales merchandise total when evaluating whether a customer qualifies for a loyalty membership. Valid values are:
|
Cancellation activity against orders before the Effective start date: Cancellation activity is evaluated based on the date of the cancellation itself, rather than the date of the original order. For example, you process a cancellation of $50 in merchandise on January 31 against an order that was entered on December 30. The system is evaluating the customer for a loyalty program with an effective start date of January 1. The value of the $50 cancellation is subtracted from the total dollar value since January 1, even though the order was originally entered before that date. |
|
Update demand flag: A cancellation always reduces the total order merchandise amount if you use a cancel reason code whose Update demand? flag is selected. The result of this type of cancellation might be to make a customer ineligible for a particular loyalty program if it is based on the order total. |
|
Update demand for order maintenance transactions? If the Update Demand for Order Maintenance Transactions (C72) system control value is unselected, it is possible to understate the customer’s total merchandise order dollars. Because the order dollar total in this situation does not increase if, for example, you add an item in order maintenance, processing a cancellation can have the effect of “double dipping” when the system subtracts the cancellation dollars from the order total. For example, a customer’s total dollars ordered is $500.00. You add a $100.00 item in order maintenance, and then cancel it. Because the total dollars ordered was never increased by the $100.00 in order maintenance, the cancellation effectively reduces the customer’s total dollars ordered to $400.00. For this reason, you might want to leave this flag unselected if the Update Demand for Order Maintenance Transactions (C72) system control value is Unselected. |
|
Net soldouts |
Indicates whether to subtract the total merchandise dollar value of soldouts from the total order or sales merchandise total when evaluating whether a customer qualifies for a loyalty membership. Valid values are:
|
Soldout activity against orders before the Effective start date: Soldout activity is evaluated based on the date of the soldout cancellation itself, rather than the date of the original order. For example, you sell out $50 in merchandise on January 31 against an order that was entered on December 30. The system is evaluating the customer for a loyalty program with an effective start date of January 1. The value of the $50 soldout is subtracted from the total dollar value since January 1, even though the order was originally entered before that date. |
|
Update demand for order maintenance transactions? If the Update Demand for Order Maintenance Transactions (C72) system control value is unselected, it is possible to understate the customer’s total merchandise order dollars. Because the order dollar total in this situation does not increase if, for example, you add an item in order maintenance, selling out an item can have the effect of “double dipping” when the system subtracts the soldout dollars from the order total. For example, a customer’s total dollars ordered is $500.00. You add a $100.00 item in order maintenance, and then sell it out. Because the total dollars ordered was never increased by the $100.00 in order maintenance, the sellout effectively reduces the customer’s total dollars ordered to $400.00. For this reason, you might want to leave this flag unselected if the Update Demand for Order Maintenance Transactions (C72) system control value is unselected. |
|
Benefits | |
Discount percent |
The discount percentage that a member of the loyalty program qualifies for. The system sets this percentage when it creates the customer loyalty membership, and it defaults to the order header each time you enter a new order for the customer. The discount percentage for a customer loyalty membership is displayed at the Loyalty Customer Membership Screen. Numeric, 5 positions with a 2-place decimal; optional. |
Discount duration |
The number of months that the discount specified for the customer membership should be applied automatically to the customer’s orders. The system adds this number of months to the current date in order to set the Discount end date for the customer loyalty membership, displayed at the Loyalty Customer Membership Screen. Even if the customer membership status is Active, the discount does not automatically apply after this date. If you leave this field blank, the system does not stop applying the discount automatically. Numeric, 2 positions; optional. |
Free freight |
Indicates whether to provide free freight to customer who are assigned to the loyalty membership. If this flag is selected, the Calc freight flag is unselected when you enter an order for the customer. The free freight flag for a customer loyalty membership is displayed at the Loyalty Customer Membership Screen. Note: It is still possible for the customer to be charged additional freight even if freight is free. |
Customer class |
Indicates the customer class, if any, to assign to customers who are assigned to the loyalty membership. This customer class replaces the current class assignment, if any, for the customer. When you deactivate a loyalty membership, or the system deactivates one, the system does not automatically update the customer class currently assigned to the customer. The update occurs only at the time of activating a customer loyalty membership. Customer classes are defined in and validated against the Customer Class table; see Setting Up the Customer Class Table (WCCL) for more information. Also, see the First Create Sold To Customer Screen for more information on assigning a customer class to a customer. Note: Not to be confused with the Customer class, if any, to use as one of the Qualifying Values for the loyalty membership.Alphanumeric, 2 positions; optional. |
Priority |
The priority in which the system should evaluate this loyalty program compared to other current loyalty programs, where a lower number indicates a higher priority. If you are setting up multiple, graduated loyalty programs, you should assign a higher priority (lower number) to the ones with the higher dollar value requirement in order to ensure that the customer is assigned the highest-level loyalty program that he qualifies for. Example: You are setting up two loyalty programs: PROGRAM2, with a discount of 5%, requires a total order value of $1000; and PROGRAM1, with a discount of 10%, requires a total order value of $2000. You assign a priority of 1 to PROGRAM1, and a priority of 2 to PROGRAM2. Each time you process an order from a customer, the system first evaluates whether the customer qualifies for PROGRAM1 with the higher discount percentage (priority 1). If the customer does not qualify for PROGRAM1, the system then evaluates whether the customer qualifies for PROGRAM2 and the lower discount percentage (priority 2). If there are two current loyalty programs assigned the same priority, the system evaluates them in alphanumeric order based on Membership ID. Numeric, 3 positions; required. |
Priority B/O |
Indicates the default Priority, if any, that the system should set on the order header when you enter an order for a customer in this loyalty program. 9 indicates the highest priority, while 0 is the lowest priority. You can override this default in order entry. The Evaluate Backorders program uses the priority to determine which backorders to reserve first when inventory becomes available. See Working with the EBO_ASYNC Job for more information. Numeric, 1 position; optional. |
Pick msg (pick message) |
Enter the message, if any, to print on the pick slip for customers who are members of this loyalty program. This message prints in addition to any other messages selected for the pick slip. See Performing Pick Slip Generation for more information on generating pick slips. Alphanumeric, 60 positions; optional. |
Work with Membership Program Detail Screen
Purpose: Use this screen to work with the items that default onto customer membership orders.
How to display this screen: Select Work with Details for a membership program at the Work with Memberships Screen.
Note:
This option is not valid for loyalty memberships. See Membership Overview for more information.Field | Description |
---|---|
Membership ID |
The code representing the membership program. Alphanumeric, 12 positions; display-only. |
Description (Unlabeled field to the right of the membership ID) |
The description of the membership program. Alphanumeric, 30 positions; display-only. |
Item |
An item to include on orders you create for customer memberships. Note: You can replace an item for existing customer memberships and the membership program itself through the Update Customer Memberships (MMCM) option.Alphanumeric, 12 positions; optional. |
SKU |
The item's unique characteristics, such as its color and size. Alphanumeric, three 4-position fields; display-only. |
Order quantity |
The quantity of the item to include on each order you create for customer memberships. Numeric, 5 positions; display-only. |
Rot (Rotation) |
The interval when the item should be included in an order. A rotation of 1 indicates that the item should be included on the first order you generate, and will always be included if there are no items with a rotation higher than 1. A rotation of 2 indicates that the item should be included on the second order, and so on. A rotation of 0 indicates that the item should be included on every order. If the Generating Membership Orders (EGMO) program attempts to generate an order for a customer membership and there are no eligible rotations (either the current rotation number or a rotation of zero), then the program does not generate the order, and the customer membership is listed on the Memberships in Error Report. Numeric, 3 positions; display-only. |
# of times (Number of times to include) |
The total number of times to include the item on an order. If this field is blank, there is no limit to the number of times to include the item. Numeric, 3 positions; display-only. |
N/C (No charge) |
Indicates whether the item should be free of charge on orders you generate. Valid values are:
|
Ovr rsn (Price override reason code) |
The price override reason code for the system to use when adding the item to the order at no charge, or with an override price. Alphanumeric, 1 position; display-only. |
Ovr price (Price override) |
The price to charge for the item on orders you generate for customer memberships. You would specify a price override if you do not want the system to use the regular pricing hierarchy for membership orders. Numeric, 13 positions with a 2-place decimal; display-only. |
Screen Option | Procedure |
---|---|
Enter a new item to include in the membership program |
Select Create to advance to the Membership Program Screen. |
Change an item included in the membership program |
Select Change for an item to advance to the Membership Program Screen (Change Mode). At this screen, you can change anything but the membership ID. See Membership Program Detail Screen. Note: Changing an item on a membership program does not update any existing customer memberships or their generated orders. |
Delete an item from a membership program |
Select Delete for an item to delete it from the membership program. Note: Deleting an item on a membership program does not update any existing customer memberships or their generated orders. |
Display an item |
Select Display for an item to advance to the Membership Program Detail Screen (Display Mode). You cannot change any information on this screen. See the Membership Program Detail Screen for a field descriptions. |
Membership Program Detail Screen
Purpose: Use this screen in Add mode to add an item to a membership program.
How to display this screen: Select Create at the Work with Membership Program Detail Screen.
Field | Description |
---|---|
Membership ID |
The code representing the membership program. Alphanumeric, 12 positions; display-only. |
Item |
The item to include on orders you create for customer memberships. Item codes are defined in and validated against the Item table. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; required. |
SKU |
The item's unique characteristics, such as its color and size. Alphanumeric, three 4-position fields; required if the item has SKUs. |
Order quantity |
The quantity of the item to include on each order you create for a customer membership. Numeric, 5 positions; required. |
Rotation |
The interval when the item should be included in an order. A rotation of 1 or zero indicates that the item should be included on the first order you generate. A rotation of 2 indicates that the item should be included on the second order, and so on. Once you have generated as many orders as the highest rotation number assigned to an item, items on rotation 1 are selected and the cycle begins again. The default rotation is 1. A rotation of 0 indicates that the item should be included on every order you generate. If each item on the membership has a rotation of 1, they will all be included on each generated order. If the Generating Membership Orders (EGMO) program attempts to generate an order for a customer membership and there are no eligible rotations (either the current rotation number or a rotation of zero), then the program does not generate the order, and the customer membership is listed on the Memberships in Error Report. Numeric, 3 positions; optional. |
# of times to include |
The total number of times to include the item on an order. If this field is blank, there is no limit to the number of times to include the item. Numeric, 3 positions; optional. |
No charge |
Indicates whether the item should be added free of charge to an order you generate. Valid values are:
If you select No Charge for this field, you need to complete the price override reason code, below. |
Price override code |
The price override reason code for the system to use when adding the item to the order at no charge, or with an override price. Price override reason codes are defined in and validated against the Price Override Reason Code table. See Establishing Price Override Reason Codes (WPOR). Alphanumeric, 1 position; required if the item is flagged as "no charge" or if you enter a price override. |
Price override |
The price to charge for the item on orders you generate for customer memberships. You would specify a price override if you do not want the system to use the regular pricing hierarchy for membership orders. Numeric, 13 positions with a 2-place decimal; optional. |
Note:
Adding an item to a membership program does not update any existing customer memberships or their generated orders.Working with Customer Memberships (WWCM)
Purpose: Use the Work with Customer Memberships menu option to review or change customer memberships. Available options for standard membership programs include:
- creating a new customer membership
- changing the terms of the membership, including dates and payment information
- working with items for the membership
- activating, deactivating, or canceling a membership
- advancing to standard order inquiry for the customer membership
Settings default from membership program: The settings you have defined for the standard membership program default for each new customer membership you create. These settings include dates, frequency of shipments, discount, and included items. However, you can override these defaults for standard membership programs as long as the membership type permits it. See Working with Membership Programs (WWMP).
You can also update the source code and replace an item on existing customer memberships through the Update Customer Memberships (MMCM) option.
Create through quote or order entry: You can also use quote or order entry to create a standard customer membership. See Membership Overview for general information, Entering Customer Memberships in Order Entry for detailed information, and Entering Customer Memberships in Order Entry for information on the differences between quote an order entry.
Deleting memberships on quotes: If you delete a membership item on a quote in entry or maintenance, the system also deletes the customer membership.
Canceling memberships through order maintenance: When you cancel a membership item in order maintenance or cancel the order or quote that contains the membership item, the system cancels the customer membership created by the membership item if possible.
However, the system cannot cancel the membership if the customer membership is currently in In process status. A customer membership is in In process status if:
- The membership order generation process is currently running and the customer membership is eligible for order generation, or
- A generated order is currently suspended in an order batch.
In either situation, you will need to:
- Cancel the customer membership through the process described under Canceling a Customer Membership.
- Cancel any generated membership orders that you do not want to ship to the customer.
See Canceling a Membership Item for more information on the process of canceling a membership item.
Loyalty memberships: Unlike standard customer memberships, customer loyalty memberships are created automatically based on the customer’s order history, sales history, or customer class. You cannot create a customer loyalty membership through this menu option. See Loyalty Memberships for an overview.
In this topic:
- Work with Customer Memberships Screen
- Create Customer Membership Window
- Customer Membership Screen (Change Mode)
- About Entering Cash Amounts for a Customer Membership
- Customer Membership Details Screen
- Customer Membership Detail Screen (Change Mode)
- Canceling an Item on a Customer Membership
- Order Total Pop-Up Window (Reviewing the Next Order Total)
- Loyalty Customer Membership Screen
- Changing Customer Membership Status, Rotation or Release Date
- Display Membership Orders Screen
- Deleting a Customer Membership
- Alternate Shipping Address Screen (Change Mode)
- Customer Membership Recipient Screen (Change Mode)
Work with Customer Memberships Screen
How to display this screen: Enter WWCM in the Fast path field at the top of any menu or select Work with Customer Memberships from a menu.
Field | Description |
---|---|
Customer # |
A unique number to represent the sold-to customer who ordered the membership. Ghost customers: If you enter the customer number of a ghost customer, the scan screen does not display any memberships; this is because a merge/purge has assigned any memberships using that customer number to the “target” customer. You can identify a ghost customer by the setting of the Ghost flag. Numeric, 9 positions; optional. |
Membershp ID (Membership ID) |
A code that identifies the membership program in which the customer is enrolled. Alphanumeric, 12 positions; optional. |
Type |
A code that identifies the type of membership program. You can use membership types to group membership programs, to indicate whether any of the settings for the membership program can be overridden for specific customer memberships, or to identify a membership program as a loyalty program. See Working with Membership Types (WWMT) for more information. Alphanumeric, 2 positions; display-only. |
Status |
The current status of the customer membership. Valid values are:
Note: This status does not apply to loyalty memberships. |
Note: Canceling the items for a customer membership changes the status to Complete, not Canceled.
Note: This status does not apply to loyalty memberships.See Changing Customer Membership Status, Rotation or Release Date. Optional. |
|
Shp int (Shipment interval) |
The minimum interval, in number of days, that the Generating Membership Orders (EGMO) program should wait between generating orders for this customer membership. Standard membership programs only. Numeric, 3 positions; display-only. |
Int day (Interval day of the month) |
The day of the month when the Generating Membership Orders (EGMO) program should consider the customer membership eligible for order generation. Standard membership programs only. Numeric, 2 positions; display-only. |
# shp (Number of shipments) |
The number of membership orders that have been generated to date for the customer membership. Standard membership programs only. Numeric, 3 positions; display-only. |
Next rot (Next rotation) |
The next rotation due to be included when you generate membership orders. You assign a rotation to an item on a customer membership to indicate when it should be included in an order. Standard membership programs only. Note: If the membership does not have differing rotations (that is, each order includes the same item(s)), the next rotation is always 1.Numeric, 3 positions; display-only. |
Next rel date (Next release date) |
The next date when the Generating Membership Orders (EGMO) program should consider the customer membership eligible for order generation. The system calculates this date based on the schedule defined for the membership. Also, you can change the next release date by selecting Change release date/rotation for a customer membership; see Changing Customer Membership Status, Rotation or Release Date. Standard membership programs only. Numeric, 6 positions (in user date format); display-only. |
Last ord date (Last order date) |
The last date when an order was generated for the customer membership. Standard membership programs only. Numeric, 6 positions (in user date format); display-only. |
Customer name (Unlabeled field below the customer number) |
The name of the customer who ordered the membership, or qualified for the loyalty membership. Alphanumeric, 41 positions; display-only. |
Recipient (Unlabeled field to the right of the sold-to customer name) or program description |
This field displays:
You can set up these types of recipients for standard memberships:
Alphanumeric, 30 positions; display-only. |
Screen Option | Procedure |
---|---|
Create a new customer membership |
Select Create to advance to the Create Customer Membership Window. Note: This option is not available for loyalty customer memberships. See Loyalty Memberships for an overview. |
Change a customer membership |
Select Change for a membership to advance to the Customer Membership Screen (Change Mode) in Change mode for standard memberships, or the Customer Membership Detail Screen (Change Mode) for loyalty memberships. Note: You cannot change any information for a customer membership if the program type does not have the Change customer membership flag selected; in this situation, you advance to the same screen whether you select Change for or select Display for a customer membership. |
Cancel an active customer membership |
Select Cancel for an active membership to display the Confirm Cancel Request pop-up window. See Canceling a Customer Membership. Note: Once you cancel a customer loyalty membership, you cannot change its status or create a new loyalty membership. Only the system can create customer loyalty memberships. |
Delete a customer membership |
Select Change for a membership to advance to the Customer Membership Screen (Change Mode) in Change mode; then, select Delete. See Deleting a Customer Membership. Note: This option is not available for loyalty customer memberships. |
Display a customer membership |
Select Display for a standard customer membership to advance to the Customer Membership Screen in Display mode for standard memberships or the Customer Membership Detail Screen (Change Mode) for loyalty memberships. You cannot change any information on these screens. You can advance to these screens regardless of the membership's status. Note: Depending on the user’s authority to credit card information, the system writes a record to the Credit Card Audit table when the Customer Membership Detail Screen (Change Mode) screen is displayed. See Logging Credit Card Data Access in the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information.See Customer Membership Screen (Change Mode) for field descriptions for the Customer Membership Screen in Display mode. |
Reactivate an inactive customer membership |
Select Activate for an inactive membership to display the Override Release Date pop-up window (standard membership programs only) and change the membership's status to Active. See Activating a Customer Membership. |
Change the next release date or rotation for a customer membership |
Select Change release date/rotation for a membership to display the Override Release Date pop-up window. See Changing Release Date or Rotation for a Customer Membership. Note: This option is not available for loyalty customer memberships. |
Deactivate an active customer membership |
Select Deactivate for an active membership to change its status to Inactive. See Deactivating a Customer Membership. |
Work with items for a customer membership |
Select Details for a standard membership to advance to the Customer Membership Details Screen. Note: This option is not available for loyalty customer memberships. |
Review orders generated for the customer membership |
Select Orders for customer for a membership to advance to the Display Membership Orders Screen. Note: This option is not available for loyalty customer memberships. |
Create Customer Membership Window
Purpose: Use this window to indicate the customer and membership program when you are creating a new customer membership.
Note:
- This option is not available for loyalty customer memberships. See Loyalty Memberships for an overview.
- You cannot create a standard customer membership from the Work with Customer Memberships Screen if the membership type does not allow changes and there is no default ship via specified for the membership program, because the ship via code is a required field. See Working with Membership Programs (WWMP) for more information on setting up membership programs.
How to display this screen: Select Create at the Work with Customer Memberships Screen.
Field | Description |
---|---|
Customer # |
The number that identifies the customer sold-to who is ordering the membership. You can select the Customer# box to advance to:
Customer sold-to numbers are defined in and validated against the Customer Sold To table. See Creating and Updating Sold-to Customers (WCST). If you enter the number of a ghost customer, the system displays the Ghost Customer Warning Pop-up Window. Numeric, 9 positions; required. |
Membership ID |
The code that identifies a membership program. The settings you have defined for the membership program default to the new customer membership program. You can override these defaults unless the membership program's type is flagged to prohibit changes. Membership programs are defined in and validated against the Membership table. See Working with Membership Programs (WWMP). You cannot enter a membership ID whose membership type is flagged as a loyalty program. See Loyalty Memberships for an overview. Alphanumeric, 12 positions; required. |
Completing this window: You advance to the Customer Membership Screen (Change Mode).
Ghost Customer Warning Pop-up Window
A ghost customer is a customer whose records have been merged with the records of a matching customer when you performed a Merge/Purge. The ghost customer was the source customer in the merge; records for this customer were merged with the records for a matching target customer. When performing the merge you can elect to flag a source customer as a Ghost on the Work with Source Customers Screen. Ghost customer records are retained in the Customer Sold To table for informational purposes, but they do not represent the most recent customer order information from the merged (target customer) records.
When you enter the number of a ghost customer, the pop-up Warning Window displays information on the ghost customer.
Select Continue to return to the Create Customer Membership Window with the target customer number entered on the screen. For example, if you enter 202, a ghost customer, the system will display the warning window informing you that customer 202 has been merged into customer 137. When you continue with the create customer membership process, customer 137 will default on the Create Customer Membership Window.
See Working with Merge/Purge Sold-to Names (MMCS) for more information on the merge/purge function.
Note:
The system displays a message such as Cannot manually create cust. if the membership ID you enter specifies a loyalty program. You cannot create a customer loyalty membership. See Loyalty Memberships for an overview.Customer Membership Screen (Change Mode)
Purpose: Use this screen to review or override the settings for the standard membership program that have defaulted for a customer membership.
- If the membership program's type prohibits changes, you will not be able to override any of the settings that have defaulted from the membership program.
- Depending on the user’s authority to credit card information, the system writes a record to the Credit Card Audit table when this screen is displayed. See Logging Credit Card Data Access in the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information.
- You cannot create a standard customer membership at this screen if the membership type does not allow changes and there is no default ship via specified for the membership program, because the ship via code is a required field. See Working with Membership Programs (WWMP) for more information on setting up membership programs.
How to display this screen: Complete the Create Customer Membership Window, specifying a standard membership program as the Membership ID.
Change a membership: You can also advance to this screen by selecting Change for a standard customer membership at the Work with Customer Memberships Screen. You can change a membership only if the membership status is Active (A) or Inactive (I). You cannot change memberships that are Canceled (C) or Complete (X), or if the membership type prohibits changes.
Field | Description |
---|---|
Customer # |
A unique number to identify the customer who ordered the membership. Numeric, 9 positions; display-only. |
Customer name |
The name of the customer who ordered the membership. Alphanumeric, 41 positions; display-only. |
Order# |
The order on which the customer ordered the customer membership. This field does not appear if you created the customer membership through the Working with Customer Memberships (WWCM) menu option. Numeric, 8 positions; display-only. |
Membership ID |
A code to identify the membership program. Alphanumeric, 12 positions; display-only. |
Description (Unlabeled field to the right of the membership ID) |
The description of the membership program. Alphanumeric, 30 positions; display-only. |
Membership type |
A code to identify the type of membership program. You can use membership types to group membership programs, to control whether it is possible to override membership program defaults for specific customer memberships, or to flag loyalty membership programs. See Working with Membership Types (WWMT) for more information. Alphanumeric, 2 positions; display-only. |
Status |
The status of the customer membership. Valid values are:
|
See Changing Customer Membership Status, Rotation or Release Date. Display-only. |
|
Created on |
The date when you created the customer membership. Numeric, 6 positions (in user date format); display-only. |
Changed on |
The most recent date when you entered a change for the customer membership. Numeric, 6 positions (in user date format); display-only. |
Cancel reason |
The reason code you used when canceling the customer membership or the membership item (see Canceling a Membership Item for information). Included only for canceled memberships. Cancel reason codes are defined in and validated against the Cancel Reason Code table. See Establishing Cancel Reason Codes (WCNR). Alphanumeric, 2 positions; display-only. |
Description (Unlabeled field to the right of the cancel reason code) |
The description of the cancel reason code. Included only for canceled memberships. Alphanumeric, 30 positions; display-only. |
Cancelled on |
The date when you canceled the customer membership. Included only for canceled memberships. Numeric, 6 positions (in user date format); display-only. |
Shipment interval |
The minimum interval, in number of days, that the Generate Customer Membership Orders program should wait between generating orders for this membership. If a shipment interval was specified for the membership program, it defaults here. Example: If a customer membership's shipment interval is set to 30, the Generate Customer Membership Orders program will consider the membership eligible for a new order if 30 days have passed since the last order was generated. You cannot specify both a shipment interval and a fixed shipment day for a membership program. You can override the shipment interval only if the membership program's type allows changes. See Working with Membership Programs (WWMP). Numeric, 3 positions; required if you don't specify a fixed shipment day, or display-only. |
Fixed shipment day |
The day of the month when the Generating Membership Orders (EGMO) program should consider the customer membership eligible for order generation. If a fixed shipment day was specified for the membership program, it defaults here. Example: If you set the membership's fixed shipment day to 15, the system initially sets a release date as follows:
The system recalculates the Next release date if you change the Fixed shipment day. Order generation: Each time you generate a new order for the customer membership, the Generate Customer Membership Orders program resets its release date as described above. |
Validation: You cannot specify both a shipment interval and a fixed shipment day for a customer membership. Also, your entry cannot be greater than 28, to make sure that the customer membership will be eligible for order generation during each month of the year. You can override the fixed shipment day only if the membership program's type allows changes. See Working with Membership Programs (WWMP). Numeric, 2 positions; required if you don't specify a shipment interval, or display-only. |
|
Next release date |
The next date when the Generating Membership Orders (EGMO) program should consider the customer membership eligible for order generation. When you create the customer membership or generate a new order, the system calculates this date based on the Shipment interval or Fixed shipment day. To change: Select Release Date. See Changing Release Date or Rotation for a Customer Membership. The system updates the next release date if you change the Fixed shipment day. Numeric, 6 positions (in user date format); display-only. |
Last order date |
The last date when you generated a new order for the customer membership. Numeric, 6 positions (in user date format); display-only. |
Next rot (Next rotation) |
The rotation number for the next order to be generated for the customer membership. If the membership does not have differing rotations, this number will be 1. You can change the next rotation for a membership by selecting Release Date. See Changing Release Date or Rotation for a Customer Membership. Numeric, 3 positions; display-only. |
Discount start date |
The date when any discount percentage for the membership begins applying to orders for the customer. The current date defaults if you set up a Discount duration for the membership program. Validation: If the customer membership includes a discount start date, it also requires a discount end date; otherwise, both fields must be blank. Membership status: Regardless of the discount start and end dates, the system applies a discount to orders only if the customer membership is in an active, in process or error status. You can override the discount start date only if the membership program's type allows changes. See Working with Membership Programs (WWMP). Numeric, 6 positions (in user date format); optional. |
Discount end date |
The last date when any discount percentage for the membership applies to orders for the customer. If you set up a Discount duration for the membership program, the system calculates this date when you create a customer membership by adding the number of months for the discount duration to the current date. Validation: If the customer membership includes a discount start date, it also requires a discount end date, it also requires a discount end date; otherwise, both fields must be blank Membership status: Regardless of the discount start and end dates, the system applies a discount to orders only if the customer membership is in an active, in process or error status. You can override the discount end date only if the membership program's type allows changes. See Working with Membership Programs (WWMP). Numeric, 6 positions (in user date format); optional. |
Disc% (Discount percentage) |
The percentage discount to apply to orders for the customer as long as the status of the customer membership is active, in process or error and the current date is within the discount start and end dates, if defined. Discount hierarchy: If the customer has more than one eligible membership that carries a discount percentage, the highest discount percentage applies. Additionally, if an additional discount percentage, such as a customer discount or a promotional discount, applies to the order, the system applies this discount after subtracting the membership discount from the merchandise total. Discount-only memberships: If the membership is for discounting purposes only (that is, you will not be generating orders), the membership will never close automatically. Even after the discount end date passes, the membership will remain active, although the discount will no longer apply to new orders. You can override the discount percentage only if the membership program's type allows changes. See Working with Membership Programs (WWMP). Numeric, 5 positions with a 2-place decimal; optional. |
Pay type |
The pay type to apply to orders generated for the customer membership. Pay type codes are defined in and validated against the Pay Type table. See Working with Pay Types (WPAY). Required for order generation: A customer membership requires payment information unless it is for discounts only. If the customer membership does not have payment information when you generate orders, it will not be selected for order generation,; instead, it will appear on the Memberships in Error Report, produced when you generate membership orders. Validation: You can enter only the following payment categories for a customer membership:
Changes you make to a customer membership do not affect any orders you have already generated for the membership. The system performs credit card validation if the credit card number has not been tokenized. Tokenization: You cannot change the pay type if the credit card number has been replaced with a token; in this situation, you must change the credit card number and the pay type. Numeric, 2 positions; optional. |
Cash amount |
The amount of cash to apply to the customer membership. You can enter a cash amount for a prepaid payment type only. When you generate an order: The system updates the cash amount available for the membership each time you generate an order against it. For example, if there is a $100.00 prepayment against the membership, and you generate an order for $20.00, the system reduces the cash amount for the membership to $80.00. Updating the cash amount: Your entry should represent the actual amount now available for the membership. Example: A customer prepays with two $50.00 checks for a total of $100.00. You generate an order for $20.00, and the system reduces the cash amount for the membership to $80.00. Subsequently, a $50.00 check from the customer is returned for insufficient funds. You need to enter a cash amount of $30.00 ($80.00 - $50.00) to update the cash amount correctly. Any cash amount you enter for a customer membership does not apply to existing orders you have already generated. See About Entering Cash Amounts for a Customer Membership. Numeric, 13 positions with a 2-place decimal; required if you enter a prepaid payment type. |
Card# (credit card number) |
The credit card number to use as payment for membership orders. This is a token instead of an actual credit card number if you use credit card tokenization and the Tokenized field in the Customer Membership table is Y. A credit card number is required if you enter a credit card pay type; otherwise entry is prohibited. The system validates your entry against the settings for the pay type. Additionally, the credit card number requires authorization when you generate a pick slip for a membership order. Credit card validation: The system validates your entry against the settings for the pay type. Also, the credit card number requires authorization when you generate a pick slip for the membership order. Initial vs. subsequent authorization to CyberSource or the External Payment Service: If you use CyberSource or the External Payment Service, the authorization request for a generated membership order is passed as a subsequent authorization if there is an initial authorization, either from the originating order or from a previously generated order. However, if you change the card after generating any orders, the next membership order you generate is submitted to CyberSource or the External Payment Service as an initial authorization. For background, see:
Existing membership orders: Changes you make to a customer membership do not affect any orders you have already generated for the membership. Masking: If you do not have authority to the Display Full Credit Card Number (B14) secured feature, the credit card number displays in the format specified at the Credit Card Number Layout Screen for the associated pay type. For example, ************1443 may display instead of the entire credit card number. See Credit Card Number Format for an overview. If you do not have authority to the Restrict Access to Credit Card Numbers in OI and OM (A88) secured feature, this field is blank. You will not be able to edit the credit card number. CC last four: The system stores the last four digits of the credit card number in the CC last four field in the Customer Membership table in order to verify that card with the customer. Numeric, 20 positions; required for a credit card pay type. |
CC Last 4 |
The last four digits of the credit card number. From the CC Last 4 field in the Customer Membership table. If you use credit card encryption, the system does not encrypt the value in this field. Alphanumeric, 4 positions; display-only. |
Expiration date |
The last date when the credit card number is valid. An expiration date is required if you enter a credit card pay type; otherwise, entry is prohibited. Validation: The system validates that the expiration date has not already passed when you select OK at this screen. Additionally, the system checks the expiration date as part of the authorization process when you generate a pick slip for a membership order. If you do not have authority to the Restrict Access to Credit Card Numbers in OI and OM (A88) secured feature, this field is blank. You will not be able to edit the credit card number. Numeric, 4 positions (in user date format); required for a credit card pay type. |
Default source |
The source code to use when generating orders for the membership. If a source code was specified for the membership program it defaults here, but you can override it. The system validates that the source code you enter is current, valid and not restricted. The source code you enter here defaults to the Original source field if you are creating the membership through the Work with Customer Memberships menu option. If this source code matches the source code in the Default Unknown Source Code (I58) system control value, the system updates the source code on the order header to the source code associated with the offer on the first order detail line; see Default Unknown Source Code Logic. Changes you make to a customer membership do not affect any orders you have already generated for the membership. Source codes are defined in and validated against the Source Code table; see Working with Source Codes (WSRC). You can override the default source only if the membership program's type allows changes. See Working with Membership Programs (WWMP). Alphanumeric, 9 positions; required. |
Original source |
The original source code associated with the customer membership. If you create the customer membership through Working with Customer Memberships (WWCM), the source code assigned to the membership program defaults. If you create the customer membership through order entry, the source code from the order header defaults. This code is used for reporting and tracking purposes only. Changes you make to a customer membership do not affect any orders you have already generated for the membership. You can override the original source only if the membership program's type allows changes. See Working with Customer Memberships (WWCM). Alphanumeric, 9 positions; required. |
Ship via |
The ship via to use for orders you generate for the membership program. The ship via specified for the membership program (if any) defaults here, but you can override it. Invalid SCF/ship via combination: If the ship via for the customer membership is not valid for the shipping address on the order, the order will appear on the Print Phone Errors listing report when you generate orders and will remain in error status (E) until you correct the error in batch order entry; also, the customer membership will be in-process (I) status. Changes you make to a customer membership do not affect any orders you have already generated for the membership. You can override the ship via only if the membership program's type allows changes. See Working with Customer Memberships (WWCM). Ship via codes are defined in and validated against the Ship Via table. See Working with Ship Via Codes (WVIA). Auto-selection of best way ship via: If the ship via for the customer membership matches the Best Way Ship Via for Auto-Assignment (J67), the system automatically selects the “best way” ship via with the lowest overall shipping costs when you generate a membership order. However, in this situation, the Order Total Window (Reviewing the First Order Total) displayed in order entry or in Working with Customer Memberships (WWCM) does not include any shipping charges. See the Best Way Ship Via for Auto-Assignment (J67) system control value for a discussion on auto-assignment. Note: You cannot create a standard customer membership at this screen if the membership type does not allow changes and there is no default ship via specified for the membership program, because the ship via code is a required field. See Working with Customer Memberships (WWCM) for more information on setting up membership programs.Numeric, 2 positions; required. |
Ship complete |
Controls whether all items on each order you generate for the customer membership must ship together. Valid values are:
The setting from the membership program defaults, but you can override it. Changes you make to a customer membership do not affect any orders you have already generated for the membership. You can override the ship complete flag only if the membership program's type allows changes. See Working with Customer Memberships (WWCM). |
Recip (Recipient) |
The customer sold-to number identifying the recipient for the customer membership. You can select the Customer# box to advance to the Select Customer Sold To pop-up window; this window permits scanning on various types of information, such as postal code, name, telephone number and email address. If you do not select a customer through this window, you advance to the Customer Membership Recipient Screen (Change Mode). Changes you make to a customer membership do not affect any orders you have already generated for the membership. Customer sold-to numbers are defined in and validated against the Customer Sold To table. See Creating and Updating Sold-to Customers (WCST). Numeric, 9 positions; optional. |
Ship to # |
A number to identify a permanent ship-to customer associated with the Recipient customer for the membership. See Creating and Updating Ship-to Customers (WCST). The system validates your entry against the ship-to customers associated with the membership recipient. To select a ship-to customer associated with the customer who ordered the membership, you should enter that same customer sold-to number in the Recipient field. Changes you make to a customer membership do not affect any orders you have already generated for the membership. Numeric, 3 positions; optional. |
Recipient name |
The name of the recipient of the customer membership, or the recipient's ship-to, if selected; this is the customer who will actually receive the order(s) for the membership. Alphanumeric, 41 positions; display-only. |
Gift |
Indicates whether the order is flagged as a gift. Valid values are:
Flagging an order as a gift can control:
See Performing Pick Slip Generation. Changes you make to a customer membership do not affect any orders you have already generated for the membership. The Default “Gift Order” Flag (D14) system control value does not affect the default setting for this field. |
Shipments |
The total number of orders generated for this customer membership. If a generated order fails the edit and is in error status, this total is not updated until you correct the error(s) and reprocess the order batch. Numeric, 3 positions; display-only. |
Shipment $ |
The total dollar value of all orders generated for the membership, including merchandise, tax, and all related charges. If a generated order fails the edit and is in error status, this total is not updated until you correct the error(s) and reprocess the order batch. Numeric, 20 positions with a 2-place decimal; display-only. |
Gift message |
A message to print on the pick slip for gift orders you generate for the membership. This message prints only if your unique printing program supports it. Changes you make to a customer membership do not affect any orders you have already generated for the membership. The message will print on the pick slip for the next order you generate; once the message prints, the system deletes the message from the customer membership. Alphanumeric, three 60-position fields; optional. |
Screen Option | Procedure |
---|---|
Create a customer membership recipient |
Select Recipient to advance to the Customer Membership Recipient Screen (Change Mode). |
Work with an alternate shipping address for the customer membership |
Select Alt Ship to advance to the Alternate Shipping Address Screen (Change Mode). You would use an alternate address if the customer wants the membership orders sent to a different address, such as a vacation home, for a limited period of time. |
Create a new customer as a recipient for the membership, or work with an existing membership recipient |
Select Alt Ship to advance to the Customer Membership Recipient Screen (Change Mode). A recipient customer has a separate customer sold-to record in your company. |
Work with items for the customer membership |
Select Details to advance to the Customer Membership Details Screen. |
Delete the customer membership |
Select Delete. You can delete a customer membership only if you have not already generated any orders; otherwise, you must cancel the membership. See Deleting a Customer Membership. |
Change the next release date for the membership |
Select Release Date to display the Override Release Date pop-up window. See Changing Release Date or Rotation for a Customer Membership. |
About Entering Cash Amounts for a Customer Membership
Overview: You can enter cash amounts for standard customer memberships in order to use the cash as a payment method on generated customer orders.
Update to cash amount: When you generate an order for the customer membership, the system reduces the total cash amount to reflect the amount allocated to the new order. For example, if the total cash amount is $100.00, and you generate an order for $20.00, the system reduces the cash amount for the customer membership to $80.00.
You can update the cash amount after you have begun to generate orders for the customer membership; however, your reset to the cash amount total should reflect the total amount that has already been allocated to generated orders. Your entry should be equal to the new total cash amount available for the customer membership.
Example: A customer prepays with two $50.00 checks for a total of $100.00. You generate an order for $20.00, and the system reduces the cash amount for the membership to $80.00. Subsequently, a $50.00 check from the customer is returned for insufficient funds. You need to enter a cash amount of $30.00 ($80.00 - $50.00) to update the cash amount correctly.
When the cash amount is exhausted: The system will continue to generate orders for the membership; however, these orders will be put on hold because of the balance due. You must use order maintenance to apply cash to these orders and change their status to open.
About existing orders: Any cash amount you enter does not apply to existing orders that have been generated for the membership. You must use order maintenance to enter payment information for these orders.
Canceling a prepaid membership: The system does not generate a refund for the remaining cash amount for the membership. You will need to create and generate the refund separately.
Refund when membership closes: When you generate the last order for a prepaid membership, the system creates a refund for any remaining prepayment amount. The system closes a membership when all items have been included on generated orders the number of times specified in the Number of times to include field.
Customer Membership Details Screen
Purpose: Use this screen to enter or review items to include on a standard customer membership. This option is not available for loyalty customer memberships.
How to display this screen: Select Details at the Customer Membership Screen (Change Mode), or select Details for a standard customer membership at the Work with Customer Memberships Screen.
Note:
You can change information on this screen only if the membership program's type allows changes; otherwise, each field is display-only. See Working with Membership Programs (WWMP) Additionally, if you advanced to this screen from the Customer Membership Screen in Display mode, each field on this screen is display-only and cannot be changed.Field | Description |
---|---|
Membership header information | |
Customer # |
The number that identifies the customer who ordered the customer membership. The customer's name appears to the right. Number: numeric, 9 positions; display-only. Name: alphanumeric, 41 positions; display-only. |
Membership ID |
The code representing the membership program. The description of the program appears to the right. ID: alphanumeric, 12 positions; display-only. Description: alphanumeric, 30 positions; display-only. |
Type |
A code that identifies the type of membership program. Alphanumeric, 2 positions; display-only. |
Last order date |
The last date when an order was generated for the customer membership. Numeric, 6 positions (in user date format); display-only. |
Next release date |
The next date when the Generating Membership Orders (EGMO) program should consider the customer membership eligible for order generation. Numeric, 6 positions (in user date format); display-only. |
Next rot (Next rotation) |
The next rotation due to be included when you generate membership orders. You assign a rotation to an item on a customer membership to indicate when it should be included in an order. A rotation of 1 indicates that the item should be included on the first order you generate. A rotation of 2 indicates that the item should be included on every other order, and so on. A rotation of 0 indicates that the item should be included on every order. If the membership does not have differing rotations (that is, each order includes the same item(s), the next rotation will always be 1. Numeric, 3 positions; display-only. |
Membership detail information | |
Item |
An item to include on membership orders you generate. Items that are currently included in the membership, including items that defaulted from the membership program, appear below. If you have not already generated an order that includes the item, you can change the item code itself by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). You cannot delete an item from a customer membership. To cancel an item, select Cancel for the item; see Canceling an Item on a Customer Membership. Item codes are defined in and validated against the Item table. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; optional. |
SKU |
The item's additional characteristics, such as its color and size. If you have not already generated an order that includes the item, you can change the SKU by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). Alphanumeric, three 4-position fields; required if the item has SKUs. |
Qty ord (Quantity ordered) |
The quantity of the item to include in an order you generate for the membership. Entering a new item: This field is required if you are entering a new item for the customer membership. Default from membership program: The quantity defaults from the membership program if the item itself defaulted; however, you can override the quantity by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). Numeric, 5 positions; required. |
Rot (Rotation) |
The rotation in which to include the item when you generate orders. Items with a rotation of 1 will be included in the first order you generate, while items with a rotation of 2 will be included in the second order, and so on. Items with a rotation of 0 will be included in each order you generate. After creating a number of orders that is a multiple of the highest rotation assigned to an item, the cycle repeats. For example: A membership includes these items and rotations: AB100: rotation = 0 CD200: rotation = 1 EF300: rotation = 2 The items will be included in the following pattern: First order: AB100, CD200 Second order: AB100, EF300 Third order: AB100, CD200 (cycle repeats) |
Entering an item: This field defaults to 1, but you can override it. Set the rotation to 0 to include the item in every order you generate. Default from membership program: The rotation defaults from the membership program if the item itself defaulted; however, you can override the rotation by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). Numeric, 3 positions; required. |
|
Tms inc (Number of times to include) |
The total number of times to include the item on an order. If this field is blank or 0, there is no limit to the number of times to include the item. Entering an item: Leave this field blank to include the item indefinitely. Default from membership program: The number of times to include defaults from the membership program if the item itself defaulted; however, you can override the number of times to include by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). Numeric, 3 positions; optional. |
N/C (No charge) |
Indicates whether the item is to be included free of charge. Valid values are:
Entering an item: Leave this field blank if the item should have a price. Otherwise, select this field; you will also need to specify a price override reason code, below. Default from membership program: If an item was flagged as “no charge” for the membership program, it defaults here; however, you can override this flag by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). |
Override price |
The price to charge for the item on orders you generate for customer memberships. You would specify a price override if you do not want the system to use the regular pricing hierarchy for membership orders. Entering an item: Leave this field blank to have the system use its normal pricing hierarchy to determine the price of the item when you generate orders. Otherwise, enter an override price; you will also need to specify a price override reason code. Default from membership program: The price override, if any, defaults from the membership program if the item itself defaulted; however, you can change or delete the price override by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). Numeric, 13 positions with a 2-place decimal; optional. |
Ovr rsn (Price override reason code) |
The price override reason code for the system to use when adding the item to the order at no charge, or with an override price. Entering an item: Enter a price override reason code if you have flagged the item as "no charge" or entered an override price. Default from membership program: The price override reason code, if any, defaults from the membership program if the item itself defaulted; however, you can change this information by selecting Change for the item to advance to the Customer Membership Detail Screen (Change Mode). Price override reason codes are defined in and validated against the Price Override Reason Code table. See Establishing Price Override Reason Codes (WPOR). Alphanumeric, 1 position; required if the item is flagged as "no charge" or if you enter a price override. |
Sts |
The status of the item on the customer membership. Valid values are:
Alphanumeric, 1 position; display-only. |
Tms shp (Times shipped) |
The total number of times the item has been included on an order you have generated for the membership. The system updates this number when you generate orders. If the order is in error when you first generate, the system does not update this number until you correct the error(s) and reprocess the order batch. Numeric, 3 positions; display-only. |
Qty shp (Quantity shipped) |
The total number of units of the item that has been included on orders you have generated for the membership. The system updates this number when you generate orders. If the order is in error when you first generate, the system does not update this number until you correct the error(s) and reprocess the order batch. Numeric, 5 positions; display-only. |
Description |
The description of the item (not the SKU, even if the item has SKUs). Alphanumeric, 120 positions; display-only. |
Avail (Quantity available) |
This is the quantity of this item that is available to sell across all shippable warehouses. A negative quantity indicates that the SKU is unavailable in your inventory and is backordered. The system displays this information only if the status of the item on the membership is active. Numeric, 7 positions; display-only, updated by the system. |
Exp (Expected date) |
The next date when a delivery of this SKU is expected, based on an open purchase order. No date displays if there are no open purchase orders for this SKU. This date is displayed for drop ship items only if the Assign Drop Ship Expected Ship Date (I59) system control value is selected. See that system control value for more information. The system displays this information only if the status of the item on the membership is active. Numeric, 6 positions (in user date format); display-only. |
Adding an item to a customer membership:
- Complete the Item and Quantity ordered fields and any optional fields.
- The system validates your entry and highlights any fields you need to correct. Correct any fields and select OK again.
- The system clears your entries from the enterable fields, and displays the item you have added at the end of the listing of items for the customer membership.
Screen Option | Procedure |
---|---|
Change an item on the customer membership |
Select Change for an item to advance to the Customer Membership Detail Screen (Change Mode). |
Cancel an item on the customer membership |
Select Cancel for an item to cancel it. See Canceling an Item on a Customer Membership. |
Display an item on the customer membership |
Select Display for an item to advance to the Customer Membership Detail screen (Display mode0. You cannot change any information in this mode. See Customer Membership Detail Screen (Change Mode) for field descriptions. |
Review current pricing for an item |
Select Pricing for an item to advance to the Display Quantity Pricing pop-up window. See Working with Items on the Order. |
Review open purchase orders for an item |
Select Open POs for an item to advance to the Display Open Purchase Orders Screen. See Working with Items on the Order. |
Work with header information for the customer membership |
Select Header to advance to the Customer Membership Screen (Change Mode). |
Review the dollar total for the next order to be generated |
Select Next order total to display the Order Total Pop-Up Window (Reviewing the Next Order Total). |
Customer Membership Detail Screen (Change Mode)
Purpose: Use this screen to change an item on a standard customer membership.
Note:
You can change an item on a membership only if the membership program's type allows changes, the membership is Active (A), and the item's status is also Active (A). See Customer Membership Details Screen.How to display this screen: Select Change for an active item at the Customer Membership Details Screen.
Field | Description |
---|---|
Customer# |
A unique number to represent the sold-to customer who ordered the membership. Numeric, 9 positions; display-only. |
Membership ID |
A code that identifies the membership program in which the customer is enrolled. Alphanumeric, 12 positions; display-only. |
Status |
The status of the item on the customer membership. Valid values are:
Display-only. |
Item |
The item on the customer membership. If you have not already generated an order that includes the item, you can change the item code itself; otherwise, the item field is display-only. Item codes are defined in and validated against the Item table. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; required or display-only. |
SKU |
The item's additional characteristics, such as its color and size. If you have not already generated an order that includes the item, you can change the SKU; otherwise, the SKU field is display-only. See Canceling an Item on a Customer Membership. Alphanumeric, three 4-position fields; required if the item has SKUs or display-only. |
Order quantity |
The quantity of the item to include in an order you generate for the membership. Numeric, 5 positions; required. |
Rotation |
The rotation in which to include the item when you generate orders. Items with a rotation of 1 will be included in the first order you generate, while items with a rotation of 2 will be included in the second order, and so on. A rotation of 0 indicates that the item will be included in every order. If all items on the membership are assigned a rotation of 1 (the default), they will all be included on every order. Numeric, 3 positions; required. |
# of times to include |
The total number of times to include the item on orders you generate for the membership. Once the item has been included in this number of orders, the system changes its status to closed (X). If you do not define a number of times to include, the item will be included in generated orders until you cancel the item, or the membership itself is closed. If a number of times to include was defined for the item on the membership program, it defaults for the customer membership. You can change this number at the Customer Membership Detail Screen (Change Mode). Numeric, 3 positions; display-only. |
No charge |
Indicates whether the item is to be included free of charge. Valid values are:
If an item is to be included at no charge, you must also specify a price override reason code. |
Price override code |
The price override reason code for the system to use when adding the item to the order at no charge, or with an override price. Enter a price override reason code if you have flagged the item as "no charge" or entered an override price. Price override reason codes are defined in and validated against the Price Override Reason Code table. See Establishing Price Override Reason Codes (WPOR). Alphanumeric, 1 position; required if the item is flagged as "no charge" or if you enter a price override. |
Price override |
The price to charge for the item on orders you generate for customer memberships. You would specify a price override if you do not want the system to use the regular pricing hierarchy for membership orders. Leave this field blank to have the system use its normal pricing hierarchy to determine the price of the item when you generate orders. Numeric, 13 positions with a 2-place decimal; optional. |
# of shipments |
The number of times the item has been included on orders generated to date for the customer membership. Numeric, 3 positions; display-only. |
Date of last shipment |
The last date when an order that included the item was generated for the membership. Numeric, 6 positions (in user date format); display-only. |
Quantity shipped |
The total number of units of the item that has been included on orders you have generated for the membership. Numeric, 5 positions; display-only. |
Note:
Changes you make to an item on a membership do not affect any open, unshipped orders you have already generated for the membership.Canceling an Item on a Customer Membership
Purpose: When you cancel an item from a standard customer membership, the item will not be included in any more orders that you generate for the membership, and the item's status on the membership changes to Canceled (C).
Note:
If there are any open, unshipped orders that were generated for the customer membership that include the item, the status of the item on the open order(s) remains open. You must use order maintenance to cancel the item and prevent it from shipping to the customer.How to cancel: Select Cancel for an item at the Customer Membership Details Screen to exclude the item from orders you will generate for the membership in the future. The system displays the Confirm Cancel Request pop-up window.
Enter cancel reason: If you select OK at the Confirm Cancel Request pop-up window, the Enter Cancel Reason window opens. This window indicates the item you are canceling from the membership and requires a cancel reason code. The cancel reason code is a 2-position, numeric code, defined in and validated against the Cancel Reason Code table; see Establishing Cancel Reason Codes (WCNR).
The system stores the cancel reason code for the item in the Customer Membership Detail table.
Canceling an item on a membership does not affect any open, unshipped orders you have already generated for the membership.
Last item? If you cancel the last remaining item on a customer membership, the membership’s status changes to Complete. In this situation, the system does not send the membership cancellation email.
Order Total Pop-Up Window (Reviewing the Next Order Total)
Purpose: Use this window to review the projected dollar total for the next order due to be generated for a standard customer membership.
How to display this screen: Select Display next order total at the Customer Membership Details Screen.
About this window: This window indicates the next rotation eligible for order generation.
Order total an estimate: The order total that appears in this window includes merchandise and tax. It also includes projected freight charges if the ship via on the order does not match the Best Way Ship Via for Auto-Assignment (J67). This order total is an estimate only. The actual order total when you generate the first order may vary, depending on changes to pricing, using various freight methods, including special charges, and so on.
Loyalty Customer Membership Screen
Purpose: Use this screen to review or change the information on a customer loyalty membership. The system creates customer loyalty memberships automatically based on the customer’s order history, sales history, or customer class. See Loyalty Memberships for an overview.
How to display this screen: Select Change or Display for a customer loyalty membership.
Note:
Regardless of whether you select Change or Display for the membership, you cannot change any information at this screen if the Change customer membership flag for the membership type is unselected.Field | Description |
---|---|
Customer # |
A unique number to identify the customer who qualified for the loyalty membership. The customer’s name or company name is displayed to the right. Number: numeric, 9 positions; display-only. Name: alphanumeric, 41 positions; display-only. |
Membership ID |
A code that identifies the loyalty membership program in which the customer is enrolled. The description displays to the right. ID: alphanumeric, 12 positions; display-only. Description: alphanumeric, 30 positions; display-only. |
Type |
A code that identifies the type of membership program. See Working with Membership Types (WWMT) for more information. Alphanumeric, 2 positions; display-only. |
Status |
The current status of the loyalty membership. Possible statuses are:
Display-only. |
Created on |
The date when the system created the customer loyalty membership. The background jobs create customer loyalty memberships based on order activity that affects the customer’s order history, external sales dollars, or customer class. Numeric, 6 positions (in user date format); display-only. |
Changed on |
The most recent date when the customer loyalty membership was updated. Numeric, 6 positions (in user date format); display-only. |
Cancel reason |
The cancel reason you used when canceling the customer loyalty membership. The description is to the right. Displayed only for loyalty memberships in Canceled status. Reason: numeric, 2 positions; display-only. Description: alphanumeric, 30 positions; display-only. |
Cancelled on |
The date when the customer loyalty membership was canceled. Displayed only for loyalty memberships in Canceled status. Numeric, 6 positions (in user date format); display-only. |
Discount start date |
The date when the loyalty discount and other options (free freight, backorder priority) become effective. The same as the Created on date. Numeric, 6 positions (in user date format); display-only unless the Change customer membership flag for the loyalty membership type is selected. |
Discount end date |
The last date to apply the loyalty discounts and other options (free freight, backorder priority). Calculated by the system when it creates the customer loyalty membership, based on the Discount duration specified for the loyalty program. See Working with Membership Programs (WWMP) for more information. Numeric, 6 positions (in user date format); display-only unless the Change customer membership flag for the loyalty membership type is selected. |
Discount % |
The discount percentage that defaults to the customer’s orders based on membership in the loyalty program. The percentage defaults from the Discount percent specified for the loyalty program. See Working with Membership Programs (WWMP) for more information. Numeric, 5 positions with a two-place decimal; display-only unless the Change customer membership flag for the loyalty membership type is selected. |
Free freight |
Selecting this field indicates that free freight defaults on the customer’s orders. This setting defaults from the Free freight setting for the loyalty program. See Working with Membership Programs (WWMP) for more information. Display-only unless the Change customer membership flag for the loyalty membership type is selected. |
Priority B/O |
Indicates the backorder priority, if any, that defaults to the customer’s orders. 9 indicates the highest priority, while 0 is the lowest priority. This setting defaults from the Priority B/O field for the loyalty program. See Working with Membership Programs (WWMP) for more information. Numeric, 1 position; display-only unless the Change customer membership flag for the loyalty membership type is selected. |
Changing Customer Membership Status, Rotation or Release Date
Canceling a Customer Membership
Select Cancel for a membership at the Work with Customer Memberships Screen to display the Confirm Cancel Request pop-up window. If you select OK at this window, the system displays the Enter Cancel Reason pop-up window, where you must enter a cancel reason.
Cancel reason code: This window requires a cancel reason code. The cancel reason code is a 2-position, numeric code, defined in and validated against the Cancel Reason Code table; see Establishing Cancel Reason Codes (WCNR).
The system stores the cancel reason code for the item in the Customer Membership table.
You can cancel a membership only if its status is Active (A) or Inactive (I).
Cautions: Canceling a membership does not:
- affect any open, unshipped orders you have already generated for the membership.
- delete the membership; it remains on the system. See Deleting a Customer Membership on how to remove a membership you created in error.
- delete the membership item from the quote or order where it originated.
- generate a refund for the remaining cash amount for a prepaid membership. You will need to create and generate the refund separately.
Note:
Canceling a loyalty membership does not prevent the background jobs from creating a new loyalty membership for the customer the next time there is order activity.Email notification: If the Membership Cancellation Email Program (K77) system control value specifies a valid program name, the system generates the membership cancellation email or Outbound Email XML Message (CWEmailOut) when you cancel a membership as described above. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). And see Membership Cancellations for a discussion.
Canceling through order maintenance: You can also cancel a standard customer membership in order maintenance by canceling the order or membership item that created the customer membership. See Canceling a Membership Item.
Canceling a membership in order maintenance does not generate the email notification.
You cannot cancel a loyalty membership in order maintenance, since loyalty memberships are created by the system and not by adding a membership item to an order.
Deactivating a Customer Membership
Select Deactivate for a membership at the Work with Customer Memberships Screen to change the membership's status from Active (A) to Inactive (I). The system will not generate any new orders for an inactive membership, and any discount will not apply to any orders the customer places.
You can deactivate a membership only if its current status is Active.
Note:
The system does not send a deactivation notification email to the customer if you deactivate a loyalty membership using this method. See Loyalty Memberships for more information.Activating a Customer Membership
Select Activate for a membership at the Work with Customer Memberships Screen to change the membership's status from Inactive (I) to Active (A).
The system displays the Override Release Date pop-up window.
You can activate a membership only if its current status is Inactive.
Changing Release Date or Rotation for a Customer Membership
Select Change release date/rotation for a standard customer membership at the Work with Customer Memberships Screen to display the Override Release Date pop-up window.
Release date: Enter the next date when the order should be eligible for release. The next release date must be later than the current date and the Last order date.
Note:
- Eligible for release date change? You can change the release date only for a standard customer membership that includes items that are scheduled for shipment on the next rotation. You can review the items on the customer membership by selecting Details.
- No automatic customer notification: If you change the release date, there is no mechanism to automatically notify the customer of the new date or change the order message that was written as a result of the Write Order Messages for Membership Rotation (K04) system control value.
Rotation: Enter the next rotation to use when you generate an order for the membership. The current setting to the Next rotation field defaults. The system will select items based on the rotation you enter. You cannot enter a rotation number if there are no items for the membership assigned to that rotation.
You can display this window only if the membership is currently in Active (A) or Inactive (I) status. This option is not available for loyalty customer memberships.
Note:
You can also display this window by selecting Release Date at the Customer Membership Screen (Change Mode).Summary of Status Change Options for Customer Memberships
The options available for changing a membership's status or release date at the Work with Customer Memberships Screen are:
If current status is... | Then you can... | ||||
---|---|---|---|---|---|
Cancel | Activate | Deactivate | Change Release Date | Change Rotation | |
Note: Standard customer memberships only. Not available for loyalty memberships |
|||||
Active |
Yes |
No |
Yes |
Yes |
Yes |
Inactive |
Yes |
Yes |
No |
Yes |
Yes |
Canceled |
No |
No |
No |
No |
No |
Completea |
No |
No |
No |
No |
No |
In Processa |
No |
No |
No |
No |
No |
Display Membership Orders Screen
Purpose: Use this screen to review the orders that have been generated for a standard customer membership and to select an order for inquiry. Only orders that have been generated through the selected customer membership appear on this screen.
How to display this screen: Select Orders for customers for a membership at the Work with Customer Memberships Screen.
Note:
This option is not available for loyalty customer memberships.Field | Description |
---|---|
Customer # |
A unique number to represent the sold-to customer who ordered the membership. The name of the customer appears to the right. Number: numeric, 9 positions; display-only. Name: alphanumeric 41 positions; display-only. |
Membership ID |
A code that identifies the membership program in which the customer is enrolled. Alphanumeric, 12 positions; optional. |
Sequence number (Unlabeled field to the right of the membership ID) |
A unique number to identify the membership program for this customer. The sequence number is separated from the membership ID by a hyphen (-). If there is only one customer membership for the same customer and membership program, the sequence number will be 1. Numeric, 3 positions; display-only. |
Date |
The date the order was generated. Numeric, 6 positions (in user date format); optional. |
Order# (Order number) |
A unique number to identify the order. Numeric, 8 positions; optional. |
Sts (Status) |
The status of the order. Valid values are:
Optional. |
Rcp (Recipient) |
The number of recipients for the order. Normally, this number will be 1 unless you added a recipient in order maintenance. Numeric, 3 positions; display-only. |
Order total |
The total dollar value of the order. Numeric, 20 positions with a 2-place decimal; display-only. |
Ent (Entity) |
A code representing the entity associated with the source code on the order header. See Working with Entities (WENT). Numeric, 3 positions; display-only. |
Activity |
Codes that indicate whether any of the items on the order have been returned, exchanged, or backordered. Each of these valid values may appear:
Alphanumeric, three 2-position fields; display-only. |
R/E date (Return/exchange date) |
The date when you last received a returned item against the order. Numeric, 6 positions (in user date format); display-only. |
Screen Option | Procedure |
---|---|
Select an order for inquiry |
Select an order. You advance to either the standard order inquiry header or detail screen, depending on the setting of the Default Version for Order Inquiry (C34) system control value. |
Deleting a Customer Membership
Purpose: To delete a standard customer membership, you must advance to the Customer Membership Screen (Change Mode) and select Delete.
You can delete a standard customer membership only if its status is Active or Inactive, and you have not generated any orders for the membership. If you have already generated one or more orders, you will need to cancel the membership; see Canceling a Customer Membership.
To delete: Select Delete to delete the customer membership. The system displays the Confirm Delete pop-up window.
Prepaid memberships: If you have entered a cash prepayment amount, the system does not generate a refund when you delete the membership; you must do so separately.
Note:
This option is not available for loyalty customer memberships.Alternate Shipping Address Screen (Change Mode)
Purpose: Use this screen to define an alternate shipping address to use for orders you generate for the standard customer membership. For example, you would use this screen to enter a vacation or summer address.
Note:
Your entries on this screen do not update any open, unshipped orders you have already generated for the membership.How to display this screen: Select Alt Ship at the Customer Membership Screen (Change Mode).
Note:
This option is not available for loyalty customer memberships.When you select Alt Ship at the Customer Membership Screen in Display mode, the Alternate Shipping Address screen is also in Display mode. You cannot change any information in this mode.
Field | Description |
---|---|
Customer# |
A unique number to represent the sold-to customer who ordered the membership. Numeric, 9 positions; display-only. |
Customer name (Unlabeled field to the right of the customer number |
The name of the customer who ordered the membership. Alphanumeric, 41 positions; display-only. |
Order# |
The order on which the customer ordered the customer membership. This field does not appear if you created the customer membership through Working with Customer Memberships (WWCM) Numeric, 8 positions; display-only. |
Membership ID |
A code that identifies the membership program in which the customer is enrolled. Alphanumeric, 12 positions; display-only. |
Description (Unlabeled field to the right of the membership ID) |
The description of the membership program. Alphanumeric, 30 positions; display-only. |
Type |
A code that identifies the type of membership program. You can use membership types to group membership programs, to control whether any of the settings for the membership program can be overridden for specific customer memberships, or to identify loyalty membership programs. Alphanumeric, 2 positions; display-only. |
Name |
The following 5 fields are available for you to enter the customer's full name: Prefix A title (such as "Mrs." or "Dr.") that precedes the customer's name. Alphanumeric, 3 positions; optional. First Name The customer's first name Alphanumeric, 15 positions; optional. Initial The initial of the customer's middle name. Alphanumeric, 1 position; optional. |
Last Name The customer's last name. Alphanumeric, 25 positions; required if company name is not present. Suffix An addition to the customer's full name (such as "M.D.," "Fr.," or "III"). The suffix will print on labels, reports, etc., but is not accessible to scans. Alphanumeric, 3 positions, optional. |
|
Company |
The name of the company. Alphanumeric, 30 positions; required if last name is not present. |
Address |
The customer's street address. This is the primary delivery address. Alphanumeric, 32 positions; required. |
Apt./suite (Apartment/suite) |
The apartment number or suite number associated with the customer's delivery address. Follow these steps to enter an apartment or suite address: 1. Enter APT to indicate an apartment or STE to indicate a suite. 2. Insert a space and enter the number of the apartment or suite, for example: APT 4 or STE 116. Addresses must conform to United States Parcel Service (USPS) address formatting field description standards. For example, always precede the apartment or suite number with the appropriate abbreviation (for example, APT or STE). Alphanumeric, 10 positions; optional. |
Additional address (Unlabeled fields below the street address) |
Three additional lines of the customer's delivery address. If the address represents a post office box, you must enter P.O. Box on the first line to meet USPS delivery regulations. Alphanumeric, three 30-position lines; optional. |
Postal code |
The postal or zip code for this customer. This code represents a delivery area. Required only if the Require postal code? flag is selected for the country; see Setting Up the Country Table (WCTY). If a postal code is required, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP). Note: The system fills in the City and State fields appropriately if you set up the Postal Code/City/State table and you enter a valid postal code.Alphanumeric, 10 positions; required or optional based on country. |
City |
The city where the customer lives or receives mail or shipments. Alphanumeric, 25 positions; required. |
State |
The state or province where the customer lives or receives mail or shipments. State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Required only if the Require state? flag is selected for the country. The system validates that the state you enter is assigned to the SCF for the postal code. Alphanumeric, 2 positions; required or optional based on country. |
Country |
The code for the customer's country. Country codes are defined in and validated against the Country table. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required. |
Delivery |
Identifies a business (commercial) or residential address, and is used to calculate shipping charges for shippers that use rate tables (such as U.P.S.). The value in the Default Delivery Code for New Order Entry Customers (D13) system control value defaults here; however, you can override this default. If you clear this field and select OK, the system assigns the default delivery code to the shipping address.
Only Business and Residential are valid values for U.P.S. The system defines the shipper on an order as U.P.S. if the Type field in the Ship Via table = U; see Working with Ship Via Codes (WVIA). Required. |
Start date |
The first date when orders should be shipped to the alternate address. You can leave both the Start date and Stop date blank to use the alternate address indefinitely. You can also enter a Start date and leave the Stop date blank; the system displays a message requiring you to select OK to confirm. You cannot complete both this field and the Start with shipment field. Numeric, 6 positions (in user date format); required if you enter a stop date. |
Stop date |
The last date when orders should be shipped to the alternate address. You can leave both the Start date and Stop date blank to use the alternate address indefinitely; however, the Start date or the Start with shipment field is required if you enter a Stop date. You can also enter a Start date and leave the Stop date blank; the system displays a message requiring you to select OK to confirm. Numeric, 6 positions (in user date format); optional. |
Start with shipment |
Indicates the first shipment to use the alternate shipping address. For example, if you enter 5 in this field, the fifth order and subsequent orders for the membership will be shipped to the alternate address. You cannot complete both the Start date and this field. Numeric, 3 positions; optional. |
End with shipment |
Indicates the last shipment to use the alternate shipping address. For example, if you enter 10 in this field, the system will use the alternate shipping address up to the tenth order, then stop. Numeric, 3 positions; optional. |
Note:
You must advance to this screen from the Customer Membership Screen (Change Mode), not Display mode, to enter or change an alternate address.Your entries on this screen do not update any orders you have already created for the membership.
Screen Option | Procedure |
---|---|
Delete the alternate shipping address |
Select Delete. Note: Deleting the alternate address from the membership will not update any open, unshipped orders for the membership. |
Customer Membership Recipient Screen (Change Mode)
Purpose: Use this screen to enter information on a customer who will receive shipments on orders you generate for a standard customer membership.
Unlike the alternate shipping address, the recipient customer refers to a separate customer in the Customer Sold To table.
Note:
This option is not available for loyalty customer memberships.Change or Create Options for a Membership Recipient
If a recipient customer is not already assigned:
- Select a customer to assign to the membership: Click on the arrow in the first enterable field on the screen to advance to the Select Customer Sold To pop-up window. You can use this window to select an existing sold-to customer, who will be assigned to any future orders you generate for the membership. Existing open, unshipped orders for the membership will not be updated. However, if you make any changes to the customer's name and address information at the time you are assigning the customer to the membership, both the customer's record in the Customer Sold To table and any existing orders will be updated with the new information.
- Create a new customer to assign to the membership: Complete the fields on this screen to create a new customer sold-to, who will be assigned to any future orders you generate for the membership. Existing open, unshipped orders will not be updated.
If a recipient customer has already been assigned:
- Change the assigned customer's name and address information: Any changes you make to the customer's name and address information update both the customer's record in the Customer Sold To table and any existing orders.
- Assign a different customer as a recipient for the membership: Click on the arrow in the first enterable field on the screen to advance to the Select Customer Sold To pop-up window. You can use this window to select an existing sold-to customer, who will be assigned to any future orders you generate for the membership. Existing open, unshipped orders for the membership will not be updated.
- Remove the recipient customer from the membership: Return to the Customer Membership Screen (Change Mode) and delete the Recipient field to clear it. Any future orders you generate for the membership will not include the recipient customer; however, existing open, unshipped orders for the membership will not be updated.
How to display this screen: You can display this screen by selecting Alt Ship at the Customer Membership Screen (Change Mode). You can also display this screen by:
- clicking on the arrow in the Recip field on the Customer Membership Screen (Change Mode), then selecting Exit at the Select Customer Sold To pop-up window.
- Selecting Recipient at the Customer Membership Screen (Change Mode).
When you select Alt Ship at the Customer Membership Screen in Display mode, the Customer Membership Recipient screen is also in Display mode. You cannot change any information in this mode.
Field | Description |
---|---|
Sold to (Sold-to customer number) |
A unique number to represent the sold-to customer who ordered the membership. Numeric, 9 positions; display-only. |
Customer name (Unlabeled field to the right of the customer number) |
The name of the customer who ordered the membership. Alphanumeric, 41 positions; display-only. |
Customer name (Unlabeled field to the right of the customer number) |
The name of the customer who ordered the membership. Alphanumeric, 41 positions; display-only. |
Membership ID |
A code that identifies the membership program in which the customer is enrolled. Alphanumeric, 12 positions; display-only. |
Description (Unlabeled field to the right of the membership ID) |
The description of the membership program. Alphanumeric, 30 positions; display-only. |
Type |
A code that identifies the type of membership program. You can use membership types to group membership programs, or to indicate whether any of the settings for the membership program can be overridden for specific customer memberships. Alphanumeric, 2 positions; display-only. |
Recipient# |
The sold-to customer number of the recipient assigned to the customer membership. To change the recipient number, select Exit to return to the Customer Membership Screen (Change Mode), where you can enter a different number or select Header to create a new sold-to customer as a recipient for the membership. This field is blank if you have not yet assigned a recipient customer to the membership. If you complete the information on this screen, the system creates a new sold-to customer and assigns that customer as the recipient for the membership. Numeric, 9 positions; display-only. |
Name |
The following 5 fields are available for you to enter the customer's full name: Prefix A title (such as "Mrs." or "Dr.") that precedes the customer's name. Alphanumeric, 3 positions; optional. First Name The customer's first name Alphanumeric, 15 positions; optional. Initial The initial of the customer's middle name. Alphanumeric, 1 position; optional. |
Last Name The customer's last name. Alphanumeric, 25 positions; required if company name is not present. Suffix An addition to the customer's full name (such as "M.D.," "Fr.," or "III"). The suffix will print on labels, reports, etc., but is not accessible to scans. Alphanumeric, 3 positions, optional. |
|
Company |
The name of the company. Alphanumeric, 30 positions; required if last name is not present. |
Address |
The customer's street address. This is the primary delivery address. Alphanumeric, 32 positions; required. |
Apt./suite (Apartment/suite) |
The apartment number or suite number associated with the customer's delivery address. Follow these steps to enter an apartment or suite address: 1. Enter APT to indicate an apartment or STE to indicate a suite. 2. Insert a space and enter the number of the apartment or suite, for example: APT 4 or STE 116. Addresses must conform to United States Parcel Service (USPS) address formatting field description standards. For example, always precede the apartment or suite number with the appropriate abbreviation (for example, APT or STE). Alphanumeric, 10 positions; optional. |
Additional address (Unlabeled fields below the street address) |
Three additional lines of the customer's delivery address. If the address represents a post office box, you must enter P.O. Box on the first line to meet USPS delivery regulations. Alphanumeric, three 30-position lines; optional. |
Postal code |
The postal or zip code for this customer. This code represents a delivery area. If a postal code is required, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP). Note: The system fills in the City and State fields appropriately if you set up the Postal Code/City/State table and you enter a valid postal code.Alphanumeric, 10 positions; required or optional based on country. |
City |
The city where the customer lives or receives mail or shipments. Alphanumeric, 25 positions; required. |
State |
The state or province where the customer lives or receives mail or shipments. State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Required only if the Require state? flag is selected for the country. The system validates that the state you enter is assigned to the SCF for the postal code. Alphanumeric, 2 positions; required or optional based on country. |
Country |
The code for the customer's country. The value in the Default Country for Customer Address (B17) system control value defaults, but you can override it. Country codes are defined in and validated against the Country table. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required or optional, based on country. |
Delivery |
Identifies a business (commercial) or residential address, and is used to calculate shipping charges for shippers that use rate tables (such as U.P.S.). The value in the Default Delivery Code for New Order Entry Customers (D13)system control value defaults here; however, you can override this default. If you clear this field and select OK, the system assigns the default delivery code to the shipping address.
Only Business and Residential are valid values for U.P.S. The system defines the shipper on an order as U.P.S. if the Type field in the Ship Via table = U; see Working with Ship Via Codes (WVIA). Required. |
Gift |
Indicates whether the order is flagged as a gift. Valid values are:
Flagging an order as a gift can control:
See Performing Pick Slip Generation. The Default “Gift Order” Flag (D14) system control value does not affect the default setting for this field. |
Day |
The customer's daytime phone number. Alphanumeric, 14 positions; optional. |
Eve |
The customer's evening phone number. Alphanumeric, 14 positions; optional. |
Fax or Mobile |
The customer's fax machine or mobile phone number. The Third Phone Number Type (L53) system control value determines the label for this field. Alphanumeric, 14 positions; optional. |
Email address |
The customer’s email address. See Email Address Validation for an overview of how the system verifies that the email address you enter is formatted correctly. Primary email address: A plus sign (+) next to the email address indicates that there are additional email addresses on file for the customer; the email address on this screen is the customer’s primary email address, which displays on screens that include the customer email address and defaults in order entry. If you enter a new email address, the address you enter becomes the customer’s current primary email address, although the existing email addresses for the customer remain in the Customer Sold To Email table. Entering a new email address: If you overwrite the existing email address in this field, the system flags your entry as the primary email address for the customer, but retains the previous email address in the Customer Sold To Email table. In order to delete the previous email address, you need to prompt (by clicking on the right-facing arrow) to display the Select Customer Email Address Screen and delete the previous email address there. See Working with Customer Email Addresses for an overview. Deleting the email address: Similar to entering a new email address, if you delete the email address at this screen, the system removes the primary email flag for the address but retains the address in the Customer Sold To Email table. Alphanumeric, 50 positions; optional. |
Generating Membership Orders (EGMO)
Purpose: Use the Generate Customer Membership Orders menu option to generate orders for standard customer memberships.
In this topic:
- Generate Membership Orders Screen
- Membership Order Generation Process
- Release Membership Orders (RMEM)
- Memberships in Error Report
- Active Procedure Log
Generate Membership Orders Screen
How to display this screen: Enter EGMO in the Fast path field at the top of any menu or select Generate Membership Orders from a menu.
Field | Description |
---|---|
Up to release date |
The latest release date for the system to consider when evaluating customer memberships for order generation. Only standard memberships whose next release date is on this date or earlier are eligible to generate orders. The current date defaults, but you can override it. Numeric, 6 positions (in user date format); required. |
Order date |
The system assigns the date you enter here as the Order date and Entered date for each generated membership order; however, demand updates (such as Order Billing History) use the actual system date. The current date defaults, but you can override it to a future date. Note: The order date you enter here is included in the order confirmation email, even if you enter a future date. If the order is eligible for an order confirmation email and the order is in open or held status, the background job generates the order confirmation immediately, regardless of whether the order date is in the future.See Updates During Background Processing for a listing of tables updated by the ORDR_ASYNC job, including demand updates. Numeric, 6 positions (in user date format); required. |
Select membership types |
The membership type(s) for the system to consider when evaluating customer memberships for order generation. You can enter up to five membership types, or leave all these fields blank to evaluate all memberships regardless of type. Membership types are defined in and validated against the Membership Type table; see Working with Membership Types (WWMT). Discount-only memberships: If you sell memberships for the purpose of applying a discount to customer orders, but that do not generate orders, you can use these fields to select other membership types and exclude the discount-only type. Otherwise, any discount-only memberships will appear on the memberships in error report because they do not include any items. Note: The system does not evaluate loyalty membership types for order generation.Alphanumeric, five 2-position fields; optional. |
Instructions: Follow these steps at the Generate Membership Orders Screen to start the Membership Order Generation Process:
- Complete the required fields and any optional fields as described above.
- Select OK. The system validates your entries and highlights any fields you need to correct. Correct any fields and select OK again.
- Select Generate Orders.
For more information: See Membership Overview.
Membership Order Generation Process
Process overview: You can choose to generate membership orders based on the membership type and release date. When you begin the generation process, the system starts the GEN_ORDERS job, which:
# | Step |
---|---|
1. |
Selects each customer membership that is eligible to generate an order, based on the membership's status (which must be active) and next release date (which must be on or earlier than the selection date). If you specify one or more membership types, the membership must be one of the specified types, as well. |
2. |
Evaluates the customer membership for errors, and includes these memberships on the Memberships in Error Report. Errors are:
|
3. |
Selects each item to include on generated orders, based on the item's status (which must be active) and the rotation number (which must be the same as the current rotation for the membership header or the rotation must be 1 or zero, indicating to always include the item). |
4. |
Creates orders, which it then evaluates in the same way as orders you create through the generic order API; this edit flags errors such as a missing item price or invalid SCF/ship via combination. |
5. |
Automatically assigns the “best way” ship via with the lowest overall shipping charges to the order if the ship via for the customer membership matches the Best Way Ship Via for Auto-Assignment (J67); see that system control value for more information. |
6. |
When creating the order payment method for the order, uses the CIT Transaction ID and the original authorization amount from the customer membership, if they are populated, identifying the order as a subsequent card-holder initiated transaction with credentials on file. These fields would be populated through the integration with CyberSource or through the External Payment Service, either through the order originating the customer membership, or through a generated order that was authorized through CyberSource or the External Payment Service. Otherwise, these fields on the payment method for the generated order are updated when the order is authorized through CyberSource or the External Payment Service, and in this case the customer membership is also updated with these fields. For more information: See:
|
7. |
Updates the customer membership:
|
8. |
Writes an order message to the generated order indicating the name of the membership program and the Next release date if the Write Order Messages for Membership Rotation (K04) system control value is selected. This order message is flagged to print on the pick slip, and the user ID identifies the user who submitted the membership generation job. See the system control value for more information. |
9. |
Assigns the suspended membership orders to an order batch. The batch is assigned to the user ID of the user who submitted the membership generation job. |
10. |
Puts orders with errors in Error status. |
11. |
Puts orders that are error-free in Open or Held status, removes the batch number from the order header, and applies pick slip preparation to the eligible orders; see Applying Pick Slip Preparation to an Order. |
12. |
Updates the customer membership with the next release date, shipment number, and rotation; also, changes the status if the current order completes the membership. |
Note:
The GEN_ORDERS job runs in the QSYSNOMAX job queue rather than the default QBATCH job queue in order to reduce conflicts with other submitted jobs.Generated reports: The GEN_ORDERS job produces:
- Memberships in Error Report
- Order Batch Listing. See Accepting or Rejecting the Order Batch for more information on this report.
Orders in error: Any membership orders that have any errors remain suspended in the generated batch. Use the Edit/Accept option on the Work with Error Orders Batches Screen to submit the batch to edit so that you can review the errors and then advance to an individual order in error so that you can correct it. See Accepting or Rejecting the Order Batch for more information.
Which order date to use? The system uses the Order date you enter at the Generate Membership Orders Screen as the Order date and Enter date for generated membership orders; however, all other updates are posted using the current date. For example, records in the Order Billing History table are created using the current date.
Active procedure check: Before the order accept process runs, the system checks to see whether there is already an order generation (GEN_ORDERS) job that is active in your company. If there is currently an active order generation job, the system stops the newly submitted job and generates the Active Procedure Log.
Loyalty memberships: The program ignores any loyalty memberships when generating membership orders. See Loyalty Memberships for an overview.
Tokenization: If the credit card number for a membership order has been replaced with a token, the system bypasses credit card validation; see the Data Security and Encryption Guide on My Oracle Support (1988467.1) for more information.
Email address? If the customer sold-to has a primary email address, this address defaults as the order-level email address; otherwise, there is no order-level email address assigned. See Generating Membership Orders (EGMO) for more information.
Membership orders without existing customer memberships: It is possible for the system to generate a membership order for which you cannot find the associated customer membership in the following situation:
- You receive an order that includes a membership item and that is in error for some reason. For example, you receive an order through the order API, and the order includes both a membership item and another order detail line that is in error status because it failed an edit related to order line quantity. In this situation, the system creates the customer membership even though the order is in suspended status.
- You run Generating Membership Orders (EGMO) and generate the membership order for the customer membership created through the suspended order.
- You then reject the order or the order batch, removing the suspended order that originated the customer membership.
Because the customer membership no longer exists, the system does not generate any additional membership orders for the customer.
Cancelling the membership item: If you cancel the membership item on the order that originated the customer membership after you have used the membership generation process, a pop-up window opens:
- If a membership order has already been generated: The Order Warning Message Window indicates that one or more membership orders have already been generated for the customer membership, and that you need to cancel the generated orders manually; however, canceling the membership item results in canceling the remainder of the customer membership, so the program will not generate any additional orders.
- If the membership generation program is currently running, or if it has generated an order but the order is still suspended in batch: The Membership in Process Window indicates that the membership is currently being processed. You will need to cancel the generated order and the customer membership to prevent additional orders from being generated.
See Canceling a Membership Item for more information.
Printing the Expected Membership Orders Report (PEMO)
Purpose: Use the Expected Membership Orders report to review the total number of membership orders that will be available for generation for a range of dates. The system uses the Next release date from the customer membership to calculate these totals. This report provides a summary of total quantity by date only, and does not include detail information on the membership programs, membership types, customers, or items.
For more information: See Membership Overview for an explanation of how membership programs work, or see Generating Membership Orders (EGMO) for information on how to generate orders for membership programs.
Loyalty memberships: This report does not consider loyalty memberships, which do not generate orders. See Loyalty Memberships for an overview.
In this topic:
Print Expected Membership Orders Screen
How to display this screen: Enter PEMO in the Fast path field at the top of any menu or select Print Expected Membership Orders from a menu.
Field | Description |
---|---|
Starting with release date |
The first release date to include on the Expected Membership Orders Report. The system includes customer memberships whose Next release date is on this date or later. The current date defaults. Numeric, 6 positions (in user date format); required. |
Ending with release date |
The last release date to include on the Expected Membership Orders Report. The system includes customer memberships whose Next release date is on this date or earlier. The current date defaults. Numeric, 6 positions (in user date format); required. |
Completing this screen: Select Submit to generate the report. You return to a menu, and the system submits the EXP_ORDERS job.
Update Customer Memberships (MMCM)
Purpose: Use this option to update the source code and/or any one item on customer memberships and, optionally, the membership program itself.
For more information: See:
- Membership Overview
- Working with Membership Programs (WWMP)
- Working with Customer Memberships (WWCM)
- Generating Membership Orders (EGMO)
Note:
Even if a membership program is flagged not to allow changes based on the membership type, you can still process updates through the this menu option.Update Customer Memberships Screen
How to display this screen: Select Update Customer Memberships from a menu or enter MMCM in the Fast path field on any menu.
Field | Description |
---|---|
Membership ID |
Enter the codes identifying the membership program(s) for which you would like to update the source codes and/or items on customer memberships. You can enter up to four membership programs. Entry of at least one membership program is required. Restrictions: The system does not verify whether there are any active customer memberships for the program(s) you enter, whether the membership program is currently active, or whether you are entering a type of membership program that actually generates orders. However, you cannot enter an Item to be Replaced and a New Item unless there is at least one customer membership for at least one of the membership program(s) you enter here. Alphanumeric, four 12-position fields; entry of the first field required. |
Source Code |
Optionally, enter the source code to assign to existing customer memberships. You can assign this source code to each selected membership program by selecting the Update Membership Program flag. You can enter a source code only if it is not restricted. Effects of update:
Example: You enter the membership ID’s of MEMB01 and MEMB02 and enter a Source Code of MBS23. When you select OK, the system changes the source code for all MEMB01 and MEMB02 customer memberships to MBS23. If you generate membership orders tomorrow, the generated orders will have source code MBS23. However, orders you generated yesterday are still assigned to the source code(s) previously assigned to the MEMB01 and MEMB02 customer memberships.
Example: To continue the example above, you also update the MEMB01 and MEMB02 membership programs themselves. The next time you create a customer membership, it will be assigned to the MBS23 source code by default. Alphanumeric, 9 positions; optional (required if you do not enter an Item to be Replaced and a New Item). |
Item to be Replaced |
Optionally, enter the item (and SKU, if the item has SKUs) to remove from existing customer memberships and replace with the New Item. You can also remove this item and SKU from each selected membership program and replace it with the New Item by selecting the Update Membership Program flag. Restrictions: You cannot perform an item update on just membership programs if the Item to be Replaced is not on at least one customer membership for one of the selected programs. To update just the membership programs, use Working with Membership Programs (WWMP). However, once you attempt to enter an Item to be Replaced, you cannot clear the item fields and submit just a source code update; instead, you need to exit the screen and re-enter. Effects of update:
Example: You enter the membership ID’s of MEMB01 and MEMB02, enter an Item to be Replaced of AB0101 SMLL, and enter a New Item of BC0202. When you select OK, the system removes the item AB0101 SMLL for all MEMB01 and MEMB02 customer memberships, and adds BC0202. If you generate membership orders tomorrow, the generated orders will include BC0202. However, orders you generated yesterday still include AB0101 SMLL. Example: To continue the example above, you also update the MEMB01 and MEMB02 membership programs themselves. The next time you create a customer membership, it will include BC0202 (but not AB0101 SMLL) by default. Note: The system adds the New Item to the customer membership (and, optionally, membership program) only if the Item to be Replaced was already on the customer membership or membership program. For example, if you entered membership programs MEMB01, MEMB02, and MEMB03, but only customer memberships for MEMB01 included the Item to be Replaced, then customer memberships for MEMB02 and MEMB03 are not updated when you select OK.Alphanumeric, 12 positions with three four-position SKUs; optional (required if you do not enter a Source Code). |
New Item |
Enter the item (and SKU, if the item has SKUs) to add to existing customer memberships when removing the Item to be Replaced. You can also add this item and SKU to each selected membership program by selecting the Update Membership Program flag. See the Item to be Replaced field, above, for a discussion. Restrictions: You cannot enter a New Item unless you are replacing an item that is already on customer memberships (and, optionally, the selected membership program(s)). Alphanumeric, 12 positions with three four-position SKUs; required if you enter an Item to be Replaced. |
Update Membership Program |
Indicates whether to update the selected membership program(s) in addition to the existing customer memberships with the indicated source code and/or item replacement: Selected (default) = Update each selected membership program with the source code; also, if the Item to be Replaced is on the membership program, replace it with the New Item Unselected = Do not update any of the membership programs |
Completing this screen:
- Complete each field as described above.
- Select OK to validate your entries. See the field descriptions above for more information.
- Once you have completed each required field, select OK to update each eligible customer membership and membership program, if applicable. The update takes place interactively.
Email Repository
In this part:
- Working with Email Category (WEMC) provides information on setting up categories for tracking and grouping emails.
- Working with Email (WEML) provides information on reviewing unrouted emails and assigning them to customers and orders.
- Purging Email History (MPCH) provides information on purging emails earlier than a given date.
- Updating Email Domains (MUEE) provides information on making universal updates to the domain name for all matching email addresses in your company.
- Printing the Email Error Report (PEME) provides information on printing a report listing all email addresses in your company that do not conform to formatting requirements.
Working with Email Category (WEMC)
Purpose: Use email categories to group email correspondence for scanning or informational purposes. You can assign an email category to an email at various screens where you work with email correspondence.
Notification category: The system uses the NTF category for any email notification generated by the system. For example, when you use the Generate Backorder Notices (GBOC) menu option, the system assigns an email category of NTF to each backorder notification email generated. The system automatically creates the NTF category the first time that you advance to the Work with Email Category Screen.
Note:
The system saves outbound notification emails only if the Write Outbound Email to Email Repository (H99) system control value is selected.For more information see the Email Repository Overview in the Web Services Guide on My Oracle Support (ID 2149144.1).
In this topic:
Work with Email Category Screen
How to display this screen: Enter WEMC in the Fast path field at the top of any menu, or select Work with Email Category from a menu.
Field | Description |
---|---|
Category |
The category that you use to group email correspondence between you and your customers. Enter a full or partial category to display email categories in alphanumeric order, starting with your entry. Alphanumeric, 3 positions; optional. |
Description |
The description of the category. Enter a full or partial description to display email categories in alphanumeric order that contain your entry. Alphanumeric, 40 positions; optional. |
Option | Procedure |
---|---|
Create an email category |
Select Create to advance to the Create Email Category Screen. |
Change an email category |
Select Change for a category to advance to the Change Email Category screen. You can change the Description. See Create Email Category Screen for field descriptions. |
Delete an email category |
Select Delete for a category to delete it. Note: The system does not prevent you from deleting a category that is currently assigned to one or more emails. |
Display an email category |
Select Display for a category to advance to the Display Email Category screen. See Create Email Category Screen for field descriptions. You cannot change any information on this screen. |
Create Email Category Screen
Purpose: Use this screen to create a new email category.
How to display this screen: Select Create at the Work with Email Category Screen.
Field | Description |
---|---|
Category |
The category that you use to group email correspondence between you and your customers. Alphanumeric, 3 positions. Create screen: required. Change screen: display-only. |
Description |
The description of the category. Alphanumeric, 40 positions; required. |
Working with Email (WEML)
Purpose: Use Work with Email to review and work with emails that have been forwarded into Correspondence History and that are in error. For more information: See Email Repository Overview the Web Services Guide on My Oracle Support (ID 2149144.1) for more information on how the system processes forwarded emails.
Possible error reasons include:
- the email did not include sufficient information to assign it to a customer
- the email included conflicting information: for example, it specified a customer number and an order number, but the order number is not valid for that customer
- the email included invalid information, such as an email category that does not exist
- the email address in the email does not match an existing customer
- there is more than one customer with the email address in the email (Note: This condition produces an error only if the Assign Unreferenced Email (H93) system control value is set to *DUPE)
In this topic:
- Work with Unrouted Email Screen
- Change Email Screen
- Display Email Screen
- Display Email Detail Screen
- Symbol and Special Character Conversion in Emails
Work with Unrouted Email Screen
How to display this screen: Enter WEML in the Fast path field at the top of any menu, or select Work with Unrouted Email from a menu.
Field | Description |
---|---|
Date |
The date when the email was forwarded into the system. You can select Sort by email date to display the date when an email was originally sent (the Email sent date) rather than the date when it was forwarded into the system and the Correspondence History record was created (the Created on date). Similarly, after you have selected to display the Email sent date, you can select Sort by create date to switch the displayed date back to the Created on date. Numeric, 6 positions (in user date format); optional. |
Src (Source) |
Indicates whether the email was inbound or outbound. Valid values are:
A user-supplied code indicating the email’s source is not currently implemented. Normally, only inbound (EXT) emails are listed on this screen as unrouted. Alphanumeric, 3 positions; optional. |
Rsn (Reason) |
The reason why the system did not assign the email. Possible reasons are:
|
To determine the specific error(s) for an email, select Change for an email to advance to the Change Email Screen, where the system displays an error message. See Email Repository Overview for general information. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Optional. |
|
Cat (Category) |
A category that you use to group email correspondence between you and your customers. A category of NTF indicates that the email was a notification generated by the system and sent to the customer. Alphanumeric, 3 positions; optional. |
Email address |
The email address of the person who originated the email. Alphanumeric, 50 positions; display-only. |
Option | Procedure |
---|---|
Change an unrouted email |
Select Change for an email to advance to the Change Email Screen. |
Delete an unrouted email |
Select Delete for an email to delete it. |
Display an unrouted email |
Select Display for an email to advance to the Display Email Screen. |
Create a tickler for the MN (manually created) tickler event |
Select Create tickler for an email to advance to the Create Tickler Screen. |
Display email subject and text |
Select Display detail for an email to advance to the Display Email Detail Screen. |
Change display sequence by date |
Select FIFO to display emails in ascending chronological order (earliest to latest). Similarly, once FIFO is selected, Select LIFO to display emails in descending chronological order (latest to earliest). |
Change displayed date to the date email was originally sent |
Select Sort by email date to display the date when an email was originally sent (the Email sent date) rather than the date when it was forwarded into the system and the Correspondence History record created (the Created on date). Similarly, after you have selected to display the Email sent date, you can select Sort by create date to switch the displayed date back to the Created on date. You can use this option together with selecting FIFO to display emails in ascending or descending chronological order based on Created on date or Email sent date. The four possible sort options are:
The current sort is indicated in the upper left corner of the screen. |
Change Email Screen
Purpose:
- Unrouted email: An unrouted inbound email is an email that originated from a customer but has not been assigned to a customer because of insufficient or invalid identifying information. Use this screen to review the specific errors and other detail information, correct any errors, and assign the email. Any fields that are in error are highlighted when you advance to this screen, and an error message indicates the nature of the error.
- Routed email: A routed email is an inbound email or outbound email notification that is assigned to an customer and, potentially, additional records such as an order, bill-to customer, or purchase order. Use this screen to review detail information or to reassign the email differently if you have the proper authority; the Changed Routed Email (B08) secured feature controls access to this screen for routed (assigned) emails. If you do not have authority to change a routed email, you can use the Display Email Screen to review all of this information.
How to display this screen: Select Change for an email at the:
- Work with Unrouted Email Screen
- Work with Email by Order Number Screen
- Work with Email by Customer Sold To Number Screen
- Work with Email by Customer Ship To Number Screen
- Work with Email by Customer Bill To Number Screen
Field | Description |
---|---|
Created on |
The date and time that the email was received into Order Management System and the Correspondence History record was created. Date: numeric, 6 positions (in user date format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. |
Email sent |
The date and time when the email originated. This is not the date and time when you forwarded an external email into Order Management System, but the date and time when a forwarded email was originally sent. Because the date and time on an external systems can be set differently, it is possible for there to be discrepancies between this date and the date when the email record was created in Order Management System. In the case of an email notification generated by the system, the dates created and sent should be identical. Date: numeric, 6 positions (in user date format); display-only. Time: numeric, 6 positions (HH:MM:SS format); display-only. |
Subject |
The subject line of the email.
|
Alphanumeric, 78 positions; display-only. |
|
Email address |
The email address of the person who originated the email. Alphanumeric, 50 positions; display-only. |
Display name |
The name associated with the email address. Depending on the original email application, a forwarded message might include either the display name or the actual email address: Uses actual email address: -----Original Message----- From: lak@example.com Sent: 08/09/2006 10:33:38 AM Uses display name: -----Original Message----- From: Harry Truman Sent: 08/09/2006 10:33:38 AM Alphanumeric, 50 positions; display-only. |
CC |
The email addresses that were sent copies of the email. This field is truncated if the original information exceeded the maximum length in Order Management System. Alphanumeric, 50 positions; display-only. |
Source |
Indicates whether the email was inbound or outbound. Valid values are:
A user-supplied code indicating the email’s source is not currently implemented. Alphanumeric, 3 positions; display-only. |
Routed |
Indicates whether the email has been assigned to a customer. Valid values are:
|
Attachment |
Indicates if there was a file attached to the email. Attachments to emails forwarded into Order Management System are discarded; however, if you forward the email using the Outlook form, the form adds a flag to the subject line indicating that the email originally had an attachment. An attachment could be any sort of file that is sent along with the email, such as a document, image, script, or program. Valid values are:
|
Error reason |
The reason why the system did not assign the email. This field is set only for unrouted emails. Possible reasons are:
|
See Email Repository Overview for general information. For more information see the Web Services Guide on My Oracle Support (ID 2149144.1). Alphanumeric, 1 position; display-only. |
|
Category |
A category that you use to group email correspondence between you and your customers. A category of NTF indicates that the email was a notification generated by the system and sent to the customer. Category codes are defined in and validated against the Correspondence Category table; see Working with Email Category (WEMC). Alphanumeric, 3 positions; optional. |
Order number |
The order number and order ship-to number, if any, related to the email. The order ship-to number is separated from the order number by a hyphen (-). See Identifying an Unrouted Email for information on completing or correcting these fields for an unrouted email. Order number: numeric, 8 positions; optional. Order ship-to number: numeric, 3 positions; optional. |
Customer reference number |
A cross-reference code available to identify the customer with a record in another system. Validated against the Alt customer # field at the second Create Customer screen in customer maintenance, or an Alternate customer # cross reference from the Alternate Customer # Cross Reference table (see Working with Alternate Customer Number Cross-References). Note: If the Display Alternate Customer Cross Reference Window (I84) system control value is selected, the system selects the last customer numerically (that is, the most recently created customer) who matches based on the primary Alt customer # from the Customer Sold To table, if any; otherwise, it selects the last customer numerically who matches based on the Alternate customer # cross reference. If the Display Alternate Customer Cross Reference Window (I84) system control value is unselected, the system selects the last customer numerically who matches based on the Alternate customer # cross reference, regardless of whether there is also a match based on the Alt customer #.See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Alphanumeric, 15 positions; optional. |
Order reference number |
A cross-reference code available to identify the order with a record on another system. Validated against the E-commerce order number field in the Order Header Extended table; this field is displayed as the Alternate order field at the Display Order Properties Screen. See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Alphanumeric, 35 positions; optional. |
Customer sold to |
A number identifying the sold-to customer associated with the email. Validated against the Customer Sold To table. If a sold-to number is identified, the customer’s company name, if any, and name appear to the right. See Identifying an Unrouted Email for information completing or on correcting this field for an unrouted email. Customer number: numeric, 9 positions; optional. Customer name: alphanumeric, 41 positions; display-only. |
Customer ship to |
A number identifying a permanent shipping address associated with a sold-to customer. See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Numeric, 3 positions; optional. |
User code 1 |
A field available to enter a one-position code or flag. Not validated against any table. Alphanumeric, 1 position; optional. |
Customer bill to |
A number identifying a customer responsible for payment on an order. Validated against the Customer Bill To table. See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Numeric, 7 positions; optional. |
User code 2 |
A field available to enter a 10-position code. Not validated against any table. Alphanumeric, 10 positions; optional. |
Invoice number |
A number identifying the invoice with which an order was billed or credited. Validated against the Invoice Header table. See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Numeric, 7 positions; optional. |
User code 3 |
A field available to enter a 20-position code. Not validated against any table. Alphanumeric, 20 positions; optional. |
Vendor number |
A number identifying a vendor who supplies you with merchandise. Validated against the Vendor table. Ordinarily used here only for drop shop purchase orders associated with an order. See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Numeric, 7 positions; optional. |
User number |
A field available to enter a 13-position number. Not validated against any table. Numeric, 13 positions; optional. |
Purchase order number |
A number identifying a purchase order. Validated against the PO Header table. Ordinarily used here only for drop ship purchase orders associated with an order. See Identifying an Unrouted Email for information on completing or correcting this field for an unrouted email. Numeric, 7 positions; optional. |
User date |
A field available to enter a date. Numeric, 6 positions (in user date format); optional. |
Option | Procedure |
---|---|
Display the text of the email |
Select Display email detail to advance to the Display Email Detail Screen. |
Advance to standard order inquiry |
Select Order inquiry. If the email is associated with an order number, you advance to the Order Inquiry Header Screen or the Order Inquiry Detail Screen, depending on the setting of the Default Version for Order Inquiry (C34) system control value. If the email is not associated with an order number, you advance to the Order Inquiry Scan Screen. Note: This option is not available when you are working with a routed email in standard order inquiry. |
Accept your entries and assign the email |
After you have identified the email, select Accept. See Identifying an Unrouted Email below for more information. Note: This option is available only if you have the proper authority, based on the Changed Routed Email (B08) secured feature. |
Identifying an Unrouted Email
You can associate an email with any of the following:
- order-related information:
-
Order number and order ship-to number
-
Customer sold to number
-
Customer ship to number
-
Customer bill to number
-
Purchase order number (for drop shipments)
-
Vendor number (for drop ship purchase orders)
-
- customer-related information:
-
Customer sold to number
-
Customer ship to number
-
- Vendor number and Purchase order number
To associate an email with any of the above types of information, complete the field or prompt for a list of valid values.
When you complete a field, the system:
- Fills in the related fields if it can positively identify them. For example, when you enter an order-related field such as the order
number, the system fills in the customer sold-to number and the following
related fields if they exist on the order:
-
Customer ship-to number
-
Customer bill-to number
-
Order reference number
-
- Confirms that all entries on the screen are consistent. For example, if you complete the order number and the customer reference number, but the customer reference number is not correct for the customer sold-to on the order indicated, the system displays an error message.
Things to note: The system does not:
- Fill in a field if more than one possible relationship exists. For example, when you enter the order number, the system does not fill in the invoice number, because it is possible for an order to have more than one invoice.
- Confirm a relationship between a vendor number and order-related or customer-related information; however, the system does confirm that a purchase order number is consistent with a vendor number if you enter both, and fills in the vendor number if you enter just the purchase order number. The exception is drop ship purchase orders, in which the vendor number and purchase order number are validated as order-related information.
- Confirm a relationship between customer-related information and a bill-to number, unless order-related information is also identified.
- Assign the email if you specify just a bill-to customer without specifying a sold-to customer. The system accepts your entry, but leaves the email in unrouted status.
Selecting the correct customer or order: Select Order inquiry. If you have selected an order number, you advance to the Order Inquiry Header Screen or the Order Inquiry Detail Screen, depending on the setting of the Default Version for Order Inquiry (C34) system control value. You can review the order and customer information at these screens to see if they are consistent with what you know about the email.
If you have not selected an order number, you advance to the Order Inquiry Scan Screen. At these screens, you can scan on customer name or email address to help you identify the originator of the email and the related order, if appropriate.
When you have completed your inquiry, select Exit to return to the Change Email screen, where you can enter the appropriate information.
Accepting your entries: If there are no errors, select Accept to accept your entries and assign the email.
Rejecting your entries: Select Exit to exit the screen without accepting your entries. If you advanced to this screen from the Work with Unrouted Email Screen, a pop-up window prompts you to confirm that you are exiting.
Click Accept changes to accept your changes, OK to exit the screen without saving your changes, or Exit to return to the Change Email screen.
Display Email Screen
Purpose: Use this screen to review detailed information about an email. You cannot change any information at this screen. See Change Email Screen for field descriptions.
How to display this screen: Select Display for an email at the:
- Work with Unrouted Email Screen
- Work with Email by Order Number Screen
- Work with Email by Customer Sold To Number Screen
- Work with Email by Customer Ship To Number Screen
- Work with Email by Customer Bill To Number Screen
Display Email Detail Screen
Purpose: Use this screen to review the content of an email.
Note:
The system does not save the text of outbound email notifications, which are identified by a Src (Source) of INT (internal) and a Cat (Category) of NTF notification; however, you can review the subject line at the Change Email Screen or the Display Email Screen to determine the type of notification that was sent. The system saves a record of email notifications only if the Write Outbound Email to Email Repository (H99) system control value is selected.How to display this screen:
- Select Display detail for an email at the:
- Work with Email by Order Number Screen
- Work with Email by Customer Sold To Number Screen
- Work with Email by Customer Ship To Number Screen
- Work with Email by Customer Bill To Number Screen
- Select Display email detail at the:
Email text: The contents of the email are presented on this screen. The Email Presentation (I01) system control value controls the extent to which blank line spaces in the email are consolidated.
Field descriptions: See the Change Email Screen for a description of the remaining fields on this screen.
Symbol and Special Character Conversion in Emails
Emails are stored in the Correspondence History table in plain text. The table below describes how some commonly used symbols and special characters are rendered.
Symbol/character appearance | Description | Converted to: |
---|---|---|
< |
left angle bracket |
< |
— |
em dash |
- (hyphen) |
– |
en dash |
- (hyphen |
non-breaking space |
space |
|
© |
copyright symbol |
¤ |
® |
registration symbol |
« |
™ |
trademark |
(tm) |
¼ |
1/4 |
Ê |
½ |
1/2 |
Ë |
§ |
section symbol |
º |
¶ |
paragraph symbol |
à |
abcde |
symbol font |
abcde (regular text) |
The following characters are deleted from the email:
- ~ (tilda)
- | (pipe)
- optional hyphen
- em space
- en space
Purging Email History (MPCH)
Purpose: Use this menu option to purge email correspondence history created before a specific date. You might want to use this menu option to conserve disk space if the Correspondence History and Correspondence History Detail tables are large.
The system uses the creation date to determine the age of the email rather than the sent date.
Correspondence history related to open or held orders is not purged, regardless of date.
Purge Correspondence History Screen
The Date field on this screen defaults to blank; you must enter the earliest date for which you want to retain email correspondence history.
How to display this screen: Enter MPCH in the Fast path field at the top of any menu or select Purge Correspondence History from a menu.
Completing this screen: Enter the earliest date for which you want to retain email correspondence history and click Accept.
Updating Email Domains (MUEE)
Purpose: Use this function to universally update email addresses for a domain name. For example, you would use this function if ABC Corp. changed its name to XYZ Corp., and as a result all of its employees’ email addresses now end with @xyz.com instead of @abc.com.
Components of an email address: For the purposes of this menu option, the system searches for and replaces the domain name and/or the extension. For example, in direct@example.com, example is the domain name and com is the extension. These are the only components of an email address that you can update through this menu option. The entire domain name and extension must be an exact match; for example, @mail.com is not a match for @123mail.com.
When you use this function, the system updates the domain name for all matching email addresses in the following tables:
- Customer Sold To
- Customer Sold To Email
- Customer Ship To
- Customer Bill To
- Vendor (both vendor email and remittance email addresses)
- Vendor Contact
- Order Ship To Address
- OM Batch Header
- Soldout Notification
- Threshold Value
Update Email Address Domain Screen
How to display this screen: Enter MUEE in the Fast path field at the top of any menu, or select Update Email Address Domain from a menu.
Completing this screen: Enter the domain name that you want to change and the domain name you want to change it to. Your entry must include the correct position of the @ sign and the period: the domain name must begin with the @ sign, and the period must be followed by an extension, such as com or gov, of one or more characters. For example, the following are correctly formatted domain names for this menu option:
- @example.com
- @mailcity.org
- @university.edu
The system rejects any domain names formatted like:
- oracle.com
- @example
Important:
The system does not verify that your entry is actually a valid, existing domain name.Once you have entered the original and new domain names, Select Accept to submit. The system starts the UPDEMLDOM job and displays the following messages:
The update email address domain job has been submitted.
Printing the Email Error Report (PEME)
Purpose: Use this screen to generate a list of email addresses that are formatted incorrectly in the following tables:
- Customer Sold To
- Customer Sold To Email
- Customer Ship To
- Customer Bill To
- Vendor (both vendor email and remittance email addresses)
- Vendor Contact
- Order Ship To Address
- OM Batch Header
- Soldout Notification
- Threshold Value
In this topic:
When is an Email Address in Error?
An email address is considered in error if:
- there is not an @ sign and a period (.)
- there is no text:
- before the @ sign
- between the @ sign and the period
- after the period
For example, the following email addresses would appear on the error report:
- @example.com
- sbrown@example
- sbrown@.org
- www.example.com
Any additional validation? The system does not confirm that an entry represents a valid email address, or that the domain name (such as “company” in company.com) even exists.
Email Errors Report Screen
How to display this screen: Enter PEME in the Fast path field at the top of any menu, or select Email Error Report from a menu.
Completing this screen: Click Accept to submit the Email Errors Report.
Customer Service Appendices
Purpose: These topics provide reference information for use throughout the system.
- Displaying More Options in OIOM describes several options related to Order Inquiry, Order Maintenance and Order Entry that are not available on the regular screens.
-
Work with Customer Action Notes (WCAN): Use this menu option when you want to view or work with a list of all customer action issues for a company
- Loading Address Updates describes how to load and process a table containing Sold To Customer address updates, and how to review changed and unchanged customer information.
-
Process Address Changes Screen (PACS): Use this screen to process address changes when the ACS Tape or the MBS Tape tables are already loaded with address change information.
-
Work with Changed Customers Screen (MBSI): Use this screen to review the customer's name and address before and after the address updates
Work with Customer Action Notes (WCAN)
Purpose: Use this menu option when you want to view or work with a list of all customer action issues for a company. Using this menu option, you can delete, display, resolve, update the status of an issue, or attach detail notes for a customer action issue, by using options similar to those on the Edit Customer Actions Window. At the Work with Customer Actions menu option, you can also:
- View a list of all unresolved customer action issues for your company
- View the ID of the user who initially entered the customer action issue, as well as the ID of the user assigned to the customer action issue when it was created, or the most recent user to work with this customer action issue
- Scan for an action issue by reason code, status and date
- Advance to the Scan Orders by Customer screen (Order Inq)
- Advance to Order Inquiry Scan Screen
- Select another company
- Customer action issues that have been resolved do not display on this screen.
- You cannot create a note for a new customer action issue at this screen. Use the Edit Customer Actions Window to create a customer action note.
- You can print a report listing customer action notes by date or by the person who entered them. See Printing the Customer Exposure Report (PCER).
In this topic:
- Work with Customer Action Notes Screen
- Change Customer Action Screen
- Resolving or Deleting an Action Issue
- Customer Action Note Details Screen
For more information: See About Customer Action Notes.
Work with Customer Action Notes Screen
How to display this screen: Enter WCAN in the Fast path field at the top of any menu or select Work with Customer Action Notes from a menu.
Field | Description |
---|---|
Rn (Reason Code) |
The code representing the reason for the customer action issue. See Working with Customer Action Reason Codes (WCAR). Alphanumeric, 2 positions; optional. |
S (Status) |
The status of the customer action issue. Valid values:
Optional. |
Entry date |
The date the customer action issue was entered. Numeric, 6 positions; optional. |
Customer # |
A number which identifies the customer. Numeric, 9 positions; display-only. |
Ent user (Entered user) |
The user who initially entered the customer action issue Alphanumeric, 10 positions; display-only. |
Worked on user |
The user who has most recently worked on the customer action issue. This field automatically updates when a user selects Work in process to update the status of an issue and enter details of its investigation; if the status of an issue has not been updated, this field displays the ID of the user initially assigned to investigate the issue. Alphanumeric, 10 positions; display-only. |
Worked on date |
The most recent date that the issue was investigated and “work in process” details were entered. This field automatically updates when a user selects Work in process to update the status of the issue and enter details of its investigation. If no action has been taken on the issue, its status remains O (open) and this field is blank. Numeric, 6 positions; display-only. |
Dtl (Details) |
The code indicating whether detail notes have been entered for this issue. D indicates detail notes have been entered; otherwise, the field remains blank. Alphanumeric; 1 position; display-only. |
Description (Unlabeled field) |
A brief description of the customer action issue. Alphanumeric, 40 positions; display-only. |
Screen Option | Procedure |
---|---|
Change a customer action note |
Select Change for a customer action note to advance to the Change Customer Action Screen. |
Delete a customer action note |
Select Delete for a customer action note to delete it. See Resolving or Deleting an Action Issue. |
Display a customer action note |
Select Display for a customer action note to advance to the Display Customer Action screen. You cannot change any information on this screen. See the Change Customer Action Screen for more information. |
Enter detailed notes for a customer action issue |
Select Detail notes for a customer action note to advance to the Customer Action Note Details Screen, where you can enter details of the action issue. This option will not update the status of the issue. |
Update the status of a customer action issue to indicate that the issue has been investigated but not yet resolved |
Select Work in process for a customer action note to advance to the Customer Action Note Details Screen, where you can detail any actions that have been taken on the customer issue. This option automatically updates the Status and Worked on user fields of the issue. |
Resolve the issue |
Select Resolve for a customer action note to resolve the issue and clear it from this screen. |
Advance to the Scan Orders by Customer screen |
Select Order Inq for a customer action note to advance to the Scan Orders by Customer screen. See Using the Order Inquiry Scan Screens (OIOM). |
Advance to the standard Order Inquiry screen |
Select Order Inquiry to advance to the Order Inquiry Scan Screen. |
Change Customer Action Screen
Purpose: Use this screen to change the description of the action issue, the reason code, and the user assigned to follow up on the issue.
Note:
You can also change a customer action note at the Edit Customer Actions Window by entering over the previous entries.How to display this screen: Select Change for a customer action issue at the Work with Customer Action Notes Screen.
Note:
If you do not have authority to the Change Customer Action Notes Description (A93) secured feature, you cannot change the description of an action note on the Edit Customer Actions Window, and when you try to advance to the Change Customer Action Screen from the Work with Customer Action Notes Screen, the system displays a message:Not authorized to change
Field | Description |
---|---|
Customer (Sold-to customer number) |
A number assigned by the system to identify the customer. Numeric, 9 positions; display-only, assigned by the system. |
Customer name (Unlabeled field to the right of the customer field) |
The customer's last name, first name and middle initial. Last name: alphanumeric, 25 positions; display-only. First name: alphanumeric, 15 positions; display-only. Initial: alphanumeric, 1 position; display-only. |
Action |
A brief sentence describing the customer action issue. Alphanumeric, 40 positions. |
Status |
The current status of the customer action issue. Valid values are:
Display-only, updated by the system. |
For user |
The user ID of the person who should follow up on or resolve the action issue. Alphanumeric, 10 positions. |
Reason |
The reason code and description behind the customer action note. Reason code: alphanumeric, 2 positions. Reason description: alphanumeric, 30 positions; display-only. |
Entered |
The date the customer action issue was entered. This field defaults to the current date when you create the customer action note. Numeric, 6 positions (in user date format); display-only. |
Entered user name (Unlabeled field next to the Entered field) |
The user ID and name of the person who entered the action issue. User ID: alphanumeric, 10 positions; display-only. User name: alphanumeric, 30 positions; display-only. |
Resolved (Date resolved) |
The date the customer action issue was resolved. This field defaults to the current date when you use option 23 to resolve the issue. Numeric, 6 positions (in user date format); display-only. |
Resolved user name (Unlabeled field next to the Resolved field) |
The user ID and name of the person who resolved the action issue. User ID: alphanumeric, 10 positions; display-only. User name: alphanumeric, 30 positions; display-only. |
How to use this screen: To change the action description, the user, or the reason code, enter over the information already entered in these fields to return to the Work with Customer Action Notes Screen.
Resolving or Deleting an Action Issue
Purpose: There are two ways to close a customer action issue at the Edit Customer Actions Window: deleting it or resolving it.
Note:
Similarly, you can also resolve or delete a customer action issue at the Work with Customer Action Notes Screen.To delete: Select Delete for the issue you want to delete.
Note:
The action issue is deleted immediately from the screen; there is no Confirm Delete pop-up window.The deleted issue no longer displays automatically for the customer.
To resolve: Select Resolve for the issue you want to identify as “resolved.”
The resolved issue will no longer display on the Work with Customer Action Notes Screen; however, a resolved issue will continue to appear on the Edit Customer Actions Window in a status of resolved until it is deleted. This may be useful if, for example, the action has been resolved but you still need to notify the customer.
Optionally, you can select Detail notes for a resolved issue to advance to the Customer Action Note Details Screen, where you can enter notes about how you resolved the issue.
Note:
If you do not have authority to the Delete Customer Action Notes (A96) secured feature, a message indicates when you try to delete a customer action issue: Not authorized to delete. If you do not have authority to the Change Customer Action Notes Status/Resolve (A98) secured feature, a message indicates when you try to resolve a customer action issue: Not authorized to this option.Customer Action Note Details Screen
Purpose: Use this screen to add additional information about a customer action issue. The comments you enter on this screen are attached to the short description of the customer issue that appears on the Edit Customer Actions Window. You can also use this screen to enter information about what steps you have taken toward resolving the issue, and to update the status from O (open) to W (work in process).
How to display this screen: Select Detail notes for an action issue at the Edit Customer Actions Window and the Work with Customer Action Notes Screen. You can also display this screen by selecting Work in process for an action issue; in this situation, the status of the issue changes from O (open) to W (work in process).
User override: If you are not the assigned user, the Confirm User Override pop-up window opens. Select Accept at this window to advance to the Customer Action Note Details Screen. The status of the customer action issue will automatically change from O (open) to W (work in process), indicating that the issue has been investigated, and the user ID will automatically update to the current user.
Field | Description |
---|---|
Customer# (Sold-to customer number) |
A number assigned by the system to identify the customer. Numeric, 9 positions; display-only, assigned by the system. |
Status |
The current status of the customer action issue. Valid values are:
Display-only. |
Entry date |
The date the customer action issue was entered. This field defaults to the current date when the issue is entered. Numeric, 6 positions (in user date format); display-only. |
User |
The user ID of the person who entered the action issue. This is not necessarily the same as the user assigned to follow up on the issue, or the most recent user to work on the issue. Alphanumeric, 10 positions. |
Description |
A short description of the customer action issue, which was entered on the Edit Customer Actions screen. Alphanumeric, 40 positions |
Note |
Entry fields for you to enter as much information as necessary to fully describe the customer action issue. If you need extra space, use Scroll or Page Down to display more entry fields. The notes you enter on this screen are attached to the short description of the customer action issue. Alphanumeric, 60 positions per line. |
About this screen: Enter as much information as necessary to fully describe the customer action issue. If you need additional space, press Scroll or Page Down to display extra entry fields. Select OK when you are through entering notes.
If you do not have authority to the Add Customer Action Detail Notes (A94) secured feature, you cannot add extra lines of detail notes to this screen. If you do not have authority to the Change Customer Action Detail Notes (A95) secured feature, you cannot change the notes already entered; the notes are display-only.
Process Address Changes Screen (PACS)
Purpose: Use this screen to process address changes when the ACS Tape or the MBS Tape tables are already loaded with address change information.
For more information: See Process Address Changes Screen (PACS) for background.
How to display this screen: Enter PACS in the Fast path field at the top of any menu, or select Process Address Changes from a menu.
Field | Description |
---|---|
Process deliverable addresses only |
Indicates whether to process only those names and addresses identified as deliverable. Valid values are:
When processing the records for non-deliverable addresses, the system updates the values in the Mail and Rent fields to unselected. This ensures that you do not send any more catalogs to this address or sell the customer's name to another company. |
Change date |
The date when the address changes become effective. The system compares this date against the change date in the Customer Sold To table. If the change date you specify here is:
Numeric, 6 positions (in user date format); required. |
Input file type |
Indicates where the address changes are located. Valid values are:
Alphanumeric, 3 positions; required. |
Completing this screen: Complete each field as indicated above and select Submit to submit address updates. See Process Overview for more information.
MBS and ACS Table Formats
Purpose: This table describes the format of the MBS and ACS Tape tables. The Process Address Changes Screen (PACS) and MBS and ACS Table Formats require tables in one of the formats described below.
MBS Tape table (CSMBST) | ACS Tape table (CSACST) | ||||
---|---|---|---|---|---|
Field | Position (From-To) | Length | Position (From-To) | Length | Valid values |
Customer # |
17-25 |
9 |
|||
First name |
1-20 |
20 |
64-78 |
15 |
If the ACS move type (position 39) is set to B (business), then positions 44-87 are not parsed into name components, but are treated as a single 41-character business name field. |
Last name |
21-40 |
20 |
44-63 |
20 |
|
Prefix code |
41 |
1 |
79-81 |
3 |
The MBS format uses a single-position code, whereas the ACS format uses the literal value.
|
Suffix code |
42 |
1 |
85-87 |
3 |
The MBS format uses a single-position code, whereas the ACS format uses the literal value.
|
Address 1 |
43-72 |
30 |
118-177 |
60 |
The components of the ACS old address field are parsed as follows: Field/Position/Size Primary No./118-127/10 Pre-directional/128-129/2
|
Address 2 |
73-102 |
30 |
|||
City |
103-122 |
20 |
178-205 |
28 |
The first 20 positions of the ACS city maps to the MBS city code. |
Filler |
123-127 |
5 |
|||
State |
128-129 |
2 |
206-207 |
2 |
|
Zip |
130-134 |
5 |
208-212 |
5 |
|
Zip+4 |
135-138 |
4 |
ACS does not provide old ZIP+4. |
||
Filler |
139-150 |
12 |
|||
Dwelling code |
151 |
1 |
40 |
1 |
Valid MBS codes:
|
Filler |
152-158 |
7 |
|||
Priority |
159-161 |
3 |
No matching ACS field. |
||
Key |
162-169 |
8 |
No matching ACS field. |
||
Multi-buyer Code |
170 |
1 |
No matching ACS field. |
||
Filler |
171-185 |
15 |
|||
Zip Level |
186-188 |
3 |
No matching ACS field. |
||
Carrier Route |
191-194 |
4 |
No matching ACS field. |
||
NCOA Indicator |
195 |
1 |
37 |
1 |
If F or I, new address at position 491 |
Filler |
196-198 |
3 |
|||
Zap Indicator |
199 |
1 |
1 |
1 |
Valid MBS codes:
If Z, new zip at position 130 If ACS position 38 is set to one of the following values, then this is a “Nixie” record (undeliverable) and the MBS Zap indicator are loaded with a value of X: |
|
|||||
|
|||||
The MBS table will not contain COA records reflecting changes only to the ZIP code. A postal customer would not submit a COA form if the zip code changed but he/she did not move, so there would be no COA request to trigger a record in this table. Note: The first record on the ACS Tape table has an H in this field, indicating that this is a header record and should not be used. |
|||||
Tier Code |
200 |
1 |
No matching ACS field. |
||
Filler |
201-233 |
33 |
|||
Old Zip Code |
234-238 |
5 |
208-212 |
5 |
|
NCOA Move Date |
239-242 |
4 |
33-36 |
4 |
|
Filler |
243-275 |
33 |
|||
DT Dwelling Code |
276 |
1 |
No matching ACS field. |
||
Old DMT Dwelling Code |
277 |
1 |
No matching ACS field. |
||
Old Finalist Dwelling Code |
278 |
1 |
No matching ACS field. |
||
Filler |
279-364 |
86 |
|||
Address Reverse Indicator |
365 |
1 |
No matching ACS field. |
||
Filler |
366-381 |
16 |
|||
String |
382-383 |
2 |
No matching ACS field. |
||
Standard Addr1 |
384-413 |
30 |
No matching ACS field. |
||
Standard Addr2 |
414-443 |
30 |
No matching ACS field. |
||
Standard City |
444-456 |
13 |
No matching ACS field. |
||
Standard State |
457-458 |
2 |
No matching ACS field. |
||
Filler |
459-478 |
20 |
|||
Delivery Point Barcode |
479-481 |
3 |
342-344 |
3 |
|
Filler |
482-490 |
9 |
|||
New Addr1 |
491-520 |
30 |
244-303 |
60 |
The components of the ACS new address field are parsed as follows: Field/Position/Size Primary No./244-253/10 Pre-directional/254-255/2 Street name/256-283/28 Street suffix/284-287/4 Post-directional/288-289/2 Unit designator/290-293/4 Secondary no./294-303/10 |
New Addr2 |
521-550 |
30 |
|||
New City |
551-565 |
15 |
304-328 |
25 |
|
New State |
566-567 |
2 |
332-333 |
2 |
|
New 9-digit Zip |
568-576 |
9 |
334-343 |
10 |
|
New Carrier Route |
577-580 |
4 |
No matching ACS field. |
||
Move Type |
581 |
1 |
39 |
1 |
|
Undeliverable Type |
582 |
1 |
38 |
1 |
If ' ', zip code or address change |
If ACS position 38 is set to one of the following values, then this is a “Nixie” record (undeliverable), and the MBS Zap indicator will be loaded with a value of X:
|
|||||
|
|||||
Filler |
583-592 |
||||
Customer code |
593-601 |
9 |
17-25 |
9 |
|
602-772 |
Not used by Order Management System. |
Work with Changed Customers Screen (MBSI)
Purpose: Use this screen to review the customer's name and address before and after the address updates. You can also use this screen to delete a change, purge all name and address changes or print a list of changes.
The system creates these updates after you use the MBS and ACS Table Formats or the Work with Changed Customers Screen (MBSI).
You can review name and address updates that did not take effect through the Work with Unchanged Customers Screen (MBSF). Customers may be unchanged because the updates were not processed, the customer was not found, the customer has open orders, or the change date for the customer was later than the change date on the received file.
For more information: See Work with Changed Customers Screen (MBSI) for background.
How to display this screen: Enter MBSI in the Fast path field at the top of any menu or select the Work with MBS Before and After Images option from the menu.
Field | Description |
---|---|
Customer # |
A number to identify a customer. The customer record must exist on the system for any address updates to be performed. Numeric, 9 positions; display-only, assigned by the system. |
Customer name |
The customer's name. Alphanumeric, 25 positions; display-only. |
City |
The city where the customer lived before the address update (if the address update resulted from a move). Alphanumeric, 25 positions; display-only. |
State |
The code for the state or province where the customer lived before the address update (if the address update resulted from a move). Alphanumeric, 2 positions; display-only. |
Screen Option | Procedure |
---|---|
Remove a record from the screen |
Select Delete for a record to delete it. Note: This does not undo the address update; it simply purges the record from the MBS Changed Customers table. |
Review the address before and after the update |
Select Display for a record to advance to the Display Changed Customers Screen (Reviewing the Address Before and After the Update). |
Purge all address updates from the MBS Changed Customers table |
Select Purge. Note: To maintain job performance, you should backup and purge this table prior to loading any new address updates. |
Print a report listing the customer addresses before and after the update |
Select Print to print the Changed Customers Report. |
Display Changed Customers Screen (Reviewing the Address Before and After the Update)
Purpose: Use this screen to review the changes to a customer's name and address before and after the update.
How to display this screen: Select Display for a customer number at the Work with Changed Customers Screen (MBSI).
The BEFORE information represents the customer's name and address prior to the update. The AFTER information represents the customer's current name and address, resulting from the update.
Field | Description |
---|---|
Customer # |
A number to identify a customer. The customer record must exist on the system for any address updates to be performed. Numeric, 9 positions; display-only, assigned by the system. |
PO box? |
Indicates whether the address is a post office box. Valid values are:
|
Delivery code |
Indicates whether the address is a business or residence. This information is used by shippers who charge different rates for shipping a package to a business or home. Display-only, updated by the system. |
Address |
The customer's old and new addresses. |
Work with Unchanged Customers Screen (MBSF)
Purpose: Use this option to:
-
review the unprocessed records in the MBS Work table
-
remove a record from the table
-
review the type of name and address change
-
purge all records in the table
-
process the records in the table
For more information: See Loading Address Updates for background.
Selecting this option: Enter MBSF in theFast path field at the top of any menu or select the Work with MBS Address Change File option from the menu.
Field | Description |
---|---|
Customer # |
A number to identify a customer. The customer record must exist on the system for any address updates to be performed. Numeric, 9 positions; display-only, assigned by the system. |
Change status |
The status of the record, which may indicate reason that the customer name and address was not updated. Valid values are:
|
Change type |
Identifies the reason for the name and address change.
Display-only, updated by the system. |
Deliverable address |
Indicates whether the address is a valid, deliverable address. Valid values are:
If NO, the system changes the values in the Mail and Rent fields in the Sold To Customer table to unselected so that you do not send any more catalogs to the customer or sell the customer's address to other companies. Display-only, updated by the system. |
Screen Options | Procedures |
---|---|
Update the status of a record to Not Processed |
Select Reset for a record to update its status to Not Processed. |
Remove a record from the work table |
Select Delete for a record to delete it. |
Review the change |
Select Display for a record to display the Work with Customer Changes Screen (Reviewing Unapplied Address Changes). |
Purge all records in the work table after you process or review them |
Select Purge. |
Process the updates |
Select Process. |
Print a report of the unchanged customers that identifies the customer number, change condition, change type, whether it is a deliverable address, the address, the delivery code, and whether the address is a P.O. box |
Select Print to print the Unchanged Customers Report |
Work with Customer Changes Screen (Reviewing Unapplied Address Changes)
Purpose: Use this screen to review an unapplied address change.How to display this screen: Select Display for a customer number at the Work with Unchanged Customers Screen (MBSF).
Field | Description |
---|---|
Customer # |
A number to identify a customer. The customer record must exist on the system for any address updates to be performed. Numeric, 9 positions; display-only, assigned by the system. |
Change status |
The status of the record, which may indicate the reason that the customer address was not updated. Valid values are:
Alphanumeric, 25 positions; display-only, updated by the system. |
Change type |
Identifies the reason for the change. Valid values are:
Alphanumeric, 15 positions; display-only, updated by the system. |
Deliverable |
Indicates whether the address is a valid, deliverable address. Valid values are:
If NO, the system changes the values in the Mail and Rent fields in the Sold To Customer table to unselected so that you do not send any more catalogs to the customer or sell the customer's address to other companies. Alphanumeric, 3 positions; display-only, updated by the system. |
PO box? |
Indicates whether the address is a post office box. Valid values are:
|
Delivery code |
Indicates whether the address is a business or residence. This information is used by shippers who charge different rates for shipping a package to a business or home. Display-only, updated by the system. |
Address |
The customer's address BEFORE the address update. |
Process Changes Screen
Purpose: Use this screen to process name and address updates.How to display this screen: Select Process at the Work with Unchanged Customers Screen (MBSF).
Field | Description |
---|---|
Change Date |
The date when the changes become effective. The system compares this date against the change date in the Customer Sold To table. If the change date for the received record is later than the change date in the Sold To Customer table, the system applies the address change. If the change date for the received record is earlier than the change date in the Customer Sold To table, the system does not apply the address change; instead, the system creates a record in the MBS Address Change table for you to review. Numeric, 6 positions (in user date format); required. |
Source of Update |
Indicates the table from which the system uploads changes. Valid values are:
Alphanumeric, 4 positions; required. |