Results for “p_budget_group_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PSB_VALIDATE_ACCT_PVT is a private (PVT) PL/SQL package within the Oracle EBS Public Sector Budgeting (PSB) module, part of the Enterprise Resource Planning family. Its business function is to validate accounting code combinations against a specific budget group and, when validation succeeds and the combination is new to the budget group, to create the corresponding budget account records for the account set associated with that budget group. The package therefore acts as the integrity gatekeeper between General Ledger chart-of-accounts structures and the budgeting tables that track account positions, budgets, and worksheet activity. The header comment carries the RCS identifier PSBVVACS.pls, dated 2005/07/13, and the package has been part of the application since at least 1997 (original author L Sekar). Because the package is classified as PVT rather than a public API, Oracle does not document it for customer extension; it is an internal implementation unit consumed by other PSB packages.

Key Procedures and Functions

One procedure is documented in the ETRM metadata for this package.

• VALIDATE_ACCOUNT — The core procedure. Per the source header, it "validates code combination or ccid for a given budget group" and, if the code combination is valid and new, "creates records in Budget Accounts table for the account set that belong the budget group." Its documented parameter signature includes a standard FND_API boilerplate set (p_api_version, p_init_msg_list, p_commit, p_validation_level, p_return_status, p_msg_count, p_msg_data) plus business parameters: p_parent_budget_group_id, p_startdate_pp, p_enddate_cy, p_set_of_books_id, p_flex_code, p_create_budget_account, p_concatenated_segments, p_worksheet_id, and p_in_ccid. Note that the comment block above the procedure contains older parameter names (p_budget_group_id appears twice, plus p_out_ccid, p_return_status, and p_flex_code listed as NUMBER, which is inconsistent with the actual signature) — these are historical header-comment artifacts and should not be relied upon. The authoritative parameter list is the procedure declaration itself. Outputs are returned through p_return_status, p_msg_count, and p_msg_data using FND_API message conventions.

Tables Accessed

The package reads and writes the following tables (referenced via APPS synonyms):

• GL_CODE_COMBINATIONS — source of valid account code combinations and CCIDs; the primary validation target.
• FND_ID_FLEX_STRUCTURES, FND_ID_FLEX_SEGMENTS — key flexfield structure and segment metadata used to interpret the concatenated segments and the flex code.
• PSB_BUDGET_GROUPS — identifies the budget group, its set of books, and its associated account set.
• PSB_ACCOUNT_POSITION_SETS, PSB_ACCOUNT_POSITION_SET_LINES — define the account set whose members require budget account records.
• PSB_SET_RELATIONS — relationship mapping that ties budget groups to account position sets.
• PSB_BUDGET_ACCOUNTS — target of inserts when a valid new code combination is accepted for the budget group.
• PSB_WORKSHEETS — worksheet context, used when the worksheet ID parameter is supplied.
• PSB_ENTITY, PSB_ENTITY_ASSIGNMENT — entity and assignment data relevant to validating that the combination belongs within the budgeting organization structure.
• DBMS_SQL — Oracle-supplied package invoked for dynamic SQL, most likely to perform flexfield-based validation of the concatenated segment string.

Usage Notes

Because PSB_VALIDATE_ACCT_PVT is a PVT-classified package, it is not intended for direct invocation from client code. The documented metadata shows it is referenced by three other APPS packages, confirming it is called internally by the PSB budgeting engine — typically when a user enters or selects an account combination on a budgeting worksheet or account position form, and the system must confirm the combination is valid for the applicable budget group and set of books before committing budget account rows. Callers pass the set of books, flex code, concatenated segments or an existing CCID, the parent budget group, and the period dates; the procedure then returns a status and, where warranted, a CCID. Custom code should not call this package directly: developers needing equivalent validation should use publicly documented APIs such as the GL code combination validation APIs or the supported PSB public interfaces. Any reliance on VALIDATE_ACCOUNT in customization is unsupported, since Oracle may change its signature or behavior between releases, and the header comments already demonstrate that the documented parameter names have drifted from the implemented signature.