This chapter describes the process for setting pricing and billing features in Oracle Service Contracts.
This chapter covers the following topics:
You can set up multiple, ad hoc billing profiles in Oracle Service Contracts. Billing profiles include information about accounting and invoicing rules, type of billing, and its frequency. Invoices are generated according to the billing profile attributes.
You can create billing profiles for a specific customer, a specific customer bill to site, or a generic one for all customers and sites.
For more information see Creating Billing Profiles, Oracle Service Contracts User Guide.
The Service Contracts Main Billing process utilizes Invoice Level Loading, a parallel program to assign groups of invoices to different concurrent programs. The program first determines the count for all of the contract lines that qualify for the master request submission. If the count is greater than the threshold value (currently set to 500) the program splits up the master request into sub requests. There is no setup for this functionality other than to enable the profile option. For more details, see the OKS: Parallel Worker profile option.
Before sending billing transactions directly to Oracle Receivables, you can preview the invoice information to ensure accuracy. When initiating the billing process, you can set up the application to place the transactions into a separate set of Service Contracts tables. These tables mirror the billing transaction tables used during the normal billing process.
Guidelines:
If necessary, you can create a simple report to access the required information in these tables.
The tables used for Invoice Preview are:
oks_bcl_pr
oks_bsl_pr
oks_btn_pr
oks_bsd_pr
oks_btl_pr
The preview process runs in much the same way as the normal billing process. It includes only those contracts that meet the same criteria that must be included in the actual contract billing process. For example, status is eligible for invoicing, bill on date is due.
If potential billing errors are found during the preview, you can make adjustments manually in the appropriate application, for example, Oracle Service Contracts or Oracle Install Base, and re-run the pre-invoice report. This iterative process would continue until the pre-invoice process gives the expected results, at which point you may choose to run the actual billing process.
The billing process uses the latest data in calculating the invoices, so it should be recognized that the actual invoices created may be different from those included in the last pre-invoice process, if there is sufficient delay between running the process and the actual billing process. Changes can occur such as counters updated, contracts terminated, new products added to coverage, which affect the actual invoices created from the Contracts application.
The process includes the same information normally sent to Oracle Receivables during the actual billing process. Service Contracts sends either detailed or summary information to Oracle Receivables, depending on the value of the OKS: Summary Transactions profile option.
Transaction types define the accounting for the debit memos, charge backs, commitments, and invoices you create in Oracle Receivables. Transaction types also determine whether your transaction entries update your customer's balances and whether Oracle Receivables posts these transactions to your general ledger. To bill from Service Contracts, transaction types must be defined for invoices and credit memos.
Select the Receivables responsibility. Navigate to Setup, select Transactions, and then select Transaction Types.
Enter a transaction name: Invoice-OKS (this OKS transaction type is case sensitive and must be entered as: Invoice-OKS). Optionally, enter a description.
Select Invoice as transaction from the Class LOV.
Select the Open Receivable check box.
This updates your customer balances each time you create a complete debit memo, chargeback, or on–account credit with this transaction type. Oracle Receivables also includes these transactions in the standard aging and collection processes.
Select the Post To GL check box to allow posting to general ledger.
Choose a default Printing Option for transactions with this transaction type. Select Print or Do Not Print. You can override this value when entering transactions.
Choose a Transaction Status of Open, Closed, Pending, or Void. Use these statuses to implement your own invoice approval system.
Optionally, select the Allow Freight check box to allow freight to be entered for transactions with this transaction type.
Select the Tax Calculation check box to let Oracle Receivables calculate tax for transactions with this transaction type.
Choose a Creation Sign. If you are using the Cash Basis accounting method, your transaction's creation sign must be either Positive or Negative. You cannot update this field after you enter transactions with this type.
To restrict the direction in which items with this transaction type can be updated by applications entered against them, select the Natural Application Only check box. If you select this box, Oracle Receivables sets Allow Overapplication to No. You cannot update this option after you save this transaction type.
Optionally, select an Application Rule Set for this transaction type from the LOV. An Application Rule Set determines the default payment steps when you use the Applications window or AutoLockbox to apply receipts to transactions using this type. If you do not enter a rule set, Oracle Receivables uses the rule set in the System Options window as the default.
If you did not select the Natural Application Only check box, choose whether to Allow Overapplication against items with this transaction type by selecting or clearing this box. If you select this check box, Oracle Receivables sets Natural Application to No and you cannot update it after you save this transaction type. If you use the Cash Basis accounting method, the default value is No and you cannot change it.
Enter the Credit Memo Type to use when crediting items with this transaction type (optional). When you enter a credit memo against an invoice with this transaction type, the value you enter here is the default credit memo transaction type.
Enter the Receivable Account for transactions with this transaction type. Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the receivable accounts for transactions with these types. Oracle Receivables creates a transaction record using this account so you can transfer to your general ledger and create a journal entry if the Post To GL check box is selected for this transaction type.
Enter a Freight Account for transactions with this transaction type. Oracle Receivables uses this information, along with your AutoAccounting definition to determine the freight account for transactions with this transaction type. Oracle Receivables skips this field if the Allow Freight check box is not selected.
Enter a Revenue Account for transactions with this transaction type. Oracle Receivables skips this field if the Allow Freight is not selected. Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the revenue account for transactions with this transaction type.
Enter a Clearing Account for transactions with this transaction type. Oracle Receivables uses this account to hold any difference between the revenue amount specified for the Revenue Account and the selling price times the quantity for imported invoice lines. Oracle Receivables only uses the Clearing Account if you have enabled this feature for transaction sources that you use for your imported transactions.
Enter an Unbilled Receivable Account. When you use the Bill In Arrears invoicing rule, Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the Unbilled Receivable account for transactions with this transaction type.
Enter an Unearned Revenue Account. Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the unearned revenue account for transactions with this transaction type. Oracle Receivables only uses this account when your transaction's invoicing rule is Bill In Advance.
Enter a Tax Account. Oracle Receivables uses this information along with your AutoAccounting definition to determine the tax account for transactions with this transaction type.
Enter the range of dates that this transaction type will be active. The default Start Date is today's date, but you can change it. If you do not enter an End Date, this transaction type will be active indefinitely.
Save.
Select the Receivables responsibility. Navigate to Setup, select Transactions, and then select Transaction Types.
Enter a transaction name: Credit-OKS (this OKS transaction type is case sensitive and must be entered as: Credit-OKS). Optionally enter a description.
Select Credit Memo from the Class LOV.
Select the Open Receivable check box. This updates your customer balances each time you create a complete debit memo, chargeback, or on-account credit with this transaction type. Oracle Receivables also includes these transactions in the standard aging and collection processes.
Select the Post To GL check box to be able to post transactions with this type to your general ledger.
Choose a default Printing Option for transactions with this transaction type. Select Print or Do Not Print. You can override this value when entering transactions.
Choose a Transaction Status of Open, Closed, Pending, or Void. Use these statuses to implement your own invoice approval system.
Optionally, select the Allow Freight check box to allow freight to be entered for transactions with this transaction type
Optionally, select the Tax Calculation check box to let Oracle Receivables calculate tax for transactions with this transaction type.
Choose a Creation Sign. If you are using the Cash Basis accounting method, your transaction's creation sign must be either Positive or Negative. You cannot update this field after you enter transactions with this type.
If you want to restrict the direction in which items with this transaction type can be updated by applications entered against them, select the Natural Application Only check box. If you select this box, Oracle Receivables sets Allow Overapplication to No. You cannot update this option after you save this transaction type.
Enter an Application Rule Set for this transaction type or select one from the list of values (optional). An Application Rule Set determines the default payment steps when you use the Applications window or AutoLockbox to apply receipts to transactions using this type. If you do not enter a rule set, Oracle Receivables uses the rule set in the System Options window as the default.
If you did not select the Natural Application Only check box, choose whether to Allow Overapplication against items with this transaction type by selecting or clearing this box. If you select this check box, Oracle Receivables sets Natural Application to No and you cannot update it after you save this transaction type. If you use the Cash Basis accounting method, the default value is No and you cannot change it.
Enter the range of dates that this transaction type will be active. The default Start Date is today's date, but you can change it. If you do not enter an End Date, this transaction type will be active indefinitely.
Enter the Receivable Account for transactions with this transaction type. Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the receivable accounts for transactions with these types. Oracle Receivables creates a transaction record using this account so you can transfer to your general ledger and create a journal entry, if the Post To GL check box is selected for this transaction type.
Enter a Freight Account for transactions with this transaction type. Oracle Receivables uses this information, along with your AutoAccounting definition to determine the freight account for transactions with this transaction type. Oracle Receivables skips this field if the Allow Freight check box is not selected.
Enter a Revenue Account for transactions with this transaction type. Oracle Receivables skips this field if the Allow Freight is not selected. Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the revenue account for transactions with this transaction type.
Enter an Unbilled Receivable Account. When you use the Bill In Arrears invoicing rule, Oracle Receivables uses this information, along with your AutoAccounting definition, to determine the Unbilled Receivable account for transactions with this transaction type.
Enter an Unearned Revenue Account. Receivables uses this information, along with your AutoAccounting definition, to determine the unearned revenue account for transactions with this transaction type. Receivables only uses this account when your transaction's invoicing rule is Bill In Advance.
Enter a Tax Account. Receivables uses this information along with your AutoAccounting definition to determine the tax account for transactions with this transaction type.
Save.
Batch sources control the standard transaction type assigned to a transaction and determine whether Oracle Receivables automatically numbers your transactions and transaction batches. Active transaction batch sources appear as list of values choices in the Transactions, Transactions Summary, and Credit Transactions windows.
You can define two types of transaction batch sources:
Manual: Use manual batch sources with transactions that you enter manually in the Transaction and Transactions Summary windows.
Imported: Use imported batch sources to import transactions into Oracle Receivables using AutoInvoice. Batches are automatically numbered with the batch source name - request ID.
You can make a batch source inactive by clearing the Active check box and saving your work. Oracle Receivables does not display inactive transaction batch sources as list of values choices or let you assign them to your transactions.
Suggestion: If you have installed multiple organization support (multi–org), define an imported batch source with the same name in each organization These sources can have the same or different settings. This enables you to import order lines that belong to different organizations in Oracle Order Management into Oracle Receivables.
For more information on setting up transaction batch source, transaction types, refer Oracle Receivables User Guide.
Select the Receivables responsibility. Navigate to Setup: Transactions, and then select Sources.
Enter OKS_CONTRACTS as the name.
Select Imported as the type.
Select the Batch Source tab.
Enter a description.
Enter the range of effective dates for this source. The Start date is the current date, but you can change it. If you do not enter an end date, this transaction batch source will be active indefinitely.
Select the Automatic Transaction Numbering check box and enter a Last Number to automatically number new transactions you create using this source. You can use automatic transaction numbering with both Imported and Manual sources.
Optionally, select the Copy Document Number to Transaction Number check box to use the same value for both the document number and the transaction number for transactions assigned to this source.
Select Invoice-OKS as the Standard Transaction Type for this batch source. When you choose a batch source during transaction entry, this is the default transaction type. You can define new transaction types in the Transaction Types window.
Select the AutoInvoice Options tab.
Specify how AutoInvoice handles imported transactions that have Invalid Tax Rates. An invalid tax rate is one in which the imported transaction's tax rate does not match its tax code. Select Correct from the Invalid Tax Rate LOV, for AutoInvoice to automatically update the tax rate that you supplied to the one that you defined previously for the tax code. Select Reject if you want AutoInvoice to reject the transaction.
Specify how AutoInvoice handles imported transactions with Invalid Lines by selecting either Reject Invoice or Create Invoice from the Invalid Line LOV.
Specify how AutoInvoice handles imported transactions that have lines in the Interface Lines table that are in a closed period. To have AutoInvoice automatically adjust the GL dates to the first GL date of the next open or future enterable period, select Adjust from the GL Date in a Closed Period LOV. Alternatively, select Reject to reject these transactions.
Optionally, select a Grouping Rule to use for a transaction line from the Grouping LOV. If you do not enter a grouping rule, AutoInvoice uses the following hierarchy to determine which rule to use:
The grouping rule specified in the Transaction Sources window for the batch source of the transaction line.
The grouping rule specified in the Customer Profile Classes window for the bill–to customer and bill–to site of the transaction line.
The grouping rule specified in the Customer Profile Classes window for the bill–to customer of the transaction line.
The default grouping rule specified in the System Options window.
For AutoInvoice to require that the revenue amount for each transaction line is equal to the selling price times the quantity specified for that line, select the Create Clearing check box. Use this option to distribute revenue on a transaction in an amount that is not equal to the transaction line amount. If you select this check box, AutoInvoice puts any difference between the revenue amount and the selling price times the quantity for a transaction into the AutoInvoice Clearing account that you have defined. Otherwise, AutoInvoice requires that the revenue amount be equal to the selling price times the quantity for all of the transactions it is processing. Define your clearing account in the Automatic Accounting window.
Indicate whether sales credits can be entered for transactions using this source by selecting or clearing the Allow Sales Credit check box. This option and the Require Salesreps option in the System Options window determine whether sales credits are optional or required.
Select the Customer Information tab.
Select Id for each option to indicate that AutoInvoice validates your customer information for this batch source using an identifier. Choose Value if you use this source to import data from a non–Oracle system.
Select the Accounting Information tab.
Select Id to indicate how AutoInvoice validates your Invoice and Accounting Rule data for this batch source.
Select Id to indicate whether AutoInvoice validates the identifier for this batch source.
Select the Derive Date check box to derive the default rule start date and default GL date from the ship date, rule start date, order date and the default date that you supply when you submit AutoInvoice. If Oracle Inventory is installed, this must be selected.
Select Id to indicate that AutoInvoice validates your Payment Terms for this batch source using identifiers.
Select Percent to indicate that AutoInvoice validates your Revenue Account Allocation data for this batch source.
Select the Other Information tab.
Select Id to validate other data except for Agreement, Sales Territory, and Related Document.
Select the Sales Credit Validation tab.
Select Id for the first two options to validate information using identifiers for this batch source.
Select Percent to validate sales credits based on percent.
Save.
Transaction flexfields are descriptive flexfields that AutoInvoice uses to uniquely identify transaction lines. Oracle Receivables lets you determine how to build your transaction flexfield structure and what information you want to capture. To define the line-level Transaction Flexfield, query “Line transaction Flexfield” in the title field of the Descriptive Flexfield Segments window and enter the text and segments associated with this transaction flexfield.
The following table shows the values for the transaction flexfields.
| Column Name | Segment Name |
|---|---|
| INTERFACE_LINE_ATTRIBUTE1 | CONTRACT_NUMBER |
| INTERFACE_LINE_ATTRIBUTE2 | CONTRACT_MODIFIER |
| INTERFACE_LINE_ATTRIBUTE3 | INSTANCE_NO |
| INTERFACE_LINE_ATTRIBUTE4 | BILLED_FROM |
| INTERFACE_LINE_ATTRIBUTE5 | BILLED_TO |
| INTERFACE_LINE_ATTRIBUTE6 | AMOUNT |
| INTERFACE_LINE_ATTRIBUTE7 | BILLED_FROM_DATE |
| INTERFACE_LINE_ATTRIBUTE8 | START_DATE |
| INTERFACE_LINE_ATTRIBUTE9 | LINE_TYPE |
| INTERFACE_LINE_ATTRIBUTE10 | BILL_INSTALLMENT_NUMBER |
Select the System Administrator responsibility. Navigate to Application, and then select FlexField. Select Descriptive, and then select Segments.
Enter or query Oracle Receivables as the application and Line Transaction Flexfield for the title.
Clear the Freeze Flexfield Definition check box (otherwise you cannot create a new record).
Select OKS CONTRACTS in the Context Field Values region.
Click Segments to edit the definition.
Enter the values listed in the previous table.
Note: These must be entered in upper case.
Compile the flexfield by clicking Compile.
Select the Freeze Flexfield Definition check box to freeze the definition.
There are a number of setups you may perform related to pricing.
Adding Items to a Price List
For any items that you create, you must add them to a price list. See the Adding Items to a Price List procedure in the Oracle Advanced Pricing User's Guide.
Creating Price Breaks for Usage Items
You can set special price breaks for usage items.
See Creating Special Price Breaks, Oracle Service Contracts User Guide.
Setting Up Price Adjustments
You can adjust prices of service, subscription, and usage lines in your contract by applying adjustments set up by the application administrator. See Entering Price Adjustments, Oracle Service Contracts User Guide and Getting Help in Picking Adjustments, Oracle Service Contracts User Guide.
You can set up multi-currency price lists. For example, a customer that operates in 40 countries may want three price lists, each with a different currency. Rather than administering 120 price lists (three price lists in each currency), multi-currency price lists allow the customer to maintain three price lists that handle all of the currency conversions.
Prerequisite:
Set up multi-currency price lists as specified in the Multi-Currency Conversion Lists chapter of the Oracle Advanced Pricing User's Guide.
Set the system profile QP:Multi Currency Installed to Yes.
Run the concurrent program Update Price Lists with Multi-Currency Conversion Criteria.
Set the system profile QP: Multi Currency Usage to Yes at Application Level.
If the currency on the contract is changed, conversion rate used to calculate price is based on the date that is specified in the OKS: Default Pricing Date profile option, but not the date that is entered in the Pricing/Billing tab. Based on the value, this profile option identifies a conversion entry in the currency daily rates window, which references the From and To currencies that are specified in the Pricing /Billing tab.
Note: After you run the concurrent program, you cannot revert your price lists back to single-currency price lists. Oracle does not support changing the profile QP: Multi Currency Installed back to No.
To price a contract on a multiple currency price list, the transactional or functional currency must be either the same as the price list base currency or must be specified on the conversion list attached to the price list.
Oracle Service Contracts integrates with Oracle Advanced Pricing to price services. A Service Contracts request type is seeded in Advanced Pricing to allow Service Contracts to leverage Attribute Management capabilities in Advanced Pricing. See the Oracle Advanced Pricing User's Guide for more information on Attribute Management). You can map pricing attributes and qualifiers to the Service Contracts request type in Advanced Pricing. After you complete the mapping, pricing calls from Service Contracts can automatically source the attributes that are used for determining price. For instance, a service provider that employs a price list with special pricing for the company's top five customers can now automatically pass the customer name from Service Contracts to Advanced Pricing as a pricing qualifier.
Select the Pricing Manager responsibility. Navigate to Setup, and then select Attribute Management. Select Pricing Transactions Entity Associations.
The Pricing Transaction Entity window appears.
Select ORDFUL from the Name LOV.
Confirm that the Enabled check box associated with OKS is selected.
Save and close.
Navigate to Setup, select Attribute Management, and then Context and Attributes.
The Context Setup window appears.
Query for CUSTOMER in Code field.
Verify that PARTY_ID code is available and enabled.
Save and close.
Navigate to Setup, select Attribute Management and then Attribute Linking and Mapping.
The Pricing Transaction - Attribute Linking window appears.
Select Order Fulfillment (ORDFUL) from the Pricing Transaction Entity LOV.
Select Qualifier Context from the Context Type LOV.
Highlight CUSTOMER in the Code field.
Click Link Attributes.
Highlight Party ID in the Code field.
Click Attribute Mapping.
In Application Name field, select Service Contracts.
In User Source Type field, select PL/SQL API.
In User Value String, enter OKS_QPATTRIB_PVT.G_CONTRACT_HDRREC.PARTY_ID for Header and OKS_QPATTRIB_PVT.G_CONTRACT_LINREC.PARTY_ID for Line.
Save and close.
After creating pricing qualifiers and attributes you must run the Build Attribute Mapping Rules concurrent program to ensure that the pricing engine uses only the qualifier and pricing attributes used in the price lists, modifiers, and formulas that are relevant to each call, rather than all attribute mapping rules.
You can run this program using the Oracle Pricing Manager responsibility.
For information see the Oracle Advanced Pricing User's Guide.
You can set up sales territories using Oracle Territory Manager to automatically:
Assign sales agents as vendor contacts to new contracts created from Oracle Order Management orders.
You can use sales territories to assign sales agents to a contract. This is useful if your company uses different organizations for selling and renewing service contracts.
Assign new sales agents to contracts after personnel changes and reorganizations.
For contracts in the active, signed, and hold statuses, there is a concurrent program that makes the new sales agent assignments and end-dates any existing sales agents in the contract. For contracts in the entered status, the concurrent program simply replaces the existing sales agents with those derived from the territories.
When the application cannot assign a resource from the territory, for example for new or dormant customers that have no territories set up for them, the application looks for the individual to notify in OKS: Contract Administrator and, if none is set, then in OKC: Contract Approver
Prerequisite:
Set up sales territories for Oracle Service Contracts as described in the Oracle Territory Manager Implementation Guide. Use the following guidelines during your setup:
Select the CRM Administrator responsibility. Navigate to Territory Manager, and then select Territory Administration.
Enable Oracle Service Contracts qualifiers:
Choose Setup Qualifiers from the Administration menu.
Choose Oracle Service Contracts from the Usage LOV.
Click Find.
The application displays the list of qualifiers available for use in Oracle Service Contracts:
Country
Customer Name
Customer Range
State
Select the respective Enabled check box to enable each qualifier.
Click Update Qualifiers.
Close the window.
Navigate to the Oracle Service Contracts folder in the territory manager Navigator and create your territories. For each territory:
From the Overview tab, choose Contract Renewal as the Transaction Type.
From the Transaction Qualifiers tab, choose the qualifiers using the Name LOV.
Enter the qualifier values for the territory.
From the Resources Tab, choose the resource using the Name LOV. Enter the name of one resource.
Run the concurrent program Generate Territory Packages with the following parameters:
Usage: Oracle Service Contracts
Transaction Type: Contract Renewal
To have the application use the sales territories to automatically assign a resource as a vendor contact in contracts created through Oracle Order Management orders:
Set the system profile OKS: Territory Sales Person for First Year Contracts to Derive at the site level. (By default this system profile is set to Retain, causing the application to copy the sales person on the order to be the vendor contact or type Salesperson on the contract).
Confirm the following system profiles are set to the resource to notify if the application cannot assign a sales person to the contract based on the territory setup.
In this case, the following hierarchy is used to send the notification when the application cannot assign a resource from the territory:
OKS: Contract Administrator
OKC: Contract Approver
To reassign sales agents to contracts based on the sales territories, for example, as a result of personnel changes or reorganizations, run the concurrent program Service Contracts Concurrent Program for Reassigning Resources. The profile option value of OKS: Use Territories to Default Sales Person should be set to Yes either at the user level or site level.
This program reassigns sales agents to in Entered, Active, Signed and Hold statuses. For contracts in the Entered status, the application replaces all vendor contacts of role Salesperson with the resource supplied by the territory. For contracts in the Active, Signed, and Hold statuses, the application end-dates (system date -1) the current vendor contact(s) of role Salesperson and appends the resource supplied by the territory. The application sets the new sales person's start date to the system date. You can restrict the scope of the concurrent program's assignment by entering any of the following parameters:
Contract Number
Contract Status
Organization
Sales Person (sales person within that organization)
Note: If you do not enter any of these parameters, the program reassigns sales agents to all contracts.
The procedures for executing service contract billing involve the following concurrent requests:
Service Contracts Main Billing: According to pricing and billing schedule in the contract, running this request generates transactions in the Service Contracts billing tables and the Oracle Receivables interface table.
Autoinvoice Import Program: Running this request picks records from the Oracle Receivables interface table and process billing.
Service Contracts Fetch Receivables Info for Billing: Running this request fetches the invoice number and tax from Oracle Receivables and updates the contract billing history.
These processes should be set to run on a periodic basis, the frequency of which is dependent on your billing policy. You may find it useful to run these requests as a request set. You may also consider running the QA process within this set to ensure that information in the contract is still accurate prior to running the billing process. See Executing Billing Through Concurrent Programs, Oracle Service Contracts User Guide.
When you enter a credit card within the Oracle Service Contracts Authoring form, the application integrates with Oracle Payment to verify credit card details, such as the validity of the card number and the security code. It also determines if the card appears masked within the application, for example, 4444XXXXXXXXXXXX.
Verify the following setups for integration with Oracle Payment:
Verify Oracle Payment setups for masking credit card numbers. Masking determines how entered credit cards appear within the application, for example, 4444XXXXXXXXXXXX or 4444000012345678.
Verify Oracle Payment setups for security codes. You can require security codes for new credit cards.
For more information on setting up masking and security features in Oracle Payment, see the Oracle Payment Implementation Guide.
You can define how the application calculates partial periods for pricing, billing and termination amounts. A partial period is any billing period or service effective duration that is not in multiples of Billing/Pricing Period unit of measure (UOM). For information on setting up partial period attributes within the Global Contracts Defaults, see Entering Contract Defaults, Oracle Service Contracts User Guide.