My Oracle Support Banner


Last updated on FEBRUARY 03, 2019

Applies to:

PeopleSoft Enterprise SCM eSupplier Connection - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.


Need enhanced functionality for Suppliers that are manufacturer's representatives.

These type of Suppliers often represent 10-20 different manufacturers and
depending on where their territories land, there could be more than one rep
for a specific line of materials.

For example, the manufacturer Valmont is represented by two different reps -
Lynn Elliott and Power Equipment Sales

As an example the Suppliers would be set up as Valmont c/o Lynn Elliott
(Location 1 for transmission poles) and then Valmont c/o Power Equipment
Sales (Location 2 for distribution poles).

They have to both be set up with the same vendor number, because they have
the same TIN representing Valmont. In these cases you do not make payment to
the rep, but directly to the Manufacturer (Valmont). The TIN is used to
check for duplicates. This validates that we don't have a duplicate supplier,
invoice id, invoice date and Invoice amount- allowing us to prevent duplicate
vouchers and potentially duplicate payments. Having two vendor numbers with
the same TIN also increases the H200 Match Exception Rule because the system
potentially can't identify who should be paid. This could delay appropriate
payments or if someone isn't paying attention.

They are both registered in the Supplier portal under the same vendor number.
The only difference would be the location.

The problem is they can both see each other's PO's, Invoices, Purchase Order
Acknowledgements, etc. because registration only goes to the vendor level-
not to the vendor location level.


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.