PR instead of PO created

[Former Member]

Hello Guys,

in classic scenario I'm facing the problem, that SRM wants to create a PR in the BE instead of a PO.

Customizing is set (BBP_TARGET OBJ) that a PO should be created. Source of supply is transferred from a catalog (CCM 200).

SC data are complete that a PO could be created.

Number ranges and document types are maintained correct in SRM and BE.

Manual creation of PO in the BE with the same data like in SC is possible.

Is still the FM BBP_REQREQ_TRANSFER transfering the document to the BE? Trying to transfer the SC manual by testing the FM was not successful!

In BBP_PD I can see in table BBP_PDBEI that field BE_OBJECT_TYPE is filled with BUS2105 (PR) instead of BUS2012 for PO.

Has anyone an idea what is wrong?

We are using:

SRM 400

PI 2005_1_640

support package 08

R/3 46C Backend

PI 2004_1_46C

Rgds

Dieter

[Former Member]

I want to let you know the solution for this problem.

After SAP analyzed our system we had to implement note 140846 in the backend system. I think the note is an update for the backend PI.

[Former Member]

Hello Guys,

I opened a SAPnet call and will let you know what the reason was!!!

Thank you so far and

rgds

Dieter

[Former Member]

Dieter,

Did you ever find out what the cause of this was ? We have the exact same problem.

Kindest Regards

Paul

[Former Member]

Hello Yann

Yes, no problem.

I can convert the PR in a PO.

I only have to maintain a number for the PO because of cause the PO document type ECPO in BE has an external number range!

Rgds

Dieter

[yann_bouillut]

Hi Dieter,

IF your shopping cart is considered to be complete by SRM (with a fixed 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.

Now maybe it is time to try to debug.

Christophe has suggested a way to debug without debuging into R/3 :

- 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)

Kind regards,

Yann

[Former Member]

Yann,

This look like a complete "copy & past" of a previous post of mines.

In that case, just copy the link, it's quicker:

Don't forget the copyright !!

Especially you Dieter when you will assign points ))

Christophe

[yann_bouillut]

Christophe,

I mentionned your name and give Dieter only the extract (debug description) he required. ))

Yann

[Former Member]

Mouais.... l'extract allait plus loin que le pavé sur le debug.

Y'en a qui ont attaqué Google pour moins que ça !!

[yann_bouillut]

christophe :

Il n'y a que le debug et je t'ai cité !!

Le reste (message info record et (*) font partie de mes anciens posts et non des tiens. )) : tu peux vérifier.

Yann

[Former Member]

Hello Yann,

I already tried various constellations for this customizing activity, also the one you described.

No succes!

Rgds

Dieter

[yann_bouillut]

Hi Dieter,

You said you were able to create a PO directly in R/3.

Did you succeed in converting the R/3 PR (coming from SRM) into a R/3 PO ?

Regards,

Yann

[Former Member]

Hello Yann,

yes I tested it and no change in system behaviour. PR is still created after setting message 06 334 from error to warning.

So this can not be the reason.

Thank you for your support!!!

Any other ideas?

Rgds

Dieter

[yann_bouillut]

Hi Dieter,

Could you check that in custo : Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders), you didn't put "*" forpurchasing group and product category else a PR is created.

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

Please confirm.

Kind regards,

Yann

[Former Member]

Hello Yann,

i have a fixed vendor and no problems occur with the source of supply.

A PR can be created but I want a PO to be created.

Rgds

Dieter

[yann_bouillut]

Hi Dieter,

This error message prevent PO to be created !

If message is set to error, a PR is created instead of a PO.

That's why message should be warning instead of error.

Could you test it ?

Kind regards,

Yann

[yann_bouillut]

Hi Dieter,

Please check error messages in R/3 : O6 334 that could occurs in the case of a fixed vendor (please enter info record)

SE16

T160M

message 334

classe 06

change from "E" (error) to "W" (Warning)

Kind regards,

Yann

Message was edited by: Yann Bouillut