Last updated on MARCH 13, 2017
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When copying a Purchase Order into a PO Voucher, the Payment Terms Basis Date Type is not defaulting from the copied PO transaction. It still takes the value specified at the Business Unit Payables Definition level, which is higher in the hierarchy, and should not be taken into consideration if at the Purchase Order level a different value got selected.
This issue seems to be similar to that reported in FSCM 9.1 <Bug 14728020>, and explained in existing <Document 1513690.1> (EAP: The 'Basis Date Type' field on the Voucher Entry page is not loading from the PO).
1.- At the Business Unit Payables Definition level for US001, define the Payment Terms Basis Date Type = Invoice Date
2.- At the USA0000001 Supplier's Location Procurement options, define the Payment Terms Basis Date Type = Default from Higher Level
3.- Create a brand new Purchase Order for Business Unit US001, and Supplier ID USA0000001, making sure to have the following settings at the Supplier Details tab: (overriding the initially defaulted values)
a) Payment Terms = 00 (Due Immediately)
b) Basis Date Type = User Date
c) Basis Date = December 30th 2016
4.- Proceed to dispatch the Purchase Order
5.- Add a new Voucher transaction into the system, within Business Unit US001
6.- At the Invoice Information tab, use the Copy From PO feature to select the Purchase Order previously created, and default all its content into the new PO Voucher
7.- Confirm that while Payment Terms are correct, defaulting the value from the Purchase Order, the Basis Date Type is incorrect: Inv Date instead of User Date
8.- Click on the Payment Terms Details icon, and confirm that:
a) The Basis Date Type is Inv Date, while it should be User Date
b) The Basis Date is blank, while it should have defaulted the one specified at the Purchase Order level: December 30th 2016
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
The Basis Date Type is Inv Date, while it should be User Date, and Basis Date is blank, while it should have defaulted the one specified at the Purchase Order level: December 30th 2016. This will surely cause an incorrect Due Date to be calculated, and placed at the Scheduled Payment tab.
The Payment Basis Date Type value from the PO Voucher should take that coming from the original Purchase Order, which overrode the Business Unit, and Supplier configurations.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms