Search Results instance_tbl

Overview

CSE_ASSET_CREATION_PKG is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Enterprise Asset Management (eAM) and Install Base functional area and is responsible for the automated creation of fixed assets from Oracle Install Base (CSI) transactions. When capitalized items are received, installed, or moved, the package translates the associated Install Base transaction data into corresponding Oracle Assets records, ensuring financial visibility of tracked equipment.

The package is classified in the ETRM metadata as an "OTHER" API. Its status is VALID, and it depends on the shared utility package APPS.CSE_DATASTRUCTURES_PUB along with standard Oracle technology stack components such as FND_API and the SYS.STANDARD library. The presence of CSE_DATASTRUCTURES_PUB as a dependency is significant: that public package supplies the common data structures (record types and PL/SQL tables) used to pass asset and transaction information between the various CSE packages consistently.

Key Procedures and Functions

The ETRM documentation records five callable units within this package. No parameter lists are published in the referenced metadata; the descriptions below reflect their documented purposes only.

• CREATE_DEPRECIABLE_ASSETS — Drives the creation of depreciable asset records in Oracle Assets, typically processing Install Base items that qualify for capitalization and depreciation.
• CREATE_ASSET — Creates an individual asset, mapping Install Base instance data to the Oracle Assets additions interface. It is the core creation routine invoked by the higher-level procedures.
• FIND_ASSET — Locates an existing asset associated with a given Install Base instance or transaction, preventing duplicate creation and supporting updates to previously capitalized items.
• ADJUST_ASSET — Applies adjustments to an existing asset when the underlying Install Base transaction data changes, such as cost corrections or quantity modifications.
• COMPLETE_CSI_TXN — Finalizes the Install Base transaction after asset processing, marking the CSI transaction as complete and recording any errors encountered during processing.

Tables Accessed

The package reads and writes a broad set of Install Base, Assets, and transaction-control tables through APPS synonyms.

• Install Base tables: CSI_ITEM_INSTANCES and CSI_ITEM_INSTANCES_H hold the current and historical instance records; CSI_TRANSACTIONS, CSI_T_TRANSACTION_LINES, and CSI_T_TXN_LINE_DETAILS capture transaction header and line data; CSI_TXN_TYPES, CSI_SOURCE_IB_TYPES, and CSI_IB_TXN_TYPES define transaction and source type validation; CSI_A_LOCATIONS stores instance locations; CSI_I_ASSETS links instances to assets; and CSI_TXN_ERRORS records processing failures.
• Oracle Assets tables: FA_MASS_ADDITIONS and FA_ASSET_INVOICES serve as the interface for asset additions and invoice matching, while FA_ADDITIONS and FA_ADDITIONS_B store the resulting asset definitions and descriptive details.

Together these tables allow the package to read the source Install Base transaction, validate it, write to the Assets interface, and then update the Install Base side with completion or error status.

Usage Notes

CSE_ASSET_CREATION_PKG is typically invoked indirectly rather than called directly by end users. It is referenced by CSE_ASSET_MOVE_PKG and by itself, indicating that asset movement processing and recursive or batched creation flows depend on its routines. In standard EBS operation, the package is triggered by Install Base transaction processing — for example, when a capitalized item is received or installed — and by concurrent programs that mass-create assets from qualifying Install Base transactions.

Because the package writes to the FA_MASS_ADDITIONS interface and to CSI transaction tables, customers extending or debugging asset creation should understand that the standard sequence is: CREATE_ASSET or CREATE_DEPRECIABLE_ASSETS creates the asset, FIND_ASSET supports lookup or de-duplication, ADJUST_ASSET handles corrections, and COMPLETE_CSI_TXN closes the loop on the Install Base transaction. Custom code should respect this ordering and always check CSI_TXN_ERRORS after invocation. The dependency on CSE_DATASTRUCTURES_PUB means any customization should use the same shared record structures to remain compatible with the supported API surface.