addHierarchyRelationship
- Description
- This transaction adds a parent-child relationship between two existing nodes in an existing hierarchy. Hierarchy relationship details include parent node ID, child node ID, description, start date and end date.
- Web Services
- Operation name: addHierarchyRelationship
- Example
- Add a relationship between two nodes, Accounting and Finance, where the Finance node is the parent and the Accounting node is the child in the relationship.
- Usage information
- Not applicable
- Preconditions
- Parent node must exist.
Child node must exist.
- Mandatory input
- ParentNodeId
- ChildNodeId
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- If start date not supplied, default to current system date.
The relationship start date must be equal to or greater than the hierarchy start date.
The relationship start date must be equal to or greater than both parent node and child node start dates.
The relationship end date must be less than or equal to the hierarchy end date.
The relationship end date must be less than or equal to both parent node and child node end dates.
Only one active parent-child relationship can exist between any two nodes at any given point in time.
Cyclical relationships are not permitted. The child of a node cannot also be the node's parent.
- Request message
- <TCRMTxType> addHierarchyRelationship
<TCRMTxObject> DWLHierarchyRelationshipBObj
<TCRMObject> DWLHierarchyRelationshipBObj
- Response objects
- DWLHierarchyRelationshipBObj
- Special note
- Not applicable