Skip to Content
avatar image
Former Member

Need help for "Requestor" attribute

We are building organization structure (manually) with around 40000 (fourty thousands) users. We have to provide BOBO (Buy on behalf of) functionality here. Our client wants this functionality for all users. I would like to take your suggestions on that, how we can build it efficiently, so that we won't get any performance issue on the later stage.

I did lot of research via oss messages/notes. I found the following things:

"A very important point to note is that the attribute "requestor" is provided to define single employee (or limited number of employeesÂ’ assigned to specific department) for which one is allowed to "shop for". It is not recommended to define the whole company as performance problems will occur.

If possible, change the attribute "requestor" to a lower organization unit. This will improve the performance significantly. We should define the attribute requestor at more specific level instead of at a higher organization unit, inheriting the entire organization structure.

But, if we have to have this requirement (having this functionality for all employees); we have to use BADI "BBP_F4_READ_ENTRY" for the method GET_BROWSER. This will stop the system to preload all data to an internal table".

So, now my questions are:

1. For maximum how many users, we can use this BOBO functionality without any performance issue?

2. In case, If we have to implement the above BADI, how much effort is required to do it? If possible, please give me estimate.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Apr 25, 2008 at 03:02 PM


    Good research on BOBO.

    #1. As far i know, there is "NO" specific user number to determine the performance bottleneck.

    Because it depends upon the complexity of Org structure, relational data, resource availability (hardware), network performance...etc.. so you can't determine a specific number with all these external factors. i wont recomment to go for BOBO for across the company.

    #2. BADI implementation depends upon your developer skills, i can visualize this to a max of 2 or 3 business week.

    Cheers, Renga.

    **Award points for helpfull answer**

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 26, 2008 at 02:32 PM

    Hi Neelesh,

    You are very correct. The shop on behalf functionality will not impose performance issues if it is used for a set of users (i.e. Person is responsible for shopping on behalf for a set of users)

    But when you are planning to use Org Id in the "REQUESTER" i.e. The user is set as responsible for shopping on behalf for a Org, then this will cause serious performance issues.

    The approach is to use the BADI to populate the Users list without using the "REQUESTER", either through some roles, custom attributes etc. Hope this helps.



    Add comment
    10|10000 characters needed characters exceeded