Resolved Issues in 37.018.00.00 and later
Not all resolved issues are included on the page below when the release notes are first published. This page will be continuously updated bi-weekly for the subsequent sandbox releases until the next quarterly release.
Issues resolved in 37.018.00.00
| Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
| ZR-36393 | Reporting | RCRF report generated many zero records | Earlier, the RCRF report included many zero records since it did not limit the decimals in the amount fields. This issue is now fixed. The system will perform the zero check after reducing the Amount field's decimals to two. This change will will exclude most of the zero records from the report output. | |
| ZR-37543 | CPD | Revenue activity in CPD does not include Contract Impairment | The impairment activity was not considered in the CPD’s Revenue Report table under the Accounting Analysis tab, which caused a mismatch between the reports. This issue is now fixed. | |
| ZR-37378 | CPD | The period-close task does not refresh when switching organizations for Multi-org customers | Previously, the CPD’s Period Close tasks tab did not refresh when switching organizations using the ORG dropdown in CPD. This issue is now fixed. | |
| ZR-37257 | CPD | An issue with the Data Readiness exception | The export of the Data readiness details from the CPD failed due to a numeric data type size limit. This issue is now fixed by enhancing the data type with a larger size limit. | |
| ZR-35564 | 469668 | Data Collection |
Differences in data processing for sales orders in different sandbox environments |
The system caused a difference in data processing for sales orders in different sandbox environments because it did not use the order by clause while inserting the data into the staging table from the customized UI table. This issue is now fixed by making code changes to load the data in an order. |
Issues resolved in 37.018.01.00
| Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
| ZR-37749 | 486650 | Allocation | An issue with the Allocation treatment flag | Earlier, when you performed mass action to update the CV flag in the initial period, the Allocation treatment flag was disabled. This issue is now fixed by allowing the Allocation treatment flag to change only during revision period. |
| ZR-37623 | 486119 | Allocation | Journal entries out of balance | While switching allocation, the system did not reverse the intercompany entries for the lines deferred causing out-of-balance journal entries. This issue is now fixed by reversing the intercompany entries when switching allocation. |
| ZR-37802 | 487075 | Defer revenue contracts | Exceptions when performing defer revenue contracts | When you try to defer a revenue contract in a multi-org instance, all the Org IDs were concatenated from the UI, causing exceptions. This issue is now fixed. The system will only defer the applicable revenue contract by configuring the relevant Org ID. |
| ZR-37945 | Reporting | Issue with Accounting Detail Report | The Accounting Detail Report had an error due to including the Schedule Type Description field in the user-defined layout. This issue is now fixed. | |
| ZR-37721 | Reporting | The Accounting Report does not include the MJE Period and MJE Reversal period name | Earlier, the accounting report displayed only the period ID. In this release, the MJE Period and MJE Reversal period names are included (instead of the Period name) in the report. | |
| ZR-35341 | Contract Modification | The system does not adjust the waterfall when the sales order is collected with a decrease in term |
When the system collects updated sales orders in the revision period for lines with CV Eligible Flag = N, the system did not defer/recognize the term change for contractual prospective users when retrospective or prospective treatment is triggered for the same line. This issue is now fixed. The system will handle the term change for update SO collected for lines with CV Eligible Flag = N to participate in the defer/recognize process.
|
Issues resolved in 37.017.00.00
See Resolved Issues in 37.017.00.00 and Later to get a complete list of all issues resolved in that release.