Enviar
This analytic test combines two separate datasets into one unified dataset. This test is useful when you need to combine two datasets because one dataset holds master data which enriches the insights you can derive from the second transactional dataset. For example, you could use this test to identify vendors with no transactions.
Note that the two datasets being joined to are referred to as dataset A (the primary file) and dataset B (the secondary file).
This test supports the following joins:
-
Inner Join (Retains only the rows that have matches in both datasets A and B)
-
Outer Join (Retains all rows that have matches in either dataset A or B, or in both)
-
Left Outer Join (Retains all rows from dataset A, and the matching rows from B)
-
Right Outer Join (Retains all rows from dataset B, and the matching rows from A)
-
Registros sin coincidencias secundarias
-
Registros sin coincidencias primarias
This analytic test can be used to:
-
Verificar que todas las transacciones de proveedor se han registrado adecuadamente. Un archivo de datos maestros de proveedor garantiza que todos los proveedores estén documentados, lo que reduce el riesgo de que falten transacciones.
-
Confirmación de que la información del proveedor es precisa. Esto ayuda a garantizar que los pagos se realizan a proveedores legítimos y que se reduzcan los errores en la información de proveedor.
-
Garantizar que el archivo de datos maestros de proveedor se mantiene de conformidad con los requisitos reglamentarios y las políticas de la empresa es esencial para los fines de cumplimiento. Los auditores verifican el cumplimiento con las leyes, reglamentos y políticas internas relevantes.
Fields used for analysis
The following fields are required for this analysis:
Core column(s):
-
Primary File:
-
One or more fields that will be used as the match
-
One or more fields to be included in the joined result.
-
-
Secondary File:
-
One or more fields that will be used as the match.
-
One or more fields to be included in the joined result.
-
For the two join fields there must also be an indicator if the join should be performed in an ascending or descending order. The fields from the primary and secondary files must match as they will be used as the key for the join.
Parámetros
One parameter must be set in order to run the test:
Join Type:
-
Inner Join (Retains only the rows that have matches in both datasets A and B)
-
Outer Join (Retains all rows that have matches in either dataset A or B, or in both)
-
Left Outer Join (Retains all rows from dataset A, and the matching rows from B)
-
Right Outer Join (Retains all rows from dataset B, and the matching rows from A)
-
Registros sin coincidencias secundarias
-
Registros sin coincidencias primarias
Test configurations
The only configuration available for this test is Transactions with no supplier account.
Especificación técnica
When you run the Duplicates analytic test, the following steps are performed to run the test:
-
Obtain if this is a final result or an interim result.
-
Obtain the type of join being performed from the following types:
-
Inner Join (Retains only the rows that have matches in both datasets A and B)
-
Outer Join (Retains all rows that have matches in either dataset A or B, or in both)
-
Left Outer Join (Retains all rows from dataset A, and the matching rows from B)
-
Right Outer Join (Retains all rows from dataset B, and the matching rows from A)
-
Registros sin coincidencias secundarias
-
Registros sin coincidencias primarias
-
-
Obtain the primary file:
-
Obtain the matching field(s)
-
Obtain the list of fields that will be included in the result
-
-
Obtain the secondary file:
-
Obtain the matching field(s)
-
Obtain the list of fields that will be included in the result
-
-
Obtain if the matches are in ascending or descending order or a mix.
-
Perform the proper join based on the user selections.
