Search Results p_line_sequence

Overview

The APPS.IGW_PROP_PERSON_BIOSKETCH_TBH package body is a table handler (the _TBH suffix denotes "Table Handler") in the Oracle E-Business Suite Grants and Proposal Management module. It provides a controlled, API-based interface for maintaining records in the IGW_PROP_PERSON_BIOSKETCH table, which stores the biographical sketch information associated with personnel named on a proposal. Within the Oracle EBS 12.1.1 and 12.2.2 architecture, table handlers such as this one encapsulate DML logic so that callers never update the underlying table directly, thereby enforcing consistent concurrency control, audit column maintenance, and error handling. The package is owned by APPS and is classified as an OTHER API in the ETRM repository.

Key Procedures and Functions

The package exposes a single documented procedure, UPDATE_ROW. Its purpose is to update an existing row in the IGW_PROP_PERSON_BIOSKETCH table. The procedure identifies the target row through the X_ROWID parameter and accepts the column values to be written—P_PROPOSAL_ID, P_PERSON_BIOSKETCH_ID, P_SHOW_FLAG, and P_LINE_SEQUENCE—as well as a P_MODE indicator and a P_RECORD_VERSION_NUMBER used for optimistic locking. It returns a status through X_RETURN_STATUS.

The P_MODE parameter governs how the audit columns are populated. When set to 'I' (initial or interface mode), the procedure assigns LAST_UPDATED_BY as 1 and LAST_UPDATE_LOGIN as 0. When set to 'R' (runtime mode, the default), it derives these values from FND_GLOBAL.USER_ID and FND_GLOBAL.LOGIN_ID, substituting -1 when either is null. Any other mode raises the standard FND exception SYSTEM-INVALID ARGS. On a successful update, RECORD_VERSION_NUMBER is incremented to reflect the new row version.

Tables Accessed

The package performs DML against a single documented table, IGW_PROP_PERSON_BIOSKETCH, accessed through its APPS synonym. This table holds the per-person biographical sketch records linked to a proposal, including the display flag (SHOW_FLAG) and the ordering column (LINE_SEQUENCE) that determine where each biographical sketch appears in proposal output. The procedure also maintains the standard Oracle audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the RECORD_VERSION_NUMBER column directly on this table.

Usage Notes

This table handler is typically invoked indirectly rather than called by end users. It is referenced by one other package within the APPS schema, which acts as a higher-level API or business logic layer that delegates row-level updates to UPDATE_ROW. In the Oracle EBS Grants module, such handlers are commonly reached from Oracle Forms-based maintenance screens, from concurrent programs, or from custom PL/SQL extensions that manipulate proposal personnel data.

Two usage considerations merit emphasis. First, callers must supply the correct X_ROWID and the current P_RECORD_VERSION_NUMBER; if the row has been changed since the version number was read, the SQL%NOTFOUND check triggers message IGW_SS_RECORD_CHANGED and X_RETURN_STATUS is set to 'E', providing optimistic concurrency protection. Second, the exception handler logs the error through FND_MSG_PUB.ADD_EXC_MSG using the package and procedure names and re-raises the exception after setting the return status to FND_API.G_RET_STS_UNEXP_ERROR. The P_LINE_SEQUENCE parameter is the field that controls the display ordering of biographical sketches in proposal documents, and it is written only through this controlled update path.