PR instead of a PO in the backend

[Former Member]

Hi Gurus,

Can some one clarify me how does a can create PR instead of PO in the backend .

What are the factors repsonsible for creation of a PR.

I see all the data in SHC is complete and I checked the SPR0 settings also it fine there

So kinldy suggest me what should be done in this suituations.

Regards,

Sairam.

[Former Member]

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)

When you create a shopping cart in the EBP, no commitment is set

up.However, since the succession objects set up a commitment, the budget

must already be checked when you are creating the shopping

cart.Consequently, the commitment set up is simulated.This causes error

messages if a budget overrun occurs.The classic scenario is an exception

to this rule, whereby a purchase requisition is generated automatically

from a shopping cart in the R/3 back end (controlled through the

Customizing in EBP).In this case, the purchase requisition commitment is

set up in R/3.The purchase order commitment (=obligation to accept from

bindingly issued purchase orders) is set up in the FI/CO back end

(similar to R/3).The budget is checked on this basis.

When you create a shopping cart, you can control via the Customizing in

the EBP System, whether a purchase requisition or a purchase order (with

complete data) is to be created.During the generation of a purchase

order, this differentiation is of course not necessary.

I hope this information helps.

Kind regards,

Gaurav

[Former Member]

Under

SRM IMG->SRM->SRM server -> Cross-Application Basic Settings->Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)->

pur grp=*

prod cat= exact value of the prod cat in srm you want to create PR

source sys=backend

Int proc=always external proc 3

Ext proc=1 always PR

also map the no range in ECC PR doc type

and no range interval of PR in srm server backend no ranges

BR

Dinesh

[Former Member]

Hi Dinesh,

The reson why I have asked you this question is.. One user has created a Non catalog shopping cart i.e using a Textorder , Actually /Ideally this has to create a PO in the backend as per the SPRO settings in SRM.But this creates a PR in the backend .

I see everything is right in SPRO. But still the SHC creates a PR in the backend instead of PO.

I dont understand the Lpap

where exactly we are missing

can you look into this and provide me some soultion please.

Regards,

Sairam.

[Former Member]

the reason can be SOS

i.e. source of supply in SC

if you are using contract as a SOS

pl check the validity of contract and source list in ME01

SRM create PO only if the SOS is valid

otherwise it creates requisition as a follow-on

so pl check in this line

BR

Dinesh

[Former Member]

Hi. If you want to use a manual source of supply keyed into each cart you will have to use the BBP_DOC_CHANGE_BADI to change partner 00000039 to 00000019.

That way the "desired vendor" becomes a fixed vendor.

Regards,

Dave.

[imthiaz_ahmed]

I see a contradiction here for the question asked and the answer.

Ext proc=1 always PR -- Dinesh

I see everything is right in SPRO. But still the SHC creates a PR in the backend instead of PO. -- SAI RAM 

With the settings Dinesh mentioned( May be the way questioned was raised was confusing) , only the PR's will be created. I would suggest to set it up as the second option "Purchase Order if...".

Regards, IA