SAP EXIT_SAPLWSO7_001 Function Module for Find Processor Group for Error Messages









EXIT_SAPLWSO7_001 is a standard exit saplwso7 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find Processor Group for Error Messages 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 exit saplwso7 001 FM, simply by entering the name EXIT_SAPLWSO7_001 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XSO7
Program Name: SAPLXSO7
Main Program:
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPLWSO7_001 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 'EXIT_SAPLWSO7_001'"Find Processor Group for Error Messages
EXPORTING
* I_MATNR = "
* I_KUNNR = "
* I_MATKL = "
* I_MTART = "
* I_WERKS = "
* I_LIFNR = "
* I_MSGNR = "
* I_ARBGB = "
* I_MSGTYP = "

CHANGING
I_OTYPE = "
I_OBJID = "

EXCEPTIONS
NO_ENTRY_FOUND = 1
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
CHECK_OBJECT_IN_DISCONTINUE_WF determine all workflow items containing an object (key check)
CHECK_OBJECT_IN_WF determine all workflow items containing an object
CHECK_OBJECT_KEY_IN_WF determine all workflow items containing an object (key check)
CHECK_OBJECT_PATTERN_IN_WF determine all workflow items containing an object pattern
CREATE_DISCONTINUATION_EVENTS Create an event for discontinuation process
DICONTINUATION_CREATE_EVENT create events in material discontinuation
GET_TASK_RESPONSIBLE determine person responsible for workflow task in IS-Retail
MATERIAL_LOGICAL_DELETE Delete Material logically and reset validity periods
MATERIAL_VALIDITY_UPDATE Change of validity period of material
MULTIPLE_MATERIAL_LOG_DELETE logical deletion of multiple mataerials and reset validity
OL_CHECK_MATERIAL Checking of a material for discontinuation
OL_PHYSICAL_DELETE physical deletion of a material
OL_PREPARE_OUTPUT Preparation of Error Protocol for display and Entry in Application Log
OL_SET_LVORM_MATERIAL Preparation for Setting/Unsetting of Deletion Incicators
READ_ACTORS_FOR_ERRORS read person responsible for error message
READ_DELAY_TIME_FOR_MATERIAL Read of time in days for physical deletion of an article
READ_FOLLOW_ACTIONS Read follow-on actions during article discontinuation
READ_MARC_FOR_REFPLANT read MARC for distribution line when specifying a reference site
READ_MESSAGES_FOR_ARBGB Read all messages of a message class
START_WF_FOR_MATNR_DELETE Start of workflow for logical/physical deletion
TASK_RESPONSIBLE_USER_EXIT call a user-exit

IMPORTING Parameters details for EXIT_SAPLWSO7_001

I_MATNR -

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

I_KUNNR -

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

I_MATKL -

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

I_MTART -

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

I_WERKS -

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

I_LIFNR -

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

I_MSGNR -

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

I_ARBGB -

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

I_MSGTYP -

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

CHANGING Parameters details for EXIT_SAPLWSO7_001

I_OTYPE -

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

I_OBJID -

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

EXCEPTIONS details

NO_ENTRY_FOUND -

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

Copy and paste ABAP code example for EXIT_SAPLWSO7_001 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_i_matnr  TYPE IMSEG-MATNR, "   
lv_i_otype  TYPE SWHACTOR-OTYPE, "   
lv_no_entry_found  TYPE SWHACTOR, "   
lv_i_kunnr  TYPE KNA1-KUNNR, "   
lv_i_objid  TYPE SWHACTOR-OBJID, "   
lv_i_matkl  TYPE MARA-MATKL, "   
lv_i_mtart  TYPE MARA-MTART, "   
lv_i_werks  TYPE IMSEG-WERKS, "   
lv_i_lifnr  TYPE IMSEG-LIFNR, "   
lv_i_msgnr  TYPE T100-MSGNR, "   
lv_i_arbgb  TYPE T100-ARBGB, "   
lv_i_msgtyp  TYPE WPLST-FEHLERTYP. "   

  CALL FUNCTION 'EXIT_SAPLWSO7_001'  "Find Processor Group for Error Messages
    EXPORTING
         I_MATNR = lv_i_matnr
         I_KUNNR = lv_i_kunnr
         I_MATKL = lv_i_matkl
         I_MTART = lv_i_mtart
         I_WERKS = lv_i_werks
         I_LIFNR = lv_i_lifnr
         I_MSGNR = lv_i_msgnr
         I_ARBGB = lv_i_arbgb
         I_MSGTYP = lv_i_msgtyp
    CHANGING
         I_OTYPE = lv_i_otype
         I_OBJID = lv_i_objid
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " EXIT_SAPLWSO7_001




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLWSO7_001

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 MATNR FROM IMSEG INTO @DATA(ld_i_matnr).
 
"SELECT single OTYPE FROM SWHACTOR INTO @DATA(ld_i_otype).
 
 
"SELECT single KUNNR FROM KNA1 INTO @DATA(ld_i_kunnr).
 
"SELECT single OBJID FROM SWHACTOR INTO @DATA(ld_i_objid).
 
"SELECT single MATKL FROM MARA INTO @DATA(ld_i_matkl).
 
"SELECT single MTART FROM MARA INTO @DATA(ld_i_mtart).
 
"SELECT single WERKS FROM IMSEG INTO @DATA(ld_i_werks).
 
"SELECT single LIFNR FROM IMSEG INTO @DATA(ld_i_lifnr).
 
"SELECT single MSGNR FROM T100 INTO @DATA(ld_i_msgnr).
 
"SELECT single ARBGB FROM T100 INTO @DATA(ld_i_arbgb).
 
"SELECT single FEHLERTYP FROM WPLST INTO @DATA(ld_i_msgtyp).
 


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!