Search Results generate_asset_summary

Overview

OKL_LA_ASSET_PVT is a private (PVT) API package in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. The "LA" component of the name denotes Lease Accounting, and the package operates with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling schema rather than the package owner. Its principal responsibility is to manage the asset-related side of lease accounting: assembling asset summary information, propagating updates from contracts down to the asset and capital cost records, and determining whether a contract is in an active state. In release 12.1.1 and 12.2.2 the package forms part of the internal accounting engine that bridges Oracle Contracts (OKC) line data, Oracle Assets (FA) asset records, and Lease Management header/line tables. It is not a public, customer-callable API; it is consumed internally by other OKL packages and by Lease Management forms and concurrent programs.

Key Procedures and Functions

The ETRM metadata documents six packaged procedures and functions, of which four are named explicitly:

• GENERATE_ASSET_SUMMARY — Builds a consolidated summary of lease assets, using the las_rec_type composite record structure to carry asset number, manufacturer, description, units, residual values, and contract line dates.
• UPDATE_CONTRACT_LINE — Propagates changes originating in the asset/accounting context back to the associated contract line records in OKC_K_LINES_B, keeping contract line dates, status, and termination information synchronized with asset activity. This is the procedure most commonly targeted by callers searching for contract line maintenance logic.
• UPDATE_FIN_CAP_COST — Updates the financial capital cost components of a lease, working with the fin_adj_rec_type record that carries top line identifier, asset number, OEC (original equipment cost), capital reduction amounts and percentages, and down-payment indicators.
• ISCONTRACTACTIVE — Evaluates contract status to determine whether a contract is active; this is typically used as a gate before allowing asset or cost updates to proceed.

Two further procedures are present in the package but not individually named in the available metadata excerpt; they support the same asset accounting lifecycle.

Tables Accessed

The package reads and writes a broad set of tables through APPS synonyms. Asset master and descriptive data come from FA_ADDITIONS_B and FA_ADDITIONS_TL, while OKC_K_LINES_B, OKC_K_HEADERS_B, OKC_K_ITEMS, and OKC_K_LINES_TL supply contract line, header, item, and translated line attributes. OKC_LINE_STYLES_B and OKC_STATUSES_B provide line style and status reference data. Lease-specific entities are drawn from OKL_K_HEADERS, OKL_K_LINES, and OKL_SUBSIDIES_B. Installed base context is retrieved from CSI_ITEM_INSTANCES, and party and location details from HZ_LOCATIONS, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES. Vendor information is referenced from PO_VENDORS. Together these accesses allow the package to reconcile contract terms against physical asset records.

Usage Notes

OKL_LA_ASSET_PVT is a PVT-layer API and should not be invoked directly by custom code where a public API exists. It is referenced by five other packages within the OKL and OKC stack, which call its procedures during contract booking, asset creation, capital cost adjustment, and termination processing. In practice it is triggered from Lease Management forms and from accounting-related concurrent programs that refresh asset summaries or re-cost leases. Because the package relies on AUTHID CURRENT_USER and uses the OKL_API.G_MISS_NUM sentinel, callers must initialize record attributes carefully and ensure the invoking session has appropriate access to the underlying FA, OKC, OKL, CSI, and HZ objects. When troubleshooting "update_contract_line" behavior, the procedure should be examined in conjunction with OKC_K_LINES_B status codes and the contract active check performed by ISCONTRACTACTIVE.