E1: 74: SEPA Need the Ability to Secure Access to Report Definition (RD) Output and RD Source for SEPA Credit Transfer (R704001) (Doc ID 2939779.1)

Last updated on OCTOBER 22, 2024

Applies to:

Symptoms

We have standard Payment UBEs that are using Report Definitions and produce XML payment files that are supposed to be sent to the bank. Ex: SEPA Credit Transfer (R704001), CGI Payment Format Extractor (R744003), SEPA Direct Debit Extractor (R743005). These contain Bank Account details which should be secured according to industry standards like Payment Card Industry Data Security Standard even for the users that produced the payment files. We implemented recently a feature to secure Bank Account details implemented in Financials: JDE E1: Data Security/Masking for Bank Accounts in EnterpriseOne (Doc ID 2790533.2). But for payments that use Report Definitions there is no way to secure the RD Source and RD output which will contain Bank Account details. Therefore it is necessary to have the ability to secure access to RD Output and RD Source. This arises from necessity to secure IBAN and Bank Account Numbers.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.