SAP ISU_DB_INNERJOIN_ERDO_SELECT Function Module for INTERNAL: Select Invoicing Outsorting by Diverse Parameters
ISU_DB_INNERJOIN_ERDO_SELECT is a standard isu db innerjoin erdo select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Select Invoicing Outsorting by Diverse Parameters 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 isu db innerjoin erdo select FM, simply by entering the name ISU_DB_INNERJOIN_ERDO_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EVDB
Program Name: SAPLEVDB
Main Program: SAPLEVDB
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISU_DB_INNERJOIN_ERDO_SELECT 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 'ISU_DB_INNERJOIN_ERDO_SELECT'"INTERNAL: Select Invoicing Outsorting by Diverse Parameters.
EXPORTING
* X_RELEASED = '' "
* X_CANCELLED = '' "
* X_SIMULATED = '' "Simulation Type
* X_MAXHITS = 0 "Maximum Number of Hits
* X_TOBERELEASE = "
TABLES
* T_PORTION = "
* T_VKONT = "Selected Contract Accounts
* T_GPARTNER = "
* T_OPBEL = "
* T_VALIDIN = "
* T_MANOTIN = "
* T_V_ERDO = "Result of Selection
EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2
IMPORTING Parameters details for ISU_DB_INNERJOIN_ERDO_SELECT
X_RELEASED -
Data type: REGEN-KENNZXDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_CANCELLED -
Data type: REGEN-KENNZXDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_SIMULATED - Simulation Type
Data type: ERDK-SIMULATEDDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_MAXHITS - Maximum Number of Hits
Data type: RSEUMOD-TBMAXSELOptional: Yes
Call by Reference: No ( called with pass by value option)
X_TOBERELEASE -
Data type: FLAGOptional: Yes
Call by Reference: Yes
TABLES Parameters details for ISU_DB_INNERJOIN_ERDO_SELECT
T_PORTION -
Data type: ISU20_RANGES_8Optional: Yes
Call by Reference: No ( called with pass by value option)
T_VKONT - Selected Contract Accounts
Data type: ISU20_RANGES_12Optional: Yes
Call by Reference: No ( called with pass by value option)
T_GPARTNER -
Data type: ISU20_RANGES_10Optional: Yes
Call by Reference: No ( called with pass by value option)
T_OPBEL -
Data type: ISU20_RANGES_12Optional: Yes
Call by Reference: No ( called with pass by value option)
T_VALIDIN -
Data type: ISU20_RANGES_10Optional: Yes
Call by Reference: Yes
T_MANOTIN -
Data type: ISU20_RANGES_8Optional: Yes
Call by Reference: Yes
T_V_ERDO - Result of Selection
Data type: V_ERDOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DB_INNERJOIN_ERDO_SELECT 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_not_found | TYPE STRING, " | |||
lt_t_portion | TYPE STANDARD TABLE OF ISU20_RANGES_8, " | |||
lv_x_released | TYPE REGEN-KENNZX, " '' | |||
lt_t_vkont | TYPE STANDARD TABLE OF ISU20_RANGES_12, " | |||
lv_x_cancelled | TYPE REGEN-KENNZX, " '' | |||
lv_system_error | TYPE REGEN, " | |||
lt_t_gpartner | TYPE STANDARD TABLE OF ISU20_RANGES_10, " | |||
lv_x_simulated | TYPE ERDK-SIMULATED, " '' | |||
lt_t_opbel | TYPE STANDARD TABLE OF ISU20_RANGES_12, " | |||
lv_x_maxhits | TYPE RSEUMOD-TBMAXSEL, " 0 | |||
lt_t_validin | TYPE STANDARD TABLE OF ISU20_RANGES_10, " | |||
lv_x_toberelease | TYPE FLAG, " | |||
lt_t_manotin | TYPE STANDARD TABLE OF ISU20_RANGES_8, " | |||
lt_t_v_erdo | TYPE STANDARD TABLE OF V_ERDO. " |
  CALL FUNCTION 'ISU_DB_INNERJOIN_ERDO_SELECT' "INTERNAL: Select Invoicing Outsorting by Diverse Parameters |
EXPORTING | ||
X_RELEASED | = lv_x_released | |
X_CANCELLED | = lv_x_cancelled | |
X_SIMULATED | = lv_x_simulated | |
X_MAXHITS | = lv_x_maxhits | |
X_TOBERELEASE | = lv_x_toberelease | |
TABLES | ||
T_PORTION | = lt_t_portion | |
T_VKONT | = lt_t_vkont | |
T_GPARTNER | = lt_t_gpartner | |
T_OPBEL | = lt_t_opbel | |
T_VALIDIN | = lt_t_validin | |
T_MANOTIN | = lt_t_manotin | |
T_V_ERDO | = lt_t_v_erdo | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
SYSTEM_ERROR = 2 | ||
. " ISU_DB_INNERJOIN_ERDO_SELECT |
ABAP code using 7.40 inline data declarations to call FM ISU_DB_INNERJOIN_ERDO_SELECT
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 KENNZX FROM REGEN INTO @DATA(ld_x_released). | ||||
DATA(ld_x_released) | = ''. | |||
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_cancelled). | ||||
DATA(ld_x_cancelled) | = ''. | |||
"SELECT single SIMULATED FROM ERDK INTO @DATA(ld_x_simulated). | ||||
DATA(ld_x_simulated) | = ''. | |||
"SELECT single TBMAXSEL FROM RSEUMOD INTO @DATA(ld_x_maxhits). | ||||
Search for further information about these or an SAP related objects