Search Results hr_tips_dml




Overview

HR_TIPS_DML is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its name and documented contents indicate that it provides the data manipulation layer for the "tips" feature within the Oracle HRMS (Human Resources Management System) product family. Tips in this context are short contextual messages presented to end users — typically HR professionals operating HRMS forms — offering guidance, reminders, or product hints tied to the current window or task. The package encapsulates the insert and maintenance logic required to persist these tip records, insulating calling forms and concurrent programs from direct DML against the underlying tables.

Within the ETRM object classification the package is designated API classification OTHER, meaning it is not a formally published business API such as those registered in the integration repository, but rather an internal DML helper intended primarily for Oracle-authored forms and internal processing. The ETRM record lists the package with status VALID in the APPS schema, confirming it is a supported, compiled component of the application database tier.

Key Procedures and Functions

ETRM documents two callable units within HR_TIPS_DML:

  • ADDTIP — Creates a new tip record. This procedure inserts the row-level definition of a tip so that it becomes available to the HRMS forms layer that displays contextual messages. It is the primary entry point for populating tips, whether during setup, patching, or programmatic generation of guidance content.
  • CLEARTIPS — Removes tip records. This procedure provides the complementary maintenance operation, allowing tip definitions to be purged or repositioned so that stale, obsolete, or superseded guidance no longer appears to users.

The two procedures form a paired create/clear interface, which is a common pattern for small data-maintenance helper packages. The documented metadata does not enumerate parameter signatures, and in accordance with that limitation no parameter lists are asserted here; consumers should inspect the package specification in the database for exact argument definitions before invoking these units directly.

Tables Accessed

The package operates on two documented tables, accessed through APPS synonyms:

  • HR_TIPS — The base transactional table holding tip definitions. ADDTIP writes to this table, and CLEARTIPS deletes from it.
  • HR_TIPS_S — The corresponding translated (localized) table, which stores the language-specific tip text associated with a tip definition. Because HRMS forms display tips directly to users, the text must be available in each installed language. ADDTIP and CLEARTIPS maintain both the base definition and its translations in a coordinated fashion so definitions and their multilingual text do not diverge.

Read access in the dependency metadata is limited to the SYS-owned STANDARD package, reflecting standard PL/SQL runtime usage rather than additional application tables.

Usage Notes

HR_TIPS_DML is an internal helper rather than a public integration surface. It is typically invoked from Oracle HRMS forms logic and from Oracle-supplied scripts or concurrent processing that seeds or refreshes tip content during implementation and patching. Because ETRM records zero other packages referencing HR_TIPS_DML, it should be treated as a leaf-level utility: external dependencies are limited, and no application package depends on it being executed as part of an API chain.

Custom code should exercise caution. The package is documented as classification OTHER and is not governed by Oracle's public API compatibility guarantees, so its behavior or availability may change across patch levels within 12.1.1 and 12.2.2. Where custom extension requires tip data, direct manipulation of HR_TIPS and HR_TIPS_S through supported tooling is preferable to binding custom logic to this internal DML package. When direct invocation is unavoidable, callers must ensure records are committed consistently across both tables and must validate that resulting tip text is present in all required languages before relying on the data in a production forms session.