Contract Rule Groups and Contract Rules

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.

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

Oracle Receivable Contacts Query

SELECT DISTINCT

  (rc.first_name||' '||rc.last_name) name,

  rc.title            ,

  DECODE(HCP.PHONE_LINE_TYPE,'GEN',HCP.PHONE_AREA_CODE ||'-' ||HCP.PHONE_NUMBER,NULL) "tel_number",

  hcp.phone_extension "Extension"      ,

  DECODE(HCP.PHONE_LINE_TYPE,'FAX',HCP.PHONE_AREA_CODE||HCP.PHONE_NUMBER,NULL) FAX_NUMBER ,

  rc.email_address                    ,

  hca.account_number "Legacy customer",

FROM hz_parties hp          ,

  ra_contacts rc               ,

  hz_cust_site_uses_all hcsu   ,

  hz_cust_acct_sites_all hcas  ,

  hz_party_sites hps           ,

  HZ_CUST_ACCOUNTS hca         ,

  hz_party_relationships hprel ,

  HZ_CONTACT_POINTS HCP

WHERE 1 = 1

   AND hcsu.cust_acct_site_id        =hcas.cust_Acct_Site_id

   AND hcas.party_site_id            =hps.party_site_id

   AND rc.contact_id                 =hcSU.CONTACT_ID

   AND rc.party_relationship_id      = hprel.party_relationship_id

   AND hprel.party_id                = hcp.owner_table_id

   AND hprel.party_relationship_type = 'CONTACT_OF'

   AND rc.status                     = 'A'

   AND hcp.status                    = 'A'

   AND hcp.contact_point_type        ='PHONE'

   AND hp.party_id                   =hps.party_id

   AND HCA.CUST_ACCOUNT_ID           =HCAS.CUST_ACCOUNT_ID

   AND hcsu.site_use_code            ='SHIP_TO'

   AND HCSU.STATUS                   = 'A'

   AND hcas.org_id                   =736;

   --AND hcas.org_id =457;