The has-hypercube arc is the keystone of XDT. Every other dimensional construct, the hypercube-dimension arc, the dimension-domain arc, the domain-member arc, all of them serve to populate a structure that has-hypercube hangs off the primary item. Get this arc right and the dimensional graph reads cleanly. Get it wrong and you get cryptic errors at both the instance and DTS levels, often without an obvious single cause.
Two arcrole flavours live on this arc. all means "the primary item must report against this hypercube"; the arc asserts a positive constraint. notAll means "this primary item must not report against the listed sub-cube"; the arc carves an exclusion out of an otherwise applicable cube. Both arcs live in the definition linkbase, attached to a link:definitionArc element, and both come with a small set of XDT-specific attributes that change how the cube behaves.
xbrldt:contextElement is mandatory on a has-hypercube arc. Its job is to tell every fact reporting against this cube where to put its dimensional members in the context: inside xbrli:segment or inside xbrli:scenario. Forget contextElement and you raise xbrldte:HasHypercubeMissingContextElementAttributeError at the DTS level. Set it to segment in an ESEF report and you have authored a finding, because Reporting Manual section 2.1.3 requires scenario.
xbrldt:closed equals true is the second knob. By default a hypercube is open: contexts may carry dimensions beyond the ones declared on the cube. Closed reverses that: the container must contain exactly the declared dimensions and no others. Closed hypercubes are how supervisory frameworks like DPM keep dimensional contexts strictly within the schema.
xbrldt:targetRole is the cleverest of the three. It lets the rest of the dimensional graph (the hypercube-dimension arcs, the dimension-domain arcs, the domain-member arcs) live in a different ELR from the has-hypercube arc itself. That separation is how a single dimensional structure gets reused across multiple statements without duplicating the wiring. Read targetRole as "follow this link to find where the dimensions actually live". Many production taxonomies are split this way; missing the targetRole when chasing arcs is a common source of confusion.
The has-hypercube arc connects a primary item (or a placeholder concept) to a hypercube. all means positive (must apply); notAll means negative (must not apply).
xbrldt:contextElement on the has-hypercube arc selects the container (segment or scenario) for the hypercube's dimensions in the instance context.
xbrldt:closed='true' on the has-hypercube arc constrains the container to exactly the listed dimensions.
xbrldt:targetRole on the arc lets the rest of the dimensional graph (hypercube-dimension, dimension-domain, domain-member) live in a different ELR. Useful for sharing dimensional structure across statements.
The has-hypercube arc lives only in the definition linkbase. Confusing it with calculation or presentation arcs is a common reading mistake.
3 questions. Press 1 to 4 to select, Enter to confirm.
Completing this quiz marks the section done in your progress.
Tip: press 1 to 4 to select, Enter to confirm.