My Oracle Support Banner

Troubleshooting Issues Resulting from Invalid or Missing EXPENDITURE_ITEM_DATE on Supplier Invoices (Doc ID 1486372.1)

Last updated on JANUARY 31, 2019

Applies to:

Oracle Payables - Version 12.1.1 to 12.1.3 [Release 12.1]
Oracle Project Costing - Version 12.1.1 to 12.1.3 [Release 12.1]
Oracle Grants Accounting - Version 12.1.1 to 12.1.3 [Release 12.1]
Oracle Project Planning and Control - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Purpose

In Release 12 new functionality was added to allow users various options in terms of how the expenditure item date is derived when matching an invoice to a project-related purchase order.

This feature is controlled by the profile option "PA: Default expenditure Item date for supplier cost" (PA_AP_EI_DATE_DEFAULT). The possible settings are:

 

SettingLookup Code
Source Document Exp Item Date POTRNSDT
Transaction Date INVTRNSDT
Transaction GL Date INVGLDT
Transaction System Date INVSYSDT

 

Two primary issues with the implementation of the feature have been:

  1. When the profile option is not set, or is set to an invalid value, supplier invoices created in Payables by matching to a project-related PO are created with a NULL expenditure item date (EXPENDITURE_ITEM_DATE). 

    The original profile option definition created from pa120pc.ldt incorrectly defined the List of Values (LOV) for the profile option.  As a result, when the profile option was set by the user, the value being saved on the back end was the lookup meaning rather than the actual lookup code (e.g., the profile option value was stored as 'Transaction Date' rather than 'INVTRNSDT').  This naturally has resulted in many cases where the profile has been set to an invalid value, even though the correct user-visible value (e.g., 'Transaction Date') is displayed in the profile options form.

  2. When the value of the profile option is something other than "Source Document Exp Item Date", this can result in a change to the expenditure item date that was entered and validated on the PO.  These validations were not being carried out on the new expenditure item date at the point of matching the invoice to the PO, which could result in invalid expenditure item dates being assigned on the invoice.

These two issues result in missing or invalid expenditure item dates on project-related supplier invoices, and this condition can produce a wide array of symptoms, issues, and problems in both Payables and Projects.  The purpose of this document is to identify the various symptoms that can result from the two conditions above, and to provide a complete solution which will resolve them.

 

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Symptoms
 Symptom:  Supplier Invoices are Not Being Interfaced to Projects or the Interface Process Encounters Errors
 Symptom:  Supplier Invoices are Rejected During Interface With Rejection Reasons Related to the Expenditure Item Date
 Symptom: PRC: Update Project Summary Amounts (PAXACMPT) or PRC: Refresh Project Summary Amounts (PAXACRPT) Fail with ORA-01400
 Symptom:  Project Performance Reporting Processes Fail
 Symptom:  The Expenditure Type LOV in the Invoice Workbench Contains No Values
 Symptom:  Distributions Cannot be Generated on Freight Lines Created in iSupplier
 Symptom:  Supplier Invoices in Payables Fail Validation During Funds Check
 Solution
 Setup
 Code Fix
 Data Fix
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.