My Oracle Support Banner

Sourcing Events Awarded To Purchase Order With Incorrect Budget Date (Doc ID 2814866.1)

Last updated on MARCH 07, 2022

Applies to:

PeopleSoft Enterprise SCM Strategic Sourcing - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Sourcing Events awarded to Purchase Order with incorrect budget date

A requisition for a sourcing event was created in FY21 but the sourcing event was not awarded to a Purchase Order until FY22. The PO is getting created with a budget date from the requisition which is in a previous fiscal year. 
This is causing an issue because the users cannot receipt and pay against this Purchase Order unless it rolls the Purchase Order to the new fiscal year.
Purchase Order should be built with the date that the PO was created.

The issue can be reproduced at will with the following steps:

1. Create Requisition and Budget Check. Requisition date '08/26/2021' (past date).   Note: Distribution information. Budget date 08/26/2021
2. Copy requisition into a Sourcing Event. Requisition copied
3. Mark Event as public
4. Post the event
5. Bid on the event from supplier portal
6. Submit bid
7. Analyze the event and save it
8. Award the event to a PO
9. PO created in current date '08/30/2021',  Accounting date is current date is '08/30/2021'. But Budget date was created from requisition associated '08/26/2021' and should be '08/30/2021'


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.