‎2010 Jan 06 10:30 AM
Dear All,
I found a list of events which will be used for the transaction EA10 by the method mentioned in the video.
http://www.sap-isu.net/video/fica-events.
Out of the many events which are triggerred one of them is R431.
Right now the function module in this has no code . Accept the function start and end syntax.
When I try to put the breakpoint in this and run the transaction in the debugging mode , the flow of the program doesnt stop at the debug point.
Why such analomy?
Edited by: Rahul_paldiwal on Jan 6, 2010 11:30 AM
‎2010 Jan 06 2:56 PM
Hi,
If you go to the code of program LE21AF08. You will see that program will not go to the code if the function module is 'ISU_SAMPLE_R431'.
FORM event_r431 TABLES p_contrcl STRUCTURE t_contrcl
CHANGING p_iiu TYPE isu21_invoice_unit
p_param TYPE isu21_invoice_param.
PERFORM get_user_exit_function USING 'R431'.
REFRESH: t_vkk_doc_id.
LOOP AT t_fbstab WHERE funcc NE 'ISU_SAMPLE_R431'.
t_vkk_doc_id = p_iiu-t_vkk_doc_id.
wa_t_bill_doc = p_iiu-t_bill_doc.
CALL FUNCTION t_fbstab-funcc
EXPORTING
x_printdoc = p_iiu-print_doc
x_bldat = p_param-bldat
x_budat = p_param-budat
x_bupa = p_iiu-bupa
x_fkkvkp = p_iiu-acc-fkkvkp
TABLES
t_contrcl = p_contrcl
t_bill_doc = wa_t_bill_doc
t_vkk_doc_id = t_vkk_doc_id
EXCEPTIONS
error_message = 1.
IF sy-subrc <> 0.
mac_msg_putx co_msg_error sy-msgno sy-msgid
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4 iu_error.
ENDIF.
FREE: wa_t_bill_doc.
ENDLOOP.
* for cross reference purpose only
SET EXTENDED CHECK OFF.
IF 1 = 2. CALL FUNCTION 'ISU_SAMPLE_R431'. ENDIF.
SET EXTENDED CHECK ON.
ENDFORM. "EVENT_R431
most of time if I know the event, I just where use list the function module and go into the code and set the break-point a little bit earlier.
Cheers,
Chaiphon
‎2010 Jan 06 10:47 AM
Hi,
try to set a breakpoint at FM FKK_FUNC_MODULE_DETERMINE.
Regards,
Alexander
‎2010 Jan 06 2:56 PM
Hi,
If you go to the code of program LE21AF08. You will see that program will not go to the code if the function module is 'ISU_SAMPLE_R431'.
FORM event_r431 TABLES p_contrcl STRUCTURE t_contrcl
CHANGING p_iiu TYPE isu21_invoice_unit
p_param TYPE isu21_invoice_param.
PERFORM get_user_exit_function USING 'R431'.
REFRESH: t_vkk_doc_id.
LOOP AT t_fbstab WHERE funcc NE 'ISU_SAMPLE_R431'.
t_vkk_doc_id = p_iiu-t_vkk_doc_id.
wa_t_bill_doc = p_iiu-t_bill_doc.
CALL FUNCTION t_fbstab-funcc
EXPORTING
x_printdoc = p_iiu-print_doc
x_bldat = p_param-bldat
x_budat = p_param-budat
x_bupa = p_iiu-bupa
x_fkkvkp = p_iiu-acc-fkkvkp
TABLES
t_contrcl = p_contrcl
t_bill_doc = wa_t_bill_doc
t_vkk_doc_id = t_vkk_doc_id
EXCEPTIONS
error_message = 1.
IF sy-subrc <> 0.
mac_msg_putx co_msg_error sy-msgno sy-msgid
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4 iu_error.
ENDIF.
FREE: wa_t_bill_doc.
ENDLOOP.
* for cross reference purpose only
SET EXTENDED CHECK OFF.
IF 1 = 2. CALL FUNCTION 'ISU_SAMPLE_R431'. ENDIF.
SET EXTENDED CHECK ON.
ENDFORM. "EVENT_R431
most of time if I know the event, I just where use list the function module and go into the code and set the break-point a little bit earlier.
Cheers,
Chaiphon
‎2010 Jan 07 11:05 AM
Thanks Chaiphon for your help. It gave me a new perspective for writing Functional Specs