My Oracle Support Banner

EGL9.2:Updates to Project Chartfield in Allocation Step Pool is Validating Older Effective Dated Steps Resulting to Warning Message: 'Invalid PROJECT_ID value xxxxxxxxxxxxxxxx specified in the Pool Fields. (5060,60).' (Doc ID 2853511.1)

Last updated on MARCH 07, 2022

Applies to:

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

Symptoms

Issue:

Updates to Project chartfield in Allocation Step Pool is validating older effective dated steps.

When saving updates to a Project pool in an Allocation Step, the system is validating Projects in the older effective dated steps and preventing user from saving the changes to the current effective dated Allocation Step.

 For example: User needs to make changes to current effective dated Allocation Step, Project 1 is inactive and it does not exist in current effective date for the step.  Project 1 does exist in a previous effective date.
 When they make changes to the current effective dated step, on save, they would get an error message -- 'Invalid Project_id value specified in the pool fields'.
 The system does not allow user to save the changes and they have to go to the older effective dates and activate the project in order to save.

Error/Warning Message:


Steps to replicate:

1.  Navigate to Project Costing > Project Definitions > Define Project General Information and inactivate a Project:

    - Select Project 000000000000164.
    - Click Project Status link.
    - Add a new effective dated row.
    - Use Effective Date = 01/01/2020 with Status from A to C.  Then, Save.
    * Note now that Project 000000000000164 is Inactive.

2.  Open an Allocation Step (ex:  PC_TEST)

     Effective Date = 01/01/1900

     Note that in Pool tab, Pool Fields have the following:
        Analysis Type
        Billing Distribution Status
        Project
        Source Type

     For Project, it is set with Range of Values (Excluded Specified Values):

       000000000000164 (this is inactive)
       000000000000168
       000000000000169

3.  Click ‘+’ to add a new effective dated row.

     Effective Date = 01/01/2021
     Then, save.

     Note that all values added to the new effective date.

4.  Under the Pools tab, see Pool Field ‘Project’.

     Delete of the row by clicking ‘-‘, which is the inactive value.  Click OK on the deletion confirmation message.

5.  The row gets removed from display.  Click Save.  Click OK on warning message below twice.

     'Warning -- "Selected Detail Values" should be used for equal From /To Values for Pool Field PROJECT_ID. (5060,10)'

6.  Then, get message below:

     'Invalid PROJECT_ID value 000000000000164 specified in the Pool Fields. (5060,60)'

See replication here.

NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample
         (based up made up data used in the Product name test environment). 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.