Search Results p_show_flag




Overview
Explore in AI Chat

Overview

IGW_PROP_PERSON_DEGREES_TBH is a table handler package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Grants/Proposal Management (IGW) product family, specifically the subset that manages proposal personnel data. The package encapsulates the low-level DML logic required to maintain degree records associated with individuals listed on a proposal. In the EBS architecture, "TBH" suffices designate table handler routines that isolate row-level update, insert, and delete operations from the higher-level business APIs and the Oracle Forms user interface that invoke them. This separation allows validation, concurrency control, and audit column maintenance to be implemented consistently in PL/SQL rather than duplicated in form triggers. The package is classified under the ETRM metadata as an OTHER API and is documented with a single public procedure, UPDATE_ROW, which is the sole entry point exposed by the specification. Because the package deals with the SHOW_FLAG and DEGREE_SEQUENCE columns, it supports the presentation ordering and visibility control of degrees on proposal-related screens and reports. The header comment indicates the source file igwtppdb.pls at version 115.2, last shipped in March 2002, reflecting the long-standing stability of this component across releases.

Key Procedures and Functions

The documented interface contains one procedure:

  • UPDATE_ROW — Updates a single row in the proposal person degrees table identified by a ROWID. It accepts the row identifier together with the business key values for the proposal, the person degree, the show flag, and the degree sequence. An optimistic locking mechanism is implemented through a record version number parameter: the update statement includes a predicate on the current record version, and the version column is incremented by one on each successful update. When no row matches, the procedure raises the IGW_SS_RECORD_CHANGED message and sets the return status to an error indicator, signalling that the record was modified or removed by another user. Audit columns (last update date, last updated by, last update login) are populated from SYSDATE and FND_GLOBAL depending on the operating mode, with the mode parameter distinguishing an initialization context from a regular user context. Invalid mode values raise the FND SYSTEM-INVALID ARGS exception. The procedure also includes a WHEN OTHERS exception handler that logs the error text through FND_MSG_PUB and returns the unexpected error status defined in FND_API.

The user search term p_show_flag corresponds directly to the P_SHOW_FLAG parameter of UPDATE_ROW, which carries the visibility indicator written to the SHOW_FLAG column.

Tables Accessed

The package performs DML against a single table, accessed through its APPS synonym:

  • IGW_PROP_PERSON_DEGREES — Stores degree information for persons associated with proposals. The UPDATE_ROW procedure modifies the PROPOSAL_ID, PERSON_DEGREE_ID, SHOW_FLAG, DEGREE_SEQUENCE, audit columns, and the record version number for a row selected by ROWID. No other tables are referenced in the documented source.

Usage Notes

IGW_PROP_PERSON_DEGREES_TBH is normally invoked indirectly. Oracle Forms modules covering proposal personnel maintenance call the table handler during the save cycle, supplying the row identifier, current column values, the user's record version number, and an appropriate mode. Higher-level PL/SQL APIs may also delegate to UPDATE_ROW when programmatic updates to degree visibility or ordering are required. Custom extensions should call the procedure rather than issuing direct UPDATE statements, because the handler enforces record version checking and populates audit columns that would otherwise require manual coding. The ETRM metadata records that the package is referenced by one other package, confirming that it is a dependency of at least one higher-level routine within the IGW schema. Developers writing custom code should anticipate the IGW_SS_RECORD_CHANGED condition and handle the returned status value, and should avoid modifying the same row through direct SQL while a form session holds an uncommitted version.