Released: 24-May-2023

In addition to all of the new features and changes listed in the Release Notes, this topic contains the issues that were resolved in 2022.R2-SP1.

Inception and Contract Operation

  • Users can now successfully freeze company codes with contracts or activation groups that are missing due to bad data. (Reference: RGE 08)

  • If there are a large number of Profit Centers in Master Data Configuration, performance improvements have been made when the contract and activation group Accounting page is loaded. (Reference: RGM 23)
  • When the switch "Enable Posting Sequence Validation" is enabled on the Posting Settings page, users can now successfully post payment postings when there are previous periods with NA posting status (Reference: RRB 91, EST 70)

Financial Schedules and Lease Events

  • When a lease modification has been performed on a contract that is using IBR values, the application no longer updates the IBR during a subsequent impairment event. (Reference: RAG 28)

Mass Operations

  • When WorkflowLiteConfig is configured in backend configuration to transition master agreements and contracts directly from Define to Active status (skipping Waiting for Approval), users can now successfully run Mass Contract Change batches in Batch Management. (Reference: RBO 58)
  • In the Mass Import Tool contract Excel import template, the cell format of columns in the template have been changed from "General" to the required format (e.g., Number or Text). In addition, users can now view the required cell format by clicking on the column name. (Reference: REL 16)
  • In the Master Data Configuration Flow Code table (that is reserved for future use), two new Document Types have been added for exercised and unexercised cash incentive terms added through lease events. (Reference: RGE 42)
  • When a file is imported via the Mass Import Tool while an SAP sync is running, the import is now prioritized in the queue and can no longer get stuck behind the sync task. If the import takes more than 60 minutes, a timeout has been implemented to cancel the task. In this case, you must re-import the file. (Reference: RGB 56)
  • When master agreements, contracts, or activation groups are exported in the Mass Lease Modification tool and multiple IDs are selected in the bulk object drop-down filter, the drop-down field no longer collapses after each ID is selected. (Reference: RGE 54)
  • When new terms are added through the Mass Lease Modification tool, users are now properly required to always define unique term object IDs in the uploaded Excel file. (Reference: RGO 94)
  • The Payment Date To field on the Inputs page of Mass CPI Change batches in Batch Management is no longer required if the checkbox "Apply Event in First Period" is selected. Note that even though the field was previously mandatory, this field was always ignored when the checkbox was selected. (Reference: RGR 80)
  • When contracts are imported via the Mass Import Tool and the Calculated End Date on the Financial Term tab is empty, the application can now automatically calculate the end date based on the duration and start date for applicable terms. (Reference: RGT 40)
  • If a Close action Workflow Mass Transition batch is run with invalid future End Date, the activation group is no longer closed with the invalid date and a clear error message is now displayed for the failed batch item. (Reference: RMT 32)
  • The Mass Import Tool now properly displays an error during the file validation if tabs are missing in an imported master agreement Excel file. (Reference: RSS 33)
  • In the LT_GLAccount tab of the System Configuration Excel template, the spelling of the column "ProfitCtrEnabled" has been corrected. As a result, data in this column can now be successfully uploaded. (Reference: RTA 11)
  • If a Mass Lease Modification is run and an error is identified during data validation, the application now properly only displays the error message for the specific invalid contract (instead of occasionally displaying the same error for all other valid contracts). (Reference: RTA 43)

Dashboards and Reports

  • When the Consolidated Transaction Report is generated with a contract that has Generate Vendor Invoices selected, there are no longer duplicate clearing posting documents displayed in the report. (Reference: ESR 17)
  • When the Asset Roll Forward Disclosure Report is generated and there is a contract matching the filter criteria that has no revision history (even though an event was previously performed), the report can now be successfully generated. (Reference: ESS 17)
  • The "New ROU Asset" column in the Asset Roll Forward Disclosure Report is now correct when a lease modification event is performed in the first period of the lease. (Reference: ESR 40, ESL 91)
  • If a contract has multiple accounting standards and one does not have Depreciation Area Currency configured in Master Data Configuration (and the other standard has a single depreciation area currency configured), the following columns in the Movement and Closing Balance Reports in Additional Reports are now correct and are no longer empty:
    • Movement Report: "ROU Depreciation - Profit/Loss (Debit)" and "ROU Depreciation - Balance Sheet (Credit)"
    • Closing Balance Report: "ROU - Profit/Loss Depreciation" and "Accumulated Depreciation"

    (Reference: RAA 22)

  • The Consolidated Transaction Reports now properly display the Cost Center from the unit level for all postings (and no longer occasionally display the Cost Center from the contract level). (Reference: RBR 59)
  • When the Consolidated Transaction Reports are generated in CSV format, the currency and amounts for Asset Depreciation postings are now always in the correct columns and are no longer shifted to the left. (Reference: REL 00)
  • When the Activity Analysis by Amount Report in Additional Reports is generated with a start date that coincides with the ROU Start Date of a contract, the "New Lease Addition" column in the Liability section of the report is now correct. (Reference: RET 56)
  • The Consolidated Transaction Reports now properly display the Functional Area from the unit level (instead of the contract level) for Asset Capitalization, Asset Depreciation, and Asset Retirement documents. (Reference: RGE 15)
  • In the Contract Expiration Reports in Additional Reports, the page no longer freezes when a minus sign (-) is entered in the Number of Months or Number of Days filters. (Reference: RGS 70)
  • When a contract with a Last Payment Date that is after the ROU End Date is closed, the Closing Gross Book Value and Closing Net Book Value in the Asset Roll Forward Report in Disclosure Reports are now correct. (Reference: RGT 24)
  • When the Activity Analysis by Amount Report in Additional Reports is generated with a contract that has a Last Payment Date that is after the ROU End Date, the "Ending Principal Lease Liability Balance (Schedule)" column is now correct. (Reference: RSB 88)
  • When a Cash Incentive term is exercised through a lease modification or reassessment, the "Ending ROU Asset Balance (Gross)" column in the Activity Analysis by Amount Report in Additional Reports is now correct and no longer contains duplicate amounts for the incentive term. (Reference: RSB 98, RLR 29)


  • In SAP ECC EhP8 connected systems, if BAPI_ASSET_ACQUISITION_POST or BAPI_ASSET_RETIREMENT_POST returned a warning message during asset postings, the application was displaying an invalid SAP document number in the posting document. As a result, there were also no line items in the document because the application was using the invalid document number to retrieve the line items from SAP. This has now been corrected and the correct document number and line items are used. (Reference: RML 01)


  • When an accrual posting batch is run on a contract that has multiple accounting standards (one of which is classified as ASC 842 operating), the application now properly uses the configuration in the Accounting Determination table. Note that the application was previously using the GL accounts configured for the operating classification for all accounting standards on the lease.

    Warning: If different GL accounts are configured for the different standards in the Accounting Determination table, the application will begin posting accrual batches to these new GL accounts. This may result in remaining balances when existing leases are closed. To work around this issue, modify your configuration to continue using the same GL accounts or contact Nakisa Support for additional options.

    (Reference: RER 19)

Nakisa Finance Suite 2022.R2-SP © 2023



Nakisa Inc. All rights reserved worldwide.