2438094 - Orphan Objects Still Visible After Scoping

Orphan objects still visible after scoping the question Do you want in general restrict access to data records that do not contain any access restriction relevant content?.

SAP Cloud for Customer

We will use Accounts as example.

1. Log in with user user01(user01 represents the name of the user).
2. Go to the Customers work centre.
3. Select the Accounts view.
4. Select the All filter query.
5. User user01 is able to see orphan accounts, despite scoping.

Compatibility mode for Access Context 1015 (Employee, Territory, Sales Data) is scoped. This Scoping question is in contradiction with the question related to the restriction of data records without any access restriction relevant content.

Compatibility mode for Access Context 1015 is supposed to display all objects that were orphans, before introducing the third Access context Sales Data.

In order to restrict the visibility of orphan objects fully you have to de-scope Compatibility mode for Access Context 1015 (Employee, Territory, Sales Data).

 In order to do so you have to use the following steps:

1. Go to the Business Configuration work centre.
2. Select the Implementation projects view.
3. Select the relevant project.
4. Click the Edit Project Scope button.
5. Click the Next button until you reach Step 4 Questions.
6. Expand the Built-in Services and Support element.
7. Expand the System Management element.
8. Select the User and Access management element.
9. Under the business option scope Compatibility mode for Access Context 1015 (Employee, Territory, Sales Data) unflag the question Do you want the Access Context 1015 - sales area restriction to be effective only for objects with employee or territory assignments?

The user should not see the orphan objects anymore.

KBA , acl entry 555555555555555555555555555555 , LOD-CRM-ACC , Account , How To

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions