Error in IDOC

[Former Member]

Hi experts,

How do we rectify the errors in IDOC once the process of configuration is over ( in case of outbound IDOC )

thanx inadvance.

Regards,

Priya.

[varma_narayana]

Hi..

We can Use the Tcode WE19 to Correct the Errors in IDOC data and Reprocess it.

But it will generate a new IDOC.

<b>reward if Helpful</b>

[Former Member]

Hi Narayana,

thanx for ur answer,so in this case we need to generate new IDOC again??

Regards,

Priya.

[Former Member]

in we05 check the statuses of u r idoc it will clearlygive the staus information ...and where u r idoc got failed ......

go to we47 and check for which status number what is the error ......

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.

reward points if helpful...

Message was edited by:

raam

Message was edited by:

raam

[Former Member]

Hi Ram,

I'd not understand the complex process u've explained......pls be bit simple and easy to understand if possible.

Regards,

Leena.

[Former Member]

How to reprocess an Idoc:

1. Go to transaction BD87

2. Enter Idoc number, and check that the dates are correct

3. Click the Execute button or press F8

4. To reprocess, select the Idoc status in the "IDOC in inbound processing" tree.

5. Click the Process button

6. The following screen will give the status of the IDOC and wheter it processed sucessfully

How to flag an Idoc to be deleted:

1. Go to transaction BD87

2. Enter Idoc number, and check that the dates are correct

3. Click the Execute button or press F8

4. To delete, select the Idoc status in the tree and click EDIT -> RESTRICT AND PROCESS

5. Click the Execute button

6. Un-check the Bkgd Processing checkbox.

7. Click the Execute button

8. Click the Delete Flag button

regards,

srinivas

[Former Member]

Hi,

Go through this

BD87 Status Monitor. Idocs can be selected base on number of criteria and there

processing status can be seen in detail.

WE20 Partner Profile

Here we create partner profile for each and every partner from / to which

the messages will be exchanged.There are 6 types of PF generally only

profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.

We specify the partner number and partner type and the agent and

the agent type responsible for handling of errors .

For every message send to the partner we have a outbound record and for

evry message coming from the partner we have the inbound record .

We specify the message in the otbound/inbound records ,double

clicking will take us to the detailed screen where the IDOC Type ,Port

and whether the IDCO will be immediatelt processed or collected are

mentioned.

Thanks

Naveen khan

[Former Member]

Hi Naveen ,

Is this the process to rectify the error. I just want to know,cos i cant get confused with different answers. anyway thanx for ur effort.

Regards,

Priya.

[varma_narayana]

Hi Priya..

If you specify which Error you are getting and is it in Inbound or Outbound..Then i can give u some more info...

regards,

Varma

[Former Member]

Hi Varma,

its an Outbound IDOC. And the error is like data not uploaded completely.

Regards,

priya.

[varma_narayana]

Hi..

Check the Details of the error by displaying the IDOC in Tcode WE05.

See the Data records of the Various segments and try to find which data is not updated in IDOC.

Let me know the result..

regards.

[Former Member]

thanx a lot varma for both ur time and interest. i'll defenitely try this and let u know.

Regards,

priya.

[Former Member]

ok thanx for reminding one point in ur description.........