High Volume and High Performance

This chapter covers the following topics:

Quick Sales Orders

Overview

Quick Sales Orders reduces data entry and shortens the time required to perform this task through the use of a streamlined entry window. You can search for customer data by using the Easy Search feature, enabling you to search on various fields, then bring that customer's information into the order. Headers and lines are displayed in the same window. In the Line Details region you can add related items or upsell the existing item on the line as well as verify price and availability.

Use Quick Sales Orders to configure your user interface to meet business flow needs, and make input intuitive for users with minimal training. You can create keyboard hot keys or configure window buttons to reduce keystrokes using the folder function. Data entry is shortened by the reduced need for navigation to other windows. Processes can be deferred during order processing, including pricing and automatic data refresh processes.

The interface has been designed to facilitate orders to be entered with minimal data entry and time lag, and provides the following features and functions:

Setup

There are no setup steps required to enable Quick Sales Order functionality. There are folder extensions to assist in the configuration of the user interface. All existing sales orders can be queried and modified using this feature as is in the existing sales order window. All pre-existing sales orders are queryable and modifiable from this window as currently supported in the existing sales order window. The quick sales order window does not currently support mass selection. Use the sales order window to perform these functions. The scheduling organizer and item search are not supported.

Profile options

OM: Default Defer Pricing at Order Entry Values at Site Level

This profile controls the default setting of Defer Pricing; options are Yes or No. This value is read from the profile when a new session begins; however, a user is able to activate Defer Pricing directly.

OM: User Interface Defer Pricing

This profile determines if pricing is deferred during line entry. Options are Defer pricing to save, and No. For Defer pricing to save, pricing is done when the lines are saved. Line level pricing is suppressed. If No is selected, pricing is not deferred.

OM: Quick OE Auto Refresh. Site, Application, LOV

This profile controls the automatic refreshing of a window when changes have been made. It allows instant updating of the display. The options are Line, Line Detail, or Both.

OM: Use Configurator

If the Advanced Configurator product is installed and the OM: Use Configurator profile is set to Yes, selecting the Configurator Button will take you to the Configurator window. If it is set to No then the options section in line details displays. Selecting the configurator button moves you to the options section for model items.

OM: Enable Related Items and Manual Substitution

This profile enables the selection of related items in the line details region if you are using related items.

Supported Features

Defer Pricing

This feature enables you to defer pricing at line level. Unit List Price, Unit Selling Price are not displayed to the user while entering the line and navigating out of the line. Order and lines are priced when the lines are saved. This feature can be controlled through the Defer Pricing check box that is displayed in the Lines window.

Quick Order Entry Window Line Details Options

The Options region in Line Details has the following fields: Option Number, Item, Item Description, UOM, and Qty. Options and Classes are created and displayed in this window. Option Number is system generated and may not be the actual option number that the system assigns when the configuration is saved. It is a sequence number assigned for display purposes. The quantity defaults to what is entered on the mode line.

Auto Refresh

If the Toggle Query Coordination check box is selected then the newly created option lines are displayed immediately in the lines block when the cursor is moved to the line. If it is not selected the options are saved. The lines region does not display available options immediately upon navigation to the lines; you have to manually requery to see them.

Creating & Managing Folders in Oracle Applications

Please refer to the Oracle E-Business Suite User's Guide on how to customize the layout of data in various forms by creating and managing folders in Oracle Applications.

Extended Folder Functionality in Quick Sales Orders

Quick Sales Orders is folder enabled, but the folder functionality in Quick Sales Orders allows display of additional tabs both at the header and line; you can select which line detail regions need to be displayed. The folder can be configured to select which specific actions should be available as buttons.

Folders can be extended separately for the header and the line regions of Quick Sales Orders.

Folder extensions at the header level can:

Folder extensions at the line level can:

Folder Extensions- Header Level:

  1. Order Tabs

    Using this feature, the Others tab can be displayed by selecting the Others check box and saving the folder. This folder can be saved to open as default folder and in which case this folder is opened automatically whenever the form is invoked.

  2. Configure Buttons

You can select which specific actions should be displayed as action buttons. All the critical actions that are currently available from the headers and lines are seeded and can be selected to be displayed as buttons. Up to eight buttons can be displayed. Optionally, you can specify a custom prompt and an access key. If the access key is already used by some other button, then the access key that is specified here is ignored. The configure buttons functionality is enabled only when a folder for the Header is created.

