‎2007 Feb 22 1:16 PM
Hi All,
We are making programs unicode compliant. While doing extended checks I am getting following error. Could you please let me know how to resolve errors from extended checks.
<b>Error :
Program: ZSDS_DEPLOYMENTS_BACK Row: 1196 [Prio 1]
In PERFORM or CALL FUNCTION "BAPI_PO_CREATE1", the the actual parameter
"WT_RETURN" is too short for the formal parameter "RETURN".
(You can hide the message using "#EC *)</b>
<b>Program:</b>
wt_return type BAPIRETURN occurs 0 with header line,
ws_return like bapiret2,
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
POHEADER = wm_poheader
POHEADERX = wm_poheaderx
POADDRVENDOR =
TESTRUN =
MEMORY_UNCOMPLETE =
MEMORY_COMPLETE =
NO_MESSAGING =
NO_MESSAGE_REQ =
NO_AUTHORITY =
NO_PRICE_FROM_PO =
IMPORTING
EXPPURCHASEORDER = wm_exppurchaseorder
EXPHEADER = wm_expheader
TABLES
RETURN = wt_return
POITEM = wt_poitem
POITEMX = wt_poitemx
POADDRDELIVERY =
POSCHEDULE = wt_poschedule
POSCHEDULEX = wt_poschedulex
POACCOUNT =
POACCOUNTPROFITSEGMENT =
POACCOUNTX =
POCONDHEADER =
POCONDHEADERX =
POCOND =
POCONDX =
POLIMITS =
POCONTRACTLIMITS =
POSERVICES =
POSRVACCESSVALUES =
POSERVICESTEXT =
EXTENSIONIN =
EXTENSIONOUT =
POTEXTHEADER = wt_potextheader
POTEXTITEM = wt_potextitem
POPARTNER =
.
Commit BAPI changes to database.
call function 'BAPI_TRANSACTION_COMMIT'
importing
return = ws_return.
Thanks
‎2007 Feb 22 1:21 PM
Hi Yogesh,
Structure of BAPIRETURN and BAPIRET2 is different.
Try defining your table refering to BAPIRET2.
wt_return type <b>BAPIRET2</b> occurs 0 with header line,
Regards,
Phani
‎2007 Feb 22 1:19 PM
Hi Yogesh,
Structure of BAPIRETURN and BAPIRET2 is different.
Try defining your table refering to BAPIRET2.
Regards,
Phani
‎2007 Feb 22 1:21 PM
Hi Yogesh,
Structure of BAPIRETURN and BAPIRET2 is different.
Try defining your table refering to BAPIRET2.
wt_return type <b>BAPIRET2</b> occurs 0 with header line,
Regards,
Phani
‎2007 Feb 22 1:22 PM
<b>DATA: WT_RETURN TYPE TABLE OF BAPIRET2 WITH HEADER LINE.</b>
‎2007 Feb 22 1:25 PM