Search Results okc_rep_bookmarks_u1

Overview

The OKC.OKC_REP_BOOKMARKS table is a repository-side object within the Oracle E-Business Suite Contracts (OKC) schema. It stores user-defined bookmarks that allow individual users to flag specific contracts or folders for rapid retrieval, effectively serving as a personal shortcut mechanism within the Contracts reporting and repository interface. Because it is deployed under the OKC schema and registered as FND Design Data (OKC.OKC_REP_BOOKMARKS), it participates fully in the EBS Application Object Library and standard concurrent processing conventions.

Under the heuristic Data Vault classification mined from its foreign-key structure, OKC_REP_BOOKMARKS is assessed as satellite-leaning. This suggests that in a dimensional or Data Vault model it is best treated as an attribute-bearing satellite attached to the parent contract entity, rather than as an independent hub or a pure link table. The table carries descriptive context (bookmark type, owning user, audit metadata) alongside its reference to the bookmarked object, which is characteristic satellite behavior. The object is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index resides in the APPS_TS_TX_IDX tablespace.

Key Information Stored

The table contains ten documented columns. The structural and business columns are as follows:

• OBJECT_ID – The numeric identifier of the bookmarked object (a contract or folder). This column is the surrogate primary key, enforced through OKC_REP_BOOKMARKS_PK, and it is also the column through which the table relates to its parent entity.
• OBJECT_TYPE – A VARCHAR2(30) discriminator storing the type of the bookmarked object. Per the documented comments, it stores the Contract Type.
• USER_ID – The numeric identifier of the user who created the bookmark, scoping the bookmark to a specific individual.
• BOOKMARK_TYPE_CODE – A VARCHAR2(30) code describing the bookmark category. Only the value CONTRACT is currently supported.
• OBJECT_VERSION_NUMBER – A sequential versioning column initialized to 1 on insert and incremented on update. It is used by the public APIs to implement optimistic locking and ensure that the current record version is passed during DML.

The remaining columns are the standard Who columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These provide the audit trail required across all Oracle EBS transactional tables.

It is important to distinguish the surrogate primary key (OBJECT_ID) from the business-key candidate. The unique index OKC_REP_BOOKMARKS_U1 is defined on the composite of OBJECT_TYPE, OBJECT_ID, USER_ID, and BOOKMARK_TYPE_CODE. This composite enforces the business rule that a given user may hold only one bookmark of a given type against a given object, while the PK on OBJECT_ID alone provides the internal row identity referenced by dependent objects.

Common Use Cases and Queries

Typical use cases center on retrieving a user's saved contract shortcuts, auditing bookmark creation activity, and validating bookmark uniqueness. A common reporting pattern joins the bookmark to its user and contract context:

SELECT b.OBJECT_TYPE, b.OBJECT_ID, b.USER_ID, b.BOOKMARK_TYPE_CODE
FROM   OKC.OKC_REP_BOOKMARKS b
WHERE  b.USER_ID = :p_user_id
AND    b.BOOKMARK_TYPE_CODE = 'CONTRACT';

Because OKC_REP_BOOKMARKS is referenced by the APPS synonym OKC_REP_BOOKMARKS, querying through the APPS synonym is valid for custom reports and BI Publisher data models. Auditing queries commonly inspect the Who columns to determine when a bookmark was created or last modified, while integrity checks verify that no duplicate combination exists across the four columns of OKC_REP_BOOKMARKS_U1. Migration or decommissioning scripts frequently select the full column list against a target USER_ID before deleting stale bookmarks.

Related Objects

Relationship data identifies OKC_REP_BOOKMARKS as referenced by the APPS synonym and captured as a satellite-leaning entity whose OBJECT_ID resolves to a parent contract or folder. The most significant associated objects are:

• OKC.OKC_REP_BOOKMARKS_PK – the primary key constraint on OBJECT_ID.
• OKC.OKC_REP_BOOKMARKS_U1 – the unique business-key index on OBJECT_TYPE, OBJECT_ID, USER_ID, BOOKMARK_TYPE_CODE.
• APPS.OKC_REP_BOOKMARKS – the APPS-layer synonym through which the table is exposed to reports and APIs.
• OKC.OKC_REP_BOOKMARK – the public API package that maintains bookmark records and enforces the optimistic locking driven by OBJECT_VERSION_NUMBER.
• Parent contract and folder entities resolved through OBJECT_ID using OBJECT_TYPE as the discriminator.
• FND_USER, joined on USER_ID to resolve the bookmark owner in user-facing reports.