Note: When the user configures a folder for the header region, the Line Tabs, Line Details section and Default region List of Values are disabled.

Setting Header Level Folder Functionality for Quick Sales Orders

the picture is described in the document text

The figure above shows a header level folder configuration with the Others Tab displayed at the header. The Action buttons have been configured to display Configurator, Pricing/Availability, Price Adjustments, and Price Order as buttons. Actions is not selected for display as a button.

Price Adjustments has the user prompt "Discounts." That reads as "Discounts" when the folder is invoked.

Price Order and Price Adjustments are selected to be displayed as buttons with the access keys as "P" and "D" respectively.

Folder Extensions- Line Level:

  1. Line Tabs

Using the folder extension at the line level, the following additional tabs can be selected for display:

Any of the above listed tabs can be displayed by selecting the corresponding check boxes and saving the folder. This folder can be saved to open as default folder and in which case this folder is opened automatically whenever the form is invoked.

  1. Line Details (Regions):

Folders can be used to control the display of the following line details (regions):

You can select the default line details region that displays when you switch to Expand Line Details mode.

Setting Line Level Folder Functionality for Quick Sales Orders

the picture is described in the document text

The figure above shows the line level folder configured to display only the Pricing and Addresses line tabs. The other line tabs like Shipping, Returns, Services and Others will not be displayed when this folder is invoked as these have not been checked.

This folder allows you to view all the line details (regions) from the Options, Services, Adjustments, Related Items and Pricing/Availability tabs as all these have been checked.

At the bottom of the window is the Default Region field. The various Line Details (Regions) as mentioned above, are available for selection in the list of values. In this case, Options is selected as the default region.

Note: The Order Tabs section and Configure buttons regions are disabled when you configure a folder for the line region. The folder will not save if you select a value in the Default Region List of Values that is not also selected in the Line Details region. The configuration window that launches when selecting the Configurator button is dependent on whether you are using Oracle Order Management Configurator or Oracle Configurator. If Order Management Configurator is used, select the Options check box or the application will error out. The check box is disabled if you are using Oracle Configurator.

High Volume Order Processing

Overview

High Volume Order Import improves the performance of order import for high volume users who require basic processing. If you have enabled Multi-Org Access Control, you can use High Volume Order Import to import orders for all Operating Units that are accessible to you in a single submission.

Please refer to the following guides for more information on High Volume Order Processing:

Oracle Order Management User's Guide.

Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide.

High Volume Order Processing (HVOP) takes advantage of the high-volume processing features introduced with Oracle8. HVOP uses memory caching extensively and it bulk enables several processing operations. For lines imported in booked status, it also improves the performance of interfacing lines to shipping. If full quantity is shipped, it improves the performance of interfacing lines from shipping to Order Management.

High Volume Order Processing (HVOP) Pricing Integration also leverages the JAVA Pricing Engine, which is required for optimal performance. See the Oracle Pricing Implementation Guide for more information.

Note: The Java Pricing Engine is only available to those in the Approved Strategic Implementation Program.

Certain features have not been bulk enabled for High Volume Order Import, and are not optimized for HVOP. These features are:

Supported Operations

Creating Orders with HVOP Order Import

You can perform high-volume order processing on orders that are created via Order Import (this includes EDI orders). High-volume order processing supports creation of supported order entities, including creation of the entire order, i.e., Order Header, Order Lines, Order/Line Price Adjustments. Lines imported in Booked status are bulk enabled for Shipping Interface, which means the lines flow through to shipping in less time.

Pricing Integration with HVOP Order Import

The performance of pricing integration is optimized for orders brought into Order Management with HVOP Order Import. Performance of pricing integration is optimized for many pricing features used by high volume users.

See: Oracle Pricing Setup, Oracle Advanced Pricing Implementation Manual

Shipping Interface

With HVOP Order Import

The interface of lines to shipping is now optimized with HVOP Order Import. Using a typical line flow, lines are entered and scheduled and then interfaced to shipping. Without HVOP Shipping Interface, individual line workflows go one by one to interface with shipping. But if you import scheduled lines in Booked status using HVOP Order Import, the bulk processing pushes the lines all the way through to interface with shipping. Once the lines are interfaced with shipping, it is possible to pick ship, etc.

Without HVOP

