About Settings Records

Settings records allow you to make your source objects accessible to Revenue Management. You must create a settings record for each source object in your organization. You must be signed in as an administrator to create and maintain settings records.

We recommend that you select and configure your source objects carefully before attempting to configure settings records. See Choosing Your Source Objects for related information.

Note:

Which fields are mandatory varies depending on which value types (Revenue and Cost), settings types (Actual and Forecast), and settings level you choose for a settings record. See "Settings Fields" for more details.

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

Field Mappings

The application needs to know information such as total revenue or total cost, start date and currency details from the source object or objects that you have defined. Your administrator gives the application access to this information by setting up a series of field mappings on the Settings page.

The optional field mapping Fully Recognized and Amortized improves record retrieval performance. If you map this field to an appropriate Boolean field on your source object, the field is set to true when the revenue becomes fully recognized and cost becomes fully amortized. Source records with this Boolean field set to true are ignored by the retrieval process.

Tip:

If you are recognizing revenue against source records, you can use the same custom Boolean field on the source object to put a source record on "Hold". To do this, select the checkbox manually and the record will be ignored by Revenue Management. Remember to clear the checkbox later to release the record from "Hold". (If you are recognizing revenue against revenue schedules, you can use the On Hold field mapping to exclude records from being recognized.)

The optional field mapping Recognized to Date Value is useful for reporting. If you map this field to an appropriate field on your source object, the recognized to date value is stored on the source record. If this mapping exists, the recognized to date value is updated each time transactions are committed. You can use the Cost Amortized to Date Value field in the same way to store cost amortized to date values.

General Ledger Accounts

The application needs to know details about your financial accounting chart of accounts, such as:

• The balance sheet (deferred income or cost) GLA to which the revenue recognition journals are posted.
• The income statement (revenue or cost) GLA to which the revenue recognition journals are posted.

Analysis Details

There are optional field mappings for:

• Salesforce account
• Product
• Company
• Analysis Item 1-4

If you set up these mappings, revenue recognition transaction lines include lookups to the Salesforce account and product, and text values for company and the four analysis values. You can use these fields when reporting on revenue recognition transaction lines. If you are using FinancialForce Accounting with Revenue Management, you might want to use the analysis values to populate the Dimension 1-4 fields on journal line items.

Note:

When setting up mappings for these analysis detail fields you can either enter the API name of a field on the source object, or using lookup relationships you can reference a field on an object linked by a path of up to five lookups. To build a relationship to a parent object, enter the API names of the lookup fields that chain together to reach the information you want. Use a period to separate API names in the chain.

For example, your object hierarchy might be Level 1=Project, Level 2=Milestone, Level 3=Timecard. When creating the settings record for your Timecard object, if you want to derive the Salesforce Account from the related project, the syntax would be:
pse__Milestone__r.pse__Project__r.pse__Account__c

Field Mappings for Deferred Revenue True-Up

If you intend creating deferred revenue true-up transactions to correct discrepancies due to exchange rate fluctuations, you must ensure that the following field mappings are configured:

To True-Up in This Currency	Configure These Field Mappings
Home Currency	Document Currency Home Currency Recognized to Date Recognized to Date (Home) Deferred Revenue to Date Deferred Revenue to Date (Home) True-Up GLA Include in True-Up
Dual Currency	Document Currency Dual Currency Recognized to Date Recognized to Date (Dual) Deferred Revenue to Date Deferred Revenue to Date (Dual) True-Up GLA Include in True-Up

For more information, see Deferred Revenue True-Up.