Skip to main content
Question

Receive Shop Order IFS REST API

  • November 24, 2025
  • 1 reply
  • 16 views
D
Do Gooder (Customer)

I have been trying to receive a shop order using an IFS REST API.

 main/ifsapplications/projection/v1/ReceiveShopOrderHandling.svc/ReceiveShopOrderSet

I execute this request successfully. I append the correct fields, quantities, and toggle the flags to denote reception. All rolls smooth and returns and object key and tag reference.

I then execute

main/ifsapplications/projection/v1/ReceiveShopOrderHandling.svc/ReceiveShopOrderSet(Objkey='" + key + "')/IfsApp.ReceiveShopOrderHandling.ReceiveShopOrder_FinishExecute?"

to finish the execution and flush the virtual table. Both requests are successful and return 200 status opcodes. However, nothing happens in IFS. There is zero indication any receipt was performed. I pass in the correct order number, release number, sequence number, and part number. I also append my finish request with the appropriate e-tag and object key.

Is this a known bug?

 

1 reply

Indika99
Do Gooder (Employee)
Forum|alt.badge.img+3
  • Indika99
  • Do Gooder (Employee)
  • November 25, 2025

Hi ​@dylanvicc, 

 

This behavior is not a product defect. It is related to how the ReceiveShopOrderHandling projection is designed and used internally by IFS.

According to IFS experts, this API is primarily built to support the Shop Floor Workbench assistant flow in the web UI, not for direct transactional integrations.

Why your update is not reflected in IFS

When you call ReceiveShopOrderSet, the data is not written directly to the operational database tables. Instead, it is stored in a virtual staging structure used by the assistant workflow.

The FinishExecute action only simulates clicking the Finish button in the assistant. If any intermediate step, validation, or required flag is missing in your API call sequence, the data remains in the staging layer and is never committed to the actual shop order tables.

The returned HTTP status codes such as 201 Created or 200 OK only confirm that:

  • The staging record was created, or

  • The finish action was accepted by the service

They do not confirm that the shop order receipt was successfully posted in the backend.

Important note

Assistant based APIs require a full sequence of steps, similar to how the web UI processes data. If one step is missing or the payload is incomplete, the final commit does not occur.

Recommended approaches

Option 1: Use a dedicated API for Shop Order receipts

  • From IFS Cloud 22R2 onwards, use the Premium API ShopFloorConnector and its action ReceiveOrder.
    This API is designed for integrations and directly updates shop order data without using the assistant staging mechanism.

  • For IFS 10 or earlier, consider using ShopFloorReportsHandling.
    This API supports reporting completed quantities and labor without going through the Shop Floor assistant flow.

Option 2: Fully simulate the assistant workflow

If you must use ReceiveShopOrderHandling, you need to replicate the complete assistant process by performing:

  • All UI validation steps

  • Required intermediate PATCH calls

  • Proper flag handling and status changes
    before calling FinishExecute.

Related discussion

A similar scenario has been discussed here:
https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/receiving-shop-order-using-rest-api-27071

 

Hope this is helpful.

Terms & ConditionsCookie settingsAccessibility statement