Results for “asset_cost”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.JL_ZZ_FA_FUNCTIONS_PKG is a custom PL/SQL package in the Oracle E-Business Suite environment that supports Fixed Assets (FA) processing as part of the JL (Japanese Localization / JLZZ) module family. The package is defined with AUTHID CURRENT_USER and declares a set of public functions that encapsulate Fixed Assets calculation and reporting logic. Its header comment identifies it as a customization layer shipped under the label jlzzfafs.pls, originating from an early-2000s release cycle (header version 115.12, dated 2003/09/03).

The package exists to satisfy localized Fixed Assets reporting and computation requirements — notably the exhibit-style data output referenced by the user search term populate_fa_exhibit_data. In EBS terminology, an "exhibit" refers to the statutory fixed-asset schedules and disclosures that a legal entity must produce. Rather than depending on standard Oracle FA reports alone, the package bundles re-usable calculation functions and a dedicated population routine so that exhibit data can be assembled consistently from underlying FA transaction, depreciation, and calendar tables. It is classified as an OTHER API, meaning it is not a published import/interface API but rather an internal utility package consumed by forms, concurrent programs, reports, or other custom packages (the metadata records six dependent packages).

Key Procedures and Functions

  • MIDDLE_MONTH — Determines the "middle month" position used to adjust assets that are added or sold within a fiscal year up to the midpoint of their period of use. The calculation draws the half-period value from Middle Month tables and accounts for whether the DPIS month and the retirement month should be included in the periods-of-use calculation.
  • PERIODS_OF_USE — Computes the periods of use for an asset based on the method configured by the customer. Like MIDDLE_MONTH, it considers the addition month, retirement month, the DPIS inclusion flag, and the retirement-month inclusion flag.
  • ASSET_COST — Returns or derives asset cost information for use in exhibit and reporting calculations.
  • ASSET_DESC — Returns asset descriptive information, supporting the presentation layer of exhibit output.
  • POPULATE_FA_EXHIBIT_DATA — The routine surfaced by the user's search. It drives the assembly of Fixed Assets exhibit data, coordinating the calculations supplied by the other package functions and sourcing the necessary transaction, depreciation, and book information from the FA base tables.

No parameter lists are reproduced here; these are inferred only from the documented functional descriptions above.

Tables Accessed

The package references fifteen Fixed Assets tables through APPS synonyms. Collectively these support exhibit population across cost, adjustment, depreciation, and reporting dimensions:

The price index tables are notable: they indicate that the exhibit calculation supports revaluation or inflation-adjusted asset values, consistent with a Japanese localization context. The category-book and depreciation-period tables provide the book-specific context required to render per-book exhibit figures.

Usage Notes

The package is typically invoked from custom Oracle Forms, concurrent programs, or report templates that produce Fixed Assets statutory exhibits for the Japanese localization. Callers first invoke the aggregate POPULATE_FA_EXHIBIT_DATA function to stage or materialize exhibit rows, relying on PERIODS_OF_USE and MIDDLE_MONTH to correctly pro-rate assets added or retired mid-year, and on ASSET_COST and ASSET_DESC for amount and description attributes. Because the package is classified as OTHER rather than a public interface API, direct invocation from ad-hoc SQL is discouraged; integration should occur through the surrounding known calling packages or the concurrent programs that own the exhibit process. The AUTHID CURRENT_USER clause means callers must hold the necessary privileges on the underlying FA tables, and the six dependent packages documented in metadata confirm the routine is embedded within a broader custom FA reporting chain.