Search Results validate_worksheet

Overview

PSB_BUDGET_ACCOUNT_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API. It belongs to the Oracle Enterprise Technical Reference Model (ETRM) inventory for release 12.1.1 and remains applicable in 12.2.2. The package supports the budgeting and worksheet processing functionality associated with the Public Sector Budgeting (PSB) application family, providing the underlying programmatic logic that populates budget accounts from account position sets and validates budget worksheets before they are committed or advanced in the budgeting cycle. Because it is a private package, it is intended for internal use by other EBS product code rather than as a formally supported public integration point. The source header indicates version 120.3, last modified in August 2004, reflecting the long-standing stability of this component across the EBS 12.x code line.

Key Procedures and Functions

Four documented procedures make up the package interface:

• POPULATE_BUDGET_ACCOUNTS — The primary API-form procedure that generates or refreshes budget account records for a given set of books and account set. It follows the standard EBS PL/SQL API convention, accepting an API version, initialization flag, commit flag, and validation level, and returning status, message count, and message data. It also accepts a full maintenance flag (introduced under Bug 3573740) that controls the extent of account maintenance performed.
• POPULATE_BUDGET_ACCOUNTS_CP — The concurrent-program wrapper for the above. It uses the standard concurrent program signature (errbuf, retcode) and delegates to the core population logic, allowing budget account population to be scheduled or submitted as a batch job.
• VALIDATE_WORKSHEET — The API-form procedure that validates a specific budget worksheet, identified by worksheet ID. It follows the same API parameter conventions as POPULATE_BUDGET_ACCOUNTS and additionally accepts a message write mode parameter, giving callers control over how validation messages are recorded.
• VALIDATE_WORKSHEET_CP — The concurrent-program wrapper for worksheet validation, accepting worksheet ID through the standard concurrent signature. Both validation procedures were introduced under Bug 3247574.

Tables Accessed

The package operates against the following tables, referenced through APPS synonyms:

• PSB_ACCOUNT_POSITION_SETS and PSB_ACCOUNT_POSITION_SET_LINES — define the account position sets and their constituent lines that drive which accounts are relevant to budget population.
• PSB_BUDGET_ACCOUNTS — the target table populated and maintained by the population procedures.
• PSB_WORKSHEETS — the budget worksheets subjected to validation.
• GL_CODE_COMBINATIONS — supplies the valid accounting flexfield combinations used when resolving and creating budget account records.
• FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_SEGMENTS — provide the key flexfield structure and segment definitions needed to interpret the accounting flexfield.
• DBMS_SQL — the Oracle-supplied dynamic SQL package, used where account combinations must be constructed or processed dynamically.

Usage Notes

PSB_BUDGET_ACCOUNT_PVT is invoked indirectly through Public Sector Budgeting forms and concurrent programs rather than being called directly by end users. The _CP variants are registered as concurrent programs and are the typical entry points for batch processing: one to populate budget accounts for a set of books and account set, and one to validate individual worksheets. The non-_CP variants expose the API-style signature and are called from other PL/SQL packages within the budgeting flow; ETRM records two dependent packages referencing this one. Customizations that need to trigger budget account population or worksheet validation should generally call the public wrapper procedures exposed by PSB rather than this private package, since the PVT classification means the interface may change without notice. All callers should observe the standard EBS API contract by checking the returned status and retrieving messages when the return status is not success.