Using Financial Analytics Dashboards

The Billing Contracts dataset is added to your Financial Management Analytics dataflow when your app is created. The dataflow combines data derived from Billing Central with data derived from Accounting, and includes contracts, contract line items and related opportunities. It does not include billing documents. For more information on the objects used to create the Billing Contracts dataflow, see Billing Contracts Dataset Output Fields.

From Spring 2020, you can create the Billing Contracts dataset without first installing and configuring the Opportunity to Contract Integration.

However, we recommend that you do not use the Subscription Bookings dashboard without first installing and configuring the Opportunity to Contract Integration. If you have not installed and configured the integration, then the Billing Central default configuration is used. This might result in incorrect data displayed in your dashboard.

Warning:

The Billing Contracts dataset relies on the linkage created by the composite key between fields on the Contract Line Item and Opportunity Line Item objects in Billing Central. Edits made to the fields used by the composite key on one of these objects must be replicated on the other. For example, if you edit fields used by the composite key on the Contract Line Item object, then you must manually replicate these edits on the Opportunity Line Item object. If edits to fields are not matched, then the composite key cannot link these fields and incorrect data may be displayed in your dashboard.

Billing Central uses the following list action values created by the Opportunity to Contract Integration to trigger the creation of a contract from an opportunity:

• New Contract Action Value
• Renew Action Value
• Upsell Action Value
• Replace Action Value

The Billing Contracts dataset uses all of these action values when calculating the KPIs displayed in the Subscription Bookings dashboard. If you do not use all of these default action values then your data may be displayed incorrectly.

Contracts with a status of "Draft" and of type "Change Request" and their contract line items are filtered from the Billing Contracts dataset. Superseded contracts are included in the Billing Contracts dataset, but are not displayed in the Subscription Bookings dashboard.

The dataflow builds upon existing Billing Central functionality by creating relationships between contract line items and the contract line items that precede and follow them. By creating these relationships, the resulting dataset enables you to view the increase or decrease in monthly recurring revenue (MRR) of individual contract line items and perform the calculations required to create the KPIs used in the Subscription Bookings dashboard.

Composite Keys

In order to create these relationships, the Financial Management Analytics dataflow uses composite keys.

Note:

These keys are used within the dataflow, and are not visible in the Billing Contracts dataset after your app is created.

These composite keys perform the following functions:

• Links a contract line item to the previous contract line item. This composite key matches the following fields: Previous Contract + Product + Billing Type.
• Links a contract line item to the following contract line item. This composite key matches the following combination of fields: Next Contract + Product + Billing Type.
• Links opportunity line items to contract line items through opportunities and contracts. This composite key matches the following combination of fields: Contract ID + Product + Billing Type + Start Date + Quantity.

If the Billing Type field is not populated on the opportunity line item, then the value specified on the Billing Type field on the product is used.

If the Contract Start Date field is not populated on the opportunity line item, then the value specified on the Contract Line Item Start Date field on the parent opportunity is used.

If an upgraded contract with two or more contract lines for the same product is renewed, the contract line with the higher MRR value is calculated as "Renewed" and mapped to the next contract line.

Upgraded Contracts

The value of all contract lines with a lower MRR value that precede this newly-mapped contract line are combined with the highest-MRR value contract line using the Total Previous Monthly Recurring Revenue field. This enables a total MRR value to be calculated if multiple contract lines for identical products exist on a contract. The values of these contract lines are then combined into a single line and stored on the renewal contract.

The following flow chart details this process:

The Billing Contracts dataset filters out data derived from any Accounting companies your assigned permission set has not been granted access to. For more information, see the Accounting Help.

Access to Company Data

Access to company data held in the Billing Contracts dataset is managed by the dataset's security predicate settings.

Contract line items are filtered from the Billing Contracts dataset if a user does not have access to a Accounting company specified on the contract line item.

Contract line items are not filtered from the Billing Contracts dataflow if the following conditions apply:

• There is no company specified on the contract line items contained within your Billing Central data.
• The contract line items contained within your Billing Central data specify a Foundations company that has not been integrated with Accounting.

To remove the security predicate on the Billing Contracts dataset, using the following steps:

1. Navigate to the Analytics Studio tab and click Datasets.
2. Select the Billing Contracts dataset, and select Edit from the drop-down list.
3. Delete the value displayed in the Security Predicate field.

The Billing Documents dataset is added to your Financial Management Analytics Analytics dataflow when your app is created. The dataset combines data derived from Billing Central with data derived from Accounting. It does not include contracts, contract line items and related opportunities. For more information on the objects used to create the Billing Documents dataset, see Billing Documents Fields.

To create the Billing Documents dataset, you must install and configure Billing Central in your org. For more information, see the Billing Central Help.

Access to Company Data

Access to company data held in the Billing Documents dataset is managed by the dataset's security predicate settings.

Contract line items are filtered from the Billing Documents dataset if a user does not have access to a Accounting company specified on the contract line item.

Contract line items are not filtered from the Billing Documents dataset if the following conditions apply:

• There is no company specified on the billing documents contained within your data.
• The billing documents contained within your data specify a Foundations company that has not been integrated with Accounting.

To remove the security predicate on the Billing Documents dataset, using the following steps:

1. Navigate to the Analytics Studio tab and click Datasets.
2. Select the Billing Documents dataset, and select Edit from the drop-down list.
3. Delete the value displayed in the Security Predicate field.

The Financial Balances dataset is equivalent to the Reporting Balances object in Accounting. The dataset includes fields from the Reporting Balances object such as Reporting Balance Type as well as additional fields that relate to a transaction. The Financial Balances dataset is not a copy of the Reporting Balances object. The transactions within the Transaction Line object are extracted from Accounting and are then aggregated within Analytics to create the balance equivalent.

As well as the standard fields available in the Reporting Balances object, the Financial Balances dataset includes other values which have been generated based on the transactions you have posted. The Financial Balances dataset includes summaries and additional transaction information at a summarized level. For instance, Transaction Name, Transaction Line Name, Transaction Document Number, and Transaction Document Description. These fields enable you to see transactional information without needing to drill into sources, such as Accounting.

Some of the members within the dataset contain the suffix (s). The (s) indicates that the value sign has been transformed in some way. For example, where the (s) suffixes a value, it indicates that the signage of that value has been reversed. For example, when you design an income statement, rather than showing your sales accounts as negatives, you can use the Home (s) field to reverse all of your sign values so that values stored as negative appear positive and vice versa. Similarly, (s) at the end of the name of a general ledger account indicates that the name has been trimmed.

Other examples of transformed values are the Year and Period values. These values have been transformed into numbers so that you can do ‘between’, ‘greater than’, and ‘less than’ calculations. For all transformed fields, see Transformed Fields.

In addition to the standard value based measure fields, there are fields for financial years and periods including the Financial Period, Financial Year, and the Financial Year and Period. These fields are typically held only as alphanumeric members within the dataset, allowing you to include them as 'group by' members only. However, by additionally cloning and transforming these members into numbers within the dataflow, they also appear in the Measures section of the lens and you can perform 'greater than' or 'between' calculations.

The Financial Balances dataset also includes the option for you to add your own custom code so that you can modify the order in which your data appears. For example, if the Trial Balance 1 picklist order is required for the report and it is not alphanumeric. Contact your implementation consultant or Customer Support for more information.

For information about which fields are included in the Financial Balances dataset, see Financial Balances Fields.

The Financial Transactions dataset stores fields associated with the Transaction and Transaction Line objects in Accounting, as well as some balance data from the Reporting Balance object, and ancillary objects such as Global Ledger Account, Periods, and Account. For information about which fields are included in the Financial Transactions dataset, see Financial Transactions Fields.

The Financial Periods dataset stores ancillary fields associated with a Accounting period. The dataset includes fields from the Period object in Accounting. For more information about which fields are included in the Financial Periods dataset, see Financial Periods Fields.

The Financial Matching dataset stores the matching history for all transactions that have been cash matched within Accounting. For more information, see the matching objects in Accounting.

The Financial Accounts dataset stores ancillary fields associated with Salesforce accounts. The dataset includes fields from the Accounts object in Salesforce. For more information, see the Accounts object.

The Recognition Transactions dataset is added to your Financial Management Analytics dataflow when your app is created. The dataset contains data derived from Revenue Management. For more information on the objects used to create the Recognition Transactions dataset, see Recognition Transactions Flow Input Fields.

To create the Recognition Transactions dataset, you must install and configure the Spring 2020 version of Revenue Management in your org. For more information, see the Revenue Management Help.

Access to Company Data

Access to company data held in the Recognition Transactions dataset is managed by the dataset's security predicate settings.

Revenue Management transaction line items are filtered from the Recognition Transactions dataset if a user does not have access to a Accounting company specified on the Revenue Management transaction line item.

Revenue Management transaction line items are not filtered from the Recognition Transactions dataset if there is no company specified on the Revenue Management transaction line items contained within your data.

To remove the security predicate on the Recognition Transactions dataset, using the following steps:

1. Navigate to the Analytics Studio tab and click Datasets.
2. Select the Recognition Transactions dataset, and select Edit from the drop-down list.
3. Delete the value displayed in the Security Predicate field.

The Supply Chain Management Core dataset is added to your Financial Management Analytics dataflow when your app is created. The dataset contains data derived from Supply Chain Management. For more information on the objects and fields used to create the Supply Chain Management Core dataset, see Supply Chain Management Core Fields.

Notes:

• To create the Supply Chain Management Core dataset, your version of Supply Chain Management must be Spring 2021 or later. For more information, see the Supply Chain Management Help.
• To use any analytics item that displays data from the Supply Chain Management Core dataset you must have the Use Business Analytics for SCM permission set assigned in SCM.

If your org is configured for multiple currencies, the Currencies dataset is also available in your Financial Analytics app. The dataset contains the currencies configured in your org and the relevant exchange rates. For more information, see Currencies Dataset Output Fields (Financial Analytics).