cancel
Showing results for 
Search instead for 
Did you mean: 

Shop-on-behalf issue

Former Member
0 Kudos

Hi,

We are facing one issue where not all the users are shown in the shop-on-behalf search from the same company node.

For ex: If we have 50 users under the company node in PPOMA_BBP, and if a user tries to shop on behalf of these, then only few users are shown and some users are not shown in the shop-on-behalf search. System says "No values for this selection" for these users.

The user, who is trying to shop-on-behalf, has been assigned the correct id in his "Requester" attribute so no issues from that angle.

Any pointers in this regard would be helpful.

Thanks.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Ajay,

Can you check and compare SAP & Portal roles of the users and see is there any difference.

Thanks,

Hari

Former Member
0 Kudos

Hi Hari,

Roles look fine. Moreover, since here hundreds of such users are involved, I don't think it has anything to do with roles. And sometime back, the shop-on-behalf for all the users was working fine. But it stopped abruptly for some users recently.

Any other pointers in this regard?

Thanks,

Ajay

Former Member
0 Kudos

Hi Ajay,

Try to debug the search help BBP_BOBUSER_VALUE2 for the shop-on behalf field. Sometimes also when the REQUESTOR attribute has values as OXXXXXX, due to performance issue also the results are incorrect.

Based on the findings from debugging the search help, we can do some validations if required.

Moreover the maintainance of attibute REQUESTOR on org level is always recommended when the users are less. else it may lead to inconsistencies.

Thanks,

Anshu

Former Member
0 Kudos

Hi Ajay,

I believe the REQUESTOR attribute is maintained for the corresponding company code org id, but inspite this the user is not getting the entire list of user to shop for. One of the reason might be the some of the users in that company code have the Person ID. Whenever this is the case the Person id will take the precendence, since the system will display the list of user based on the Person ID. Only the possible workaround is to maintain the REQUESTOR attribute for individual user ID i.e USXXXXXX for all the users.

Thanks,

Anshu

Former Member
0 Kudos

Hi Anshu,

Thanks for the inputs.

Currently there isn't any Person (P) ID available in PPOMA_BBP for any of the users (who don't appear in shop-on-behalf search) and the relationship just looks fine.

And since there are lot of such users who don't appear in the shop-on-behalf search, it will be a tough task to maintain the REQUESTER attribute for individual user IDs.

By the way, is there any way we can check if Person ID is available for any of the users who are not appearing in the search, just to ensure.

Moreover, until a couple of days back all the users were available in shop-on-behalf search.

So this looks quite strange.

So any further pointers on this?

Former Member
0 Kudos

Hi Ajay,

The Person ID will not be visible in PPOMA_BBP.  I understand the task to maintain the REQUESTOR attribute at user level is a tedious one. Just check the table HRP1001 , to cross check the relationship interlinkage existing for the user. Else check transaction code PA20.

Thanks,

Anshu

Former Member
0 Kudos

Hi Anshu,

I checked in the table and the relationship looks fine there too.

For a position (S) id, there are two entries in the table; one for O and one for CP, which seems ok.

And, moreover business is not in favour of individual maintenance of the user IDs in the REQUESTER attribute.

Thanks,

Ajay