This chapter covers the following topics:
Oracle Project Contracts enables you to define holds at different levels (header, line, deliverable) with different hold reasons, to analyze holds and the promptness of their resolution, and to track release due dates and reasons. Hold management is workflow-based to allow modeling of business processes for different hold reasons.
For details on setting up Hold Management in Oracle Project Contracts, see: Setting Up.
Hold statuses can be used to describe a contract hold during its life cycle, and can also be used to handle hold escalations.
You can associate a workflow process to each hold status. This workflow process will be initiated when a contract hold is set to the corresponding status. You can use the workflow processes to generate notifications to inform the appropriate parties regarding the extents and the contexts of the contract hold.
Default workflow processes are provided when the product is installed. You can tailor the default workflow processes to fit your business needs. We recommend that you use the default workflow processes as a basis for copying into new workflow processes instead of modifying the default workflow processes directly.
Hold types and apply/remove hold reasons can be used to route different processing logic when customizing the workflow processes. For example, a customer initiated hold request may be subject to a more thorough approval process then an internal initiated hold request. You can use a different hold type to denote the source of the hold request.
To use hold types and hold reasons to fine-tune your workflow processes, we recommend that you define custom workflow lookup types to mirror the hold type and hold reason lookup values.