Debug the Outbound IDoc

Hi,
I have a outbound IDoc.
I would like to reprocess the same and test the FM.
I am going through the Tcode :WE19.
put the IDOC : XXX in the exisiting IDoc field. Execute.
I get to see the IDoc structure and the data.Then i click on the "standard outbound processing".
I would like to get into the FM and debug it.
But once i press "standard outbound processing".
It is giving a pop up which says "start outbound processing of file immediately"
No of IDoc's to be generated.
Receiver port
Port type
output file
etc.
But i would like to get into the debug mode.
Pls advise.

Set ur Break point at your code
now come to VA02 Transaction and use order 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 : V1
Object key - order Number ( 10 digit)
Output type - BA00( SAP Standard)
Transmission medium = 6(EDI) ,A(ALE)
Now it will stop at your code.
Reward Points if it is helpful
Thanks
Seshu
Message was edited by:
Seshu Maramreddy
Message was edited by:
Seshu Maramreddy

Similar Messages

How to Debug the Outbound IDOC

Dear SDN Members,
How to debug the outbound idoc please.
Thanks in advance
Yerukala Setty

Hi,
IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc in transaction BD87 you can put a breakpoint in the function module and it will stop there.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).
Thanks,
Asit Purbey.

How to find the Program that triggered the outbound idoc

Hi,
I need to find the program that triggers a particular Outbound IDoc.
I have the IDoc number/segment/message type.
We need to Debug the Outbound IDoc but we do not know from where the IDoc got triggered.
Is there a way we can find which program triggered it?
Thanks!

Hi Suresh,
Go to tcode WE20, select ur partner profile type, which configured in output type for EDI documents.
On right side, double click on the Message type in outbound parameters.
go to message control Tab, double click on process code variable to see FM triggers for the IDOC.
same as for Inbound also.
Regards
Syed A

How to debugg the outbound idoc

Hi all,
I am adding one segment standard Invoic02 outbound idoc.
Executing invoice number ,idoc automaticall y trigger and populate the data.
1)problem is my new adding segment is not populated idoc level.
2)I am testind idoc (WE19) showing a 02 error.
3) How to debugg the outbound idoc.
Thanks
Sreddy

Take a look at your outbound processing code (transaction WE41). When you double click on the entry you are using you can find the function module which is used to process the IDOC. Just set a breakpoint at the beginning of that function module and you can debug the creation of your outbound IDOC.
Hope that helps,
Michael

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Where to put break point when debugging the inbound IDOC processing

Hi, Dear Experts,
If IDOC has error and want to debug, which program or function module to put break point when debugging the inbound IDOC processing
Thank you so much!
Helen

It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

How to find the outbound idoc function module?(Urgent)

Dear All,
How to identify the outbound function module if there is process code assigned to message type.
For partner profile the mesasge type is assigned and idoc type .This is the only information maintained .
Now my question is how to identify the fucntion module which is getting trigger in the system is there any data maintained in the standard table or any t-code .
Points will be rewarded for right answers.
Thank You.
Regards,
Ravi Ganji

Hi,
If u know the message and basictype then we can know the process code for that message type in transaction code WE64.
if we know process codes then we can know the function modules in transaction codes WE41(Outbound process code) and WE42(Inbound process code).
Each process code is attached with a FM...
Reward if helpful
Regards,
Nagaraj

Debugging the outbound queue

Hi,
I have an outbound queue failed with the error 'SYSFAIL' and the error text ,"for object, number range interval doesnot exist" in CRM system. Please help me as i would like to debug the queue. As i am new to CRM middleware, i would like to know the process of debugging it.

Hi,
Can you please check the very helpful note 656823 for interface debugging.
Please see as well link
http://wiki.sdn.sap.com/wiki/x/JovwDg
Please check as well in t-code SNRO if the number range is set properly in both system ECC and CRM.
Best regards
Christophe

Regarding the Outbound IDOC process

Hi Experts,
Please answers the following questions which i have some doubts in Outbound Process.
1) Which program is resposible to fill the segments of IDOC(Std IDoc) in case of Outbound IDOC Process with message control , Is it FM in Process code or any other FM based on message type( Std Msg)?.
2) Where we need to code or search the exit in Case of extension of basic IDOC type with and without message control?
3)Which prog is responsible to fill the IDOC in case of outbound process without message control but using std basic IDOC.
Regards,
Kali Pramod

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

To send the outbound IDOC DEBMDM from R/3

Hi,
I have created an extension for DEBMDM06 as ZDEBMDM06.
Please sent me the outbound FM and the process code that is used for the above type.
When i checked with the system i got the peocess code DEBM that is relevant for DEBMAS type.
And also the transaction that is used for creating the IDOCS, because BD12 is relvant for DEBMAS idoc type.
please confirm me whether the tcode MDM_CLNT_EXTR is used for sending the IDOC from R/3.
Above mentioned is an outbound IDOC that will be sent from R/3. please suggest me some solution for solving this issue.
Thanks in advance.
Praba

