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