My Oracle Support Banner

EAP: What Data Should Be Returned For Search Defintions EP_AP_PAYMENTS and EP_AP_VOUCHERS Using "Index Only Last x Days" (Doc ID 2584427.1)

Last updated on JULY 21, 2020

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


On the PeopleTools > Search Framework > Designer > Search Definition > Advanced page, there's a field in the "Full Indexing Criteria" section called "Index Only Last x Days." doesn't seem to be working correctly for some Search Definitions, including EP_AP_PAYMENTS and EP_AP_VOUCHERS.

In the connected query AP_SRCH_PAYMENTS for the EP_AP_PAYMENTS search, the connected query uses the PS_PAYMENT_TBL.SES_LAST_DTTM field and the VENDOR.SES_VN_ATTR_L_DTTM field. That SQL looks for rows of data from PS_PMT_INQ_SRCH_VW (PS_PAYMENT_TBL) where SES_LAST_DTTM is greater than a certain date OR where VENDOR.SES_VN_ATTR_L_DTTM is greater than a certain date.

Q1. Why does the vendor selection exists at all?  If a vendor change happens in 2019, this SQL will go back and retrieve all payment data as far back as payment data exists.  Should payment data be retrieved for forty years or more just because the vendor updated their vendor record? Is that the intended purpose of that OR statement?

Q2. How is SES_VN_ATTR_L_DTTM populated? If SES_VN_ATTR_L_DTTM gets updated by recent transactions, is the process designed to pull in ALL historical payments for that vendor?

Q3 How are VENDOR.SES_VN_ATTR_L_DTTM and PAYMENT_TBL.SES_LAST_DTTM supposed to be populated during the conversion from 9.1 to 9.2?


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

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