Debug IDoc ?

All,
I have an IDoc for message type MBGMCR. That we are sending from Warehouse Management (WM) Box to our Finance Box ( Both are SAP instances) . But IDoc getting failed in Target system (Finance Box) with status 53.( Error saying authorisation not found for accounts posting).
Then i reprocess the IDoc from BD87 and it got sucessful with 51.
I know this is because of RFC user authorisation. Then i have given SAP_ALL to RFC user and try to send IDoc from WM box to FIN box. Still my IDoc got failed.
Now my question is how can debug the IDoc while at the time sending IDoc from WM to FIN box.
I have tried SM50 RFC debuging option , but If i opened the SM50 debuging IDoc getting generated in 64 status.
and also tried to search the code for message class & message number in error occured, and put break-point and run from WE19, system doesn't stop at break-point.
PS Please don't suggest to use WE19, BD87 for debugging.( If i use these IDoc getting created sucessfully)
a®

Issue is with RFC user type. Problem solved
a®

Similar Messages

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 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

Debugging IDOCs

Hello -
How do I debug an IDOC ? The transaction codes I know for processing IDOCs are:
WE02, BD87 and WE19
I am trying to debug an IDOC which is creating a credit memo request in VA01.
Thank you,
LP

LCPicker,
There is an easy way, go to WE19, put the Idoc number and hit F8 then choose for e.g inbound function module, set the function(you can find it at WE64), checked "CAll in debug mode" and if you want check foreground mode.
regards,
Alexandre

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)?

F110S - debugging - Idoc basic type PEXR2002

Hi,
i'm trying to debug F110S and its not stopping in FEDI0003 routines. am i missing something.
i have to populate bank details in this Idoc (basic type pexr2002 and message type PAYEXT)
please let me know.
Thanks.
Edited by: vij k on Aug 5, 2009 9:51 PM

figured it out. 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

Debuging IDOCS

Hi,
Im making a test between two differents SAP systems by using CREMAS IDOCS.
To do that, I modified the code postal by XK02 and then, I created a outbound idoc by BD14 transaction (in source system)...
Where do I could put a break point in order to debug how the DESTINATION system receive and process the new idoc?
Thanks in advance for your help
Leandro.

Hi Amit Khare ,
Thanks for your quick answer.
I knew that WE19 can be use to test inbound idocs, but in this case is different because I have access to both systems: Source System and Target System.
Then, I want to make a complete test.
To do that, I create an idoc in Source system and I want to debug the receive idoc in target system.
As far as I understand, I get the 2 FM used to process inbound IDOCS type CREMAS:
IDOC_INPUT_CREDITOR
IDOC_INPUT_CREDITOR_MDM
And I set a break point in them. But when I send the idoc in the source system. The debug mode never starts...
Do you have any idea about that?
Thanks again,
Leandro

Debugging Idoc Acc_document02

Hi Gurus ,
I want to debug the idoc Acc_document02 and message type is Acc_document in Inbound function module in we19 .
In the dialogue box i click the function module search help i get two Bapi , Bapi_idoc_input1 and Bapi_idoc_inputp. which one should i select and whats the difference between these two Bapi.
Thanks,
Lakshmi Rajkumar.

Hi Lakshmi,
Please try to follow the below process you can easily find out which FM is the correct one to debugg the inbound idoc.
Please try to check the partner profile in WE20 for the inbound idoc which you want to debug.
To know the partner profile details give the idoc number in WE02 execute. Right side of the display idoc you can see Technical Short info tab there you will get the Partner number and partner type.
Go to WE20 check the partner profile details. Right side you can see the outbound parameters , and inbound parameter. Go to inbouund parameters tab double click on the message type Acc_document there you can see Process code under Inbound Options tab. Again double click on the process code it will take you to the FM which is being used for the message type Acc_document. That FM you can utilize for debugging inbound idoc debugging.
I hope this will helpful.
Regards,
Mufee.

Debugging of idocs

hi,
can anyone tell me how to debug idocs step by step with tcodes.
regards,
srinu.

Hi srinu
If IDoc is in status 51, it means it was properly delivered to R/3. So you can now set a break-point in the respective IDoc handling function and reprocess the IDoc with BD87 (or report: RBDINPUT). Then debug the IDoc function and find where the error message is issued.
If you un-check the option field "background processing," you will get more options and in the menu there is a selection that allows you to throw the function into batch input dialog mode. If you choose "process foreground from error," it will stop on the screen where the error happens. Then you will know which field is not supplied properly by XI.
IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc with BD87 you can have a breakpoint in the function and it will stop. For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
Rewards if helpfull
Regards
Pavan

I looking for a transaction for debug the IDOCS

Hello friends,
I looking for a transaction that allowed me to debug the IDOC´s when the direction is only 1 (Outbound), for ex. for IDOC´s has direction 2 (Inbound) I used the WE19 transaction, and to choose the "Inbound Function Module" button and I take the "Call in debug mode" checkbox,
Can you tell me if exist another program for this?
Thanks in advance,
David

Hi,
IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc with BD87 you can have a breakpoint in the function and it will stop. For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
For your knowledge [reference1|Re: How to debug Idoc; [reference2|Outbound IDoc debug;.
May it helps you.
Regards,
DS.

Can we debug a idoc?

can we debug a idoc?

Hi,
You can debug "idoc processing" in the transaction WE19.
Provide the appropriate inbound function module and execute in debugging mode..
1>Provide idoc number
2>Execute
3>For inbound
Select the option inbound function module
provide inbound function module
select call in debugging mode
For Outbound
select the option Standard outbound processing
This process you can perform for the failed idocs..to change any particular data to successfully process them
Thank you

Problem in processing incoming IDOC

Hi All,
I have a problem while processing Incoming IDOC in the system.
While I try to process and FI IDOC (without purchase order) in the system, by giving the appropriate GL account and cost centre where the document should get posted to (in transaction WE19), I find that the system creates the IDOC successfully with status 53. However, it creates a parked document in the system for the vendor.
When I try to post the document through transaction FBV0, the system asks for a cost centre. Can you please clarify, why the system is asking for a cost object though it is given in WE19 transaction. Ideally while processing the IDOC the system should post the document directly as it has all the relevant details in the IDOC right?
(Just for info, I have given the GL account details in segment E1EDP19 with qualifier 002 and the cost centre in segment E1EDP30 with qualifier 045)
Expecting your help in this regard.
Regards
Nagarajan N

Hi
You can use WE19 to debug the Idoc FM.
Check this link if it is helpful:
Debugging Idocs
Regards
Neha

Outbound idoc control recorderror - REFINT field

I am trying to send orders.orders05 idoc from ecc to xi
the message that I get in we02 in ECC is
EDI: Field REFINT in control record with value 'T080902134731A ' is invalid
Does somebody knows where this field is configured ?
when I edited this idoc in we02 and erased this value the process was sucessfuly
but when I try using we19 it assigns this value automatically
thx
Shai

I dont think it is populated in SAP, rather it comes afetr outbound IDOC is sent and tstaus record is updated afterwards.
I would say debug IDOC in WE19, create a watchpoint for the field to see where it is changing values

Debug IDoc ?

Similar Messages

Maybe you are looking for