Patching a Domain Service Order by using TMF622 api

[ursnani]

Hi All,

I cam across a scenario as below.

We are using TMF622 API fro creating a Product order which in return create a Customer order with Order type as Product Order. Now we have a Product Specification and that a related Service Specification.

Initially from TMF622 we are getting all the Product Specification Characteristics and they are filled out. But after the decomposition happens based on the relationship Domain orders PO(Product Order) and SO(Service Order)bare getting created. Now we are expecting some characteristics values that are related to Service Order and we want to use TMF622 API. 

Can we use TMF622 API for patching a Service order ?

Did anyone come across this scenario, if so can you guide me in right way.

Any help is greatly appreciated.

Thank you.

[ShashankInamdar]

Hello @ursnani ,
I am afraid TMF622 cannot be used to enrich the decomposed Service 'domain' order.

Potentially there are two options -

[1] Use TMF641 for the Service Order enrichment

OR

[2] Maintain a copy of the chars on Service Spec, on the Product Spec. And then send a patch TMF622 to enrich the values which then gets updated on the Service Spec via Attribute mapping.

My personal recommendation will be taking approach 1.

[ursnani]

Hi @Shashanklnamdar,

Thanks for the Reply
Unfortunately those two options will not work for me for the below reasons.

Option1: We cannot use TMF641 for Service "Domain" Order as the API because as we need to send the Order sysid, and if we use TMF 641 API it will look for OrderType as Service. 

In our case we are creating Order by using TMF622 where when it creates Order, order type will be Product.
TMF641 will not accept ordertype as Product Customer orders, I tried this Option but it gave a error saying that Order not found because of Order type.

Option2: we cannot move ahead with this because It will create Duplicate characteristics when the order is decomposed at Order line item. It will have same characteristics with same values but the parent will be different like the PO and SO, But individually they have only one characteristics.

Is there any option or did anyone come up with scenario, or may be an Enhancement to handle the Service Specification for the TMF622 from your side ?

Thanks.

[ShashankInamdar]

I agree and understand the challenge with both the options.

Here's what you could do - As the order decomposes, generate notifications for all/some Service 'domain' Orders and return the sys id of the domain order in the notification response.

During a patch, TMF641 can then use this sys id.

Will that work for you?

[ursnani]

Hi @ShashankInamdar 

You missing a point here I guess, to Use the TMF 641 the "Ordertype" of the Customer Order should be "Service". In our case the "Ordertype" is "Product". So by default we cannot use any TMF641 APIs.

We are bound to use only TMF622, which you guys are not handling the the Service Specification.

Thats the root cause or issue we are facing.