Idocs with status 64

[Former Member]

Hi

We are in SRM 5.0 with Classic Scenario.

We use HR replication process for udpating org. structure in SRM. Transaction PFAL do run on daily basis in R/3.

Issue : We have an issue where certain IDOCS that comes to SRM from backend R/3 get stuck in status 64 and have to be manually processed by someone on daily basis to keep org. structure up to date.

Would there be any automated process for this ? or we need to manually process the idocs daily which are in 64 ?

Please advise.

Appreciated your help.

Maron.

[Former Member · Accepted solution]

Hi

The issue for IDOCs being in 64 status could be due to the load. Pls check in the partner profiles for particular message type is the option checked as "transfer idoc immediately" If there are many idocs comes into the entry port system will ignore few of them and moves ahead. Inthis case its better to collect the idocs and schedule a periodic batch job with vraint to process the collected idocs. If at all any errorneous idocs there, your tech team can configure a work flow for that and the messages could be routed to monitroing team accordingly.

Thanks

Kiran

[Former Member · Accepted solution]

Thank you kiran.

[former_member183819]

Hi Moran

Please check with technical HR guy

1) BD61 Activate Change Pointers Globaly

2) BD50 Activate Change Pointer for Message Type

there is a concept called CHNAGE POINTER .

this helps to bring only updated data from ECC to another system. not all existing data

check it up with HCM forum for quick help.

br

muthu

[Former Member]

Muthu

A nightly job is scheduled to convert change pointers to idocs in HCM. Then another job moves these applicable idocs to SRM. There may be a number of reasons why idocs go to error when coming over from HCM. So, daily monitor the idocs and will reprocess the error ones.

Cant this be automated ?

Thank you for your replies.

Maron.