Open APIs

We are implementing a gateway that translates TMF622 Product Order into TMF641 Service Order for fulfillment.

For Move with gap, the requested scheduling is on the Product Order item, not only at the root: each item can carry its own from and to dates, and from and to can differ across items (different locations or time windows per line).

Current behavior (root level only):
When the Product Order has root-level dates, we map:

• productOrder.requestedStartDate → serviceOrder.requestedStartDate
• productOrder.requestedCompletionDate → serviceOrder.requestedCompletionDate

Question:
What is the recommended or normative guidance for representing these item-level Move-with-gap dates in TMF641, given that from and to are per order item and not necessarily aligned across items?

Specifically:

1. How should item-level "from" and "to" map to serviceOrderItem (e.g. requestedStartDate / requestedCompletionDate on the item, use of related entities, or characteristics) when the semantic is disconnect at T1 / reconnect at T2 per item?

Pointers to official examples, IG / implementation notes, or prior community guidance for Move or analogous scenarios would be appreciated.

Thank you.

Hi Irfak,

You have 2 options: 

1. Raise individual TMF641 requests for the disconnect, reconnect scenario
2. Use relatedServiceOrderItem to manage the dependencies, although you would need to extend the attribute set (deviating from the standard) to carry specific request start and completion dates.