Status 29: Error in ALE service : Entry in outbound table not found

[Former Member]

IDoc: 0000000003560240 Status 29: Error in ALE service

Entry in outbound table not found

No partner profile (outbound parameter) could be found using the following key:

/0000000000/LS//YHROT_XXM_IN////

This refers to the key fields in table EDP13:

RCVPRN Partner number

RCVPRT Partner type

RCVPFC Partner function

MESTYP Logical message

MESTYP Message code

MESCOD Message function

TEST Test indicator

Procedure

Please check the EDI partner profiles.

But The IDOC befor this and after this is successfully run.

And even after reprocessing also it is giving same error.

After checking Contorl record, we found that there is no data in receipant Info in Partner Tab.

What would be the issue.

Please suggest.

Thanks & Regards,

Monika

[Former Member]

Hi

Check whether you have maintained partner profile in WE20 properly for the periculer message type to the perticuler system.

[Former Member]

Hi,

This is because the reciepient port and partner profile details specified are not correct.

clearly define the PORT for logical system in WE21 and Partner profile in WE20 for the port and logical system you need to send the Idoc. Pass these details in EDIDC.

[Former Member]

Hi Sorry for late reply.

Actually everything is maintained properly.

One IDOc is getting successful and another is getting errored.

We processed 60 Idocs anad then we found out of that 27 got into error.

Error Status 29. But Port n all is there.

what will be the case? One more thing we observed is that, Header segment is missing in that idocs.

How? Not able to analysed.

Please suggest.

Your help will be grateful.'

Monika

[mithun_shetty4]

Does this 29 Error records have the Control record ? EDIDC segment contains the Details of receiver sender and message type

How are your IDOC Created ? We19 or is it a real time process ?

[Former Member]

It is a real time process.

It has no control records as well as header segment.

not able to analysed what is the issue.

coz EDIDC segment which contains the Details of receiver sender and message type are already maintained properly.

and strange is that the same IDOC is proccessing successful and some are giving error 29.

just for now we processed it by maintaing control record manually through we19.

But it is not the process for everytime.

What will be the issue.

Should we need to use Collect IDOCs.?

Is port getting busy or what? Any kind of buffer free activity required?

Please help

[mithun_shetty4]

if you have received all the segments properly from sender( EDIDC & EDIDD) then i feel that there is some user exit which may be the cause for this error.

Have u checked the same ? Which message type and IDOC type are u using ?

[Former Member]

Hi ,

Thanks for your reply.

We are using one custom message type.

I would like to give you example of exact scenario.

Suppose my IDOC has large amount of segments then ,

It is dividing as

1st IDOC : Control record ....header and data segments

2nd IDOC : only data segment

3rd IDOc : only data segment

4th IDOC : data segment and Trailer.

In this way, I am getting all my 4 IDOCs in error.

What should be d reason?

your help will be grateful.

Hi Everyone,

any update?

Edited by: Monika.Dhumal on Feb 14, 2012 11:49 AM

[Former Member]

Hello Experts,

Please suggest.

[Former Member]

Hi Monika,

Control record is mandatory for every Idoc and hence you should not split the Idoc as you mentioned above.

Identify the process code assigned to your message type through WE64.

Then identify the underlying function module for the process code fetched above in WE41.

Look for the logic written over there and correct it accordingly so that you can resolve the issue permanently.

Cheers,

Raja.D

[Former Member]

Hi Monika,

    Have your issue been solved?

    I am facing the same error message, if your problem has solved, could you please let me know how?

Thanks,

Lucy

[noral]

i encountered this similar issue too.help