Results for “upload_action_dl”

5 results




Overview
Explore in AI Chat

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

Overview

OKC_UDA_TEMPLATES_UTIL is a utility package body in the APPS schema that supports the Oracle Contracts (OKC) User-Defined Attribute (UDA) template framework. Its principal business function is to propagate the metadata that underpins UDA templates into the Oracle E-Business Suite Extensibility Framework (EGO), so that UDA templates and their associated actions, displays, pages, and function mappings are correctly registered and available to the Contracts application. In effect, the package acts as a bridge between the Contracts UDA template tables and the EGO repository that drives dynamic page rendering and action behavior.

The package is classified as a UTIL object, meaning it is not intended as a directly callable business API but as internal infrastructure invoked by higher-level Contracts processes. It is a leaf dependency: no other database object references it, and therefore its effect is strictly outward, driving the EGO tables that other components consume.

Key Procedures and Functions

Eleven documented procedures and functions make up the package's supported surface.

  • UPLOAD_ACTIONS — Loads action definitions from the UDA template context into the EGO action tables.
  • UPLOAD_ACTIONS_NLS — Handles the translated (NLS) action text associated with the uploaded actions.
  • UPLOAD_ACTION_DL — Populates action display-level information for the uploaded actions.
  • UPLOAD_ACTION_DISPLAYS — Registers action displays within the EGO framework.
  • UPLOAD_FUNCTION_MAPPINGS — Establishes mappings between EGO functions and their parameters for the template.
  • COPY_ASSOCIATIONS — Duplicates association records, notably EGO_ASSOCS_S entries, when a template is copied.
  • COPY_UDA_ACTIONS — Copies action definitions as part of a template copy operation.
  • COPY_PAGES — Replicates EGO page and page-entry definitions when a template is duplicated.
  • COPY_TEMPLATE_DETAILS — Copies the broader set of template detail records, including deliverable usages.
  • IS_TEMPLATE_FREEZED — Determines whether a template is frozen, governing whether updates are permitted.
  • DELETE_TEMP_DETAILS — Removes temporary or staging template detail rows after processing.

Tables Accessed

Through APPS synonyms, the package reads and writes the Contracts UDA template objects OKC_UDA_TEMPLATES_ALL, OKC_UDA_TEMPLATES_VL, OKC_UDA_DELIVERABLE_USAGES, and the sequence OKC_UDA_DEL_USAGES_S1. On the EGO side it operates on EGO_ACTIONS_B, EGO_ACTIONS_TL, EGO_ACTIONS_S, and EGO_ACTIONS_DL for action definition and translation data; EGO_ACTION_DISPLAYS_B, EGO_DATA_LEVEL_B, and EGO_PAGES_B / EGO_PAGES_V / EGO_PAGE_ENTRIES_V for display and page structure; EGO_FUNCTIONS_B, EGO_FUNC_PARAMS_B, and EGO_MAPPINGS_B for function-to-parameter mappings; EGO_OBJ_AG_ASSOCS_B and EGO_ASSOCS_S for object association data; and EGO_FND_DSC_FLX_CTX_EXT for descriptive flexfield context extensibility. Supporting lookup tables include FND_APPLICATION, FND_LANGUAGES, and FND_OBJECTS.

Usage Notes

The package relies on FND_API, FND_GLOBAL, FND_MSG_PUB, FND_LOG, and FND_FILE for error handling, message resolution, logging, and file output, and it leverages EGO_EXT_FWK_PUB and OKC_API for higher-level framework and Contracts operations. It is invoked indirectly by Contracts setup forms and concurrent programs that create, upload, or copy UDA templates, and by any custom extension that programmatically duplicates template definitions. Because it is unreferenced by other database objects and marked UTIL, direct invocation in custom code is discouraged unless replicating standard template upload and copy behavior. Logging through FND_LOG and the use of FND_API error stacks provide the diagnostic trail expected of standard ETRM processing.