There are also performance optimizations for lines that interface back to Order Management after shipping. For instance, after shipping the order line is updated with shipping information. If the full quantity of the line ships, performance of the Shipping to Order Management interface is optimized. The optimization can occur either when you ship confirm manually, or when you run the Trip Stop Interface concurrent program.

Supported Features

The following is a list of features that are supported by high-volume order processing.

Unsupported Features

The following is a list of features that are not supported by high-volume order processing.

If you need to use unsupported features, use standard Order import for those lines.

Types of Items

You can process the following types of items on high-volume orders.

Booking

Orders created using high-volume order processing with the Book Order request are validated for booking and created as booked. Pricing is based on booking events. Modifiers tied to the booking phase are evaluated for these orders.

Credit checking is supported, but not optimized. You can use either real-time credit checking or credit-checking with the precalculated exposure functionality. Use pre-calculated exposure functionality for improved performance. Also note that real-time credit checking with HVOP may not be accurate with multiple threads, because the commit boundary in HVOP depends on the batch size. It is possible for several orders to be processed before a batch is committed, in which case the exposure calculations may not include order lines being processed by other threads at the time of the calculation.

Auto-Scheduling

Auto-scheduling is optimized for high-volume order processing. Regular scheduling via Workflow can be performed, but it is not optimized for high-volume order processing.

Auto-scheduling does not currently support the reservation time fence. A warning message will be populated when the schedule date falls within the reservation time fence. In addition, the lines are scheduled but are not reserved.

Note: High-volume import supports auto-scheduling for both supported item types: standard, non-ATO items and kit with its included items. Please note that regular import supports auto-scheduling only for standard, non-ATO items.

Credit Checking

Credit checking can be set up to calculate real-time credit exposures or pre-calculated exposures. For optimal performance, use the pre-calculated exposure functionality. Also consider limiting the use of credit checking to higher risk customers.

Sales Credit

The software automatically creates a 100% sales credit for the sales person on the order. For the order line, if sales person matches the order header, then there is no sales credit created at the line level. If sales person is different, then it will generate 100% sales credit for the sales person on the line and 100% sales credit for sales person on order header (this is how regular order entry is done). For high-volume order processing, the data in the sales credit interface tables is not processed.

Holds Processing

You can evaluate hold sources and automatically put the applicable orders/order lines on hold.

Price Adjustments

High-volume order import supports only manual price adjustments of the type: Discount, Freight Charge, and Surcharge. There is no such restriction on automatic adjustments. All types of automatic adjustments can be defined and applied if order is priced during high-volume import. During manual adjustments, it is necessary to modify the Corrections form and enter the values in the Operand (for ordered quantity) and Operand per PQTY (for pricing quantity) fields. This ensures that the overridden values are applied.

Tax Calculation

There is no tax calculation during high volume order import. Order lines imported in this mode will not display tax values. Therefore, you can only use line transaction types with a receivable transaction type that does not require tax calculation or order transaction types in which tax calculation is performed at the point of invoicing.

Pricing

Both Basic and Advanced Pricing are optimized. Features commonly used by high volume customers are optimized:

Features not supported include pricing attributes, ask-for promotions, and coupons.

See: Oracle Advanced Pricing Implementation Manual

Defaulting

Orders created using high-volume order processing will undergo defaulting for attributes that the customer cannot know and hence cannot send. These attributes are defaulted using a fixed hierarchy of two or three sources. These requirements are based on EDI needs.

Certain key attributes that are required for successfully processing the order are not defaulted regardless of how the Defaulting Enabled? parameter is set. This is detailed in the following tables.

Bill-to and payment terms are defaulted from the header, but not at the line level. This is done to simplify credit checking and this means that orders that have lines that have a bill-to or payment term that is different from the header will be errored out.

Tables 1 and 2 lists the individual attributes that are defaulted and the fixed source and hierarchy used for each attribute.

Defaulting Sources for Order Header

Defaulting Sources for Order Line

Any other sources for Order Line are not supported.

You can turn off defaulting in case the customer is providing all the required attributes. This is implemented using the Defaulting Enabled? parameter.

Note: High-volume order processing uses a different defaulting mechanism than the standard Order Management Defaulting Framework to default attributes. It defaults from a limited number of source attributes using a fixed hierarchy. However, once the order has been created, any updates to attributes that result in the clearing and re-defaulting of dependent attributes will use the rules set up in the standard Order Management Defaulting Framework. Even though the fixed defaulting hierarchies that the bulk process uses reflect in most cases the seeded rules in the standard Defaulting Framework, you might occasionally see different values being defaulted in case of an update.

