How to debug IDoc and waht about WE19

hi experts how to debug idocs waht is we19 and perpose

We19 is Testing Inbound IDOC and you can debugging from we19 Transaction
Outbound IDOC Debugging :
Example of Invoice :
Set ur Break point at your code
now come to VF02 Transaction and use invoice number.
click on enter
GOTO->HEADER->OUTPUT
Give the output type and print medium should be 6(EDI) or A( ALE)
Click on Further data and select->select send with periodically scheduled job and save it.
Now Come to SE38 and use RSNAST00
Output Application : V3
Object key - Invoice Number ( 10 digit)
Output type - RD00( SAP Standard)
Transmission medium = 6(EDI) ,A(ALE)
Now it will stop at your code.
Reward Points if it is helpful
Thanks
Seshu

Similar Messages

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

How to debug serlvet and EJB using IDE

Anybody knows how to debug Servlet and EJB through standard IDE, like
Symantec or VisualAge? Does the attach to process works?
Thanks.

1) Download and install the jpda package from sun (Java Platform Debugger
Architecture, it contains the jdwp.dll, this has to be in your %PATH%
variable).
2) Start weblogic with something like this:
%JDK_HOME%\bin\java -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y
,address=8000 -ms64m -mx64m -Xbootclasspath:%JAVACLASSPATH% -classpath
%WEBLOGICHOME%\classes\boot -Dweblogic.class.path=%WEBLOGICCLASSPATH% -Dwebl
ogic.home=%WEBLOGICHOME% -Dweblogic.system.name=MyServer -Djava.security.man
ager -Djava.security.policy==%WEBLOGICHOME%\weblogic.policy weblogic.Server
3) address is the portnumber (in this example 8000) for the remote debugger.
Attach to the VM with arguments -host <hostname> -port <address>
-Falk
"test" <[email protected]> wrote in message
news:8frkq6$ru5$[email protected]..
Anybody knows how to debug Servlet and EJB through standard IDE, like
Symantec or VisualAge? Does the attach to process works?
Thanks.

How to Debug IDOC posting

Hi,
Could anyone please advise how to debug an IDOC posting. I am new to ABAP.
regards,
Munavar Basha A.K.

Hi,
1)Use tcode we19 , enter your idoc no and click on the inbound function module push button then check call in debugging mode to debug.
or
1. Go to BD87
2. make a right click at the IDoc and choose restrict and process.
3. delete the check at the bottom(Background Processing)
4. Go ahead
5. edit -> process -> Foreground at Error
Thanks Hope this will be Helpful
Thanks
Kalyan

Hi, how to debug IDOC using se37.

Hello experts:
       Thank you in advance for all your replies.
       I tried to debug the function IDOC_OUTPUT_ORDCHG like the following in our company(because the structure of IDOCS this morning are totally wrong):
      1   I set some breakpoints at IDOC_OUTPUT_ORDCHG .
      2 modify a PO with me22n and an IDOC was created because the MESSAGE(on the menu bar) showed that an IDOC is created .
      3 the program didn't stop at where I set the breakpoint.
      Is there anything wrong how I tried to debug?
       couldn't thank you more.
Best regards.
Frank

Hi,
To debug IDOC
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html
Regards,
Jagadish

How to create idoc and send it frm one sap to another sap

hi,
can anyone tell me the complete procedure of creating the idoc and sending it to another sap r/3
how to create rfc destination, partner profiles, port and outbound parameter and inbound parameter
thanks

Hi Azhar,
Go through the following Links
IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Go through the following Steps for Creating IDoc Via ALE
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 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V 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
Regards
Sreeni

How to debug qRFC and Trfc.

Hi All,
how to debugging asynchronyos finction module and Transactional function module when call in Background?
Regards,
Anuj Jain

Hi Anuj,
In transaction SM50 (process overview), you can select a background process and choose Program/Mode -> Program -> Debugging from the menu.
Debugging TRFC
1. Go to the program 'ZREPORT' and go to the CALL FUNCTION 'ZFUNCTIOn' IN BACKGROUND TASK .
2. Keep breakpoint in 'ZREPORT' just before the CALL FUNCTION start .
3. when you reach the breakpoint, Go to menu -- > Settings-> Display/Change debugger settings-> select the flag "tRFC (In Background Task): Block Sending".
4. Execute SM58, Select the background task, and choose menu --->edit -
>debug LUW, the "background task" will start and the debugger will stop at the FM.
Let me know If any further queries
Edited by: Raj on Jul 27, 2010 1:07 PM

