Standard Solution :You might be aware of a standard solution. In transaction RSRT, select your query and click on the "message" button. Now you can determine which messages for the chosen query are not to be shown to the user in the front-end.
Custom Solution:
Only selected messages can be suppressed using the standard solution. However, there's a clever way you can implement your own solution... and you don't need to modify the system for it!
All messages are collected using function RRMS_MESSAGE_HANDLING. So all you have to do is implement an enhancement at the start of this function module. Now it's easy. Code your own logic to check the input parameters like the message class and number and skip the remainder of the processing logic if you don't want this message to show up in the front-end.
FUNCTION rrms_message_handling.
Start
ENHANCEMENT 1 Z_CHECK_BIA.
* Filter BIA Message
if i_class = 'RSD_TREX' and i_type = 'W' and i_number = '136'
* just testing it.
* exit
end if.
ENHANCEMENT
End
IMPORTING
---------
---------
--------
EXCEPTIONS
Dummy
Labels
- BW Architecture (1)
- BW Reporting (3)
- Data Loading issues (7)
- Datawarehousing (9)
- Extraction (3)
- General Maintainence (5)
- HANA (1)
Blog Archive
-
▼
2008
(21)
-
▼
September
(17)
- Difference between LIS and LO Extraction
- What will happend if a request in Green is deleted?
- When is reconstruction allowed? Questions
- Handling Amount Values with currencies in BW
- PSA reverse posting
- Unable to Cancel Job in SM37 (R3)
- Attribute delta loading "duplicate record found"
- How to supress messages generated by BW Queries
- Dimension Size Vs Fact Size
- BW Main tables
- Production Support Issues in BW
- Selective Deletion in Process Chain
- How to Debugg Update and transfer Rules
- BW tables
- How to define F4 Order Help for infoobject for rep...
- TCURF, TCURR and TCURX
- Error loading master data - Data record 1 ('AB03...
-
▼
September
(17)
17 Sept 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment