Siebel Order Management Infrastructure Guide > PSP Engine > Configuring PSP Procedures >

Best Practices for Configuring PSP Procedures

To reduce the work of maintenance and to tune performance, follow these guidelines for designing PSP procedures:

  • Use the standard PSP procedures as your starting point. Trim and tune each PSP procedure to match your business requirements. PSP procedure execution is critical to the end-user response time of your Siebel application. Always review the standard, shipped PSP procedures and trim them as necessary, for example:
    • Eliminate steps that are not required in your implementation.
    • Eliminate variables from the default variable maps that are not required to support your business logic.

      NOTE:  These tuning guidelines can have a major impact on performance and scalability. For help with tuning, create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create an SR or get a status update on your SR. Support phone numbers are listed on My Oracle Support.

  • Add useful subprocedures. In every case for which the same set of steps is invoked from multiple places, consider creating a subprocedure for those steps. Then call the subprocedure rather than repeating the set of steps.
  • Remove unnecessary subprocedures. Avoid or remove subprocedures that are not required by your organization's particular needs. This is recommended because subprocedure calls involve copying the row set, which adds to performance overhead.
  • Keep the logic generic. Do not implement account-specific or product-specific logic in a PSP procedure. Because this logic changes frequently, it is best for it to be maintained by marketing administrators.
Siebel Order Management Infrastructure Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.