This article addresses a potential issue with SAP Business One data coming into Solver.
SAP Business One users have reported experiencing a situation where their integration jobs would result in some missing and/or duplication with the imported data in the Data Warehouse. This issue was only applicable to those with Non-GL integrations with larger data sets.
To correct this, a known determined sort order based on a unique field needs to be added to any data set being imported into Solver. By introducing a sort order into Odata queries, we can remove the risk of any data discrepancies coming into the application.
This will require your company’s SAP admin or someone familiar with creating or modifying Hana Graphical calculation views in SAP HANA Studio. They must add a custom field called ‘Solver_Order_By’ to any view that is used to bring data into Solver. This field should be the primary key or some other unique field or combination of fields to make a unique record for each record in the view.
Please note that this fix will not affect any existing logic put in place for the SolverJournalEntryRows object. SolverJournalEntryRows uses existing fields for the sort order, however, it will use Solver_Order_By if present.