topic MESSAGE_TYPE_X in Application Development and Automation Discussions

MESSAGE_TYPE_X

peter_strauss — Tue, 16 Dec 2008 00:06:57 GMT

Hello,

My customer is getting intermittent MESSAGE_TYPE_X errors generated from a customer developed ocx file.

The customer consulted with their developers and they want to know whether it is possible to assign a single DYNPRO program to a single thread.

Is this possible?

Kind regards,

Peter

Re: MESSAGE_TYPE_X

Former Member — Tue, 16 Dec 2008 03:26:16 GMT

Hi Peter,

There are many SAP notes available for the error message MESSAGE_TYPE_X . Please check if there is any relevant note for your transaction.

Best regards,

Prashant

Re: MESSAGE_TYPE_X

peter_strauss — Tue, 16 Dec 2008 03:29:02 GMT

Well... there don't tend to be may SAP notes regarding custom coding.

What I specifically want to know is:

Can a dynpro program be run as a single thread?

Re: MESSAGE_TYPE_X

Former Member — Tue, 16 Dec 2008 04:14:17 GMT

Yes if you have assigned a TCODE to it, then it can be executed as a single program . Ensure that the screen flow is defined & BACK event is handled.

I would still recommend to have a look at sap notes as this is a standard error message which is raised if you are using a specific scenario.

Few of them are as follows :-

Note 940654 - MESSAGE_TYPE_X Short Dump on Word Document viewer screen

373437 - MESSAGE_TYPE_X in control processing

Best regards,

Prashant

Re: MESSAGE_TYPE_X

peter_strauss — Thu, 18 Dec 2008 07:35:27 GMT

Hello Prashant,

Thanks for your help.

The customer found that the problem with MESSAGE_TYPE_X errors was caused by an issue with multihtreading in an ocx file that they had developed. They were considering applying this restriction via SAPGUI, but they have decided to work on the ocx file instead.

From your anwer it sounds like they would be able to do the same on the SAPGUI side as well.

Thanks again.

Peter