[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-19。"],[[["\u003cp\u003eThis document outlines common issues encountered when exporting rebilling data from the Partner Sales Console to BigQuery, such as missing billable costs, discrepancies in list costs, and null values in certain columns.\u003c/p\u003e\n"],["\u003cp\u003eWhen dealing with charges that lack associated list costs, the \u003ccode\u003ecost_at_list\u003c/code\u003e column may show \u003ccode\u003enull\u003c/code\u003e, so it's recommended to use \u003ccode\u003eSUM(IFNULL(cost_at_list, cost))\u003c/code\u003e in queries to account for this.\u003c/p\u003e\n"],["\u003cp\u003eTaxes are calculated based on the location in the account details and displayed in exported data as \u003ccode\u003ecost_type\u003c/code\u003e set to \u003ccode\u003e'tax'\u003c/code\u003e, with \u003ccode\u003enull\u003c/code\u003e values for \u003ccode\u003ecustomer_cost\u003c/code\u003e and \u003ccode\u003echannel_partner_cost\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eUnassigned or unassociated billing subaccounts can lead to \u003ccode\u003enull\u003c/code\u003e values in several columns like \u003ccode\u003eentitlement_name\u003c/code\u003e, \u003ccode\u003ecustomer_name\u003c/code\u003e, and \u003ccode\u003echannel_partner_name\u003c/code\u003e, which can be fixed by properly assigning them to customers.\u003c/p\u003e\n"],["\u003cp\u003eIf the BigQuery export is not adding new data, it could be due to a recently enabled export, service account access issues, billing not enabled, row or column-level access control, no parent Cloud Billing accounts, or an invalid schema.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot issues with BigQuery exports\n\nThis page presents common issues you might encounter when using the\nPartner Sales Console to export rebilling data to BigQuery, and how\nto resolve these issues.\n\nNo values for billable costs\n----------------------------\n\nRows that represent taxes, adjustments, and rounding are specific to your\ninvoice reconciliation process and do not contain values for billable costs to\ncustomers or channel partners.\n\nCharges without list costs\n--------------------------\n\nSome charges (for example, support charges) do not have an associated list cost.\nRepricing configurations for these charges that use the *List Cost* rule will\nuse the base cost to calculate the repriced cost.\n\nWhen you create a BigQuery export using the\nPartner Sales Console, the line item for these types of charges will show\n`null` in the `cost_at_list` column. This may lead to a discrepancy when viewing\nthe charge in the export and when viewing it on the Google Cloud console.\n\nTo resolve this issue, use `SUM(IFNULL(cost_at_list, cost))` instead of\n`SUM(cost_at_list)` when you query a rebilling export.\n\nTaxes in exported data\n----------------------\n\nTaxes for every billing subaccount associated with your primary billing account\nare calculated based on the location listed in your account details. Your\ncustomers' locations will not affect taxes charged to their accounts.\n\nIf a billing subaccount has their `cost_type` set to `'tax'`, exported data will\nshow our attribution of your local tax rate as it applies to that account. This\nvalue is based on the customer's portion of usage and any additional costs they\nincur.\n\n### Null values for costs\n\nAny rows in your exports that have a `cost_type` of `'tax'` will show `null` in\nthe `customer_cost` and `channel_partner_cost` fields. Before you generate an\ninvoice for this type of customer, make sure you review these rows and verify\nthe correct values are in place.\n\nUnassigned and unassociated subaccounts\n---------------------------------------\n\nCreating a Google Cloud entitlement and linking it to a customer creates a\nbilling subaccount for that customer. If you don't create this entitlement you\nmay see unassigned billing subaccounts under your main billing account.\n\nUsing the Partner Sales Console to remove a customer that has assigned\nbilling subaccounts will cause those subaccounts to become unassociated.\n\n### Null values for subaccounts\n\n[Using BigQuery to export data](/channel/docs/troubleshoot/channel/docs/rebilling/export-data-to-bigquery)\nthat includes unassigned or unassociated subaccounts will cause the following\ncolumns to show a value of `null` for those subaccounts.\n\n- entitlement_name\n- customer_name\n- customer_cost\n- credits.customer_amount\n- channel_partner_name\n- channel_partner_cost\n- credits.channel_partner_amount\n\nTo resolve this issue, you should [assign these billing subaccounts to\ncustomers](https://support.google.com/channelservices/answer/10022594).\n\nRestoring export table to a previous state\n------------------------------------------\n\nIf you accidentally dropped your export table or deleted some of its data, or if\nyou want to revert the table to a previous state, you can recover it using\nthe BigQuery [time travel](/bigquery/docs/time-travel) feature. For\nexample, you can run the following command to restore the table to a previous\nstate: \n\n bq cp \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e:\u003cvar translate=\"no\"\u003eDATASET_ID\u003c/var\u003e.reseller_billing_detailed_export_v1@\u003cvar translate=\"no\"\u003eREVERT_TO\u003c/var\u003e \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e:\u003cvar translate=\"no\"\u003eDATASET_ID\u003c/var\u003e.reseller_billing_detailed_export_v1\n\n\u003cvar translate=\"no\"\u003eREVERT_TO\u003c/var\u003e represents the time, in seconds from the Unix\nepoch, that you want to revert to. Note that you can only go back up to 7 days,\nand your data isn't backfilled.\n\nExport is not adding new data\n-----------------------------\n\nIf no new rows are appearing in your export, there are several issues that could\nprevent it from working:\n\n### You recently enabled exports\n\nAfter exports are enabled, it might take up to a day for your usage to appear in\nyour tables. If nothing is there for any longer than that, consider the other\npotential issues here.\n\n### The dataset cannot be accessed by the service account\n\nThe dataset can't be updated if our service account doesn't have access to it.\nYou can update this automatically by clicking update on the [Billing\nExport](https://channelservices.cloud.google.com/billing/billing-export) page in\nthe Partner Sales Console.\n\n### Billing is not enabled for the project\n\nThe export can stop working if billing is not enabled for your project. Follow\n[these instructions](/billing/docs/how-to/modify-project#enable_billing_for_a_project)\nto enable billing. If you're using the [BigQuery\nSandbox](/bigquery/docs/sandbox#upgrade), you must upgrade your account.\n\n### Row or column-level access is enabled on the dataset\n\nIf the dataset has [row-level](/bigquery/docs/row-level-security-intro) or\n[column-level](/bigquery/docs/column-level-security-intro) access control, the\nexport will fail. To re-enable, [delete the row-level access\npolicy](/bigquery/docs/managing-row-level-security#delete_row-level_access_policies)\nand the [column-level access\npolicy](/bigquery/docs/column-level-security#clear_policy).\n\n### You have no parent Cloud Billing accounts\n\nThe export doesn't work if there are no parent Cloud Billing accounts\nto export. If product families don't have associated Cloud Billing\naccounts, they're automatically turned off. To fix this, ensure that there are\nactive Cloud Billing accounts for your selected data source.\n\n### The export has an invalid schema\n\nIt is not supported to modify the\n[schema](/channel/docs/rebilling/export-data-to-bigquery#table_schema)\nof the export table. If you want to add or remove columns, you can create a\n[view](/bigquery/docs/views-intro) or a\n[materialized view](/bigquery/docs/materialized-views-intro), or you can join\nagainst your other tables in your queries. If your table gets in this state, you\nwill need to revert it back to having all the correct columns and nothing else.\n\n### Re-enabling your export\n\nAfter you have found and remedied the issue, go to the\n[Billing Export](https://channelservices.cloud.google.com/billing/billing-export)\npage in the Partner Sales Console. Notice the error on the page saying that\nyour export is disabled.\n\nTo re-enable your export, click **Update**."]]
