SAP SHOM_REPORT_ORA_ERROR Function Module for









SHOM_REPORT_ORA_ERROR is a standard shom report ora error SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 shom report ora error FM, simply by entering the name SHOM_REPORT_ORA_ERROR into the relevant SAP transaction such as SE37 or SE38.

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



Function SHOM_REPORT_ORA_ERROR 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 'SHOM_REPORT_ORA_ERROR'"
EXPORTING
MSGVALUE = "
* TYPE3 = 'C' "
* ARG4 = "
* TYPE4 = 'C' "
MSGSEVERITY = "
MSGID = "
MSGNO = "
* ARG1 = "
* TYPE1 = 'C' "
* ARG2 = "
* TYPE2 = 'C' "
* ARG3 = "

EXCEPTIONS
COULD_NOT_BUILD_NODE = 1 COULD_NOT_SEND_T100_MESSAGE = 2 UNDETERMINED = 3
.



IMPORTING Parameters details for SHOM_REPORT_ORA_ERROR

MSGVALUE -

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

TYPE3 -

Data type: XMIARGTYP
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARG4 -

Data type: XMIARGTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TYPE4 -

Data type: XMIARGTYP
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGSEVERITY -

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

MSGID -

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

MSGNO -

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

ARG1 -

Data type: XMIARGTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TYPE1 -

Data type: XMIARGTYP
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARG2 -

Data type: XMIARGTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TYPE2 -

Data type: XMIARGTYP
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARG3 -

Data type: XMIARGTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

COULD_NOT_BUILD_NODE -

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

COULD_NOT_SEND_T100_MESSAGE -

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

UNDETERMINED - ?

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

Copy and paste ABAP code example for SHOM_REPORT_ORA_ERROR 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_msgvalue  TYPE ALMSCRVAL-VALUE, "   
lv_could_not_build_node  TYPE ALMSCRVAL, "   
lv_type3  TYPE XMIARGTYP, "   'C'
lv_arg4  TYPE XMIARGTXT, "   
lv_type4  TYPE XMIARGTYP, "   'C'
lv_msgseverity  TYPE ALMSCRVAL-SEVERITY, "   
lv_could_not_send_t100_message  TYPE ALMSCRVAL, "   
lv_msgid  TYPE SY-MSGID, "   
lv_undetermined  TYPE SY, "   
lv_msgno  TYPE SY-MSGNO, "   
lv_arg1  TYPE XMIARGTXT, "   
lv_type1  TYPE XMIARGTYP, "   'C'
lv_arg2  TYPE XMIARGTXT, "   
lv_type2  TYPE XMIARGTYP, "   'C'
lv_arg3  TYPE XMIARGTXT. "   

  CALL FUNCTION 'SHOM_REPORT_ORA_ERROR'  "
    EXPORTING
         MSGVALUE = lv_msgvalue
         TYPE3 = lv_type3
         ARG4 = lv_arg4
         TYPE4 = lv_type4
         MSGSEVERITY = lv_msgseverity
         MSGID = lv_msgid
         MSGNO = lv_msgno
         ARG1 = lv_arg1
         TYPE1 = lv_type1
         ARG2 = lv_arg2
         TYPE2 = lv_type2
         ARG3 = lv_arg3
    EXCEPTIONS
        COULD_NOT_BUILD_NODE = 1
        COULD_NOT_SEND_T100_MESSAGE = 2
        UNDETERMINED = 3
. " SHOM_REPORT_ORA_ERROR




ABAP code using 7.40 inline data declarations to call FM SHOM_REPORT_ORA_ERROR

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 VALUE FROM ALMSCRVAL INTO @DATA(ld_msgvalue).
 
 
DATA(ld_type3) = 'C'.
 
 
DATA(ld_type4) = 'C'.
 
"SELECT single SEVERITY FROM ALMSCRVAL INTO @DATA(ld_msgseverity).
 
 
"SELECT single MSGID FROM SY INTO @DATA(ld_msgid).
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno).
 
 
DATA(ld_type1) = 'C'.
 
 
DATA(ld_type2) = 'C'.
 
 


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!