Results for “okc_unexpected_error”

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

Overview

OKC_AR_INT_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the integration between Oracle Contracts (OKC) and Oracle Receivables (AR). Its principal business function is to expose contract contingency and rule data to the Receivables side of the application, so that billing, invoicing, and revenue-related processing can evaluate the contingencies defined against a contract or contract line before generating transactions.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the package owner. This characteristic is significant in an EBS environment because it means the effective schema and synonym resolution depend on the session context of the caller, and it also means that errors raised inside the package surface under the caller's privilege set.

The most commonly observed reference to this package is the global constant G_UNEXPECTED_ERROR, which is defined as the literal string 'OKC_UNEXPECTED_ERROR'. This constant is the source of the message token that users encounter as "OKC_UNEXPECTED_ERROR" in the EBS error dialog. The package embeds this constant in its standard message-handling framework alongside the SQL error message and SQL code tokens, so that any unhandled exception raised during contingency retrieval is reported to the caller with a generic unexpected-error label rather than a specific diagnostic.

The package also defines the global exception G_EXCEPTION_HALT_VALIDATION, which signals to the calling code that validation should stop. In practice, this is used to abort a contingency check cleanly rather than allowing processing to continue against inconsistent data.

Key Procedures and Functions

Only one program unit is documented in the package specification: GET_CONTRACT_CONTINGENCIES.

• GET_CONTRACT_CONTINGENCIES — Retrieves the set of contingencies that apply to a specified contract or contract line. The procedure follows the standard Oracle API conventions: it accepts an API version, an optional message-list initialization flag, a contract identifier, and a contract line identifier, and it returns a PL/SQL table of contingency records together with the standard return status, message count, and message data outputs. This conforms to the documented API error-handling model used throughout EBS, which is why the unexpected-error constant is central to the procedure.

Each contingency record carries a contingency type, a flag indicating whether the contingency is present, an expiration date, an expiration start event (defaulting to 'INVOICE'), an expiration duration, and a unit of measure for that duration. The default start event of INVOICE confirms that the intended consumer is the billing/invoicing process, which evaluates the contingency's expiration window relative to the invoice event.

The procedure does not introduce any other documented entry points; no additional public functions or procedures are recorded in the metadata.

Tables Accessed

The package accesses contract rule data through the following APPS synonyms:

• OKC_RULES_B — the base table holding contract rules, including contingency definitions. The procedure reads rule rows associated with the requested contract or line to build the contingency table returned to the caller.
• OKC_RULE_GROUPS_B — the base table holding rule group definitions, used to resolve the grouping structures under which rules and contingencies are organized for a contract.

Access is read-only in the documented behavior; the package returns contingency data rather than persisting it. The join between rule groups and rules allows the procedure to return the contingencies in the context of the rule groupings defined for the contract.

Usage Notes

OKC_AR_INT_PUB is invoked whenever Receivables-side logic needs to determine which contract contingencies apply before proceeding with invoice or billing operations. It is typically called from other server-side PL/SQL, from Oracle Forms-based contract and billing windows, or from custom extensions that mimic the AR/OKC integration.

The documented metadata records zero other packages referencing this one, which suggests the package is called primarily from form-level or program-unit code rather than from a broad chain of dependent public APIs. Because it uses AUTHID CURRENT_USER, callers must ensure that the invoking session has the necessary privileges on the three underlying objects through APPS synonyms; failure to do so, or failure inside the contingency query, is reported to the end user as the generic OKC_UNEXPECTED_ERROR message. When troubleshooting that message, the relevant investigation path is the SET_CONTRACT_CONTINGENCIES retrieval logic, the privileges of the invoking user, and the state of the OKC_RULES_B and OKC_RULE_GROUPS_B rows for the contract in question.