Search Results organization_rec_type

Overview

APPS.JTF_UM_REGISTER_USER_PVT is a private (PVT) PL/SQL package belonging to the Oracle E-Business Suite User Management infrastructure. Its declared purpose is to define the specifications for PL/SQL records and tables that are consumed by the registration handlers responsible for creating and managing user accounts within Oracle EBS 12.1.1 and 12.2.2. The package is compiled with AUTHID CURRENT_USER, meaning that its execution privileges and schema resolution are governed by the invoking user rather than by the package owner. The source header indicates a revision level of 115.5, last modified in 2002, and the package resides in the APPS schema despite carrying the PVT designation reserved for internal, non-public APIs.

Functionally, the package serves as a data structure definition layer for the user registration flow. By declaring strongly typed record structures, it standardizes the shape of the data passed between registration handlers and the underlying Oracle Trading Community Architecture (TCA) and FND_USER entities. Registration logic in the JTF User Management module depends on these records to assemble person and organization attributes before persistence.

Key Procedures and Functions

The documented ETRM metadata lists zero procedures or functions for this package. This is consistent with a specification-only package whose primary contribution is the declaration of composite data types rather than executable business logic. The package exposes two central record types:

• Person_rec_type — A record defining the attributes required to register an individual user, including first name, last name, username, password, phone area code, phone number, email address, party identifier, user identifier, active start date, and a privacy preference flag defaulting to 'NO'.
• Organization_rec_type — A record defining the attributes required to register an organization, including organization number, organization name, multiple address lines, city, state, postal code, county, province, phonetic address line, country, phone and fax details, and organization and contact party identifiers.

A global default record, G_MISS_Person_Rec, is also declared from the person record type, providing a baseline template that handlers can reference or reset against. Because no callable units are documented, the package should be regarded as a supporting declaration artifact within the registration subsystem rather than an entry point for direct invocation.

Tables Accessed

Although the package contains no executable code, the record declarations anchor their field types to columns in four documented tables, resolved through APPS synonyms:

• FND_USER — Supplies the types for username, email address, and user identifier, tying registration records directly to the EBS application user account.
• HZ_PARTIES — Provides types for person and organization names, party number, party identifier, and the address and country attributes used in the organization record.
• HZ_CONTACT_POINTS — Provides types for phone area codes, phone numbers, and fax numbers associated with both persons and organizations.
• HZ_LOCATIONS — Supplies the type for the phonetic address line field in the organization record.

This anchoring ensures that registration handlers operate with type-safe variables that remain aligned with the underlying TCA and FND_USER schema definitions.

Usage Notes

As a PVT API, this package is intended for internal consumption by the user registration handlers rather than for direct call by customers or integrators. The ETRM metadata records that it is referenced by four other packages, confirming its role as a shared declaration dependency within the JTF User Management module. Typical invocation therefore occurs indirectly: registration flows — whether driven by self-service registration pages, administrative forms, or concurrent processes that create users — populate Person_rec_type and Organization_rec_type instances and pass them to the handler packages that reference this specification. Custom code should avoid depending on these private structures, as Oracle does not guarantee their stability across patch levels or releases. Developers requiring registration functionality should use the supported public APIs in the JTF User Management layer instead.