My Oracle Support Banner

PO Receipt into Project Sets GL Date and Expenditure Item Date Incorrectly in PA Interface Tables (Doc ID 1510385.1)

Last updated on SEPTEMBER 21, 2018

Applies to:

Oracle Asset Tracking - Version 12.1.2 and later
Information in this document applies to any platform.


When a PO receipt to projects is performed for an expense item, the PA interface table is populated with the Expenditure item date as the current date (date of being populated) and the GL date is populated as the week-ending date of the Expenditure item date.

This is incorrect functionality. The GL date should be populated as the receiving transaction date and the expenditure item date should be populated based on the value of profile option PA: Default Expenditure Item Date for Supplier Cost

The Projects Costing User Guide provides the following information:

Expenditure Item Date:
The date that you expect to incur the expenses for the goods or services that you are requesting for a requisition or a purchase order, or the date that you incur the charge for a invoice.This date is used during online validation using project transaction controls and becomes the expenditure item date on the expenditure item in Oracle Projects Costing.

Oracle Payables uses the profile option PA: Default Expenditure Item Date for Supplier Cost during invoice match process to determine the default expenditure item date for the supplier invoice distribution lines. Oracle Payables also uses the profile option to determine the default expenditure item date when you enter supplier invoice distribution lines for unmatched invoices.

Oracle Projects Costing uses this profile option when you run the program PRC: Interface Supplier Costs to determine the expenditure item date for Oracle Purchasing Receipts , Invoice Payments and discounts.

Therefore the expenditure item cost should be set according to the value of the PA: Default Expenditure Item Date for Supplier Cost profile option as follows:

- Transaction Date (INVTRNSDT) - The date on the receipt must be defaulted to the expenditure item that is being created. 
- Transaction GL Date (INVGLDT) -  The GL date on the receipt or PO must be used as the Expenditure Item Date
- Transaction System Date (INVSYSDT) - The current system date must be used as the Expenditure item date if the profile option date is set to this value
- Source Document Exp Item Date (POTRNSDT) - The source document date i.e the expenditure item date on the PO must be defaulted as the expenditure item date on the receipt.

Note: Failure to set this profile option can cause no record to be created in PA_TRANSACTIONS_INTERFACE_ALL and for an error to be recorded for the receipt transaction in CSI_TXN_ERRORS:
CSE_OTHERS_EXCEPTION (ERR_MSG=ORA-06592: CASE not found while executing CASE statement)



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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.