The tables behind Social Welfare Scheme Mgmt

Use the stored Program, Assessment and Measure references when importing related records. A readable applicant or program name should not replace its record identity. The planned-benefit duplicate check concerns the same assessment; agree applicant identity and repeated-submission handling separately.

Resolve the current user through People.User before comparing Activities.Owner with that person’s identity. People.Active uses Yes and No. Preserve the Users.User self-reference and establish its platform identity behavior during setup.

Measure definitions establish how to interpret Numerator and Denominator. The ratio is a reporting calculation; retain the underlying inputs and show unavailable when Denominator is missing or zero. Keep benefit disbursements.Amount separate from payment progress and preserve it during the guarded status action.

1. Users and staff. Establish platform Users and People so program and activity ownership resolves correctly.
2. Programs. Import Programs with their owners, operating dates and budgets under the agreed monetary convention.
3. Funding and work. Link funding awards, Activities and Milestones to the intended program. Reconcile existing kickoff names before processing approval-triggered creation.
4. Assessments and benefits. Import eligibility assessments with program and criteria context, then reconcile existing benefit disbursements by Assessment before repeating eligible capture.
5. Expenses. Preserve Expenses evidence and status under the correct program; retain external payment confirmation when importing Paid history.
6. Measures and results. Establish outcome measures definitions before outcome results, preserving reporting periods and evidence. Keep missing denominator inputs distinguishable from zero.