Description
Split a supplied hierarchical business-unit code at a literal separator.
Administrative records depend on policy dates, authorization scope, attendance denominators and accounting definitions. A calendar-date shift does not skip holidays, a quorum fraction is not a quorum decision, and a weighted voting fraction differs from economic ownership. Recorded signatory presence does not authenticate a signature or establish authority.
Split a supplied hierarchical business-unit code at a literal separator.
When to use this tool
Use Business Unit Code Parent Split when you already have unitCode, separator and need to split a supplied hierarchical business-unit code at a literal separator.
How to use the tool and how it works
- Enter unitCode, separator. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read parentCode, leafCode, hasParent. Inspect hasParent before interpreting the associated values.
Require nonempty separator/code; split literally and reject empty segments. Return the last segment, preceding segments rejoined, and whether more than one segment exists.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| unitCode | Unit Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| separator | Separator | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| parentCode | Parent Code | Required. Text; maximum UTF-16 length 8192. |
| leafCode | Leaf Code | Required. Text; maximum UTF-16 length 8192. |
| hasParent | True for more than one literal separator-delimited segment; an empty segment is rejected. | Required. Boolean. |
{
"input": {
"unitCode": "ORG/FIN/AP",
"separator": "/"
},
"output": {
"parentCode": "ORG/FIN",
"leafCode": "AP",
"hasParent": true
}
}Limitations and assumptions
- One segment returns empty parentCode and hasParent=false. No hierarchy, organizational unit, ownership, code grammar or actual relationship is verified.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Check controlled policies, meeting records, contracts and account definitions. Apply the complete applicable rules when actual approval, payment or governance matters; local version selection and arithmetic do not make those determinations.
References
Similar or alternative tools
- Policy Version Effective Date Choice
Choose the most recently effective supplied policy version by an as-of date.
- Policy Acknowledgment Revision Match
Compare an acknowledged revision with a supplied current revision.