Search Results g_fnd_oid_synch

Overview

FND_OID_USERS is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that provides the integration layer between Oracle Internet Directory (OID) and the Oracle Trading Community Architecture (TCA) and FND user model. Its primary business function is to synchronize user and person data originating from an LDAP directory into EBS as TCA parties, party sites, contact points, and original system references. The package is the recipient of inbound LDAP messages — represented by the fnd_oid_util.ldap_message_type record — and translates attributes such as sn, givenName, telephoneNumber, homePhone, mail, c, and street into corresponding TCA entities.

The header comment identifies the source file as AFSCOURB.pls (version 120.6), indicating this package has historically been part of the Oracle CRM/Foundation user provisioning stack. It is referenced by three other packages, confirming its role as a shared utility rather than an entry-point-only routine. The package adheres to standard EBS API conventions: OUT NOCOPY x_return_status parameters set to Fnd_Api.G_RET_STS_SUCCESS, and FND_LOG instrumentation gated on fnd_log.G_CURRENT_RUNTIME_LEVEL. The user search term g_fnd_oid_synch relates to the broader OID synchronization configuration context in which this package executes.

Key Procedures and Functions

The package exposes nineteen documented procedures and functions, organized around create, update, and retrieval operations against TCA and user data:

• HZ_CREATE — Top-level entry point for creating a party from an inbound LDAP message. Validates that sn or givenName is present before delegating to CREATE_PARTY.
• CREATE_PARTY — Creates a TCA party record (HZ_PARTIES) for the incoming person, including name components.
• CREATE_PHONE_CONTACT_POINT — Creates a telephone contact point (HZ_CONTACT_POINTS) for LDAP phone attributes.
• CREATE_EMAIL_CONTACT_POINT — Creates an e-mail contact point from the LDAP mail attribute.
• CREATE_LOCATION — Creates an HZ_LOCATIONS record for the person's address.
• CREATE_PARTY_SITE — Associates a location with a party via HZ_PARTY_SITES.
• HZ_UPDATE — Top-level entry point for updating an existing party from an LDAP message.
• UPDATE_PARTY, UPDATE_PHONE_CONTACT_POINT, UPDATE_EMAIL_CONTACT_POINT, UPDATE_PARTY_SITE — Component-level update routines mirroring the create operations.
• GET_PERSON_REC, GET_CONTACT_POINT_REC, GET_LOCATION_REC, GET_PARTY_SITE_REC — Retrieval functions that fetch existing TCA records before update or for de-duplication.
• GET_ORIG_SYSTEM_REF, CREATE_ORIG_SYSTEM_REFERENCE, UPDATE_ORIG_SYSTEM_REFERENCE — Manage HZ_ORIG_SYS_REFERENCES, binding the LDAP distinguished name (or similar source key) to the TCA entity for cross-system traceability.
• TEST — A diagnostic routine for validating the package's behavior.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

• HZ_PARTIES — Core person/organization records created and updated by CREATE_PARTY and UPDATE_PARTY.
• HZ_PARTY_NUMBER_S — Sequence used to generate party numbers.
• HZ_CONTACT_POINTS — Phone and e-mail contact points.
• HZ_LOCATIONS — Address records for party sites.
• HZ_PARTY_SITES and HZ_PARTY_SITE_NUMBER_S — Party site associations and their sequence.
• HZ_ORIG_SYS_REFERENCES — Original system references linking LDAP identities to TCA entities.
• FND_USER — EBS application user records.
• FND_TERRITORIES — Country/territory validation derived from the LDAP c attribute.
• DUAL — Standard PL/SQL single-row operations.

Usage Notes

FND_OID_USERS is not typically invoked directly by end users. It executes within the OID-to-EBS user synchronization flow, called by the OID integration infrastructure and by the three packages that reference it. In EBS 12.1.1 and 12.2.2, this flow is associated with Oracle Internet Directory integration and single sign-on user provisioning. Whenever an LDAP message is received for a person with a surname or given name, HZ_CREATE or HZ_UPDATE is invoked to reflect that data in TCA. Custom code should not call HZ_CREATE or HZ_UPDATE without constructing a valid fnd_oid_util.ldap_message_type record and checking x_return_status against Fnd_Api.G_RET_STS_SUCCESS. Diagnostic logging is available by raising the FND_LOG runtime level for the fnd.plsql.oid.fnd_oid_users. module source. Because the package writes directly to TCA base tables via the supported APIs, changes should be applied in EBS environments where the OID profile options (including the synchronization flags referenced by g_fnd_oid_synch) are correctly configured.