Results for “hz_organization_bo_pub”

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

Overview

APPS.HZ_ORGANIZATION_BO_PUB is the Organization Business Object API within Oracle Trading Community Architecture (TCA). It exposes a public PL/SQL interface that allows callers to create, update, save, and retrieve organization business objects in the TCA model. The package is classified as a public API (API classification: PUB) in Oracle E-Business Suite 12.1.1 and 12.2.2, and is owned by the APPS schema. Its documented purpose is to manage organization business objects, including creation and update of the business object, with validation of business object completeness controlled by the caller.

The package header of record is ARHBPOBS.pls (header revision 120.7, dated 2006/09/21), and the API is registered under the product HZ with an active lifecycle, the display name "Organization Business Object API," and the business entity HZ_ORGANIZATION. This object is the programmatic entry point for organization-level business object processing, distinct from the lower-level party and location APIs, and is intended to be called through published procedure signatures rather than modified directly.

Key Procedures and Functions

ETRM documents 19 procedures and functions for this package. The externally callable, documented entries are:

• CREATE_ORGANIZATION_BO — Creates an organization business object. It accepts an initialization flag for the message stack, a business object validation flag, the organization object, and the creating module identifier, and returns status, message count, message text, and the generated organization identifiers (organization ID, original system, and original system reference).
• UPDATE_ORGANIZATION_BO — Updates an existing organization business object.
• SAVE_ORGANIZATION_BO — Inserts or updates an organization business object in a single call.
• GET_ORGANIZATION_BO — Retrieves a single organization business object.
• GET_ORGANIZATIONS_CREATED — Returns organizations recorded as created.
• GET_ORGANIZATIONS_UPDATED — Returns organizations recorded as updated.
• GET_ORGANIZATION_UPDATED — Returns a specific updated organization record.
• GET_IDS_ORGANIZATIONS_CREATED — Returns identifiers for organizations recorded as created.
• GET_IDS_ORGANIZATIONS_UPDATED — Returns identifiers for organizations recorded as updated.

The package also documents internal worker routines that implement the above: DO_CREATE_ORGANIZATION_BO, DO_UPDATE_ORGANIZATION_BO, and DO_SAVE_ORGANIZATION_BO. These are not intended for direct external invocation. Callers are expected to honor the standard message-stack and return-status conventions of the TCA public APIs when interpreting results.

Tables Accessed

The package operates against the following tables, referenced through APPS synonyms:

• HZ_PARTIES — The core TCA party table, holding the party record that underlies the organization entity.
• HZ_BUS_OBJ_TRACKING_S — Sequence used to generate business object tracking identifiers.
• HZ_DUP_SETS — Duplicate sets used during validation and matching processing.
• HZ_MATCHED_PARTIES_GT — Global temporary table holding matched party results used by the matching flow.
• DUAL — Used for single-row evaluation and scalar lookups.
• PLITBLM — PL/SQL integer table type used for index-by table manipulation.

These tables support the creation and update lifecycle, identifier assignment, and duplicate detection behavior of the business object.

Usage Notes

HZ_ORGANIZATION_BO_PUB is a public API and is referenced by three other packages, indicating it is a foundational component of TCA organization processing rather than a top-level user interface entry. In Oracle EBS 12.1.1 and 12.2.2, it is typically invoked from TCA forms, from concurrent programs that bulk-process customer and organization data, and from custom PL/SQL integration code that must create or maintain organization business objects while respecting TCA validation, duplicate detection, and upsert semantics. Callers should initialize the message stack, pass the business object validation flag deliberately, and inspect x_return_status, x_msg_count, and x_msg_data to determine the outcome. Direct DML against the underlying tables should be avoided in favor of this API.