Setting up the RRT to Journal Integrations

The RRT to Journal Integrations between Revenue Management and FinancialForce Accounting allow you to create Accounting journals for revenue and cost amounts on committed revenue recognition transactions. There are dependencies between the two integrations, so if you enable one you must also enable the other. For more information about these integrations, see RRT to Journal Integrations Overview.

To set up the RRT to Journal Integrations you must enable the following Feature Console features in the order specified:

  1. Accounting - Journal Integration with Return Data. This feature creates publications and subscriptions required by Revenue Management's RRT to Journal Integration features and adds the Revenue Recognition journal types to Accounting. For details, see Enabling the Journal Integration with Return Data.
  2. Revenue Management - RRT to Journal Integration. This feature creates publications and subscriptions to connect with those created by the Journal Integration with Return Data feature. It also creates fields and permissions used when creating journals for either revenue or cost. Therefore you must enable this feature even if you only intend creating cost journals. For details, see Enabling the RRT to Journal Integration.
  3. Revenue Management - RRT to Journal Integration for Cost. This feature extends the RRT to Journal Integration feature to support cost journals. You must enable this feature even if you do not intend creating cost journals because it is required for validation. For details, see Enabling the RRT to Journal Integration for Cost.

If you are upgrading and your org is configured with a custom solution for creating journals from revenue recognition transactions (such as ClickLink), deactivate your custom solution when the RRT to Journal Integrations are set up.

Note:

Make sure the Override Currency Values on Journal Line field in the Accounting Settings (FF) custom setting is selected. This is required to allow Revenue Management to pass Document Rate and Dual Rate values to the journal line items.

Revenue Recognition Transactions Must Be Grouped by Company

In the FFA subscription to the Journal.Create message type, the mappings for Journal Currency and Period are resolved in relation to Company. Therefore it is imperative that revenue recognition transactions are grouped by a field that identifies a source record's company.

  • If you intend creating revenue recognition transactions using Recognize All, the settings records for your primary source objects must have Grouped By mapped to a field that identifies a source record's company.
  • If you intend creating revenue recognition transactions from the Recognize Revenue page, the RM Grouped Transactions feature in Feature Console must be enabled, and you must group your source data on the Recognize Revenue page by a field that identifies a source record's company.
  • If you intend creating recognition transactions using the Recognize Schedules process, the recognition settings records for your source objects must have Company mapped to a field that identifies a source record's company.

The process to create journals will fail if the correct company cannot be identified on revenue recognition transactions.