Hw to debug outbound function module

Hi,
I know how to debug inbound idoc using WE19 can sum1 tell how can i debug outbound function module.
i want to debug to see as to why certain segments are not being updated in IDOC PORDCR1.PORDCR102.
even though i put an external break-point it does't trigger .
Regards,
Jayaram Maganti

>
JAYARAM MAGANTI wrote:
> Hi,
>
> I know how to debug inbound idoc using WE19 can sum1 tell how can i debug outbound function module.
> i want to debug to see as to why certain segments are not being updated in IDOC PORDCR1.PORDCR102.
> even though i put an external break-point it does't trigger .
>
>
> Regards,
> Jayaram Maganti
Hi
See this link this is helpful for you.[debug outbound function module|Re: Cannot debug outbound queue;

Similar Messages

Debugging outbound function module

Hi,
I am trying to create or save sales order(va01). I am using ZWIP as the output type and transmitting the details to 3rd party system using idoc. Now Once I save, I could see the out bound idoc being generated. But when I put the break-point in the underlying function module, the process is not stopping there. I want to debug that function module. But all the time the idoc has been generated without stopping at the break-point.
How do I debug the function module for the outbound idoc?
Any ideas would be appreciated.
Thanks
Sachin

HI,
Before saving, put '\h' incommand line and press enter, it will go into debugging then goto settings then update debugging. Then you can press F8 to go the break-point you have create before FM.
Reg,
Sachin

Debugging Outbound Function module in EDI

Hello All,
I have a query regarding debugging function module which is used for creation of outbound Idoc for Purchase Order.
We have a Z process code which is assigned to a Z function module which creates an IDOC while a PO is created in the system.
But If I set break points in the Function module, the execution does stop there.
Can any one please tell me how to debug outbound processing Functioon module while PO is created.
Regards
Arindam

Hi,
There are 2 ways to to debug an outbound idoc triggered by an output type. One way is to set the output timing to 1, and save the purchase order and then execute RSNAST00 which will take the control to the breakpoint.
You can also debug the idoc with the output timing set as 4.
Here the idoc is triggered in update mode. Hence any breakpoints you may have set before will not reflect. Hence you need to activate update debugging.
Below are the steps for the same..
1. Add the output type in purchase order.
2. Enter '/h' to activate debugging in transaction window.
3. Save purchase order.
4. The process enters debugging mode.
5. In Settings tab, select checkbox for Update Debugging.
6. Click F8.
7. The control will appear to go out and re-enter debugging mode.
8. Now from the menu bar, in breakpoints option, choose Breakpoint At Function Module option, and give the name of the function module which is processing the idoc.
9. Once breakpoint set, click F8.
10. The control will now go to the function module. You can then debug the FM.
Hope this information is helpful.

How to connect our outbound function module to the message type

how to connect our outbound function module to the message type any transcation code exits to assign the message type with the function module .
Thank in advance .
A. Thiru

Hi Thiru,
Standard Transaction Codes, have their own Function Modules for generating Outbound/Indbound Idocs. Where these Function Modules will be configured to a particular Process Codes.
For E.g for PO's
Process code : ME10 - IDOC_OUTPUT_ORDERS - for creation
In case if its a Z Function Module, It depends on the case how you use IDOC types. either directly through Z Program or through Inbound/Outbound Process codes with respective Function modules.
Regards,
Anbalagan

How can I debug a Function Module used by smartforms

Hello everyone,
i have a problem with the function module /1BCDWB/SF00000040.
It's a module executed from a smartforms form. I need to debug this
function module while printing an invoice. While printing it should jump
to the place of the function module.
Would be grateful if someone could help me.
Best regards
F. Hoppe

This is exactly what i have done last time.
The problem is that the breakpoint does not stay at the same place
when i activate it in the module itself.
Isn't there a transaction you can put breakpoints specific to a FM?

How to DEBUG a function module running in background mode? Please help!

Hi Experts,
 I am calling a function module in my ABAP code in background module using the following syntax:
CALL FUNCTION 'YBBC2_CREATE_SNAPSHOT' IN BACKGROUND TASK
 TABLES
 itab_std_format_inv = itab_std_format_inv
 itab_snapshot_inv = itab_snapshot_inv.
 COMMIT WORK.
If I put the breakpoint in the CALL FUNCTION line and execute the program, the debugger does not take me to the valled function module. This may be because I am running the function module as background task.
I cannot comment this "IN BACKGROUND TASK" statement as well since i am debugging in Quality system where I don't have change access.
So how to DEBUG a function module running in background mode? Please help!
Thanks
Gopal

Hi,
You could try to use the following trick:
(1) Put an endless loop into the coding of your function module where you want to start debugging, e.g.
DATA:
 lx_exit_loop(1) TYPE c.
lx_exit_loop = ' '.
DO.
 IF ( lx_exit_loop = 'X' ).
 EXIT.
 ENDIF.
ENDDO.
(2) Call your function module in background task
(3) Call transaction SM50 and search for the background process.
(3) Choose from menu Program/Mode -> Program -> Debugging
Now you the debugger should bring you right to your endless loop. Set lx_loop_exit = 'X' in the debugger and continue (F5 or F6).
Reward points
Regards

IDoc outbound function module to generate Purchase order PORDCH IDoc

Hi all,
Can anyone help me with the outbound function module to generate PORDCH IDoc

instead of that you can use the Below For PO's.
Message Type : ORDCHG
Process Code : ME11
Function : IDOC_OUTPUT_ORDCHG

How to debug a function module using in the generic datasource?

Hi all,
We have created a generic data source using function modulle and have been extracting the data for a single customer it contains single records but it has pulled out more than 10,000 records. how to debug the function module used in the data source.
since we schedule for extraction in bi and back ground job gets triggered in ecc for extraction,
i know in se37 we can select the function module name and then debug but still need to check while the bacground job is trigered through bi.
Thanks

Yes you can debug the Function Module.
Open the function module in SE37 and put a break point in the code where you want to check from, then come to RSA3 and give the datasource name and check the Debug check box on this screen, once you click on the start button it will take you the place where you have placed the break point in the FM, by pressing F5 you can see the flow of the FM.
Let me know whether this solves your issue.

What is outbound function module for IDoc type INFRECMASS01

Hi,
What is outbound function module for IDoc type INFRECMASS01? This is for purchasing info record.
Thanks
Kamal

Hi Kamal,
Have you looked standard program RBDSEINF or transaction code ME18?
This program will call function module MASTERIDOC_CREATE_REQ_INFREC to generate purchasing info record IDoc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Outbound function module for IDOC WMMBID02

Hi,
Do we have any outbound function module for basic IDOC type WMMBID02 (Stock movements from ext. systems) which has message type WMMBXY.
I searched with hot keys OUTBOUND_WMMBXY in SE37 but unable to find a standard FM. My task is to extend that FM by a user-exit so as to populate my extended IDOC which is of basic type WMMBID02.
Any help would be greatly appreciated.
Regards,
Harsh

Hi Kamal,
Have you looked standard program RBDSEINF or transaction code ME18?
This program will call function module MASTERIDOC_CREATE_REQ_INFREC to generate purchasing info record IDoc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Sample Outbound Function Module for IDocs

Hello All,
Does anyone have sample code for an outbound function module for an IDoc - they created themselves. Custom or extended? Weblogs, sample code will be useful
ty, dd
Message was edited by:
 Demi Douglas

Hi,
Check this program:
REPORT zmatmas_idoc.
INCLUDE zmatmas_idoc_top.
INCLUDE zmatmas_idoc_selscreen.
INCLUDE zmatmas_idoc_formroutine.
START OF SELECTION
START-OF-SELECTION.
PERFORM get_data.
PERFORM create_idoc.
PERFORM distribute_idoc.
TABLES
TABLES: mara.
Structures
*Header
TYPES: BEGIN OF gs_h_mara,
 matnr TYPE mara-matnr,
 ersda TYPE mara-ersda,
 ernam TYPE mara-ernam,
 laeda TYPE mara-laeda,
 aenam TYPE mara-aenam,
 pstat TYPE mara-pstat,
 END OF gs_h_mara.
*Item
TYPES: BEGIN OF gs_i_makt,
 spras TYPE makt-spras,
 maktx TYPE makt-maktx,
 maktg TYPE makt-maktg,
 matnr TYPE makt-matnr,
 END OF gs_i_makt.
TYPES: BEGIN OF gs_i_mbew,
 lvorm TYPE mbew-lvorm,
 lbkum TYPE mbew-lbkum,
 salk3 TYPE mbew-salk3,
 vprsv TYPE mbew-vprsv,
 verpr TYPE mbew-verpr,
 stprs TYPE mbew-stprs,
 peinh TYPE mbew-peinh,
 matnr TYPE mbew-matnr,
 END OF gs_i_mbew.
TYPES: BEGIN OF gs_i_mvke,
 vkorg TYPE mvke-vkorg,
 vtweg TYPE mvke-vtweg,
 lvorm TYPE mvke-lvorm,
 versg TYPE mvke-versg,
 bonus TYPE mvke-bonus,
 provg TYPE mvke-provg,
 matnr TYPE mvke-matnr,
 END OF gs_i_mvke.
TYPES: BEGIN OF gs_i_mlan,
 aland TYPE mlan-aland,
 taxm1 TYPE mlan-taxm1,
 taxm2 TYPE mlan-taxm2,
 taxm3 TYPE mlan-taxm3,
 taxm4 TYPE mlan-taxm4,
 matnr TYPE mlan-matnr,
 END OF gs_i_mlan.
*Segment & control record
DATA: gs_segment_h LIKE zmara_h,
 gs_segment_i1 LIKE zmakt_i,
 gs_segment_i2 LIKE zmbew_i,
 gs_segment_i3 LIKE zmvke_i,
 gs_segment_i4 LIKE zmlan_i,
 gs_control_rec LIKE edidc.
Internal Table and work area
*Header & Item
DATA: gt_h_mara TYPE STANDARD TABLE OF gs_h_mara,
 gt_i_makt TYPE STANDARD TABLE OF gs_i_makt,
 gt_i_mbew TYPE STANDARD TABLE OF gs_i_mbew,
 gt_i_mvke TYPE STANDARD TABLE OF gs_i_mvke,
 gt_i_mlan TYPE STANDARD TABLE OF gs_i_mlan.
DATA: gw_h_mara TYPE gs_h_mara,
 gw_i_makt TYPE gs_i_makt,
 gw_i_mbew TYPE gs_i_mbew,
 gw_i_mvke TYPE gs_i_mvke,
 gw_i_mlan TYPE gs_i_mlan.
*EDIDD & EDIDC
DATA: gt_edidc LIKE TABLE OF edidc WITH HEADER LINE,
 gt_edidd LIKE TABLE OF edidd WITH HEADER LINE.
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
SELECT-OPTIONS: s_matnr FOR mara-matnr OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
*& Include ZMATMAS_IDOC_FORMROUTINE
*& Form get_data
FORM get_data .
SELECT matnr ersda ernam laeda aenam pstat
FROM mara
INTO TABLE gt_h_mara
WHERE matnr IN s_matnr.
IF sy-subrc <> 0.
 MESSAGE e003(zkaren_msgclass).
No data found according to the selection criteria
ENDIF.
IF gt_h_mara IS NOT INITIAL.
 SELECT spras maktx maktg matnr
 INTO TABLE gt_i_makt
 FROM makt
 FOR ALL ENTRIES IN gt_h_mara WHERE matnr = gt_h_mara-matnr.
 SELECT lvorm lbkum salk3 vprsv verpr stprs peinh matnr
 INTO TABLE gt_i_mbew
 FROM mbew
 FOR ALL ENTRIES IN gt_h_mara WHERE matnr = gt_h_mara-matnr.
 SELECT vkorg vtweg lvorm versg bonus provg matnr
 INTO TABLE gt_i_mvke
 FROM mvke
 FOR ALL ENTRIES IN gt_h_mara WHERE matnr = gt_h_mara-matnr.
 SELECT aland taxm1 taxm2 taxm3 taxm4 matnr
 INTO TABLE gt_i_mlan
 FROM mlan
 FOR ALL ENTRIES IN gt_h_mara WHERE matnr = gt_h_mara-matnr.
ENDIF.
ENDFORM. " get_data
*& Form create_idoc
FORM create_idoc .
*Control data
gs_control_rec-mestyp = 'ZKAR_MATMAS_MSG_TYPE'. "Message type
gs_control_rec-idoctp = 'ZKAR_MATMAS'. "IDoc
gs_control_rec-rcvprt = 'LS'. "Partner type of receiver
gs_control_rec-rcvprn = 'T90CLNT810'. "Partner number of receiver
LOOP AT gt_h_mara INTO gw_h_mara .
*Header data.
 gs_segment_h-matnr = gw_h_mara-matnr.
 gs_segment_h-ersda = gw_h_mara-ersda.
 gs_segment_h-ernam = gw_h_mara-ernam.
 gs_segment_h-laeda = gw_h_mara-laeda.
 gs_segment_h-aenam = gw_h_mara-aenam.
 gs_segment_h-pstat = gw_h_mara-pstat.
*Header segment
 gt_edidd-segnam = 'ZMARA_H'.
 gt_edidd-sdata = gs_segment_h.
 MOVE gt_edidd-sdata TO gs_segment_h.
 APPEND gt_edidd.
 WRITE:/ gs_segment_h-matnr, gs_segment_h-ersda, gs_segment_h-ernam,
 gs_segment_h-laeda, gs_segment_h-aenam, gs_segment_h-pstat.
*ITEM 1
 LOOP AT gt_i_makt INTO gw_i_makt.
 IF gw_i_makt-matnr = gw_h_mara-matnr.
*Item data
 gs_segment_i1-spras = gw_i_makt-spras.
 gs_segment_i1-maktx = gw_i_makt-maktx.
 gs_segment_i1-maktg = gw_i_makt-maktg.
*Item segment
 gt_edidd-segnam = 'ZMAKT_I'.
 gt_edidd-sdata = gs_segment_i1.
 APPEND gt_edidd.
 ENDIF.
 ENDLOOP. "at gt_i_vbak
*ITEM2
 LOOP AT gt_i_mbew INTO gw_i_mbew.
 IF gw_i_mbew-matnr = gw_h_mara-matnr.
*Item data
 gs_segment_i2-lvorm = gw_i_mbew-lvorm.
 gs_segment_i2-lbkum = gw_i_mbew-lbkum.
 gs_segment_i2-salk3 = gw_i_mbew-salk3.
 gs_segment_i2-vprsv = gw_i_mbew-vprsv.
 gs_segment_i2-verpr = gw_i_mbew-verpr.
 gs_segment_i2-stprs = gw_i_mbew-stprs.
 gs_segment_i2-peinh = gw_i_mbew-peinh.
*Item segment
 gt_edidd-segnam = 'ZMBEW_I'.
 gt_edidd-sdata = gs_segment_i2.
 APPEND gt_edidd.
 ENDIF.
 ENDLOOP.
*ITEM3
 LOOP AT gt_i_mvke INTO gw_i_mvke.
 IF gw_i_mvke-matnr = gw_h_mara-matnr.
*Item data
 gs_segment_i3-vkorg = gw_i_mvke-vkorg.
 gs_segment_i3-vtweg = gw_i_mvke-vtweg.
 gs_segment_i3-lvorm = gw_i_mvke-lvorm.
 gs_segment_i3-versg = gw_i_mvke-versg.
 gs_segment_i3-bonus = gw_i_mvke-bonus.
 gs_segment_i3-provg = gw_i_mvke-provg.
*Item segment
 gt_edidd-segnam = 'ZMVKE_I'.
 gt_edidd-sdata = gs_segment_i3.
 APPEND gt_edidd.
 ENDIF.
 ENDLOOP.
*ITEM4
 LOOP AT gt_i_mlan INTO gw_i_mlan.
 IF gw_i_mlan-matnr = gw_h_mara-matnr.
*Item data
 gs_segment_i4-aland = gw_i_mlan-aland.
 gs_segment_i4-taxm1 = gw_i_mlan-taxm1.
 gs_segment_i4-taxm2 = gw_i_mlan-taxm2.
 gs_segment_i4-taxm3 = gw_i_mlan-taxm3.
 gs_segment_i4-taxm4 = gw_i_mlan-taxm4.
*Item segment
 gt_edidd-segnam = 'ZMLAN_I'.
 gt_edidd-sdata = gs_segment_i4.
 APPEND gt_edidd.
 ENDIF.
 ENDLOOP.
ENDLOOP. "at gt_h_kna1
ENDFORM. " create_idoc
*& Form distribute_idoc
FORM distribute_idoc .
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 master_idoc_control = gs_control_rec
 TABLES
 communication_idoc_control = gt_edidc
 master_idoc_data = gt_edidd
 EXCEPTIONS
 error_in_idoc_control = 1
 error_writing_idoc_status = 2
 error_in_idoc_data = 3
 sending_logical_system_unknown = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 WRITE:/ 'Error'.
ELSE.
 LOOP AT gt_edidc.
 WRITE:/ gt_edidc-docnum.
 ENDLOOP. "at gt_edidc
ENDIF.
ENDFORM. " distribute_idoc

How to debug a function module that is written to extend a datasource

Hi all -
this is BW related question.
I have a datasource that I extended but instead of writing the code in the user exit, I created a function group and a function module to populate the custom fields. My problem is - I want to debug the function module and when I do that, I have to give datasource, infosource and update mode as input parameters. There is no data in the internal table C_T_DATA, how can I debug to get data into this table.
please let me know.
thanks,
Sabrina.

Keep the Break point Before Updating.
just click on the table c_t_data .or choose the internal table and say CTRL+F4, you can internal table content
you can find change, append ,delete options.
just select the row and click append they one blank row will appear. just add entries to that , and enter
the record will be appended, do in the same way if you need more records to add...
regards
vijay

How to debug a function module

hi,
Please Tell me how to debug an Function module
Thanks in advance
ajay

Hi,
In SE37 while executing the FM there is an option to execute the same in Debugging mode. If you want to debug the FM as a stand alone code you can make use of this functionality. Provide the necessary input values and run the FM in debugging mode.
If you intend to debug the FM from another program wherein it is called you can always set a breakpoint inside the FM and execute the code in the calling program. The control will stop for you at the point where you have set the break point inside the FM automatically.
Hope you have a clear picture now.
Reward if helpful.

Debug a functional module

Hi,
Could you please tell me how to debug the function module.
Thanks,
Subha.

In SE37 while executing the FM there is an option to execute the same in Debugging mode. If you want to debug the FM as a stand alone code you can make use of this functionality. Provide the necessary input values and run the FM in debugging mode.
If you intend to debug the FM from another program wherein it is called you can always set a breakpoint inside the FM and execute the code in the calling program. The control will stop for you at the point where you have set the break point inside the FM automatically.
check this link also
http://help.sap.com/saphelp_nw04s/helpdata/en/d1/801f36454211d189710000e8322d00/content.htm

Debugging customized function module when Idoc is triggered via ALE

Hi,
Whenever we save the billing document, an outbound idoc is triggered via ALE. The logic for the data to be included in the idoc is written in a customized function module.
However we are making some changes and would like to include some more data in the idoc. But we find that when we put a breakpoint in the function module, on saving the billing document, the flow does not stop at the break point. We are 100% sure that the code in the function module gets executed based on the data in the idoc.
How do we get into debug mode and break the flow in the function module so that we can debug in the function module?
Any help would be greatly appreciated.
Thanks in advance,
Mick

Hi Mick, this might be of some help 4 u.
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
cheers,
Hema.

Hw to debug outbound function module

Similar Messages

Maybe you are looking for