Slave No Master
In this function, we will demonstrate how CABAM can be used to identify scenarios where you have transactional data without the corresponding master data or to find slave data records that are redundant and need to be flagged as inactive or deleted. This is to avoid reports being distorted, possibly leading to an incorrect decision from management.
For example, you may have references to customers in a collection of transactional data and you may find that some of the customer ID are do not exist in the customer master data. In short, you may find a transaction that is not linked to a valid Customer. CABAM will flag this as an anomaly and alert you.