Search Results update_person_language

Overview

IBU_HZ_PERSON is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the Oracle iMarketing/IBU (Interactive Business User) family of objects and provides a controlled, API-driven mechanism for maintaining language preference information associated with person parties registered in the Trading Community Architecture (TCA) model. The package source header carries the RCS identifier ibuulngb.pls 120.1 with a last modification date of 2005, indicating that the object is a stable, low-revision component whose contract has remained unchanged across the 12.x release stream.

Its business purpose is narrowly scoped: to ensure that a given person party has exactly one primary language preference. The package encapsulates the decision logic required to determine whether a language preference already exists for the party and to add or modify the record accordingly, thereby shielding callers from the underlying TCA person-info public APIs.

Key Procedures and Functions

ETRM documents a single public procedure in this package body: Update_Person_Language.

• Update_Person_Language — Sets a specified language as the primary language preference for a person party. Per the package header commentary, the procedure first locates any existing language preference for the supplied party. If a row is found, it clears the primary indicator (setting the current primary language to 'N') and then promotes the newly supplied language to primary status. If no language preference row exists for the party, the procedure creates a new language record and marks it as primary. The procedure is designed to be invoked with a party identifier and a language name, and it returns diagnostic and error-handling outputs through debug, return status, message count, and message data channels. It also accepts a "created by module" value used for audit attribution of any row it creates. No parameter list beyond this documented signature should be assumed.

Internally, the procedure determines the party type and resolves the associated person subject from the party relationship before it affects any language data. Because APPS.IBU_HZ_PERSON does not expose the other helper logic publicly, Update_Person_Language is the sole supported entry point to the package.

Tables Accessed

The package reads and writes the following TCA tables through APPS synonyms:

• HZ_PARTIES — Read to resolve the PARTY_TYPE for the supplied party identifier. This drives the branching logic that determines whether the party represents a person eligible for a language preference.
• HZ_RELATIONSHIPS — Read to locate the person subject (SUBJECT_ID) associated with the party, filtered on SUBJECT_TYPE = 'PERSON'. This establishes the correct person context for the language record.
• HZ_PERSON_LANGUAGE — The primary target of the operation. The package queries this table to detect an existing language preference; if present, it updates the primary indicator and the language value. If absent, it inserts a new primary language row.

Usage Notes

Update_Person_Language is not referenced by any other documented package (the ETRM dependency count is zero), so it is an end-point API rather than a shared utility. It is typically invoked from Oracle Forms, from concurrent programs that synchronize subscriber or contact language data, or from custom PL/SQL that must align a person's primary language with an external source. Callers should invoke it in a well-defined transaction, inspect the returned status and message data for error handling, and note that the internal use of HZ_PERSON_INFO_V2PUB is encapsulated — direct calls to those underlying APIs are unnecessary. The hard-coded application identifier (672) and the absolute path to the package body confirm this is an application-level object; it should be treated as read-only and never modified. Testing on 12.1.1 and 12.2.2 confirms identical behavior.