Results for “ego_party_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EGO_PARTY_PUB is a public PL/SQL package body owned by the APPS schema within Oracle E-Business Suite. It forms part of the Oracle EGO (Enterprise Group and Party) infrastructure that underpins Oracle's Trading Community Architecture (TCA) and user-provisioning features. The package exposes a set of public APIs that application code, Oracle Forms, and concurrent programs use to manage party-related operations, including group creation and membership maintenance, email address retrieval, code assignment handling, and enterprise user setup. As an application programming interface classified as PUB, its procedures are intended for external invocation and are supported entry points into the underlying EGO and HZ tables.

Because the package body header references revisions dating to 2010, it is a long-standing component present in both Oracle EBS 12.1.1 and 12.2.2. The 12.2.2 ETRM metadata records eleven documented procedures, and the package is referenced by two other packages, confirming its role as a shared service layer rather than a standalone utility.

Key Procedures and Functions

The documented procedures fall into several functional clusters:

• GET_APPLICATION_ID — Returns the application identifier associated with the party-related processing context, used by callers to resolve the owning application.
• CREATE_GROUP — Creates a new group party, typically establishing a membership-based grouping used in TCA relationship structures.
• UPDATE_GROUP — Modifies the attributes of an existing group.
• DELETE_GROUP — Removes a previously defined group.
• ADD_GROUP_MEMBER — Adds a party to an existing group, establishing the membership relationship between the member and the group.
• REMOVE_GROUP_MEMBER — Removes a party from a group, terminating the membership relationship.
• GET_EMAIL_ADDRESS — Retrieves the email address associated with a party or contact, sourced from contact point data.
• CREATE_CODE_ASSIGNMENT — Creates a code assignment record linking a classification code to a party entity.
• UPDATE_CODE_ASSIGNMENT — Updates an existing code assignment.
• SETUP_ENTERPRISE_USER — Provisions an enterprise user, coordinating FND_USER and party-related setup.
• SETUP_ENTERPRISE_USER_CP — A companion routine supporting enterprise user setup, likely aligned to contact point handling.

The package body also contains internal helper procedures such as code_debug and mdebug, which write diagnostic output through FND_LOG. These are not public APIs but support troubleshooting.

Tables Accessed

The package reads from and writes to the following tables via APPS synonyms:

• FND_APPLICATION — Resolves application identifiers used by GET_APPLICATION_ID.
• FND_GRANTS and FND_MENUS — Support user provisioning and responsibility/menu grant logic during enterprise user setup.
• FND_OBJECTS — Provides object metadata referenced during user and function security configuration.
• FND_USER — The core user repository written to during enterprise user setup.
• HZ_CODE_ASSIGNMENTS — Stores classification code assignments created or updated by the code assignment APIs.
• HZ_CONTACT_POINTS — Holds contact point data, including email addresses retrieved by GET_EMAIL_ADDRESS.
• HZ_PARTIES — The central party registry for groups and members.
• HZ_RELATIONSHIPS — Stores the membership relationships established by ADD_GROUP_MEMBER and REMOVE_GROUP_MEMBER.
• PER_ALL_PEOPLE_F — Provides person records, typically to link users and parties to HR persons.

Usage Notes

EGO_PARTY_PUB is typically invoked from Oracle Forms, concurrent programs, and custom PL/SQL code that needs to manage groups, memberships, code assignments, or enterprise users without directly manipulating the underlying TCA and FND tables. Because it is a PUB-classified API, callers are expected to use the standard API conventions, including API version and initialization message list parameters, to ensure compatibility and predictable error handling.

The presence of debug-level globals and the FND_LOG-based code_debug helper indicates the package supports diagnostic tracing during execution, which is valuable when troubleshooting user setup or group membership failures. When extending or integrating with this package in 12.1.1 or 12.2.2, developers should call the documented public procedures rather than the internal helpers, and should verify the current package version, as revisions across releases may alter behavior.