My Oracle Support Banner

Blank Card Type Value causes Procurement Card Information not to be Carried Forward to the Purchase Order (PO) when running PO_AUTO_SRC (Doc ID 2126721.1)

Last updated on SEPTEMBER 07, 2021

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

When the CARD TYPE is missing from either the Card Holder Profile or the Requester's setup, or if it is missing from the Vendor Location, Procurement Procurement Card setup, then the card information is not carried forward to the purchase order created by the PO_AUTO_SRC process.

If the card type is corrected, then the expected card data is populated on the sourced Purchase Order.

Expectation:
If the card type is required, the system should state that. As it currently is, the system does not REQUIRE the CARD_TYPE and therefore, unexpectedly, data from the requisitions is not flowing to the purchase orders.


The issue can be reproduced at will with the following steps:
1. Leave CARD_TYPE blank on the Card Holder Profile and at the Requester 's Setup.
2. Create an ePro requisition with Pcard data populated.
3. Run PO_AUTO_SRC
4. Review the PO created: the card data is not populated.

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.