{"id":3444,"date":"2020-08-27T09:41:00","date_gmt":"2020-08-27T08:41:00","guid":{"rendered":"https:\/\/www.brainbox.consulting\/blogs-nieuws\/ariba-feature-release-2005-4\/"},"modified":"2020-08-27T09:41:00","modified_gmt":"2020-08-27T08:41:00","slug":"ariba-feature-release-2005-4","status":"publish","type":"post","link":"https:\/\/brainbox.consulting\/talent\/ariba-feature-release-2005-4\/?lang=nl","title":{"rendered":"Ariba Feature Release 2005\/4"},"content":{"rendered":"

Set access control for editing sourcing event content<\/strong><\/h1>\n

1.\u00a0\u00a0\u00a0\u00a0\u00a0 Description<\/h2>\n

In the 2005 feature releases from SAP Ariba for SAP Ariba Sourcing and SAP Ariba Strategic Sourcing Suite, a new feature Set access control for editing sourcing event content <\/strong>is available, automatically enabled for all customers and ready for immediate use. The challenge that this feature solves is that previously, project owners on sourcing projects could define project groups that their members could view only some content contained in a sourcing event. However, for groups that had visibility into sourcing event content, there was no way to control edit access to that sourcing event content. As a result, SAP Ariba enabled this feature introducing two new roles that allow users to define project groups and access control lists to control edit access to sourcing event content, the Sourcing Supplier List Editor<\/strong> and the Sourcing Content Editor<\/strong>.<\/p>\n

Follow in this blog we will explain the prerequisites, restrictions, and changes of this feature to the existing functionality.<\/p>\n

 <\/p>\n

2.\u00a0\u00a0\u00a0\u00a0\u00a0 Prerequisites & Restrictions<\/h2>\n

As a prerequisite, to set access control for sourcing events, items and item terms, the user should be a member of the Template Creator<\/strong> group.<\/p>\n

Besides the prerequisites, below we are presenting the restrictions that this feature includes.<\/p>\n

    \n
  1. All users having permission to view an event section can see all content regardless of the edit access control setting. The edit control setting only restrict the ability to edit the content on an event section.<\/li>\n
  2. The team members who can edit the RFX have, by default, the permission to edit all content in the event. SAP Ariba recommends that administrators set up content to be restricted by default so that users cannot edit content without the proper permissions, and then provide specific content edit permission for event sections.<\/li>\n
  3. Permissions can be given for sourcing events, content, sections, items, item terms, questions, and the list of suppliers invited to the sourcing event.<\/li>\n
  4. The permissions given for the item terms should not override the permissions for items.<\/li>\n
  5. The edited permissions for an item term, such as a price term, the information is updated in all the places where that item term is used.<\/li>\n
  6. Access control settings do not grant event edit permission to users who do not otherwise have it. To be more specific, only members of the Project Owner and assignee project groups have permission to make a sourcing event editable. If a sourcing event is editable, editing access control further can restrict who can edit specific sections or not.<\/li>\n<\/ol>\n

     <\/p>\n

    3.\u00a0\u00a0\u00a0\u00a0\u00a0 Changes to existing functionalities<\/h2>\n

    As it was mentioned above there are two roles that allow users to define project groups and access control lists to control edit access to sourcing event content, the Sourcing Supplier List Editor,<\/strong> and the Sourcing Content Editor. <\/strong><\/p>\n