Update Inventory Transactions

The Update function allows you to modify existing inventory transactions (INV_TRANSACTIONS_INTERFACE) that have been created but not yet processed by Oracle ERP Cloud. To update a transaction, the Upload Action column value must be set to Update or update records.

How to Update

The recommended approach for updating transactions is to first download the existing records using the Download function. This ensures you are working with the most current data held in Oracle ERP Cloud and reduces the risk of overwriting incorrect values. Refer to the Download Inventory Transactions section for more information on how to download.

Use the Download function to retrieve the existing transactions you wish to modify.
Change the Upload Action column to Update for each row you want to modify.
Make the required changes to the relevant columns in the sheet.
Validate and upload. The integrator will submit the changes to Oracle ERP Cloud via the REST Web Service.

Fields Available for Update

The following fields can be modified during an update operation. Fields marked as key identifiers cannot be changed as they are used to locate the existing record in Oracle.

Field

Updatable

Description

Organization

Key identifier — used to locate the record.

Transaction Date

Yes

Can be adjusted to reflect the correct date.

Transaction Type

Key identifier — used to locate the record.

Item Number

Key identifier — used to locate the record.

Transaction UOM

Yes

Can be adjusted to reflect the correct uom.

Transaction Quantity

Yes

Can be adjusted to reflect the correct quantity.

Account Alias

Yes

Applicable to Account Alias Receipt and Account Alias Issue types.

Distribution Account

Yes

Applicable to Account Issue and Account Receipt types.

Subinventory

Yes

Can be changed to a different valid subinventory.

Locator

Yes

Can be updated if the subinventory is locator-controlled.

Note: Only transactions that have not yet been processed by Oracle can be updated. Once a transaction has been processed and inventory balances have been affected, the record is considered final and cannot be modified through this integrator.

Project Details

The Project Details fields can be updated for Project Material Issue/Receipt transactions that are still in a pending, unprocessed state. The same fields available during Create are available for update.

Field

Updatable

Description

Project Number

Can be updated to redirect the cost to a different active project. The replacement project must be open and active.

Task Number

Yes

Can be updated to a different task within the same or updated project. The task must belong to the selected Project Number and must be active and open.

Expenditure Type

Yes

Can be updated to reclassify the expenditure type prior to processing.

Expenditure Organization

Yes

Can be updated to a different expenditure organization if required.

Lot Details

Lot details can be updated for pending lot-controlled transactions. The Lot Number cannot be changed as it is used to identify the lot record; however the Lot Quantity can be corrected prior to processing.

Field

Updatable

Description

Lot Number

Key identifier — used to locate the lot record. Cannot be changed.

Lot Quantity

Yes

Can be corrected prior to processing. The sum of all lot quantities must still equal the Transaction Quantity on the main line.

Lot Expiration Date

Yes

Can be corrected for receipt transactions prior to processing.

Serial Details

Serial numbers assigned to a pending transaction cannot be changed as they uniquely identify each unit in Oracle inventory. If an incorrect serial number was entered during Create, the transaction must be deleted and re-created with the correct serial number.

Field

Updatable

Description

Serial Number*

Key identifier — serial numbers cannot be changed on an existing transaction. Delete and re-create the transaction to correct an incorrect serial number.

Note: Serial numbers uniquely identify individual units in Oracle. Because they are used as the key to locate the serial record, they cannot be modified. If a serial number was entered incorrectly, use the Delete function to remove the transaction and create a new one with the correct serial number.

Upload Results

As with the Create operation, the way results are returned after an Update upload depends on the Process Option configured in the Settings Form.

Process Option

Behaviour After Upload

Online Processing

Oracle processes the updated transaction immediately. Results are written back to the sheet in real time upon completion of the upload. Any validation failures or Oracle rejections are displayed directly on the relevant row without any further action required.

Background Processing

Updated transactions are loaded into the Oracle interface tables and a concurrent program is submitted to process them. Results are not returned immediately. Use the Scheduled Processing options on the More4apps ribbon to manage and monitor the concurrent program.

Scheduled Processing (Background Processing Only)

Use the Scheduled Processing option on the More4apps ribbon to submit and monitor the Oracle concurrent program for your updated transactions. The same three actions apply as for the Create operation:

Action

Description

Submit

Submits the Oracle concurrent program to process the updated transactions loaded into the interface tables.

View

Opens the Oracle concurrent program monitor so you can check the current status of the submitted program (e.g., Pending, Running, Completed, or Error).

Refresh

Updates the sheet with the final processing status once the concurrent program has completed. Successfully processed updates are marked accordingly. If a transaction encountered an error, the error detail is written back to the relevant row in the sheet.

Note: Always run Refresh after the concurrent program has completed to ensure the sheet reflects the final update outcome. Until Refresh is run, the sheet will not display whether records were successfully updated or encountered errors.

Warning: Submit processes all pending interface transactions

The Manage Inventory Transactions concurrent program has no parameters. Clicking Submit in the More4apps ribbon fires the process with no filtering — it will pick up and process every pending transaction across all organizations sitting in the interface table at that moment, not just the records loaded by the current user. Coordinate with other users before submitting to avoid unintentionally processing another user’s incomplete or unvalidated data.