1. Log in under the Service Contracts Manager or Service Contracts User responsibility.
Navigate to Contract Administration, and then select Launchpad.
Select New from the Tools menu. The Create a New Contract window appears

2. Select a category using the list of values (LOV):
• If you are creating a contract with service agreements for individual items (covered products) in the customer's installed base, then select Warranty and Extended Warranty or Service Agreement. Warranty and Extended Warranty category does not permit you to add usage lines or to sell service to other levels of coverage (a party, site, or system).
• If you are creating a usage contract or a service agreement for levels other than items in the customer's install base (Products), then Service Agreement.
• If your contract includes subscriptions, then select Subscription Agreement. Subscription agreements permit you to enter subscriptions, service, and usage lines.

3.1 The application supplies a contract number for you automatically after you firstsave the contract, but you can instead enter a number of your own. The contract number can be a combination of any characters, but it must be unique.
3.2 Optionally, enter another short identifier in the Known As field to help you identify the contract later.
3.3 Specify the dates that the contract is effective by entering.
The dates that you enter here are automatically passes to each new line in the contract. The dates that individual lines are effective cannot fall outside this range; they cannot have a start date earlier than the contract start date or an end date later than the contract end date. If you enter dates that are outside this range in a contract line, then you must extend the contract dates accordingly for
your contract to pass Quality Assurance (QA).

4.1 You must enter an operating unit. From the Party region of the Parties subtab:
• Select Vendor Operating Unit from the Role LOV.
• Select an operating unit from the Name LOV.

4.2 Save the record.
You are now ready to enter the rest of the contract information that is required for your contract to become active:
• General contract information, including the vendor and customer, what quality check the contract must pass to become active, and how the contract will be renewed.

4.3 You can create different versions of the contract for your customer and at different price points and send them out for review.

5. Check to see whether you have entered all the required information in the contract or whether some external reason exists why the contract cannot be implemented, by
running the QA check.
Following are examples of issues that are tracked in the QA check:
• Failure to create a billing schedule for the customer.
• Failure to include an e-mail address for the customer contact.
• Absence of sales credits for contract lines.
• Customer credit on hold.

Your contract becomes active only after it passes the QA check list and obtains the approvals that are required by the Oracle Workflow process.