Introduction/ Issue:
Occasionally an item is assigned to the wrong category name in the inventory catalog, or a category needs to be renamed after go-live. There was no simple, supported way for the functional team to correct this directly in the UI for a specific item, so we needed a repeatable way to update an item’s category name using the Fusion REST API.
Why we need to do / Cause of the issue:
An item can be mapped to the wrong category name when it is created or migrated – for example through a data load, a template default, or a manual entry error. Left uncorrected, this affects catalog reporting, searches, and any downstream process that groups items by category. Since there wasn’t a bulk-correction screen for this, each occurrence needed a quick, safe, scriptable fix that could be repeated for other items without touching unrelated attributes.
How do we solve:
The fix is a three-step REST API flow against the itemsV2 resource: look up the item, find its current category assignment, then patch that assignment with the corrected category name. Environment host names below are masked as customer-test.fa.ocs.oraclecloud.com.
Step 1 – Look up the item by item number to get its ItemId:
GET – URL:
https://customer-test.fa.ocs.oraclecloud.com/fscmRestApi/resources/11.13.18.05/itemsV2?q=ItemNumber=ERU2101S
From the response, locate the child link where “name”: “ItemCategory”.
Step 2 – Call the ItemCategory child collection for that item to find the current assignment:
GET – URL:
https://customer-test.fa.ocs.oraclecloud.com:443/fscmRestApi/resources/11.13.18.05/itemsV2/<ItemId>/child/ItemCategory
From the response, copy the “ItemCategoryAssignmentId” value (for example, 300000011489044) and append it to the URL above.
Step 3 – PATCH the specific category assignment with the corrected category name:
PATCH – URL:
https://customer-test.fa.ocs.oraclecloud.com:443/fscmRestApi/resources/11.13.18.05/itemsV2/<ItemId>/child/ItemCategory/<ItemCategoryAssignmentId>
Payload:
{
“CategoryName”: “ERU”
}
The response confirms the assignment now reflects the corrected category name.
Conclusion:
Using three chained REST calls – a GET to find the item, a GET to find its current category assignment, and a PATCH to correct it – we were able to fix mis-categorized items directly and safely, without a manual UI workaround. The same three-step pattern can be reused for any item that needs its category name corrected.
