Search Results allocship_toomany_rtn

Overview

ITG_MSG is a centralized message-handling utility package in the Oracle E-Business Suite APPS schema. Its role is to provide a single library of user-facing message and error routines that other modules—particularly the procurement, receiving, invoicing, and intercompany translation subsystems—invoke to report validation failures, data conflicts, and processing exceptions in a consistent manner. The package source header identifies it as an ARCS-tracked file (itgmsgs.pls), placing it within the intercompany/invoice translation generation family of code. Rather than embedding literal warning strings throughout procedural logic, callers route user feedback through ITG_MSG so that message text, severity, and presentation remain uniform across the affected products. The metadata classifies the package under API classification OTHER, indicating it is not a public integration API but an internal support library. The documented surface area is broad: ninety-six procedures and functions are catalogued in ETRM 12.2.2, and the package is referenced by eleven other packages, confirming its position as a shared dependency rather than an entry point.

Key Procedures and Functions

The documented routines fall into several groups, all oriented toward emitting diagnostic or validation messages:

• Generic output routines — TEXT, DEBUG, and DEBUG_MORE provide the base mechanisms for writing informational and troubleshooting output. DEBUG accepts a package name and procedure name to identify the origin of the message.
• Element and value validation — MISSING_ELEMENT_VALUE, DATA_VALUE_ERROR, and UPDATE_FAILED report absent inputs, out-of-range numeric values, and failed persistence attempts respectively.
• Flexfield and account handling — EXISTING_FLEX_VALUE, INVALID_ACCOUNT_TYPE, FLEX_INSERT_FAIL, FLEX_UPDATE_FAIL_NOVALUE, and FLEX_UPDATE_FAIL_NOTL address key flexfield conflicts and accounting type errors.
• Currency and exchange rate checks — INVALID_CURRENCY_CODE, SAME_CURRENCY_CODE, and DUPLICATE_EXCHANGE_RATE cover conversion-setup anomalies.
• Procurement and receiving checks — NO_PO_FOUND, NO_LINE_LOCS_FOUND, POLINE_CLOSED_RCV, POLINE_ZEROQTY_RCV, POLINE_NEGQTY_RCV (added for Bug 5438268), RECEIPT_TOL_EXCEEDED, receipt close and release failures, and the corresponding inspection routines POLINE_NEGQTY_INS, POLINE_ZEROQTY_INS, and INSPECT_TOL_EXCEEDED.
• Invoicing checks — POLINE_ZEROAMT_INV, POLINE_BADSIGN_INV, POLINE_CLOSED_INV, INVOICE_TOL_EXCEEDED, and the invoice close/release failure routines.
• Allocation safeguards — ALLOCSHIP_TOOMANY_RTN, ALLOCDIST_TOOMANY_RTN, and ALLOCREQN_TOOMANY_RTN.

Several routines accept a return code or originating identifier so the message can be correlated with the failed operation.

Tables Accessed

ETRM records no direct table references for this package through APPS synonyms. This is consistent with its design as a message formatter: its procedures accept already-retrieved values as parameters and raise or display messages rather than querying base tables. Where callers pass identifiers such as purchase order codes or organization IDs, those values are resolved upstream by the invoking package. The absence of documented table dependencies means the package carries minimal data-access risk and can be called from any context without additional privileges.

Usage Notes

ITG_MSG is invoked indirectly rather than by end users. The eleven dependent packages call its routines at validation and exception points during receiving, invoice matching, allocation, and intercompany processing, so the messages appear in Oracle Forms error dialogs, concurrent program output logs, and OAF pages driven by the calling logic. In Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and is generally not customized; extensions should call the exposed procedures rather than duplicate message text. Developers debugging a specific failure—such as an unexpected validation message or a missing value complaint—can trace the message string back to the corresponding ITG_MSG routine and then to its caller to identify the triggering condition. Because the parameter name p_sob does not appear in the documented signature list, references to it in search results likely originate from the intercompany or accounting context in which the package operates rather than from ITG_MSG itself; the set-of-books value would be resolved by the calling module before the message routine is reached.