Search Results get_party_id

Overview

APPS.OE_CREDIT_SUMMARIES_PKG is a PL/SQL package in Oracle E-Business Suite that maintains the OE_CREDIT_SUMMARIES table, the operational store of aggregated credit exposure balances used by Order Management for credit checking. The package encapsulates the data-maintenance logic required to create, modify, and remove credit summary rows, providing a controlled interface between credit-checking processes and the underlying summary table so that direct DML against OE_CREDIT_SUMMARIES is not required.

The package header carries a version stamp of OEXCRSMB.pls 115.3 with a last modification date of 20-OCT-2003, identifying it as a long-standing, stable component of the Order Management credit architecture. Its API classification is OTHER, which indicates that it is an internal maintenance package rather than a formally published public API, and it is referenced by one other package within the EBS code base.

Key Procedures and Functions

The documented interface of the package body comprises three maintenance procedures alongside the function that the user searched for.

• get_party_id — Although not enumerated in the API register, this function is present in the package body source shown in the documentation. It accepts a customer account identifier and resolves the corresponding party identifier by querying HZ_CUST_ACCOUNTS. When no matching row exists, the NO_DATA_FOUND handler returns a NULL value and writes a message through OE_DEBUG_PUB. Unexpected errors are intercepted by the OTHERS handler, which conditionally logs a message via OE_MSG_PUB and then re-raises the exception. The function is used to translate a transactional customer account reference into the trading partner key required by credit summary processing.
• Insert_Row — Inserts a new row into OE_CREDIT_SUMMARIES. Its parameter set covers customer account, operating unit (org_id), site use, currency, balance type, balance amount, and the standard WHO audit columns (creation and last-update dates and user identifiers), confirming that the package preserves full auditability of credit summary records.
• Update_Row — Modifies an existing credit summary record, typically to refresh a balance figure after orders are booked, invoiced, or otherwise change the customer's outstanding exposure.
• Delete_Row — Removes a credit summary record, supporting cleanup of obsolete or no-longer-required summary lines.

Tables Accessed

• HZ_CUST_ACCOUNTS — Read-only access. The package queries this Trading Community Architecture table to obtain the party_id associated with a given cust_account_id, establishing the party-level identity used for credit aggregation across customer accounts.
• OE_CREDIT_SUMMARIES — The central table maintained by the package. It holds summarized credit balances keyed by customer account, operating unit, site use, currency, and balance type. The Insert_Row, Update_Row, and Delete_Row procedures perform the corresponding DML operations against this table.

Both tables are referenced through APPS synonyms, consistent with standard EBS coding practice in the 12.1.1 and 12.2.2 releases.

Usage Notes

OE_CREDIT_SUMMARIES_PKG is an internal, non-public API and is therefore not intended for direct invocation by customer extensions. It is typically called by Order Management credit-checking and order-processing logic, including concurrent programs that rebuild or refresh credit exposure summaries, and by forms that display or amend credit information. Custom development should avoid calling the procedures directly because their signatures and behaviour are not governed by Oracle's public API policy; instead, consumers should rely on the documented, supported credit-checking interfaces that ultimately drive this package.

The presence of OE_DEBUG_PUB and OE_MSG_PUB calls throughout the source means the package participates in the standard EBS debug and message-stack framework. Enabling OE debug at an appropriate level will surface the diagnostic text emitted by get_party_id, which is useful when diagnosing credit-check failures caused by missing or mismatched customer account records. The relationship between HZ_CUST_ACCOUNTS and OE_CREDIT_SUMMARIES also means the package depends on correct Customer Account setup; a cust_account_id without a corresponding customer account row will yield a NULL party identifier rather than an error, so validation of input identifiers is advisable in any surrounding code.