Skip to Content

FPM provides Message mapping feature which is very interesting, but I found it tough to use it for the first time.  After going through the FPM cookbook thoroughly, I got a better idea of this concept, and realized that it is something similar to Message mapping in HCM Process and Forms. Though I had initial hiccups of getting it working, but slowly I managed to get it working as per my requirement. In order to make other’s life easy, I listed down all the steps to illustrate this feature.

To start with, Enable the Message Mapping in OIF/GAF/OVP Component configuration for e.g. Let’s take the component configuration HAP_OIF_MAIN_DOC of the WD Application : HAP_MAIN_DOCUMENT’s Application Configuration : HAP_AC_MAIN_DOC is customized to Set the Message Mapper Settings(Enable Message Mapping) as shown below-


The message mapping is done in the view – FPM_V_MSG_MAPPER which has two new columns like Application Context Name and Message Category. It took some time for me to understand these 2 new columns usage, but as I started debugging (the class-CL_FPM_MESSAGE_MANAGER, method-IF_FPM_MESSAGE_MANAGER~REPORT_T100_MESSAGE), I found it as an easy way to populate/find these column values in this mapping table –


By debugging this method, I got the message that needs to be mapped with the column values – Namespace as SAP, Application Context Name as HRHAP00_DOCUMENT, Message Class as HRHAP00_DOCUMENT, Message Number as 214, Message Type as E with an alternate message(Alternate Message Class, Alternate Message Number).


 As observed, a new message is defined in the custom message class for the alternative message.


Finally test your application to see the mapped message.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply