Search Results concurrent




Overview

The concurrent program FACTFR is documented within Oracle E-Business Suite under the product CUA - Capital Resource Logistics - Assets. Its user-facing name is Post Mass External Transfer, and its functional description is recorded as External Transfers Post Program. The program belongs to the mass external transfer posting flow within the Capital Resource Logistics asset family, where external transfer transactions are validated and posted to the asset repository. An associated data record also carries the description "Post Mass External Transfer (Obsolete)," indicating that earlier iterations of this program or its associated configuration were retired as the product evolved.

According to the ETRM metadata for release 12.2.2, the concurrent program is disabled (Enabled: No). This status is significant: although the executable and metadata remain registered in the application, the program is not intended for submission in a standard 12.1.1 or 12.2.2 environment. Customers upgrading from earlier releases may still encounter the definition in the Concurrent Programs form, but it should be treated as a legacy, non-operational object.

Execution Details

The documented execution attributes for FACTFR are as follows:

  • Execution Method: Spawned
  • Argument Method: Database fetch
  • Executable: FACTFR
  • Execution File: FACTFR
  • User Name: Post Mass External Transfer
  • Product: CUA - Capital Resource Logistics - Assets
  • Enabled: No

The "Spawned" execution method indicates that the program is launched as an operating-system-level process rather than as an in-process PL/SQL call, and that it is typically invoked from within another concurrent program or process rather than submitted directly by a user. The "Database fetch" argument method means the program does not rely on a standard SRS parameter window; instead, its arguments are derived from database queries at runtime. No subroutine name is documented, and the executable filename is identical to the program short name, FACTFR.

How to Run

Because the program is disabled and uses the Spawned execution method with database-fetched arguments, it is not designed for direct submission from the Submit Requests (SRS) window. In environments where a comparable posting process is active, the standard approach is to submit the parent mass external transfer program, which in turn spawns the post program after the transfer batch has been validated. Operators should confirm the enabled status of the parent transfer program and verify that the associated transaction batches are in a postable state before initiating the workflow.

For releases where an equivalent posting program remains enabled, the general guidance is to run the post process after all external transfer interface records have been loaded and validated, and to review the request log for records rejected during posting. Because argument values are fetched from the database, there is no parameter form to populate; any scoping, such as organization or batch selection, is governed by the parent process.

Related Objects

The following object categories are commonly associated with the post mass external transfer process in this product line:

  • External transfer interface and staging tables used to hold mass transfer transactions prior to validation and posting.
  • The parent mass external transfer concurrent program that spawns FACTFR after validation completes.
  • Asset transfer APIs and posting routines that update asset assignment, location, and transfer history records in the asset repository.
  • Request log and output files generated by the spawned FACTFR process, used for reconciliation and error analysis.
  • Related concurrent program definitions for the CUA - Capital Resource Logistics - Assets product, including those governing transfer validation and purge activities.

Because the documented record is marked obsolete and disabled, implementers should confirm the current, supported replacement program through the ETRM for the target release before attempting to reinstate or invoke this definition in a 12.1.1 or 12.2.2 instance.