Search Results bal_pdevformula
Overview
FA_FAS955_XMLP_PKG is a public PL/SQL package owned by APPS in the Oracle E-Business Suite, classified under API classification OTHER. It is the packaged PL/SQL support object generated for the Oracle Assets report FAS955, commonly known as the "Reserve Summary" or asset cost/reserve comparative report. The package is declared with AUTHID CURRENT_USER, meaning that at runtime all unqualified object references are resolved using the privileges of the calling user rather than the package owner — a standard convention for XML Publisher (BI Publisher) report support packages in EBS 12.1.1 and 12.2.2.
The package encapsulates the report's global parameters, formula functions, and the Before/After report triggers required by Oracle Reports and the XML Publisher concurrent program architecture. Because the report contrasts period-to-date, quarter-to-date, and year-to-date cost and reserve balances across asset books, accounts, categories, and cost centers, the package exposes a large family of numeric "deviation" formulas that compute variances between a beginning ("B") value and an adjusted/actual ("A") value. The package also determines the accounting period context — fiscal year, period number, quarter number, and period start/end dates — from the user's requested period.
Key Procedures and Functions
The documented 29 procedures and functions fall into three logical groups.
- Report lifecycle and identification: REPORT_NAMEFORMULA derives the printed report name from the company name; BEFOREREPORT and AFTERREPORT are the standard report triggers used to initialize globals, resolve the reporting period, and perform cleanup after output is produced.
- Period resolution: PERIOD1_PCFORMULA computes the period-end/period-close context for a given distribution source book, working with the globals PERIOD1_POD, PERIOD1_PCD, PERIOD1_FY, PERIOD_NUM, and QUARTER_NUM.
- Variance/deviation formulas: CAT_PDEVFORMULA, CAT_QDEVFORMULA, CAT_YDEVFORMULA (category-level period, quarter, and year deviations); RP_*DEVFORMULA (report-level); CC_*DEVFORMULA (cost center-level); BD_*DEVFORMULA (book-level); and BAL_*DEVFORMULA (balance-level, including BAL_PDEVFORMULA, BAL_QDEVFORMULA, and BAL_YDEVFORMULA). ACCT_BAL_APROMPT_P and the related *_PROMPT globals (ACCT_BAL_APROMPT, ACCT_CC_APROMPT, CAT_MAJ_RPROMPT) supply the runtime prompt values displayed on the report output.
The function names themselves follow a consistent naming grammar: the prefix identifies the report row/level (CAT, RP, CC, BD, BAL), the middle segment identifies the time basis (P, Q, Y for period, quarter, year), and DEV signifies a deviation calculation. No parameter lists are reproduced here; the documented signatures should be taken from the source.
Tables Accessed
The package resolves three APPS synonyms. FA_DEPRN_PERIODS provides the depreciation calendar period definitions — period name, fiscal year, period number, and start/end dates — that drive the period1_pcformula logic and the P_PERIOD1 bind. FA_PERIOD_MAPS maps the reporting period across books, allowing the report to align periods when multiple distribution source books are selected. FND_CONCURRENT_REQUESTS is read to resolve P_CONC_REQUEST_ID, the concurrent request identifier that ties the running report to its submission record and to any associated report/log output.
Usage Notes
FA_FAS955_XMLP_PKG is not intended for direct invocation by custom code. It is referenced by the Oracle Assets FAS955 concurrent program and its associated XML Publisher data template; the ETRM metadata records zero packages referencing it, confirming that its callers are external (report definitions and concurrent program registrations) rather than other PL/SQL units. The "period_num_p" search term corresponds to the PERIOD_NUM global and the period-related parameters (P_PERIOD1, Period1_POD, Period1_PCD, Period1_FY) that the BeforeReport trigger populates before the report query executes. In both 12.1.1 and 12.2.2 the package resides in the APPS schema and is invoked under the calling user's privileges; customizations should be confined to the underlying report definition rather than to this generated package, since regeneration by the XML Publisher/report migration utilities can overwrite source changes.