The Clubbed capex approval notes: the papers a planned Clubbed capex proposal goes to the committee with, a row per…
The Clubbed capex approval notes: the papers a planned Clubbed capex proposal goes to the committee with, a row per note. A proposal may have several; note_no says which of them a row is, 1 for the first raised on it and one more for each raised after, and capex_plan_line_id which proposal it is. A Project, Specified or Flexible proposal’s notes are capex_approval_notes.
What the proposal and its planning decided is read off them and cannot be changed here: fiscal_calendar_name, scheme_code (the Request ID, which is also the Budget ref no.), the unit and location (site_name, location_name), implementing_unit_name (the proposal’s location, or its unit where it names no location), category (always CLUBBED), budget_category_name (the Sub-Category), item_description (the Description of asset, as the consolidated plan has it) and plan_amount (the Amount as per Division’s capex plan: the proposal’s Capex Amount). The tender committee is for Project proposals, so a Clubbed note asks nothing of it.
What the note says is its own. background, justification and technology_rationale are documents: markup with pictures and PDFs named by file id, as a capex proposal’s justification is. vendor_evaluation (up to 4,000 characters), payment_terms (up to 1,000) and specialist_recommendation (up to 2,000) are words. order_placement_on, installation_start_on, completion_on, cash_flow_on and capitalization_on are the implementation schedule, each on or after the one before it. The expense summary is basic_cost_amount, freight_amount, installation_amount, taxes_amount, contingency_amount and gst_credit_amount, the cash flow cash_flow_q1_amount to cash_flow_q4_amount and the capitalization capitalization_q1_amount to capitalization_q4_amount, each from zero up to 99,999,999.99. vendor_selection is SINGLE_PARTY or MULTI_PARTY. Its four lists are capex_clubbed_note_vendors, capex_clubbed_note_risks, capex_clubbed_note_advances and capex_clubbed_note_write_offs; vendor_count and write_off_count say how many rows the first and the last hold.
expense_total is the five costs of the expense summary added together, the contingency among them: it is the Cost of project proposal and the Adjusted Amount as well, and null until all five are given. cash_flow_total and capitalization_total add up their four quarters, null until all four are given.
The note is approved in a workflow of its own, sent with submit_capex_clubbed_note once it is written; note_needs lists what it still needs before it can be sent or approved, empty when nothing: its columns, and vendors or risks for a list that is not yet complete. note_status is OPEN until it is decided, APPROVED when the last level approves it (or at once when sent with no workflow to ask) and REJECTED when a level rejects it, which is final, with note_status_reason what was said. request_id and request_display_status are its approval request, the open one where there is one; last_approved_by_name and last_approved_at who last approved a level of it, and when, which on an approved note is its final approval. may_edit says whether you may change it now: while it is with its approvers only the approver it waits on may, and otherwise anybody holding finance.capex_approval_note.edit, until it is decided. may_send says whether you may send it.
created_at, created_by_id and created_by_name say when the note was raised and by whom; created_source says what raised it where nobody signed in did. updated_at, updated_by_id and updated_by_name say when it was last changed and by whom.
You see every note if you may view approval notes (finance.capex_approval_note.view). Without that, you see a note only while a step of its approval is waiting on you under your own authority.

