Calling BAPI_PO_CREATE1 in ME_PROCESS_PO_CUST

Hi Buddies,
Users want to create another PO automatically when they created one PO using ME21N and if the automatic creating failed the error message will be populated in ME21N.
I chose to call BAPI_PO_CREATE1 within the method ME_PROCESS_PO_CUST~CHECK,but the problem is the transaction will be ran endless untill the memory was consumed over.
But when I put the BAPI in the method POST,everything is fine except error messages can't interrupt the process.
is there anyone who has the practical experiences in creating a PO with the enhancement of ME21N?

Similar Messages

Error while calling BAPI_PO_CREATE1

dear experts , we are creating PO from SRM using bapi BAPI_PO_CREATE1 ,
I am getting a strange problem for PO type GTX it is throwing error that enter Payment terms but with the same data if PO type is TX them there is no error
I tried to debog the bapi I got this that it is not checking payment terms field in case of TX PO
please help
Edited by: Akash on Sep 27, 2010 8:24 AM

Hi Akash,
May be for particular Document type you need to pass Payment terms..
so pass value for Payment term and also pass 'X' in POHEADERX for payment terms...
Regards,
Ankit.

Getting error Maintain services or limits while calling BAPI_PO_CREATE1

Hi All,
I am facing the problem with the BAPI for creating the Open Purchase Orders.
I am using the BAPI_PO_CREATE1 and getting the error "Please maintain services or limits".
I have check all the field which are required in the POSERVIES table and populating the same. But still getting the same error.
Can any one please suggest me how to solve this error.
Thanks for Helping.
Regards
Balu

Hi Akash,
May be for particular Document type you need to pass Payment terms..
so pass value for Payment term and also pass 'X' in POHEADERX for payment terms...
Regards,
Ankit.

Submit new Item Conditions via Function Module BAPI_PO_CREATE1

Hi all,
I have problems using FM BAPI_PO_CREATE1.
I want to transfer Item conditions via FM, but I am not able to change the netprice via FM, my Conditions are not displayed within the Item (only netprice of Item is displayed).
I create POs out of a SRM System via FM BBP_PO_INBOUND (which calls BAPI_PO_CREATE1).
My question:
Has anyone an example how to fill in data within table POCOND so that my PO item contains for example a gross price and a rebate.
I am stucked, I can´t find the solution to create item conditions via FM BAPI_PO_CREATE1.
Any examples?
Thanks a lot
Regards
Andreas

Problem resolved
I used the FBGENDAT param in R/3 system to generate test data automatically, compare the data and finally I found my error.
--> OSS note 539978
Regards
Andreas

Regarding BAPI_PO_CREATE1

Hi Freinds,
I am using BAPI_PO_CREATE1 to create a purchase order based on the purchase requisition from ME21n.
but I am struck up with the following 2 errors.
1. 'Procurement without material from vendor with plant assignment is not defined'.
2. 'Subcontracting as stock transfer within a company code not possible'.
Even I search in this forum also not found.
Please help on the above.

Hi,
For those who will have the same problem related to passing the subcontract fields
The solution is to fill the table EXTENSIONIN : example :
STRUCTURE VALUEPART1 VALUEPART2
SERRU 1 00010
DISUB_SOBKZ "Q" 00010
DISUB_PSPNR "00000289" 00010
If it is not working try :
TYPES: BEGIN OF lty_ebelp,
ebelp TYPE ebelp,
END OF lty_ebelp.
TYPES BEGIN OF lty_adsub.
include TYPE lty_ebelp.
include TYPE disub_mepoitem_data.
TYPES END OF lty_adsub.
TYPES BEGIN OF lty_adsubx.
include TYPE lty_ebelp.
include TYPE disub_mepoitem_datax.
TYPES END OF lty_adsubx.
DATA: ls_extensionin TYPE bapiparex,
lt_extensionin TYPE STANDARD TABLE OF bapiparex,
ls_adsub TYPE lty_adsub,
ls_adsubx TYPE lty_adsubx.
ls_adsub-ebelp = '00010'.
ls_adsub-serru = '1'.
ls_adsub-disub_sobkz = 'B'.
ls_adsub-disub_pspnr = '00000289'.
MOVE ls_adsub TO ls_extensionin-valuepart1.
ls_extensionin-structure = cl_adsub_constants=>extin_po_struc.
APPEND ls_extensionin TO lt_extensionin.
ls_adsubx-ebelp = '00010'.
ls_adsubx-serru = 'X'.
ls_adsubx-disub_sobkz = 'X'.
ls_adsubx-disub_pspnr = 'X'.
MOVE ls_adsubx TO ls_extensionin-valuepart1.
ls_extensionin-structure = cl_adsub_constants=>extin_po_strucx.
APPEND ls_extensionin TO lt_extensionin.
So data structure LT_EXTENSIONIN will be used when calling BAPI_PO_CREATE1.
Note : The solution is explained in the SAP Note 1566153.
Best regards
Youssef BENAAMOU

