Results for “sync_allowed_yn”

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

Overview

OKC_ACTIONS_B is the base table within the Oracle Contracts Core (OKC) product module that stores the definitional records for Actions in Oracle E-Business Suite 12.1.1 and 12.2.2. Actions in the Contracts Core model represent the executable units that drive contract lifecycle behavior, such as routing, approval, notification, and clause-related processing. Each row in OKC_ACTIONS_B represents a single action definition, identified internally by a surrogate key and externally by a correlation identifier. The table resides in the OKC schema and is registered as VALID in ETRM.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is hub-leaning. This suggests that OKC_ACTIONS_B functions primarily as a hub of distinct business entities (actions), with dependent detail and attribute data likely carried in satellite or related tables such as OKC_ACTION_ATTRIBUTES_B. Downstream references confirm its central role, since multiple foreign keys from other tables point to OKC_ACTIONS_B rather than the reverse, which is characteristic of a reference or hub table.

Key Information Stored

The table contains 33 documented columns. The most significant include:

• ID — the internal identifier and part of the unique index OKC_ACTIONS_B_U1 (ID, ZD_EDITION_NAME). This serves as the primary surrogate key, enforced through the OKC_ACTIONS_B_PK constraint.
• CORRELATION — the business-key candidate captured in the unique index OKC_ACTION_B_U2 (CORRELATION, ZD_EDITION_NAME) and referenced in the ACN_UK constraint. It provides the stable, externally meaningful identifier for an action.
• ACN_TYPE — indicates the category or classification of the action, driving which business logic is applied.
• ENABLED_YN and FACTORY_ENABLED_YN — control whether the action is active at runtime and whether it was enabled by Oracle as a seeded feature.
• COUNTER_ACTION_YN and SYNC_ALLOWED_YN — govern counter-action behavior and synchronization permissions for the action.
• SEEDED_FLAG — distinguishes Oracle-delivered seed data from customer-defined actions.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• SECURITY_GROUP_ID and APPLICATION_ID — provide multi-tenant security grouping and owning-application context; SECURITY_GROUP_ID carries a foreign key to FND_SECURITY_GROUPS.
• Audit columns including CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield storage.
• ZD_EDITION_NAME — the editioning column supporting EBS 12.2 online patching.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include identifying all enabled actions for a given action type, validating which actions are Oracle-seeded versus custom, and tracing how condition headers and action attributes reference a particular action. A common query pattern joins OKC_ACTIONS_B to its dependent tables by the ACN_ID column.

• Listing enabled actions by type: SELECT id, correlation, acn_type FROM okc_actions_b WHERE enabled_yn = 'Y' AND acn_type = :p_type;
• Finding seeded versus custom actions: SELECT correlation, seeded_flag FROM okc_actions_b WHERE factory_enabled_yn = 'Y';
• Joining to attribute details: SELECT a.correlation, b.acn_id FROM okc_actions_b a, okc_action_attributes_b b WHERE a.id = b.acn_id;
• Linking to condition headers: SELECT c.acn_id, a.correlation FROM okc_condition_headers_b c, okc_actions_b a WHERE c.acn_id = a.id;

Related Objects

The following objects are the most significant dependents and references based on the documented foreign key structure:

• OKC_ACTION_ATTRIBUTES_B — references OKC_ACTIONS_B via ACN_ID, holding the attribute detail for each action.
• OKC_CONDITION_HEADERS_B — references OKC_ACTIONS_B via ACN_ID, linking actions to condition definitions.
• AHL_EVENT_ASSOCIATIONS — references OKC_ACTIONS_B via EVENT_ID, associating actions with events in the AHL (Oracle Advanced Planning) module.
• FND_SECURITY_GROUPS — referenced by OKC_ACTIONS_B.SECURITY_GROUP_ID, supplying multi-tenant security context.

Together these relationships confirm OKC_ACTIONS_B as a foundational hub table in the Contracts Core action framework, with OKC_ACTION_ATTRIBUTES_B and OKC_CONDITION_HEADERS_B acting as its principal satellite and dependent structures.