My Oracle Support Banner

EAR 9.2: Error Message (9000,229) Being Triggered at Payment Worksheet Accounting Entries Page for Write-Off Transaction (WAO/WAU) if ChartField Inheritance Is Enabled (Doc ID 3017362.1)

Last updated on APRIL 17, 2024

Applies to:

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

Symptoms

At the Receivables Options set up level, the 'Enable Write-Off Override' check-box has been selected, which implies that authorized Users should be able to manually edit the Accounting Entries of Write-Off transactions (Overpayments, and Underpayments), with whatever ChartField Accounting values are input. At the same time, the system has been defined to Always Inherit the Project ChartField in AR/BI ChartField Inheritance Group, as well as the External Bank Account settings for AR Cash, and Control.

However, having manually input the Project Accounting ChartFields of Project Costing Business Unit, Project ID, and Activity ID, for the Write-Off transaction User row on a Payment Worksheet, the system incorrectly throws Error Message (9000,229) stating that Project Costing field is required, after having automatically blanked it out on prior validations.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator User
    2.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Design ChartFields > ChartField inheritance > Define CF Inheritance Options
    3.- Enable Projects to 'Always Inheritance' for the ChartField Inheritance Group AR/BI
    4.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Receivables > Receivables Options
    5.- For the Set ID used, go to the Payment Options tab, and make sure to select the 'Enable Write-Off Override' check-box
    6.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Project Costing > Setup PC BU Options
    7.- For the Business Unit at hand, on the Project Costing Options tab, define the 'Business Unit, Project, Activity' setting to 'Required'
    8.- Navigate to: Banking > Bank Accounts > External Accounts
    9.- For the Bank Account used, go to the External Accounts tab, and for the Account Types needed, define the Projects ChartField as 'Always Inheritance' (Cash-AR, Cntrl-AR)
    10.- Log into the FSCM Online Application as a Receivables User
    11.- Navigate to: Project Costing > Project Definitions > Define Project General Info
    12.- Create a new Project ID under the desired Business Unit, (Example: PC BU US001, and Project ID OSS_PROJECT)
    13.- Navigate to: Project Costing > Activity Definitions > Define Project Activities
    14.- Create a new Activity for the Project ID recently raised
    15.- Navigate to: Accounts Receivable > Pending Items > Online Items > Online Item Group Entry
    16.- Create a new Pending Item Group under the desired Business Unit and Customer ID, and define an Amount of 100 USD
    17.- Go to the Accounting Entries tab, and generate them, to later on manually input the PC Business Unit, Project ID, and Activity ID ChartField values just created
    18.- Save the changes, and confirm that the Project ChartField values from the User Accounting Line have been defaulted as well into the AR line
    19.- Go to the Group Action tab, and place the Post Action to 'Batch Standard'
    20.- Navigate to: Accounts Receivable > Receivables Update > Request Receivables Update
    21.- Launch the AR Update process for the Business Unit desired, and the 'Pending Items' option selected
    22.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
    23.- Create a new Regular Deposit, and Payment transaction for the Business Unit, Customer, and Item previously created, with an Amount of 105 USD (5 USD more than the Item)
    24.- Navigate to: Accounts Receivable > Payments > Apply Payments > Apply Payments Worksheet
    25.- Build a new Payment Worksheet for the Regular Deposit recently created, and match the amount to the outstanding Item, confirming there is an overpayment of 5 USD, which will go into a Write-Off WAO new entry
    26.- Once balanced, click on the Worksheet Action link
    27.- At the Worksheet Action page, click on the Create/Review Entries button
    28.- The system brings the User to the Accounting Entries page, listing the 3 included Entry Type transactions on the Worksheet: PY, AO, and WAO
    29.- Notice that in the Accounting Entries for Entry Type WAO, the User row has editable Accounting ChartFields
    30.- Proceed to define the values on PC Business Unit, Project ID, and Activity ID
    31.- Save the changes
    32.- PROBLEM: The system blanks out Project ID ChartField, and proceeds to throw 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 problem.

ERROR MESSAGE:

    " PC Bus Unit, Project and Activity are Required (9000,229)

      The Business Unit Options for this Projects Business Unit require that Business Unit, Project and Activity are input "


The Write-Off Overpayment transaction created cannot get its overridden Accounting Entries manually entered to be validated by the system, preventing the Payment Worksheet to be further processed, leaving the original Invoice as outstanding, and the payment task not able to get interfaced further into FIN General Ledger module.

If the Write-Off Override feature has been enabled at the Receivables Options level, then a User should be able to manually input the Project ChartField values desired on the Write-Off Item generated by the system at the Payment Worksheet level, (whether that is overpayment, or underpayment), get them validated, and have the ChartField Inheritance default those values into the AR Control and AR Cash rows for both OA and WAO Entry Types.

NOTE: In the images/screenshots/examples mentioned and/or 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.

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.