Skip to Content
avatar image
Former Member

IDOC debugging

Hi All,

How can i debugg an outbound IDOC.

Regards,

Amit.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Nov 19, 2007 at 02:30 PM

    Hi Amit,

    Go through below link

    how-to-debug-outbound-idoc-in-we19

    Reward Points if this helps,

    Satish

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 19, 2007 at 02:28 PM

    Amit,

    For outbound function module debugging you can use the following:

    1) RBDMIDOC - for master IDocs configured via change pointers.

    2) RSNASTED - for transaction IDocs with output/message control.

    3) RSEOUT00 - For IDoc whose status is "to be processed".

    Regards

    Aneesh.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 19, 2007 at 02:40 PM

    hi

    YES

    WE19 would help but worth checking the following out;

    1. There is a valid outbound partner profile for the

    combination of receiving partner (plus partner type/function0 and message

    type (plus message function and code) and test flag?

    2. The profile points to the correct port which has the correct

    RFC destination attached

    3. The RFC destination is OK, it has the correct address for

    the receiving system and (if it is trfc destination) the userid is valid

    (use SM59 then menu options for testing authorizations)

    How are you generating the idoc? - that would have a bearing on potential

    errors (e.g. control data values) and what are the errors you get?

    u can debug or test u r idoc using we19 tool also ....

    Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.

    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.

    · You generate the IDoc using .

    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.

    · To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .

    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.

    · Click on the white fields to change data in the segments.

    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.

    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.

    · The additional procedure depends on whether you want to test inbound or outbound processing.

    Outbound Test Tool: Procedure

    1. When you have completed your IDoc, choose Standard outbound. If you have chosen a valid port, the port and port type are displayed for you to check.

    2. Decide if you want to start outbound processing immediately: The IDocs will then be transferred to the port (status 03), regardless of what is in the partner profiles. If you do not configure the test indicator, the status of the IDocs remains 30 in the database, again independent of the settings in the partner profiles. You can also send several copies of your IDoc (repetition factor).

    If you want to pass the IDocs, which you stored in status 30 with the test tool in the database, on to the port, use Test: Outbound Processing from IDoc The advantage is that the settings then take effect in the partner profiles. In particular, a receiving system is also triggered when the file port is used, if that is defined in the partner profiles.

    3. Choose to start the outbound processing.

    Inbound Test Tool: Procedure

    When you have completed your IDoc, select one of the following processing options:

    Standard inbound processing:

    The IDoc is treated like an IDoc which was sent by an external system. The IDoc is first saved in the database, then the corresponding control records are compared with the inbound partner profiles and finally the business process determined using the process code is triggered (see Inbound processing).

    Inbound function module (inbound processing using ALE):

    the IDoc is first saved in the database and can then be forwarded directly to the specified function module. The function module can be run in debugging mode. If the function module calls a transaction, it can be processed in the background, foreground or in the foreground from the point at which an error is found. To do so, however, the ABAP command CALL TRANSACTION must use the import parameter INPUT_METHOD, in conjunction with MODE. Otherwise, the transaction is always processed in the background.

    Function modules called directly must have the ALE Interface (Release 3.0 onwards).

    Inbound File:

    Generate or extend a sequential inbound file: The IDoc is first saved in the database with status 68 ("error, no further processing") and then in a file. Specify the name explicitly. The system proposes a name determined from the test port of the IDoc administration. If you select Start IDoc inbound processing immediately, the file is processed immediately and then deleted if processing was successful. This mode corresponds exactly to standard IDoc inbound processing. If further processing is not started immediately, the file is kept and can be used for additional test purposes.

    You can write the test IDoc more than once in the file and thus also send them for inbound processing more than once (repetition factor).

    Choose to start inbound processing from the corresponding screen.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 19, 2007 at 02:42 PM

    WE19 is a testing tool for IDOC

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 20, 2007 at 04:10 AM

    Hi..Amit..

    To debug an Outbound IDOC:

    1. Find the Outbound FM of the respective IDOC Type and Message Type in Tcode WE57.

    Eg : For ORDERS03 idoc type it is IDOC_OUTPUT_ORDERS

    2. Open the FM in SE37 and Set the break point in the Source code .

    3. In Tcode WE19 (Idoc test tool) try to generate the sample idoc. Then it will get into debugging.

    <b>reward if Helpful.</b>

    Add comment
    10|10000 characters needed characters exceeded