registration_rates

Posting night of this rate row (one row per stay night) = transactions.post_date. NOT a service/schedule date — for the “charge for day X” concept see transactions.charge_date.

DEAD COLUMN – declared DEFAULT 0 NOT NULL but never written by any code path (verified: 0 non-zero rows on sample and aonestar). Do not read it and do not start writing it: the room-only amount depends on the meal plan and rate inclusions, which live outside this table (registration.adult/child/mealtype_id/rateplan_id), so a row-level trigger could not keep it fresh and rate rows are written in bulk. Use sp_rate_schedule_breakdown(…).room for the GROSS room-only amount and .room_net for the amount net of itemizers. Same applies to service, tax, extrabed, extrabed_svc, extrabed_tax, abf, lunch, dinner and discount on this table.

DEAD COLUMN – never written. See the comment on registration_rates.room. For the service-charge slice use sp_rate_schedule_breakdown(…).room_service.

DEAD COLUMN – never written. See the comment on registration_rates.room. For the tax slice use sp_rate_schedule_breakdown(…).room_tax.

Guard column only: set by rpc.reservation_namelist_create/clear and read by fn_get_room_charge_dept to tell whether the room charge was already posted. It is mostly NULL (0/26,867 rows on aonestar). It is NOT the department that posting uses – sp_auto_post / sp_auto_post_folio resolve that as COALESCE(rate_plan.room_charge_dept, fn_sys_param(‘AUTO_POST’,‘ROOM’)), which is also what sp_rate_schedule_breakdown reports as room_net_dept.