E1: 09: Enhancement Request To Prevent JAS_MSG317 When Entering Accounts With Security (P0901)
(Doc ID 2766473.1)
Last updated on JUNE 02, 2021
Applies to:JD Edwards EnterpriseOne General Ledger - Version 9.1 and later
Information in this document applies to any platform.
When entering a new account in Accounts (P0901), the system will use the Next Number defined in Next Numbers: 09 > Next Account ID.
Before trying to enter the account, P0901 will verify if an account already exists for this Next Number and, if it does, it will search for a new Next Number that does not already exist.
However, if the Next Number is setup incorrectly (to an existing account ID) and the user has Row Security for the Company for which that account has been entered, P0901 will not be able to find that account and will assume the Next Number is correct and therefore try to insert a new account using that Next Number. This will result in the following error being displayed by the program: JAS_MSG317: Duplicate key not allowed. Please correct the duplicate key field.
The system should be able to find the Next Number is used even if the Security setup prevents the user from viewing that account.
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