Search Results create_phone_contact_point

Overview

FND_OID_USERS is an Oracle E-Business Suite internal PL/SQL package that performs Oracle Internet Directory (OID) to TCA (Trading Community Architecture) user provisioning and synchronization. Its business function is to create and maintain the registry records that represent OID users as parties, party sites, locations, and contact points within the Oracle EBS data model. The package header constants (G_PERSON, G_LOCATION, G_BUSINESS, G_PERSONAL, G_PHONE, G_EMAIL, G_HZ_PARTIES, G_HZ_PARTY_SITES, G_HZ_CONTACT_POINTS, and the various generation and status flags) reflect its role in mapping LDAP user attributes onto HZ entities. It is classified as an "OTHER" API owned by APPS and carries an internal FND designation, indicating it is intended to be invoked by Oracle's own directory integration infrastructure rather than by general customer code.

Key Procedures and Functions

The package exposes 19 documented procedures and functions, divided into creation, update, retrieval, and reference-management groups.

• HZ_CREATE — Top-level entry point that creates TCA entities to reflect an OID user, taking an LDAP message payload and returning a status.
• CREATE_PARTY — Creates a person party record derived from the supplied LDAP attributes.
• CREATE_PHONE_CONTACT_POINT / CREATE_EMAIL_CONTACT_POINT — Create phone and e-mail contact point records for a party.
• CREATE_LOCATION — Creates the location (address) record associated with a party site.
• CREATE_PARTY_SITE — Creates the party site linking a party to a location.
• HZ_UPDATE — Top-level synchronization entry point that updates TCA entities to match changed OID user data.
• UPDATE_PARTY / UPDATE_PHONE_CONTACT_POINT / UPDATE_EMAIL_CONTACT_POINT / UPDATE_PARTY_SITE — Apply modifications to the corresponding TCA records.
• GET_PERSON_REC, GET_CONTACT_POINT_REC, GET_LOCATION_REC, GET_PARTY_SITE_REC — Retrieval helpers that locate existing records for comparison and synchronization.
• GET_ORIG_SYSTEM_REF, CREATE_ORIG_SYSTEM_REFERENCE, UPDATE_ORIG_SYSTEM_REFERENCE — Manage the origin system reference entries that tie TCA records back to their OID source identity.
• TEST — A diagnostic routine used to validate package behavior.

Tables Accessed

The package operates against the core HZ registry tables and supporting FND objects through APPS synonyms:

• HZ_PARTIES — Stores the person or organization party rows created for each OID user.
• HZ_PARTY_SITES and HZ_LOCATIONS — Hold party site and address information synchronized from LDAP attributes.
• HZ_CONTACT_POINTS — Stores phone and e-mail contact points.
• HZ_ORIG_SYS_REFERENCES — Links TCA records to the originating OID entries.
• HZ_PARTY_NUMBER_S and HZ_PARTY_SITE_NUMBER_S — Sequences used to generate party and party site numbers, consistent with the G_HZ_GENERATE_PARTY_NUMBER and G_HZ_GENERATE_PS_NUMBER constants.
• FND_USER — The EBS application user account associated with the directory user.
• FND_TERRITORIES — Territory validation for address data.
• DUAL — Used for scalar lookups and sequence access.

Usage Notes

FND_OID_USERS is invoked as part of Oracle's OID/LDAP integration workflow, typically through the directory synchronization infrastructure referenced by the G_FND_OID_SYNCH constant. It is not a general-purpose public API. The package is referenced by three other packages, and its procedures are called internally when OID user events (creation or modification) are propagated into EBS. Custom code should not call these procedures directly; integration points should instead use supported TCA APIs such as HZ_PARTY_V2PUB or the FND_USER_PKG. The p_ldap_message parameter type (FND_OID_UTIL.LDAP_MESSAGE_TYPE) confirms the package consumes already-parsed LDAP attribute collections, and the x_return_status out parameter follows standard EBS API error-handling conventions for the caller to evaluate success or failure.