EES: Self-Service Invoicing Defaults To Wrong Address Seq Number When The Supplier Is Being Defaulted And Not Changed In Fluid
(Doc ID 2657782.1)
Last updated on APRIL 17, 2020
Applies to:PeopleSoft Enterprise FIN eSettlements - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Self-Service Invoice is created with the wrong Invoicing Address and Remitting Address when the Supplier used is the default supplier
1. Navigate to eSettlements > Supplier Information > Review Supplier Details> Create a New Supplier
2. Register Supplier ID = USA0000011 as an eSettlements Supplier
3 On the Address page, add a 2nd Address
4. On the Locations page, add a 2nd Location
a. Under Location Details, Invoicing Address and Remitting Address is associated to 2nd Address
5. On the Supplier > Location page for the 2nd Location, select Payables hyperlink
a. On the Payables Options page, Address = 2 for both Invoicing and Remitting
6. Agreement is created for Buyer = US001 / Supplier = USA0000012 / Location = LOC2
7. Navigate to eSettlements > Supplier Information > Review User Profiles
8. For User ID = JSCOTT, under Accessible Suppliers, only have 1 Supplier specified -- Contra Costa Communications (USA0000012)
9. Navigate to Main Menu > SuppliersSupplier InformationAdd/UpdateSupplier User - Make sure that the Default Supplier in eS checkbox is checked for Supplier USA0000011.
10. Create a Purchase order
11. Log into the Supplier Portal with User ID = JSCOTT
12. Create a Self-Service Invoice - Supplier USA0000011 will be defaulted
13. Enter Invoice id and click next
14. Click Copy Purchase order and click next
15. Click Submit
12. Using SQL, check the VCHR_HDR_QV for the Voucher associated to the Invoice created in Step 12
13. ADDRESS_SEQ_NUM and REMIT_ADDR_SEQ_NUM = 1
NOTE: In the Steps above, User Details/Company Name/Address/Email/Telephone Number represent a fictitious sample (based upon made-up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
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