Creating Settings Records

Settings records must be correctly configured before you use the Revenue Management application. You must be signed in as an administrator to create and maintain settings records. See About Settings Records for more background information.

For information about configuring a settings record for revenue schedule generation, see Additional Setup for Generating Revenue Schedules.

Settings

To create a new settings record for a primary object:

1. Sign into your Salesforce organization as an administrator.
2. Click the Settings tab.
3. Click New.
4. Enter a unique name for this settings record, such as Project Settings.
5. Select "Primary" in the Settings Level field. You must define the setting record for this object first.
6. Enter the API name of the primary object into the Object field.
7. Skip the Parent Settings field. This is not relevant when you are defining primary object settings.
8. Skip the Parent Lookup field. This is not relevant when you are defining primary object settings.
9. From the Value Type field, choose whether this settings record will be used to process revenue values, cost values, or both.
10. Select a settings type of "Actual" if this record will be used by the Recognize Revenue process, or select a settings type of "Forecast" if this record will be used by the Forecast Revenue process.
11. Select the Use in Revenue Contract checkbox if the source object will be used to create performance obligations on revenue contracts. Note that if this checkbox is selected, by default any source object records linked to this settings record will not be included in forecasting and recognizing revenue calculations; they will only be included in revenue contract processing. When this checkbox is selected, you must populate the POLI Source Lookup field with the API name of the field on the performance obligation line item that is a lookup to the source record. (This is explained in Additional Setup for using Multiple-Element Arrangements.)
12. In the Lookups to Source Object section:
    • For a settings type of "Actual", in the Revenue Recognition Txn Line Lookup field enter the API name of the lookup field (to the source object at this settings level) that your administrator has added to the Revenue Recognition Transaction Line object.
    • If you have enabled Use Actual vs Forecast Feature in the custom setting Revenue Management Settings, in the Actual vs Forecast Line Lookup field you must enter the API name of the lookup field (to the source object at this settings level) that your administrator has added to the Actuals vs Forecast Line object.
    • For a settings type of "Forecast", in the Revenue Forecast Transaction Lookup field enter the API name of the lookup field (to the source object at this settings level) that your administrator has added to the Revenue Forecast Transaction object.
    • For a settings type of "Forecast", in the Revenue Forecast Transaction Line Lookup field enter the API name of the lookup field (to the source object at this settings level) that your administrator has added to the Revenue Forecast Transaction Line object.
13. Create the field mappings by entering the API name for each source field in your primary object. You must complete the SSP field if the Use in Revenue Contract checkbox is selected.
14. [Optional] Map the currency fields if you want to use historic exchange rates when recognizing revenue and amortizing cost, so that currency exchange gains and losses do not occur. For more information, see Using Historic Currency Exchange Rates when Recognizing Revenue.
15. For a settings type of "Actual", complete the following analysis GLAs for revenue and costs depending on the selected value types:
    • Enter the API name of the field on the primary object that defines the income statement GLA to which the revenue recognition journals are posted. This GLA must already exist in the chart of accounts of your financial accounting application.

      Alternatively, enter the income statement GLA code as fixed text and then select the Fixed Income Statement checkbox to indicate that this is not an API name.

    • Enter the API name of the field on the primary object that defines the balance sheet GLA to which the revenue recognition journals are posted. This GLA must already exist in the chart of accounts of your financial accounting application.

      Alternatively, you can enter the balance sheet GLA as fixed text as described for the previous field. If you do this, remember to select the Fixed Balance Sheet checkbox to indicate that this is not an API name. This GLA must already exist in the chart of accounts of your financial accounting application.

    • [Optional] If your management accounts are sub-analyzed by a specific component of your chart of accounts, define it in the Cost Center field in the same way as described for the previous two fields.
16. [Optional] Map the deferred revenue true-up fields if you intend creating deferred revenue true-up transactions to correct discrepancies due to exchange rate fluctuations. For more information, see Field Mappings for Deferred Revenue True-Up.
17. Click Save.
18. If the Use in Revenue Contract checkbox is selected, click the Create Mapping button to generate the default field mapping definition to map fields from source records to performance obligation line items.

Creating Settings for Source Objects below the Primary Object

To create a settings record for source objects at a level below primary, repeat the steps described earlier for a primary object, but this time you must make the following alternative choices:

• Setting Name: Enter a unique name.
• Settings Level: Select the level of this source object settings record.
• Object: Enter the API name of the object that acts as the data source at this level. The selected source object must be in a master-detail or lookup relationship with the primary object.
• Parent Lookup: Enter the API name of the lookup field to the related source object.
• Parent Settings: Select the parent settings record (the settings record for the source object one level above this one in the hierarchy).
• Settings Type: Select the relevant settings type (Actual or Forecast). This must be the same as its parent settings record.
• Revenue Forecast Transaction Lookup: Leave blank at levels below "Primary".
• Continue by mapping fields and analysis GLAs as before. The source fields must exist on the selected object. The analysis GLAs must already exist in your finance application's chart of accounts.