Search Results jtf_auth_principals_pkg




Overview
Explore in AI Chat

Overview

The APPS.JTF_AUTH_PRINCIPALS_PKG package body is a standard Oracle E-Business Suite generated table-handler and translation-support package that manages the persistence layer for the JTF_AUTH_PRINCIPALS authorization principals entity. In Oracle EBS 12.1.1 and 12.2.2, the JTF (Java Technology Foundation / CRM Foundation) schema hosts the security and authorization infrastructure used across CRM and self-service applications. Authorization principals represent the actors — users or roles — against which functional and data-level privileges are granted. The package provides the DML and multi-language translation plumbing required to keep the base table (JTF_AUTH_PRINCIPALS_B) and the translation table (JTF_AUTH_PRINCIPALS_TL) synchronized with what the application tier exposes.

Its status is VALID in the ETRM registry, confirming the package is compiled and operational in the documented release. The body is classified as an OTHER API rather than a true business API, reflecting its role as generated infrastructure rather than an orchestrated business service. It depends on FND_API, FND_MESSAGE, APP_EXCEPTION, FND_LANGUAGES, and JTF_UM_ROLE_VERIFICATION, indicating it participates in the standard EBS error-handling, messaging, and role-verification infrastructure.

Key Procedures and Functions

The package exposes eight documented procedures/functions covering the full maintenance lifecycle of an authorization principal record:

  • INSERT_ROW — Creates a new authorization principal record in the base table, assigning a primary key from the sequence and stamping WHO columns.
  • LOCK_ROW — Acquires a row-level lock on an existing principal to serialize concurrent updates, typically invoked before an UPDATE_ROW.
  • UPDATE_ROW — Modifies the attributes of an existing principal record, preserving audit columns through the standard EBS WHO framework.
  • DELETE_ROW — Removes an authorization principal and, where applicable, its associated translation rows.
  • ADD_LANGUAGE — Inserts a new translation row into JTF_AUTH_PRINCIPALS_TL for a specified language, enabling the principal's display name to be localized.
  • TRANSLATE_ROW — Updates an existing translation row so that an administrator can correct or refine localized text without altering the base record.
  • LOAD_ROW — Provides an idempotent load/upsert entry point, used by seed-data and migration processes to insert a principal if absent or update it if present.

Parameter lists are intentionally omitted here; the documented metadata does not enumerate them, and they should be confirmed directly in the deployed package specification before custom invocation.

Tables Accessed

  • JTF_AUTH_PRINCIPALS_B — The base table storing the non-translatable attributes of each authorization principal. It is the primary target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
  • JTF_AUTH_PRINCIPALS_TL — The translation table holding language-specific display text. ADD_LANGUAGE and TRANSLATE_ROW write to it, and it is joined to the base table for localized queries.
  • FND_LANGUAGES — Read to validate that a requested language is installed and active before a translation row is created or updated.

All three tables are accessed through APPS synonyms, which is standard for generated EBS table-handler packages.

Usage Notes

This package is typical of EBS generated infrastructure: it is invoked indirectly by the Applications Framework (OAF) pages, Oracle Forms, and concurrent programs that maintain authorization principals, rather than being called directly by end users. Developers integrating with it should prefer the supported business API layer where one exists, and reserve direct calls to JTF_AUTH_PRINCIPALS_PKG for data migration, seeding, or controlled backfill scripts.

The ETRM registry shows the package is referenced by two other database objects and references JTF_UM_ROLE_VERIFICATION, so any change to the package body should be recompiled with dependents to avoid invalidations. Because the package writes to translated tables, bulk operations should set the language context and commit appropriately to preserve WHO audit information.