SAP ABAP IMG Activity /SRMERP/V_MSG_F (Configure Message Filtering and Mapping)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
MM-PUR-SSP (Application Component) Self-Service Procurement
⤷
/SRMERP/OL_COMMON (Package) Object Layer: common entities

⤷

⤷

IMG Activity
ID | /SRMERP/V_MSG_F | Configure Message Filtering and Mapping |
Transaction Code | /SRMERP/44000484 | (empty) |
Created on | 20110616 | |
Customizing Attributes | /SRMERP/V_MSG_F | Configure Message Filtering and Mapping |
Customizing Activity | /SRMERP/V_MSG_F | Configure Message Filtering and Mapping |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SRMERP/V_MSG_F |
Use
In this Customizing activity, you can configure how messages can be displayed to customers, or how they may be mapped to generic messages.
Requirements
Standard settings
Activities
You enter the settings you define for this activity in a table.
To specify the messages that an entry applies to, you must use the following columns:
- Message class
- Msg. no.
- Message Type
You can make entries in one of the following ways:
- Create an entry for a specific message of a specific type
- Enter the message class, the message number, and the message type
- Create an entry for a specific message
- Enter the message class, and the message number
- Create an entry for a specific message type, in a specific message class
- Enter the message class, and the message type
- Create an entry for all message in all message classes
- Enter the message class, and leave the message number, and the message type empty
- Create an entry for messages of a certain type, in all message classes
- Enter the message type, and leave the message class, and message number empty
- Create an entry for all messages
- Leave all three fields empty and select the Log and Alert checkboxes as required
When a message is generated, the system checks for matches in the table in the following order:
- The entry exists for this message class, message number, and message type
- The entry exists for this message class and message number
- The entry exists for this message class and message type
- The entry exists for this message class
- The entry exists for this message type
- There is a generic entry for all message classes, message numbers, and message types
When a matching entry is found, the corresponding setting is used for the message.
If the customizing entry can be filtered, (that is when you check the Filter checkbox), or can be mapped fully to a message, all three fields have to be entered.
Example
Business Attributes
ASAP Roadmap ID | 251 | Transport Customizing for Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | /SRMERP/V_MSG_F | 0 | HLA0009512 | Purchasing |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
/SRMERP/V_MSG_F | V - View | SM30 |
History
Last changed by/on | SAP | 20110616 |
SAP Release Created in | 606 |