My Oracle Support Banner

EAR 9.2: Express Deposit Component Incorrectly Throwing Error Message (6040,903) for an Item Whose Revenue Accounting Lines Exist in Contracts Module (Doc ID 2794297.1)

Last updated on JULY 26, 2021

Applies to:

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

Symptoms

The Receivables system is throwing Error Message (6040,903) when trying to create a new Express Deposit for an Item that has been originated in Contracts module. This is taking place even if the expected Revenue Lines properly exist in Record PS_CA_ACCTG_LN_PC.

The solution delivered through <Bug 31473166> (AR9.2: UNABLE TO APPLY PAYMENTS FOR ITEMS COMING FROM CONTRACTS), provided an option for companies to decide whether or not Revenue Rows in Contracts/Billing are needed for a Payment to be applied against an Item if Commitment Control is being used. This setting is to be configured at the Receivables Options level (General 2 tab), where a new check-box named 'Notify if Revenue Missing' can be selected.

Having this 'Notify if Revenue Missing' flag selected, the system is only expected to trigger Error Message (6040,903) if no Revenue Lines are found in Record PS_CA_ACCTG_LN_PC for the Invoice/Item at hand, allowing further processing for those transactions whose rows are present. This is working correctly when building a Payment Worksheet manually, but does not seem to be fixed when an Express Deposit is being created online.

REPLICATION STEPS:

    1.- Enable Commitment Control in the FSCM modules of General Ledger, Billing, Receivables, and Project Costing
    2.- Ensure that there are Budgets defined with enough amounts for the Expense and Revenue Ledgers on the ChartField combinations to be used
    3.- At the Receivables Options level, under the used Set ID, ensure that flag 'Notify if Revenue Missing' is selected within General 2 tab
    4.- Create a brand new Project ID, and set it to a Status of Approved and Active
    5.- Define a new Project Activity for the recently created Project ID
    6.- Create a brand new Contract, and add a new Contract Line with Price Type RATE
    7.- At the Contract Line Terms level, link the Contract Line to the Project ID and Project Activity previously created, and define a Rate Set
    8.- From the Contract Line, assign a new Billing Plan with an 'As Incurred' method, and select the Pre-Approved check-box
    9.- From the Contract Line, assign a new Revenue Plan with an 'As Incurred' method
    10.- At the Contract Line Accounting Distribution, define the Distribution Code that will point to the expected ChartField accounting values under the Revenue Forecast section
    11.- Set the new Contract in a Status of ACTIVE
    12.- In Project Costing, add a new ACT (Analysis Type) Transaction Line for the Project ID and Activity ID, with an Amount of 1000 USD, and using the Expenses ChartField accounting values
    13.- Process the newly created Transaction (PC_WRAPPER AE Program)
    14.- At the Project Costing Transaction List level, for the Project ID in question, ensure the new BIL (Analysis Type) Transaction has been generated
    15.- Launch the Process As Incurred Billing program (CA_BI_INTFC) for the Contract ID in question
    16.- Proceed to run the Billing Interface process (BIIF0001 AE Program) for the Interface ID created
    17.- Confirm a new Invoice has been created in Billing module, and set it to a RDY (Ready) status
    18.- Launch the Single Action Invoice PS Job with Commitment Control process for the Invoice at hand (BIJOB03K PSJob)
    19.- Launch the Update Contract/Projects Data BIPCC000 AE Program for the Invoice transaction
    20.- Launch the PC_BI_TO_PC AE Program for the Project ID and its Activity ID
    21.- Go to the Accounts Receivable module, and set the Post Action to Batch Standard on the newly created External Item Group
    22.- Run AR Update process (AR_UPDATE AE Program) with the 'Pending Items' flag selected
    23.- Define the needed Accounting Rules (For PC BU, GL BU, and Analysis Type BLD combination), so that the Revenue line is pointing to the ChartField accounting values used for the Revenue Ledger
    24.- Launch the Process Project Accounting process for the Customer Contract (PSA_ACCTGGL AE Program)
    25.- Query the Record PS_CA_ACCTG_LN_PC for the Customer Contract at hand, and confirm that Field INVOICE is properly populated with the Billing transaction value
    26.- Launch the Journal Generator process (FS_JGEN AE Program) for the Contract Accounting Entries (Accounting Definition CAPCDEFN), with the options of Edit, Budget Check, and Post selected (This would create the new Journal Entry from the Accounting present at Record PS_CA_ACCTG_LN_PC)
    27.- Create manually a brand new Express Deposit, and at the Payments tab, define the Item generated from the Billing Invoice transaction
    28.- Upon saving the Express Deposit component, or trying to select an Action for further processing, the system triggers an Error Message

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

ERROR MESSAGE:

 

Changes

 

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
Changes
Cause
Solution
References


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