Master Data — Core concepts

Concept	Meaning
Enterprise	Top-level organization, including custom URL and service-area policy.
BusinessUnit (BU)	Main data/configuration boundary for payment, billing, timezone, providers.
Org / Site	Physical or logical site under a BU where programs/sessions run.
Account	Family/customer account container.
Account Holder / Contact	Representative contact for an account; profile image belongs to Contact, not Account.
Attendee	Participant/child referenced by booking, subscription, incident, and finance.
Term	Operating/academic period.
ProgramCategory	Program type such as Term Care, Holiday, Class, or Camp.
Program	Concrete program within a category.
TermProgramSet (TPS)	Offering/course in a term; carries schedule, capacity, and pricing context.
TermProduct	Concrete session/slot selected by booking or referenced by schedule.
System image	Built-in or uploaded asset for avatar/course/activity/profile display.

Source entity vs runtime record

Master Data is usually source/reference data. Runtime records like TermBooking, Enrollment, Invoice, and PaymentBatch reference it to know who, where, and which program they operate on.

Ownership summary

Owner	Owns
Enterprise	Custom URL and enterprise service-area policy.
BusinessUnit	BU-scoped settings and data boundary.
Contact	Account holder profile image/avatar.
Attendee	Attendee profile, measurements, product config.
Program/Term structure	Category, program, TPS, product setup and availability.