Try extending the following logic:
| Req8 | Commodity Approvers |
Adds approvers to the approval flow based on the commodity code of the items. For a collaborative requisition this rule applies after the end of collaboration.
[Required Helper File - CommodityApprovers.csv]
| Rec01 | Commodity Central Receivers | Adds central receivers (by commodity code), as specified in the Approver Lookup Table, to the approval flow. [Required Helper File - CommodityCentralReceiversForApprovalProcess.csv] |
Configuring Visibility Control
Application.Approvable.OrganizationalVisibilityPartitioning
Specifies whether the Visibility Control feature is enabled. The Visibility Control feature extends the approvable document and approval flow limits provided by the Import Responsible User Assignments data import task. It also adds constraints on searching (on search pages and in choosers) and reporting.
-From a Search perspective, this feature would apply only to users with QueryAll privileges. Otherwise, a user w/o QueryAll would only be able to view their own approvables and those of their subordinates.
For a user who is a member of a query all group, the Visibility Control feature limits queries to approvable documents that belong to purchasing units the user is responsible for (according to the file
ResponsibleUser.csv). The search constraint is hierarchal—that is, users can also query approvable documents that belong to “child” purchasing units.
For a user who is a member of a query all group, the Visibility Control feature provides the following search constraints for users:
• Users can query other users in:
• Their own purchasing unit and any purchasing unit they are responsible for.
• The “child” purchasing units of their own purchasing unit and of any purchasing units they are responsible for.
Other objects, such as suppliers, are filtered based on the PeopleSoft SetID. (When the Visibility Control
feature is not enabled, users are also filtered based on the PeopleSoft SetID.)
-The Visibility Control feature affects the approval flow of approvable documents as follows:
• If an approvable document is assigned to a purchasing unit that has no responsible user, or if an approvable document does not have a purchasing unit, Procure-to-Pay sends it to users who are responsible for the All purchasing unit for the appropriate group.
• Users responsible for the All purchasing unit are not added to the approval flow of approvable documents for a given purchasing unit if another user exists who has responsibility for that purchasing unit.
• Any group specified in the ResponsibleUser.csv file has an All private group, even if there are no users in that group. This behavior prevents approvable documents from being visible to the wrong users. For example, suppose User2 is responsible for purchasing units All and B as a member of the Invoice Manager group. In this case, User2 would be added to the approval flow for:
• All invoice-related approvable documents that do not have a purchasing unit, and
• All invoice-related approvable documents that belong to purchasing unit B.
Catalog Views
Application.Catalog.MinCategorySizeForCategoricView
Decides the view of Catalog Results. User can see either the categorical view or the result rows based on this parameter.
The value is an integer. If set to 0 or less, user would see the categorical view till the last node is reached. If it's a positive integer, there should be at least two categories having at least the specified number of items, to see the categorical view. The default value is 10.
Discuss with your Ariba support technical resource ( Ariba as in ARIBA resource, not an inhouse consultant working on Ariba) to look into : Catalog Views Set-up (OPTIONAL)
Use filter Types 1,2,3,4 and 5.
1 [default] Start with view nothing, show more catalog items to the qualified users --> The catalog (or all catalogs from one supplier) you specify is the only catalog shown to user groups that you did not select. So, if you selected Catalog Approver, groups other than Catalog Approver will see only the specified catalog and no others.
Similar Logic can also be used for Suppliers: Members of the group/department you specified in one of the previous steps (1-4) will be able to view items from this supplier. Anyone who does not belong to the group/department you specified will not be able to see items from this supplier.