cancel
Showing results for 
Search instead for 
Did you mean: 

SXMS_TO_ADAPTER_ERRTXT - Length of string in Alert

Former Member
0 Kudos

Hi,

I have configured the below text in my alert email.

<i>SXMS_TO_ADAPTER_TYPE:[&SXMS_TO_ADAPTER_TYPE&]

SXMS_TO_ADAPTER_ERRTXT:[&SXMS_TO_ADAPTER_ERRTXT&]

</i>

The result I got is

SXMS_TO_ADAPTER_TYPE:[File]

SXMS_TO_ADAPTER_ERRTXT:[Error: Message processing failed: Exception: Message processing failed - configu]

The text is obviously truncated.

In alert categories definition, I've defined container variable SXMS_TO_ADAPTER_ERRTXT to be of datatype CHAR90. (I tried with datatype ZSTRING - A custom data type I created with type String).

However, the result is still the same.

How can I display the full error message?

Please help.

Ron

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

HI,

Check the configuration .

See the below links

Regards

Chilla

bhavesh_kantilal
Active Contributor
0 Kudos

A simialr thread posted just minutes ago.

The lenght of the text is restrcited to 80 characters,. You cannot have more than 80 charcters.

Regards

Bhavesh

Former Member
0 Kudos

Thanks Bhavesh.

I never expected such restrictions.

I have further questions:

My full format of my email is like defined as:

EMAIL TEXT

SXMS_MSG_GUID:[&SXMS_MSG_GUID&]

SXMS_RULE_NAME:[&SXMS_RULE_NAME&]

SXMS_ERROR_CAT:[&SXMS_ERROR_CAT&]

SXMS_ERROR_CODE:[&SXMS_ERROR_CODE&]

SXMS_FROM_PARTY:[&SXMS_FROM_PARTY&]

SXMS_FROM_SERVICE:[&SXMS_FROM_SERVICE&]

SXMS_FROM_NAMESPACE:[&SXMS_FROM_NAMESPACE&]

SXMS_FROM_INTERFACE:[&SXMS_FROM_INTERFACE&]

SXMS_TO_PARTY:[&SXMS_TO_PARTY&]

SXMS_TO_SERVICE:[&SXMS_TO_SERVICE&]

SXMS_TO_NAMESPACE:[&SXMS_TO_NAMESPACE&]

SXMS_TO_INTERFACE:[&SXMS_TO_INTERFACE&]

SXMS_TO_ADAPTER_TYPE:[&SXMS_TO_ADAPTER_TYPE&]

SXMS_TO_ADAPTER_ERRTXT:[&SXMS_TO_ADAPTER_ERRTXT&]

However the actual email text I got is:

EMAIL TEXT

SXMS_MSG_GUID:[1d8d091806842e4fbf3fbe23c360439f]

SXMS_RULE_NAME:[GENERAL_ALERT_RULE]

SXMS_ERROR_CAT:[]

SXMS_ERROR_CODE:[]

SXMS_FROM_PARTY:[]

SXMS_FROM_SERVICE:[BS_DEV1_ODS_OOTS]

SXMS_FROM_NAMESPACE:[urn:dev1:fapl:oots:OperationProcInfo]

SXMS_FROM_INTERFACE:[MI_OperationProcInfo_Inbound_Async_OperationProcInfo]

SXMS_TO_PARTY:[]

SXMS_TO_SERVICE:[BS_DEV1_ODS_OOTS]

SXMS_TO_NAMESPACE:[urn:dev1:fapl:oots:OperationProcInfo]

SXMS_TO_INTERFACE:[MI_OperationProcInfo_Inbound_Async_OperationProcInfo]

SXMS_TO_ADAPTER_TYPE:[File]

SXMS_TO_ADAPTER_ERRTXT:[Error: Message processing failed: Exception: Message processing failed - configu]

Everything looks fine, except for Error Code and Error Category - they are not reflected.

Did I define them wrongly?

When I launch the message display tool on RWB, I can see:

Error Category - XI_J2EE_ADAPTER_FILE

Error Code - PROCESSING_ERROR

Sender Party

Sender Service - BS_DEV1_ODS_OOTS

Receiver Party

Receiver Service - BS_DEV1_ODS_OOTS

Interface - urn:dev1:fapl:oots:OperationProcInfo MI_OperationProcInfo_Inbound_Async_OperationProcInfo

Did I define the variables wrongly?

In ALERTCATDEF, I defined Error Category with Datatype SXMSERRCAT and ErrorCode with Datatype CHAR70.

Please help.

Thanks.

Ron

bhavesh_kantilal
Active Contributor
0 Kudos

Ron,

I think there are no correspoding Error Category and Error Code for Adapter Engine Errors. These are for Integration Engine Errors and not for Adapter Engine Errors.

For Adapter Engine Errors you have the additinal fields SXMS_TO_ADAPTER_TYPE and SXMS_TO_ADAPTER_ERRTXT .

Likewise for integration engine errors, you will not find entry for SXMS_TO_ADAPTER_TYPE and SXMS_TO_ADAPTER_ERRTXT but you will get entry for Error Category and Errror Code.

This is the standard behavior.

Regards

Bhavesh

Former Member
0 Kudos

Bhavesh,

I suspected this too.

But why can I see error code and error category when I launch the message display tool from RWB -> Message Monitoring -> Select Message -> Details -> Message Data,

I can see:

Error Category - XI_J2EE_ADAPTER_FILE

Error Code - PROCESSING_ERROR

Sender Party

Sender Service - BS_DEV1_ODS_OOTS

Receiver Party

Receiver Service - BS_DEV1_ODS_OOTS

Interface - urn:dev1:fapl:oots:OperationProcInfo MI_OperationProcInfo_Inbound_Async_OperationProcInfo

I'm puzzled.

Former Member
0 Kudos

Ron,

We are facing a similar problem as you did for the length of the string in the Alert container variable SXMS_TO_ADAPTER_ERRTXT. Were you able to find a resolution for this? If so, I would really appreciate if you can share the same. We have already opened an OSS note with SAP, but with no luck so far.

Thanks,

Tarun.