PO not transferred to the backend R/3

[Former Member]

Hi,

01) Is it mandatory that the Extended Classic Scenario should always have a Local P Org and P group?

02) The no. range for the PO should it be local PO no. range in SPRO or can we use the no. range defined in SPRO for the SC and follow on documents for Extended Classic Scenario?

03) When we use the local P Org and P groups, PO is created in SRM system, but not transferred to R/3 (ECC 6.0).

We have done all the config and tested, it does create a PO with status approved and workflow is completed. But the PO document is not transferred to R/3.

We are on SRM 5.0 with ECC 6.0. Any SAP notes to be looked into?

Thanks and Best Regards,

DV

[masa_139 · Accepted solution]

Hello DV,

What is the document status ? Go to transaction BBP_PD.

What is the backend error message ? Go to transaction RZ20, Purchase Order.

Regards,

Masa

[yann_bouillut]

Hi,

First check :

- that your PO is a COMPLETE one (especially with "fixed" vendor

- the document type in BBP_PD

Find your SC line item content and if you have "EP" type, ECS sceanrio is ok

- Your backend destination for your product category (please refer to configuration point).

I am using SRM50 and ECC 6.0 with ECS scenario without any issue.

You just have a configuration issue ))

Kind regards,

Yann

[Former Member]

Hi Yann & Disha,

BBP_PD status for PO.

clean_reqreq_up is working fine.

BBP_PDBEI : BE_OBJECT_TYPE : BUS2012

Vendor partner function in the SC is 00000019

HEADER I1009 Held X

HEADER I1015 Awaiting Approval X

HEADER I1021 Created

HEADER I1038 Complete

HEADER I1039 Incomplete X

HEADER I1043 Ordered

HEADER I1080 In Transfer to Execution Syst. X

HEADER I1132 Transfer Failed (E.Sys.)

HEADER I1180 Document Completed

One more interesting thing is: It is mandatory to pass purchasing group details to the R/3 backend (which was apart of my question). How you pass these values depend on the situation like, maintain in the org str. with responsibilities assigned for p grp, user parameter EKG for the RFC user or use BADIs. all will lead to pass the PORG and PGRP values to pass to backend to create a PO.

I will reward points for u all guys!!!

Thanks and Best Regards,

DV

[Former Member]

Hi,

Relation for POrg and PGroup must exist in SRM and backend system.

If your item exist in backend, you need to create on ppoma_bbp POrg structure with relation to backend.

e.g:

POrg -> tab Function -> checked POrg function with backend system name and backend purchasing org. ID.

PGroup -> tab Function -> checked PGroup with backend system name and backend purchasing org. ID.

For both in attributes tab:

SYS = SRM logical system and R/3 logical system

BSA = SRM logical system and R/3 logical system (SRMCLNT100\<your_code>)

ACS = R/3 logical system

Regards,

Marcin Gajewski

[Former Member]

Hi,

Whats the status in BBP_PD?Also,check the foll:

1.Background job CLEAN_REQREQ_UP is running properly.

2.Check whether entries exist in table BBP_CUSTOM_TAB.

3.Check whether there is any entry in table BBP_PDBEI for the SC.

BR,

Disha.

Pls reward points for helpful answers.

[Former Member]

Hi,

ad 1. Yes, in Ext. Classic Scenario You must have local POrg and PGroup if you use plan driven procurement.

ad 2. Better way is to use diffrent number ranges for PO. This same number of ranges must exist in backend system (checked as extendent number of ranges). If You want to use the same range for PO as a SC enter prefix (for SC) in SPRO ->... -> Cross-Application Basic Settings -> Number Ranges -> Define Number Ranges per Backend System for follow-on doc. in column 'Number ranges of POs'.

ad 3. Check in transaction RZ20 -> B2B Procurement Monitor -> Purchase Order for more information about PO transfer.

Regards,

Marcin Gajewski