Results for “copy_uda_actions”

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

Overview

The OKC_UDA_TEMPLATES_UTIL package is a utility (UTIL) PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the OKC (Oracle Contracts) application module. Its principal business purpose is to support the definition, deployment, and lifecycle management of User Defined Attribute (UDA) templates and their associated actions, displays, pages, and function mappings. UDAs allow organizations to extend contract structures with customer-specific attributes without modifying the underlying data model; this package provides the low-level plumbing that populates and maintains the EGO (Oracle Product Information Management / Extensible Object Framework) metadata that drives those attributes.

The package is declared with AUTHID CURRENT_USER, meaning procedures execute with the privileges of the invoking user rather than the definer, a design consistent with an internal utility invoked from setup or administrative contexts. Global constants such as G_PKG_NAME, G_APP_NAME ('OKC'), and error tokens OKC_UNEXPECTED_ERROR, ERROR_MESSAGE, and ERROR_CODE indicate adoption of the standard EBS error-handling and message-token conventions.

Key Procedures and Functions

The package exposes eleven documented procedures and functions that fall into two functional groupings: metadata upload routines and template copy/freeze routines.

• UPLOAD_ACTIONS — Loads action definition metadata for a user-defined attribute group, associating an action name with a classification code, internal attribute group name, object, sequence, function, description, and owner.
• UPLOAD_ACTIONS_NLS — Provides the translated (National Language Support) counterpart to UPLOAD_ACTIONS, populating language-specific action text.
• UPLOAD_ACTION_DL — Uploads data-level and visibility configuration for an action, governing where the action appears and whether it is visible.
• UPLOAD_ACTION_DISPLAYS — Uploads display metadata for an action, including execution method, execution trigger, display style, application short name, prompt message name, and visibility flag.
• UPLOAD_FUNCTION_MAPPINGS — Registers mappings between functions and the UDA template metadata so that the framework can resolve executable logic at runtime.
• COPY_ASSOCIATIONS — Duplicates association records when a template is cloned.
• COPY_UDA_ACTIONS — Copies action definitions from a source template to a new template.
• COPY_PAGES — Copies page definitions associated with a template.
• COPY_TEMPLATE_DETAILS — Replicates the core template detail records during template duplication.
• IS_TEMPLATE_FREEZED — A function used to determine whether a given template has been frozen, which the caller uses to prevent modification of locked template metadata.
• DELETE_TEMP_DETAILS — Removes temporary or staging detail records created during upload or copy processing.

Tables Accessed

The package reads and writes the EGO extensibility tables via APPS synonyms. These include EGO_ACTIONS_B, EGO_ACTIONS_TL, and EGO_ACTIONS_S (base, translation, and sequence tables for actions), EGO_ACTION_DISPLAYS_B for display definitions, EGO_DATA_LEVEL_B for data-level configuration, EGO_ASSOCS_S for associations, EGO_FUNCTIONS_B and EGO_FUNC_PARAMS_B for function and parameter metadata, EGO_MAPPINGS_B for function mappings, EGO_OBJ_AG_ASSOCS_B for object/attribute-group associations, EGO_PAGES_B for page definitions, and EGO_FND_DSC_FLX_CTX_EXT for descriptive flexfield context extensions. Reference lookups against FND_APPLICATION and FND_LANGUAGES supply application and installed-language validation.

Usage Notes

OKC_UDA_TEMPLATES_UTIL is an internal utility rather than an end-user API. It is typically invoked by setup forms, concurrent programs, or seeded Oracle Contracts routines during template administration, template cloning, and metadata migration between environments. Because it is referenced by zero other packages per the documented metadata, direct callers are largely confined to the OKC setup layer or custom code performing bulk template deployment. Callers should account for the AUTHID CURRENT_USER declaration, ensure the invoking user holds appropriate EGO and OKC privileges, and use IS_TEMPLATE_FREEZED to guard write operations against frozen templates before executing copy or upload procedures.