PO is created in the Backend Instead of PR - Classic Secnario - SRM 5.0

Question

SRM experts,
My client has upgraded to SRM 5.0 and ECC 6.0 from SRM 3.0 and 4.6c version respectively. SRM is using classic scenario, so Shopping cart is created in SRM and Purchase Requisition and Purchase Orders are created in the backend system. In the Sources of supply tab, we will see the Vendor, Outline agreement and other information based on the Plant, Product category and Purchasing group we select in the shopping cart. If user selects the vendor with outline agreement in the sources of supply tab then Shopping cart will create Purchase order instead of Purchase requisition in the backend system.  I am new at this client’s site and client does not have any documentation about how these has been configure in the system. Can someone please help me to find out where the settings might have been made in the system to create Purchase order instead of Purchase requisition if shopping cart contains vendor with outline agreement. I am asking this question because we have another enhancement request with similar requirement but with different condition.
I will reward the points for helpful answers.
Thank you experts.
MP

Answer 1

Hi,
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:
Re: PO not create from SC with source of supply in classic sena
BR,
Disha.
<b>Pls reward points for useful answers.</b>