issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Former Member — Thu, 19 Jul 2012 09:47:30 GMT

Hi Experts ,

As I am trying to post the Goods Receipts against each Handling unit. Delivery had been created but Material document information is not posting in MKPF table . I think I had passed all the required parameters to this BAPI. Do this BAPI required any other parameters to pass?

could any one help me regarding the same....

it's very urgent..............

Below is my code......

TABLES: lips.

TYPES : BEGIN OF ty_lips,

vbeln TYPE lips-vbeln,

posnr TYPE lips-posnr,

matnr TYPE lips-matnr,

werks TYPE lips-werks,

lgort TYPE lips-lgort,

lfimg TYPE lips-lfimg,

vrkme TYPE lips-vrkme,

vgbel TYPE lips-vgbel,

vgpos TYPE lips-vgpos,

bwart TYPE lips-bwart,

kzbew TYPE lips-kzbew,

END OF ty_lips.

DATA: gt_goodsmvt_header LIKE bapi2017_gm_head_01,

gt_goodsmvt_item LIKE bapi2017_gm_item_create OCCURS 0 WITH HEADER LINE,

gt_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.

DATA: gt_goodsmvt_headret LIKE bapi2017_gm_head_ret,

goodsmvt_code_tmp TYPE bapi2017_gm_code,

testrun TYPE c VALUE 'X'.

DATA: l_return LIKE bapiret2.

DATA: it_lips TYPE TABLE OF ty_lips,

wa_lips LIKE LINE OF it_lips,

lt_vepo TYPE STANDARD TABLE OF vepo,

lw_vepo TYPE vepo.

data: lv_mat_doc TYPE bapi2017_gm_head_ret-mat_doc,

lv_mjahr TYPE mjahr.

IF it_vepo IS NOT INITIAL.

BREAK-POINT.

SELECT vbeln posnr matnr werks lgort lfimg vrkme vgbel vgpos bwart kzbew

FROM lips INTO TABLE it_lips

FOR ALL ENTRIES IN it_vepo

WHERE vbeln = it_vepo-vbeln.

ENDIF.

gt_goodsmvt_header-pstng_date = sy-datum.

gt_goodsmvt_header-doc_date = sy-datum.

gt_goodsmvt_header-pr_uname = sy-uname.

CLEAR: wa_vepo.

LOOP AT it_vepo INTO wa_vepo.

gt_goodsmvt_header-ref_doc_no = wa_vepo-vbeln.

gt_goodsmvt_item-material = wa_vepo-matnr .

gt_goodsmvt_item-plant = wa_vepo-werks.

gt_goodsmvt_item-stge_loc = wa_vepo-lgort.

gt_goodsmvt_item-batch = wa_vepo-charg.

* gt_goodsmvt_item-deliv_numb_to_search = wa_vepo-venum.

* gt_goodsmvt_item-deliv_item_to_search = wa_vepo-vepos.

gt_goodsmvt_item-entry_qnt = wa_vepo-vemng. "'50'.

gt_goodsmvt_item-entry_uom = wa_vepo-vemeh.

READ TABLE it_lips INTO wa_lips WITH KEY vbeln = wa_vepo-vbeln

posnr = wa_vepo-posnr.

IF sy-subrc EQ 0.

gt_goodsmvt_item-deliv_numb_to_search = wa_lips-vbeln.

gt_goodsmvt_item-deliv_item_to_search = wa_lips-posnr.

gt_goodsmvt_item-move_type = wa_lips-bwart . "'101'.

* gt_goodsmvt_item-entry_qnt = wa_lips-lfimg . "'50'.

* gt_goodsmvt_item-entry_uom = wa_lips-vrkme.

gt_goodsmvt_item-mvt_ind = wa_lips-kzbew.

gt_goodsmvt_item-po_number = wa_lips-vgbel.

gt_goodsmvt_item-po_item = wa_lips-vgpos.

ENDIF.

* gt_goodsmvt_item-no_more_gr = 'X'.

APPEND gt_goodsmvt_item.

CLEAR: wa_vepo, wa_lips, gt_goodsmvt_item.

ENDLOOP.

* LOOP AT it_lips INTO wa_lips.

****<<<<<<<<<<<BAPI Communication Structure: Material Document Header Data>>>>>>>

* gt_goodsmvt_item-material = wa_lips-matnr .

* gt_goodsmvt_item-plant = wa_lips-werks.

* gt_goodsmvt_item-stge_loc = wa_lips-lgort.

* gt_goodsmvt_item-batch = wa_vips-charg.

* gt_goodsmvt_item-deliv_numb_to_search = wa_lips-vbeln.

* gt_goodsmvt_item-deliv_item_to_search = wa_lips-posnr.

* gt_goodsmvt_item-move_type = wa_lips-bwart . "'101'.

* gt_goodsmvt_item-entry_qnt = wa_lips-lfimg . "'50'.

* gt_goodsmvt_item-entry_uom = wa_lips-vrkme.

* gt_goodsmvt_item-mvt_ind = wa_lips-kzbew.

* gt_goodsmvt_item-po_number = wa_lips-vgbel.

* gt_goodsmvt_item-po_item = wa_lips-vgpos.

* gt_goodsmvt_item-no_more_gr = 'X'.

* APPEND gt_goodsmvt_item.

* ENDLOOP.

goodsmvt_code_tmp = '01'. "Assign code to transaction for BAPI goods movement

CALL FUNCTION 'BAPI_GOODSMVT_CREATE'

EXPORTING

goodsmvt_header = gt_goodsmvt_header

goodsmvt_code = goodsmvt_code_tmp

* testrun = testrun

IMPORTING

goodsmvt_headret = gt_goodsmvt_headret

materialdocument = lv_mat_doc

matdocumentyear = lv_mjahr

TABLES

goodsmvt_item = gt_goodsmvt_item

* GOODSMVT_SERIALNUMBER =

return = gt_return.

* IF gt_return[] IS INITIAL.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

wait = 'X'

IMPORTING

return = l_return.

BREAK-POINT.

* ENDIF.

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

laurent_fournier2 — Thu, 19 Jul 2012 10:15:52 GMT

What is the error you are getting ?

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Former Member — Thu, 19 Jul 2012 10:45:02 GMT

am not getting any error but the material document information is not posting into the MKPF table .........

Thanks

Ashok

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

laurent_fournier2 — Thu, 19 Jul 2012 11:00:27 GMT

No error and no posting at all, or you have fields not updated ?

You are talking about MKPF table , that's why I'm asking.

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Former Member — Thu, 19 Jul 2012 12:26:03 GMT

Hi Experts,

when we use the above posted code we get an success message that "Delivery 180045623 Created", this BAPI is creating a Delivery instead of creating a GR for Handling Unit.

We are surprised why this BAPI is creating a Delivery number? Is some thing we are passing wrong to this BAPI?

Your help would be highly appriciated.

Thanks & Regards

Chowdary

topic issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE' in Application Development and Automation Discussions

issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'

Re: issue while posting the GR against each Handling unit using 'BAPI_GOODSMVT_CREATE'