Results for “status_code”

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

Overview

FA_MUPD_V is a reporting view owned by the APPS schema within the Oracle Assets (OFA) module. It exposes the results of mass asset updates processed through the Mass Update Batch Details framework, which allows a user to change attributes such as category, lease number, serial number, asset key, distribution, and other descriptive fields across many assets in a single operation. The view presents each affected asset together with the old value, the new value, the processing status, any rejection reason, and the concurrent request identifier under which the update ran.

Critically for the searched term, the view carries the CONCURRENT_REQUEST_ID column. This links each mass update detail line back to the specific concurrent program run in FND_CONCURRENT_REQUESTS, enabling audit, reconciliation, and diagnostic reporting. Administrators commonly use this relationship to find every asset change produced by a given request, to detect rejected rows, and to confirm successful completion before downstream period-close activity.

Underlying Base Objects

The view is defined over two documented base objects:

• FA_MASS_UPDATE_BATCH_DETAILS — the driving table (aliased MUBD), holding batch-level attribute changes, old and new value identifiers, status code, rejection reason, and the concurrent request identifier.
• FA_ADDITIONS — the asset master (aliased AD), supplying the human-readable ASSET_NUMBER.

The view also invokes the PL/SQL package FA_CUA_ASSET_WB_APIS_PKG to translate stored identifiers into display values, notably GET_CATEGORY_NAME, GET_LEASE_NUMBER, and GET_ASSET_KEY_NAME. The definition is a UNION of six branches, each restricted to a single ATTRIBUTE_NAME value: CATEGORY (branch 1), LEASE_NUMBER (2), SERIAL_NUMBER (3), ASSET_KEY (4), DISTRIBUTION (5), and the remaining generic attributes (6). Each branch returns a literal discriminator (1–6) and joins MUBD to AD on ASSET_ID. Documented metadata identifies the referenced objects as FA_ADDITIONS (synonym), FA_CUA_ASSET_WB_APIS_PKG (package), and FA_MASS_UPDATE_BATCH_DETAILS (synonym).

Key Columns

• BATCH_ID — the mass update batch that produced the detail row.
• ASSET_NUMBER — the affected asset, retrieved from FA_ADDITIONS.
• Old / New Value — column pairs derived from ATTRIBUTE_OLD_ID and ATTRIBUTE_NEW_ID, resolved through the FA_CUA_ASSET_WB_APIS_PKG functions for category, lease, and asset key; raw for serial number, distribution, and generic attributes.
• STATUS_CODE — outcome of the update attempt (for example, processed versus rejected).
• REJECTION_REASON — explanation when a row did not process successfully.
• ATTRIBUTE_NAME — which attribute the row concerns; also fixes the UNION branch and the discriminator literal.
• CONCURRENT_REQUEST_ID — the concurrent request that executed the mass update, joining to FND_CONCURRENT_REQUESTS.REQUEST_ID.

Common Use Cases and Queries

The most frequent scenario is tracing the assets changed by a specific concurrent request. A straightforward query is:

SELECT batch_id, asset_number, attribute_name, status_code, rejection_reason
FROM apps.fa_mupd_v
WHERE concurrent_request_id = :request_id;

Additional scenarios include listing only rejected rows for remediation, summarizing outcomes per batch, and joining to FND_CONCURRENT_REQUESTS to obtain the request name, completion phase, and dates. Because identifiers are resolved to display values, results can be exported directly for audit or reconciliation without further lookup.