Stock Transfer Order: Delivery date issue BAPI_PO_CREATE1

Hi,
I am creating STO using Inbound Delivery data from BAPI_PO_CREATE1
inbound shipping date is 30 may 2014.
Passing below data
HeaderData:
doc_type = 'UB'.     "STO
suppl_plnt     =     '101'
doc_date     =     inbound shipping date.
comp_code     =     '1000'
purch_org = '20'
pur_group     =     '200'
Headerx Data:
doc_type = X
suppl_plnt     =     X
doc_date     =     X.
comp_code     =    X
purch_org = X
pur_group     =   x
Item Data:
Po_item = tabix of loop
Material = material from Inbound delivery item
plant = '101'
strge_loc = W.
Qunatity = from Inbound item only.
ItemX Data:
Po_item = X
Material = X
plant = 'x
strge_loc = X.
Qunatity = X.
Schedule Line Data:
po_item = tabix of loop
schedule_line = '001'
delivery_date = shipping date
del_datcat_ext = 'D'.
Quantity     =     quantity from Inbound item.
call function 'bapi_po_create1'.
     exporting
          poheader = header data
          poheaderx = headerx data
      importing
          exppurchaseorder = po
      table
          return = return
          poitem = item data
          poitemx = itemx data
          poschedule = schedule data
          poschedulex = schedulex data.
when i am creating STO with above method STO is getting created and all data in it also correct but delivery date is 20th june 2014
instead of 30 may 2014.
it is coming as there is planned delivery time that is 21 so it is showing 20th june 2014.
but i need this value as 30th may 2014 only.
please help me on that.
thanks in advance.
Regards,
Gaurav

Hello,
You have to populate internal tables pocond and pocondx with values for itm_number,cond_st_no,cond_count,cond_value,cond_type, currency and change_id. Then call BAPI_PO_CREATE1.
Thanks,
Venu

Issue BAPI_PO_CREATE1

Hi,
I am creating Purchase order using the BAPI , BAPI_PO_CREATE1, but the problem is that, when I am passing new Net_price in ITEM and 'X' in ITEMX for the same, the Po is created but the price I passed is not there it is adopted from OLD. What Parameter I have to pass so that my Po is created with new price.
thanks
bobby

Hello,
You have to populate internal tables pocond and pocondx with values for itm_number,cond_st_no,cond_count,cond_value,cond_type, currency and change_id. Then call BAPI_PO_CREATE1.
Thanks,
Venu

Purchase Order item customer fields

I have the following scenario:
- I need to save some customer fields in Purchase Order item, when it is generated through the Shopping Cart (EBP).
- When EBP will generate a PO in backend (R/3), it calls B470_PO_CREATE function module and inside it calls BAPI_PO_CREATE1 in R/3. This call does not use extensionin parameter.
- I have all the values in PO_ITEMS parameters. (an append structure in bapi_mepoitem).
- Trying to solve this, I think I have to use EXIT_SAPL2012_001 to create the extensionin parameter.
- Anyone else has this problem?
- How can I create the extensionin parameter? Is it only necessary to add 'BAPI_TE_MEPOITEM' and 'BAPI_TE_MEPOITEMX'?
- Do you have an example?
Thank you!

