SAP FERC_MESSAGE_TYPE_GET Function Module for Get the message type for a customizable message









FERC_MESSAGE_TYPE_GET is a standard ferc message type get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get the message type for a customizable message processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ferc message type get FM, simply by entering the name FERC_MESSAGE_TYPE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: FE01
Program Name: SAPLFE01
Main Program: SAPLFE01
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FERC_MESSAGE_TYPE_GET pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FERC_MESSAGE_TYPE_GET'"Get the message type for a customizable message
EXPORTING
* MESSAGE_CLASS = 'F=' "Message class
MESSAGE_NUMBER = "Message number

IMPORTING
MESSAGE_TYPE = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFE01_001 Determine regulatory indicator or specify as clearing object
EXIT_SAPLFE01_002 Specific standard cost adjustment order and cost element of cost center
EXIT_SAPLFE01_004 Check if posting to G/L account is possible

IMPORTING Parameters details for FERC_MESSAGE_TYPE_GET

MESSAGE_CLASS - Message class

Data type: T100C-ARBGB
Default: 'F='
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESSAGE_NUMBER - Message number

Data type: T100C-MSGNR
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FERC_MESSAGE_TYPE_GET

MESSAGE_TYPE -

Data type: T100C-MSGTS
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FERC_MESSAGE_TYPE_GET Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_message_type  TYPE T100C-MSGTS, "   
lv_message_class  TYPE T100C-ARBGB, "   'F='
lv_message_number  TYPE T100C-MSGNR. "   

  CALL FUNCTION 'FERC_MESSAGE_TYPE_GET'  "Get the message type for a customizable message
    EXPORTING
         MESSAGE_CLASS = lv_message_class
         MESSAGE_NUMBER = lv_message_number
    IMPORTING
         MESSAGE_TYPE = lv_message_type
. " FERC_MESSAGE_TYPE_GET




ABAP code using 7.40 inline data declarations to call FM FERC_MESSAGE_TYPE_GET

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single MSGTS FROM T100C INTO @DATA(ld_message_type).
 
"SELECT single ARBGB FROM T100C INTO @DATA(ld_message_class).
DATA(ld_message_class) = 'F='.
 
"SELECT single MSGNR FROM T100C INTO @DATA(ld_message_number).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!