Oracle Service Contracts provides a complete contract authoring execution solution to manage warranties, extended warranties, usage, and subscription services, as well as complex service agreements. With Oracle Service Contracts you can:
A contract in Oracle Service Contracts comprises:
The header is where you enter a brief description and specify the contract duration. You can default values from the header of a contract down to the lines and, if applicable, to sublines as well.
The header level is composed of the fields at the top of the Service Contracts Authoring form as well as the Summary tab. The Summary tab also includes several secondary tabs. The following list briefly describes these pages:
Lines list the individual service, usage, and subscription items that are included in the contract. A single contract can have multiple lines.
Each line inherits certain information from the contract header such as effectivity dates, bill to and ship to information, and billing rules and schedules. These can be changed as appropriate to allow the contract to conform to the customer requirements. A contract line may be related to one or more sublines.
Three line types are available:
The Lines tab includes several secondary tabs, which include:
Sublines specify what the service covers or the counters where the usage is tracked. You can access this information from the Pricing/Products subtab of the Lines tab.
The following list describes how each line type uses sublines:
Oracle Service Contracts enables you to manage the entire contract life cycle, including contract creation, renewal, and termination. For detailed information refer to the following procedures:
You can create a contract manually. In addition, a contract can be created automatically through Oracle Order Management or by creating a product that has a warranty in Oracle Installed Base. See About Ordering Service in Oracle Order Management.
You can author service contracts in multiple operating units without changing responsibility. You must select an operating unit for each contract.
Note: This procedure covers how to create a contract by navigating from the Launchpad. You can also open the Service Contracts Authoring form from the Administrator Workbench. For more information about the Administrator Workbench, see Overview of the Administrator Workbench.
Your contract becomes active only after it passes the QA check list and obtains the approvals that are required by the Oracle Workflow process.
Note: The application uses a common workflow for new and renewed contracts. Each new contract, whether a renewal or new, initiates a workflow process. See Overview of Managing Contract Negotiation.
The standard contract approval workflow integrates with Oracle Approval Management Engine (AME). Standard AME features support rules based approval routing and definition of approval groups. Key attributes have been seeded in AME for approval setup, such as Contract ID, Operating Unit, Customer Party, Contract Category, and Contract Amount.
Your administrator can define additional attributes through AME. For more information see the Oracle Service Contracts Implementation Guide.
You can copy information from an existing contract into a new contract, an existing contract, or to a new modifier of the existing contract.
Note: For existing contracts, you cannot copy the components of a contract across categories. For example, you cannot copy the components from a Warranty into a Service Agreement.
You can copy from Contract Navigator as well as the results table in the Search Templates and Contracts window. In this case, you select the Source Contract and then search for a target contract to which you can copy the information.
You can also initiate copy from within the contract itself. In this case, the selected contract is the target contract and you search for a source contract from which you intend to copy components. You will typically use this method to copy service lines and covered level into the contract you have open.
A template makes it possible for you to speed up the contract creation process by filling in frequently used values.
Prerequisite
Display a contract.
You can import contracts from legacy or external systems by running the Service Contracts Import concurrent program.
Service Contracts provides an open interface that allows bulk import of standard warranties, extended warranties, service contracts and intangible subscription contracts.
Using this concurrent program, you can perform the following tasks:
After you successfully import contracts, you can purge the records from the interface tables by running the Service Contracts Import Purge concurrent program.
For more information on the concurrent programs, log in to the application using the Integrated SOA Gateway responsibility. Access the Integration Repository and navigate to Service Contracts in the Contracts Suite.