Message category

Hi, expert,
i want to change some of message's category form error to warning, where can i do it?
when i use SE91, i can't see message category, and appears a popup :Changes to Repository or cross-client Customizing are not permitted
when i use OMCQ, i can't see the application area i want. so both of them don't work,
please tell me how can i change the message category as i want?
thanks and best wishes,

Hello David,
The below paths gives sytem message
1. IMG-Materials Management- Purchasing-Enviornment Data-Define Attribute of sytem Messages
2. IMG-Materials Management- External Service Management-Define Attribute of sytem Messages
3. IMG-Materials Management- Inventory Management & Physical Inventory-Define Attribute of sytem Messages
4. IMG-Materials Management- Logistics Invoice Verification-Define Attribute of sytem Messages
In OMCQ, 2nd Column "Appl.A" is application area.
I think this will help you.
rgds,
S.Balaji.

Similar Messages

SD - Two message category for an invoice document type

Good morning all,
I use InterCompany biling in SD with standard invoice document type 'IV' and message category 'RD04' (which enables vendor invoice creation).
My customer asks to be able to print a form for the intercompany bills.
For the non intercompany bills this is actually performed by using a specific message category.
So my question is : is there any way to have TWO message category ('RD04' + specific message for form) automatically attached to an intercompany bill (customizing, user-exit,...) ?
Best regards.
Didier GOBLET.

Hi Didier
Assign the logic to the RD04 output type smartform.Then it is possible,In the smartform include the logic that it should automatically attach to the intercompany billing.
Regards
Srinath

Finding the Message Category from Message Type ( TXN - NOTIF_CREATE )

Dear All,
According to my requirement , I need to find the Message Category , from the Message Type.
As for Example :
SLF1 is the Message Category for Message Type SLFN .
I have got a F.M "SUP_STSUP_READ_PROCESS_TYPE" which gives the Message Type , now i need the Corresponding
Message Category.
We can also see the Message Type in Transaction : NOTIF_CREATE.
Please Help.
Thanking You All.

Dear All,
According to my requirement , I need to find the Message Category , from the Message Type.
As for Example :
SLF1 is the Message Category for Message Type SLFN .
I have got a F.M "SUP_STSUP_READ_PROCESS_TYPE" which gives the Message Type , now i need the Corresponding
Message Category.
We can also see the Message Type in Transaction : NOTIF_CREATE.
Please Help.
Thanking You All.

Process Message Category

Dear Experts,
I need a clarification How does Process message work in PP PI sheet
See as i know control recipe is created when process order is released
For setting point of control recipe destination and instruction category is assigned in Master Recipe. Control recipe destination has thier addresses and porcess instruction to be generated . Characteristic and thier values are assigned in process instruction category.
I would like to know that where is process message/ Category in the loop and How does it trigger in PPPI sheet
Can you explain me to get away from this doubt.
Regards,
Edited by: Kumar DS on Jun 10, 2009 8:23 AM

SAP has some standard Process mesaages.
Each message has a destnation, which is nothing but a BAPI.
So when a Process message is created with relevant inputs. the data is sent to the BAPI when it is sent to the destination.which gets executed and achieves the results intended for.
For example PI_Prod is use for doing a GR (101) for a Process order.
When we create a Process message with PI_PROD category all the relevant details like Order no, Material , qty, units and Storage location are neeed.then when you send it. The GR is posted.
.it is used for posting relevant changs from XMII or external systems.
Edited by: Ratan on Jun 10, 2009 2:40 PM

Message category INFREC and Basic Type INFREC01

Hi,
Do any one know how to send a material condition record to other SAP system through ALE.
I am trying to find what what is teh Message tye used to send.
I am using the Message category INFREC and Basic Type INFREC01 to send info record, however it is not send A017 and KONP entres of info record.
Please let me know if any one know Basic Type which containes A017 and KONP table fields
Bhima

Hi
use Message COND_A to transfer the conditions.
Hope this helps.
Best Regards, Murugesh

Change message category

Hi,
How can we change message category? Say error message to warning message.

Hi
The foll T Codes must be of use to you:
- OCHS
- OMPL1
- OPJB
- OVNM
- OBMSG
Regards
Srini

Message Category CONDBI

Hi All,
What is message category CONDBI ? Should it be included in Partner Profiles (in Outbound Parameters).
Regards,
Vamsi

Hi
CONDBI is used for Condition Update..and also message Type
It is depend up on situation either include or Exclude in Oubound Parameters
Regards
Vijai Jain

Message Services (Category)

Hi all,
I have a question regarding the Message Category.
Is it possible to set it in the URL, when posting the data to the queue? Something like:
http://localhost:50000/XMII/Illuminator?service=WSMessageListener&mode=WSMessageListenerServer&NAME=Test&CATEGORY=MyCategory&Content-Type=text/xml&Session=false
Thanks in advance,
Jacob
Edited by: Michael Appleby on May 26, 2011 2:42 PM

Jacob,
I assume you've tried this with no success. To the best of my understanding the Category is only used by the processing rules, so when a message is received it either categorizes it in the database buffer, or runs the associated transaction directly.
By varying the Name property you can effectively have the messages received by the processing rule, and instead of using the wildcard (*) you can use the name and map it to your desired category for further processing in a TRX (scheduled or otherwise).
So with the common built in WSMessageListener you will provide multiple processing rules for each Name and map it to the category.
Regards,
Jeremy

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

CO54: Message is not sent to any destination: Commit Work is getting failed

Hello,
While processing the Messages from XFP to SAP Update is getting terminated due to the use of Commit Work. SAP Note 147467 - Update termination when sending process messages has been referred which is for 4.6C, but we are in ECC6.0.
While processing the message in second iteration Commit Work triggres and Update happens in the data base.
Following Issue is only concerned with Nested HUs
T-Code used CO54
Following are the analysis:
it looks like u201CCreate and Post a Physical Inventory Docu201D is failing in the initial processing because the inventory doc is created when the Transfer Order to the PSA (or the TO from the PSA) is not yet completed (quant is still locked somehow).
CO54, process message category=ZHU_CONS: HU to be consumed is a nested pallet (unpacking/ repacking and TOs to/from) and qty to consume is greater that HU qty in SAP (creation of a physical inventory doc is required).
1. The error occurs while clearing the inventory posting for the physical inventory document.
2. The surprising factor is the u201CProcess Messageu201D is not processed correctly for the first time.
3. Indeed it is successfully processed without any error if you do process it second time.
Error Log from C054 T-Code.
02.08.2010                                         Dynamic List Display                                                1
Type
Message text
LTxt
Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
Message to be sent to destination:
ZHGI ZPP_0285_XFP_GOODSISSUE Individual Processing Is Active
=> Message will be sent to destination (check log for destination)
Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
Message destination ZPP_0285_XFP_GOODSISSUE triggered COMMIT WORK
Input parameters OK, passed to source field structure
Step 0: Now checking if scenario with HU
Step 2: Scenario with HU, Now checking if HU nested
Step 3: HU nested, checking if HU in repack area
Step 4: HU not in repack area, moving it to repack area
HU moved to repack area, TO number 0000000873
Step 5: Depacking nested HU...
Nested HU depacked, HU pallet n°: 00176127111000461994
Steps 6-7: Moving back HUs to supply storage type / bin...
HU 00376127111000462001 moved back to original area with TO number 0000000875
Steps 6-7: Moving back HUs to supply storage type / bin...
No need to move back HU 00176127111000461994 (not in table LEIN)
Step 8: Checking if HU fully used and quantity matches HU system quantity
HU not fully used but picked quantity > HU quantity: inventory necessary
Step 9: Inventory needed, creating physical inventory document...
Physical inventory document 0000000126 created
Step 10: Adding weighted quantity on inventory document...
Weighted quantity entered in document 0000000126
Step 11: Posting rectification in inventory document 0000000126...
Physical inventory document 0000000126 rectified
Error: rectification for doc 0000000126 not updated in DB!
=> Destination ZHGI ZPP_0285_XFP_GOODSISSUE can currently not process the message
=> Message is not sent to any destination
The errors in SM13 for this contain the program SAPLZPP_0285_HUINV_ENH (creating/changing the HUM physical inventory doc). WM Function module L_LK01_VERARBEITEN is also involved.
From SM13, it displays the following piece of code in include LL03TF2M (read the LEIN table=Storage Units table):
WHEN CON_LK01_NACH.
       IF (LEIN-LGTYP = LK01-NLTYP AND
             LEIN-LGPLA = LK01-NLPLA) OR
              NOT P_LEDUM IS INITIAL.
       ELSE.
