Last updated on FEBRUARY 01, 2017
Applies to:Siebel Order Management - Version 188.8.131.52 SIA  and later
Information in this document applies to any platform.
The performance, measured as the time it takes after clicking ‘Done’ until the document is displayed, of synchronizing a complex product to the underlying document (Quote|Order|Agreement) can be improved by electing to bypass the final run of the Eligibility and Compatibility workflow. Removing this final call should be a decision made by the business. Typically, all business logic has already run prior to clicking the Done. The reason the final run of Eligibility and Compatibility is there OOTB is to assure nothing else has happened to the projected asset cache between the previous call (e.g. Selection of a Component) and the ‘Done’ click. As an example, a provision of the asset may have updated the structure while the user was configuring it and it was not present during the last click (AddItem) but is there now. The business must decide if this is a likely occurrence or an unlikely occurrence. If it is the latter then the following steps can be deployed to remove the call and improve performance.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms