SAP STATUS_SELSCHEM_EXIST Function Module for Existence Check for Status Selection Profile
STATUS_SELSCHEM_EXIST is a standard status selschem exist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Existence Check for Status Selection Profile 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 status selschem exist FM, simply by entering the name STATUS_SELSCHEM_EXIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSVS
Program Name: SAPLBSVS
Main Program:
Appliation area:
Release date: 11-Sep-1998
Mode(Normal, Remote etc): Normal Function Module
Update:
Function STATUS_SELSCHEM_EXIST 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 'STATUS_SELSCHEM_EXIST'"Existence Check for Status Selection Profile.
EXPORTING
SELID = "Status Selection Profile
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for STATUS_SELSCHEM_EXIST
SELID - Status Selection Profile
Data type: TJ48-SELIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Profile Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STATUS_SELSCHEM_EXIST 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_selid | TYPE TJ48-SELID, " | |||
lv_not_found | TYPE TJ48. " |
  CALL FUNCTION 'STATUS_SELSCHEM_EXIST' "Existence Check for Status Selection Profile |
EXPORTING | ||
SELID | = lv_selid | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
. " STATUS_SELSCHEM_EXIST |
ABAP code using 7.40 inline data declarations to call FM STATUS_SELSCHEM_EXIST
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 SELID FROM TJ48 INTO @DATA(ld_selid). | ||||
Search for further information about these or an SAP related objects