Das ist der Fall einer TA-Quittierung wo Von-Hu = Nach-HU ist und sofort die WA-Buchung erfolgt. Dann steht die HU noch auf dem Von-Platz, daher darf hier kein Fehler kommen, sondern es wird ein. Flag gesetzt, daß verhindert daß die LE fortgeschrieben wird.
         FLG_NO_LE_UPDATE = CON_X.
        MESSAGE A558 WITH P_LENUM.
       ENDIF.
Translation in English of the German text via Google:
"This is the case where confirmation of a TO source-HU = destination-HU, and now the WA (Good Issue?)- made book. Then, the HU is still on the From-space may therefore come here not a mistake, but it sets a flag that prevents that the LE is updated."
Thanks and Regards,
Prabhjot Singh
Edited by: Prabhjot Singh on Aug 2, 2010 4:39 PM

Hope you have carried out following things in Production ( Please refer to SAP help before actually doing it in production).
1. Transport the predefined characteristics from the SAP reference client (000) to your logon client.
2. Adopt Predefined Message Categories - In this step, you copy the process message categories supplied by SAP from internal tables as Customizing settings in your plants.

Sales Order Eroor Message

Hi friends,
Here my client requirement is needed a error message while creating sales order with reference to expired quotation, but sap standard only giving warning message, but needed hard stop, pls find me a way to get error message , Thanks.
Nina.T

Hi Naina,
Can you please let us know whatu2019s the message number you getting.
Please go to Transaction u2013 OVAH (System Message), go to your message Number and change System message category from u201CWu201D to u201CEu201D.
Try to create Sales Order again and let us know whether your problem get resolved or not.
Cheers !!!!
Imzo

Deletion marked material should give error message while creating proc ord

Hello,
i had marked the material for deletion through T-code MM06 & saved.
Now when i'm creating the process order for the deleated material, System is giving only Warning message that " Material XXXX in plant XXXX has been marked for deletion."
But my requirement is system shold give an ERROR message while creating Process Order for the deleted material.

Yes Brahman is Right,
Check the followig..
Go to OMCQ and change the message category to E- Error message instead of W- Waring message in Message no M7 127, but
not M7 121.
and check it,
Regards,
Pavan idlur.

Error while calling up RFC Message No. UPC202

Hi Experts,
Calling Thru Trans code : BPS0 in ECC6.
Getting This Error :
Error while calling up RFC message No. UPC202.
After i check in BW with Trans code : ST22
Following this error message:
Category Internal Kernal Error
Runtime Errors PARAMETER_CONVERSION_ERROR
Application Component BC-MID-RFC.
More details Please find attached file.
Thanks & Regards,
Mohammed Kaleem.

Hi Mohammed,
If you are getting this error currently Please go to Sap market Place and Search with the Key words of Short Dump " PARAMETER_CONVERSION_ERROR".
Also you can raise this with your Basis team who should be able to help you out with the same.
Thanks & Regards,
RDS

Change information message to error in PS when PO created against material

In CJ20N I am changing a material that has a PO already created and all I am getting is an information message. I want this to be an error. Where would I configure this?

Hi Karen
I am not sure if your message exists there or not but give it a try, go to tcode OMCQ search for your message and change the system message category to "E".
regrds
Yogesh

System message setting for delivery.

Hi All,
I need to set message VL 261 Free goods group not complete as error message. I tried to do this setting at LE> shipping> system modification-->specify characteristic for system message.
But when i am enter error message number 261 it is giving error " enter valid value". But when I am creating delivery I can see that message in log as information. can any one help on this.
Thanks in advance.
Regards
Chetan

Hi Chetan,
for my understanding you can not switch "VL 261 Free goods group not complete as error message". If you look at the SAP customizing help you will see following information:
"The maximum possible message category is predefined by SAP. For this reason some error messages only have a limited selection of message catogories that can be set. Use F4 Help to find the maximum possible message category from the sequence 'E', 'W', 'I', ' '."
That means the message types predefined in customizing can be switched from error to warning and vice versa. BUT error messages not included can not be added or switched by customizing.

Message category

Similar Messages

Maybe you are looking for