Idocs neding in 64 status and not processed further

[Former Member]

Hi

We have inbound idocs of FIDCC2 message type, which are set to be triggered immediately. However we have noticed that sometimes (not always) these idocs are in 64 status and are not processed further. We have to manually reprocess them.

What could be the problem? Where should we start investigating?

Any help would be appreciated.

Thanks

Mick

[GauthamV]

Check your settings in partner profile whether triggering immediately or by background program,

also they might have used collect idoc method.

Run RBDAPP01 program to transfer those idocs to status 53.

[Former Member]

thanks Gautham.

But the idocs settings in partner profile is triggered immediately. Also the idocs end up in status 64 only sometimes not always.

Where do we check and what do we investigate?

Mick

[GauthamV]

If this happens only sometimes then there might be any delay

in RFC connection which may keep status in 64 and also if

the work process are not available for background job to be triggered

immediately which may also have your idocs in status 64.

[Former Member]

Can you explain this in more detail? Also how can we prevent this?

There is no batchjob which processes these idocs since the setting is triggrer immediately (or atleast that is my understanding that if the setting is trigger immediately no batch job is required)

Mick

[Former Member]

Please help as I am new to ALE Idocs and not sure what is casing this issue?

Any help would be appreciated.

Thanks

Mick

[Former Member]

I think the comment by Gautham Vangaveti is probably correct.

We hit the same issue occassionally. We have IDOCS as trigger immediately, but at the time they try to process, there are no available work processes which can handle the IDOC and they sit at status 64.

There is an oss note 1333417 which describes the situation

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1333417

And unhelpfully suggests changing over to processing by batch job, which is not always appropriate.

It may be worth enlisting help from you Basis team to try and indentify if those going to status 64 are occuring at the same time each day, and maybe looking to see what other processes are running at that time. If the load on the system can be managed then the problem may go away, it did for us.

Otherwise, Basis may be able to increase the number of work process which may also resolve the issue.

[Former Member]

As there are no further answers, closing this thread