<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Configuring message in t-code OPJB in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800468#M1881020</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, in my case, the message in COR1 t-code is being raise from line 123, Include LCOSDF3F, Form BOM_APPROVAL_CHECK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Dec 2014 05:23:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-12-17T05:23:32Z</dc:date>
    <item>
      <title>Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800464#M1881016</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a requirement to convert a standard warning message to an error message in t-code COR1.&lt;/P&gt;&lt;P&gt;The message is: Application area: 40, Message: 093.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To achieve this, I created a new entry in t-code OPJB but it does not work.&lt;/P&gt;&lt;P&gt; However, when I changed the message type for an existing entry, it worked.&lt;/P&gt;&lt;P&gt;Example: Application area: CO, message : 035.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, am I missing any other configuration or it is not the right solution?&lt;/P&gt;&lt;P&gt;Kindly suggest. Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Richa&lt;/P&gt;&lt;P&gt;&lt;BR /&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 10:28:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800464#M1881016</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-16T10:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800465#M1881017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Richa!&lt;/P&gt;&lt;P&gt;I suppose, this question is more for functional consultants, so I'll look at it from ABAP point of view.&lt;/P&gt;&lt;P&gt;First of all, why 035(CO) is able to be customized. Looking at message usage I found that in COR1 there is a &lt;SPAN class="L0S52"&gt;CALL &lt;SPAN class="L0S52"&gt;FUNCTION &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'CO_MES_GET_MESS_TYPE' before showing the message. This FM gets modified message type if was changed by customization.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;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):&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;&lt;SPAN class="L0S52"&gt;CALL &lt;SPAN class="L0S52"&gt;FUNCTION &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'CM_F_MESSAGE'&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;EXPORTING&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ARBGB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S55"&gt;= &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'40'&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MSGNR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S55"&gt;= &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'095'&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MSGTY&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S55"&gt;= &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'E'.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;Inside of this FM there is a&amp;nbsp; &lt;SPAN class="L0S52"&gt;CALL &lt;SPAN class="L0S52"&gt;FUNCTION &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'READ_CUSTOMIZED_MESSAGE'.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S33"&gt;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.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 14:34:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800465#M1881017</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-16T14:34:20Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800466#M1881018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with &lt;STRONG&gt;&lt;A _jive_internal="true" href="https://answers.sap.com/people/nikolayevstigneev"&gt;&lt;SPAN lang="EN-US" style="font-weight: normal;"&gt;Nikolay&lt;/SPAN&gt;&lt;/A&gt;, &lt;/STRONG&gt;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)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 15:01:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800466#M1881018</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2014-12-16T15:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800467#M1881019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Raymond/ Nikolay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried with both OBA5 and OBMSG.&lt;/P&gt;&lt;P&gt;OBA5: After maintaining entries in view&amp;nbsp; 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"&lt;/P&gt;&lt;P&gt;OBMSG: I maintained an entry, but the output does not change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you suggest any other solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Richa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2014 04:51:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800467#M1881019</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-17T04:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800468#M1881020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, in my case, the message in COR1 t-code is being raise from line 123, Include LCOSDF3F, Form BOM_APPROVAL_CHECK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2014 05:23:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800468#M1881020</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-17T05:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800469#M1881021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2014 06:17:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800469#M1881021</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-17T06:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800470#M1881022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2014 08:02:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800470#M1881022</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2014-12-17T08:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800471#M1881023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried the above solution but also. But, the type of message in the output does not change.&lt;/P&gt;&lt;P&gt;Any other solution you may suggest?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Richa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2014 11:42:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800471#M1881023</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-17T11:42:24Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring message in t-code OPJB</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800472#M1881024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As suggrsted by Nikolay and Raymond, some standard SAP messages are not configurable.&lt;/P&gt;&lt;P&gt;Hence, we will need to raise a custom error message.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Dec 2014 11:03:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/configuring-message-in-t-code-opjb/m-p/10800472#M1881024</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-12-18T11:03:55Z</dc:date>
    </item>
  </channel>
</rss>

