Results for “gl_period”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_CAP_INT_PVT is the private PL/SQL package in Oracle Projects (APPS schema) that implements the Capitalized Interest business process. Capitalized interest represents the cost of financing construction or capital projects, calculated by applying interest rate schedules to eligible expenditures and then capitalizing that calculated interest against the project. This package owns the full lifecycle of that calculation: generation of capitalized interest, optional auto-release of the generated run, manual release initiated from a form, and purging of the source detail rows that support a given calculation. Because the package is classified as PVT (private), it is not a published integration API; it is the internal engine invoked by Oracle Projects reports, concurrent programs, and form logic.

The generation logic is driven by interest rates set up for the submitter's manufacturing/organization (M/O ORG_ID). Rates that exist in schedules associated with projects falling between the supplied project number bounds are processed, and each rate processed produces a single run row. Financial integrity is enforced at the project level: if any problem is encountered on a project, no transactions for that project are created, and a project can only be successfully processed once per month. Summarized control numbers are reported on the log, while the calling report displays more detailed results.

Key Procedures and Functions

  • GENERATE_CAP_INTEREST — The main entry point, called from an Oracle Report and also used when release is requested from a form. It accepts low and high project number bounds, the GL period and expenditure item date for the calculated interest, flags for creating source details and for auto-releasing each run batch, and a run_id when a release of an existing run is being requested.
  • PURGE_SOURCE_DETAIL — Called from an Oracle Report to purge capitalized interest source detail rows for a given GL period, optionally bounded by low and high project numbers.
  • EXCLUDE_EXPENDITURE_TYPE — Evaluates whether a given expenditure type is excluded from the capitalized interest calculation.
  • CDL_STATUS — Returns calculation status information used to control whether a project or rate can be processed.
  • TASK_CAPITAL_FLAG — Determines the capital flag applicable to a task, used to decide whether expenditures associated with that task are eligible for interest capitalization. This is the object most commonly inspected when diagnosing why a task's costs were or were not capitalized.
  • GL_PERIOD — Resolves/validates the GL period used for the calculated interest.
  • PERIOD_END_DATE — Derives the period end date associated with the GL period.
  • PROJECT_ID — Resolves the internal project identifier from the project number used in the concurrent program parameters.
  • RATE_NAME — Returns the interest rate name associated with the rate being processed.

Tables Accessed

The package reads GL_PERIOD_STATUSES for period validation and PERIOD_END_DATE derivation, and HR_ALL_ORGANIZATION_UNITS for the submitter's organization. Interest rate configuration is read from PA_CINT_RATE_INFO, PA_CINT_RATE_INFO_ALL, and PA_CINT_RATE_MULTIPLIERS. Calculated results and supporting detail are written to PA_CINT_SOURCE_DETAILS. Allocation-related processing uses PA_ALLOC_RULES_ALL, PA_ALLOC_EXCEPTIONS, PA_ALLOC_RUNS, PA_ALLOC_RUNS_ALL, PA_ALLOC_RUNS_S, PA_ALLOC_TXN_DETAILS, and PA_ALLOC_TXN_DETAILS_S. Budget context is obtained from PA_BUDGET_VERSIONS and PA_BUDGET_ENTRY_METHODS.

Usage Notes

PA_CAP_INT_PVT is invoked indirectly in normal operation: the Generate Capitalized Interest, Generate and Auto-Release Capitalized Interest, and Purge Capitalized Interest Source Details concurrent programs call the package through their Oracle Reports, and the Release Capitalized Interest form button calls GENERATE_CAP_INTEREST with a run_id. Because it is a private package, direct calls from custom code are not supported and should be avoided; custom development should instead use documented public APIs or the standard concurrent programs. When troubleshooting capitalization results, the most useful handle is TASK_CAPITAL_FLAG, which explains task-level eligibility, complemented by EXCLUDE_EXPENDITURE_TYPE for expenditure type exclusions.