Hello,
As you rightly said, you can use the Transaction BD12 to Send Customer Master Data.
However, if you have a specific requirement to add some Extended Segment / Fields, you can go for a Custom Program / Report in which you can extract all the Customer Master Data required along with the Extended Segment Fields and send it through MASTER_IDOC_DISTRIBUTE. This program can be scheduled for Background Job as and when you want.
Thanks and Regards,
Venkat Phani Prasad Konduri

OUTBOUND IDOC DEBUGGING

I have Output type defined for the application V3
i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
This output type is defined for edi processing.
Now the problem is when invoice is created and this
outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code and find the function module that is running in the background for collection of data of invoice and
filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
Help me out i will be waiting for the response.

Hi,
You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
Let me know if you need further help.
Thanks,
Eric

How to debug outbound Idoc function module for invoice

I have to debug the outbound IDOC function module and UserExit for invoice message type INVOIC, process code SD09, function module is IDOC_OUTPUT_INVOIC and user exit for the function module LVEDF001.
I tried putting the break point in function module IDOC_OUTPUT_INVOIC and recreate the IDOC using WE19 but it creates the idoc but does not stop at the break point. I have also tried generation of idoc through VF02. It again creates the idoc but does not stop at the function module.
Please let me know if I am missing any thing and not doing it right.
Appreciate your help.
Rohit

Hi Ali,
I faced the same problem. Thing is the break point is not getting triggered when i ran tha IDOC through WE19.
What i have done is i created a project for my exit in CMOD and kept some junk code in the exit and executed it through BD21. Then the Break point got triggered. See if it works.
Regards,
Uday S.

Debugging outbound idocs

Hi,
Can anyone suggest me how to debug the outbound idocs like in case we19 for inbound.
i am creating an idoc for ORDERS message type with process code ME10. i need to debug to know if data is populating in segments correctly.
shylesh

Hi Sailesh,
You can set break point at FM <b>IDOC_OUTPUT_ORDERS</b> and go through the code step by step.
Also you can check customer function for any custom enhancement related to populating/deleting IDoc segment within the above FM.
Hope this will help.
Regards,
Ferry Lianto

Degugging Inbound and Outbound idocs

Hi friends,
Can any one help me in debugging Inbound and outbound IDocs?
1.I found the inbound FM using Tcode we19,clicked the inbound FM button and called it in the debugging mode.
While debugging the Inbound FM iam nt able to figure out the actual problem.Is there any way to reach out the exact problem?
2.How to find out the outbound Idoc FM and debug it?
Your help is appreciated.
Thanks in Advance.

Hi,
Inbound or Outbound IDoc processing FM can be found iin partner profiles(WE20).
for Outbound: WE20 --> choose partner type --> Outbound parameters --> choose message type --> Message control Tab --> Double click on Process code to get the FM assigned.
for inbound: WE20 --> choose partner type --> Inbound parameters --> choose message type --> inbound options --> Double click on Process code to get the FM assigned.
For debugging, use Tcode WE15 for outbound, But before that u need to set the output type dispatch time as 1 (Send with periodically scheduled Job). Go to Output type assignment screen --> assign the output type --> choose further processing --> Set Dispatch time as 1 --> Save.
Note: U need to keep the break point in the Outbound FM or exit if any before going to WE15 to debug from that point.
Hope it helps,
SG.

Test Outbound Idoc type DELVRY01

Hi all,
We've a client who is presently using idoc type DESADV/DELVRY01 for sending Orders outbound. They want to modify the existing output data, which I've deduced I can do by using an existing user exit (.
But when I use WE19 to test the outbound process, ALE is not stopping at my break-point. Can any tell if I'm doing anything wrong with my testing process? How can I get the outbound idoc to stop?
Points rewarded for useful answers.
Cheers,
Steve

Hello Stephen,
WE19 is for testing for Inbound IDOC..
If you want to test Outbound IDOC ,you need to create delivery or change the delivery in VL01N or VL02N Transaction.
Here you need to give correct output type like Delivery transaction output would be LD00 -> you can find out Delivery Output type in NACE Transaction.
GOTO NACE -> select V2 Application -> Click on output type -> here you are able to see all output types
if you don't find output type then contact Functional guy.
once you create delivery it will create IDOC ,you can IDOC Status in WE02 Transaction.
if you want to debug IDOC then follow below Steps :
goto delivery transaction -> when you create delivery ,please modify output type -> extras -> header -> output type
here see the further data -> select peridocally scheduling.
now come to RSNAST00 Program
enter delivery number as object number
Application -> V2
Output type -> enter delivery output type
Medium - A (ALE) ,6(EDI)
Now you are able to work on debugging
Thanks
Seshu

Debug the Outbound IDoc

Similar Messages

Maybe you are looking for