Asset Retirements Limitations

In the absence of a suitable Oracle web service, we’ve implemented a download solution using a BI Report.

The data downloaded through the BI Report leverages some, but not all, of the access controls used in the Oracle Fusion ERP UI. To ensure only authorized users can access information, administrators manage download access through a profile option.

The download is intended for the following types of users: * Users that are restricted by Business Units or * Users with Implementer roles.

This download is not designed for users with data access restricted by the "VIEW" access function security.

There is a bug in the Oracle REST web service that is preventing the Retirements DFFs with Number and Date Attributes from being uploaded. A service request has been logged with Oracle to address this issue. If you’d like more information about this, please log a support case with More4apps here. This issue is fixed in Oracle version 26A.

Approval workflows cannot be enforced or processed when using direct API integration methods. While approval governance is fully supported via the Oracle Fusion Assets UI and our Fixed Assets Mass Additions Integrator, direct integration for the following operations is unsupported on approval-enabled Asset Books: Asset Additions, Asset Adjustments, Asset Assignment Transfers, Asset Retirements.

These four direct Integrators bypass the staging interface (FA_MASS_ADDITIONS) and attempt synchronous, real-time writes directly to core production tables. Enforcing an approval workflow requires the transaction engine to halt for human intervention. Because data cannot sit in a "Pending Approval" state within live production tables, the system prevents the write to maintain data integrity. As a result, the transaction engine aborts the process, returning an immediate execution error.