There are three modes in the Compare (ERP) section present in the document header.
Comparison Modes
They are explained from left-to-right in detail below:
Off
The first option is to keep the comparison mode off. This will be the default mode in which the Transformed Data state will be present in.
Compare Mode: Off
State Wrapper
The layout will have document and table data on the bottom section whereas form data in the right section.
Form Data: The form data will be in the form of accordions where they will be grouped accordingly. Each input will have a key name and an input box which is editable.
Form Data
Table Data: The table data will be present in the bottom below the document in collapsed format by default. Users can expand the table data vertically by clicking on the Show Table option present.
Table Data Section
Table Data Open
Similarly, users can also expand the table data horizontally by clicking on the Hide Form option.
Table Data Expanded
If a table cell is empty, then a “-” will be present to represent the empty cell.
Empty Cell
At the end of each table row, we have two icons through which user can perform various actions. When the user clicks on the Pen icon to edit the whole row, the fields of that row becomes editable.
Editable rows in table data
Then we also have the menu icon present at the end of each table row. When clicked, a dropdown will be present where users will be provided with options for following actions:
Menu for each table row
Add Row: Add a row from wherever the user prefers. A side overlay will open providing users with option to add any number of row from wherever they prefer.
Delete Row: Delete the selected table row.
Footer
The footer consists of two actions that user can take regarding the document.
Footer in Compare Mode: Off
Save: Save will allow users to save the contents that were changed in form data and table data.
Execute and Override: This will allow users to execute the transaction and override the TMS data.
Mismatches
This mode is to show all the ERP values which has a mismatch between ERP value and Rippey value.
Compare Mode: Mismatch Only
The layout of the page looks similar to when the compare mode is off. There are only few changes and additional functions added to it which are mentioned in the points below:
All the form and table data input boxes which has a mismatch between the Rippey Value and ERP Value will be highlighted red in colour.
Form Data Mismatch
Table Data Mismatch
The mismatches will be indicated in the Form Data and Table Data headers, along with the workflow step header as well.
Form Data Mismatch count
Table Data Mismatch Alert
Workflow Step Mismatch Alert
The footer will have additional features as well. With the comparison of Rippey extractions with TMS data, the user can see the comparison statistics at the footer. There are two kind of statistics that the user can view based on their preferences.
Mismatch Comparison
This statistics will state the count of Total fields, Total Matches, Total Mismatched and Empty Data. The additional Query button will query the TMS data for any changes in it.
Accruals/Actuals Comparison
This statistics will calculate the Accrual value and Actual value and provide the comparison of it. The additional Query button will query the TMS data for any changes in it.
All data
This mode is to show all the ERP values, including matches and mismatches.
Comparison Mode: All Data
There is not much difference in the layout and functionalities between Mismatch and All Data mode. The only difference is that all the ERP values will be shown in this mode. The mismatches will be in Red colour whereas the Matched values will be grey colour.
Criteria for Comparison Mode
Exception Criteria and support needed when Comparison Screen
Comparison based on datapoints:
Each and every data points will not have comparison values. For example: In table data, costs will have comparison values whereas currency will not have comparison values. These will be configured at the very beginning. This is highly configurable per datapoints to enable or disable it.
Straight through processing:
During comparison, if the total accrual and the total actual matches exactly, then it is called Straight through processing.
Executing the transaction will push our extractions to the ERP system.
Integer and decimal match:
In cases where an integer (for example: 18) is being compared with decimal (for example: 18.00), the comparison should be true and not a mismatch. European format and other data format also should be supported. This will also be configured such that if the raw data of a numerical value is 18.00, then the output shown will 18. In such way, we can show correct comparison in the Comparison screen.
Columns Hide/Unhide Capability
Each column present in the table data can be hidden for comparison modes. This will allow user to have the focus on columns that are indeed of value to them. This will be configured at the very beginning by backend.
Mismatch in Charge Code
Since charge code is the main identifier for the table data, mismatch between them in Rippey data and ERP data should be considered:
Case 1: If mismatch from our side, then the rest of the data points will not be shown ->change in processing screen, push to ERP and pull data
Case 2: if mismatch in ERP (charge code details not added in the ERP) -> send mail to customer about the mismatch (currently we're sending the mail manually informing about the mismatch).