How transfer a PO created by a program from SRM to R3

[Former Member]

Hi,

I created a program (SE38) in which i create a released PO´s, i use the functions

bbp_pd_po_create_initial

bbp_pd_po_update

bbp_pd_po_save

and commit work

The PO is released in SRM

But now i want to transfer that PO to R3, Is there a call function or a badi or code or a report to transfer the created PO's to R3 since the program.

thanks.

[Former Member]

Hi

IN SRM PO will transmitted to backend system with RFC settings.

But can manually push a PO to the back end useing the FM : BBP_PD_PO_TRANSFER.

REgards,

Satish Gopal

[Former Member]

Hi Giovani,

Did you try to create PO with the correct parameter as below.

BE_OBJECT_TYPE = BUS2012 ,

BE_OBJECT_ID = <po numbe>r ,

BE_OBJ_ITEM = <po line item number>

BE_LOG_SYSTEM = <backend logical system>

check the BBP_PD doc for PO created from SRM and PO created through the ABAP. you could notice some difference.

The other thing is that after your PO creation through ABAP , workflow should be triggered and the satatus should be set to approved. once approved the set released method of the workflow would trigger the transfer of document to backend.

Cheers

Iftekhar Alam

[peter_novoth]

Hi Giovani,

the SRM uses RFC for sending PO data to the backend system. The formal call of for the PO creation is:

CALL FUNCTION 'BAPI_PO_CREATE1'
    DESTINATION av_rfc_dest

where you need to give the name the logical system as a destination (here: 'av_rfc_dest'). It's suggested to use this standard way.

For more information see also the part 'Create docment' of the SAP Community page I created recently:

https://wiki.sdn.sap.com/wiki/display/SRM/Shoppingcarttransfer

- In the classic scenario -depending on the backend system release- we use one of these adaptors (SE24, doubleclick on the methond CREATE_DOCUMENT):

TYPE FUNCTION

ERP_1.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

ERP_2.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

ERP_2.0_1C CL_BBP_BS_ADAPTER_PO_CRT_ERP10

ERP_3.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

ERP_4.0 /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP

NON_SAP_1 NOR3_PO_CREATE

R/3_3.1H CL_BBP_BS_ADAPTER_PO_CRT_31I

R/3_3.1I CL_BBP_BS_ADAPTER_PO_CRT_31I

R/3_4.0B CL_BBP_BS_ADAPTER_PO_CRT_40B

R/3_4.5B CL_BBP_BS_ADAPTER_PO_CRT_45B

R/3_4.6B CL_BBP_BS_ADAPTER_PO_CRT_46B

R/3_4.6C CL_BBP_BS_ADAPTER_PO_CRT_46C

R/3_4.70 CL_BBP_BS_ADAPTER_PO_CRT_470_1

ERP_4.0 CL_BBP_BS_ADAPTER_PO_CRT_ERP10

- In the extended classic scenario -depending on the backend system release- we use one of these adaptors (SE24, doubleclick on the methond CREATE_DOCUMENT):

TYPE FUNCTION

APO_3.0A BAPO30A_DPO_TRANSFER

ERP_1.0 B46B_DPO_TRANSFER

ERP_2.0 B46B_DPO_TRANSFER

ERP_2.0_1C B46B_DPO_TRANSFER

ERP_3.0 B46B_DPO_TRANSFER

ERP_4.0 B46B_DPO_TRANSFER

MARKETSET XML_DPO_TRANSFER

NON_SAP_1 NOR3_DPO_TRANSFER

R/3_3.1H B31I_DPO_TRANSFER

R/3_3.1I B31I_DPO_TRANSFER

R/3_4.0B B31I_DPO_TRANSFER

R/3_4.5B B31I_DPO_TRANSFER

R/3_4.6B B46B_DPO_TRANSFER

R/3_4.6C B46B_DPO_TRANSFER

R/3_4.70 B46B_DPO_TRANSFER

REMOTE_01 XML_DPO_TRANSFER

Regards,

Peter