DBA Data[Home] [Help] [Dependency Information]


TABLE: OKC.OKC_RG_DEF_RULES

Object Details
Object Name: OKC_RG_DEF_RULES
Object Type: TABLE
Owner: OKC
FND Design Data: TableOKC.OKC_RG_DEF_RULES
Subobject Name:
Status: VALID


Oracle Contracts holds meta-data about RULES and RULE GROUPS and how they may be used.
The rule "types" are called RULE DEFINITIONS and are stored in FND_LOOKUPS. The rule group types are called RULE GROUP DEFINITIONS and are also stored in FND_LOOKUPS.
A rule may be used in more than one rule group. It may be mandatory in one rule group and optional in another. OKC_RG_DEF_RULES defines what rule definitions are associated with what rule group definitions and the optionality of that association. This is meta-data, it defines what rules are allowed to be included in a rule group.
For example, the rule definition "Payment Term" may be included in the rule group definitions "Billing" and "Payment", and be optional in both.


Storage Details
Tablespace: TablespaceAPPS_TS_SEED
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
OKC_RG_DEF_RULES_U1 NORMAL UNIQUE TablespaceAPPS_TS_SEED ColumnRGD_CODE
ColumnRDF_CODE
Columns
Name Datatype Length Mandatory Comments
RGD_CODE VARCHAR2 (30) Yes Rule groups code.
RDF_CODE VARCHAR2 (30) Yes Foreign key to FND_LOOKUP_VALUES.
OBJECT_VERSION_NUMBER NUMBER (9) Yes Sequential number set at 1 on insert and incremented on update. Used by APIs to ensure current record is passed.
CREATED_BY NUMBER (15) Yes Standard Who column.
CREATION_DATE DATE
Yes Standard Who column.
LAST_UPDATED_BY NUMBER (15) Yes Standard Who column.
LAST_UPDATE_DATE DATE
Yes Standard Who column.
OPTIONAL_YN VARCHAR2 (3)
Indicates if the rule is optional.
LAST_UPDATE_LOGIN NUMBER (15)
Standard Who column.
SECURITY_GROUP_ID NUMBER

Used in hosted environments
APPLICATION_ID NUMBER

Application Identifier
MIN_CARDINALITY NUMBER (9)
This is the minimum occurrence of instances of a rule within a rule group
MAX_CARDINALITY NUMBER (9)
This is the maximum occurrence of instances of a rule within a rule group
PRICING_RELATED_YN VARCHAR2 (3)
Indicates whether the Rule can be an attribute used to determine the price in a Contract. For example, the price of a line can be based on a Ship To location defined using a Rule while a Notification Rule may not be used for this purpose.
ACCESS_LEVEL VARCHAR2 (1)
Indicates the protection level for the record.
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT RGD_CODE
,      RDF_CODE
,      OBJECT_VERSION_NUMBER
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      OPTIONAL_YN
,      LAST_UPDATE_LOGIN
,      SECURITY_GROUP_ID
,      APPLICATION_ID
,      MIN_CARDINALITY
,      MAX_CARDINALITY
,      PRICING_RELATED_YN
,      ACCESS_LEVEL
FROM OKC.OKC_RG_DEF_RULES;

Dependencies

[top of page]

OKC.OKC_RG_DEF_RULES does not reference any database object

OKC.OKC_RG_DEF_RULES is referenced by following:

SchemaAPPS
SynonymOKC_RG_DEF_RULES