Sales Person and user details are showing in all the CCO terminals

[hari_1503]

Dear Anderson,

We are encountering some issue in the customer checkout.

1. Initially In the customer checkout manager, we have created and assigned User - X under Org. Unit (Root) & to respective CCO terminal - A. Later we have blocked the Org. Unit (Root) for the User - X and assigned to Org. Unit (A). Now when we are checking the CCO terminal - A under the user list User - X also visible.

2. In the CCO terminal, we have enabled "Enable missing sales person" option. CCO system is showing all the sales person available from the customer checkout manager irrespective of the CCO terminal assigned to the user. For. example if the User - X is assigned to CCO terminal - A, then this user should not show in other CCO terminal as a Sales person.

Please clarify this and revert if anything we can do from our end.

Thanks
Hari

[hari_1503]

Dear Anderson,

There are 10 CCO terminals and all together 20 users affected

Please advice...

Thanks

Hari

[anderson_schmitt]

Hi Hari,

It seems the possible workaround is doing some changes directly in the database.
So, I suggest you to open an incident to the SAP Support for a deeper analyze in your case.

Thank you.

Regards,
Anderson

[hari_1503]

Dear Anderson,

I have gone through the KBA and the request....

Our urgency is that the customer is insisting us to remove the sales person who is not related to the CCO terminal. This will lead the sales transaction with wrong sales person.

We don't have clue when the created request will be deployed. Please provide us any work around to overcome this issue.

Thanks

Hari

[anderson_schmitt]

Dear Hari,

How many users are affected?

Regards,
Anderson

[anderson_schmitt]

Dear Hari,

Currently, this is the system behavior. When you lock the user for an specific Org Unit, it means that the user can't log in anymore in the PoS assigned for this Org Unit, but the user remains available as sales person.

Refer to the KBA 2905615 for additional information.

There is already a Request in our Influence Channel to change this behavior. The request was accepted by our development team, but it was not deployed yet.

Regards,
Anderson

[hari_1503]

Dear Anderson,

Please advice...

Thanks

Hari