sn_ind_tmt_orm_order, sn_ind_tmt_orm_order_line_item are not extended from base task

[davidnovak]

Hello TSM enthuasists,

we are starting to use Telecommunications Service Management in our project and as was looking through it i found some unclearness i'd like you to ask about.

I found out the tables (we will be interacting with) "sn_ind_tmt_orm_order" and "sn_ind_tmt_orm_order_line_item" are extended from same CSM tables (in particular "sn_csm_om_order_line_item" and "sn_csm_om_order"). However these CSM tables are stand-alone (they don't have any other inherited table), see below:

When i was checking the same in Service Management (essentialy the where we migrate from) the same logical tables ("sm_order", "sm_task") are extended from base "task" table

And there goes the question: Why is there this "disparity"? Is there any specific reason behind this? Are there are any plans that in upcoming releases the original tmt / cms tables will be extended from base task table too?

From my POV i would expect since both order tables are used for same or similar purpose i would expect the baseline will the same hence there will same inheritance for both.

Thank you anybody for your inputs.

David

[Kailash Bhange]

Hi davidnovak,
Greetings!

As far as i have understoond above, below is your question. Please correct me if I am wrong.

1. Why are below two tables extended from TASK table and not the other four tables.
extended from TASK: -
sm_order
sm_task

not extended from TASK: -
sn_ind_tmt_orm_order
sn_ind_tmt_orm_order_line_item
sn_csm_om_order_line_item
sn_csm_om_order

2. Is there any plan to extend four tables from TASK in future?

-------
Ok, so to answer your question.
1. Why are below two tables extended from TASK table and not the other four tables.
-> Extending an existing ServiceNow table means the table you create will inherit the parent table’s columns as well as the table’s business logic. The most commonly extended table is the Task table.
But in TSM module I do not see any major need to extending it from TASK rather the CSM order/order line item table are more suitable here(as per both column and business logic). I suppose that's the main/major reason behind this one.

2. Is there any plan to extend four tables from TASK in future?
-> Maybe the product owner and the core team of ServiceNow can confirm on this. @Tom Schnarr @Sapan Behera 

Hope this helps.
If my answer resolves your issue, please mark my answer as ✅ Correct & Helpful based on the validations.

Thank You!
Regards,
Kailash

[Kailash Bhange]

Hello David,

Greetings!

Could you please confirm if the comment above has helped you and you don't see the issue?

Request you to mark the answer as correct so that the thread can be closed.

Thank You!
Regards,
Kailash
LinkedIn

[VaranAwesomenow]

My two cents

Order management which is part of CSM and Service order management which is part of TSM are stand-alone by design since they are fulfilling a different use case compared to service request management (ITSM). This also applies to other areas of TSM and CSM, for example product inventory (TSM) an extension of sold product (CSM) is also a standalone entity even though it has a association with assets and CIs on CMDB and ITSM side, same approach is taken for order management table model as well.