Search Results csi_t_ui_pvt




Overview
Explore in AI Chat

Overview

CSI_T_UI_PVT is a private PL/SQL package body in the APPS schema that supports the user interface and transaction-processing layer of Oracle's Converged Supply Chain Intelligence / Transactional (CSI/T) framework. It is classified as a PVT (private) API, meaning it is not intended as a public integration point and is instead consumed internally by a small set of dependent packages. Its primary business purpose is to provide standardized wrapper routines and lightweight record constructors used when processing inbound or outbound inventory and procurement-related transactions through the UI, normalizing error constants, validation flags, and date/number sentinel values against the FND_API standard.

Key Procedures and Functions

The package exposes eleven documented functions, several of which are thin utility helpers around FND_API globals:

  • G_MISS_NUM, G_MISS_CHAR, G_MISS_DATE — Return the FND_API "missing value" sentinels for number, varchar2, and date datatypes respectively. These are used to flag attributes that were not supplied in an API call.
  • G_VALID_LEVEL — Translates a textual validation level (NONE, FULL) into the corresponding FND_API numeric constant. Any unrecognized value triggers an exception message via FND_MSG_PUB and raises FND_API.G_EXC_UNEXPECTED_ERROR.
  • G_BOOLEAN — Converts the text strings 'TRUE'/'FALSE' into FND_API.G_TRUE or FND_API.G_FALSE, again raising an unexpected-error exception on invalid input.
  • GET_ERROR_CONSTANT — Maps an error-state string ('G_RET_STS_ERROR', 'G_RET_STS_UNEXP_ERROR', 'G_RET_STS_SUCCESS') to the matching FND_API return-status constant. This is the routine most directly relevant to the user's search term and is used wherever callers need to transfer or compare a status value returned from an API.
  • UI_TXN_SOURCE_REC, UI_TXN_SOURCE_PARAM_REC, UI_TXN_LINE_REC, UI_PARTNER_ORDER_REC — Constructor-style functions that return initialized record structures for a transaction source, its parameters, its line detail, and its partner-order context. These populate the UI-layer record types defined elsewhere in CSI_T_UI_PVT.
  • GET_SRC_TXN_TYPE_ID — Resolves the transaction type identifier for a given source, used when classifying records during UI transaction intake.

Tables Accessed

The package references three base tables through APPS synonyms:

  • MTL_SYSTEM_ITEMS — The item master, consulted to resolve and validate item identifiers associated with transaction lines.
  • OE_ORDER_LINES_ALL — Order Management sales order lines, used when a transaction source is a sales order and line context must be derived.
  • PO_REQUISITION_LINES_ALL — Purchasing requisition lines, used when the transaction source is an internal requisition.

Only the GET_SRC_TXN_TYPE_ID routine is expected to perform these lookups; the remaining functions are pure value helpers that touch no tables.

Usage Notes

Because CSI_T_UI_PVT is a PVT package, it is invoked indirectly by the four dependent packages ETRM identifies rather than called directly from forms or concurrent programs. Its helpers are most commonly reached from within PL/SQL that builds or parses CSI/T transaction payloads, in particular when translating stored or persisted error strings back into FND_API constants using GET_ERROR_CONSTANT, and when assembling UI transaction records prior to validation. Custom code that must interoperate with these private APIs should call the public parent interface instead, since the PVT signature is subject to change between the 12.1.1 and 12.2.2 releases.