Error "Terminal type 202: Incorrect output destination/message type TERM"

[former_member277633]

Hi:

We actually are using SRM v. 5, and we detected an intermiteng error in SM21, it says

<b>Terminal type 202: Incorrect output destination/message type TERM</b>

It is generated at Client 000 and relates to program BBP_BGRD_APPROVAL. The actual output of the log is described:

<b>Terminal type 202: Incorrect output destination/message type TERM

No Active Link Found in the Link Table

> Conversation ID: 39968053

> CPI-C function: ?

No Active Link Found in the Link Table

> Conversation ID: 39968053

> CPI-C function: CMRCV

Delete session 001 after error 004 </b>

What we are worried about, is that the final error, relates to a user session end =(.

We were looking for some information on SAP Notes and forums, but we didn't find any useful info.

Does any one know what is this error about? We will appreciate any comments.

Thanks in advance, Abrahamdelgdaov

[marcelo_sehnem · Accepted solution]

Hello Abraham,

I don't think this is an error. It's just the

message in SM21 is a little misleading. When the system administrator

ends the session manually, or the work processes restart, there is

a communication error between the ITS and the work process. This is

just a warning in SM21, and there's nothing to worry about it.

Regards,

Marcelo

[former_member277633]

There's actually not a problem the situation described, we sent a message to SAP and the answer was the same.

[former_member277633]

Hi Marcelo:

Thanks for your comments. Actually, we have observed this type of messages quite commonly on our system. As administrators, we don't cancell user sessions, excepto it is requested, and it is less common to do so on our SRM system.

When the user session is closed by timout, it didn't appear this message, and as I said, we are concerned about the message of the user session.

In which cases the Work Process needs to restart? Is there a configuration or parameter to control this behavior on work process?

Thanks a lot, Regards

[marcelo_sehnem]

Hi,

This kind of error message usually arises if a program wants to send

data to the partner program which will be identified via the

conversation ID, but this conversation ID is not in the list of

active RFC links.

This always happens when one of the two partner programs finishes the

conversation and informs the remaining partner program.

Also included in this information is that the gateway already deletes

the communication entry in the communcication table and conveys the

message to the partner program.

This partner program in turn accepts the message but still wants to

send a receipt or something else to the program that is already finished

Another send after you've received the close of the connection is not

allowed.

Therefore the messages you are seeing in the syslog are definitely ha

rmless because even if the send would go through, the receiver is not

able to receive the message.

Check if there are any other network related errors in the system.

Regards,

Marcelo