[Home] [Help]
[Dependency Information]
Object Name: | IBE_CT_RELATION_RULES |
---|---|
Object Type: | TABLE |
Owner: | IBE |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
IBE_CT_RELATION_RULES contains information about the rules that define relationships. The information about the relationship types is stored in FND_LOOKUPS view with lookup type of 'IBE_RELATIONSHIP_TYPES'. There are two types of relationship rules: mapping and SQL rule. Any relationship type can have either multiple mapping rules or one SQL rule but not both of them.
The mapping rules define relationships in a from-to form. The type of from and to objects can be Categories, Sections or Items. The relationships generated by mapping rules are preevaluated and stored in IBE_CT_RELATED_ITEMS table. When a mapping rule is added and deleted, corresponding item level relationships will be added and deleted in IBE_CT_RELATED_ITEMS table. For example, when we add a rule 'Section A is related to Category B' for the relationship type 'SERVICE', IBE_CT_RELATED_ITEMS table is added with new rows where the inventory_item_id column has item ID of products in Section A, and related_item_id has item ID of products in Category B.
A relationship type can have a SQL rule instead of mapping rules, which will be executed at run time to get the actual item level relationships. The SQL queries can have up to 10 bind variables and unlike the mapping rules the SQL rules are not preevaluated. These SQL queries are executed in the runtime using input parameters.
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
IBE_CT_RELATION_RULES_U1 | NORMAL | UNIQUE |
![]() |
![]() |
IBE_CT_RELATION_RULES_U2 | NORMAL | UNIQUE |
![]() |
![]() ![]() ![]() ![]() ![]() |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
RELATION_RULE_ID | NUMBER | (15) | Yes | Relation Rule (Definition) identifier |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Object version number for locking | |
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 | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
RELATION_TYPE_CODE | VARCHAR2 | (30) | Yes | Relation type code |
DESCRIPTION | VARCHAR2 | (240) | Relation Description | |
ORIGIN_OBJECT_TYPE | VARCHAR2 | (30) | Yes | Origin object type code (I, C, S, or N) |
DEST_OBJECT_TYPE | VARCHAR2 | (30) | Yes | Destination object type code (I, C, S, or N) |
ORIGIN_OBJECT_ID | NUMBER | Origin object identifier | ||
DEST_OBJECT_ID | NUMBER | Destination object identifier | ||
SQL_STATEMENT | VARCHAR2 | (2000) | Manual SQL statement that defines the relationship | |
ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | Descriptive Flexfield structure defining column | |
ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment column | |
SECURITY_GROUP_ID | VARCHAR2 | (240) | Security Group Identifier. |
Cut, paste (and edit) the following text to query this object:
SELECT RELATION_RULE_ID
, OBJECT_VERSION_NUMBER
, CREATED_BY
, CREATION_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
, RELATION_TYPE_CODE
, DESCRIPTION
, ORIGIN_OBJECT_TYPE
, DEST_OBJECT_TYPE
, ORIGIN_OBJECT_ID
, DEST_OBJECT_ID
, SQL_STATEMENT
, ATTRIBUTE_CATEGORY
, ATTRIBUTE1
, ATTRIBUTE2
, ATTRIBUTE3
, ATTRIBUTE4
, ATTRIBUTE5
, ATTRIBUTE6
, ATTRIBUTE7
, ATTRIBUTE8
, ATTRIBUTE9
, ATTRIBUTE10
, ATTRIBUTE11
, ATTRIBUTE12
, ATTRIBUTE13
, ATTRIBUTE14
, ATTRIBUTE15
, SECURITY_GROUP_ID
FROM IBE.IBE_CT_RELATION_RULES;
IBE.IBE_CT_RELATION_RULES does not reference any database object
IBE.IBE_CT_RELATION_RULES is referenced by following:
|
|
|