Results for “ibc_content_item”
11 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.IBC_CITEM_PERMISSIONS_V is a security-resolution view in the Oracle E-Business Suite content management schema (IBC). It exposes the effective permission set applicable to each content item, resolving the grants that flow down from directory nodes to the content items they contain. Its central role is to answer the question "which user or resource may perform which action on which content item," combining object-level grants with inheritance rules and precedence-based overrides. Because it flattens the grant hierarchy into discrete permission rows, the view is widely used in reports, extensions, and integrations that must reproduce or audit the access decisions made by the IBC content repository rather than reimplementing the grant logic independently.
The view is defined in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. The row returned for each content item carries a generated SECURITY_FLAG of 'Y', confirming that the row represents an applicable, non-restricted permission for the current session user context.
Underlying Base Objects
The view is constructed from a UNION ALL over two symmetric grant-evaluation branches. Both branches join the same documented base objects:
- IBC_CONTENT_ITEMS — the content item master, supplying item identity, status, ownership, version pointer, and audit columns.
- IBC_OBJECT_GRANT_GROUPS — the association between an object instance (such as a directory node) and a grant group.
- IBC_GRANTS — the individual permission grants, including permission code, action (ALLOW or RESTRICT), and grantee identification.
- IBC_DIRECTORY_NODES_B — the directory hierarchy through which grant inheritance flows.
- FND_OBJECTS — the object registry, used here to constrain grants to the IBC_DIRECTORY_NODE and IBC_CONTENT_ITEM object names.
- FND_GLOBAL — supplies the ambient session user id through FND_GLOBAL.user_id.
- IBC_UTILITIES_PVT — the package whose Check_Current_User function determines whether a grant applies to the current user, including responsibility and resource-group membership.
- JTF_RS_GROUP_MEMBERS, JTF_RS_GROUPS_DENORM, JTF_RS_RESOURCE_EXTNS — resource and group membership tables referenced through the utilities and grantee resolution.
Key Columns
- permission_code — the permission being granted or evaluated.
- content_item_id / item_reference_code — the content item identifier and its human-readable reference.
- content_type_code / content_item_status / base_language — classification, lifecycle status, and originating language of the item.
- directory_node_id / parent_item_id / live_citem_version_id — the owning directory node, parent item, and current live version pointer used to trace inheritance.
- locked_by_user_id / wd_restricted_flag / encrypt_flag — concurrency and protection attributes affecting accessibility.
- owner_resource_id / owner_resource_type — the resource that owns the item.
- security_group_id — the security group scoping the item.
- NVL(IG.grantee_user_id, FND_GLOBAL.user_id) — the resolved grantee, defaulting to the session user when the grant is not user-specific.
- SECURITY_FLAG — a constant 'Y' marking the row as a valid, applicable permission.
Common Use Cases and Queries
Typical scenarios include auditing which permissions a given content item inherits, listing all content items a user can access, and validating that configured grants resolve as intended after migration or patching.
- List permissions for a specific item:
SELECT permission_code, item_reference_code, content_item_status
FROM ibc_citem_permissions_v
WHERE content_item_id = :p_item_id; - Report items and permissions for the current session user:
SELECT content_item_id, item_reference_code, permission_code
FROM ibc_citem_permissions_v
WHERE security_flag = 'Y'; - Audit inherited versus restricted grants by joining back to IBC_GRANTS on permission_code.
Because the view relies on FND_GLOBAL and IBC_UTILITIES_PVT, it must be queried within an initialized EBS session so that the current user and responsibility context are correctly established.