Skip to main content

Zuora RevPro 36.003.00 Release Notes


Zuora RevPro 36.003.00 Release Notes

This article provides a summary of new features, enhancements, and resolved issues in the Zuora RevPro version 36.003.00.

New Features and Enhancements

The following new features and enhancements are available in this release.

Enhancement to GL and MJE Interface Mapping

Previously, when the transfer accounting outbound file is generated, the format of the file does not follow the sequence of how the GL or MJE Interface Mapping is defined. It is not convenient for you to change the sequence of the fields in the outbound file. You have to re-create the file to match with the sequence. Besides, the Interface Field Name values are used directly in the outbound file as field names. You cannot customize the field names that are displayed in the outbound file.

From this release, when you click Setups > Application > Interface Setup to define the GL or MJE mapping, two columns are added for you to customize the format of the outbound file:

  • The Display Sequence column is added as the first column. You can adjust the field sequence in the outbound file by specifying different numbers in the Display Sequence column. If the sequence is not defined for the GL or MJE mapping, the fields in the outbound file will be sorted by their IDs in ascending order.

  • The Display Label column is added. Values specified in the Display Label column are used for field names in the outbound file.

This enhancement applies to both the old UI and the new UI.

Selectable Currency for RC Approval Rules

Previously, when you set an approval rule for revenue contracts, the currency of the approval criteria always defaults to transaction currency.

From this release, if you select an amount-based field in an approval rule as criteria, you can also specify the currency for this field with a drop-down list.

If the approval rule is to be applied to aggregated values, you can set its currency to be lowest common currency or reporting currency. If the approval rule is to be applied to transaction lines, you can set its currency to be transaction currency, functional currency, or reporting currency. The total amount of the revenue contract is determined based on your selection and the related exchange rates.

This enhancement applies to the new UI only.

Enhancement to Configurable Waterfall Templates

In version 36.002.00, configurable waterfall templates are added to provide more flexibilities for you to define the format of waterfall data.

From this release, when you select Periods/Quarters/Years as the waterfall format, a required field named No. Of Periods is added for you to specify the total number of periods (prior and future) to be included in the waterfall data.

Validation is also added to ensure that the total number of prior periods, future periods, prior quarters, and future quarters does not exceed the maximum limit 40, which is defined by the WX_TMPL_MAX_PROD profile.

The system level value of the WX_TMPL_MAX_PROD profile is 40, which cannot be changed from this release. If you did not change the seeded value in the previous version, you must run a data fix to use the existing template. If you changed the seeded value, you must edit the template based on your requirement.

This enhancement applies to the new UI only.

Currency of MJE Lines Must Align with Currency of RC Lines

From this release, when the MJE is linked to a revenue contract, the validation process is triggered to ensure that the currency of the MJE lines is aligned with the transaction currency of the RC lines.

For example, if the transaction currency of the RC lines is USD and the functional currency is EUR, then currency of the MJE line that is linked to this RC should be USD and the currency of the MJE head is EUR. The MJE cannot be approved if the currency is different.

Support to Run Waterfall Report for All Organizations

Since version 3.5, it has been impossible to run waterfall reports for your organizations all at once no matter whether they have the same open period.

From this release, when you run waterfall reports, if all the organizations in your company have the same current open period, you can select ALL for the Org Name field to run the reports for them all at once. However, if one or more organizations have a different open period, ALL is not listed as an option for the Org Name field. You have to run the waterfall reports for the organizations one by one.

This enhancement applies to both the old UI and the new UI.

Enhancement to Notification of Accounting Changes That Require Summarization

From version 36.002.00, if there are accounting changes that have not been summarized, an orange bell icon is displayed next to the current accounting period in the header line after you log in to RevPro.

From version 36.003.00, in addition to the orange bell, a window named Summarization Snapshot Details window will be displayed before launching the report.

The revenue contracts that have accounting changes and require summarization are all listed in this window. The Summarization Snapshot Details window works only as a warning message.

Remember that the Summarization Snapshot Details window is displayed only for the reports that require summarization.

This enhancement applies to the new UI only.

Long-term Revenue & Short-term Revenue Available in RC Rollforward Report

Prior to this release, there is no segregation of long-term liability and short-term liability in the RC Rollforward Report. From this release, three columns are added to show the long-term contract liability in functional, transactional and reporting currency. The prerequisite to populate these values is that you must run the long-term and short-term reclassification program.

More Fields Added to RC Workbench Timeline Report

Prior to this release, only a few fields are available for display in the RC Workbench Timeline Report. From this release, all the fields of RC_Line are added to this report. Part of the added fields are listed below:

  • Carves Adjustment

  • Customer Number

  • End User

  • Ext Sell Price

  • Ext SSP Price

  • Line Creation Period

  • Line Item Num

  • Line Type

  • Order Type

  • Product Line

Issues Resolved in This Release

The following major problems or issues are fixed in this release. Refer to the attached CSV file to get a list of all issues that have been resolved in this release.

  • When cost events with the revenue segment are collected and processed by RevPro, wrong accounting entries are created. 
  • For prospective allocation, the allocatable amount and allocated amount are incorrectly calculated. 
  • When a report is downloaded, headers in the downloaded report are not populated correctly. 
  • A new RC is created containing the SO line with the same DOC Line ID, which results in the same SO line appearing in different RCs. 
  • The batch collection process for holds is stuck in staging with Oracle internal errors. 
  • The scheduled job group skips the duplicated children programs and comes to the end unexpectedly. 
  • When allocations are performed in reporting currency, the revenue summary in the Workbench is displayed in functional currency instead of reporting currency. 
  • No data is returned for the Line Staging Report. 
  • The Posted Percent value is incorrectly calculated when partial CM-R (credit memo for return) is collected. 
  • When multiple custom codes for the CUSTOM_UI_UPLOAD object are enabled, the custom codes are not triggered. 
  • The Posted Percent value is calculated when prospective allocation is triggered for a revenue contract. 
  • During bundle collection, allocation schedules and accounting entries are not created for the $0 children lines. 
  • In the old UI, the Overview tab in the Workbench is empty without any revenue contract summary. 
  • In the old UI, when you run the waterfall reports with the Enable Totals switch toggled to Yes, the line of total amounts is displayed on the top of the report, which should be at the bottom. 
  • When the unreleased sales order lines are canceled during the contract revision timeline, the carves amount and the fair value amount are updated as expected. 
  • Multiple health check issues occur when CM-R (credit memo for return) contract modifications happen. 
  • Impairment schedules are not created for the RORD lines as expected. 
  • It takes a long time to export data from the API BI view due to performance issues. 
  • The Unbilled Flag value is not updated according to the Unbilled Flag value that is specified for the contract modification lines.