Search Results fa_transaction_interface_pk

Overview

The FA_TRANSACTION_INTERFACE table is the open interface staging table for the Oracle Assets (OFA) module. It serves as the mandatory landing point for transaction data that must be validated and transferred into the assets transaction tables via the "Post Mass Additions" concurrent program. During a mass addition, the program reads rows flagged with a POSTING_STATUS of 'POST' and converts them into asset cost adjustments, additions, or transfers. The table also supports other upload paths, including transaction types defined in FA_TRANSACTION_TYPES such as additions, adjustments, and retirements, allowing external systems, legacy conversions, and feeder programs to create asset transactions without invoking the Assets APIs directly.

Applying heuristic Data Vault classification based on key structure, the table resembles a link object. Its surrogate primary key, TRANSACTION_INTERFACE_ID, is a generated identifier rather than a composite natural key, but the two foreign key relationships (BOOK_TYPE_CODE and CONCURRENT_REQUEST_ID) tie each row to a book context and a concurrent request, consistent with a transactional link between a book and an upload process rather than a descriptive satellite.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• TRANSACTION_INTERFACE_ID — surrogate primary key (FA_TRANSACTION_INTERFACE_PK, U1 unique index); populated from a sequence and used as the row-level identifier.
• BOOK_TYPE_CODE — foreign key to FA_BOOK_CONTROLS; identifies the asset book to which the transaction is posted.
• TRANSACTION_TYPE_CODE — denotes the transaction category (for example addition, adjustment, or transfer) declared in FA_TRANSACTION_TYPES.
• TRANSACTION_DATE — the accounting date applied when the transaction posts to the book.
• POSTING_STATUS — the processing flag read by Post Mass Additions; rows marked 'POST' are eligible for transfer.
• ASSET_KEY_PROJECT_VALUE, ASSET_KEY_HIERARCHY_VALUE, ASSET_KEY_NEW_HIERARCHY_VALUE — key flexfield segment combinations describing the asset key, used to identify or locate the target asset for adjustments and transfers.
• REFERENCE_NUMBER and COMMENTS — free-form descriptive and audit attributes carried into the resulting transaction.
• CONCURRENT_REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS; records the concurrent program run that created or processed the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO audit columns.

Common Use Cases and Queries

Typical usage involves monitoring the interface queue before and after running Post Mass Additions:

• Counting pending rows by book and type:

SELECT book_type_code, transaction_type_code, COUNT(*) FROM fa_transaction_interface WHERE posting_status = 'POST' GROUP BY book_type_code, transaction_type_code;

• Identifying the source concurrent request for failed uploads:

SELECT ti.transaction_interface_id, ti.book_type_code, ti.posting_status, r.request_id, r.phase_code, r.status_code FROM fa_transaction_interface ti, fnd_concurrent_requests r WHERE ti.concurrent_request_id = r.request_id;

• Validating a book exists before posting:

SELECT ti.transaction_interface_id FROM fa_transaction_interface ti, fa_book_controls bc WHERE ti.book_type_code = bc.book_type_code;

Reporting teams use this table to reconcile interface volumes against posted asset transactions, and integration developers use it to verify that feeder loads are complete before invoking the post process.

Related Objects

• FA_BOOK_CONTROLS — referenced by BOOK_TYPE_CODE; defines the target asset book.
• FND_CONCURRENT_REQUESTS — referenced by CONCURRENT_REQUEST_ID; links rows to the processing request.
• FA_MASS_ADDITIONS — holds mass addition lines prepared for posting alongside this interface.
• FA_TRANSACTION_HEADERS — stores posted transaction groups after the interface is processed.
• FA_TRANSACTION_TYPES — valid values for TRANSACTION_TYPE_CODE.
• FA_ADDITIONS — receives new asset rows resulting from successful postings.
• FA_ADJUSTMENTS — created for adjustment-type transactions posted from the interface.
• FA_API_* public APIs — alternative supported insertion paths that also populate interface processing structures.