Hi
You have to extend CI_EKPODBX with the same fieldnames with type BAPIUPDATE (in SE11), and then while passing the EXTENSIONIN to the bapi, you have to flag those. Like the following:
DATA: wa_extensionin TYPE BAPIPAREX,
wa_BAPIPAREX TYPE BAPIPAREX,
wa_BAPI_TE_MEPOITEM TYPE BAPI_TE_MEPOITEM,
wa_BAPI_TE_MEPOITEMX TYPE BAPI_TE_MEPOITEMX.
wa_BAPI_TE_MEPOITEM-po_item = <PO Line No.>.
wa_BAPI_TE_MEPOITEM-ZZZ_FIELD1 = <z-field value>.
wa_BAPIPAREX-STRUCTURE = 'BAPI_TE_MEPOITEM'.
wa_BAPIPAREX-VALUEPART1 = wa_BAPI_TE_MEPOITEM.
APPEND wa_BAPIPAREX TO extensionin.
wa_BAPI_TE_MEPOITEMX-po_item = <PO Line No.>.
wa_BAPI_TE_MEPOITEMX-ZZZ_FIELD1 = 'X'.
wa_BAPIPAREX-STRUCTURE = 'BAPI_TE_MEPOITEMX'.
wa_BAPIPAREX-VALUEPART1 = wa_BAPI_TE_MEPOITEMX.
APPEND wa_BAPIPAREX TO extensionin.
This will work. Please let me know if it does not.
See related links ->
Re: BAPI_PO_CREATE1 and EXTENSIONIN structure
Re: Passing custom fields to BAPI
Problem in populating userfields in PO using BAPI_PO_CREATE1
Re: BAPI_PO_CHANGE
Yann i need ur help..
Re: Custom field values are not being transfered to the backend system
Problem in populating userfields in PO using BAPI_PO_CREATE1
Re: Implement ME_PROCESS_PO_CUST-Urgently!
Re: Purchase Order (BAPI_PO_CREATE! --> EXTENSIONIN)
Re: How to use BAPI extensions?
Re: BAPI_PO_CREATE1 user fields not saving on EKPO
BAPI_PO_CREATE1 - EXIT_SAPL2012_001
Do let me know.
Regards
- Atul

Creating a PO Using BAPI For Multiple PLants Or Multiple Line Items

Hi All
    Can you please suggest me how to create a Purchase Order Using BAPI_PO_Create1 for Multiple Plants Or for Multiple Line items. The Requirement is like the PO is for single material for single vendor but for mulple stores i.e plants
NOte: Suggest me the Creation of PO for MUltiple Line items or for multiple plants Using BAPI . Hope you people will give me the needful.
Regards
Shivakumar Bandari

Hi,
Here is the sample code to do that...
*---> po header data
wa_poheader-vendor    = your vendor..
wa_poheader-doc_type = Your doc type..check with Functional contact....
wa_poheader-purch_org = Purchasing Org..
wa_poheader-pur_group = Purchasing Group
*---> po header data (change toolbar)
wa_poheaderx-vendor    = 'X'.
wa_poheaderx-doc_type = 'X'.
wa_poheaderx-purch_org = 'X'.
wa_poheaderx-pur_group = 'X'.
*---> poitem data
data: item like ekpo-ebelp.
item = '0010'.
loop at t_parts.
it_poitem-po_item = '00010'.
IT_POITEM-PLANT    = Plant..
IT_POITEM-STGE_LOC = Sloc...
*---> poitemx (item data change toolbar)
it_poitemx-po_item = '0010'.
it_poitemx-po_itemx = 'X'.
IT_POITEMX-PLANT    = 'X'.
IT_POITEMX-STGE_LOC = 'X'.
*---> add record's to internal table
APPEND: it_poitem,
         it_poitemx.
endloop.
*call bapi_po_create1
CLEAR v_ebeln.
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      poheader         = wa_poheader
      poheaderx        = wa_poheaderx
    IMPORTING
      exppurchaseorder = v_ebeln
    TABLES
      return           = it_return
      poitem           = it_poitem
      poitemx          = it_poitemx.
*---> check the return table for error message
READ TABLE it_return WITH KEY type = 'E'.
IF sy-subrc NE 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
endif.
Thanks,
Murali

Creating a PO using OREDERS05 IDOC

