Telecom Order Management — TMF641 Service Order Item Relationships Use orderRelationship Field Not serviceOrderItemRelationshipIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } While working with the TMF641 Service Order Management API (v4.1.1), users may encounter a compliance concern where item-level relationships (serviceOrderItem.serviceOrderItemRelationship) appear unsupported in ServiceNow’s current implementation. As per the TMF 641 specification, relationships between individual service order line items should be supported using the serviceOrderItem.serviceOrderItemRelationship construct. However, users observed that only serviceOrderRelationship (order-level relationship) is available Out of Box (OOB), creating confusion about TMF alignment and interoperability with other TMF-compliant systems. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Xanadu and Latest Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } ServiceNow’s implementation of TMF641 follows the standard specification with certain structural adaptations.While TMF641 defines serviceOrderItemRelationship for modeling item-level dependencies, ServiceNow implements this concept using the orderRelationship field at the service order item level to define horizontal relationships between two service order items (also referred to as compatibility rules). The Product Team confirmed that: The orderRelationship field in the payload is the supported construct for representing relationships between service order items.The relationshipType value "Requires"—as mentioned in the TMF specification—is supported within this structure.This design maintains the intent of TMF641 while aligning with ServiceNow’s data model and internal processing logic. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } ServiceNow supports horizontal relationships between two service order items using the orderRelationship field in the payload. Resolution Steps: Use the orderRelationship attribute under each serviceOrderItem to define item-level relationships.The relationshipType value "Requires" (as shown in TMF specification) is supported.Reference the ServiceNow documentation for serviceOrderItem.orderRelationship.relationshipType for detailed examples and schema. Documentation Reference:ServiceNow Service Order Open API DocumentationSample Payload shared by the Product Team: { "serviceOrderItem": [ { "id": "0", "action": "add", "service": { "serviceState": "active", "@type": "CFS", "serviceCharacteristic": [ { "name": "Firewall coverage", "valueType": "choice", "value": "Premium(Up to 50 sites)", "previousValue": "" } ], "serviceSpecification": { "id": "f99546ff07266010a7955b7e0ad300a8", "name": "Managed Firewall Service", "internalVersion": "2" } }, "orderRelationship": [ { "id": "1", "relationshipType": "HasChild" }, { "id": "2", "relationshipType": "HasChild" }, { "id": "2", "relationshipType": "Requires" } ], "state": "new", "@type": "ServiceOrderItem" }, { "id": "1", "action": "add", "service": { "serviceState": "active", "@type": "CFS", "serviceCharacteristic": [ { "name": "Remote CLI troubleshoot support", "valueType": "choice", "value": "Basic support" } ], "serviceSpecification": { "id": "31c5caff07266010a7955b7e0ad3006b", "name": "Firewall Administration", "internalVersion": "1" } }, "orderRelationship": [ { "id": "0", "relationshipType": "HasParent" } ], "state": "new", "@type": "ServiceOrderItem" }, { "id": "2", "action": "add", "service": { "serviceState": "active", "@type": "CFS", "serviceCharacteristic": [ { "name": "Intrusion monitoring CPE Model", "valueType": "string", "value": "5400 series" } ], "serviceSpecification": { "id": "ed168eff07266010a7955b7e0ad30034", "name": "Threat and Intrusion Prevention Service", "internalVersion": "1" } }, "orderRelationship": [ { "id": "0", "relationshipType": "HasParent" } ], "state": "new", "@type": "ServiceOrderItem" } ], }