Search Results do_trace

Overview

FA_ASSET_TRACE_PKG is an Oracle EBS Assets (Fixed Assets) diagnostic and utility package owned by APPS in the 12.1.1 and 12.2.2 environments. Its principal role is to trace the processing history and distribution accounting impact for a given asset, supporting troubleshooting of asset book, transaction, and subledger accounting flow. The package header declares AUTHID CURRENT_USER and carries a version header (faxtrcs.pls 120.5, dated 2008/10/08), indicating it has been stable across releases and is not a public integration API. It is classified in ETRM as OTHER rather than a supported open interface, meaning it is intended for internal, diagnostic, and support-oriented use. The package exposes two documented procedures: DO_TRACE and GET_DIST_INFO. Global state flags such as g_use_utl_file and g_sla_only allow callers to redirect output to a file and to restrict tracing to Subledger Accounting information. A collection type t_col_tbl is defined for holding string values during trace assembly. Collectively, these features position the package as an investigation aid for Asset traceability and distribution information, not as a transactional entry point.

Key Procedures and Functions

• DO_TRACE — the primary tracing routine. It accepts an error buffer and return code (the standard concurrent program OUT NOCOPY pair), a book identifier, an asset number, and an optional log level record of type FA_API_TYPES.log_level_rec_type. Its purpose is to produce asset trace output for the specified book and asset, honoring the log level supplied by the caller. The error buffer and return code parameters conform to the concurrent manager convention, so DO_TRACE can be registered or called as a concurrent executable. Because the parameters are declared OUT NOCOPY, the procedure is designed to return status and messages without incurring copy overhead.
• GET_DIST_INFO — retrieves distribution information. It takes a single optional log level record of the same FA_API_TYPES.log_level_rec_type type. Its role is to gather and report the distribution details associated with assets, complementing the trace output produced by DO_TRACE.

The two procedures share a common logging signature, which allows a caller to control verbosity uniformly across both trace operations.

Tables Accessed

The package references the following tables through APPS synonyms:

• FA_ADDITIONS / FA_ADDITIONS_B — asset master and descriptive data, used to resolve an asset number to its identifying attributes.
• FA_BOOKS — asset-to-book cost and assignment information, central to book-scoped tracing.
• FA_BOOK_CONTROLS — book-level control settings and accounting configuration.
• FA_TRANSACTION_HEADERS — asset transaction history, the core of processing trace.
• FND_ID_FLEX_SEGMENTS — key flexfield segment definitions, needed to interpret distribution account segments.
• FND_PRODUCT_GROUPS and FND_PROFILE_OPTION_VALUES — installation and profile option context.
• GAT_MESSAGE_TYPE — message type definitions, supporting formatted output.
• DBA_OBJECTS — object metadata lookup, used to validate or resolve database objects referenced during tracing.

Built-in packages referenced include DBMS_AQ, DBMS_AQADM, DBMS_LOCK, DBMS_SESSION, and PLITBLM, indicating use of Advanced Queuing, locking, session attributes, and index-by-table utilities in the trace implementation.

Usage Notes

FA_ASSET_TRACE_PKG is typically invoked from the Fixed Assets forms or from a support diagnostic concurrent program, particularly when an asset's transaction history or accounting distribution must be examined. The errbuf/retcode signature of DO_TRACE makes it suitable for submission as a concurrent request, while GET_DIST_INFO can be called from wrapper code. Because the package is documented as referenced by one other package, customizations should avoid altering its signatures. The globals g_use_utl_file and g_sla_only should be set by the invoking session when file output or SLA-only tracing is required. As an OTHER-classification object, it carries no compatibility guarantee and should be treated as a read-only diagnostic utility in both 12.1.1 and 12.2.2.