topic Re: ALE throws dump Message_Type_X in Application Development and Automation Discussions

ALE throws dump Message_Type_X

Former Member — Sat, 12 Mar 2011 05:30:48 GMT

Hi All,

I did ALE configuration on my DEV and PRD for transferring data from DEV to PRD. Although i know, we should not move any data from DEV to PRD, but it's client requirement.

So i did ALE and model view successfully generated on DEV and RFC is perfectly fine even by connection test or authorization test.

When i run bd10 on DEV, it successfully generated idoc with message type MATMAS. and when i get the materail via BD11, it successfully created idoc on PRD. but when i see the material in MM03, it throws error material does not exist or is not activated.

it also throws dump Message_Type_X

WORKFLOW_LOCAL_400

RFC_READ_DESTINATION_TYPE

DESTINATION_NOT_EXIST

What steps should follow now?

Regards

Disha

Re: ALE throws dump Message_Type_X

Former Member — Sat, 12 Mar 2011 13:35:35 GMT

Please check the log in MM90, you can get log number from WE02...

Also try to debug the inbound function module through WE19...

Thanks.

Re: ALE throws dump Message_Type_X

Former Member — Wed, 16 Mar 2011 12:34:49 GMT

Hi Krishnendu,

Status is in red when i check from t-code WE02.

When i check it in MM90 and execute it, it does not show any log.

Please tell if i am missing any step..

Regards

Disha

Re: ALE throws dump Message_Type_X

Former Member — Tue, 22 Mar 2011 21:36:29 GMT

Hi,

You are probably using an Idoc type using workflow. Ensure the u2018Configure RFC Destinationu2019 is set in transaction SWU3 - especially that RFC destination WORKFLOW_LOCAL_400 exists in SM59 and user WF-BATCH exist and is not locked.