Hi All,
I need to create a PO using the OREDRS05 Idoc, insted of that a standard SO is getting created as I am using ORDE process code. I dnt find any process code for creating a PO related to ORDERS05.
Is there any process code for creating a PO or we need to it any other way.
Please let me know how to reslove this. Its an urgent requirment needs to be resolved ASAP.
Thanks,
Srikanth

Hi,
Here is the sample code to do that...
*---> po header data
wa_poheader-vendor    = your vendor..
wa_poheader-doc_type = Your doc type..check with Functional contact....
wa_poheader-purch_org = Purchasing Org..
wa_poheader-pur_group = Purchasing Group
*---> po header data (change toolbar)
wa_poheaderx-vendor    = 'X'.
wa_poheaderx-doc_type = 'X'.
wa_poheaderx-purch_org = 'X'.
wa_poheaderx-pur_group = 'X'.
*---> poitem data
data: item like ekpo-ebelp.
item = '0010'.
loop at t_parts.
it_poitem-po_item = '00010'.
IT_POITEM-PLANT    = Plant..
IT_POITEM-STGE_LOC = Sloc...
*---> poitemx (item data change toolbar)
it_poitemx-po_item = '0010'.
it_poitemx-po_itemx = 'X'.
IT_POITEMX-PLANT    = 'X'.
IT_POITEMX-STGE_LOC = 'X'.
*---> add record's to internal table
APPEND: it_poitem,
         it_poitemx.
endloop.
*call bapi_po_create1
CLEAR v_ebeln.
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      poheader         = wa_poheader
      poheaderx        = wa_poheaderx
    IMPORTING
      exppurchaseorder = v_ebeln
    TABLES
      return           = it_return
      poitem           = it_poitem
      poitemx          = it_poitemx.
*---> check the return table for error message
READ TABLE it_return WITH KEY type = 'E'.
IF sy-subrc NE 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
endif.
Thanks,
Murali

BADI or BAPI Getting Trigerred at the time of PO approval or Creation

Hi Gurus,
Can Anyone of you just guide me by giving one or more BADIs name that are getting trigerred at the time of PO approval or before Ordered. I am in the nick of the project. Please help urgently.
Points will be rewarded.
Thanks in Advance,
Mohit.

Hi
Which SRM version and scenario are you using ?
In Extended Classic Scenario, the Purchase order in Back system is created using BADI - BBP_CREATE_PO_BACK (which in turn calls BAPI_PO_CREATE1 in backend system) when the final Approver / Manager approves the particular shopping cart...
Related useful pointers ->
Re: BAPI_PO_CREATE1
Re: DATA VALIDATION INSIDE BAPI_PO_CREATE / BAPI_PO_CREATE1
Re: Enable Plan Driven for Classic Scenario
Do let me know.
Regards
- Atul

How can add partner at the time of PO creation

The requirement is to add an extra partner in the Purchase Order header Partner tab at the time of PO creation itself. The PO is being posted through Idoc. A custom function module has been maintained as inbound processing FM and it calls BAPI_PO_CREATE1 inside.Can anyone help me resolving the requirement?

Using GOS ...

PO is not creating in system

Hello Experts,
Iu2019m trying to create a PO through u2018BAPI_PO_CREATE1u2019. Iu2019ve gathered all the structure and fields which this bapi needs to create PO. When I call this BAPI in my report program the whole code get execute but I never get any message which tells me that a PO has been created in the system. Can somebody please tell me what is wrong with my code OR am I missing something in it.
For reference here is my code.
===========================================================
REPORT zad_bapi_po_create                      .
Constant Declaration for BAPI *****************
Data: l_bsart like mepo_topline-bsart value 'NB',
      l_bsart1 like mepo_topline-bsart value 'ZNB'.
Constants: c_ekorg like mepo1222-ekorg value 'POMR',
           c_ekgrp like mepo1222-ekgrp value 'PG1',
           c_bukrs like ekko-bukrs value 'SBPL',
           c_x value 'X'.
