Last updated on JANUARY 13, 2017
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
Question 1:We need to pass the Purchase Order associated with Recurring PO Voucher contract to Project Costing for Cost Collection. However, once the purchase order is auto sourced, the status of POs associated with Recurring PO voucher is never set to D(dispatched). As per existing design, the Purchase Order should be either Dispatched, Complete, Pending Cancel or Cancel for PO to PC cost Collection process to select the Purchase Order. Is there any delivered way to pass this Purchase Order (related to recurring PO voucher contract) to Project Costing for cost collection.
Question:Ideally, system should allow passing the POs associated with Recurring PO Voucher contracts to Project costing for cost collection, similar to the POs that are recorded directly in Purchasing. So, can you please provide details on why these POs (associated with Recurring PO Voucher contract) are treated differently from the POs originating in purchasing when it comes to PC cost collection process.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms