topic Re: BAPI_OUTB_DELIVERY_CREATE_STO in Application Development and Automation Discussions

BAPI_OUTB_DELIVERY_CREATE_STO

Former Member — Wed, 14 Sep 2016 06:38:33 GMT

Hi Experts,

I am using BAPI_PO_CREATE1 to POs for open PRs, and after creting POs i am using Bapi commit as well and also Wait stmt is used for 5 sconds. After that i am trying create delivery for the created PO just now. BAPI_OUTB_DELIVERY_CREATE_STO is used for creating the Delivery, but i am getting error saying that PO is already delivered or PO is not for delivery relevant. But when i use BAPI is directly using SE37 and able to create Delivery. Please help.

Warm regards,

Rajesh

Re: BAPI_OUTB_DELIVERY_CREATE_STO

raghug — Wed, 14 Sep 2016 12:09:52 GMT

If SE37 works and your program does not, the first step would be to check if all the relevant fields are properly sent through their conversion exits. Your delivery number for example will have to padded with zeros in front.

Re: BAPI_OUTB_DELIVERY_CREATE_STO

Former Member — Wed, 14 Sep 2016 12:40:38 GMT

In addition to the above reply, you can check the type of PO created.

Thanks,

Sowbhagya

Re: BAPI_OUTB_DELIVERY_CREATE_STO

Former Member — Wed, 14 Sep 2016 17:40:39 GMT

i have used CONVERSION_EXIT_ALPHA_INPUT for the PO created and passed the same to to Bapi, but getting same error. "Order item XXX already delivered or not delivery relevant " Message ID V50R no 062".

Re: BAPI_OUTB_DELIVERY_CREATE_STO

raghug — Thu, 15 Sep 2016 11:50:15 GMT

All the relevant fields need to be zero padded correctly, including the item, material, etc.

Re: BAPI_OUTB_DELIVERY_CREATE_STO

Former Member — Fri, 16 Sep 2016 08:58:02 GMT

i checked and found that some Delivery no is created and showed in the import parameters on BAPI when i execute directly from SE37 but not updated in concern PO with PO History tab. That means its also not directly executing SE37 also not working i guess. If its true then what could be missing in the PO or some other ? Pl advise

Re: BAPI_OUTB_DELIVERY_CREATE_STO

raghug — Fri, 16 Sep 2016 16:04:16 GMT

You have to use BAPI_TRANSACTION_COMMIT after the first call for the data to be written to the database.

Re: BAPI_OUTB_DELIVERY_CREATE_STO

Former Member — Sat, 17 Sep 2016 02:00:50 GMT

below is the code.

CALL FUNCTION 'BAPI_PO_CREATE1'
       EXPORTING
         poheader         = wa_poheader
         poheaderx        = wa_poheaderx
       IMPORTING
         exppurchaseorder = lv_po
       TABLES
         return           = it_return
         poitem           = it_poitem
         poitemx          = it_poitemx.
     READ TABLE it_return WITH KEY type = 'E' TRANSPORTING NO FIELDS.
     IF sy-subrc = 0.
       lv_po_message = wa_return-message.
       CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
     ELSE.
       CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
         EXPORTING
           wait = c_wait.
       CLEAR : it_return,it_poitem,it_poitemx.
       CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
           input = lv_po
         IMPORTING
           output = wa_stock_item-ref_doc.
       SELECT SINGLE * FROM ekpv INTO wa_ekpv
         WHERE ebeln = lv_po.
*      wa_stock_item-ref_doc = lv_po.
       wa_stock_item-ref_item = wa_ekpv-ebelp .
       APPEND wa_stock_item-ref_doc TO it_stock_item.
       CALL FUNCTION 'BAPI_OUTB_DELIVERY_CREATE_STO'
         EXPORTING
           ship_point        = wa_ekpv-vstel
         IMPORTING
           delivery          = lv_delno
         TABLES
           stock_trans_items = it_stock_item
           return            = it_return.
       READ TABLE it_return WITH KEY type = 'E' TRANSPORTING NO FIELDS.
       IF sy-subrc = 0.
         lv_del_message = wa_return-message.
         CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
       ELSE.
         CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
             wait = c_wait.

Re: BAPI_OUTB_DELIVERY_CREATE_STO

Former Member — Sat, 17 Sep 2016 02:01:14 GMT

This message was moderated.

Re: BAPI_OUTB_DELIVERY_CREATE_STO

raghug — Mon, 19 Sep 2016 14:41:57 GMT

Re-reading this, it looks like you are saying that the BAPI call is now working and you have a delivery created. But, this delivery that is created is not showing up in the document flow. Is this correct? Or, is the delivery not actually created still, did you check the delivery tables or VL03n?

If it is still failing, did you check what is actually in the it_return in the debugger? If you are still testing in SE37, did you set up a Test Sequence to run the BAPI_TRANSACTION_COMMIT after the BAPI_OUTB_DELIVERY_CREATE_STO?