Configuring message in t-code OPJB

[Former Member]

Hello,

We have a requirement to convert a standard warning message to an error message in t-code COR1.

The message is: Application area: 40, Message: 093.

To achieve this, I created a new entry in t-code OPJB but it does not work.

However, when I changed the message type for an existing entry, it worked.

Example: Application area: CO, message : 035.

This message was of 'W' type. I changed the type to 'E' and in t-code COR1, it was displayed as error message after the change which was previously displayed as warning message.

So, am I missing any other configuration or it is not the right solution?

Kindly suggest. Thanks in advance.

Regards,

Richa

[Former Member]

Hi, Richa!

I suppose, this question is more for functional consultants, so I'll look at it from ABAP point of view.

First of all, why 035(CO) is able to be customized. Looking at message usage I found that in COR1 there is a CALL FUNCTION 'CO_MES_GET_MESS_TYPE' before showing the message. This FM gets modified message type if was changed by customization.

Speaking about message 093(40) I found only one place where it is used in COR1 (maybe there are nested calls from some FMs or smth like that):

CALL FUNCTION 'CM_F_MESSAGE'
              EXPORTING
                   ARBGB                 = '40'
                   MSGNR                 = '095'
                   MSGTY                 = 'E'.

Inside of this FM there is a  CALL FUNCTION 'READ_CUSTOMIZED_MESSAGE'.

If i remember right, it is connected with customization in OBMSG and OBA5. You may try your luck in these t-codes and find it out.

[RaymondGiuseppi]

I agree with Nikolay, you should try with Customizing transaction OBA5 (You may also require transaction SM30 on view V_T100SA to add Application Area 40 to the allowed values)

Regards,

Raymond

[Former Member]

Dear Raymond/ Nikolay,

I tried with both OBA5 and OBMSG.

OBA5: After maintaining entries in view  V_T100SA, when I want to maintain an entry for application area 40, I get a message "No control of messages possible for work area 40"

OBMSG: I maintained an entry, but the output does not change.

Can you suggest any other solution?

Regards,

Richa

[RaymondGiuseppi]

Try to also add you area/number in table T100S with SM30, else ypu could try to use an implicit enhancement point in the identified form.

Regards,
Raymond

[Former Member]

Hi Raymond,

I tried the above solution but also. But, the type of message in the output does not change.

Any other solution you may suggest?

Regards,

Richa

[Former Member]

Also, in my case, the message in COR1 t-code is being raise from line 123, Include LCOSDF3F, Form BOM_APPROVAL_CHECK.

[Former Member]

If message is shown from that place, then I'm afraid it's not customizable. You can check the application logic - message is shown when BOM_APPR flag is not initial. Unfortunately, I'm not specialized in CO and can't help you with it. It's better to ask a functional consultant for a help - maybe there is a way to move to another branch of application logic.

[Former Member]

As suggrsted by Nikolay and Raymond, some standard SAP messages are not configurable.

Hence, we will need to raise a custom error message.