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

Shopping Cart with Sourcing

Hi guys,

We have the following situation:

We use in SRM 5.0 (classic scenario), shopping carts which are transfered automatically to the Back End system where they generate Pur.Requisitions.

NOw we want to implement a sourcing process via the sourcing cockpit which generates a Backend PO (starting with a Shopping cart)

Our problem is that we do not know how to seperate a shopping cart which goes directly to the backend (PurReq) from a shopping cart which has to pass the sourcing process.

We cannot distinguish by Product Category and both shopping carts can be without vendor located in the positions!

We could not find a config which allows to use different documento types!

anyone had this situation before? How can we solve this problem?

Thanks for any reply,

Aart

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Apr 09, 2008 at 01:19 AM

    Hi,

    How about implementing the BADI BBP_SRC_DETERMINE.

    Regards,

    Masa

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 09, 2008 at 04:35 AM

    Hello,

    Could you checkthe foll cust link in SPRO:

    Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).

    PO is created if you set the "*" for EITHER the purchasing group OR the product category.

    SRM is creating PR or PO depending on:

    SRM customizing (ex: always external proc + PR if incomplete, PO if complete)

    the interpretation of SC data by R/3.

    IF your SC is considered complete by SRM (but with a fixed vendor and not a preferred vendor) the system will check if it can create a PO in R/3.

    For this, each item will request a META_INTERPRETE_DATA to R/3, asking if it can create a PO. If R/3 considers this data as incomplete, it will reply to create a PR.

    Usual cases of R/3 PR creation instead of PO:

    prefered vendor in SRM (and not a fixed one)

    custom checks in user exits in R/3

    error messages in R/3 (ex: O6 334 In the case of a fixed vendor, please enter info record)

    ...

    To debug without debuging into R/3, you can also try the following:

    use BADI DETERMINE_TARGET_OBJECT and force PO creation

    so the system will always try to create a PO

    R/3 won't create the PO (for the same reason as in META_INTERPRETE_DATA), and will raise an error in SRM

    finally you get the real error in application monitor (SC --> backend application errors

    Related thread:

    po-not-create-from-sc-with-source-of-supply-in-cla

    I hope this will help.

    Kind regards,

    Gaurav

    Add a comment
    10|10000 characters needed characters exceeded

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.