My Oracle Support Banner

Copy Req With Closed Gl Date, All Accounts Are Null On New Req (Doc ID 2592654.1)

Last updated on SEPTEMBER 26, 2019

Applies to:

Oracle iProcurement - Version 12.2.7 and later
Information in this document applies to any platform.

Symptoms

When a user copies a requisition in iProcurement, if the requisition was created in a prior GL period the GL account from the original requisition is deleted.
If a favorite charge account exists it will use that, or the charge account will remain empty.
This is not expected behavior and if a requisition created in the current period is copied the new requisition keeps the original account code.

12.1.3
Profile PO:Validate GL Period = Redefault
Copying from existing old req with GL date in close period.
The accounts on old req will be copied on the new req with current GL date.

12.2.7
Profile PO:Validate GL Period = Redefault
Copying from existing old req with GL date in close period.
The accounts on old req will not be copied on the new req with current GL
date.
Accounts are null on new req.

*Encumbrance is used.

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.