topic Re: issue with Function module in Application Development and Automation Discussions

issue with Function module

Former Member — Thu, 14 Nov 2013 10:33:07 GMT

Dear friends

i am working on SAP FI - funds management,

my requirement is to create function modules ( as there are no BAPi's ) for Creating payment Request ( tcode F871 ), then Release Request ( F874 ) and finally Post Request ( tcode F870 ), i have created 3 function modules for all the above transactions, individually its working fine

but when i am trying to call all the three above function modules in one function module...its not working, can any one please help me in this issue

in one function module, i want all the above three functions

Thanks

Vijaya

Re: issue with Function module

nabheetscn — Thu, 14 Nov 2013 10:36:50 GMT

What is the issue you are facing when called together? did you debug themm..? Please check whether you have proper commit etc called.

Re: issue with Function module

Former Member — Thu, 14 Nov 2013 10:37:10 GMT

Hi,

Can you paste the error screen shot. You can differentiate the Three FM by actvity type parameter.

Thanks & Regards

Priyesh Shah

Re: issue with Function module

venkat_aileni — Thu, 14 Nov 2013 10:37:39 GMT

Hi-

Use COMMIT WORK AND WAIT. statement after every FM call.

-Venkat

Re: issue with Function module

NeerajRao — Thu, 14 Nov 2013 10:39:57 GMT

Hi Laxmi,

Please elaborate your question in detail and share the errors you are getting.

Re: issue with Function module

Former Member — Thu, 14 Nov 2013 10:45:19 GMT

Thanks friends for replies

i am not getting any error,

the first function module is working fine, its stopped at second function module , please let me know if anything is missing and you want any information

Thanks

Vijaya

Re: issue with Function module

Former Member — Thu, 14 Nov 2013 10:46:24 GMT

Please provide the exact nature of error you are facing

Re: issue with Function module

venkat_aileni — Thu, 14 Nov 2013 10:51:49 GMT

Hi-

Does your parameters for 2nd FM is depended on 1st FM result? If so check in debugging mode whether you are able to get those details from 1st FM results.

Are you using COMMIT WORK AND WAIT after every FM call?

-Venkat

Re: issue with Function module

former_member209120 — Thu, 14 Nov 2013 11:09:16 GMT

Hi Vijaya Laxmi

Past your code here..... to know your problem...

Re: issue with Function module

sai_krishna24 — Thu, 14 Nov 2013 11:15:01 GMT

Hi Lakshmi,

Use this statement (WAIT UP TO X SECONDS.) in between your function modules.

while we do parallel processing of transactions we need to give enough time for the commit work, else it will be in lock and rest of the transaction won't work because of lock concept.

Eg. WAIT UP TP 10 SECONDS

Thanks

Sai Krishna

Re: issue with Function module

Former Member — Thu, 14 Nov 2013 11:15:57 GMT

This is my code, i am not using COMMIT WORK and WAIT, can you please let me know how to use COMMIT WORK and WAIT

FUNCTION zfm_payment_request.

*"----------------------------------------------------------------------

*"*"Local Interface:

*" IMPORTING

*" REFERENCE(IM_BLDAT) TYPE CHAR10

*" REFERENCE(IM_BUKRS) TYPE BUKRS

*" REFERENCE(IM_BUDAT) TYPE CHAR10

*" REFERENCE(IM_XBLNR) TYPE XBLNR

*" REFERENCE(IM_BKTXT) TYPE BKTXT

*" REFERENCE(IM_LIFNR) TYPE LIFNR

*" REFERENCE(IM_FIPEX) TYPE FIPEX

*" REFERENCE(IM_FISTL) TYPE FISTL

*" REFERENCE(IM_WRBTR) TYPE CHAR14

*" TABLES

*" ITAB_MSG TYPE ZTT_MSSGS

*"----------------------------------------------------------------------

DATA : lv_req TYPE pso_lotkz,

belnr TYPE belnr_d,

l_belnr TYPE belnr_d,

p_req type pso_lotkz.

* CALL FUNCTION 'ZFM_PAY_REQ'

* EXPORTING

* bldat = im_bldat

* bukrs = im_bukrs

* budat = im_budat

* xblnr = im_xblnr

* bktxt = im_bktxt

* lifnr = im_lifnr

* fipex = im_fipex

* fistl = im_fistl

* wrbtr = im_wrbtr

* IMPORTING

* req = lv_req

* TABLES

* it_msg = itab_msg.

* CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

* EXPORTING

* input = lv_req

* IMPORTING

* output = lv_req.

CALL FUNCTION 'ZFM_PAY_REQ_APP'

EXPORTING

i_lotkz = lv_req

* IMPORTING

* REQ =

TABLES

it_msg = itab_msg.

CALL FUNCTION 'ZFM_PAY_REQ_POST'

EXPORTING

im_lotkz = lv_req

TABLES

lt_msg = itab_msg.

ENDFUNCTION.

Re: issue with Function module

former_member206479 — Thu, 14 Nov 2013 11:19:38 GMT

Hi Laxmi,

Check the necessary parameters which are needed for Second FM to succeed and after that for third FM. If every thing is good it should complete your task and dont forget to specify Commit work and wait for every FM call .

Regards,

Venkat.

Re: issue with Function module

nabheetscn — Thu, 14 Nov 2013 11:24:45 GMT

You will have to use commit work and wait if you are not using in first FM. Since 2 and 3 are dependent on value of LV_REQ which may not have got genearted.

Re: issue with Function module

satyabrata_sahoo3 — Thu, 14 Nov 2013 11:24:53 GMT

Use Commit work after the function modules.

are you using BDC for the transaction codes ?

Re: issue with Function module

former_member206479 — Thu, 14 Nov 2013 11:24:54 GMT

Hi Laxmi,

Find my Code in Bold.

FUNCTION zfm_payment_request.

*"----------------------------------------------------------------------

*"*"Local Interface:

*" IMPORTING

*" REFERENCE(IM_BLDAT) TYPE CHAR10

*" REFERENCE(IM_BUKRS) TYPE BUKRS

*" REFERENCE(IM_BUDAT) TYPE CHAR10

*" REFERENCE(IM_XBLNR) TYPE XBLNR

*" REFERENCE(IM_BKTXT) TYPE BKTXT

*" REFERENCE(IM_LIFNR) TYPE LIFNR

*" REFERENCE(IM_FIPEX) TYPE FIPEX

*" REFERENCE(IM_FISTL) TYPE FISTL

*" REFERENCE(IM_WRBTR) TYPE CHAR14

*" TABLES

*" ITAB_MSG TYPE ZTT_MSSGS

*"----------------------------------------------------------------------

DATA : lv_req TYPE pso_lotkz,

belnr TYPE belnr_d,

l_belnr TYPE belnr_d,

p_req type pso_lotkz.

* CALL FUNCTION 'ZFM_PAY_REQ'

* EXPORTING

* bldat = im_bldat

* bukrs = im_bukrs

* budat = im_budat

* xblnr = im_xblnr

* bktxt = im_bktxt

* lifnr = im_lifnr

* fipex = im_fipex

* fistl = im_fistl

* wrbtr = im_wrbtr

* IMPORTING

* req = lv_req

* TABLES

* it_msg = itab_msg.

* CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

* EXPORTING

* input = lv_req

* IMPORTING

* output = lv_req.

commit work and wait.

I think here lv_req value is required, then write like

if lv_req is not initial.

CALL FUNCTION 'ZFM_PAY_REQ_APP'

EXPORTING

i_lotkz = lv_req

* IMPORTING

* REQ =

TABLES

it_msg = itab_msg.

commit work and wait.

CALL FUNCTION 'ZFM_PAY_REQ_POST'

EXPORTING

im_lotkz = lv_req

TABLES

lt_msg = itab_msg.

else.

populate some message into itab_msg here.

endif.

ENDFUNCTION.

Regards,

Venkat.

Re: issue with Function module

thangam_perumal — Thu, 14 Nov 2013 11:25:28 GMT

Please use the keyword wait upto 5 seconds

or commit work and wait for between the function Modules.

for e.g.

CALL FUNCTION 'ZFM_PAY_REQ_APP'

EXPORTING

i_lotkz = lv_req

* IMPORTING

* REQ =

TABLES

it_msg = itab_msg.

commit work and wait. (or) wait upto 5 seconds.

CALL FUNCTION 'ZFM_PAY_REQ_POST'

EXPORTING

im_lotkz = lv_req

TABLES

lt_msg = itab_msg.

Re: issue with Function module

former_member209120 — Thu, 14 Nov 2013 11:27:09 GMT

FUNCTION zfm_payment_request.

*"----------------------------------------------------------------------

*"*"Local Interface:

*" IMPORTING

*" REFERENCE(IM_BLDAT) TYPE CHAR10

*" REFERENCE(IM_BUKRS) TYPE BUKRS

*" REFERENCE(IM_BUDAT) TYPE CHAR10

*" REFERENCE(IM_XBLNR) TYPE XBLNR

*" REFERENCE(IM_BKTXT) TYPE BKTXT

*" REFERENCE(IM_LIFNR) TYPE LIFNR

*" REFERENCE(IM_FIPEX) TYPE FIPEX

*" REFERENCE(IM_FISTL) TYPE FISTL

*" REFERENCE(IM_WRBTR) TYPE CHAR14

*" TABLES

*" ITAB_MSG TYPE ZTT_MSSGS

*"----------------------------------------------------------------------

DATA : lv_req TYPE pso_lotkz,

belnr TYPE belnr_d,

l_belnr TYPE belnr_d,

p_req type pso_lotkz.

* CALL FUNCTION 'ZFM_PAY_REQ'

* EXPORTING

* bldat = im_bldat

* bukrs = im_bukrs

* budat = im_budat

* xblnr = im_xblnr

* bktxt = im_bktxt

* lifnr = im_lifnr

* fipex = im_fipex

* fistl = im_fistl

* wrbtr = im_wrbtr

* IMPORTING

* req = lv_req

* TABLES

* it_msg = itab_msg.

COMMIT WORK AND WAIT.

if lv_req is not INITIAL.

* CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

* EXPORTING

* input = lv_req

* IMPORTING

* output = lv_req.

COMMIT WORK AND WAIT.

CALL FUNCTION 'ZFM_PAY_REQ_APP'

EXPORTING

i_lotkz = lv_req

* IMPORTING

* REQ =

TABLES

it_msg = itab_msg.

COMMIT WORK AND WAIT.

CALL FUNCTION 'ZFM_PAY_REQ_POST'

EXPORTING

im_lotkz = lv_req

TABLES

lt_msg = itab_msg.

endif.

ENDFUNCTION.

Re: issue with Function module

Former Member — Thu, 14 Nov 2013 11:30:02 GMT

YES...i used BDC

Re: issue with Function module

Former Member — Thu, 14 Nov 2013 11:56:52 GMT

In your BDC, check the Update mode at CALL TRANSACTION statement. It should be 'S'.

Debug your first functional module and check if it is returning the value for variable lv_req properly.

Re: issue with Function module

satyabrata_sahoo3 — Thu, 14 Nov 2013 12:08:36 GMT

I believe you are not using BDC Session method.

Is the first function module works fine? Read its BDC message/return parameter.

I believe second function module for F874 is using the Request Number generated from F871. Check if its getting any request number or not.

-Satya