New reporting cycle
Follow the steps below to create a reporting cycle for Bluefin Foods Group. Creation produces a draft; activation is a separate action on the final step.
Basics
Framework and period
2
Scope
Organizations in scope
3
Methodology lock
GWP, approach, conventions
4
Review and activate
Verify and activate
Scope comes from the Reporting Boundary. Boundaries remain the system of record; this step references the existing structure and never edits it. Reporting Boundaries admin
All organizations
Sets isAllOrganization: true and forces the organization list empty. Turning this on clears and disables the tree below.
Company level selected
isCompanySelected · an independent boolean, combinable with either mode below
Search the boundary structure
Bluefin Foods Group · group root · 5 business units · 45 units beneath
Aquaculture · business unit · 3 entities · 6 sites
0 of 10 in scopeProcessing and Canning · business unit · 3 entities · 8 sites
12 of 12 in scopeBluefin Processing Singapore · legal entity · Singapore
4 of 4Jurong Cannery · plant
Tuas Cold Store · cold store
Senoko Smokehouse · plant
Bluefin Processing Indonesia · legal entity · Indonesia · 3 sites
4 of 4Bluefin Processing Malaysia · legal entity · Malaysia · 2 sites
3 of 3Cold Chain Logistics · business unit · 3 entities · 5 sites
5 of 9 in scopeBluefin Cold Chain Malaysia · legal entity · Malaysia
3 of 3Shah Alam DC · distribution center
Johor Bahru DC · distribution center
Bluefin Cold Chain Singapore · legal entity · Singapore · 1 site
2 of 2Bluefin Cold Chain Vietnam · legal entity · Vietnam · 2 sites
0 of 3Retail Brands · business unit · 3 entities · 5 sites
0 of 9 in scopeCorporate Services · business unit · 2 entities · 2 sites
5 of 5 in scopeSelected ids are stored sorted and deduplicated. Collapsed branches keep their selections; per-branch counts include every unit beneath, expanded or not. Ticking a branch ticks its whole subtree; a green dash marks a branch with a partial selection.
Annotation · not proposed UIPM condition 2026-08-23: this step must never limit tenants to a narrow cookie-cutter shape. The tree is the tenant's existing boundary structure at whatever depth it has; search and collapse handle real-tenant scale. Drawn deep on purpose.
Annotation · not proposed UIOrg scope is a resolution input, and its canonical serialization is part of cycle identity for collapse and idempotency (spec 4.9): all-organizations forces an empty id list, ids are stored sorted and deduplicated. A same-months, same-framework pair that differs only in org scope is treated as overlap and is not supported in I1 (spec 8.3 step 1), so
409 CYCLE_OVERLAP can fire even when the org selections differ.
Back
Cancel
Save as draft
Continue to Methodology lock
State gallery · Scope step · annotation · not proposed UI
All organizations ON · tree cleared and disabled
All organizations
isAllOrganization: true · organizationIds: [] (forced empty, canonical form)
Company level selected
Cleared and disabled · organizationIds forced empty
Select allUnselect all
Bluefin Foods Group · group root · 45 units beneath
Aquaculture
0 of 10Processing and Canning
0 of 12Cold Chain Logistics
0 of 9Retail Brands
0 of 9Corporate Services
0 of 5422 ORG_SCOPE_INVALID · no scope mode chosen
All organizations
Company level selected
0 of 45 units in scope
Select allUnselect all
Bluefin Foods Group · group root · 45 units beneath
Aquaculture
0 of 10Processing and Canning
0 of 12Cold Chain Logistics
0 of 9Retail Brands
0 of 9Corporate Services
0 of 5422 ORG_SCOPE_INVALID
Choose a scope: all organizations, company level, or at least one specific organization.
Search filtering the tree · matches shown with their ancestors
penang
Bluefin Foods Group · ancestor
Processing and Canning · ancestor
Bluefin Processing Malaysia · ancestor
Penang Plant · plant · match
Search is a client-side filter over the boundary tree: matches render with their ancestor chain, everything else is hidden. Counts and selections are not changed by filtering.