cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Dear all,

I am trying to use BAPI_GOODSMVT_CREATE to do a plant to plant transfer, but it is returning an error "Enter a tax code", even with the field GOODSMVT_ITEM-TAX_CODE filled.

We're using non-standard movement type 901, which is a copy of movement type 301, and a non-standard tax code as well.

ls_header-doc_date   = sy-datum.
ls_header-pstng_date = sy-datum.
ls_item-material     = pt-material.
ls_item-plant        = pt-plant.
ls_item-stge_loc     = pt-storage_loc.
ls_item-move_type    = pt-mov_type.
ls_item-entry_qnt    = pt-entry_qnt.
ls_item-move_plant   = pt-move_plant.
ls_item-move_stloc   = pt-move_stloc.
ls_item-tax_code     = pt-tax_code


APPEND ls_item TO lt_item.

CALL FUNCTION 'BAPI_GOODSMVT_CREATE'

EXPORTING
   goodsmvt_header  = ls_header
   goodsmvt_code    = '04'
IMPORTING
   materialdocument = lv_matdoc
   matdocumentyear  = lv_docyear
TABLES
   goodsmvt_item    = lt_item
   return           = lt_return.

I tested thru SE37 with 901 mov type and returned the error. I tried with mov 301 and it went well.

The process thru MIGO is running fine with 901.

Isn't GOODSMVT_ITEM-TAX_CODE related to MWSKZ field in MIGO? Do I have to do any additional configuration in 901 movement type?

Thanks in advance and best regards,

Johnny

0 Likes
View Entire Topic
Former Member
0 Likes

Hi Johnny,

Mvt Type 301 working fine in BAPI post then it should work for Mvt type 901. What you can do run 301 and 901 entries seperately . Cross compare value . check missing value between these movement type . you may get answer for this .

Regards,

Vishnu