Share
Report
67Hi everyone,
We are integrating an OMS (Order Management System) with Dynamics 365 Finance & Operations. The OMS creates return orders in D365 via the ReturnOrderHeadersV2 and ReturnOrderLinesV2 OData entities, and we have some distinct return channels: in-store POS returns, eCommerce returns, and third-party returns (via Loop Returns).
We need D365 to be able to distinguish between these channels so we can configure separate batch jobs with the right behavior per channel. For example, the packing slip posting batch job for POS returns should only pick up POS return orders, not eCommerce ones.
On sales orders, we use SalesOrderOriginCode (SALESORDERORIGINCODE in DMF) to tag the channel, and it works well as a batch job filter. We are looking for an equivalent on return orders.
We could not find any ReturnOrderOriginCode or equivalent channel field on the OData entities.
Question: Is there a recommended standard field on D365 return orders to tag the originating sales channel? Or is the standard practice to use some other field as a channel identifier?
Any guidance from the community would be appreciated.
Question: Is there a recommended standard field on D365 return orders to tag the originating sales channel? Or is the standard practice to use some other field as a channel identifier?
Any guidance from the community would be appreciated.
Categories:
I have the same question (0)
All responses (
Answers (
