Usage base service providing to the product, Usage means
we can provide the service to the product on the basis of
USE(counters) and Durations(time) wise, this need to be
define in service contracts how the product get service on
eligible business process(customer support/Field
service/Depot repair) with charges or with out charges .
A contract can ahve multiple lines and the line number will
differentiate between one line to another. Sb-line number
is also dependent on line number e.g. if we have line
number as 1,2 then the sub-line number for line 1 will be
1.1, 1.2,1.3 etc.
This is 3rd Phase of service contracts and their components
as follows in R12
The Default Line Types in Service Contracts are:
a) Service Agreement:
b) Warranty and Extended Warranty
1. Extended Warranty
c) Subscription Agreement
Oracle Service Contracts can be used to sell subscriptions
for both tangible(collateral, or any other physical
item that can be shipped through OM) and intangible items(
collateral that is sent through e-mail).
The header level information for contract is captured at
top of the contract form and in summary tab. The summary
tab includes information in various sub-tabs like parties,
pricing/billing, renewal, administartion, security/text.
The line tab line tab captures the line level information
for individual service,usage and subscription items. Line
tab will have multiple sub-tabs acounts, effectivities,
pricing/products, exemption/payment options, counters,
The summary tab and line tab is required for any service
They count the usage of product.this is recorded using
counters devices/mechanism that measure usage such as
number of phone calls made, no of copiers etc.
Contracts are needed to be grouped because the renewals,terminations ,extensions of the Contracts can be done easily based on their groups.
The Contract be assigned to a particular group while authoring the Contract in the Summary--->Administration Tab.
And also we can change the Contracts to another groups from the Contract Navigator.
Bill to is required because this is the address which is
paying for our bills. Ship to is also required because if
we have tos end any material then to which address it
should be sent to.
QA Checklist is required to check that the contract is
created with all the necessary information.
the checklist checks and validates the contract before the
contract can become active
What all it is checking is a huge list.
Pl. check profile OKS: Default QA checklist
You can find termination and dues information
Administartion subtab of Summary tab.
Setup --> Contract --> Categories & Sources --> Line Types
Sections are used while defining contract terms. Sections
are headings under which we organize contract clauses. We
can define sectons that can be used in defining templates
Oracle Service Contract leverages Oracle workflow to
automate the contract approval process. After authoring the
contract one can send it for approval and obtain signature
To change version
contracts authoring-> Tools menu->create new version
contracts can be versioned to maintain the updates and
Updates can be versioned with change in minor version.
and creating a new version option changes the major version
of the contracts
Autonumbering functionality will automatically create
contract number after creation of the contract. It provides
flexibility in definining how contracts are numbered.
One can manually override the system generated number,
assuming the allow manual checkbox is selected during setup.
If you are talking about oracle apps service contract, the
service contract can be created by using OKS APIs.
If you have template then you can populate the inventory
ids diectly from service contract base tables or else you
have to use Inventory and order management tables.
query up the service contract on the launch pad, right click
and select "Terminate"