Defaulting Details

High-volume order processing does some limited defaulting if the Defaulting Enabled? parameter is set to Yes. The following tables list the attributes that will be defaulted and the sources they will be defaulted from.

Note: Attributes that are set to No for the Defaulting Enabled in High-Volume Order Processing? column in the following tables will not be defaulted regardless of how the Defaulting Enabled? parameter is set. For example, Ship To, Invoice To, Ship To Contact, Invoice To Contact etc. will not be defaulted on the order header. Therefore, users should supply these values on the interface table if needed.

The fields marked Yes in the Required? column in the following tables are mandatory fields. Depending on the Defaulting Enabled? parameter value, you may need to supply values for some or all of these fields in the interface tables. For example, on the order header, you should always populate Ship To and Invoice To in interface tables as they are never defaulted in high-volume order processing. However, Tax Exempt values should be supplied only if the Defaulting Enabled? parameter is set to No. If Defaulting Enabled? is set to Yes, then a constant value of Standard is supplied by the program.

In addition, other non-mandatory fields that are defaulted in regular order import should be supplied in the interface tables for bulk import if orders are to be created with values in these fields.

Supported for HVOP Pricing Integration

Other pricing features are supported, but if used, pricing does not use the optimized code path:

Unsupported with HVOP Pricing Integration

Attribute sourcing is somewhat restricted, because orders are placed before posting to the database.

Implementation Considerations of HVOP

Some features are supported by HVOP Order Import but not optimized. Credit Checking is an example. If you can limit credit checking to higher-risk customers, you can improve performance.

It is useful to analyze which lines can be imported with HVOP Order Import. For instance, if only 15% of your lines require tax calculation at booking, you could consider importing those lines with standard order import, and the remaining lines with HVOP order import.

You can autoschedule the lines by populating the schedule dates in the HVOP interface tables. This method of scheduling typically offers better performance than scheduling each line using workflow.

Also consider whether you can import lines in booked status. It is possible to improve the performance of lines through shipping interface if you can.

To optimize the performance of HVOP pricing integration, use the supported features and the Java pricing engine.

If a line is imported with one of the above unsupported pricing features, the lines are imported, but pricing-related performance is not recognized. You should evaluate whether you can run batches of HVOP Order Import with lines that use supported features. In this way, you will achieve higher performance.

Defaultable Attribute Defaulting Enabled in High-Volume Order Processing Defaulting Source in High-Volume Order Processing Required?
Accounting Rule Yes 1. Agreement
2. Order Type		 No
Agreement No n/a No
Contact No n/a No
Conversion Rate Date No n/a No
Conversion Type Yes Order Type No
Credit Card Expiration Date No n/a No
Credit Card Holder Name No n/a No
Credit Card Number No n/a No
Currency No n/a Yes, on entered orders
Customer No n/a Yes, on booked orders
Customer PO No n/a No
Deliver To Contact No n/a No
Deliver To Org No n/a No
Demand Class Yes 1. Ship To
2. Order Type		 No
Earliest Schedule Limit No n/a No
FOB Point Yes 1. Ship To
2. Order Type		 No
Freight Terms Yes 1. Ship To
2. Order Type		 No
Invoice To No n/a Yes, on booked orders
Invoice To Contact No n/a No
Invoicing Rule Yes 1. Agreement
2. Order Type		 No
Latest Schedule Limit Yes Ship To No
Order Date Type Code Yes Ship To No
Order Type Yes 1. Invoice To
2. Ship To		 Yes, on entered orders
Ordered Date Yes Sysdate Yes, on booked orders
Packing Instructions No n/a No
Payment Term Yes 1. Agreement
2. Invoice To		 Yes, on booked orders
Price List Yes 1 Agreement
2. Invoice To		 Yes, on booked orders
Pricing Date Yes Sysdate  
Request Date Yes Sysdate  
Sales Channel No n/a No
Salesperson No n/a Yes, on booked orders
Ship To No n/a Yes, on booked orders
Ship To Contact No n/a No
Ship Tolerance Above Yes Ship To No
Ship Tolerance Below Yes Ship To No
Shipment Priority Yes Order Type No
Shipping Instructions No n/a No
Shipping Method Yes 1. Ship To
2. Order Type		 No
Tax Exempt Yes Constant: Standard Yes, on booked orders
Tax Exempt Number No n/a No
Tax Exempt Reason No n/a No
Warehouse Yes 1. Ship To
2. Order Type		 No

