Search Results g_miss_content_source_type

Overview

The APPS.HZ_FINANCIAL_NUMBERS_PKG package body encapsulates the core create, read, update, and delete (CRUD) operations for the HZ_FINANCIAL_NUMBERS entity within the Oracle E-Business Suite Trading Community Architecture (TCA). Financial numbers represent quantitative reporting values associated with a financial report, such as projected or actual financial figures parsed by units, currency, and reporting period. The package exists to give forms, concurrent programs, and other PL/SQL APIs a controlled, consistent mechanism for persisting these records while enforcing attribute defaults, surrogate key generation, object versioning, and optimistic locking semantics.

The package body is physically delivered in the file ARHOFNTB.pls and carries the header revision identifier 120.5 dated 2005/05/25. It is classified under ETRM as an OTHER API, meaning it is a supporting persistence layer rather than a public multi-attribute business API. Five procedural entry points are documented: INSERT_ROW, UPDATE_ROW, LOCK_ROW, DELETE_ROW, and SELECT_ROW.

Key Procedures and Functions

• INSERT_ROW — Creates a new row in HZ_FINANCIAL_NUMBERS. The procedure accepts the financial number identifier as an IN OUT NOCOPY parameter, together with a ROWID output, and the substantive attributes: financial report reference, financial number, name, units applied, currency, projected/actual flag, content source type, status, object version number, created-by module, and actual content source.
• UPDATE_ROW — Modifies an existing financial number record, applying supplied attribute values and advancing the object version number for optimistic concurrency control.
• LOCK_ROW — Acquires a row-level lock on a financial number record for the duration of the calling transaction, preventing concurrent modification while dependent logic executes.
• DELETE_ROW — Physically removes a financial number row identified by its primary key.
• SELECT_ROW — Retrieves a single financial number record into the supplied out parameters, typically used to populate form blocks or to retrieve the current state before an update.

Tables Accessed

• HZ_FINANCIAL_NUMBERS — The primary transactional table holding financial number records. The package performs INSERT, UPDATE, DELETE, and SELECT operations against this table.
• HZ_FINANCIAL_NUMBERS_S — The database sequence used to generate the surrogate primary key financial_number_id whenever the caller passes FND_API.G_MISS_NUM or NULL.
• DUAL — Used for sequence retrieval and simple scalar evaluation during row processing.

Column handling in the documented INSERT_ROW body applies DECODE against sentinel values such as FND_API.G_MISS_NUM and FND_API.G_MISS_CHAR to translate "attribute not applicable" markers into NULLs, while NULL or missing primary keys trigger sequence-based ID generation. Audit columns such as created_by, creation_date, last_update_date, last_updated_by, and last_update_login are populated by the package itself.

Usage Notes

This package is internal plumbing. It is most commonly invoked indirectly by the Oracle Forms-based TCA maintenance windows that manage financial reports and their associated numbers, and by other PL/SQL packages in the Trading Community model that must persist financial number rows as part of a larger transaction. Because the package is classified as OTHER and is referenced by exactly one other package, customizations should generally call the higher-level TCA APIs rather than these low-level CRUD procedures.

Regarding the user's search term g_miss_content_source_type: the documented body declares a package-level constant, G_MISS_CONTENT_SOURCE_TYPE CONSTANT VARCHAR2(30) := 'USER_ENTERED';. This value supplies the default for the content_source_type column, indicating that records created through this package by default record their content origin as user-entered data rather than imported or derived content. When INSERT_ROW is called without an explicit content source, or with a missing sentinel, the package applies this constant to populate the content_source_type column.

Any custom code interacting with the package should respect the object version number convention: callers should read the current version, pass it back on update, and rely on LOCK_ROW to serialize concurrent writes. Failure to supply valid identifiers or to honour the sentinel conventions may result in duplicate or orphaned financial number records.