Results for “tax_transaction_header_id”

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

Overview

FA_PARALLEL_WORKERS is an Oracle E-Business Suite table owned by the FA (Assets) schema and delivered as part of the OFA – Assets product family. Its documented purpose is to control the concurrent execution of the Post Mass Additions program. When large volumes of mass addition lines are processed, the program can be partitioned across multiple parallel workers; this table records the assignment of work items to those workers, the concurrent request context driving each worker, and the disposition of each processed row. It therefore acts as a coordination and audit substrate rather than as a master or transactional data store.

From a data-modeling perspective, the metadata's relationship profile — a dense set of foreign keys pointing outward to FA_ADDITIONS_B, FA_TRANSACTION_HEADERS, FA_CATEGORIES_B, FA_BOOK_CONTROLS, and FND_CONCURRENT_REQUESTS — supports a heuristic Data Vault classification of link. It associates asset candidates, transaction headers, book and category contexts, and a concurrent request identifier, while carrying its own descriptive and status attributes. This classification is a modeling suggestion only; in functional terms the table behaves as a transient work-control table populated and purged by the Post Mass Additions concurrent program.

Key Information Stored

The documented physical schema for 12.2.2 comprises 19 columns. The most significant are:

• REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS; ties every row to the concurrent request executing the Post Mass Additions run. This is the principal partition key for isolating workers belonging to one execution.
• CONC_REQ_NUM — the concurrent request number, the user-facing counterpart to REQUEST_ID.
• PROGRAM — identifies the concurrent program under which the worker was spawned.
• WORKER_NUMBER — the ordinal of the parallel worker within the run; together with REQUEST_ID it defines the worker assignment.
• PROCESS_ORDER — the sequencing value used to order work items across workers.
• PROCESS_STATUS — the per-row processing outcome, allowing restart and error diagnosis.
• START_TIME — the timestamp at which the worker row began processing.
• ASSET_ID and ASSET_NUMBER — the candidate asset being processed, with ASSET_ID as the foreign key to FA_ADDITIONS_B.
• ASSET_TYPE — the classification of the asset (for example capitalized versus expensed).
• ASSET_CATEGORY_ID — foreign key to FA_CATEGORIES_B, governing default depreciation and account rules.
• PARENT_ASSET_ID, OLD_GROUP_ASSET_ID, and NEW_GROUP_ASSET_ID — foreign keys to FA_ADDITIONS_B supporting parent and grouped-asset adjustments.
• BOOK_TYPE_CODE — foreign key to FA_BOOK_CONTROLS, identifying the depreciation book context.
• CORP_TRANSACTION_HEADER_ID, TAX_TRANSACTION_HEADER_ID, and TRANSACTION_TYPE_CODE — foreign keys to FA_TRANSACTION_HEADERS linking the work item to its corporate and tax transaction headers.
• TRANSACTION_DATE_ENTERED — the business date of the originating transaction.

The metadata does not enumerate a declared single-column surrogate primary key or a named unique index; functionally the worker assignment is identified by the combination of REQUEST_ID, WORKER_NUMBER, and the asset/transaction context columns, which serve as the business-key candidates.

Common Use Cases and Queries

The primary operational scenario is diagnosing a stalled, failed, or partially completed Post Mass Additions run. Because worker rows carry both PROCESS_STATUS and REQUEST_ID, a support analyst can enumerate outstanding work for a specific request and identify which worker failed:

• Outstanding work for a request: SELECT worker_number, process_order, asset_number, process_status FROM fa.fa_parallel_workers WHERE request_id = :request_id ORDER BY worker_number, process_order;
• Failure distribution: grouping by WORKER_NUMBER and PROCESS_STATUS to establish whether one worker or the entire run is failing.
• Reconciliation to assets: joining ASSET_ID to FA_ADDITIONS_B to confirm that candidates captured by the worker table were ultimately posted.
• Throughput reporting: comparing START_TIME values across WORKER_NUMBER to assess parallelism effectiveness for a given CONC_REQ_NUM.

Because rows are created and released by concurrent processing, direct DML should be avoided outside of Oracle-supplied logic; the table is read for monitoring and troubleshooting rather than maintained by end users.

Related Objects

• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID; supplies request status, phase, and completion context.
• FA_ADDITIONS_B — joined on ASSET_ID, PARENT_ASSET_ID, OLD_GROUP_ASSET_ID, and NEW_GROUP_ASSET_ID; the asset definition table.
• FA_TRANSACTION_HEADERS — joined on CORP_TRANSACTION_HEADER_ID, TAX_TRANSACTION_HEADER_ID, and TRANSACTION_TYPE_CODE; the transaction header repository.
• FA_CATEGORIES_B — joined on ASSET_CATEGORY_ID; supplies category defaults.
• FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE; identifies the depreciation book.
• FA_MASS_ADDITIONS — the source queue whose rows feed the Post Mass Additions program that this table coordinates.