Known Limitations in Nakisa General Ledger

The following table lists the known limitations for Nakisa General Ledger (including Nakisa SAP Posting Bot) that may be considered in future major and minor releases. (Note that patch releases deliver bug fixes only, and are not considered to be minor releases.)

Reference Number	Description
BO 08	By default, Nakisa SAP Posting Bot posts to New General Ledger in SAP, and does not have specific configuration to support postings to the Classic General Ledger. As a workaround, in the Configuration > Master Data > ERP > Company table in Financial Organization Structure, go to the General Ledger Account table in the Relations section. Configure all GL accounts (Balance Sheet) with Open Item Management selected. When the Nakisa SAP Posting Bot runs, it will not send the Accounting Principle in BAPI_ACC_DOCUMENT_POST.
GL-158	It is possible to generate an empty Consolidated Transaction Report if an invalid Contract ID is entered into the job filter. In this scenario, users should verify that they are using a valid ID and rerun the job.

Reference Number

Description

BO 08

By default, Nakisa SAP Posting Bot posts to New General Ledger in SAP, and does not have specific configuration to support postings to the Classic General Ledger.

As a workaround, in the Configuration > Master Data > ERP > Company table in Financial Organization Structure, go to the General Ledger Account table in the Relations section. Configure all GL accounts (Balance Sheet) with Open Item Management selected. When the Nakisa SAP Posting Bot runs, it will not send the Accounting Principle in BAPI_ACC_DOCUMENT_POST.

GL-158

It is possible to generate an empty Consolidated Transaction Report if an invalid Contract ID is entered into the job filter. In this scenario, users should verify that they are using a valid ID and rerun the job.