IDocs misteriousely disapearing

[Former Member]

Hello all

We have a problem with our CUA/IDocs system.

• When creating/changing a user, an IDoc is created and can be found in BD87, with status 03.
• In Tx. BDM2, we have thousands of IDocs with status "Not transferred yet" and when we drill down, there's no IDoc number in the target system.
• In Tx. BDM5, all checks are Green.
• RFC connections are secured and functional and passed authorization checks both directions.
• In both systems, all assigned ports (WE21) are pointing to correct RFC connections.
• All steps in OSS note 333441 were implemented
• In TARGET system, no IDoc can be found.
• SM58 and SMQS are clean in both systems
  

Any ideas?

Regards,

Ami.

[POV8FE · Accepted solution]

Hi,

perhaps you can check in Tables EDIDC and EDID4 if there are any entries.

Would be a first check to be shure IDOC's have been received by the system.

Bye, Volker

[Former Member · Accepted solution]

Hi,

No evidence for those IDocs in either EDIDC nor EDID4

[Former Member]

Hi all,

Problem solved.

One of our ABAP'ers activated some FM, called SIDOC001.

This caused header data to be removed from IDocs.

Thank you TP for your assistance.

Cheers,

Ami.

[thanga_prakash]

Hello Ami,

You are always welcome.

I learned many things while analyzing on your issue.

It's great to know many things which I was not aware about IDOC's.

Learning new things is always good.

Cheers.

Ami

[Former Member]

Found another thing: IDocs DO create an entry in EDIDC and EDID4, but with no header data.

EDIDC contains only idoc number, date and time of creation but nothing else (see attached screenshots).

Where can we see the relevant queues?

Thanks.

[Former Member]

This message was moderated.

[thanga_prakash]

Hello Ami,

Check for the outbound idocs created in your system in transaction WE05.

What is the status of the IDOC's ?

Regards,

TP

[Former Member]

Hi,

some are 12 and some are 03...

[thanga_prakash]

Hi,

Check the status records of the IDOC's and drill down the status 03 to find the message details.

What does the message say, Is it "

IDoc sent to SAP system or external program" ?

Is there any TID number? If yes give that TID number to PI consultant to check whether the IDOC with this TID number is transmitted.

You can find the TID number of the IDOC's in EDIDS table.

Regards,

Tp

[thanga_prakash]

Hello Ami,

Did you check the queues as posted in the earlier message?

If there is any IDOC's stuck in the queue try to resolve by reprocessing.

Regards,

Tp

[Former Member]

TP,

for status 03 it says "IDoc sent to SAP system or external program"

for status 12 it says "Dispatch OK"

[thanga_prakash]

Please drill down from 03 and check the status.

Is it like this??

Then double click on the status, you will get a pop up, in the pop up you will have a TID number of the IDOC.

Regards,

Tp

[thanga_prakash]

Hello Ami,

Check the outbound queue of your source system with transaction WEOUTQUEUE

and inbound queue of the destination system with transaction WEINQUEUE.

There might be chances that the idocs are stuck in the queue.

Refer to the below links for the same.

http://help.sap.com/saphelp_nw70/helpdata/en/9f/9efe3e432fd861e10000000a114084/content.htm

Monitor IDoc Inbound Queue - IDoc Interface/ALE - SAP Library

Regards,

Tp

[thanga_prakash]

Hello Volker,

Check if there is any archiving or deletion program running in the system in background.

RSEXARCA - Program for archiving the IDOC's

RSEXARCD - Reads the archive and deletes the IDocs from database

Check the below link on how it is done.

http://wiki.scn.sap.com/wiki/display/ABAPConn/Deleting+and+reorganizing+IDocs+with+SARA

Regards,

Tp

[Former Member]

Hi,

No archiving jobs in the system

[thanga_prakash]

Hello Ami,

Try by running the below programs in SE38.

RBDCUS47

RBDOUTPU

It might help you.

Regards,

Tp

[Former Member]

Hi,

No, nothing there.

We do see the IDoc in BD87, with status 03, bu nothing in the target system...

We also debugged FM ALE_IDOCS_CREATE in the source system and it looks fine.

It looks like IDocs are disappearing into some black hole

Thank you,

Ami.