EAP: Defaulting on Voucher When Vendor Location has Multiple Effective Dates with Different Payables/Procurement Options (Doc ID 1515382.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

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

Goal

The pay Terms defined on Procurement Options of the Vendor Location are not defaulted on the Voucher as expected in the following two scenarios:

ISSUE 1:
System allows to create a Voucher with an Invoice Date prior to the Active Vendor Location Effective Date.

ISSUE 2:
Vendor Location with multiple effective dates, each with different Pay Terms, Banks and Payment Methods are defined. When the Voucher with History, Current and Future dated it is not defaulting the voucher with correct vendor setup.

STEPS:
1. Navigate to Vendors > Vendor Information > Add/Update > Vendor > Vendor Location and enter 3 active effective dated rows with 12/1/2012, 11/1/2012 and 1/1/2003.
2. Setup Procurement Options for these three effective dated rows as below:
12/1/2012 - Payment Terms ID = 00
11/1/2012 - Payment Terms ID = 30
1/1/2003 - Payment Terms ID = 2D
3. Add a Voucher on 11/30/2012 with Invoice Date = 08/30/2012. The Pay Terms on the Voucher defaults to 30. 
4. Add a Voucher on 11/30/2012 with Invoice Date = 12/3/2012.  The Pay Terms on the Voucher defaults to 30.

EXPECTED BEHAVIOR:
The Pay Terms in the first case needs to be defaulted to 2D and 00 in the second case.
 

Solution

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