Results for “update_party_status”

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

Overview

IBE_PARTY_V2PVT is a private PL/SQL package in the APPS schema that provides the foundational party- and user-creation logic for Oracle EBS self-service and iStore (IBE) functionality. It wraps the public TCA (Trading Community Architecture) APIs — principally HZ_PARTY_V2PUB, HZ_CONTACT_POINT_V2PUB, and HZ_LOCATION_V2PUB — into higher-level routines that create a complete registered user in a single call. Rather than requiring callers to invoke several TCA APIs and stitch their outputs together, this package orchestrates creation of the party, person or organization records, contact points, account, contact preferences, and the matching FND user, returning the resulting identifiers.

The version header (IBEVPARS.pls 120.1, dated 2005) indicates the package has been stable since the 11i era and is carried forward unchanged into 12.1.1 and 12.2.2. Its classification is OTHER, and it is referenced by two other packages, confirming it is an internal building block rather than a directly callable public API.

Key Procedures and Functions

The package exposes twelve documented procedures. The one most often queried, CREATE_INDIVIDUAL_USER, combines a username and password with person, email, and phone record types (work, home, and fax) plus a contact preference, and returns the person party ID, the FND user ID, and standard TCA return status, message count, and message data. In effect it registers a person as both a TCA party and an application user.

The remaining routines address related scenarios:

• CREATE_BUSINESS_USER — creates a person, an organization, a location, and the relationship between them, along with phone, fax, and email contact points, returning person, relationship, organization party, and user IDs.
• CREATE_ORG_CONTACT — establishes a person as either EMPLOYEE_OF or CONTACT_OF an existing organization party.
• CREATE_PERSON and CREATE_ORGANIZATION — create the underlying TCA party records without the user-account overhead.
• CREATE_ACCOUNT — creates the customer account associated with a party.
• CREATE_CONTACT_POINTS — creates phone, fax, and email contact points for a party or party site.
• UPDATE_CONTACT_PREFERENCE and UPDATE_PERSON_LANGUAGE — maintain the party’s preferred contact method and language.
• UPDATE_PARTY_STATUS — changes the active/inactive status of a party.
• FIND_ORGANIZATION — locates an existing organization party.
• SAVE_TCA_ENTITIES — persists related TCA entity changes in a coordinated fashion.

Tables Accessed

The package reads and writes the core TCA tables through APPS synonyms. Person, organization, and relationship data reside in HZ_PARTIES and HZ_RELATIONSHIPS; addresses and site associations use HZ_PARTY_SITES. Phone, fax, and email values are stored in HZ_CONTACT_POINTS, with the preferred channel held in HZ_CONTACT_PREFERENCES. Customer-account creation touches HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and the account number sequence HZ_ACCOUNT_NUM_S. Organization contact roles are recorded in HZ_ORG_CONTACTS, and language preference in HZ_PERSON_LANGUAGE. DUAL is used for sequence and utility queries.

Usage Notes

Because IBE_PARTY_V2PVT is a private package, it is not intended for direct invocation by external integrations. It is called internally by the two referencing packages, which in turn serve iStore registration flows, self-service user provisioning, and administrative forms where a party and its login must be created together. Customizations that need equivalent behavior should generally call the public HZ_PARTY_V2PUB and FND_USER_PKG APIs directly rather than this wrapper. Where the package is invoked, callers must check X_RETURN_STATUS and iterate the message stack via FND_MSG_PUB, since TCA errors are surfaced through X_MSG_COUNT and X_MSG_DATA rather than raised exceptions.