error messgae to warning message

[Former Member]

Hi all

I have a standard error message used in a standard tcode.

I need to chnage the error messgae to warning messgae ..

Is it possible ?

Cheers

Christina

[Former Member]

It can be done only through customizing. ABAP changes for this task means changing standard program.

[Former Member]

if you have access key of standard program than you can change it to warning message.

Amit.

[JozsefSzikszai]

First you can try in customizing: Start transaction OBA5, enter the message class and check if the message number can be selected. If yes, than you can set to warning, otherwise not.

(Of course the message could be set to warning, through changing the source code, but that means changing standard SAP, which is not really suggested.)

[Former Member]

Hi

U can not amend standard error messahe.

Create Z... message class in Se93 and create your message there. Then use this message in your program

Regards

Anbu

[Former Member]

Hi,

Go to SPRO transaction

Click on IMG - >Navigate through the following path

Supplier Relationship Management -> Cross- Application basic settings -> Message Control -> Influence message control (Click here)

A new window opens up.

Select BUS2121 (Business object)

and then double click on Message control folder

on the left side.

Create a new entry with

Mesaage class - BBP_PD

Msg no - 584

Text - Preferred delivery date cannot be kept; Earliest date: &

Type - W

Standard - E

Hope this will definitely solve the problem.

Regards,

Harish

[Former Member]

HI Harish

ya i tried ur logic.. but in SRM there is no path as 'Cross Application - basic settings'.

Can u pls tell me where it is..

Cheers

Christina

[Former Member]

hi use this.. it is possible

message e000(00) display like 'I' with 'this is text '.

[Former Member]

Hi all

I have done a user exit and made some changes in the include..and also i have created a include..

Is it possible to include a message class in include.

Cheers

Christina

[Clemenss]

Hi Christina,

You can use a message from another message class by using the MESSAGE Syntax

MESSAGE ID id TYPE mtype NUMBER n with ...

If the exit functions include gets more complex, it is advisable to copy the involved customer function group to customers name space. In the exits include call your own function. In the newly creates function group you can assign a message class and create FORM includes as you need. This may gain a lot of transparency and make the exit maintenence-friendly.

Regards,

Clemens