addHierarchyUltimateParent
- Description
- This transaction adds an ultimate parent designation to an associated node in an existing hierarchy.
- Web Services
- Operation name: addHierarchyUltimateParent
- Example
- Add a head office group to an existing organization chart and designate it as an ultimate parent.
- Usage information
- Not applicable
- Preconditions
- Associated node must exist.
- Mandatory input
- HierarchyNodeId
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- If start date not supplied, default to current system date.
The ultimate parent start date must be equal to or greater than the hierarchy start date.
The ultimate parent start date must be equal to or greater than the associated node start date.
The ultimate parent end date must be less than or equal to the hierarchy end date.
The ultimate parent end date must be less than or equal to the associated node end date.
Only one node can be designated as an active ultimate parent at any given point in time.
A node designated as an ultimate parent cannot have any parent relationships for the duration of the time that it is ultimate parent.
- Request message
- <TCRMTxType> addHierarchyUltimateParent
<TCRMTxObject> DWLHierarchyUltimateParentBObj
<TCRMObject> DWLHierarchyUltimateParentBObj
- Response objects
- DWLHierarchyUltimateParentBObj
- Special note
- Not applicable