Internal table Declaration for BAPI *****************
Data:begin of i_tab occurs 0,
     verkf like ekko-verkf,
     verkf1 like ekko-verkf,
     lifnr like ekko-lifnr,
     werks like ekpo-werks,
     ebelp1 like ekpo-ebelp,
     matnr like ekpo-matnr,
     idnlf like ekpo-idnlf,
     menge(16),
     bprme like ekpo-bprme,
     lewed like ekpo-lewed,
     netpr(13),
     currkey(5),
     ebeln like eord-ebeln,
     ebelp like eord-ebeln,
     verkf2 like ekko-verkf,
     kalsk like lfm1-kalsk,
     bsart like mepo_topline-bsart,
     lifnr1 like ekko-lifnr,
     flag(1),
     pstyp like ekpo-pstyp,
     end of i_tab.
Data Declaration for BAPI *****************
DATA: BEGIN OF pohead OCCURS 10.
        INCLUDE STRUCTURE bapimepoheader.
DATA: END OF pohead.
DATA: BEGIN OF poheadx OCCURS 10.
        INCLUDE STRUCTURE bapimepoheaderx.
DATA: END OF poheadx.
*EXPPURCHASEORDER
DATA: BEGIN OF ponum.
        INCLUDE STRUCTURE bapimepoheader.
DATA: END OF ponum.
DATA: BEGIN OF poitem OCCURS 100.
        INCLUDE STRUCTURE bapimepoitem.
DATA: END OF poitem.
DATA: BEGIN OF poitemx OCCURS 100.
        INCLUDE STRUCTURE bapimepoitemx.
DATA: END OF poitemx.
DATA: BEGIN OF poitemsch OCCURS 100.
        INCLUDE STRUCTURE bapimeposchedule.
DATA: END OF poitemsch.
DATA: BEGIN OF poitemschx OCCURS 100.
        INCLUDE STRUCTURE bapimeposchedulx.
DATA: END OF poitemschx.
DATA: BEGIN OF errmsg OCCURS 10.
        INCLUDE STRUCTURE bapiret2.
DATA: END OF errmsg.
DATA : errflag.
START-OF-SELECTION.
refresh pohead.
refresh poheadx.
clear pohead.
refresh poitem.
refresh poitemx.
pohead-DOC_type = i_tab-bsart.
pohead-vendor = i_tab-lifnr.
pohead-purch_org = c_ekorg.
pohead-creat_date = sy-DATUM.
pohead-pur_group = c_ekgrp.
pohead-comp_code = c_bukrs.
pohead-sales_pers = i_tab-verkf2.
pohead-doc_Date = sy-datum.
pohead-langu = sy-langu.
pohead-currency = 'USDN'.
pohead-item_intvl = ''.
append pohead.
poheadx-doc_type = c_x.
poheadx-vendor = c_x.
poheadx-purch_org = c_x.
poheadx-pur_group = c_x.
poheadx-comp_code = c_x.
poheadx-sales_pers = c_x.
poheadx-item_intvl = c_x.
poheadx-doc_date = c_x.
poheadx-currency = c_x.
poheadx-langu = c_x.
append poheadx.
refresh poitem.
clear poitem.
refresh poitemsch.
clear poitemsch.
refresh poitemschx.
clear poitemschx.
poitem-po_item = '0010'.
poitem-material = '40-210'.
poitem-quantity = '1'.
poitem-po_unit = 'ST'.
poitem-net_price = '1'.
poitem-no_rounding = 'X'.
poitem-plant = '1200'.
poitem-info_upd = ''.
poitem-item_cat = '0'.
poitem-vend_mat = ''.
append poitem.
clear poitemx.
poitemx-po_item = '0010'.
poitemx-MATERIAL = c_x.
poitemx-QUANTITY = c_x.
poitemx-PO_UNIT = c_x.
poitemx-NET_PRICE = c_x.
poitemx-NO_ROUNDING = c_x.
poitemx-PLANT = c_x.
poitemx-GR_TO_DATE = c_x.
poitemx-INFO_UPD = c_x.
poitemx-tax_code = c_x.
poitemx-item_cat = c_x.
POITEMx-ACCTASSCAT = c_x.
poitemx-AGREEMENT = 'X'.
poitemx-AGMT_ITEM = 'X'.
poitemx-VEND_MAT = c_x.
append poitemx.
poitemsch-po_item = '0010'.
poitemsch-sched_line = '0001'.
poitemsch-delivery_date = sy-datum.
poitemsch-quantity = '1'.
append poitemsch.
poitemschx-po_item = '0010'.
poitemschx-sched_line = '0001'.
poitemschx-po_itemx = c_x.
poitemschx-delivery_Date = c_x.
poitemschx-quantity = c_x.
append poitemschx.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
    poheader                     = pohead
    POHEADERX                    = poheadx
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
NO_MESSAGING                 =
NO_MESSAGE_REQ               =
NO_AUTHORITY                 =
NO_PRICE_FROM_PO             =
IMPORTING
EXPPURCHASEORDER             =
   EXPHEADER                    = ponum
