Results for “fa_mass_retirements”

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

Overview

FA_MASS_RETIREMENTS is the driving table for Oracle Assets mass retirement and mass reinstatement activity in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a single mass transaction definition — a set of criteria that Oracle Assets uses to identify a population of assets eligible for retirement, and then to track the concurrent processes that either retire or reinstate that population. The table resides in the FA schema and belongs to the OFA - Assets product family.

Because the table stores both the selection criteria (cost ranges, asset number ranges, date ranges, segment ranges) and the request handles for the retirement and reinstatement concurrent programs, it functions as a controlling object rather than a pure transaction detail table. Mass retirement is normally initiated from the Mass Retirements window or via the Mass Retirements concurrent program, and the resulting execution entries are held in FA_MASS_RET_EXCEPTS, which reference this table by MASS_RETIREMENT_ID.

From a dimensional modeling perspective, the documented FK topology (references to multiple independent parents such as FA_BOOK_CONTROLS, FA_ADDITIONS_B, FA_LOCATIONS, PA_PROJECTS_ALL, FND_CONCURRENT_REQUESTS, and FA_GROUP_ASSETS) suggests a link classification rather than a pure hub or satellite. In a Data Vault implementation, MASS_RETIREMENT_ID would serve as the link key connecting the retirement/reinstatement process to its book, asset range, location, category, project, and concurrent request participants.

Key Information Stored

• MASS_RETIREMENT_ID — surrogate primary key. The unique index FA_MASS_RETIREMENTS_U1 alongside the PK constraint FA_MASS_RETIREMENTS_PK make this column the single documented business-key candidate.
• BOOK_TYPE_CODE — identifies the asset book to which the mass retirement applies; foreign key to FA_BOOK_CONTROLS.
• STATUS — current state of the mass retirement record (e.g., pending, completed, or in error).
• RETIREMENT_DATE — the date on which retirement is applied to the selected assets.
• RETIREMENT_TYPE_CODE and ASSET_TYPE — control which retirement accounting and asset categories are in scope.
• FROM_ASSET_NUMBER / TO_ASSET_NUMBER — the asset number range that defines which assets are selected; both reference FA_ADDITIONS_B.
• FROM_COST / TO_COST and FROM_THRESHOLD_AMOUNT / TO_THRESHOLD_AMOUNT — cost-based selection criteria.
• FROM_DATE_PLACED_IN_SERVICE / TO_DATE_PLACED_IN_SERVICE — date-placed-in-service range filter.
• LOCATION_ID, CATEGORY_ID, EMPLOYEE_ID — filtering by location (FA_LOCATIONS), category (FA_CATEGORIES_B), and assigned employee (PSB_EMPLOYEES).
• SEGMENT1_LOW … SEGMENT30_LOW / SEGMENT1_HIGH … SEGMENT30_HIGH — low/high range pairs for each accounting flexfield segment, allowing mass retirement scoped to a specific distribution range.
• RETIRE_REQUEST_ID, REINSTATE_REQUEST_ID, CREATE_REQUEST_ID — foreign keys to FND_CONCURRENT_REQUESTS capturing the concurrent program instances that created, retired, or reinstated the population.
• GROUP_ASSET_ID and GROUP_ASSOCIATION — link to FA_GROUP_ASSETS for grouped asset handling; PROJECT_ID and TASK_ID support project-related retirement via PA_PROJECTS_ALL and PA_TASKS.
• Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centres on auditing which assets were selected for retirement, verifying that the retirement and reinstatement concurrent requests completed, and reconciling proceeds of sale or cost of removal postings. A frequent reporting query joins the retirement record to its concurrent requests:

• List recent mass retirements with their book and status: SELECT mr.MASS_RETIREMENT_ID, mr.BOOK_TYPE_CODE, mr.STATUS, mr.RETIREMENT_DATE FROM FA_MASS_RETIREMENTS mr WHERE mr.BOOK_TYPE_CODE = :book ORDER BY mr.CREATION_DATE DESC;
• Check concurrent program outcomes: join RETIRE_REQUEST_ID / REINSTATE_REQUEST_ID / CREATE_REQUEST_ID to FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS to confirm phase and status.
• Review exceptions: join FA_MASS_RET_EXCEPTS on MASS_RETIREMENT_ID to identify assets that failed validation during the run.
• Segment-range audit: filter using SEGMENTn_LOW/SEGMENTn_HIGH to confirm the accounting flexfield range used in a particular mass transaction.
• Reversal support: identify records with a populated REINSTATE_REQUEST_ID to trace reinstatement history.

Related Objects

• FA_MASS_RET_EXCEPTS — child table holding per-asset exceptions; joins on MASS_RETIREMENT_ID.
• FA_BOOK_CONTROLS — via BOOK_TYPE_CODE; defines the book and period context.
• FND_CONCURRENT_REQUESTS — via RETIRE_REQUEST_ID, REINSTATE_REQUEST_ID, and CREATE_REQUEST_ID.
• FA_ADDITIONS_B — via FROM_ASSET_NUMBER and TO_ASSET_NUMBER; the asset master.
• FA_LOCATIONS and FA_CATEGORIES_B — via LOCATION_ID and CATEGORY_ID; selection filters.
• FA_GROUP_ASSETS — via GROUP_ASSET_ID for grouped asset retirement.
• PA_PROJECTS_ALL and PA_TASKS — via PROJECT_ID and TASK_ID for project-related retirement.
• PSB_EMPLOYEES — via EMPLOYEE_ID, identifying the responsible employee.