A rule group is a collection of one or many rules while Rules collect one or many related pieces of information. Rules can be grouped so that rules with similar characteristics can be easily referenced and accessed. For example, you can create a rule group for billing that would group together rules for bill to address, billing schedule, and payment terms.

A rule group must be defined as a lookup (OKC_RULE_GROUP_DEF). You can create your own Rule Groups, but you are not supposed to create new Rules. Only Seeded Rules are supported by Oracle. To Assign Rules to Rule Groups, navigate to Service Contracts Manager Responsibility & go to Setup > Contract > Rules >

Define Rule Groups.

When you select a rule group in your contract, all rules of that group are automatically copied into your contract. Each rule may be optional or mandatory.

To access a rule from the authoring window, you must include the rule group in the category definition. You can include more than one rule group to a category.

Following is the list of Commonly Used Rules:

Rule Information Category	Rule Type Meaning	Description	JTF Object Code
…STO	Ship To Address		OKX_SHIPTO
…BTO	Bill To Address		OKX_BILLTO
…CAN	Customer Account	Service, also used by Master Sales Agreements	OKX_CUSTACCT
…ARL	Accounting Rule	Receivables, Invoice Accounting Rule	OKX_ACCTRULE
…PRE	Price	Used in the context of Price List, Modifier List, Discount List	OKX_PRICE
…IRE	Invoice Rule	Receivables, Invoice Rule, may also record invoice terms for buy contract	OKX_INVRULE
…QRE	Quantity Rate	Service only: Usage billing. Users optionally control contract billing
…SBG	Service Bill Schedule	Service only
…SLH	Stream Level Header	Stream Level Header	OKS_STRM_TYPE
…SLL	Stream Level Lines	Stream Level Lines	OKS_TUOM

To Attach a Rule Group to a Contract Category Go to Service Contracts Manager Responsibility and go to Setup > Contract > Define Categories



<<Click to view large image>>


Find All Rules for a line:

SELECT *
FROM OKC_RULES_V
WHERE RGP_ID = (SELECT ID
FROM OKC_RULE_GROUPS_V
WHERE CLE_ID = :CONTRACT_LINE_ID)

Create a single invoice for usage & service lines in contract with different invoicing rules for usage and service lines

Take an example of contracts with service and usage lines. We want to bill customer in advance for service & on actual usage for usage lines at the end of the month (i.e. Arrears invoicing rule). 

When such contract is billed with "Service Contracts Main Billing" Program, it creates two different invoices, one for service lines & one for usage lines as usage & services lines have different invoicing rules & one invoice can only have one invoicing rule.

Now, as we want to send customer only one invoice for this contract, we need to consolidate or group this two invoices into one invoice.

As the intention is to group some invoices, the imported billing feature of receivables can be used. Use following procedure to group the invoices:-

1.     Run "Service Contracts Main Billing" Program.

2.     Once above program is over, data will be populated in the RA_INTERFACE_LINES_ALL tables.

3.     For the contract number, populate "cons_billing_number" column in this interface table.

4.     Run "Auto Invoice" program.

5.     Auto Invoice Program will populate data in following tables:

     a.  ar_cons_inv_al………….This is header table which stores the Cons_Billing_Number.

     b.  ar_cons_inv_trx_all……This is lines table and it provides information about all the transactions

……………………………………………..assigned to one billing number.

6.     Create a customized invoice print program.

Note: All transactions belonging to one bill number can be easily extracted with the help of these tables for printing.

Please take note of following before using imported billing functionality:

In order to use this feature, in the Customer Profiles the Consolidated Billing Formats should be enabled and type should be selected as Imported and when the data comes to RA Interface table, populate the cons_billing_number and run the Auto Invoice Program. The Transactions belonging to the same bill to site can share a same billing number; else the Auto invoice program will reject all the records populated with same Cons_Billing _Number. Transactions belonging to different bill to sites cannot be clubbed under one Cons_Billing_Number.

