SAP SUPRN_IS_ORG Function Module for
SUPRN_IS_ORG is a standard suprn is org 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 suprn is org FM, simply by entering the name SUPRN_IS_ORG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUPRN
Program Name: SAPLSUPRN
Main Program: SAPLSUPRN
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SUPRN_IS_ORG 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 'SUPRN_IS_ORG'".
EXPORTING
FIELD = "
IMPORTING
VARBL = "
VTEXT = "
EXCEPTIONS
FIELD_IS_NO_ORG = 1
IMPORTING Parameters details for SUPRN_IS_ORG
FIELD -
Data type: USORG-FIELDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUPRN_IS_ORG
VARBL -
Data type: USORG-VARBLOptional: No
Call by Reference: No ( called with pass by value option)
VTEXT -
Data type: USVART-VTEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FIELD_IS_NO_ORG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUPRN_IS_ORG 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_field | TYPE USORG-FIELD, " | |||
lv_varbl | TYPE USORG-VARBL, " | |||
lv_field_is_no_org | TYPE USORG, " | |||
lv_vtext | TYPE USVART-VTEXT. " |
  CALL FUNCTION 'SUPRN_IS_ORG' " |
EXPORTING | ||
FIELD | = lv_field | |
IMPORTING | ||
VARBL | = lv_varbl | |
VTEXT | = lv_vtext | |
EXCEPTIONS | ||
FIELD_IS_NO_ORG = 1 | ||
. " SUPRN_IS_ORG |
ABAP code using 7.40 inline data declarations to call FM SUPRN_IS_ORG
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 FIELD FROM USORG INTO @DATA(ld_field). | ||||
"SELECT single VARBL FROM USORG INTO @DATA(ld_varbl). | ||||
"SELECT single VTEXT FROM USVART INTO @DATA(ld_vtext). | ||||
Search for further information about these or an SAP related objects