Ericsson Inc.
Original Message:
Sent: Mar 18, 2026 12:15
From: Chintan Acharya
Subject: Extend TMF 641 Service Order with EntityRef Resource at Service Order Level
Hi Plame, thanks for your response , but i believe externalRefernce is the Product Order Id so as to map product order to service order. Then we would lose this mapping or did i get it wrong.
------------------------------
Chintan Acharya
Original Message:
Sent: Mar 18, 2026 11:58
From: Plamen Stanoev
Subject: Extend TMF 641 Service Order with EntityRef Resource at Service Order Level
Why not use order.externalReference[] for that purpose? Each COM system can populate the externalReference with their own type/name and then event consumers can subscribe and filter by these.
------------------------------
Plamen Stanoev
Ericsson Inc.
Original Message:
Sent: Mar 18, 2026 11:23
From: Chintan Acharya
Subject: Extend TMF 641 Service Order with EntityRef Resource at Service Order Level
Hi All,
Based on TMF 641 Spec, RelatedEntity resource is associated at ServiceOrderItem.Service level.
But in my case we have multiple COM systems (e-g- COM1 and COM 2) which are creating Service Orders in the MDO system for same CFS. MDO system has single HUB endpoint which will POST SO State Change events for all SOs created, which then consumer/SO originator systems need to consume/subscribe to.
I would like to include EntityRef (Entity being the Origination System number/identifer) at Service Order Level, so that in the SO State Change event this is reflected back by MDO and consumers can filter or subscribe to HUB with a query filter on ServiceOrder:EntityRef = COM 1
Is it correct or good approach to extend and include EntityRef at Service Order Level ?
Another thought was to re-use ReleatedParty Resource which is already available at Service Order Level in the API Spec, RelatedParty being COM Applicaiton, with Role=OriginatorSystem. But this does not align with Party ABE definition and guidance.
Appreicate your inputs.
Regards,
Chintan Acharya
Senior Solution Architect