How to Use IDOC and ALE in SAP?

Hi anybody,
I want Use Idoc and ALE in sap ABAP. What is inbound and outbout process of IDOC?
Please give me sample code for Idoc . and Sample code for ALE.
anybody Please tell me.
Thanks
Regards,
S.Muthu.
IT Dept.

hi,
Follow the link for step by step ALE/IDOC tutorials.
http://www.sapmaterial.com/idoc_sample.html
http://www.****************/Tutorials/ALE/ALEMainPage.htm
An IDoc is not a process.
The term IDoc stands for intermediate document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. An IDoc is created as a result of executing an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDoc serves as input to create an application document.
IDocs are stored in the database.
In the SAP system, they are stored in database tables. Several utilities are available to display the information contained in an IDoc and present it in different ways. For details, refer to Chapter 11, "Monitoring the Interface."
Every IDoc has a unique number.
When an IDoc is generated in the system, a unique number is assigned to it. This number is unique within a client.
IDocs are independent of the sending and receiving systems. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.
IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. The size and format of data elements in an IDoc type are derived from these standards wherever applicable. For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters. If there is a conflict in data size between standards, the one with greater length is adopted. This approach ensures compatibility with most standards.
IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. For example, the ORDERS01 IDoc is used by the Purchasing module to send a purchase order, and is also used by the Sales and Distribution module to accept a sales order. Using this technique avoids creating redundant IDoc types for the same information.
IDocs can be viewed in a text editor and do not contain any binary data. Data is stored in character format. When transferred to the operating system, an IDoc is stored in a file in text format and can be viewed using a regular text editor. However, the contents make sense only if you understand the structure and format of the data in that IDoc. In the Appendix, "FAQs, User Exits, and Miscellaneous Resources," you will find an example of an IDoc file.
Hope this helps, Do reward.
Edited by: Runal Singh on Mar 5, 2008 6:09 PM

How to tranfer IDOC and BAPI through LSMW

Hi friends,
I need documents regarding processing of IDOC and BAPi through LSMW,
Thanks In advance,
Regards,
charan

Hi
LSMW-BAPI
Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed
It is given in screen shot.
http://www.****************
LSMW-IDOC
see this and do accordingly
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
Go through the steps
Hi please go through the following steps for IDOC method
Step 1. Run the transaction ( /nlsmw ) you will reach to the screen
Here you have to specify
Project : 060_BUS_TRANS
Subproject : SERVICE_TICKET
Object : SRV_TICKET_ZSVT
click on the execute button .you will reach the screen :
The screen shows the 15 steps to Run the lsmw
Step 2) select the first step ( Maintain object attributes) and click the execute button.After clicking on the execute button you will reach at. the screen
Here you have to specify ( MEssage type and basic type)
click on the BACK button
Step 3) select the 2nd step ( Maintain source structures) and click the execute button
Here you have to specify the source structures.
Step 4) Select the 3rd step ( Maintain source fields) and click on the execute button :
Here you have to specify the fields present in the source structure
Step 5) select the 4th step ( Maintain structure relationship ) and click on the execute button :
Here you have to specify relationship between source and target structures
Step 6) select the 5th step ( Maintain field mapping ) and click on the exécute button :
Here you have to map the fields between source and target structure. Also you have to apply conversion rules here if any
STEP 7) select the 6th step and click on the exécute button
Here you can define any fixed value or user define routines
Step 8) select the 7th step ( Specify files) and click on the exécute button :
At This screen we have to specify the files for This we should be in change mode .So please click on the button shown in the above screen. After clicking on This button you will be in change mode and will be able to specify the files :
Step 9) select the 8th step ( Assign files) and click on the exécute button
For assigning files yoy should be in change mode do the same thing click on the button as shown in the above screen :
Then assign the files to different structures.
Step 10 ) select the 9th step ( Read Data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Again click on the exécute button . After clicking on the exécute button you will reach to the next screen
Here you will see data is read.
Step 11) select the 10th step ( Display read data) and click on the exécute button :
Here you can see your test data present in test files assign to source sturcture
Step 12 ) select the 11th step ( Convert data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Click on the exécute button as shown on the : After click on the exécute button you will reach to the next screen
Data is converted
Step 12th ( Display converted data is same as Display read data )
Step 13 ) select the 13th step ( Start idoc generation) and click on the exécute
button :
At this step Idoc is generated using converted data
Step 14) select the 14th step ( Start idoc processing ) and click on the exécute button :
After clicking on the exécute button you will reach to the screen :
And then click on the exécute button : After clicking on the exécute button you will reach to the final processive screen
If data is processed correctly you will see ( 53 Status message with green sign)
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
Reward points for useful Answers
Regards
Anji

