The following procedure explains how to mask data across columns for packaged applications in which the relationships are not defined in the data dictionary.
To mask dependent columns for packaged applications:
Go to Data Discovery and Modeling and create a new Application Data Model (ADM) using metadata collection for your packaged application suite.
When metadata collection is complete, edit the newly created ADM.
Manually add a referential relationship:
From the Referential Relationships tab, open the Actions menu, then select Add Referential Relationship.
The Add Referential Relationship pop-up window appears.
Select the requisite Parent Key and Dependent Key information.
In the Columns Name list, select a dependent key column to associate with a parent key column.
Click OK to add the referential relationship to the ADM.
The new dependent column now appears in the referential relationships list.
Perform sensitive column discovery.
When sensitive column discovery is complete, review the columns found by the discovery job and mark them sensitive or not sensitive as needed.
When marked as sensitive, any discovery sensitive column also marks its parent and the other child columns of the parent as sensitive. Consequently, it is advisable to first create the ADM with all relationships. ADM by default, or after running drivers, may not contain denormalized relationships. You need to manually add these.
For more information about sensitive column discovery, see step 6.
Go to Data Masking and create a new masking definition.
Select the newly created ADM and click Add, then Search to view this ADM's sensitive columns.
Select columns based on your search results, then import formats for the selected columns.
Enterprise Manager displays formats that conform to the privacy attributes.
Select the format and generate the script.
Execute the masking script.
Enterprise Manager executes the generated script on the target database and masks all of your specified columns.