SE91 Maintenance and transport messages

[Former Member]

Hi,

Anyone knows how to work with SE91 transaction?, i´m using it to creating and display some messages, but when i transport this objects to QAS System, this shows "Message class Y_MSS_SEGURIDAD has not been maintained". The Y_MSS_SEGURIDAD is the object that i have been making to some abap developments. Anyone knows about this warning?

Thanks,

RCL.

Edited by: Ricardo Carrasco on Jan 20, 2009 6:26 PM

[Former Member]

Hi

Did you check the transport log to know if the transport carried the message & its sucessfully imported in your QAS system..

Thanks

Geetha

[Former Member]

Hi,

Yes, i did it, but sap tranport the object normally.

Thanks,

RCL.

[Former Member]

Hi

The system create a request as soon as u create or change a message class, just like the rest of abap objects.

So try to check if your class was transported to QAS System.

Max

[Former Member]

Hi,

SE91 is the transaction to maintain messages:

if you use somehting like below in the ABAp object

message e000(zz) with '&' '&' '&' '&' .

here you are using message 000 of the message class zz similarly you can assign a message class to a object like below in the report statement of a program:

report Zxxxxx message id ZZ.

here you can give message like below:

message e000 with '&' '&' '&' '&' .

here the bprogram takes the default class as declared above.

you should check if the message class that you are using does exist in SE91.

Regards,

Himanshu

[Former Member]

Hi Ricardo,

Go to se91 transaction give the message class and display.

In that screen go to Environtment->Transport Organizer.

Regards,

Rohit

[Former Member]

Hi,

I know that i must transport the objects. In fact, i did it. The problem is that i see the changes in DEV system, but these changes are not implemented in the QAS System, assuming that there are automatic imports in QAS system through background job.

Apparently the is generated because the request is not transported, somehow, in the QAS system, then changes cannot be reflects.

Thanks,

RCL.

[Jelena]

>

>  assuming that there are automatic imports in QAS system through background job. 
>

Assumption is mother of all screw-ups. Check the log for your transport in DEV to see if it ever made it to QAS. Ask your Basis admin to check on the transport.

[Former Member]

Hi,

The Assumption is because there is a QAS system with automatic imports through background job. I know that you´re saying.

Thanks,

RCL.

[Former Member]

As I said before, it's telling you that the message class itself (not the message) is not in QA. Have you looked into that?

Rob

[Jelena]

If the transports are automated, it doesn't mean that they all go through successfully into QAS.

Have you, yourself, created this message class (not the particular message)?

Have you checked the log for the transport (SE01 -> enter request # -> click Log)? What does the log say?

[Former Member]

Ok, i see....

I could see that there is a message related with the import in QAS, "Import steps not specific to transport request". Do you know about that? All other things related with the import says "Successfully completed".

Thanks a lot.

RCL.

[mariano_sabiche]

Hola Ricardo;

A mi me paso lo mismo en la SE91, con una clase de mensaje, y descubrí que la clase de mensaje la creé con un paquete $TMP, y esta clase de paquete no se puede transportar, por ende, es posible que tengas el mismo problema.

Una solución es que cambies el nombre de la clase de mensaje, y crees una nueva, con un paquete del tipo Z001.

Richard, see in the transaction SE91, the propertys, because you create the message class with a package $TMP, you can't transport any oder because this is a Local Package. Try to modify the name of your message class to another, and create a new message class with other package.

Best regards.

Mariano

[Former Member]

It looks as if the message class itself was never transported to QA.

Rob