Skip to Content
author's profile photo Former Member
Former Member

plan driven : Changing the Create By value of the shopping Cart.

Hi All,

We are having a few issues with the Plan driven procurement. Its working fine but we have to make some changes on the SC... so was wondering if anyone has ideas.


1. When the PR is pushed usign the BBP_EXTREQ_TRANSFER program we see that the SC is created as the RFCuser maintained in the Entry channel.

Now would like to change the Created By : from RFCuser to the Requsitioner user so that it turns out to be the requisitioners SC and not the RFusers SC..

This would affect while users are trying to search for the Bid invitations using the search criteria "My Bid" as this would only pull up bids created by their user ids and if it is the RFCuser they cant pull them up...

Trials :

1. R/3 provides us with a Badi to pass on additional data to the SC for the "Plan driven PRoc" but found that there was no Changing Parameters available to pass on the requisitioner id.. like the EBAN-ARNAM..

So were wondering if we can pass it as a value in one of the custom fields and then use the Doc change Badi..

2. Observed that the Doc change badi also does not have a export field for the Created_By to build up a criteria..

3. Would like to know from where is the RFcuser being picked in SRM to create the SC so that we could try changing that while debugging to an existing SRM user and see how it behaves..

The SRM functionmodule called is the

BBP_BC_EXTREQ_INB...just in case some one is tryin out the same scenario

Would appreciate any ideas ..


Manoj A.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Apr 11, 2006 at 02:02 PM

    Hi Manoj,

    3- the RFC users is simply defined in R/3 RFC destination, linked to PR transfer profile. This is the user R/3 is connected with in SRM to call BBP_BC_EXTREQ_INB, where a user is needed to complete SC data with connected user's attributes.

    Analyse BBP_BC_EXTREQ_INB, detect where SY-UNAME is used and replace it with wanted user id.

    Ex: BBP_BC_EXTREQ_INB --> BBP_EXTREQ_INBOUND --> PERFORM fill_partner --> determine a default requestor (SY-UNAME)

    I think this is the main point of change.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Experts,

      Same requirement with me and I would like to update the Requestor and Created by user IDs and when I investigated I arrived at the same place,


      When I amend Sy-uname to any other name Shopping cart is still getting created with RFC user ID.? Any pointers Please.

      Thanks in Advance.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.