Search Results ntb_upload_standard_who

Overview

APPS.MTH_UDA_PKG is a PL/SQL package that belongs to the Oracle E-Business Suite ETRM (Enterprise Transaction and Receipt Management) product family. Its header identifies it as a utility package built around user-defined attribute (UDA) handling for ETRM entities such as tags and devices. The package exposes a mix of driver procedures and lightweight lookup functions that move staged data from external and master staging tables into their primary transactional destinations, normalise the "who" audit columns, and resolve entity metadata (master table, primary key, external table, external TL table, and entity code) at runtime.

The presence of the get_ext_table_name function—the object the user searched for—confirms that MTH_UDA_PKG acts as an entity-to-table resolver. Callers pass an internal entity name and receive the physical external table name used for that entity's UDA storage. This allows generic uploader and device-processing code to remain independent of the specific entity being processed, since the required table names are derived dynamically rather than hard-coded.

Key Procedures and Functions

• UPDATE_TO_PRIMARY_KEY — Updates staged rows against the entity's primary key values.
• NTB_UPLOAD_STANDARD_WHO — Populates standard WHO (created/updated) audit columns for uploaded external rows.
• NTB_UPLOADTL — Uploads translated (TL) UDA records for a given entity and extension.
• NTB_UPLOAD — Main upload routine that moves staged data to the target entity table.
• DEVICE_PRE_LOG — Writes a pre-processing log entry for device uploads.
• TB_UPLOAD — Performs the table-level upload operation.
• DEVICE_POST_LOG — Writes a post-processing log entry for device uploads.
• GET_MST_TABLE_NAME — Returns the master table name for an entity.
• GET_MST_PK_NAME — Returns the master primary key column name for an entity.
• GET_EXT_TL_TABLE_NAME — Returns the external translated table name for an entity.
• GET_EXT_TABLE_NAME — Returns the external (UDA) table name for an entity; this is the function referenced in the user's search.
• GET_ENTITY_CODE — Returns the numeric entity code for a given entity name.

The documented metadata also lists composite-key variants—UPDATE_COMPOSITE_PRIMARY_KEY, GET_MST_COMPOSITE_PK_NAME, NTB_UPLOAD_COMPOSITETL, and NTB_UPLOAD_COMPOSITE_PK—which extend the same upload pattern to entities whose primary keys are composed of more than one column.

Tables Accessed

• MTH_EXT_ATTR_T_STG — staging table for external UDA attribute values; the source from which NTB_UPLOAD and its variants read.
• MTH_TAG_READINGS_T_STG — staging table for tag readings, consumed by the device upload logic.
• MTH_RUN_LOG — log table populated by DEVICE_PRE_LOG and DEVICE_POST_LOG to record device upload execution.
• DUAL — used by the resolver functions to evaluate expressions and return single scalar values.
• PLITBLM — the EBS PL/SQL table-of-strings utility referenced by the upload/parsing code.

Usage Notes

MTH_UDA_PKG is invoked from ETRM device and tag upload flows, either through concurrent programs or from form-driven processing that triggers the NTB_UPLOAD family. Custom extensions should call the GET_*_TABLE_NAME functions to resolve entity-specific table names before composing dynamic SQL, rather than embedding physical table names. GET_ENTITY_CODE supplies the numeric identifier needed to key extension and attribute lookups. Because the package is owned by APPS and classified as OTHER, it is not a public API; callers should treat the signatures as internal, verify behaviour against the target patch level (12.1.1 versus 12.2.2), and avoid modifying the source. Two other packages reference MTH_UDA_PKG, indicating it is a shared utility within ETRM rather than a standalone entry point.