Duplicate Idoc in XI

[Former Member]

Hi Friends

we are facing a issue ,please help me from getting out from this

when ever idoc created in R/3 and it has status of 01, 30 03,29,01,30,03,finally 41.when i monitored in XI IDX5 we foind the same IDOC 2 times ,can some one explain what might the reason for appearing twice in XI and this cause creation of duplicate entries in target system

can some one explain how to over come this

thanks in advance

siva

[rodrigoalejandro_pertierr]

hi, are you ussing BPM??

thanks

Rodrigo

[rodrigoalejandro_pertierr]

hi

in sender system you see 2 outbound or just one??

as matias ask you, how many entries do you have in pi tcode idx5

Thanks

Rodrigo

[Former Member]

In IDX5 you see the same "IDoc Number" value multiple times in multiple entries?

Regards,

Matias.

[Former Member]

Hi Thanks for response

In R/3 there is only one IDOC where in XI while checking in IDX5 we found two IDOCS with the same number

As i mentioned in querys the status of IDOC on R/3 side are as follows

*41* Application document created in target system

03 Data passed to port OK(IDoc sent to R/3 System or external program)

30 IDoc ready for dispatch (ALE service)(Receiver exists , No filters , No conversion , No version change)

29 Error in ALE service

03 Data passed to port OK(IDoc sent to R/3 System or external program)

30 IDoc ready for dispatch (ALE service)(Receiver found , No filters , No conversion , No version change)

01 IDoc generated

These are status that generated while transfereing the IDOC because of the status 29(ERROR IN ALE ) that might had gone twice to XI

Now how to over come this of processing multiple times to XI

Thanks in advance

[Former Member]

Did you check your occurence clause?

Kiran

[Former Member]

Hi !

Did you read:

http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm

IDoc status 29: Missing or incorrect partner profile

To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners.

For more information, see Interfaces ® External Systems ® Configure Warehouse Management ® Communication R/3 -> External System ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.

If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:

* Define the missing partner profile.

* Resend all existing IDocs, which the system has not yet been able to send.

For this error, the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user.

You trigger subsequent sending of the IDocs that contained errors from the inbox.

On subsequent transmission, the incorrect IDoc is flagged with status 31 and copied to a new IDoc, which is enhanced with data from the partner profile and transferred to the asynchronous RFC.

Note

Errors in partner profiles normally only occur in the test run.

-

-

---

Check WE20.

Regards,

Matias.

[Former Member]

Hi !

Also check this out, I think it's useful...

http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

Regards,

Matias.

[Former Member]

Hi !

Could you please give more info about the complete scenario?

Thanks.

Regards,

Matias.