Results for “get_organization_bo”

22 results




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

Overview

POS_SUPPLIER_BO_DEP_PKG is a dependent (D-oriented) PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema, defined with AUTHID CURRENT_USER. It belongs to the Procurement/Supplier "POS" module family and is designed to supply supplier-side business object (BO) data to the Oracle Trading Community Architecture (TCA) and its Suppliers integration layer. The suffix "BO_DEP" indicates a dependency or helper package that assembles business object structures consumed by other supplier or TCA APIs rather than exposing a standalone public interface.

The package header (RCS revision 120.1, dated 25-Nov-2010, created 20-Aug-2009 by JAYASANKAR) declares three public subprograms: two procedures that build business objects for financial reporting and organization context, and one function that resolves a party identifier. Its role within EBS 12.1.1 and 12.2.2 is to bridge supplier records and the underlying TCA party model, supporting supplier data extraction, supplier reporting, and integration scenarios in which a supplier's financial and organizational profile must be assembled as a structured business object. This is directly relevant to the common user requirement of performing a supplier dump — that is, extracting supplier, party, and financial attributes for reporting, migration, or reconciliation purposes.

Key Procedures and Functions

  • GET_FINANCIAL_REPORT_BOS — Returns a collection of financial report business objects. It accepts an initialization flag, an organization identifier, and an action type, and returns the financial report object table (HZ_FINANCIAL_BO_TBL) together with the standard EBS API return status, message count, and message data outputs. It is used to assemble the financial reporting attributes associated with a supplier organization.
  • GET_ORGANIZATION_BO — Returns a single organization business object (HZ_ORGANIZATION_BO) for a given organization identifier, again with the standard API output parameters and an action type. It provides the organizational profile representation of a supplier or party.
  • GET_PARTY_ID — A function that resolves and returns a party identifier given an originating system and originating system reference. This supports cross-referencing of supplier records held in legacy or external systems against TCA HZ_PARTIES.

No parameter lists beyond those documented in the header are asserted here; the descriptions above reflect the declared signatures as published.

Tables Accessed

The package reads and derives data from the following TCA tables via APPS synonyms:

These tables constitute the supplier/party data set typically extracted in a supplier dump.

Usage Notes

POS_SUPPLIER_BO_DEP_PKG is referenced by 11 other packages, indicating it functions primarily as a shared dependency rather than a directly called entry point. It is typically invoked from supplier-facing APIs, TCA integration code, and custom extraction routines that require assembled supplier or organization business objects. Because it is declared AUTHID CURRENT_USER, it executes with the privileges of the calling user, so callers must possess the necessary grants on the underlying HZ tables.

When performing a supplier dump for reporting or migration, developers generally resolve party identifiers through GET_PARTY_ID, then retrieve organizational and financial context via GET_ORGANIZATION_BO and GET_FINANCIAL_REPORT_BOS. Callers should honor the FND_API return status convention, checking x_return_status, x_msg_count, and x_msg_data for error handling. As with all Oracle EBS APIs, direct modification of the package is not supported; use should be limited to documented calls and wrapped in standard exception handling.