The Lockbox program is currently not able to handle the Consolidated billing efficiently, the customer cannot pay for one Consolidated billing invoice number, he has to pay amount due for all CBI numbers and in case if he the amount paid by customer is less than the sum of all overdue Consolidated billing invoices, then the receipt will be imported as unapplied receipt and application should be done manually. (There is an enhancement request raised from other customers to allow lockbox to apply receipts to invoices grouped by Consolidated billing number).

To solve the above lockbox issue, we can derive related invoices on the basis of consolidated invoice number given by bank & application can be done based on this invoices.

The Transaction form will show the billing number in Transactions and Receipts, if Show Billing number is checked in System options setup.

Profile Option Name	Description
OKC: View Contracts By Organization	By setting this profile option to Yes, users would only have visibility to contracts that are authored in the operating unit that is associated to their responsibility.
OKS: Contact Center Date Range	Use this profile option to set the date range for the Contract Details tab of the Contact Center.
OKS: Intangible Subscription Method	Determines the pricing method for Intangible Subscription items. Pricing method can be set to Effectivity based or Subscription based.
OKS: Transfer Party Relationship	This profile option is used to specify the relationship that would identify related parties during the transfer management process. If this relationship does not exist between the parties, the parties are considered unrelated.
OKS: Update Contract with Install Base Quantity	Determines if the contract covered product quantity is updated as a result of the update to item instance quantity in Oracle Install Base.
OKS: Warranty Consolidation	Determines whether warranties associated with goods sold can be consolidated into a single warranty contract or whether individual warranties need to be created.
OKS: Full Credit for Product Return	Determines if either a full or partial credit is issued, if a sub line is terminated as a result of a customer product return.
OKS: Transfer Status	Used to specify the default contract status for the new contract(s) after a covered product or system is transferred.

Following is the list of frequently used Service Contract Profile Options

OKC: View Contracts By Organization

OKS: Contact Center Date Range

OKS: Intangible Subscription Method

OKS: Transfer Party Relationship

OKS: Update Contract with Install Base Quantity

OKS: Warranty Consolidation

OKS: Full Credit for Product Return

OKS: Transfer Status

OKS: Credit Card Display Privileges

OKS: Intangible Subscription Pricing Method

OKS: Minimum Service Duration

OKS: Reprice Warning Message

OKS: Enable Negative Invoicing

OKS: Usage Billing Calculation

OKS: Payment Method for AR Interface

OKS: Default Order Type for Subscriptions

OKS: Category for Order Management Originated Contracts

OKS: Raise Credit Memo for Install Base Transactions

OKS: Notify User of Install Base Integration Notifications

OKS: Vendor Contact Role

OKS: Credit Card Validation Level

OKS: Credit Card Minimum Authorized Amount

OKS: Use Advanced Pricing for Manual Adjustment

OKS: Notify Contract Administrator

OKS: Notify Sales Administrator

OKS: Revenue Type for Sales Credits

OKS: Revenue Type Distribution for Sales Credit

OKS: Default Sales Person for Renewal

OKS: Use Territories to Default Sales Person

OKS: Wallet Path

If you want your users to be able to view output of reports submitted by other users, you can set following profile option at site level:

Concurrent:Report Access Level

Set the above profile to "Responsibility" When this profile is set to " Responsibility " it enables all the users (having access to the responsibility from which user submitted Program) to view the output of the program.

If above profile is set to User (Default), then only the user who has submitted the request can view the output of the submitted program.

<<Click the view image in large size>>

When you create a responsibility, you assign a profile option called MO:Operating Unit to the responsibility. This operating unit is the organization that you will be working in. When any user logged into this responsibility that user will be working only within this organization. Anything that is run concurrently, only looks at that organization.

To assign an org_id to a responsibility, log into System administrator or Application Developer responsibility, goto profile option & search by that responsibility name. Look for profile option MO: Operating Unit and assign desired organization to this profile.

Org_id in Apps Tables

All tables that end with _ALL have an org_id column. This denotes what org_id that data is related to. If the table does not have an org_id column then the data is available in all organizations.