topic Re: CATT Message Variables in Application Development and Automation Discussions

CATT Message Variables

Former Member — Tue, 15 May 2007 10:04:57 GMT

Hi All

I have created a CATT test procedure, which creates a Sales Document. A number of messages are created as the Transaction runs and I need to access the data in the messages. I can get to the data from the last message that is created but I also need to get data from a previous message. Is there any way that I can do this?

Thanks

Andy

Re: CATT Message Variables

Former Member — Tue, 15 May 2007 12:45:39 GMT

Hi.

We did that once, we selected the value right out of the database.

Table CATJ for CATT run data

-> errorcodes from CATL

In errorcodes you can then select the messages you want

MSID1 '<MessageClass>'

MSNR1 '<MessageNr>'

And cause you know the expected message you can easily use offset(length) to get the desired value out of the message.

Regards,

Timo.

Re: CATT Message Variables

Former Member — Tue, 15 May 2007 13:10:22 GMT

Hi Timo

Thanks for your reply, I will bear it in mind, however,I've managed to find the following SAP Help document that details how to do it:

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/d7/e21503408e11d1896b0000e8322d00/frameset.htm">CHEERR - Check system message</a>

Kind regards

Andy

Re: CATT Message Variables

Former Member — Tue, 15 May 2007 13:10:47 GMT

Hello,

Do you need more than the four lat ones?

If a transaction sends more than one system message, the message variables &M01 to &M04 contain the variable parts of the last message issued.

Regards,

Walter

Re: CATT Message Variables

Former Member — Tue, 15 May 2007 13:14:46 GMT

Hi Walter

As you will be aware, each message can contain upto 4 variables - I was looking for access to the variables of messages prior to the last one. As in my reply to Timo, there is a way of doing this which is explained within the above document.

Thanks for your reply.

Kind regards

Andy

Re: CATT Message Variables

Former Member — Tue, 15 May 2007 13:40:02 GMT

OOps, typo error.

But I was looking at the same page in the docu 😃