Results for “add_group_member”

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

Overview

APPS.EGO_PARTY_PUB is a public PL/SQL API package belonging to the Oracle E-Business Suite product family associated with the EGO (Oracle Product Information Management / Advanced Product Catalog) schema. Its primary business purpose is to manage party-related entities — groups of parties, party relationships, contact points, and code assignments — and to provision enterprise users within the EBS environment. The package acts as a controlled interface layer that shields calling code from the underlying complexity of the Trading Community Architecture (TCA) data model, which stores party, contact point, and relationship information across HZ_PARTIES, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS.

The package declares several public record types, including PARTY_REC_TYPE, GROUP_REC_TYPE, and RELATIONSHIP_REC_TYPE, along with associated "missing" constant records (for example, G_MISS_PARTY_REC and G_MISS_GROUP_REC). These record structures enable callers to pass structured, attribute-rich payloads — including the standard twenty-four DFF attribute columns and a content source type defaulting to USER_ENTERED — into the group and party APIs without requiring direct DML against TCA base tables.

Key Procedures and Functions

The documented public interface exposes eleven procedures and functions. GET_APPLICATION_ID returns the application identifier, typically used to resolve the appropriate FND_APPLICATION context for subsequent API calls. CREATE_GROUP, UPDATE_GROUP, and DELETE_GROUP provide the full lifecycle management of party groups, operating on the GROUP_REC_TYPE record. ADD_GROUP_MEMBER and REMOVE_GROUP_MEMBER maintain the association between individual parties and the groups to which they belong.

GET_EMAIL_ADDRESS retrieves the email contact point for a given party, reading from the contact point structures exposed through HZ_CONTACT_POINTS. CREATE_CODE_ASSIGNMENT and UPDATE_CODE_ASSIGNMENT manage classified code assignment records stored in HZ_CODE_ASSIGNMENTS, which support classification and category tagging of parties and related entities. Finally, SETUP_ENTERPRISE_USER and its companion SETUP_ENTERPRISE_USER_CP provision enterprise user accounts, coordinating with FND_USER and related security tables to establish login identities linked to underlying party and person records. The "_CP" variant supports a customized or concurrent-processing invocation path. Parameter lists are not published in the available metadata; callers should consult the package specification (EGOPRTYS.pls) for exact signatures.

Tables Accessed

The package references the following tables through APPS synonyms: FND_APPLICATION and FND_OBJECTS for application and object registration context; FND_USER, FND_GRANTS, and FND_MENUS for enterprise user provisioning and responsibility/menu grant setup; HZ_PARTIES as the master party entity; HZ_CONTACT_POINTS for email and other contact mechanisms; HZ_RELATIONSHIPS for party-to-party associations; HZ_CODE_ASSIGNMENTS for classification codes; and PER_ALL_PEOPLE_F to link enterprise users to HR person records. These tables reflect the integration between TCA party data and EBS functional security and HR structures.

Usage Notes

EGO_PARTY_PUB is typically invoked from PL/SQL-based forms, concurrent programs, and custom extensions that need to create or maintain party groups, code assignments, and enterprise user accounts without issuing direct DML against TCA or FND tables. Because it is classified as a public (PUB) API, it is intended for supported external invocation and abstracts validation and multi-org/security rules. Two other packages reference it, indicating its role as a shared dependency within the EGO product layer. Developers should always call the public procedures rather than manipulating the underlying tables directly, and should verify the current specification version, as the header indicates a 2006 revision level (120.1). The package is documented for both EBS 12.1.1 and 12.2.2, with the 12.2.2 ETRM metadata listing the eleven procedures and the tables above.