ER: Additional Search Criteria Need for GetOrderDetails Operation on OrderInformationService Webservice
(Doc ID 1546580.1)
Last updated on FEBRUARY 04, 2019
Applies to:Oracle Fusion Distributed Order Orchestration - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 1.0]
Oracle Fusion Order Management Cloud Service - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
***KM Review - Dec 2016 - Checked for Relevance***
Get Order Details web-service needs modification to accept attributes other than order number and source system:
Currently the GetOrderDetails web service requires the caller to pass the source sales order number as well as the source system.
However there may be use cases where the caller has a requirement to pass otther attributes apart from the source order number. Attributes like Delivery Option (EFF) or Parcel number (which will be stored in shipment number field of DOO_FULFILL_LINE_DETAILS table) may also be passed.
For example, the customer places an order of 10 items and some are of HOME DELIVERY type and some are CLICK & COLLECT. Customer service should be able to query the order (using the GetOrderDetails web service) based on order number and then further filter the query with the delivery option (say HOME DELIVERY). In this case they do not want to see the fulfillment lines having any other delivery option.
Similarly, the user may wish to query the sales orders based on other criteria, like the parcel number which is stored in the shipment number field in DOO on the fulfillment line.
Relaxing of Source System in Get Order Details Service:
Another requirement is for the GetOrderDetails webservice to relax the source system parameter requirement which is mandatory in the current release of DOO.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document