The next table shows the Line Attributes that will be defaulted and the sources they will be defaulted from.

Defaultable Attribute Defaulting Enabled in High-Volume Order Processing Defaulting Sources in High-Volume Order Processing Required?
Accounting Rule Yes 1. Item
2. Order Header		 No
Agreement No n/a No
Calculate Price Yes 1. Constant = Yes No
Commitment No n/a No
Customer PO No n/a No
Customer PO Line Number No n/a No
Deliver To Contact No n/a No
Deliver To Org No n/a No
Demand Class Yes 1. Ship To
2. Order Header		 No
Dep Plan Required No n/a No
Earliest Acceptable Date No n/a No
FOB Point Yes 1. Ship To
2. Order Header		 No
Freight Terms Yes 1. Ship To
2. Order Header		 No
Grade No n/a No
Invoice To Yes Order Header Yes, on booked lines
Invoice To Contact No n/a No
Invoicing Rule Yes 1. Item
2. Order Header		 No
Item Identifier Type Yes Ship To No
Item Revision No n/a No
Latest Acceptable Date No n/a No
Line Type Yes Order Type.Outbound Line Type (only Regular lines supported in Bulk!) Yes, on entered lines
Order Quantity UOM Yes Item.Primary UOM Yes, on booked lines
Ordered Quantity No n/a Yes, on booked lines
Packing Instructions No n/a No
Payment Term Yes Order Header Yes, on booked lines
Price List Yes Order Header Yes, on booked lines
Pricing Date Yes Sysdate No
Promise Date No n/a No
Request Date Yes Sysdate No
Return Reason No n/a No
Salesperson Yes Order Header No
Schedule Arrival Date No n/a No
Schedule Ship Date No n/a No
Secondary Quantity No n/a No
Secondary UOM No n/a No
Service Period No n/a No
Service Reference Type Code No n/a No
Service Start Date No n/a No
Ship To Yes Order Header Yes, on booked lines
Ship To Contact No n/a No
Ship Tolerance Above Yes 1. Item
2. Ship To
3. Order Header		 No
Ship Tolerance Below Yes 1. Item
2. Ship To
3. Order Header		 No
Shipment Priority Yes Order Header No
Shipping Instructions No n/a No
Shipping Method Yes 1. Ship To
2. Order Header		 No
Source Type Yes Constant = INTERNAL No
Subinventory No n/a No
Tax Code No n/a No
Tax Date No n/a No
Tax Exempt Yes Order Header Yes, on booked lines
Tax Exempt Number No n/a No
Tax Exempt Reason No n/a No
Warehouse Yes 1. Item
2. Ship To
3. Order Header		 No

Value to ID

If value fields are supplied on interface tables, high-volume import converts them to IDs and updates the ID fields directly on interface tables. If there is a value in the ID field, it takes precedence, and corresponding value fields are not used in the processing at all.

Note: If you decide to correct some value fields on interface tables because the order failed to import, you must clear the corresponding ID fields on interface table. For example, if the ship to location field is corrected, please check that ship to ID value is null.

Error Handling

The error messages output file identifies the following types of errors:

The output file also identifies order references to identify which orders failed to import. Note that in the case of validation errors or errors for unsupported features, one or more orders may fail to import while others import successfully. In the event of an unexpected error (memory errors, unable to extend tablespace, etc.), all orders fail to import. When an unexpected error occurs, all records in the batch are marked with an error. The errors must be cleared before submitting the records again for high volume order processing.

The following types of errors are not identified in the error count:

Setup

To import high volume orders:

  1. Populate the interface tables.

  2. Evaluate if simplified defaulting rules are sufficient. If so, use them to supply the required values.

  3. If defaulting rules are not sufficient, turn them off and provide the attribute values directly in the interface tables.

    Note: The QP: High Volume Order Processing Compliance profile option cannot be set by a user. It is set as a result of running the “Maintain the Denormalized Data in QP Qualifiers” pricing concurrent program. It should be run with the update type of HVOP_Pricing_Setup, Update High Volume Order Processing profile.