A few thoughts (mostly just the obvious stuff):
I would tease apart what your "API" is doing:
You have some order capture service that exposes TMF622
And that service is going to submit the order into downstream systems
So consider the data required by the down stream systems and how that informs data model in your order capture service.
Consider data validation, mapping and enrichment.
Then map the TMF622 data model to that of your service - keeping them logically separate.
But I would say the golden rules is think end-to-end, posting the order to a TMF622 API is only one step in an overall process, you might have qualification, address lookups, customer identification, etc. etc. Think through how the whole thing will hang together - e.g. consider how will the client come by the references in the order.
Spend some time reading up on the SID, reading the API guides, letting the big picture sink in.
Read TMF630, the guidelines.
------------------------------
Alasdair MacLeod
BT Group plc
------------------------------
Original Message:
Sent: May 19, 2021 00:56
From: Manoj Mohan
Subject: Order submission using TMF 622 API
Hi Team,
I am working on a thread where we are submitting a JSON Payload to the TMF622 API
And then expect the TMF622 API to update the legacy system
Has anyone worked on similar implementations in the recent past and can offer any insights ?
Thanks
Manoj
------------------------------
Manoj Mohan
Prodapt North America, Inc
------------------------------