2008 Aug 07 12:05 PM
Hello Experts,
My problem is related to Idoc generation using ABAP Port Type.
In the creation of ABAP Port, one Z function module is assigned which has the code to generate another Idoc(MASTER_IDOC_DISTRIBUTE is used inside).
The problem is, I am able to create the first Idoc using this ABAP Port, and in the status, the first Idoc reached 03 with a message that this Idoc number reached the Zfunction module(which is assigned to port). But I'm unable to see the second Idoc generated. Even I am not sure whether this second Idoc generated or not.
Can you please explain how this ABAP Port type behaves, how to get this function module (which is assigned to port) into debugging mode and help me to solve this.
Regards
Sunil
Hello Experts,
My problem is related to Idoc generation using ABAP Port Type.
In the creation of ABAP Port, one Z function module is assigned which has the code to generate another Idoc(MASTER_IDOC_DISTRIBUTE is used inside).
The problem is, I am able to create the first Idoc using this ABAP Port, and in the status, the first Idoc reached 03 with a message that this Idoc number reached the Zfunction module(which is assigned to port). But I'm unable to see the second Idoc generated. Even I am not sure whether this second Idoc generated or not.
Can you please explain how this ABAP Port type behaves, how to get this function module (which is assigned to port) into debugging mode and help me to solve this.
Regards
Sunil
2008 Aug 08 7:01 AM
Hi,
Here your query is not clear, If you wnat to debugg outbound idoc simply put breakpoint in your program or in the MASTER_IDOC_DISTRIBUTE fucntion module and execute your program then you can able to debug.
Thanks and regards,
radha
Edited by: radha konjeti on Aug 8, 2008 8:36 AM
2008 Aug 08 5:47 PM
Hello Radha,
Thankyou very much for your reply.
Even though we keep a break point inside the Function Module it will not come into debugging mode. It needs a different procedure.
I will explain again what my requirement is.
We have a port defined as ABAP Port (Not tRFC and not File Port ). While creating this ABAP Port it never asks for RFC destination, but it asks for a Function Module. So we have given that function module also. ( Basically this Function module creates Idocs using MASTER_IDOC_DISTRIBUTE afetr the original Idoc is created and sent to this port. )
So Initially we have generated one Idoc thru shipment which is sent to this ABAP Port. Immediately on reaching this port we got a message that this first Idoc reached this ABAP port and reached the Function Module. But we dont see any new Idocs created using this function module.
We used this Function module in a zprogram and created Idocs which means that the code in FM is working perfectly.
Now the problem is we are not sure whether the firstly created IDoc (on reaching the port) is triggering this Function module or not. We have checked WE02 if any new Idocs created after the initially created Idoc. But we found nothing. The one we created is the latest.
So can anybody explain how this function module (mandatory to give while creating ABAP port) gets triggered? And how can we get this FM in to debugging mode. Is there any link missing out there while defining ABAP port? Please explain.
Thanks you
Best Regards
Sunil
2008 Aug 15 10:11 PM
Hi,
The communication to the ABAP Port is via an RFC. Thus you would not see the IDOC in debug mode in the FM.
You need to collect the 1st IDOC, and process them via BD37.
Check the attributes of the FM, it should be remote enabled. See if you have any RFCs in error.
Check if you have authorization to trigger the RFCs.
Hope this helps.
Aryesh
2008 Aug 18 4:18 PM
HI....
We had similar problem recently, check the "Table" parameters of you Fm attached to the ABAP Port.
It Should contain "I_EDIDC" and/or "I_EDIDD".
Hope this helps.
Aryesh
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |