A recent JD Edwards YouTube video walked through how to set up configurable unmasking for bank account numbers. The National Automated Clearing House Association (NACHA) has specified a rule which states that companies with a specified amount of payments must protect bank account numbers. To support compliance to NACHA, EnterpriseOne now has bank account numbers visually masked. However, understanding your need for exceptions to the masking feature, JD Edwards provides you with an option to configure such exceptions. The video below shows how to set that up.
An important item to remember with masking is that EnterpriseOne reports also display the bank account numbers in a masked format, but they cannot have an exception from masking.
When you sign into EnterpriseOne, you’ll first review the UDC00PI to see the list of programs that have the capability to reveal the bank account number on an as-needed basis. In the video’s example, an exception is set for the Bank Accounts by Address program that has, by default, the bank account number obscured. Access the Bank Accounts by Address program, search for the bank accounts, and you will see that all records have the bank account masked.
Access the Data Protection Configuration program and select Add Option to add a record. In the Configuration Record Type field, enter the record type as “1” to configure a program ID-based exception. You can also set up the configuration as “2” to specify a user or a role to have rights to view or update bank account numbers on a specified program. When selecting the record type as “1,” the user or the role ID field automatically updates to “ABALL,” which means all users will get access to the bank account number information based on the exception defined for the program.
For the Program ID, select P0030A from the list of programs available in UDC00PI and click Select. In the View Update field, select “U” for providing update rights on the bank account number. Selecting “V” here will mean providing only view rights on P0030A. Here, it’s important to note that the system gives precedence to the user ID over the role ID for the type of right that you provide. This means that if you give a role ID the right to update the bank account number in a program, but a user in that role just viewing rights, the system allows that user to only view the bank account number in that program. So, if you have update rights for bank account numbers assigned to a role and that role still cannot update with the user ID, you can review the record for that user ID and modify it.
Finally, click the OK button to save the record. This completes the conditional unmasking setup.
Now that you have set up an exception for unmasking bank account numbers in P0030A, let’s review it in the program. Access the Bank Accounts by Address program and click Find to search for the bank accounts. You should now see that all records have the bank account numbers unmasked. To confirm that the system allows an update on the bank account number, select a record and click Select. Type in the new bank account number and then save it. The system doesn’t show any error, so you can see that the system now allows editing of the bank account number for P0030A.
To learn more about masking and configurable unmasking for bank account numbers, view the video below or check out the JD Edwards EnterpriseOne Applications Accounts Payable implementation guide and visit www.learnjde.com.