JDE E1: Installing Data Security/Masking for Bank Accounts Causes Masking in Custom Applications and UBEs
(Doc ID 2856925.1)
Last updated on DECEMBER 10, 2024
Applies to:
JD Edwards EnterpriseOne General Ledger - Version 9.2 and laterJD Edwards EnterpriseOne Sales Order Management - Version 9.2 and later
JD Edwards EnterpriseOne US Payroll - Version 9.2 and later
JD Edwards EnterpriseOne Accounts Payable - Version 9.2 and later
JD Edwards EnterpriseOne Accounts Receivable - Version 9.2 and later
Information in this document applies to any platform.
Symptoms
After applying bugs listed in JDE E1: Data Security/Masking for Bank Accounts in EnterpriseOne (Doc ID 2790533.2) custom applications and UBE's also have masking applied.
The following Data Dictionary items are affected:
- Financials:
- Customer Bank Account Number (CBNK)
- International Bank Account Number (IBAN)
- Credit Card Account Number (CRCI)
- Electronic Bank Account Number (BAN)
- HCM and Payroll:
- Bank Account Number (BKAN)
- Financial Organizational Account Number (FOA#), and FOA#2 through FOA#8
- Localization:
- Customer Bank Account Number (C75CBNK)
- Debtor Identification (74DBI)
- Bank Account Number (BNK)
- Sales Order Management:
- Account Number – Credit/Bank (CACT)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |