Inventory Transactions Integrator Limitations
While the Inventory Transactions Integrator provides robust bulk-management capabilities for Oracle ERP Cloud inventory movements, its functionality is governed by the underlying Oracle REST Web Services. Users should be aware of the following constraints when working with this integrator.
General Limitations
-
The Organization attribute is a mandatory filter requirement for the Oracle REST Web Service and must be provided for all Create, Update, Delete, and Download operations.
-
Only transactions that have not yet been processed by Oracle ERP Cloud can be updated or deleted. Processed transactions that have updated inventory balances are considered final and cannot be modified or removed through this integrator.
-
Descriptive Flexfields (DFFs) associated with inventory transactions may have context-sensitive segments. Not all DFF configurations are guaranteed to be supported in all environments.
-
The volume of records returned in a single download is subject to the Oracle REST Web Service pagination limits. Very large datasets may need to be retrieved using multiple downloads with more specific filter criteria.
Known Specific Limitations
The following limitations relate to specific fields and behaviours within the integrator. These are driven by constraints in the Oracle REST Web Services and will be addressed in future releases.
Use Current Cost Flag
The integrator currently supports the Yes value for the Use Current Cost Flag only. Support for the No value will be introduced in a coming release. Additionally, the Completed Transactions web service does not return the Use Current Cost Flag in its response payload, therefore this field will not be populated when downloading from the Completed Transactions source.
Inventory Organization Name for Interface Transaction Downloads
The Oracle REST Web Services for the Interface Transactions do not return the Inventory Organization Code in their response payload — they return the Organization Name only. To mitigate this, the integrator includes an Inventory Organization Name column on the sheet. When a download is performed using this source, the Organization Code will be automatically defaulted from the corresponding Organization Name.
Transaction Descriptive Flexfields (DFFs)
For Descriptive Flexfield (DFF) values to be processed correctly, the DFF segment configuration on the Interface transaction must match the DFF segment configuration on the base transaction table. If the interface DFF settings and the base DFF settings are mismatched, DFF values may not be transferred or may be mapped to the wrong segments during processing. Ensure your Oracle DFF setup is consistent across both layers before using DFF columns in the integrator.
Transaction Source Code, Source Line ID, and Source Header ID Not Returned by Completed Transactions
The Completed Transactions Oracle REST Web Service does not currently return the Transaction Source Code, Source Line ID, or Source Header ID in its response payload. As a result, these fields will appear blank when downloading data from the Completed Transactions source.
Lot and Serial Controlled Items
The integrator does not currently support items that are both lot‑controlled and serial‑controlled. This capability will be included in a future release.
Serial Number Cannot Be Updated on a Pending Transaction
Serial numbers assigned to a pending interface transaction cannot be modified after the transaction has been created. This is because the serial number is used as the key identifier to locate the individual serial record in the Oracle interface table
If a serial number was entered incorrectly on a pending transaction, the following steps must be taken:
-
Use the Delete function to remove the incorrect transaction from the interface table.
-
Use the Create function to re-enter the transaction with the correct serial number.
This limitation applies to all serial-controlled transaction types supported by this integrator, including Miscellaneous Receipt, Miscellaneous Issue, and Project Material Issue where the item is serial-controlled. This is not a More4apps limitation — it is a constraint of the Oracle inventoryStagedTransactions REST Web Service, which does not expose an update operation for serial number values on the serial child resource (/child/serials).
Lot Number Cannot Be Updated on a Pending Transaction
Lot numbers assigned to a pending interface transaction cannot be modified after the transaction has been created. This is because the lot number is used as the key identifier to locate the corresponding lot record in the Oracle interface table, and the integrator—when using the nested API to perform updates—cannot locate a modified lot number. This limitation will be addressed in a future release.
Download Record Limit — Interface Transactions
The Oracle REST Web Service for Interface Transactions (inventoryStagedTransactions) enforces a maximum page size of 500 records per call. This limit is imposed by Oracle at the endpoint level and cannot be increased by setting the limit parameter above 500. As a result, the download process can retrieve only up to 500 records per request. This is an Oracle‑known limitation and will be resolved once Oracle updates the web service in a future release
Future Enhancements
The limitations listed in this document will be reviewed and addressed over time as Oracle improves the underlying REST Web Services and as More4apps introduces additional features to this integrator. For the latest information on enhancements and fixes, refer to the More4apps Release Notes.
If you encounter issues not listed here, or have enhancement suggestions, please contact More4apps support at the community portal.