EXPPOEXPIMPHEADER            =
TABLES
   RETURN                       = errmsg
   POITEM                       = poitem
   POITEMX                      = poitemx
POADDRDELIVERY               =
   POSCHEDULE                   = poitemsch
   POSCHEDULEX                  = poitemschx
POACCOUNT                    =
POACCOUNTPROFITSEGMENT       =
POACCOUNTX                   =
POCONDHEADER                 =
POCONDHEADERX                =
POCOND                       =
POCONDX                      =
POLIMITS                     =
POCONTRACTLIMITS             =
POSERVICES                   =
POSRVACCESSVALUES            =
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
if sy-subrc eq 0.
write:/ 'PO Created successfully!!!'.
else.
write:/ 'Error Occured during PO Creation'.
endif.
===========================================================
Thanks,

Bapi's do not set sy-subrc. The only way to check if it was succesfull is to loop into the return table for error messages:
You have to use BAPI_TRANSACTION_COMMIT after calling BAPI_PO_CREATE1:
    READ TABLE errmsg TRANSPORTING NO FIELDS
                        WITH KEY type = c_e.
    IF NOT sy-subrc IS INITIAL.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = c_x.
ENDIF.

Problem in creating Purchase order through Idoc

Hi ABAPers,
I am trying to post PO document through WE19 t-code using inbound function module BAPI_IDOC_INPUT1 which is calling BAPI_PO_CREATE1 internally.And i am getting below error messages.
1. Characteristic does not exist in operating concern AC01
2. This function only possible for subcontracting items
3. No instance of object type PurchaseOrder has been created. External reference
passing data to IDOC:PORDCR102
Header Segment : E1BPMEPOHEADER and E1BPMEPOHEADERX
company code    0814
doc_type            NB
vendor                0000400001
poprg-                EPRO
pgroup               U01
Item Segment : E1BPMEPOITEM and E1BPMEPOITEMX
Item                  00010
material             000000000000000263
plant                 0374
Qty                   22.000
Delivery Segment E1BPMEPOSCHEDULE and E1BPMEPOSCHEDULEX
Item                  00010
Schedule line     0001
delivery date      01.12.2008
Qty                   22.000
Note: i am able to create PO successfully, through SE37 by using FM BAPI_PO_CREATE1 with given above data.
Please confirm me, what else i need to pass to post PO through WE19 t-code using inbound function module BAPI_IDOC_INPUT1.
Please reply me ASAP.
Thanks and Regards,
Sekhar Raju.

must be data format issue. when you use Function_module/BAPI from SAP GUI, convertion exit is applied automatically. hence data is converted to proper format & submited.

Create purchase order in backend ECC5

Hi,
have the following scenario:
we have a SRM-system(SRM 4.0) with many R/3 backend (46B, 46C, 4.7, ECC5)
I need to save some customer fields in Purchase Order item, when it is generated by SRM.
When SRM will generate a PO in backend (R/3) with release ECC5, it calls B470_PO_CREATE function module and inside it calls BAPI_PO_CREATE1 in R/3.
in SRM the system using Badi BBP_PO_CREATE_BACK method FILL_PO_CREATE1_INTERFACE, but we have a problem: the parameter is empty. Anyone know why?
Can you help me?
Best regards
Alessio

Hi
Please go through the links as well ->
Re: Creating of PO in backend
Re: BAPI_PO_CREATE1
Re: PO doesn't get created, backend returns PO number with "S" message
Re: User defined fields
Re: Modify print price indicator in PO using BBP_CREATE_PO_BACK
Regards
- Atul

Calling BAPI_PO_CREATE1 in ME_PROCESS_PO_CUST

Similar Messages

Maybe you are looking for