Buyer default hierarchy not working as expected
(Doc ID 1610947.1)
Last updated on APRIL 04, 2019
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Buyer Default Hierarchy not working as Expected
Lets check the Default Hierarchy one by one.
The default Hierarchy for Buyer ID is- Purchase Item Attribute->Vendor->Item Category BU->Category (Typically Used for Special Items)->User Preference->Requisition Header Defaults.
1.Purchasing Item Attribute--Check the Purchasing Attributes for the Item--Look for Primary Buyer---This is the first place it should default Buyer ID from assuming an Inventory Item is used
2.Vendor-If Buyer is not defined at above defined level -Check the Vendor-Additional Procurement Options-Buyer Field
3. Item Category Buyer-If the first 2 levels does not have any Buyer Defined, Buyer will default from Item Category --BU Attributes---Primary Buyer
4. Category (Typically used for Non Inventory Items)--If the first 3 levels does not have any Buyer defined, it will take Buyer ID as defined in Item Categories-Category Definition-Primary Buyer
5. User Preference-If none of the above 4 levels have any Buyer ID defined-System will take it from User Preferences-Procurement-Buyer Field
6. If none of the above 5 levels have Buyer defined, system will take it from Requisition Header Default level.
The higher level will always override the lower level. For example if Buyer at Purchasing Item attributes is Vp2 and at user preferences is Vp1. It should be VP2 while creating a requisition for that particular item. Similarly If buyer at Category level is VP2 and at User preferences is VP1 it will be VP2 for that particular category while raising a requisition
SET UP STEPS
We will define Buyer at Item Category Level and user Preferences level only to test this scenario. Ideally it should take Item category level buyer. Lets check the same. For testing Purpose, we will use Item XXXX, Category –XXXXand Vendor –XXXX
1. Item Purchasing Attributes-Buyer is Not defined
2. Vendor Additional Procurement Options-Buyer is not defined
3. Item Category BU Attributes –Buyer is not defined
4. Item Category –Buyer is Defined as Lets say VP2
5. User Preferences – Buyer is defined as Lets say VP3
6. Lets create a requisition using Item XXX, Vendor XXXand Category XXX
7. Add first line
8. Check the Buyer at Line level
9. As we can see it is defaulting incorrectly as VP3
10. Here category level Buyer should override the User preferences level Buyer
11. It should default VP3
12. The same issue also exists with express requisition also
13. Add the item XXXX
14. Check the Buyer
15. It is defaulting from User preferences level which is incorrect
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