topic Re: date issue while using BAPI_GOODSMVT_CREATE' bapi in Application Development and Automation Discussions

date issue while using BAPI_GOODSMVT_CREATE' bapi

Former Member — Mon, 12 Oct 2009 04:45:46 GMT

hi ,

iam using code like this

DATA: BEGIN OF GMHEAD.

INCLUDE STRUCTURE BAPI2017_GM_HEAD_01.

DATA: END OF GMHEAD.

DATA: BEGIN OF GMCODE.

INCLUDE STRUCTURE BAPI2017_GM_CODE.

DATA: END OF GMCODE.

DATA: BEGIN OF MTHEAD.

INCLUDE STRUCTURE BAPI2017_GM_HEAD_RET.

DATA: END OF MTHEAD.

DATA: BEGIN OF ITAB OCCURS 100.

INCLUDE STRUCTURE BAPI2017_GM_ITEM_CREATE.

DATA: END OF ITAB.

DATA: BEGIN OF ERRMSG OCCURS 10.

INCLUDE STRUCTURE BAPIRET2.

DATA: END OF ERRMSG.

DATA: WMENGE LIKE ISEG-MENGE,

ERRFLAG.

DATA : WA_MARA LIKE MARA.

DATA GV_VAR TYPE SY-DATUM.

GV_VAR = SY-DATUM - 30.

GMHEAD-PSTNG_DATE = '09092009'.

GMHEAD-DOC_DATE = '09092009'.

GMHEAD-PR_UNAME = SY-UNAME.

GMCODE-GM_CODE = '03'. "01 - MB01 - Goods Receipts for Purchase Order

ITAB-MOVE_TYPE = '201'. "'pcitab-mvt_type'.

itab-mvt_ind = 'B'.

ITAB-PLANT = '2101'."pcitab-plant.

ITAB-MATERIAL = 'T00105'. "pcitab-material.

ITAB-ENTRY_QNT = 11.

ITAB-COSTCENTER = '2101AD01'."pcitab-qty.

itab-move_stloc = 'CPC1'.pcitab-recv_loc.

ITAB-STGE_LOC = 'MSD1'."pcitab-issue_loc.

itab-po_number = pcitab-pur_doc.
itab-po_item = pcitab-po_item.

APPEND ITAB.

BREAK-POINT.

CALL FUNCTION 'BAPI_GOODSMVT_CREATE'

EXPORTING

GOODSMVT_HEADER = GMHEAD

GOODSMVT_CODE = GMCODE

IMPORTING

GOODSMVT_HEADRET = MTHEAD

MATERIALDOCUMENT =
MATDOCUMENTYEAR =

TABLES

GOODSMVT_ITEM = ITAB

GOODSMVT_SERIALNUMBER =

RETURN = ERRMSG

CLEAR ERRFLAG.

LOOP AT ERRMSG.

IF ERRMSG-TYPE EQ 'E'.

WRITE:/'Error in function', ERRMSG-MESSAGE.

ERRFLAG = 'X'.

ELSE.

WRITE:/ ERRMSG-MESSAGE.

ENDIF.

ENDLOOP.

BREAK-POINT.

IF ERRFLAG IS INITIAL.

COMMIT WORK AND WAIT.

IF SY-SUBRC NE 0.

WRITE:/ 'Error in updating'.

EXIT.

ELSE.

WRITE:/ MTHEAD-MAT_DOC, MTHEAD-DOC_YEAR.

perform upd_sta.

ENDIF.

out put is like this

*Error in function*

*For the V3 fiscal year variant, no period is defined for 09.20.0909*

Re: date issue while using BAPI_GOODSMVT_CREATE' bapi

former_member156446 — Mon, 12 Oct 2009 04:50:00 GMT

Do this way:

GMHEAD-PSTNG_DATE = '20090909'.

GMHEAD-DOC_DATE = '20090909'.

Re: date issue while using BAPI_GOODSMVT_CREATE' bapi

Tamas_Hoznek — Mon, 12 Oct 2009 04:50:19 GMT

You have to specify the dates in YYYYMMDD format. So instead of '09092009', use '20090909'.

Re: date issue while using BAPI_GOODSMVT_CREATE' bapi

Former Member — Mon, 12 Oct 2009 04:55:39 GMT

hi ,

useing this bapi transfering data from 'java' to 'sap' in java side they are passing date as '20090909'

still we are afcing the problem.

regards

Re: date issue while using BAPI_GOODSMVT_CREATE' bapi

former_member156446 — Mon, 12 Oct 2009 05:05:31 GMT

is 09 09 2009 valid entry in V3 ? try to pass some other date say 09 10 2009 and check..

also ask your functional team to check if the value is valid for the fisical year variant..

Re: date issue while using BAPI_GOODSMVT_CREATE' bapi

Former Member — Tue, 13 Oct 2009 09:01:18 GMT

http://www.sap-img.com/abap/bapi-goodsmvt-create-to-post-goods-movement.htm