Search Results factory_enabled_yn

Overview

OKC_ACTIONS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC (Contracts Core) product family. It presents the definition, metadata, and translation content for contract actions — the configurable business operations that may be invoked against a contract record within Oracle Contracts and its integration touchpoints. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and its referenced objects are confirmed against the 12.2.2 metadata: the base table OKC_ACTIONS_B and the translation table OKC_ACTIONS_TL, accessed through their APPS synonyms.

Because Oracle Contracts is multilingual, the underlying data is modelled in the standard EBS pattern: language-independent and non-translatable attributes are stored in the base (B) table, while translatable attributes are held in the translation (TL) table. OKC_ACTIONS_V performs the join so that callers receive a single row per action in the session language, determined by USERENV('LANG'). The view thereby serves as the canonical, report-safe interface for contract action setup, making it suitable for extraction, seeded data validation, integration lookups, and reporting without requiring consumers to resolve the B/TL join themselves.

Underlying Base Objects

The view text is a two-table equi-join. The driving table is OKC_ACTIONS_B, aliased ACNB, which supplies all identity, control, and descriptive-flexfield columns. It is joined to OKC_ACTIONS_TL, aliased ACNT, on the identical primary-key value ID. The join predicate is completed by ACNT.LANGUAGE = USERENV('LANG'), which restricts the result set to the translation row matching the caller's current language environment. This means the view returns one row per action ID per session language; if no translation exists for the session language, that action is not returned, and rows created in another language will not appear.

All non-translatable columns (correlation, enabled flags, type, application, seeded indicator, WHO audit columns, and the fifteen descriptive flexfield attribute columns) originate from OKC_ACTIONS_B. The translatable columns — SFWT_FLAG, NAME, DESCRIPTION, SHORT_DESCRIPTION, and COMMENTS — originate from OKC_ACTIONS_TL. The ROW_ID column is derived as ACNB.ROWID. Because the view exposes ROWID, it is generally treated as non-updatable through the view; DML against contract action setup should be directed at the base and translation tables through the supported Contracts APIs rather than through this view.

Key Columns

• ROW_ID — the physical row identifier from OKC_ACTIONS_B, useful for diagnostics and duplicate detection.
• ID — primary key of the contract action and the join key between the base and translation tables.
• NAME / DESCRIPTION / SHORT_DESCRIPTION / COMMENTS — language-specific display text taken from OKC_ACTIONS_TL.
• CORRELATION — the internal correlation token used to relate the action definition to its processing logic.
• ENABLED_YN — indicates whether the action is currently enabled.
• FACTORY_ENABLED_YN — the Oracle-shipped enablement state, preserved for upgrade and comparison purposes.
• COUNTER_ACTION_YN — flags whether the action represents a counter-action (for example, a reversal or undo operation).
• ACN_TYPE — the action type classification used to group behaviour.
• SYNC_ALLOWED_YN — indicates whether the action may be synchronised, typically in integration or workflow contexts.
• APPLICATION_ID — owning application, distinguishing customer-defined entries from Oracle-shipped definitions.
• SEEDED_FLAG — identifies Oracle-seeded (reference) data versus user-defined rows.
• OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield structure for customer-defined extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is most frequently used to inspect the set of enabled contract actions, to separate seeded definitions from customer-defined ones, and to report against action names in the user's language.

• List enabled actions: SELECT id, name, acn_type, correlation FROM okc_actions_v WHERE enabled_yn = 'Y' ORDER BY name;
• Identify Oracle-seeded definitions: SELECT id, name, application_id FROM okc_actions_v WHERE seeded_flag = 'Y';
• Review customer-defined actions: SELECT id, name, enabled_yn FROM okc_actions_v WHERE seeded_flag = 'N';
• Detect counter-actions and sync-capable actions: SELECT id, name, counter_action_yn, sync_allowed_yn FROM okc_actions_v WHERE counter_action_yn = 'Y' OR sync_allowed_yn = 'Y';
• Trace a specific action by correlation: SELECT id, name, correlation, factory_enabled_yn FROM okc_actions_v WHERE correlation = :p_correlation;

When results appear incomplete, the cause is almost always the language predicate. Confirming the session language, or querying OKC_ACTIONS_TL directly across all languages, resolves such discrepancies. For cross-language audits, joining OKC_ACTIONS_B to OKC_ACTIONS_TL without the language filter provides a complete translated picture.