Consider a typical integration between Oracle ERP and Salesforce. Accounts and Orders need to be in sync all the time for complete visibility.
Typically, the objects are involved are – Account, Product, Order and Order Line Item tables. On a regular basis, few questions emerge:
- Did all the Accounts from ERP app make it to the Salesforce app?
- What is the best way to compare the counts?
- Are all the records between Salesforce and ERP system matching?
- Is referential integrity among accounts, orders, order line items intact in Salesforce?
With ETL Validator, you can easily execute the above tests in no time.
Lets’s say there are 1000 products in the catalog and it is important to ensure that the metadata of this product catalog does not get accidentally modified. How would you do that?
- In ETL Validator, you can baseline a table.
- Run tests on an ongoing basis to ensure that the data accidentally does not get modified.
- If it does, then the platform can send out notifications with the records that do not have data as expected.
Over a period of time, it is important to understand the changes to profiles, roles, access privileges etc in the Salesforce platform so that only the expected changes are going in with each internal release and nothing else is slipping through the cracks.
- Using ETL Validator, take a baseline of the object metadata.
- Compare the same over time.
- If there are differences, ETL Validator sends out notifications & alerts administrators of unexpected changes.
ETL Validator be used to define rules on specific data elements: Example: Define a rule so that the percentage on a rebate is always less than 20% for a product.