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]

Ok, understood the restriction you have, but TMF622 is not the right choice for this use case.

TMF defines 622 usage to action upon the Product Domain entities and OMT is following this principle.  

To change/enrich/patch the Service, TMF641 is the recommended API.

[ursnani]

Hi @ShashankInamdar 

In our case we cannot use TMF641 what could be our other options ?

[ursnani]

Hi @ShashankInamdar 
Is there any other way we can achieve or is this something You guys can take it up and build a solution around this ?

[ShashankInamdar]

Hi @ursnani ,

If you cannot use TMF641, other options are either doing the Service Order enrichment manually via the workspace portal. This can be done as an Order Task assignment to the respective stakeholders.

Alternatively, you can explore the use of Table APIs to update the characteristics on the Domain Order - you can do so by updating the Order Characteristics table for that specific OLI, Spec and Char.

[gourav_aggarwal]

Hi @ursnani 

We are also facing a similar issue where the product order is being created via TMF 622 and service orders are decomposed from the product-service spec relationships and end up in the sn_ind_tmt_orm_service_order table. For using a patch 641, these should be present with Order Type as "Service" in sn_ind_tmt_orm_order table. We are stuck with submitting Inflights by changing service characteristic attributes. 

Were you able to figure out a solution?