My Oracle Support Banner

EAR 9.2: Error Message (15,11) In Direct Journal Payment Accounting Entries If System Account Defaulted Into InterUnit Lines When Analysis Type Is Present (Doc ID 2419767.1)

Last updated on APRIL 10, 2019

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.



An Error Message is being received when a User is trying to save the generated Accounting Entries from a Direct Journal Payment, should it contain an Account flagged as Control Account in the InterUnit balancing rows, along with the Analysis Type ChartField being populated (assuming Project Costing ChartFields are being used).

This functionality used to work fine until the codeline from Record Field PeopleCode PS_PENDING_DST.ACCOUNT.FieldFormula was modified to include not only Speed Key, but also Analysis Type in its validations.


     1.- Log into the FSCM Online Application as User ID VP1
     2.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Overall
     3.- Set the Use Legal Entity for InterUnit = Y
     4.- Navigate to: Banking > Bank Accounts > External Accounts
     5.- For Bank Set ID SHARE, Bank Code USBNK, and Bank Account CHCK, ensure GL Unit is defined as US001
     6.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > General Ledger > General Ledger Definition
     7.- For GL Business Units US001, and US005, go to the Inter/IntraUnit tab, and define InterUnit Template as CORP
     8.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Design ChartFields > Define Values > ChartField Values
     9.- Open under Set ID SHARE, existing Account 213000, and ensure it is flagged as a Control Account
     10.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Inter/Intra Unit > System Transaction Definition
     11.- Open the existing System Transaction = ARDJ
     12.- Go to the System Transaction 2 tab, and in the 'Other Fields To Populate' grid, manually add a new row for the below settings:
               - Field Name = PROJECT_ID
               - Field Source = Inherit From All Lines
     13.- Also, set the Field Source to 'Inherit From All Lines' all Project Costing related ChartFields (BU PC, Project ID, Activity ID, Analysis Type, Category, etc...)
     14.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Inter/Intra Unit > InterUnit Template
     15.- Open the existing Template ID CORP, and for the Transaction Code GENERAL, set the Account value of 213000 on the InterEntity Receivables row
     16.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
     17.- Add a new Deposit ID under Business Unit US001, and for Bank Code USBNK, and Bank Account CHCK. Define one Payment for 500 USD, and flag is a Journal Directly.
     18.- Navigate to: Accounts Receivable > Payments > Direct Journal Payments > Create Accounting Entries
     19.- Open the Deposit ID, and Payment in question, and fill in the Accounting Line row with all needed values, ensuring all Project Costing ChartFields are populated
     20.- Click on the lightning bolt icon, for the system to generate all remaining balancing Accounting Entries
     21.- Confirm that the InterUnit balancing rows have been generated, and that the InterUnit Receivables line gets defaulted Account 213000, and all PC ChartFields
     22.- Save the changes, but the system triggers an Error Message

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.


     " Invalid value -- press the prompt button or hyperlink for a list of valid values (15,11) for field ACCOUNT.
       The value entered in the field does not match one of the allowable values. You can see the allowable values by pressing the Prompt button or hyperlink. "


The Accounting Entries generated for the Direct Journal Payment cannot be saved in the system, and ultimately interfaced into General Ledger to be booked into the Ledger.


The Control Accounts should only be used for system generated Accounting Lines, and InterUnit balancing rows are such lines. The system should allow saving the transaction data.


NOTE: In the  attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.





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

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