Search Results fa_mass_transfers




Overview
Explore in AI Chat

Overview

The FA_MASS_TRANSFERS table is a core data object within the Oracle E-Business Suite (EBS) Fixed Assets (OFA) module. It serves as the primary repository for storing metadata and control information for mass transfer requests. A mass transfer is a critical business process that enables the bulk reclassification of fixed assets, typically involving changes to their location, cost center (General Ledger account), or asset category. This table does not store the detailed transaction lines for each individual asset transferred; instead, it holds the overarching request parameters and status, functioning as a control table that governs the execution of the mass transfer job submitted via a concurrent request.

Key Information Stored

The table's primary key is MASS_TRANSFER_ID, which uniquely identifies each mass transfer request. As indicated by its foreign key relationships, the table stores the defining criteria and results of a transfer operation. Key columns include CONCURRENT_REQUEST_ID, which links to FND_CONCURRENT_REQUESTS to track the job's submission and status. The transfer rules are defined by FROM_LOCATION_ID and TO_LOCATION_ID (referencing FA_LOCATIONS), FROM_GL_CCID and TO_GL_CCID (referencing GL_CODE_COMBINATIONS), and CATEGORY_ID (referencing FA_CATEGORIES_B). The BOOK_TYPE_CODE column, referencing FA_BOOK_CONTROLS, specifies the asset book to which the mass transfer applies. Additional columns typically track the request date, who initiated it, the effective date of the transfer, and the processing status.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting mass asset transfers. Common queries involve joining this table to related entities to generate detailed audit reports. For example, to list all completed mass transfers for a specific book, a query might join FA_MASS_TRANSFERS to FND_CONCURRENT_REQUESTS and the various code tables (FA_LOCATIONS, GL_CODE_COMBINATIONS) to present a human-readable summary. Another critical use is identifying the parameters of a specific transfer request, perhaps to investigate why certain assets were or were not selected by the concurrent process. A sample SQL pattern is:

  • SELECT fmt.MASS_TRANSFER_ID, fcr.request_id, fl_from.location_code FROM_LOCATION, fl_to.location_code TO_LOCATION, fmt.EFFECTIVE_DATE FROM FA_MASS_TRANSFERS fmt, FND_CONCURRENT_REQUESTS fcr, FA_LOCATIONS fl_from, FA_LOCATIONS fl_to WHERE fmt.CONCURRENT_REQUEST_ID = fcr.request_id AND fmt.FROM_LOCATION_ID = fl_from.location_id (+) AND fmt.TO_LOCATION_ID = fl_to.location_id (+) AND fmt.BOOK_TYPE_CODE = 'CORP';

Related Objects

As per the provided metadata, FA_MASS_TRANSFERS has direct foreign key dependencies on several fundamental EBS tables. These include FND_CONCURRENT_REQUESTS (for process execution), FA_LOCATIONS (for transfer locations), GL_CODE_COMBINATIONS (for General Ledger accounts), FA_CATEGORIES_B (for asset categories), and FA_BOOK_CONTROLS (for the asset book). The mass transfer concurrent program uses this table as a source for its run-time parameters. The detailed results of the transfer—the individual asset transactions—are stored in transaction tables such as FA_TRANSACTION_HEADERS and FA_ADJUSTMENTS, linked via the MASS_TRANSFER_ID. For reporting, views like FA_MASS_TRANSFERS_V may provide a more accessible layer on top of this base table.

  • Table: FA_MASS_TRANSFERS 12.1.1

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_MASS_TRANSFERS,  object_name:FA_MASS_TRANSFERS,  status:VALID,  product: OFA - Assets ,  description: Mass transfer request information ,  implementation_dba_data: FA.FA_MASS_TRANSFERS , 

  • Table: FA_MASS_TRANSFERS 12.2.2

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_MASS_TRANSFERS,  object_name:FA_MASS_TRANSFERS,  status:VALID,  product: OFA - Assets ,  description: Mass transfer request information ,  implementation_dba_data: FA.FA_MASS_TRANSFERS , 

  • Table: FA_LOCATIONS 12.2.2

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_LOCATIONS,  object_name:FA_LOCATIONS,  status:VALID,  product: OFA - Assets ,  description: Location flexfield segment value combinations ,  implementation_dba_data: FA.FA_LOCATIONS , 

  • Table: FA_LOCATIONS 12.1.1

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_LOCATIONS,  object_name:FA_LOCATIONS,  status:VALID,  product: OFA - Assets ,  description: Location flexfield segment value combinations ,  implementation_dba_data: FA.FA_LOCATIONS , 

  • Table: FA_CATEGORIES_B 12.1.1

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_CATEGORIES_B,  object_name:FA_CATEGORIES_B,  status:VALID,  product: OFA - Assets ,  description: Default financial information for asset categories (base MLS table) ,  implementation_dba_data: FA.FA_CATEGORIES_B , 

  • Table: FA_CATEGORIES_B 12.2.2

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_CATEGORIES_B,  object_name:FA_CATEGORIES_B,  status:VALID,  product: OFA - Assets ,  description: Default financial information for asset categories (base MLS table) ,  implementation_dba_data: FA.FA_CATEGORIES_B , 

  • Table: FA_BOOK_CONTROLS 12.1.1

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_BOOK_CONTROLS,  object_name:FA_BOOK_CONTROLS,  status:VALID,  product: OFA - Assets ,  description: Control information that affects all assets in a depreciation book ,  implementation_dba_data: FA.FA_BOOK_CONTROLS , 

  • Table: FA_BOOK_CONTROLS 12.2.2

    owner:FA,  object_type:TABLE,  fnd_design_data:OFA.FA_BOOK_CONTROLS,  object_name:FA_BOOK_CONTROLS,  status:VALID,  product: OFA - Assets ,  description: Control information that affects all assets in a depreciation book ,  implementation_dba_data: FA.FA_BOOK_CONTROLS ,