Open APIs

Hi everyone,

I'm Rijad, a software engineer working in back-end development and currently exploring how to integrate TM Forum Open APIs into our digital transformation efforts.

I'm currently looking into the ProductOrdering API and I have a few questions regarding its use in a B2B scenario:

1. In the case of multi-line orders (e.g., multiple products bundled under one order), is there a recommended way to handle order dependencies using this API?

2. Is the relatedParty object meant to support partner channel scenarios, and if so, how should we extend or map custom roles?

3. Has anyone implemented validation rules or lifecycle status tracking (e.g., Acknowledged, InProgress, Rejected) in combination with orchestration flows? I'd love to learn how that was approached.

I appreciate any pointers, documents, or experiences you can share. Thanks in advance!

Best regards,
Rijad

------------------------------
Rijad Karsic
ZIRA Ltd.
------------------------------

hi,

for Q1, TM Forum has an ODA component PODOM. That guy is responsible for orchestration, dependencies etc.

for Q2, relatedParty is an array, so each product can have multiple parties and each party can have a role. if a party has 2 roles, we reference the party twice, each time with one role.

for Q3, there is not much we do I would recommend! In a nutshell, each team, each system has its own solution.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------

hi,

Hi,

Thanks a lot for the detailed clarifications!

For Q1, it's helpful to know that PODOM within the TM Forum ODA is the component handling orchestration and dependencies.

For Q2, your explanation about the relatedParty array makes perfect sense-referencing the same party multiple times with different roles is a clear and flexible approach.

As for Q3, I appreciate the candid insight. It's good to know there's no one-size-fits-all solution and that each team/system handles it in their own way.

------------------------------
Denijal Jamakovic
TO BE VERIFIED
------------------------------

Original Message:
Sent: May 21, 2025 10:53
From: Matthieu Hattab
Subject: Questions about ProductOrdering use in B2B flow

hi,

for Q1, TM Forum has an ODA component PODOM. That guy is responsible for orchestration, dependencies etc.

for Q2, relatedParty is an array, so each product can have multiple parties and each party can have a role. if a party has 2 roles, we reference the party twice, each time with one role.

for Q3, there is not much we do I would recommend! In a nutshell, each team, each system has its own solution.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------

Whilst this does not answer Q3 you might find section 

4. Component Interaction Diagram  in
IG1242 ODA Component Inventory v19.0.0 - Published Deliverables - TM Forum Confluence 
helpful as it shows the ODA components and their interactions -  and hence use of Open APIs 

------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------

Original Message:
Sent: May 23, 2025 04:24
From: Denijal Jamakovic
Subject: Questions about ProductOrdering use in B2B flow

hi,

Hi,

Thanks a lot for the detailed clarifications!

For Q1, it's helpful to know that PODOM within the TM Forum ODA is the component handling orchestration and dependencies.

For Q2, your explanation about the relatedParty array makes perfect sense-referencing the same party multiple times with different roles is a clear and flexible approach.

As for Q3, I appreciate the candid insight. It's good to know there's no one-size-fits-all solution and that each team/system handles it in their own way.

------------------------------
Denijal Jamakovic
TO BE VERIFIED
------------------------------


Original Message:
Sent: May 21, 2025 10:53
From: Matthieu Hattab
Subject: Questions about ProductOrdering use in B2B flow

hi,

for Q1, TM Forum has an ODA component PODOM. That guy is responsible for orchestration, dependencies etc.

for Q2, relatedParty is an array, so each product can have multiple parties and each party can have a role. if a party has 2 roles, we reference the party twice, each time with one role.

for Q3, there is not much we do I would recommend! In a nutshell, each team, each system has its own solution.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS

just to avoid confusion, "dependencies" are managed in the product catalogue. PODOM consumes the product catalogue to understand the dependencies and use that information to decompose and orchestrate each order line.

you can read IG1228 which has a few use cases that describe product catalogue and product order "resource model" with many examples of dependencies.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------

Original Message:
Sent: May 23, 2025 04:24
From: Denijal Jamakovic
Subject: Questions about ProductOrdering use in B2B flow

hi,

Hi,

Thanks a lot for the detailed clarifications!

For Q1, it's helpful to know that PODOM within the TM Forum ODA is the component handling orchestration and dependencies.

For Q2, your explanation about the relatedParty array makes perfect sense-referencing the same party multiple times with different roles is a clear and flexible approach.

As for Q3, I appreciate the candid insight. It's good to know there's no one-size-fits-all solution and that each team/system handles it in their own way.

------------------------------
Denijal Jamakovic
TO BE VERIFIED
------------------------------


Original Message:
Sent: May 21, 2025 10:53
From: Matthieu Hattab
Subject: Questions about ProductOrdering use in B2B flow

hi,

for Q1, TM Forum has an ODA component PODOM. That guy is responsible for orchestration, dependencies etc.

for Q2, relatedParty is an array, so each product can have multiple parties and each party can have a role. if a party has 2 roles, we reference the party twice, each time with one role.

for Q3, there is not much we do I would recommend! In a nutshell, each team, each system has its own solution.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS