Results for “create_organization”

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

Overview

IGW_ORGANIZATIONS_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Grants and Proposal (IGW) subsystem, which provides the shared organization, party, and address infrastructure used across Oracle Grants Management and related modules. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling user rather than the definer, and it is classified as a PVT (private) API. Private packages of this class are not intended for direct external invocation; they act as the internal implementation layer behind a corresponding public package that exposes the supported business interface.

The business function of IGW_ORGANIZATIONS_PVT is to manage the creation and maintenance of organization records — including name and address data — within the Oracle Trading Community Architecture (TCA) party model. Because organization data in EBS is ultimately stored as parties and party sites in the HZ (Trading Community) tables, this package encapsulates the logic for generating identifiers and persisting organization details while enforcing the standard EBS API conventions.

Key Procedures and Functions

The documented API surface consists of two procedures:

• CREATE_ORGANIZATION — Creates a new organization record. It accepts organization descriptive attributes such as the organization name, three address lines, city, state, postal code, county, country name, and an active flag, and returns the generated party identifier through an output parameter. Consistent with Oracle EBS API standards it supports initialization of the message list, a validate-only mode, and a commit flag, and it returns the standard return status, message count, and message data outputs.
• UPDATE_ORGANIZATION — Modifies an existing organization. In addition to the descriptive organization and address attributes carried by CREATE_ORGANIZATION, it accepts the party identifier and party version together with the location identifier and location version, allowing the procedure to apply optimistic locking against the current TCA record. It exposes the same initialization, validate-only, and commit controls, along with the standard return status and message outputs.

No public functions are documented for this package. The shared parameter conventions — p_init_msg_list, p_validate_only, p_commit, x_return_status, x_msg_count, and x_msg_data — follow the Fnd_Api standard used throughout Oracle Application Object Library.

Tables Accessed

The package references the following objects through APPS synonyms:

• HZ_PARTY_NUMBER_S — the TCA sequence used to generate unique party identifiers assigned to newly created organizations.
• HZ_PARTY_SITE_NUMBER_S — the TCA sequence used to generate unique party site identifiers for the associated address records.
• DUAL — the standard single-row pseudo-table used for sequence value retrieval and simple expression evaluation.

These references confirm that organization creation and update is persisted into the Oracle Trading Community Architecture, with this package responsible for sourcing primary keys from the HZ numbering sequences before handing the data to the underlying TCA party and location tables. ETRM records no other packages referencing IGW_ORGANIZATIONS_PVT, indicating it is invoked from within the IGW package family rather than by external subscribers.

Usage Notes

Because IGW_ORGANIZATIONS_PVT is a private API, it should be treated as an internal implementation component. In practice it is invoked by its sibling public package within the IGW application, which in turn is called from Grants forms, concurrent programs, or other Oracle Grants Management flows that need to register or amend supplier and applicant organization data. The standard validation pattern applies: callers may first execute with p_validate_only set to validate the input without persisting changes, and set p_commit to control transaction demarcation. Custom code should avoid calling this package directly and should instead use the supported public API, since private package signatures are not guaranteed to remain stable across patch levels. In the context of EBS 12.1.1 and 12.2.2, the package remains a lightweight wrapper focused on organization and address persistence within TCA.