N97 2.1 fw and waht about N97 mini new fw

According to Nokia N97 fw update 2.1 will be releale next 1st February, and what about N97 mini, any informations about new fw?
Nokia N8 / N9 / Lumia 920 White

I'd be interested in knowing this too. If they could fix the showstopper defects (that require a battery pull or hard reset) then I'd be happy to keep the device - as it is I can't really rely on it.

How to debug idoc?

I want to find the additional custom developments done to send a sales order idoc via i-003 and not any other interface.can u suggest how to find it easily by debugging?

Hi,
check this link.
Link:[https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_all&query=howtodebug+idoc&adv=false&sortby=cm_rnd_rankvalue]
hope u'll get some idea.
Regards,
Sneha.

How to Debug Idoc Adapter from XI to R/3

Hi,
Can any one please help in debugging the Idoc adapter from XI to R/3.
Here is the my problem - XI to R/3 idocs have been created correctly but the service relation ship is created incorrectly.
i.e. When XI creates inbound idoc into R/3, it is also linking some other non relevant idoc which is created 2 years back as a outbound idoc reference to that original idoc.
And this outbound idoc is coming to XI and the same can be seen in IDX5(Table - IDXRCVPOR) for that message.
I tried to see various parameters on idoc_inbound_asynchronus FM and when I execute this FM in R/3, idocs are being created correctly and service relation ship is also correct.
I tried to debug the RFC by using dialog user in the idoc adapter - IDX_OUTBOUND_XMB. For this we forced to fail the message at the adapter level and then manually restarted in SXI_MONI so that it will stop in debug mode in IDX_OUTBOUND_XMB.. But it didn't.
Can any one help on this ?
Thanks in Advance..
Nagarjuna

If my understanding is correct, your inbound function module processing the IDoc is triggering another IDoc to be sent back to PI? If so, then have you checked the distribution model? If you want to supress it you can try removing it as the outbound Idoc for the logical system in we20 (Partner Profiles)?

LSMW - How to modify IDOC and start again conversion

Hi,
I'm using LSMW with BAPI-IDOC technique. I'm trying to find out how to elaborate again records that have been discarded in the first conversion process because the records presented errors in some fields' values.
Can anybody help me?
I do not see a way inside LSMW that can allow me to modify wrong informations in the idoc generated.
Create IDoc Overview - Allows to see but not to modify
Start IDoc Follow-Up - Allows to restart import step, but before I should need to correct what is wrong!
Thanks a lot,
Gabriele
Edited by: Raistlin82 on Oct 13, 2009 12:15 PM

Hi
In LSMW you can't modify the data inside.If errors occur in the data while uploading.You need correct that in file.
And process the file from step "Read data ".
Regards,
Raghu

How to trigger automatically an IDOC and RFC from SAP R/3 system?

Hi ,
lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger on timely basis(schedules)
1)standard IDOCs and BAPIs?
2)customized Idocs and Customized Bapis?
3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
please explain ,
thank you very much for your help.
regards,
Babu

sorryfor the late reply, I was busy with my work.thank you for your posts.
so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
And I think we use RSNASTED if we have on recieving side right?
<b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
REPORT Z_SEND_DATA_TO_XI.
parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
<<your other variable declaration and ABAP Code here>>
call function 'ZXI_SEND_DATA'
in background task
destination dest
exporting
Name = John
City = Smith. (The values to pass to XI)
commit work.
<<Any Write statements or sy-subrc statements here>>
6) Save and Activate your ABAP program.
6) After all these steps, execute your ABAP Program to send the data to file via XI.

How to debug RFC connection?

I have got an error when SAP execute RfcOpenEx.
How to debug RfcOpenEx and setup breakpoint?
Thanks for your help
Marty

Hi,
in fact the conection from SAP to the destination works using SM59. but the system reply with a connection using RfcOpenEx but this function fails because there is a mixup with the parameters maybe a wrong type.
I will try to debug from the tcode COOPC1 when I start a subscription.
Thanks
Marty

How to debug IDoc and waht about WE19

Similar Messages

Maybe you are looking for