Error in ALE Service

[Former Member]

hi experts,

currently i am working on the object on IDOC. everything is working fine but i am getting an error message

"IDOC passed without the Message type to ALE Service".

can you all tell me what is this error and how to rectify this.

Looking forward for your replies.

Answers will be rewarded accordingly.

thanks

Anil

[Former Member]

Check oss notes..Sometimes it may happen if you will not have proper authorizations !!

[Former Member]

Hi,

explain the scenario and the error in detail.

[Former Member]

hi,

thanks for replying.

Actually i am triggering the IDOC through the ouput types.

when ever the sales order is create/changed/cancelled the idoc needs to triggered with the sales order number.

when i am doing this i am getting this error message saying the IDOC WITHOUT MESSAGE TYPE HAS BEEN PASSED TO THE ale LAYER.

LOOKING FORWARD FOR YOUR REPLY.

THANKS

ANIL

[Former Member]

Have you attached your output type in messages tab of partner profiles in we20?

[Former Member]

hi suresh,

we added the Message type in WE20.

if it is in message control tab correct,

if yes means i have added the message type with the APPLICATION , output type, process code also.

[Former Member]

Hi,

I guess the basic approach of triggering outbound ORDERS message for sales order creation/change is wrong.

outbound ORDERS message will be triggered for PO creation/change and you need to us output type defined in purchase area ('EF' 'NEU' 'ME10' ).

even i can't see any process code for outbound sales order.

you can use ORDRSP(SD10 processcode) to send outbound order confirmation and in that i think you can use diffrent qulifiers for sending creation/change status .

I hope my understanding is correct.

[Former Member]

hi suresh,

it is custom process code assigned to custom message type and idoc type.

i have configured everything in we81, 82, etc.

thanks

[Former Member]

Hi,

Have you checked the details in processing log of output type ?

Regards

Vinod

[Former Member]

Check oss notes..Sometimes it may happen if you will not have proper authorizations !!