Option 2 is the better option with slight changes.
Mobile Family Bundle with Child offers and child PS as given below with the cardinality rules
1. Mobile telephony (1:1 relationship)
2. Data 10 G (1:1 relationship / 0:1 relationship - as the case may be)
3. Data shared (0:1 relationship)
The Product Order API will have the above line items with the actions codes ADD against each one
More than the API structure, the reusability of the child offers and PS in other bundles should be one important criterion that should determine your modelling practices.
Regards,
------------------------------
Sri Jagadish Baddukonda
Sigma Systems
------------------------------
Original Message:
Sent: Nov 13, 2020 14:02
From: Somesh Batra
Subject: How does the product spec hierarchy translate to product order in TMF622
The given example in TMF622 specification guide shows bundle offer and corresponding handling of product order. Is there an example for composite specification which has children specification. Should it create separate entries with order item relationship or use hierarchy of creating a nested order item. E.g. If I have a bundle offer with 2 mobile services in it. There are multiple ways to create product order structure.
1) Option 1, Create each specification as individual order item and create relationship between order items. Also will there be any product relationship in this case?Order Item | Order Action | Product Offer | Product Spec | Order Item Relationship | Product Relationship | Child Order Item |
100 | Add | Mobile Family Bundle Offer | | Bundle (101,102) | | |
101 | Add | Mobile Offer | 10GB Data, Unlimited Spec | Relies On (103) | | |
103 | Add | | Mobile Telephony | | ? | |
102 | Add | Add-On Mobile offer | Shared Data, unlimited Call Spec | Relies On (104) | | |
104 | Add | | Mobile Telephony | | ? | |
Does TM Forum suggest to use one option on other? Also what is best example of using ProductRelationship? That may be more appropriate for change order where we already have instance id of products?
------------------------------
Somesh Batra
Pegasystems, Inc.
------------------------------