Skip to Content
0
Former Member
Sep 05, 2013 at 10:18 AM

Why idoc has challenged to the status 64?

42 Views

Hi All,

I am facing with below issue.

After first integration Y02 ​​movement, Why idoc has challenged to the status 64?

Can you suggest any solution or check to include in the program that is run as job that makes sure that once the IDOC reached to 53, it should not convert to 64 status.

The IDOC at status 51 is reprocessed using RBDMANI2. Before this program converts IDOC from 51 to 53 status, there is another job which picked up this IDOC to convert from 51 status to 64 status.

So the problem is the IDOC has reched to status 53 but due to the job the final status is reached as 64 ( from 51 to 64).

Below is the information on timing for different statuses :

51 Status - 23.08.2013 07:02:17 - Application document not posted

62 Status - 23.08.2013 07:02:16 - IDoc passed to application

64 Status - 06.08.2013 16:08:40 - IDoc ready to be transferred to application

51 Status - 06.08.2013 16:08:39 - Application document not posted

62 Status - 06.08.2013 16:08:39 - IDoc passed to application

64 Status - 06.08.2013 16:08:39 - IDoc ready to be transferred to application

Can you suggest any solution or check to include in the program that is run as job that makes sure that once the IDOC reached to 53, it should not convert to 64 status.

Please help me if possible and Thanks in Advance.

Regards,

Lakshmipathi