Creating Purchase Order from accepted bid does not work

[Former Member]

Hello,

We have the following situacion:

We used SRM 5.0 with R/3 4.6C Backend.

In SRM 5.0 we aplicated the clasical escenario.

Now we upgraded our R/3 System to ECC 6.0 and found out that a previously working funcionality does not work anymore.

Funcionality: We created Purchase Orders in R/3 on the basis of a accepted Bid in the sourcing process SRM. This worked fine witha 4.6 Backend

If we try to do that with a ECC 6.0 Backend, the message "Purchase not created" (BBP_BID 233) is returned.

We checked our config in SRM and ECC 60 and it is the same as before the upgrade.

Anyone had this kind of problem before? Or how to analyze the problem? Am I right it has something to do with the upgrade?

Thanks for any reply,

Aart

[Former Member]

OK

[Former Member]

BAPI_PO_CREATE1....Check in table BBP_FUNCTION_MAP what your current version of R/3 is pointing to which FM for business object BUS2012.

[Former Member]

Hi

what is the R3 BAPI which is invoked in this process of creating a PO?

Thanks,

Aart

[Former Member]

Hi Claudia,

I did the config again as you described but this did not resolve the problem.

RFC (SM59) is working fine)

RZ20 (SRM Monitor) does not show any error for Bid invitatation / Shopping cart / Purchase Order

In transaction SLG1 I get the error message but Im not sure if this error has something to do with my problem.

"Impossible to determine comunication data from the direccion"

Message number: SPPF_MEDIA032

SLG1 (in spanish)

"-.......

Fecha: 24.08.2009 Hora: 17:12:23

Nombre de Smart Form: BBP_QUOTATION

Clase de proceso: CL_PD_QUOT_PROCESSING_BBP

Método de proceso: PROCESS_BBP_QUOT_MAI_BCS

Imposible determinar datos de comunicación a partir de dirección

No existe ningún destinatario

La acción no se ha podido ejecutar correctamente....."

Any clues?

Thanks for any answer

Aart

[Former Member]

Hi,

Just check whether the BAPI is calling the correct function module for ECC 6.0 or not...

[Former Member]

Hi Aart,

check the settings in "Define Transaction Types" and delete & reassign the follow on documents required for a RFx.

Somethings these settings have to be done again to ensure that they work.

Cheers,

Claudia