Results for “object_application_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_APP_FUNCTION_ACCESSES is a development-seeded configuration table residing in the OKC schema, the Contracts Core module of Oracle E-Business Suite. Its stated purpose is to control access to contract objects based on two axes: the application that owns the object and the application associated with the querying user. In practice, the table acts as a cross-application access control list that the Contracts runtime consults when a user attempts to view, create, or modify contract artifacts whose owning application differs from the user's responsibility application.

Because the table is seeded by development at installation or upgrade rather than maintained by end users, its row count is small and stable. Administrators and implementers typically inspect or extend the seeded content rather than treating it as transactional data. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. In practice it is closest to a reference or lookup satellite: the business key is composed of functional attributes, and the descriptive access flag and comments behave as satellite-style attributes rather than as a hub of independently tracked business entities. This classification is a modeling suggestion only; the physical table is a conventional relational configuration table.

Key Information Stored

The documented physical schema contains 14 columns in ETRM 12.2.2. The most significant are:

• FUNCTION — identifies the functional operation or contract function whose access is being governed. Together with OBJECT_TYPE this forms the semantic core of the row.
• OBJECT_TYPE — the category of contract object to which the access rule applies.
• OBJECT_APPLICATION_ID — the application that owns the object; maps to FND_APPLICATION.
• RESPONSIBILITY_APPLICATION_ID — the application owning the responsibility through which the user is operating.
• OBJECT_ACCESS_FLAG — the Boolean-style outcome of the rule; determines whether access is granted or denied for the given object/user application pair.
• COMMENTS — free-text annotation describing the intent of the seeded rule.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework for concurrent update detection.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or data-group partitioning.
• ZD_EDITION_NAME — editioning column introduced under the 12.2 online patching architecture, allowing edition-specific visibility of seeded rows.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

The unique index OKC_APP_FUNC_ACCESSES_U1 on (FUNCTION, OBJECT_TYPE, OBJECT_APPLICATION_ID, RESPONSIBILITY_APPLICATION_ID, ZD_EDITION_NAME) constitutes the business-key candidate. There is no separate surrogate key column beyond the composite uniqueness enforced by this index.

Common Use Cases and Queries

Typical usage centers on diagnosing cross-application access failures in contracting flows such as Service Contracts, Procurement Contracts, and Project Contracts. Support and implementation teams query the table to confirm whether a rule exists for a given function and application combination before investigating responsibility or menu setup.

• Verifying a rule: SELECT function, object_type, object_access_flag FROM okc.okc_app_function_accesses WHERE object_application_id = :obj_app AND responsibility_application_id = :resp_app;
• Listing all denied rules: filter on OBJECT_ACCESS_FLAG = 'N' to review restrictive seed data after upgrade.
• Auditing editions: group by ZD_EDITION_NAME to detect duplicate rows created across online patching editions.
• Security group review: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to confirm partitioning of the rules.

Related Objects

• FND_SECURITY_GROUPS — joined via OKC_APP_FUNCTION_ACCESSES.SECURITY_GROUP_ID; validates the data-group context of each rule.
• FND_APPLICATION — resolves both OBJECT_APPLICATION_ID and RESPONSIBILITY_APPLICATION_ID to application short names and descriptions.
• FND_FUNCTION — resolves the FUNCTION column to the underlying form or function definition.
• FND_RESPONSIBILITY — provides the responsibility context that supplies RESPONSIBILITY_APPLICATION_ID.
• OKC_K_HEADERS and related contract header tables — the principal objects whose access is governed indirectly by these rules.
• OKC_UTIL and the Contracts access-check APIs — runtime consumers that read this table when evaluating authorization.