Transform `f1_comp_balance_db` xbrl + dbf

This table is the debit sibling of f1_bal_sheet_cr (see #1810).

Steps:

• Mapping PR #2112
• Transformation PR #2127

Table Notes

• Only Instant, no duration.
• Lots of XBRL columns, lots of DBF rows.
• Lots of classic row-mapping to be done.
• Pretty clear one-to-one correspondence between XBRL factoids & DBF row numbers.
• DBF DATA IS QUARTERLY, keep only report_prd == 12 records.

Transformation Plan

• Keep just the end-of-year balances.
• Output will be a single column of dollar balances, with a categorical column indicating what that value is.
• Aggregation will happen via calculation arcs / aggregation trees or an association table.
• For now apply the sign conventions by category in transform_main()?

Mapping instructions

The following values should be put in the xbrl_factoid column of dbf_to_xbrl.csv, in association with the analogous DBF row_number / row_literal value. They can be used more than once, if the same DBF value is associated with different rows in different years that appear in that file.

In the row_type column, categorize each DBF row as one of:

• header
• reported_value
• calculated_value

In the notes column, indicate anything unusual about the mapping (for human eyes only).

accounts_receivable_from_associated_companies
accrued_utility_revenues
accumulated_deferred_income_taxes
accumulated_provision_for_amortization_of_nuclear_fuel_assemblies
accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility
accumulated_provision_for_depreciation_and_amortization_of_nonutility_property
accumulated_provision_for_uncollectible_accounts_credit
advances_for_gas
allowance_inventory_and_withheld
amortization_fund_federal
assets_and_other_debits
cash
cash_and_working_funds
clearing_accounts
construction_work_in_progress
current_and_accrued_assets
customer_accounts_receivable
deferred_debits
deferred_losses_from_disposition_of_utility_plant
depreciation_fund
derivative_instrument_assets
derivative_instrument_assets_hedges
derivative_instrument_assets_hedges_long_term
derivative_instrument_assets_long_term
extraordinary_property_losses
fuel_stock
fuel_stock_expenses_undistributed
gas_stored_current
gas_stored_underground_noncurrent
interest_and_dividends_receivable
investment_in_associated_companies
investment_in_subsidiary_companies
liquefied_natural_gas_stored_and_held_for_processing
merchandise
miscellaneous_current_and_accrued_assets
miscellaneous_deferred_debits
noncurrent_portion_of_allowances
nonutility_property
notes_receivable
notes_receivable_from_associated_companies
nuclear_fuel_assemblies_in_reactor_major_only
nuclear_fuel_in_process_of_refinement_conversion_enrichment_and_fabrication
nuclear_fuel_materials_and_assemblies_stock_account_major_only
nuclear_fuel_net
nuclear_fuel_under_capital_leases
nuclear_materials_held_for_sale
other_accounts_receivable
other_electric_plant_adjustments
other_investments
other_materials_and_supplies
other_preliminary_survey_and_investigation_charges
other_property_and_investments
other_regulatory_assets
other_special_funds
plant_materials_and_operating_supplies
preliminary_natural_gas_survey_and_investigation_charges_and_other_preliminary_survey_and_investigation_charges
preliminary_survey_and_investigation_charges
prepayments
rents_receivable
research_development_and_demonstration_expenditures
residuals
sinking_funds
special_deposits
special_funds
spent_nuclear_fuel_major_only
stores_expense_undistributed
temporary_cash_investments
temporary_facilities
unamortized_debt_expense
unamortized_loss_on_reacquired_debt
unrecovered_plant_and_regulatory_study_costs
unrecovered_purchased_gas_costs
utility_plant
utility_plant_and_construction_work_in_progress
utility_plant_and_nuclear_fuel_net
utility_plant_net
working_funds

[zaneselvans]

I think it’s just that they aren’t great at sticking to their own naming conventions.

If you look these factoids up in the XBRL Taxonomy you’ll see that in the human readable description they all say (Major Only), but only some of them add that to the machine readable name.

[zaneselvans]

No, because we want those rows to get dropped from the DBF tables, as they contain no data.