The consolidated capex plan: one row for each capex proposal approved for the consolidation plan, made when it was…
The consolidated capex plan: one row for each capex proposal approved for the consolidation plan, made when it was approved.
What the proposal decided is read off it and cannot be changed here: fiscal_year (with fiscal_calendar_name, the fiscal calendar the plan is counted on, and fiscal_year_start_month, the month that calendar starts its year in, so fiscal_year 2027 starting in April is April 2026 to March 2027), scheme_code (the Request ID), the unit and location, category_master_id and budget_category_id (the Category and Sub-Category), priority (the Item Type: VITAL, ESSENTIAL or DESIRABLE), investment_type (NEW or CARRY_FORWARD), carried_from_line_id (the Reference ID), scheme_value (the Capex Amount) and category (PROJECT, SPECIFIED, CLUBBED or FLEXIBLE). proposal_status is the proposal’s: APPROVED_FOR_PLAN while it is being planned, then PLAN_APPROVED or PLAN_REJECTED.
The coordinator, item_description, quantity, nature, fresh_sanction_amount, approved_carryover_amount and justification started as the proposal had them and are changed here without changing the proposal. The rest is planning: carryover_cashflow_cy (the approved cashflow of the current year carried forward) and carryover_order_reference for a carry forward; py1_carryover_outflow and py1_fresh_outflow, the estimated cash outflow in the planned year (PY1); py2_outflow to py5_outflow for the four years after it; gst_rate_id, the GST rate, a value of your organisation’s GST Rate Master list, with gst_rate_name its name and gst_rate_percent its rate as a whole percentage; py1_month_01 to py1_month_12, the planned year’s cash flow month by month from its first month; and asset_block_id, the asset block, a value of your organisation’s Asset Block Master list, with asset_block_name its name. depreciation_rate_percent is the Applicable Depreciation: the block’s depreciation rate as a whole percentage, as the block had it when the row was saved with it. It is kept while the row keeps that block, so a rate changed on the list afterwards does not change a row already planned; it is null where the block had no rate.
Worked out, never stored: py1_carryover_total is carryover_cashflow_cy plus approved_carryover_amount; py1_proposed_plan is that plus fresh_sanction_amount; py1_outflow is py1_carryover_outflow plus py1_fresh_outflow; py1_outflow_difference is py1_proposed_plan less py1_outflow; py2_py5_outflow is the four outer years added up; py1_cashflow_total is the twelve months added up, and py1_cashflow_balanced whether it equals py1_outflow. Each _gst_credit and _gst column is the GST inside that figure, the figure divided by one plus the rate times the rate, rounded to two places, and null where the figure or the rate is missing; py1_gst_credit_total adds up the twelve months’ credit, and equals py1_gst_credit when the months are balanced, give or take rounding.
The planning is approved in a workflow of its own. A row goes to its first level by itself when its proposal is approved, and its approvers plan it while it waits on them; where no workflow holds it, it stays here for your organisation’s planners to plan and send with api.submit_capex_consolidated_line. When the last level approves, proposal_status is PLAN_APPROVED; a rejection at any level is PLAN_REJECTED.
request_id and request_display_status are the planning’s own approval request, the open one where there is one, as your approvals show it; null until the plan is sent for approval. last_approved_by_name and last_approved_at are who gave the planning its latest approval, and when. Both are null until a level of the planning approves it, and stay null for a plan approved at once because no workflow applied; the approval of the proposal itself is never shown here. planning_open says whether the planners can still change the row: they cannot once the plan is approved or rejected, or while it is with approvers. planning_needs lists, in the sheet’s words, what the row still needs before its planning can be approved or sent: any of the six mandatory fields (a GST rate whose value has no rate counting as missing), the carried cashflow of a carry forward, and the twelve months adding up to py1_outflow; it is empty when nothing. may_edit says whether you may change the row now: while it is with its approvers only the approver it waits on may, and otherwise anybody holding finance.capex_consolidation.edit. may_send says whether you may send it for approval.
You see every row of the plan if you may view the consolidated plan. Without that, you see a row only while a step of its planning approval is waiting on you under your own authority, so that you can plan it before you sign; once you have decided, it is gone from what you see.
Headers
Limiting and Pagination
Limiting and Pagination
Preference
count=none Query Parameters
Filtering Columns
Ordering
Limiting and Pagination
Limiting and Pagination
Response
OK
Note:
This is a Foreign Key to capex_asset_blocks.id.
150Note:
This is a Foreign Key to capex_asset_blocks.id.
150Note:
This is a Foreign Key to business_units.id.
Note:
This is a Foreign Key to capex_natures.id.
Note:
This is a Foreign Key to capex_plans.id.
Note:
This is a Foreign Key to capex_plan_lines.id.
60Note:
This is a Foreign Key to capex_plan_lines.id.
1012Note:
This is a Foreign Key to capex_asset_blocks.id.
150200Note:
This is a Foreign Key to capex_invite_candidates.id.
3Note:
This is a Foreign Key to asset_cost_to_keep.currency_id.
200120Note:
This is a Foreign Key to capex_asset_blocks.id.
150Note: This is a Primary Key.
16200Note:
This is a Foreign Key to capex_invite_candidates.id.
20012060200122460Note:
This is a Foreign Key to entry_currencies.for_site_id.
200
