Search Results hr_tips_uk1

Overview

HR.HR_TIPS is a seed data table in the Oracle E-Business Suite Human Resources (HR) schema that stores contextual help or "tip" text associated with specific application screens and fields. It belongs to the FND Design Data group PER.HR_TIPS and is physically stored in the APPS_TS_SEED tablespace, which is consistent with its role as a seed-data object shipped with the application. The table holds a small number of columns—eight in the documented 12.2.2 schema—and each row associates a tip with a screen, a field, a language, and a business group.

The ETRM metadata explicitly records that this object is obsoleted and not used in Release 12. Consequently, while the table remains VALID and physically present in a 12.1.1 or 12.2.2 instance, it is effectively a legacy object. It should be treated as a read-only artifact for historical or upgrade analysis rather than an active functional component.

Under the heuristic Data Vault classification inferred from its foreign key structure, HR_TIPS leans toward a satellite pattern: it carries descriptive attributes (tip text, filename, enabled flag) that attach to a hub-like business entity (business group) via a foreign key, rather than serving as an independent hub or as a pure many-to-many link.

Key Information Stored

The table's surrogate primary key is TIP_ID, a system-generated NUMBER(15) populated from the HR_TIPS_S sequence and enforced by the HR_TIPS_PK index. The documented business-key candidate is the unique index HR_TIPS_UK1, which spans four columns and guarantees that a given tip is unique for a screen, field, language, and business group combination.

• SCREEN (VARCHAR2 30) — the name of the screen for which the tip is valid; part of HR_TIPS_UK1.
• FIELD (VARCHAR2 30) — the name of the field the tip describes; part of HR_TIPS_UK1.
• LANGUAGE_CODE — the language for which the tip applies; part of HR_TIPS_UK1 and the natural driver of translated tip content.
• BUSINESS_GROUP_ID (NUMBER 15) — foreign key to HR_ALL_ORGANIZATION_UNITS; part of HR_TIPS_UK1 and the join path to organizational context.
• TEXT (CLOB 4000) — the actual tip text content retained for the screen/field combination.
• ENABLED_FLAG — flag indicating whether the tip is active.
• FILENAME (VARCHAR2) — the name of the file from which the tip row was originally loaded.

The presence of a LOB index (SYS_IL0000044498C00008$$) on APPS_TS_SEED confirms that TEXT is stored as a CLOB segment requiring dedicated LOB storage.

Common Use Cases and Queries

Because HR_TIPS is obsolete in Release 12, the principal use cases are diagnostic and archival rather than operational. A consultant investigating residual seed data, comparing instance contents during an upgrade, or auditing a custom extension that still references the table would query it directly. A representative query follows:

• Retrieve all enabled tips for a screen and language, filtered by business group: SELECT TIP_ID, SCREEN, FIELD, LANGUAGE_CODE, TEXT FROM HR.HR_TIPS WHERE ENABLED_FLAG = 'Y' AND SCREEN = :screen AND LANGUAGE_CODE = :lang AND BUSINESS_GROUP_ID = :bg_id;
• Count tips per screen and field to assess the volume of retained seed content: SELECT SCREEN, FIELD, COUNT(*) FROM HR.HR_TIPS GROUP BY SCREEN, FIELD;
• Enumerate translated variants for a given screen/field pair: SELECT LANGUAGE_CODE, TEXT FROM HR.HR_TIPS WHERE SCREEN = :screen AND FIELD = :field;
• Check for duplicate business keys that might indicate a data issue, though HR_TIPS_UK1 should prevent this: SELECT SCREEN, FIELD, LANGUAGE_CODE, BUSINESS_GROUP_ID, COUNT(*) FROM HR.HR_TIPS GROUP BY SCREEN, FIELD, LANGUAGE_CODE, BUSINESS_GROUP_ID HAVING COUNT(*) > 1;

Reporting is typically limited to identifying whether any rows remain, since the module that consumed the tips in earlier releases is no longer active in R12.

Related Objects

The documented relationship data identifies the foreign key from BUSINESS_GROUP_ID to HR_ALL_ORGANIZATION_UNITS, making that table the most significant related object. Additional dependencies are implied by the object's design and design-data assignment.

• HR.HR_ALL_ORGANIZATION_UNITS — joined via BUSINESS_GROUP_ID to resolve the business group that owns each tip.
• HR.HR_TIPS# — the documented dependent object associated with the table, typically a synonym or editioning view artifact over HR_TIPS.
• PER.HR_TIPS design data — the FND design data group that defines the seed rows shipped with the application.
• HR.HR_TIPS_S — the sequence that generates TIP_ID values for the primary key.
• FND application screen/field definitions — the conceptual metadata (screens and fields referenced by SCREEN and FIELD) that provides the logical context for each tip.

Because the table is marked obsolete, no current application API is expected to depend on it; any references are likely to be legacy code, upgrade scripts, or customizations retained from earlier releases.