SAP SUSP_SU24_DARK_INSERT_OBJLIST Function Module for
SUSP_SU24_DARK_INSERT_OBJLIST is a standard susp su24 dark insert objlist 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 susp su24 dark insert objlist FM, simply by entering the name SUSP_SU24_DARK_INSERT_OBJLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUSP
Program Name: SAPLSUSP
Main Program: SAPLSUSP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SUSP_SU24_DARK_INSERT_OBJLIST 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 'SUSP_SU24_DARK_INSERT_OBJLIST'".
IMPORTING
NUM_INSERTED = "Number of check indicator entries inserted
TABLES
P_USOBX_C = "Check indicator
* P_USOBT_C = "Field values
EXCEPTIONS
BAD_TYPE = 1 LOCKED_BY_ANOTHER_USER = 10 NAME_NOT_DEFINED = 2 TABLE_P_USOBX_C_EMPTY = 3 WRONG_OKFLAG = 4 INCONSISTENT_ENTRIES = 5 NO_ENTRIES_INSERTED = 6 INSERT_FAILED = 7 NOT_AUTHORIZED = 8 ERROR_IN_LOCK_MANAGEMENT = 9
EXPORTING Parameters details for SUSP_SU24_DARK_INSERT_OBJLIST
NUM_INSERTED - Number of check indicator entries inserted
Data type: SY-DBCNTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SUSP_SU24_DARK_INSERT_OBJLIST
P_USOBX_C - Check indicator
Data type: USOBX_COptional: No
Call by Reference: No ( called with pass by value option)
P_USOBT_C - Field values
Data type: USOBT_COptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BAD_TYPE - Incorrect type (only 'TR' currently allowed)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOCKED_BY_ANOTHER_USER - Objects transferred locked by other user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NAME_NOT_DEFINED - Name (with respect to type) not defined
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_P_USOBX_C_EMPTY - No auth. object with check indicator transferred to P_USOBX_C
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_OKFLAG - Only N, X, Y for check indicator; For S*/P* objects, only X, Y
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INCONSISTENT_ENTRIES - More/fewer auth. obj. fld values than with check indicator 'Y'
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ENTRIES_INSERTED - No entries inserted (due to correction dialog box)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INSERT_FAILED - Failed to insert check indicator / field value
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED - Insert not possible as new check is inactive
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_IN_LOCK_MANAGEMENT - Error in lock management
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUSP_SU24_DARK_INSERT_OBJLIST 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_bad_type | TYPE STRING, " | |||
| lt_p_usobx_c | TYPE STANDARD TABLE OF USOBX_C, " | |||
| lv_num_inserted | TYPE SY-DBCNT, " | |||
| lv_locked_by_another_user | TYPE SY, " | |||
| lt_p_usobt_c | TYPE STANDARD TABLE OF USOBT_C, " | |||
| lv_name_not_defined | TYPE USOBT_C, " | |||
| lv_table_p_usobx_c_empty | TYPE USOBT_C, " | |||
| lv_wrong_okflag | TYPE USOBT_C, " | |||
| lv_inconsistent_entries | TYPE USOBT_C, " | |||
| lv_no_entries_inserted | TYPE USOBT_C, " | |||
| lv_insert_failed | TYPE USOBT_C, " | |||
| lv_not_authorized | TYPE USOBT_C, " | |||
| lv_error_in_lock_management | TYPE USOBT_C. " |
|   CALL FUNCTION 'SUSP_SU24_DARK_INSERT_OBJLIST' " |
| IMPORTING | ||
| NUM_INSERTED | = lv_num_inserted | |
| TABLES | ||
| P_USOBX_C | = lt_p_usobx_c | |
| P_USOBT_C | = lt_p_usobt_c | |
| EXCEPTIONS | ||
| BAD_TYPE = 1 | ||
| LOCKED_BY_ANOTHER_USER = 10 | ||
| NAME_NOT_DEFINED = 2 | ||
| TABLE_P_USOBX_C_EMPTY = 3 | ||
| WRONG_OKFLAG = 4 | ||
| INCONSISTENT_ENTRIES = 5 | ||
| NO_ENTRIES_INSERTED = 6 | ||
| INSERT_FAILED = 7 | ||
| NOT_AUTHORIZED = 8 | ||
| ERROR_IN_LOCK_MANAGEMENT = 9 | ||
| . " SUSP_SU24_DARK_INSERT_OBJLIST | ||
ABAP code using 7.40 inline data declarations to call FM SUSP_SU24_DARK_INSERT_OBJLIST
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 DBCNT FROM SY INTO @DATA(ld_num_inserted). | ||||
Search for further information about these or an SAP related objects