What's new in Customer Journeys?

Connect and learn more! ×
How to mask BANK_ACCOUNT_NUM after P2T refresh — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

How to mask BANK_ACCOUNT_NUM after P2T refresh

Received Response


I am attempting to build a custom HDL for masking of the BANK_ACCOUNT_NUM field for use after a P2T refresh in a UAT POD. We have a need to selectively mask PI data fields, so cannot use the available Oracle data masking as that process is an all-or-nothing affair.

Content (required):

The issue is that when attempting to load the ExternalBankAccount HDL that has random values for AccountNumber, we receive the error, "This bank account is used in Payroll. You can't modify the bank account. You can inactive the bank account and create a new bank account." The suggestion to inactivate the bank account and create a new one does not solve the problem of the original bank account numbers still being present in the database. This is likely a foreign key problem with another database table, but I have not been able to find any documentation or other

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!