This action might not be possible to undo. Are you sure you want to continue?
An Oracle White Paper May, 2005
Performance in Order Management
This document provides a broad discussion of how to use Oracle 11i Order Management for a robust order management solution in high volume industries. To accomplish this goal, the document lists a number of functional areas that may be tuned for optimal scalability. Order Management has an extensible configurable architecture, which allows you to tailor your flows in a way that makes sense for your industry and your business requirements. Of course, how you use and configure your system impacts performance. This document identifies opportunities for setting up your system to scale for higher volumes. High volumes may occur in any industry, but are particularly common for Consumer Goods, Wholesale Distribution, and Telco. Manufacturing companies may also have high volumes, particularly if they are using models. In general, high volume businesses process 50,000 to well over a million lines a day. However, you may want to follow some of the suggestions in this document even if you are processing 30,000 lines a day. Performance varies depending on what features you use, and how you perform key functions such as scheduling, pricing, tax calculation, credit checking, etc. This document provides tips for each of these functional areas. Performance is also dependent on system configuration. It is not possible to make absolute hardware recommendations, because hardware requirements vary based on the features used and the volume of processing. Hardware requirements may also vary depending on the time window allowed for processing. For instance, more powerful hardware is required to process 100,000 lines in one hour than in three hours. The best hardware is the fastest hardware, with substantial available memory. Although it is not possible to predict throughput for a given hardware configuration, it is possible to identify throughput observed with a specific hardware configuration. Please refer to Appendix A of this document for information about throughput observed using a specific set of features with 11i10.
White Paper Title
Order Management supports the on-line manual entry of orders. High volume users who enter many orders online should use the Quick Sales Order form, as it can be tailored to reduce the keystrokes required to enter orders. Order Management also provides two types of Order Import, standard and High Volume Order Processing (HVOP), a bulk-enabled version of order import introduced with 11i9. Standard Order Import processes and inserts records one at a time into the database. Bulk-enabled HVOP can process and insert multiple records at once, so it is called bulk-enabled. Standard order import is full-featured. HVOP supports a more limited feature set. We sometimes use the analogy of an SUV and a sports car, comparing standard order import to the SUV and HVOP order import to the sports car. To take the entire family on an outing, you want all the features provided by an SUV. On the other hand, if all you need is to get somewhere really fast, you can do without accessories such as luggage racks and spare tires. Similarly, you can use standard order import to support all features of Order Management. For greater speed but with some feature limitations, you can use HVOP. Most of the tips in this white paper pertain to importing orders more quickly. This is appropriate, as most high volume users import a significant percentage of their orders. However, there is also a section pertaining to online order entry, UI Performance. This document is organized by feature. It identifies each feature affecting performance, and explains the impact. It also states whether the recommended tips affect only HVOP order import, both types of order import, the process order API, and / or online processing.
Oracle Order Management has always supported full-featured order import. Some high-volume users asked for a streamlined, more performant version of order import in exchange for a somewhat reduced feature set. This was provided in 11i9.
In 11i9, Order Management provided High Volume Order Processing (HVOP) as an alternative way to import new orders – in other words, the creation of orders. This method of order import achieves performance gains by: • • Using the bulk processing features of RDBMS Processing order in batch, rather than order by order
White Paper Title
and DELETE. i. some features are supported but not optimized. Shipping Additionally. Pricing lines in memory cache. which is available to early adopters via the Approved Strategic Implementation Program. Lines interfaced from shipping back to Order Management are also bulk-enabled. workflow. 11i10 provides performance improvements for lines interfaced with shipping. UPDATE. before posting to the database Pricing attribute mapping in memory cache across orders Using one call to price all orders being imported • • Many pricing features used in high-volume business flows are supported.• • Providing a streamlined. which includes statements that change the data. more limited feature set Reducing the number of SQLs (Minimum DMLs) and managing data in memory. e. credit checking. rather than line by line.g. This is achieved by: • • Leveraging the JAVA pricing engine. INSERT. On the other hand. shipping integration and pricing integration. The improvement is for lines interfaced from Order Management to Oracle Shipping Execution. (DML is for Data Manipulation / Modification Language. if full quantity is shipped. perhaps with minimal hardware. you may be a candidate for HVOP. • Lines imported in Booked status with High Volume Order Processing (HVOP) order import are interfaced to shipping in batch.000 lines in an hour. Distributing data equally across threads based on number of lines per order • HVOP order processing can be an option for those who need to process large volumes of order lines in a limited amount of time. a different processing environment might be capable of processing 100.000 lines per hour without using HVOP. the following areas were enhanced to better meet the needs of high volume users. Note that this second • White Paper Title Page 4 . for either of the following conditions. pricing is bulk-enabled for HVOP order import. Refer to the Pricing section below for more details. If you have to process 30. 11i10 In 11i10.e. With HVOP 11i9. Pricing With 11i10.
manual pricing adjustments. and credit checking. to reserve lines for the reservation time fence. Shippable and non-shippable flows are supported. and use standard order import to bring in those lines using features not supported by HVOP. HVOP ORDER IMPORT If you are a high-volume user. These are supported: order creation. the time window available to import a specific number of lines. and then the Reserve Orders concurrent program. you are probably importing the majority of your order lines. To help with your self-analysis.performance improvement is not restricted to orders imported with HVOP. The autoscheduling profile option is supported.1. if 20% of your lines require drop ship. HVOP order import actions are limited. ATO items. HVOP autoscheduling supports ATP calculations but does not support the reservation time fence. However. acknowledgements. tax can be calculated at invoicing. but drop ship and return flows are not. With HVOP. 225753. consider importing 80% of your lines using HVOP. Process Manufacturing added HVOP order import support for process items. You need to evaluate whether you can use HVOP order import. workflow scheduling is supported but not optimized. If desired.1 Keep in mind that deciding whether to use HVOP is not an either / or decision. Process Manufacturing For 11i10. Orders paid with credit cards cannot be imported with HVOP. and required features.5.8. (Credit-checking is supported but not optimized.com/metalink/plsql/showdoc?db=NOT&id=225753. and the remaining 20% of your lines using standard order import. you can use Autoscheduling to schedule the lines. How do you know whether to use standard or HVOP order import? There are many factors to consider: line volumes. the system configuration. Workflow scheduling supports ATP and the reservation time fence. updates and deletes. Other HVOP supported features include holds processing. You can use both. HVOP does not support tax calculation at entry or booking. Oracle Order Management provides a questionnaire to help you assess if your business is a good candidate for HVOP order import. and service items are not.) White Paper Title Page 5 . Using HVOP. Standard items and kits are supported. and booking. http://metalink. This document. You can use HVOP to import those lines that are eligible for HVOP. item cross-referencing.oracle. is available on Metalink. released in 11. but ATO / PTO models. For example. These are not supported: manual sales credits.
White Paper Title Page 6 . navigate to the Pricing -> Setup -> Event Phases form. This means the bulk-enabling feature. this document will be updated. but this deferrment will not take the lines to Invoice Interface in less time. which is described in the subsequent section on defaulting. This will prevent the system from calculating freight charges at Ship Confirm. is used to push Booked lines all the way through to shipping more quickly. it does support a more simplified defaulting architecture. i. and then the Inventory Interface. KEY FUNCTIONAL AREAS IMPACTING PERFORMANCE Shipping With HVOP 11i10. the system does not incur the cost of splitting lines. These calls are serial. If there is an active Event called “Enter Shipment”. If there is a change. OM Interface completes before Inventory Interface begins. you can improve ITS performance by grouping deliveries with fewer trips. At the time of this writing. which optimizes performance. if you import lines with HVOP order import in Booked status. Deferring the call to Inventory Process Online API What else can you do to improve the performance of ITS? When setting up ITS (Interface Trip Stop). This means that performance is better if you can avoid partially shipped lines. and also to the concurrent program for Interface Trip Stop. you have the option to defer the Inventory Process Online API which occurs during Inventory Interface. However. You may want to defer Inventory Process Online API for the purpose of load balancing. there is no indication that performance is improved by deferring the call to Inventory Process Online API at the time of Inventory Interface. To do this. Additionally. Query up all of the sequences. you can turn off pricing events triggered by Ship Confirm. Shipping first calls the Order Management Interface. the lines are bulk-enabled as they are interfaced with shipping. When you ship full quantity. Preventing Calls to Advanced Pricing at Ship Confirm If you are not calculating freight charges at ship confirm. ITS When you Ship Confirm or run the Interface Trip Stop concurrent program in 11i10.e. This performance benefit applies to the ship confirm process.HVOP does not support the full defaulting framework. disable it by giving it an End Date. the interface of lines from shipping back to Order Management is optimized when full quantity is shipped. Appendix B contains a complete list of supported and unsupported HVOP features.
These features are supported: • • • • • Discounts Surcharges Freight and special charges Static or dynamic formulas GSA pricing Unsupported features are: promotional goods. Also. catchweights pricing. The flag for autocalculate freight at Ship Confirm can be found on the Shipping Parameters form under the Transportation tab. coupon issue.l_industry) If l_fte_install_status equals to 'I'. item upgrade.Note: you can only access the Event Phases form if you have fully licensed Advanced Pricing. if you have not licensed Oracle Transportation Execution. then the flag is checked and Advanced Pricing will be called at Ship Confirm. term substitution. and this in turn will call Advanced Pricing at the time to calculate rates.get(716. If installed. You can check whether Oracle Transportation Execution is installed via a PL/SQL function: fnd_installation. PRICING With release 11i10. Oracle Shipping will call Oracle Transportation Execution to rate the trip. pricing is bulk-enabled for HVOP. Note that there are three levels of pricing performance possible with HVOP 11i10 pricing: O Optimal Optimal Use Java Pricing Engine* Use supported pricing features Improved from 11i9 Use Java Pricing Engine* Use all pricing features Same as 11i9 Do not use Java Pricing Engine* Use all pricing features *Available to those in the Approved Strategic Implementers Program White Paper Title Page 7 . limits processing. Attribute sourcing is limited because orders are priced before posting to the database.l_fte_install_status. the flag for AutoCalculate Freight Rate at Ship Confirm is always checked. If Oracle Transportation Execution is installed. check to make sure Oracle Transportation Execution is not installed accidentally. then it means that Oracle Transportation is installed on that instance. If Oracle Transportion Execution is installed.716.
turn it off. Oracle Advanced Pricing supports modifiers that apply only at the time of booking. or change the above mapping of events to phases. here’s what happens: • • • • When you type in Item. To turn off repricing at booking. When you navigate out of a line. If you turn off repricing at booking. Quantity. it confirms that you have setup modifiers for the BOOK event. or Process Order API calls with the action request to Book the order. if you add a phase to both the LINE and ORDER event. But many users set up pricing to occur at the time the lines and orders are created. For example. sysdate)) and rownum=1. If you are using this functionality. This disables the Book event for pricing. If you want to add your own phases. Pricing Setup Tips When you are pricing online. do not attach the same phase to different events. For any event that has a BOOK event. do you require repricing at booking? If not. and tab out. To identify whether the Booking process is executing repricing. the PRICE event fires. When you book the order. set the Start Date and End Date to some prior date on the Event line. If the SQL query returns a value greater than zero. use the Pricing Manager responsibility. White Paper Title Page 8 . For example. the ORDER event fires. and query all phases. run the following SQL statement: SELECT count(*) FROM QP_EVENT_PHASES WHERE pricing_event_code = 'BOOK' AND trunc(sysdate) between trunc(nvl(start_date_active. you should not prevent repricing at booking. all the modifiers in this phase will be evaluated twice. sysdate)) and trunc(nvl(end_date_active. the LINE event fires. Go to the Event-Phase window. once when you navigate out of a line and again when you save the order. It also improves the performance of online booking. When you save the order.Repricing at Booking Regardless of whether you use standard or HVOP order import. This degrades performance unnecessarily. the BOOK event fires. If this is when your pricing occurs. it will improve the performance of both standard and HVOP order import. you can turn off repricing at booking. there are other pricing considerations.
which are not allowed with deactivation. If the site level value for QP: High Volume Order Processing Compliance is Yes. This is because the optimized code path doesn’t load the global record structure for G_HDR or G_LINE.) Run the concurrent program. • Setup the JAVA pricing engine. instead it is set by the concurrent program Maintains the Denormalized Data in QP Qualifiers. you can de-activate one of the pricing lists. or not use the optimized code path. rather than end dating. you could change your modifier from List Line Adjustment Phase to All Lines Adjustment Phase. For example. as well as both standard and HVOP order import. you should perform these setups. To optimize HVOP Pricing available with 11i10. and if you are not using customer sourcing rules. If you are sure you never use specific modifiers. you may need to modify your custom sourcing rules. as opposed to end dating. But if you define the same number of modifiers into two lists of 5 modifiers each. assuming you participate in the Approved Strategic Implementers program. Check the site level value of the profile option QP: High Volume Order Processing Compliance. it is better to deactivate them to ensure that the system will not evaluate and apply them. no further setup is required. Note: If 10 modifiers are in a single modifier list. minimize your modifiers in phases attached to the LINE event. It updates the profile option QP: High Volume Order Processing Compliance. This profile option cannot be set by users.If you are looking to reduce time navigating between lines. to determine if you can use the optimized code path. the pricing engine will only evaluate the 5 modifiers that are not end-dated. The above setup tips can improve the performance of online orders. (The setup steps will be referenced when the JAVA pricing engine is in full production. is that end-dated modifiers can be applied if you price quotes or orders with past dates. is that deactivating incurs less cost because the active flag on the modifier list is indexed. define your modifiers for easy deactivation. Also. you will need to modify your pricing setups. If you constantly change your modifier setup. But if the value is Yes and if you are using custom sourcing rules. This program checks your pricing setup. Then the pricing engine will evaluate only active price of 5 modifiers. and if 5 of those modifiers are end-dated. If the site level value is No. QP: Maintains the Denormalized Data in QP Qualifiers. there is some additional code to handle end date null values. End dates are not indexed. If your custom sourcing rules call G_HDR or • • • White Paper Title Page 9 . One benefit of deactivating. Another benefit of deactivating.
it’s critical that the modifications be done correctly. The above steps will improve the performance of HVOP order import. It also reduces DML contention against the wf_item_activity_statuses. Then when Order Management updates these subprocesses via a patch. the rest of the flow will contain references to the subprocesses defined by Order Management. So if you copy the flow and insert a new activity at the top level (i. you need to recopy and modify again the seeded flow if you have changed it. the main flow). This allows you to maintain the line flow for sourcing from stock. If you remove the subprocesses.1 With 11i10. With the Generic: Performance lineflow. Generic. you can delete the activity Branch on Source Type. Generic: Performance. WORKFLOW If you are using 11i9. This is because the traditional Line Flow. For instance. This is a side effect of having everything at the top level for performance reasons. Therefore. as White Paper Title Page 10 . It can be used for all items types. The benefit of the Generic line flow is that it simplifies extending or customizing workflow.e. when a patch is applied. the system does not need to maintain status information for the subprocesses. online processing. provides the same functionality as Generic line flow. the streamlined version of generic line flow is not seeded.oracle. only copies of the lineflow. it should not be modified. modify your sourcing rules to pass the values directly. There are no references to subprocesses. the modified workflow automatically points to the updated subprocess since the modified flow only contained a reference to it. For more information on streamlining workflow. has subprocesses. if you source from stock and do not manufacture. Note: The streamlined line flow. refer to Metalink Note 130511. there are no subprocesses. If you modify your flows. and Process Order API. This seeded flow improves performance by reducing the number of subprocesses and status checks. You may even be able to remove additional activities based on your business requirements. Because this flow is not modular. Using only the Java Pricing Engine will improve the performance of standard order import. eliminating subprocesses.com/metalink/plsql/showdoc?db=NOT&id=130511. and also for the Start / End activities inside the subprocesses. Order Management seeds a generic line flow for performance: Line Flow – Generic: Performance.1 http://metalink. Streamlining workflow improves the performance of both standard and HVOP order import.G_LINE. but you can create your own streamlined version.
To run the WF Background Engine. and cannot be multi-threaded. and progress timed-out lines one time a day. the WF background engine will pick up all timedout lines. you could pick up lines with deferred fulfillment. For example. and concurrent programs that process workflow activities. the WF background engine will pick up all deferred lines. • Try to avoid running the Workflow Background Engine multiple times with both of the above parameters set to yes. Workflow Background Engine The Workflow Background Engine also impacts overall system performance. However. You may need to run the WF Background Engine several times a day. run it as required to check for one of the parameters. you must set two parameters: • Deferred? If set to yes. the frequency depends on your business needs. The booking process is not inherently faster if deferred. and Process Order API. (It’s likely that you have more deferred processes than timed-out). but the process will be more efficient if you specify either Deferred or Timed Out lines. not both. The Workflow Background Engine processes line by line. It improves the performance of the Process Order API. online processing. For example.well as online performance. By analyzing the frequency and type of processing you require. you can ensure that the WF background engine runs efficiently. with seeded flows you can defer either Schedule Line or Ship Interface by adding a Wait Activity. For instance. as shown in the diagram below. It is single-threaded. Instead. you might want progress Deferred lines four times a day. but it provides a White Paper Title Page 11 . The activity of the Workflow Background Engine affects all order processing – standard and HVOP order import. Deferring Post-Booking Workflow Activities You have the option to defer post-booking activities at the line level. Timeout? If set to yes.
mechanism for load balancing. you will need to calculate tax at invoicing. not view the tax in the sales order form. it is possible to declare the point of tax calculation on the Order Transaction type setup. Evaluate whether you really need tax calculation at entry or booking. When converting quotes to orders. You will need to decide whether you can defer tax calculation. If you are importing orders or entering faxed information. you could defer booking. If you are using HVOP order import. White Paper Title Page 12 . Deferring tax calculation is a requirement for HVOP. Deferred booking is recommended only if (1) you cannot meet your throughput goals during peak hours and (2) you have exhausted all other tuning possibilities. Also. or 11. Certain order-taking scenarios lend themselves to deferred booking. the process can take some time. the sales order form. there is a higher possibilty that the tax rate may change between booking and invoicing. In many high volume scenarios. you might want to defer the booking process. This feature is often needed only when selling directly to consumers. Additionally. based on your business needs. With Order Management Pack G. if you are talking to a customer while taking the order. However. you will not be able to view the tax if you open the order before invoicing. The booking action can then be done in the background by the workflow engine. If a product is backordered for any length of time. and the Process Order API. you might prefer to book the order while on the phone with the customer.7.5. The Tax Event attribute on the Finance tab can be set to Invoicing. as HVOP does not support tax calculation at booking or entry. credit check will not include taxable amounts. specify the Receivables Transaction Type. Tax Calculation Tax calculation at the time of entering or booking an order is only an estimate. it improves the performance of standard order import. This reduces processing time for tax defaulting and tax calculation. In that case. Then when a user performs an action to convert a quote to an order. the requirement is simply to print the tax on the invoice. the process will take less time. RECEIVABLES TRANSACTION TYPE For each line type set up in Order Management. Order Management does not perform any tax calculation. manual order entry or order import will be faster because the booking process is deferred. the tax is still calculated in Receivables when the invoice is created. Another scenario that lends itself to deferred booking is converting quotes to orders. which improves the performance of saving lines. If you can defer booking until off-peak hours. If you are convering a large quote of perhaps 1000 lines to become a booked order. With tax calculation deferred until invoicing. However.
evaluate whether you can populate the values directly in the interface tables. For example. specify all ID columns on the interface tables instead of populating the Value columns. This reduces the time that import process requires to convert Values to IDs. and updating those attributes within Order Management. CREDIT CHECKING Evaluate the necessity of credit checking all customers. Process Order API. pass the Bill To directly to the header and the line. For best performance. Using precalculated exposure functionality. The User Guide explains that you can also import exposure details from an external system. If you pass all values to the interface tables. In many scenarios. this will improve performance. order import. But if you are importing orders. In that case. consider using the precalculated exposures. DEFAULTING Defaulting is necessary to save time when entering orders in the sales order form. you may know that the Bill To on the line is the same as the Bill To on the header. Values to ID Conversions To improve performance. You do not have the option to turn off defaulting for standard order import. to setup precalculated exposure. Avoiding Values to ID conversions will improve the performance of HVOP and standard Order Import. changes to the customer or customer site are calcualted and updated. users still ship to their important customers. If you can limit credit-checking to high-risk customers. online processing. you could still recognize performance gains by populating values directly White Paper Title Page 13 . the system can avoid the cost of checking the defaulting rules. These performance improvements will apply to the sales order form. Refer to the Order Management User’s Guide. Both standard and HVOP order import support real-time credit-checking and precalculated exposure functionality introduced in Family Pack G. and the Process Order API. Initialize Credit Summaries Table Concurrent Program. Order Management enables you to periodically rebuild a credit exposure image (orders. even if there are credit issues. When you submit the Initialize Credit Summaries Table concurrent program.This improves the performance of online processing. instead of defaulting to get those values. based on your setup for each defined credit check rule. However. invoices and payments) for all customers or customer sites for all possible credit rule definitions. and Standard order import.
For headers. SCHEDULING White Paper Title Page 14 . Populating the values directly in the interface tables improves the performance of both order import. HVOP order import parameters window provides the option to turn off defaulting. these attributes are not defaulted. They must be supplied directly in the interface tables: • • • • • • • • • • • Agreement Currency Customer / Contact Customer PO Deliver To / Deliver To Contact Invoice To / Invoice To Contact Ship To / Ship To Contact Salesperson Shipping / Packing Instructions Sales Channel Subinventory All line-level attributes except subinventory can default from the header. the fixed hierarchy is: • • • Item Ship To Order Header With HVOP. If you can populate values directly in the interface tables. HVOP Defaulting HVOP does not support the full defaulting framework. thereby allowing the system to bypass defaulting. turn off defaulting for better HVOP order import performance.in the interface tables. the fixed hierarchy is: • • • • Agreements Invoice To Ship To Order Type For lines. Instead it supports simplified defaulting with a fixed hierarchy of sourcing. and the public Process Order API.
lines can be autoscheduled when the line is saved. or by manually entering the schedule date. Scheduling can occur with batch order import. A comparison is below. Performance More performant Flexibility Less flexibility: scheduling always occurs at the time of entering or updating a line Scheduling can include ATP calculations and reservations. either standard or HVOP. etc. without manual internvention. Autoscheduling What it is Schedules when the line is entered or created Workflow Scheduling Scheduling occurs as part of a flow. Booking is followed by workflow scheduling. ATP White Paper Title Page 15 . via right-mouse click scheduling. or at the time of manual online order entry. 1. after a Wait activity. If scheduling is not deferred. if set up to do so Incurs cost associated with the start and stop of workflow More flexibility: scheduling can be deferred until after Booking. Autoscheduling Online Order Entry using the UI Standard Order Import HVOP Order Import Supports both ATP and the reservation time fence Supports both ATP and the reservation time fence ATP is supported but the reservation time fence is not Workflow Scheduling Supports both ATP and the reservation time fence Supports both ATP and the reservation time fence Supports both ATP and the reservation time fence There are a number of factors that affect scheduling.Imported lines can be autoscheduled or scheduled via workflow. When entering orders through the UI.
and the reservation time fence. If you are using standard order import and if a line fails to schedule due to no availability … • • If you are sending a Schedule Ship Date. White Paper Title Page 16 . Accurate ATP requires maintenance. If you do not do the required maintenance. the line is imported but unscheduled. online processing. as well as online order processing. If your volumes are high. The order will import and workflow will try to schedule the line again. try to populate the warehouse on the line. and may need to evaluate regions and zones. if the requested quantity is not available when Autoscheduling. 3. Sourcing Rules Regardless of whether you are using ATP. there is overhead associated with ATP. you can avoid the cost of the system checking sourcing rules to determine the best warehouse. you may encounter an issue if the requested quantity is not available. you may want to evaluate whether you can schedule for a ship date rather than an arrival date. You should use ATP calculations if needed. But if you send a specific Schedule Ship Date and there is no availability. 4. By specifying the warehouse. Reservations Manual online order entry and standard order import support the importing of reserved quantities. For example. you need to keep the PO receipt dates up-to-date.Regardless of whether you are scheduling with online order entry or with standard or HVOP batch importing. Arrival or Lead Time Scheduling Arrival / Lead Time calculations also require processing. the failed lines are imported without a Schedule Ship Date. If the requested item is not available with workflow scheduling. You may need to calculate lead times and arrival dates. the quality of ATP suffers. If you are autoscheduling. none of the lines for that order are imported. consider limiting the use of ATP to a few critical items. Lead time scheduling affects standard and HVOP order import. 2. With HVOP. and Process Order API. workflow takes the line back to Scheduling Eligible status. But if your volumes are extremely high. but many users find they can avoid ATP checks in a high volume environment. Lead time scheduling will look at the sourcing rules. the system logs a message and continues. This applies to both HVOP and standard order import. With ATP. Or you may want to to limit ATP high value items with scarce supply.
e. Autoscheduling occurs as the line is created. either with standard or HVOP order import. Also. However. For example. but scheduling occurs only when the Model line (for an ATO model or a Ship Model Complete (SMC) PTO model) reaches the scheduling activity. you can apply patch 3794704. When importing orders. and you want to use this functionality. If you want to autoschedule with standard order import. set the OM: Autoschedule profile option to Yes. For better performance. Then the system does not have to incur the cost of requerying the BOM and exploding it again at the time of scheduling or picking. With White Paper Title Page 17 . With HVOP order import.5. use Reserve Orders after booking. to create reservations as desired. using either standard or HVOP order import. i. there is an additional benefit for autoscheduling. if your batch size is 5000. With 11i10. and then run Reserve Orders. it applies to standard order import and online processing. released in 11. This is because there are associated costs with workflow scheduling. If you are using 11i9 or an earlier version with ATO or SMC models. The system still sends all configuration lines to GOP for scheduling.8. However. If the requirement is to book and schedule synchronously as quickly as possible. but autoscheduling does not.000 lines. Scheduling Configurations If you are using kits. there are two calls made for workflow scheduling. HVOP workflow scheduling supports the reservation time fence. Reserve Orders is not inherently faster than reserving via the Reservation Time Fence. The recommended approach for creating reservations with HVOP is to schedule via autoscheduling. and also online workflow scheduling. depending on your batch size. set the profile option to freeze the included item either at Entry or Booking. then defer creating reservations. the system may have to make multiple calls for workflow scheduling. and you import an order with 10. This profile option determines the date and time Order Management uses to determine the included items for a configuration’s bill of material. This performance benefit applies to workflow scheduling. they also support autoscheduling. 5.HVOP does not support the importing of reserved quantities. The above profile option does not apply to HVOP. Scheduling with Order Import Both standard and HVOP order import support workflow scheduling. OM: Included Item Freeze Method. Your requirements should drive the decision about when to reserve. note the setting of the profile option. a change was made in the way ATO and SMC PTO model lines are processed for workflow scheduling. autoscheduling is more performant than workflow scheduling.
If you need for Booking to be faster. you will lose the benefit of bulkenabling lines to the point of Shipping Interface. autoscheduling occurs as each line is saved. set the value of the profile White Paper Title Page 18 . you could schedule synchronously with booking. If you use autoscheduling with online order entry. One advantage of deferred scheduling is that it can occur in evenings. Online Scheduling Within the sales order form. as an example. not synchronous with booking. You may want to evaluate whether it’s beneficial in your business to delay scheduling until a time when there is less load on the system. but you must schedule lines as quickly as possible. With deferred scheduling. Then the cost of scheduling is not incurred at the time of booking. HVOP note: With 11i10. the system makes a single bulk call to GOP. a typical line flow synchronizes scheduling to occur with booking. Pressing Book causes the order to book. If you defer scheduling with 11i10. or by entering the schedule date. but that you can book orders more quickly. This benefit applies to both order import (standard or HVOP). ATTACHMENTS Order Management allows setting up rules to automatically attach documents when creating an order. booking is faster. If you schedule via workflow. The order lines are also updated in bulk. and plan scheduling to occur at a time when your processing load is lighter. You can modify workflow so that scheduling is deferred to occur at a different point in the flow. In addition. This is often done manually using Right Mouse. rather than line-by-line. The benefit of deferred scheduling is not that scheduling takes less time. workflow schedules the order lines. With HVOP. This will not occur if scheduling is deferred. and the overall scheduling time is more performant than workflow scheduling.HVOP. which is faster than a line-byline call. If autoscheduling is turned on and you are entering orders manually. lines must reach the status of Awaiting Shipping. at a time with the processing load is lighter. the interface to shipping will happen line by line. Also. Scheduling. it is possible to progress Booked lines more quickly to the point of Shipping Interface. If you need to Book and Schedule synchronously. To progress to the point of Shipping Interface. you can schedule orders online. you can autoschedule or schedule via workflow. consider your requirements. After booking. with a Schedule Date. with right-mouse click scheduling. you can autoschedule either by setting the OM: Autoschedule profile option to Yes. and also to online scheduling. If you are not using this functionality. When evaluating whether to defer scheduling. but defer the ship interface. omit reservations at the time scheduling and later run Reserve Orders. defer scheduling. or providing a Schedule Date on the line.
Turning off attachments improves the performance of standard order import and online processing. it helps the performance of standard order import. either manual or automatic. But Audit Trail has an effect on performance. and Process Order API. and online processing. TRANSPORTATION EXECUTION From 11i9. Versioning is a useful feature but it can tax the system if used too broadly. AUDIT TRAIL Order Management provides functionality to keep audit trails for various attributes. The functionality is very flexible. i. you might want to roll the version only at the time booking. If you require versioning. turn off Get Ship Method and Freight Rating in the Order Management System Parameters form. OM: Apply Automatic Attachments to No. If you do not require this functionality. turn it off in the Order Management Systems Parameters form. Process Order API. and online order entry. online order entry. so it is not an issue with HVOP. HVOP supports only the Create operation. Versioning uses the Audit Trail infrastructure of the Constraints framework. allowing you to maintain an audit trail for one attribute but not for others. either Fulfillment or Negotiation Also limit the conditions. MARGIN CALCULATION Order Management provides functionality to calculate margins for order lines. Disabling the Transportation Execution parameters in the OM parameters form improves the performance of standard order import.e. HVOP order import does not support automatic attachments. limit its use to the required attributes: • • Specify which attribute(s) should be versioned Select the correct Applies To phase. and there will be a larger performance impact for larger orders. Debug White Paper Title Page 19 . Order Management provides integration with Transportation Execution. Analyze your use of audit trail. If you can turn off margin calculations.option. HVOP does not calculate margins. If you can minimize its use. To help performance for standard order import. Process Order API. Keep in mind that versioning backs the entire transaction into history. VERSIONING In 11i10. If you are not using Transportation Execution. limit the extensive use of Audit Trail. Order Management provides versioning capabiltiy. The transportation features Get Ship Method and Freight Rating are not supported by HVOP. it will improve overall scalability.
you will probably want to evaluate whether you can import a significant portion of your orders using HVOP order import. White Paper Title Page 20 . This profile option should be set only at the user level. Interface Trip Stop. Although most high volume environments depend heavily on order import. set to 0 for OFF WSH: Debug Enabled. Ship Confirm. and then import the remaining lines using standard order import. the use of Folders tailored to your business scenario can save users a significant amount of time. and Inventory Interface. some high volume businesses enter orders online. set to 0 for OFF (for Pick Release and ITS debug) QP: Debug Mode. set to No WSH: Debug Level. It may be necessary to turn on debug for the purpose of troubleshooting the code execution path. if you are importing the bulk of your orders. If so. UI Performance This section pertains to entering order online processing. the debug level should be 0. Folders If you can use the default sales order form. First bring in all lines eligible for HVOP order import. However. i. increasing processing times by a factor of up to 10. separate the lines for each import run. turn on debug only for the purpose of generating the debug file. evaluate whether you can use the default folders. you may want to consider the trade-off of faster processing vs faster order entry.e. Or if only a few orders require frequent moving from tab to tab. as well as online processing. On the other hand. For generating Order Management trace files to record elapsed time. set to Request Viewer Off Having debug on can result in significant performance overhead. set OM: Debug Level to OFF. In a manual order entry environment. no special setup is required. They can also negatively impact Pick Release. • • • • OM: Debug Level.Ensure that debug is turned off. you may find that a tailored folder can reduce the amount of time required to enter the typical order. To use both standard and HVOP order import. However. there is less processing cost in the sales order form. HVOP Setup For Order Management HVOP order import. The setting of any of the Debug profile options can affect both standard and HVOP order import.
which would advance the line to Scheduling Eligible. i. Defaulting Defaulting required values greatly reduces the amount of time required for CSRs to complete the entry of an order. This feature is useful. improves the performance of saving configurations during online order entry. Online Configurations The profile option. As much as possible. For instance. OM: Show Line Details. there is some cost to defaulting. If your typical orders are for 10 models with 50 White Paper Title Page 21 . Alternatively. This feature applies only to unbooked orders created using the online UI. you can defer scheduling to occur later in the flow.6 Order Management added a feature to create a new customer account from the sales order form. test to ensure that pricing occurs as expected.5. you may want to autoschedule. because it allows CSRs to create a new customer without having to leave the sales order form and to move to the Customer form. i.e. On the other hand. is more beneficial if your model has many classes. allows you to show only the model on the sales order form. immediately after booking. all actions in the sales order form. you could create a line flow with Scheduling Manual subprocess.e. If you don’t need to schedule when saving a line or at the time of booking. the performance gains will be noticeable. If set to Yes. There is no impact on standard or HVOP order import. However. don’t incur the cost of defaulting that value to the header or line.Using default folders improves the performance of online processing. autoscheduling schedules lines as they are saved. In this case. For example. the benefit will be less. if you are using 5 classes. The values are Yes and No.e. Class lines are inserted into the database with very little validation. This extends the booking time. As an alternative. if you are not using the attribute for Shipment Priority. i. Another profile option. If you enter orders in the sales order form. However. OM: Configuration Quick Save. You should review your defaulting to ensure that you are defaulting only those attributes that are of importance to your business. 50 classes and 50 options. the class may act more like a placeholder. have all customer created before the order entry process. or they could scheduled manually at a later time. each with 50 options. Add Customer In 11. Lines in Scheduling Eligible status could be scheduled later using the Schedule Orders concurrent program. if set to Yes. If you are pricing classes. at the order event. Online Booking Scheduling can occur via workflow. This profile option. the order entry process can be greatly reduced if the customer exists in the system.
if you always use the Price and Availability form. Make sure that your changes are supporting the common business scenarios. you can reduce the number of keystrokes for entering an order. Quick Sales Order The Quick sales order form allows you to tailor the form for optimal order entry. you can move more quickly from the order header to the lines tabs. or a tax-related field changes. and if the Defer Pricing flag is set. You can keep a feature you use frequently. But when the order is savevd. instead both price and tax are calculated when the order is saved. instead pricing occurs when the order is saved. there is a flag on the form to Defer Pricing. At the time of saving. If you show only the lines for the model. pricing does not occur as the lines are entered. for instance. assume that the tax event on the Transaction Type is Entered. This profile options applies only to online order processing. you can have Pricing and Availability as a button on the form. tax calculation is deferred until the order is saved. Updating other attributes that don’t trigger taxing will not cause tax to be recalculated. Defer Pricing If you are using the Quick sales order form. • If the Tax Event on the Transaction Type is Entered.lines each. Additionally. it’s not feasible to view all the lines for a model within the sales order form. tax is calculated when the price is changed. tax is not calculated because the price is null. and Defer Pricing is set. White Paper Title Page 22 . and is relevant for both usability and improving performance. the pricing and tax calculation occurs. • The tax event on the Transaction Type is Entered. (This flag does not exist on the standard sales order form. if the tax event on the Transaction Type is Entered. If set to yes. and nagivates out of the field. By tailoring the form to meet your requirements. updating the Item or Qty attribute in the order will calculate tax. even if Defer Pricing is set to yes. You may prefer to show only the lines for the model. Also. But if Pricing is deferred. such as Pricing and Availability or Related Items. open in the lower region of the Quick Sales Order form. as you will want to avoid the cost of a tailored folder that is rarely used. Two examples are below. it’s easier to view what models are on the order. with a price. the price may change and tax will be recalculated again. If there is an existing order. Again. tax is not calculated when navigating out of the line. When the user enters an item or qty. For example.) The default value for this control is determined by the profile option OM: Quick Sales Order Form: Defer Pricing. and Defer Pricing is set.
g. Line Details. the active Line Details region displays refreshed date after the save. Users need to navigate to the region. to view the Line Details information. Line. If the following profile option is set to refresh. This option coordinates the Line Details regions. If you want the screen to be automatically refreshed. there is an additional profile option. i. The screen is refreshed. There are four possible choices for OM: Quick Sales Order Form: AutoRefresh: • • None. the screen is refreshed. Askme. while entering lines. Line. such as Related Items or Service. which eliminates the • White Paper Title Page 23 . only the Lines are refreshed after a save. or Both. or there may be a pricing update due to an order event. The entire order is refreshed to ensure the processing of delayed requests for changed values. Otherwise the screen is not refreshed. Automatic Refresh without Repositioning of the Cursor is more performance than Automatic Refresh with repositioning of the Cursor. Automatic Refresh without Repositioning of the Cursor. and they are not coordinated while entering lines. followed by AskMe. The Quick Sales Order form looks at the following profile to determine if the refresh should be initiated. i. For the Quick Sales Order form only. etc. Additionally. A dialog box asks the user to decide whether they want to refresh the screen to see the data. The changes in the Line Details region of the Quick Sales Order form.. e. Only the Line Details are refreshed after a save. and the cursor is always repositioned to the first line. Users have to requery to see the refresh changes. Related Items. Related Items. There are four values: • Automatic Refresh with Repositioning of the Cursor. Do not refresh the lines after saving. • • • Of these four options. Line Details. and the cursor is repositioned to the line from which the Save was performed. For example. OM: Quick Sales Order Form: Auto Refresh. a changed value on a model may cascade to options. a new profile option OM: Sales Order Form: Refresh Method is added in 11i10. Manual. In this case. are not refreshed after saving. Service.e. If the user says Yes. The screen is not refreshed automatically. orders are automatically requeried from the database after each save.Refresh Behavior In both the standard and Quick Sales Order form. The screen is refreshed. then the Quick Sales Order form looks at the above profile option to determine how the refresh should occur.e. To control the behavior of requerying the database for a refresh. Manual is most performant.
i. In this case. Invoking the Sales Order Form from the eBusiness Center results in opening the Sales Order Form. BEST PRACTICE FOR PERFORMANCE TUNING Begin by tuning performance for a single thread. or 500 orders with 2 lines each. the active Line Details region appears. Then tune performance for multiple threads. Again note the timings. for 100 orders of 10 lines each. • Both. autoscheduling. The refresh behavior impacts online processing. query for the customer in the eBusiness Center. For example. The profile option OM: Sales Order Form Preference controls whether TeleSales calls the standard or the Quick order form. i.e. if a typical order has 10 lines. For pricing. You want to avoid the frequent opening and closing the Sales Order Form. Both the Line and the Line Details regions are refreshed after a Save. pricing features. begin by creating a batch of orders that you will use to gather your sample data. importing them again in Entered status. Use an order size that is representative of a typical order in your production system. but does not enhance the performance of the processing of the order. Also the line details regions are coordinated while entering order line.need for the to navigate again to that region. Ensure that the order uses functionality typically used in your business. and then copy the customer account name from the eBusiness Center to the Sales Order form. etc. and qualifiers as your business requires. Note the timings for a single thread for 1000 lines of your typical order. This functionality improves the UI navigation. so the user does not have to navigate there manually to view the data in the line details region.e. credit-checking. with Trace ON. Single Thread For your test. keep the Sales Order Form open. and toggle to it from the eBusiness Center.e. create5-line orders. For instance. Then process the orders. set up price lists. which is expensive. i. Then do the following: • Import the orders in Entered status without turning on Trace. for a single thread for 1000 lines • White Paper Title Page 24 . etc. use 10-line orders. Integration with TeleSales TeleSales users can efficiently enter sales orders by directly calling the sales order form from the eBusiness Center form. Or if the typical order has 5 lines. Instead. modifiers.
Each thread will be for 1000 lines. Note the timings. Note the timings. Basedon analysis of the tkprof. Note the timings again -. the number of threads used. using the same typical orders as discussed in the above section. Implement Oracle’s recommendations. The most common batch size for diagnosis is 1000 lines. The above information is needed to report to Support the timings recorded. prsela]. fchela. and then begin another iteration of this procedure using a different number of threads. Start with perhaps 2 threads. Then import lines in Booked status with Trace On. custom indexes. • • Then import the orders in Booked status without Trace. Generate StatsPack or AWR (for 10g) reports for the run. or reverse key indexes. set up changes. and provide the trace file for one of the threads. Apply Oracle’s recommended changes to the environment. Then gradually increase the number of threads to find the optimal throughput. with the Explain plan turned off. set up changes. and may recommend additional patches. and then begin another reiteration of the test. Oracle Support may recommend additional patches. Throughput will increase as more threads are used. and the Tkprof outpot. The raw trace + Tkprof output can be sorted in [exeela. custom indexes. without trace on. do the following: Import a batch of 1000 lines in Entered status. TROUBLESHOOTING White Paper Title Page 25 . sort in exeela fchela prsela sequence. Repeat the process with SQL tracing enabled at level 8 (waits). prepare to run Order Management using 10 threads. Tuning for the optimal number of threads Repeat this process with a different number of threads to find the optimum number of threads to use. Testing for Scalability with Order Management After ensuring optimal performance for a single-thread run. for 10 threads. Using the same sample order size and setups. etc.using your typical order. Provide Oracle support with the recorded timings of the trace files. Note the timing and provide the trace file for one of the threads. Oracle Support will then be able to analyze the output. Then repeat the level 8 trace for orders in booking.for a single thread for 1000 lines using your typical orders.
which partitions Order Management tables. It gives the Database parameter details and their settings. For more informatin. If you are entering most of your order lines manually. Partitioning adds overhead for orders entered online. do not apply this patch for partitioning unless the overall benefit of partitioning outweighs the performance overhead.oracle. Statspack. Collecting Statistics If the SQL trace files. Metalink Note 169935. • White Paper Title Page 26 . There may be other reasons why you want to partition. you should gather statistics using the Gather Schema Statistics concurrent program in order to ensure the execution plans are based on the most recent set of statistics. and for which a significant amount of buffer cache latch contention is being observed.1 • bde_chk_cbo. or AWR reports suggest that a SQL statement or set of SQL statements are performing poorly and the root cause is due to a suboptimal execution plan.com/metalink/plsql/showdoc?db=NOT&id=169935. Some businesses import a small percentage of their order lines. For those who enter most of their orders manually using the standard sales order or the Quick sales order form. which results in improved scalability for standard order import or HVOP.sql -.1 Scripts In addition. To gather statistics for the schema of Order Management. you might want to separate open and closed orders. and the statistics may be stale.Order Management recommends this script because it provides output for analyzing any performance issue. You can of course partition the OM tables in a logical manner using other partition keys. but partitioning adds overhead. the partitioning supplied by Patch Patch 1531371 is not suitable. For example. is suited for those customers who primarily use parallel streams for Order Import or HVOP. with standard order import or HVOP.com/metalink/plsql/showdoc?db=NOT&id=130511.sql – Advanced Pricing recommends that you run this script if you are facing an issue pertaining to pricing performance.Partitioning Patch 1531371. http://metalink.1 provides information on how to use the following scripts: http://metalink. refer to the white paper Partitioning and Purging Best Practices in the eBusiness Suite. This patch partitions the tables by the primary keys to minimize block contention. refer to Metalink Note 130511. including the interface tables. qpperf.1.oracle.
HVOP order import does not import lines with unsupported features. Typically. If that is the case. rather than in the same block. you can apply the partitioning patch or rebuild the contended indexes as reverse key indexes. In that case. You can identify the hot or contended segments by referring to the Statspack or AWR reports in the segment waits section. you may need development assistance for troubleshooting. WATCH OUT FOR Here is an exception you will need to understand. Reverse key indexes reverse the key value. refer to the Pricing Performance White Paper: Metalink Note 137328. Oracle 11i Tuning Advanced Pricing for Optimal Performance http://metalink.1. ship sets or tax calculation at booking. and provide this information in your TAR. disk reads. and waits. This helps reduce index contention. prepare the information as directed in Appendix C. which results in index entries being stored across blocks.e.For additional information about pricing performance. i. you may experience segment contention due to block contention.l Scalability Contention If you are running multiple workers of Order Import or HVOP in parallel. With Order Management.com/metalink/plsql/showdoc?db=NOT&id=137328. To reduce the contention. Statspack or AWR will list the top segments by buffer gets. Trouble-shooting Analysis There may be occasions where you have implemented the tips covered here. the threads may show signs of contention such as waits on buffer cache latches including cache buffer chains latch waits. if you want to use both supported and unsupported features for HVOP. you need to separate lines for each type of import. so you will need to increase the buffer cache size to accommodate the reverse key.oracle. When multiple threads of order import (standard or HVOP?) are running. Reverse key indexes will also increase the index segment footprint in the buffer cache. and you still are having a performance issue. if you want to use both supported and White Paper Title Page 27 . the contention involves primary key indexes such as OE_ORDER_LINES_U1. With Pricing.
unsupported features. all your lines will import but the optimized code path will not be used if the pricing setups contain any unsupported features. White Paper Title Page 28 .
if part of the Approved Strategic Implementers Program Specify the Receivables Transaction Type for the lines Ensure that Debug is off • • • • • • Limited Features / HVOP Concurrent Program If you use HVOP. but HVOP supports the reservation time fence only via workflow scheduling. you could: • • • Populate the interface tables directly with all value. you can populate the Schedule Date directly in the interface tables for optimal performance. Then you can run the Reserve Orders concurrent program to place reservations per your defined parameters. But you want to find additional ways to improve your performance. You can run those programs at specific times.) Turn off Reprice at Booking Limit credit-checking to high-risk customers. so they are bulk-enabled up through Shipping interface Use the Java pricing engine. scheduling by supplying the Schedule Date in the interface table. you may want to use only those features supported by HVOP and Advanced Pricing. and drop shipping. You also want to use the reservation time fence. This allows you to schedule the orders in less time than using workflow scheduling. You can live without features such as iPayment integration. ship sets. To achieve your objectives. Line Flow – Generic: Performance If there are deferred processes. set the Workflow Background Engine to run efficiently (If you are not deferring processes. you could bring in the orders using HVOP. There are also concurrent programs for Inventory Interface and the Credit Check Processor. you may not need to run the Workflow Background Engine. either to White Paper Title Page 29 . For example. and using precalculated exposures Import lines as Booked. rather than use the limited defaulting capability provided by HVOP Use the streamlined workflow.EXAMPLES Limited Feature Set / HVOP Order Import Because performance is critical.
improve or the performance of order import or to control when processing occurs. and your requirement is to ensure that tax is printed on the invoice. However. Combining HVOP and Standard Order Import You have determined that for most orders. 10% of your orders are coming from an online web store. but you have high order volumes and a limited amount of time for importing and processing. Line Flow – Generic: Performance Set the Workflow Background Engine to run efficiently Turn off Reprice at Booking Limit credit-checking to high-risk customers. it’s OK to calculate tax at the time of invoicing. You can do this with HVOP. Additionally. You also ensure that no unnecessary calls are made to Pricing at the time of Ship Confirm. you modify as many setups as possible to optimize performance: • • • • • • • • Use the streamlined workflow. to ensure better performance of Interface Trip Stop. and using precalculated exposures Specify the Receivables Transaction Type for the lines Ensure that Debug is off Turn off automatic attachments if possible Limit the use of features such as Gross Margins. This is because 90% of your orders are shipped to directly to businesses. You use standard order import to import the remaining lines. you use HVOP to bring in the 90% of your lines that do not require tax calculation at the entry of booking of the order. for better load-balancing. For optimal performance. You decide to buy additional hardware and memory to support all features. and Transportation Execution as allowed by your business Also. Full Features / Standard Order Import You want to use all features within Order Management. You may even decide to defer Inventory Interface for a few minutes. you make every effort to ship full quantities. White Paper Title Page 30 . where tax must be calculated at the time of booking the order. Audit Trail.
Set up defaulting so that the CSR needs to enter minimal header information. or the Quick form. You will probably want to use the Quick Sales Order form. Options. Also choose the most efficient refresh behavior for the Quick Sales Order form. you may want the form to refresh. To avoid the cost of adding customers on the fly. based upon your business requirements. controls whether TeleSales calls the standard classic form.e. In 11i9 as well as in 11i10. you can directly launch the sales order form from the TeleSales eBusiness Center form. Services. A profile option. OM: Sales Order Form Preference. the cost of tailoring your own folder. Pricing and Availability. You should evaluate the advantages vs. If possible. This will greatly reduce the amount of time required to enter an order. but it may be acceptable to reposition the cursor to the first line. i. Related Items. set the Defer Pricing flag on the Quick Sales Order form to default to Yes. Integration with TeleSales TeleSales users can quickly and efficiently enter sales orders by directly calling the sales order form from the eBusiness Center form. but does not enhance the performance of the processing of the order. For instance. plus the item and quantity on the line. The profile option OM: Sales Order Form Preference controls whether TeleSales calls the standard or the Quick order form. set up accounts for all expected customers. as it can be tailored to keep open your most frequently used region. This functionality improves the UI navigation. White Paper Title Page 31 . Also consider using the seeded default folder. or Adjustments. which provides a 360-degree view of the customer.ONLINE ORDER ENTRY You have many heads-down data entry people who are pounding the keyboard to enter as many orders as possible in a short amount of time. for optimal performance.
Other environment details are: Applications . The order import tests are based on HVOP order import.0. using a single 450 Mhz processor. booking.11.1.3 (10gR1) Middle Tier .6. and were not audited or verified by an external agency. Credit Checks were not performed. The test was conducted using 260 orders and 77 lines per order. The following chart contains benchmarks for 11i10. • Various steps in the order-to-cash flow were measured: order creation. patchset 13 White Paper Title Page 32 . shipping & invoicing. These features were used to obtain the following benchmark.5.APPENDIX A Order Management provides many features.10 Vision Database – 10. Standard Items & Kits ATP / Non-ATP Mix (20%/80%).0. auto scheduling was used).8. Scheduling (For HVOP. A single price list was used without discounts. • • • • • Test Environment: • • These tests were internal performance tests. These numbers show the number of lines processed per hour for specific features. and each of these features has variations. It’s not feasible to provide a performance time for each of the feature variants.
11i10. For instance. Standard Items Interface Trip Stop.540 406.400 409.000 135.000 25.640 403. Standard Items Pick Release.200 37. Serial Controlled HVOP Order Import. Standard Items Ship Confirm.500 37.000 lines priced in an hour.500 112. Reserveable Items HVOP Order Import.320 129.620 134. Standard Items HVOP Order Import. One Hour.950 37. 4 processors could import 90. Reserveable Items Interface Trip Stop. Indications are that ITS and Pick Release also scale well. Reserveable Items Throughput per Hour 37500 37650 37400 37900 36000 25000 31173 8605 107000 75300 11400 8366 The order import features are known to scale well across multiple processors.000 108.2 Mhz Ghz 37.920 136. Kit Controlled HVOP Order Import with Pricing Pick Release.400 112.000 270.900 113.000 75.000 White Paper Title Page 33 . you might see a degradation of 10% across four processors. Reserveable Items Ship Confirm.Feature HVOP Order Import.e.650 112.600 388. i.000 405. Lot Controlled HVOP Order Import. HVOP Standard items Reserveable items Lot-controlled items Serial-controlled items Kits Std items with pricing 1 450 Mhz Processor 400 1.2 Mhz Ghz 135.800 90.000 4 450 Mhz Processors 400 1.700 36.
performance scales well with additional hardware.2 G H z 3 4 White Paper Title Page 34 . 300000 250000 Order Lines / Hour 200000 150000 100000 50000 0 1 2 N u m b e r o f P ro c e s s o rs 400 M H z 1 .The following graph demonstrates scalability across multiple processors. To achieve speed.
static or dynamic formulas. workflow scheduling. surcharges. freight and special charges.APPENDIX B These features are supported by HVOP order import: • • • • • • • • Autoscheduling. as described in the Defaulting section. Drop shipments End customer Freight Rating for Transportation Execution Get Ship Method for Transportation Execution Gapless order numbering Insert-based constraints Internal orders White Paper Title Page 35 . HVOP does support limited defaulting. and the scheduling parameters for LAD and Promise Date setup Booking Manual price adjustments Order creation Shippable and non-shippable flows Standard items and kits Pricing – many features such as discounts. GSA pricing Process manufacturing (11i10) These features are not supported: • • • • • • • • • • • • • • • • Add customer Any action request other than booking ATO items Audit trail Automatic attachments Commitments Configurations other than kits Credit card orders Defaulting framework – use of the full-featured defaulting.
Add. Change. coupons.• • • • • • • • • • • • • • IPayment integration Margin calculations Move. Disconnect (MACD) Multiple and partial payments Pricing attributes. deletes Versioning White Paper Title Page 36 . ship. fulfillment Tax calculation before invoicing Updates. ask-for promotions Quote processing Releases against blanket sales agreements Reservations Returns Service items Sets – arrival.
Identify the number of price lists and modifier lists. you need to provide the following information to assist with troubleshooting. provide the output of $QP_TOP/patch/115/sql/qpperf. Otherwise proceed to the next question. If you are experiencing a UI performance issues. Describe the middle tier hardware configuration (number of CPUs and memory) Does the environment use customized code in CUSTOM. Describe the Pricing setups. Is the “Not=” operator used on qualifiers? Are custom attribute mapping rules being used? If yes. Logged Issues Bug / Tar Number CSI Number Description 2. If there is higher selectivity (that is. 1. answer the following questions. the values should be cached. the pricing engine performance is much better. and if possible. fewer lines are eligible for the qualifier). do they typically apply to specific items / categories or to all items? Are blind modifiers used? White Paper Title Page 37 .pll? Are there custom folders? 3. How many attributes and qualifiers are passes per order line? Does the customer use linegroup level modifiers? When the linegroup based modifiers are set up.sql Describe the selectivity of the qualifiers on the price lists and modifiers.APPENDIX C If your performance issue(s) require development assistance.
do you use the profile option OM: Configuration Quick Save? If so. 6. provide percentage or timing improvement observed with each change. White Paper Title Page 38 . do you use complex rules? Are the rules changed frequently? How frequently are BOMs updated? Do you Oracle’s UI to create the orders? If so.g. do you import orders in both Booked and Entered status? Does pricing occur at the option class level? Does pricing occur at the option level? Are options selected with Configuration or with the Options window? If you use Configurator. how many? 5. provide % or timing improvement observed with each patch. Is this occurring? 4. Where available. e.Get_Custom_Price API should include caching whenever appropriate. Process/Setup Changes Implemented. Models and Configurations How many orders are being imported during the average import run? How many models are on the typical order? How many options and classes are in one model? Is the system checking for holds for options and option classes? Which types of models are used? ATO only? PTO only? Both? Does scheduling occur at the time of order import by passing the schedule ship date or ship set ID? How much time is taken for a typical run of order import with models? What is the Order Management Family Pack level? In one order import run. turned off pricing at booking or implemented streamlined workflow. What patches have you applied? If available.
506.7200 Web: www. Please report any errors herein to Oracle Corporation. Oracle Corporation does not provide any warranties covering and specifically disclaims any liability in connection with this document. Copyright © Oracle Corporation 2001 All Rights Reserved . All other names may be trademarks of their respective owners. Ahmed Alomari Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. Worldwide Inquiries: Phone: +1.oracle. CA 94065 U.A.S.650. Oracle is a registered trademark. and Oracle Order Management is a registered trademark(s) of Oracle corporation.650.com This document is provided for informational purposes only and the information herein is subject to change without notice. Venkatesh Malapati.506.Scalability in Order Management May 2005 Author: Manish Chavan and Linda Henry Contributing Authors: Nithya Lakshmanan.7000 Fax: +1.