Results for “orig_system_reference_code”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IBC_CONTENT_ITEMS is the master (header) table for Oracle EBS Content Manager (IBC), the module that manages reusable content and collateral used across marketing, proposals, and web placement. As its documented description states, it stores non-version and non-language-specific information about content items — that is, the identity, classification, ownership, and lifecycle status that remain constant across all versions and translations of a given item. Version-specific and language-specific attributes are held in the companion tables IBC_CITEM_VERSIONS_B and IBC_CITEM_VERSION_LABELS, both of which carry a CONTENT_ITEM_ID foreign key back to this table.
Its heuristic Data Vault classification is hub. In modeling terms, IBC_CONTENT_ITEMS corresponds to a hub: a single row per business entity (the content item) carrying its durable business key, while attributes that change over time — versions, labels, and relationships — are modeled as satellites and links in surrounding tables.
Key Information Stored
The table is defined in the IBC schema with 29 documented columns. The most significant are:
- CONTENT_ITEM_ID — the surrogate primary key, enforced by IBC_CONTENT_ITEMS_PK; it is the join column to every dependent table.
- ITEM_REFERENCE_CODE — the business-key candidate, enforced by unique index IBC_CONTENT_ITEMS_UK. A second unique index, IBC_CONTENT_ITEMS_U1, combines CONTENT_ITEM_ID and ZD_EDITION_NAME, which supports multi-edition deployments.
- CONTENT_TYPE_CODE — classifies the item; foreign key to IBC_CONTENT_TYPES_B.
- DIRECTORY_NODE_ID — the folder or node in which the item resides; foreign key to IBC_DIRECTORY_NODES_B.
- PARENT_ITEM_ID — enables hierarchical or compound content structures.
- LIVE_CITEM_VERSION_ID — points to the currently published version in IBC_CITEM_VERSIONS_B.
- CONTENT_ITEM_STATUS — the workflow/lifecycle state of the item.
- LOCKED_BY_USER_ID — identifies a user holding the item for editing.
- BASE_LANGUAGE and TRANSLATION_REQUIRED_FLAG — drive multilingual content processing.
- WD_RESTRICTED_FLAG — governs restricted (whitelist/distribution) access.
- OWNER_RESOURCE_ID and OWNER_RESOURCE_TYPE — identify the owning resource.
- SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling multi-org/security access.
- OBJECT_VERSION_NUMBER — optimistic locking.
- ENCRYPT_FLAG, ORIG_SYSTEM_REFERENCE_ID, and ORIG_SYSTEM_REFERENCE_CODE — track encryption state and the item's origin in an external or legacy system.
- Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).
Common Use Cases and Queries
Typical reporting needs are finding all live items of a given type, auditing items awaiting translation, and locating content by folder.
- List active content by type:
SELECT ci.content_item_id, ci.item_reference_code, ct.content_type_code FROM ibc_content_items ci, ibc_content_types_b ct WHERE ci.content_type_code = ct.content_type_code AND ci.content_item_status = 'ACTIVE'; - Find items pending translation:
SELECT content_item_id, item_reference_code, base_language FROM ibc_content_items WHERE translation_required_flag = 'Y';
- Resolve the current published version:
SELECT ci.item_reference_code, cv.version_number FROM ibc_content_items ci, ibc_citem_versions_b cv WHERE ci.live_citem_version_id = cv.content_item_id;
Related Objects
- IBC_CITEM_VERSIONS_B — referenced via LIVE_CITEM_VERSION_ID and referencing back via CONTENT_ITEM_ID; holds version data (the satellite).
- IBC_CITEM_VERSION_LABELS — language/label rows keyed by CONTENT_ITEM_ID.
- IBC_CONTENT_TYPES_B — content classification, joined on CONTENT_TYPE_CODE.
- IBC_DIRECTORY_NODES_B — folder hierarchy, joined on DIRECTORY_NODE_ID.
- IBC_ASSOCIATIONS and IBC_COMPOUND_RELATIONS — link tables linking content items to each other and to other entities.
- IBC_CONTENT_ITEM_NODES — site/node placement records.
- AMS_CONTENT_RULES_B — references content items as cover letters via COVER_LETTER_ID.
- PRP_PROPOSALS and PRP_COMPONENT_STYLES_B — proposal and style components referencing CONTENT_ITEM_ID.
- FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for access control.
-
IBC_CONTENT_ITEMS stores non version or language specific information about content items
-
IBC_CONTENT_ITEMS stores non version or language specific information about content items
-
View: OKC_TERMS_SECTIONS_V 12.2.2
APPS.OKC_TERMS_SECTIONS_V·↳ OKC_SECTIONS_B·Explore OKC module →
-
View: OKC_TERMS_SECTIONS_HV 12.2.2
APPS.OKC_TERMS_SECTIONS_HV·↳ OKC_SECTIONS_BH·Explore OKC module →
-
View: OKC_TERMS_SECTIONS_HV 12.1.1
APPS.OKC_TERMS_SECTIONS_HV·↳ OKC_SECTIONS_BH·Explore OKC module →
-
View: OKC_SECTIONS_V 12.1.1
-
View: OKC_SECTIONS_HV 12.1.1
-
This entity will contain relationship between template and document where it is used.
-
This entity will contain relationship between template and document where it is used.
-
Sections are used to format clauses of a Contract while printing
-
View: OKC_TERMS_SECTIONS_V 12.1.1
APPS.OKC_TERMS_SECTIONS_V·↳ OKC_SECTIONS_B·Explore OKC module →
-
View: OKC_SECTIONS_HV 12.2.2
-
This table stores all the clauses that are used for an organization. This includes the standard clauses that exist in the clause library as well as the non-standard clauses that are specific to a contract document. This table replaces the O
-
This table stores all the versions of a standard clause and non-standard clause created on a business document. Standard Clauses have multiple versions while the non-standard clauses are created as a single version. This table replaces the
-
Master table for contract terms templates
-
This table stores all the business variables that can be used in clauses. The table contains variables of all types System defined, User-defined, Table and Deliverable.
-
This table stores all the versions of a standard clause and non-standard clause created on a business document. Standard Clauses have multiple versions while the non-standard clauses are created with a single version. This table replaces th
-
History table for OKC_K_ARTICLES_B.
-
Sections are used to format clauses of a Contract while printing
-
View: OKC_TERMS_ARTICLES_V 12.1.1
APPS.OKC_TERMS_ARTICLES_V·↳ OKC_K_ARTICLES_B·Explore OKC module →
-
APPS.OKC_TERMS_ART_DETAILS_V·↳ OKC_ARTICLES_ALL·↳ OKC_ARTICLE_VERSIONS·↳ OKC_K_ARTICLES_B·Explore OKC module →
-
This is the interface table for import of user defined variables from external systems. All valid data in this table will be imported to OKC_BUS_VARIABLES_B, OKC_BUS_VARIABLES_TL by the XML Based Clause Import Concurrent program. The user
-
Master table for contract terms templates
-
This is a temporary table for storing imported contract header attributes. It is used for validating contract attributes, preparing contract header data for importing into Contracts Repository schema and generating error output file for inv
-
View: OKC_ARTICLES_V 12.1.1
This View is based on tables OKC_ARTICLES_ALL and OKC_ARTICLE_VERSIONS.
APPS.OKC_ARTICLES_V·↳ OKC_ARTICLES_ALL·↳ OKC_ARTICLE_VERSIONS·Explore OKC module →
-
OKC_K_ARTICLES holds the use of standard and non-standard ("custom", one-time use) clauses in business documents.When associated with a document header, the clause governs the entire document. When associated with a line, the clause governs
-
View: OKC_ARTICLES_V 12.2.2
This View is based on tables OKC_ARTICLES_ALL and OKC_ARTICLE_VERSIONS.
APPS.OKC_ARTICLES_V·↳ OKC_ARTICLES_ALL·↳ OKC_ARTICLE_VERSIONS·Explore OKC module →
-
History table for OKC_K_ARTICLES_B.
-
APPS.OKC_TERMS_ART_DETAILS_V·↳ OKC_ARTICLES_ALL·↳ OKC_ARTICLE_VERSIONS·↳ OKC_K_ARTICLES_B·Explore OKC module →
-
This entity will contain relationship between template and document where it is used. (history records)
-
This is the main Contracts table. This table stores the latest version of all Repository-authored contracts.
-
This entity will contain relationship between template and document where it is used. (history records)
-
View: OKC_SECTIONS_V 12.2.2
-
This table is the main Contracts table. This table stores the latest version of all contracts authored in Contract Repository.
-
This table stores all the clauses that are used for an organization. This includes the standard clauses that exist in the clause library as well as the non-standard clauses that are specific to a contract document. This table replaces the O
-
View: OKC_TERMS_ARTICLES_HV 12.1.1
APPS.OKC_TERMS_ARTICLES_HV·↳ OKC_K_ARTICLES_BH·Explore OKC module →
-
View: OKC_TERMS_ARTICLES_V 12.2.2
APPS.OKC_TERMS_ARTICLES_V·↳ OKC_K_ARTICLES_B·Explore OKC module →
-
View: OKC_TERMS_ARTICLES_HV 12.2.2
APPS.OKC_TERMS_ARTICLES_HV·↳ OKC_K_ARTICLES_BH·Explore OKC module →
-
History table for OKC_SECTIONS_B
-
History table for OKC_SECTIONS_B
-
This table stores all the business variables that can be used in clauses. This table contains variables of all type - System-defined, User-defined, Table and Deliverable.
-
OKC_K_ARTICLES holds the use of standard and non-standard ("custom", one-time use) clauses in business documents.When associated with a document header, the clause governs the entire document. When associated with a line, the clause governs
-
Table: OKC_REP_CONTRACT_VERS 12.1.1
Stores all previous versions of a contract.
-
This table stores previous versions of a contract.
-
This table stores Deliverables and amendments to deliverables.
-
VIEW: IBC.IBC_CONTENT_ITEMS# 12.2.2
-
VIEW: OKC.OKC_ARTICLES_ALL# 12.2.2