Duplicate Consistency Checks

The Duplicate Consistency Checks allows you to verify documents in SAP in the following ways:

The Duplicate Postings Check detects and reverses duplicate postings that were posted to SAP by the Nakisa SAP Posting Bot. Duplicate postings may occur if a transaction was successfully posted to SAP, however the SAP document number was not successfully sent back to Nakisa (e.g., due to connection issues). In this case, the Nakisa SAP Posting Bot may register the transaction as failed and retry the posting in the next posting run (resulting in duplicate postings in SAP).
The Consistency Check finds any externally posted transactions that do not have a valid posting document in SAP, and resets them to the correct posting status. Typically when the Nakisa SAP Posting Bot posts a transaction to SAP, an SAP document number is generated and sent back to Nakisa. The Nakisa SAP Posting Bot then records the successful posting and updates the posting status in Nakisa General Ledger. Occasionally, although a document number was generated in SAP, it is not saved and is later invalidated in SAP and the posting rolled back. This can result in a consistency issue because the application has already recorded a successful external posting (even though there is no corresponding posting in SAP). The tool corrects this by resetting the status to "Failed Posting".

Note: The checks only work if T-codes are enabled in SAP and set to NAKISA, so that the tool can identify all of the documents triggered by Nakisa. You can test the SAP connection string with T-codes enabled on the ERP Systems page.

To use the tool, you create a duplicate posting or consistency check job in the left-panel to identify the issues. You must then run the resolution task in the right-panel to reverse duplicate documents in SAP or reset the document statuses in Nakisa General Ledger if there was a consistency issue.

For more information about internal GL postings, refer to the Nakisa Lease Administration User and Admin Guide.

Note that Duplicate Consistency Checks can be scheduled to run daily at midnight (UTC) per ERP system on the ERP Systems page.

To find duplicate postings in SAP or consistency issues:

Click Main Menu > SAP Posting Bot > Duplicate Consistency Check Job.
In the Find Duplicate Postings / Consistency Issues panel on the left, click to open the Duplicate Consistency Check Job window.
Select a System from the drop down menu.
From the Company Filter drop down menu, select whether you would like to check all configured companies under the chosen System, or only select certain companies from a list.
- If "List" is selected, choose one or more companies from the Companies drop down menu.
Enter the Fiscal Period and Fiscal Year of the documents to check.
In Type, select if you are checking for "Duplicate Postings" or if you want to run a "Consistency Check".
Click Submit. Once a job is added, its status updates to "Processing". Click to refresh the jobs to see the updated status. The status changes to "Finished" or "Failed" when the job has finished running.
Click in the Reports column to view a report of how many duplicate or inconsistent items were detected. Note the following:
- Click an ID under "Internal Document Number" to open the transaction in the Ledger Transactions.
- The "Found by Detection ID" column indicates which other Duplicate and Consistency Check job also detected the same problematic document.

Note: If there is a service interruption that prevents the completion of the job while it is running, the job status changes to "Interrupted". The application will attempt to recover the job as soon as possible. If the job is recovered, it will resume from where it was interrupted. If the job cannot be recovered within the time limit specified in Financial Organization Structure, the status remains "Interrupted" and you must run the job again.

To resolve duplicate postings or consistency issues:

Once a job has been run to identify the issues, click in the Resolve Duplicate Postings / Consistency Issues in the panel on the right.
Select the ERP System. All of the issues found for the system will be displayed, even if they were detected using multiple jobs.
The Consistency Check Report tab opens by default, and lists the inconsistencies found. Select the documents that should be reversed in Nakisa General Ledger.
Click the Duplicate Postings Report tab. Each row displays a document in Nakisa General Ledger with more than one equivalent document in SAP.
1. You can use the default Posting Date and Reversal Reason if they were defined for the selected SAP system, or you can enter them in the Duplicate Consistency Check Default Posting Date and Reversal Reason fields.
2. Click on the row to expand it to see the duplicate SAP document numbers. Note that the External Doc No (Nakisa) in the main row is the SAP document number that is tied to the Internal Doc No in Nakisa General Ledger. The Duplicate Document Number in SAP are the extra documents in SAP that are tied to the same internal document.
3. Select which SAP document(s) to reverse.
Click Process. Once the task is added, its status updates to "Processing". Click to refresh the tasks to see the updated status. The status changes to "Finished" or "Failed" when the task has finished running.
Click in the Reports column to view a report of how the resolved items. The Found By Detection ID column indicates the Detection IDs from the left-panel that had originally found the issue. Note that you can click the ID under "Internal Doc No (Nakisa)" to open the transaction on the Ledger Transactions page.

To manage duplicate consistency jobs:

Click to copy the job. Note that you have the option of modifying inputs before starting the new job.

See also: