SAP ISU_EDM_STATUS_INSERT_RANGE Function Module for Insert Status Time Area in Existing Status Table
ISU_EDM_STATUS_INSERT_RANGE is a standard isu edm status insert range SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Insert Status Time Area in Existing Status Table 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 edm status insert range FM, simply by entering the name ISU_EDM_STATUS_INSERT_RANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEDM_STATUS
Program Name: SAPLEEDM_STATUS
Main Program: SAPLEEDM_STATUS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_EDM_STATUS_INSERT_RANGE 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_EDM_STATUS_INSERT_RANGE'"Insert Status Time Area in Existing Status Table.
EXPORTING
X_STATUS_CURRENT_UTC = "Table of Status Data for Profile Values (Sorted) in UTC
X_STATUS_INSERT_UTC = "Table of Status Data for Profile Values (Sorted) in UTC
X_FROM_UTC = "Structure for Profile Validity Period 'From' in UTC Time
X_TO_UTC = "Structure for Profile Validity Period 'To' in UTC Time
X_TIMEZONE = "Time Zone of Non-UTC Data
IMPORTING
Y_STATUS_MIXED_UTC = "Table of Status Data for Profile Values (Sorted) in UTC
Y_STATUS_MIXED = "Table of Status Data for Profile Values (Sorted)
IMPORTING Parameters details for ISU_EDM_STATUS_INSERT_RANGE
X_STATUS_CURRENT_UTC - Table of Status Data for Profile Values (Sorted) in UTC
Data type: TEPROFSTATUS_UTCOptional: No
Call by Reference: Yes
X_STATUS_INSERT_UTC - Table of Status Data for Profile Values (Sorted) in UTC
Data type: TEPROFSTATUS_UTCOptional: No
Call by Reference: Yes
X_FROM_UTC - Structure for Profile Validity Period 'From' in UTC Time
Data type: EPROFTIME_FROM_UTCOptional: No
Call by Reference: Yes
X_TO_UTC - Structure for Profile Validity Period 'To' in UTC Time
Data type: EPROFTIME_TO_UTCOptional: No
Call by Reference: Yes
X_TIMEZONE - Time Zone of Non-UTC Data
Data type: TIMEZONEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_EDM_STATUS_INSERT_RANGE
Y_STATUS_MIXED_UTC - Table of Status Data for Profile Values (Sorted) in UTC
Data type: TEPROFSTATUS_UTCOptional: No
Call by Reference: Yes
Y_STATUS_MIXED - Table of Status Data for Profile Values (Sorted)
Data type: TEPROFSTATUSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_EDM_STATUS_INSERT_RANGE 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_y_status_mixed_utc | TYPE TEPROFSTATUS_UTC, " | |||
| lv_x_status_current_utc | TYPE TEPROFSTATUS_UTC, " | |||
| lv_y_status_mixed | TYPE TEPROFSTATUS, " | |||
| lv_x_status_insert_utc | TYPE TEPROFSTATUS_UTC, " | |||
| lv_x_from_utc | TYPE EPROFTIME_FROM_UTC, " | |||
| lv_x_to_utc | TYPE EPROFTIME_TO_UTC, " | |||
| lv_x_timezone | TYPE TIMEZONE. " |
|   CALL FUNCTION 'ISU_EDM_STATUS_INSERT_RANGE' "Insert Status Time Area in Existing Status Table |
| EXPORTING | ||
| X_STATUS_CURRENT_UTC | = lv_x_status_current_utc | |
| X_STATUS_INSERT_UTC | = lv_x_status_insert_utc | |
| X_FROM_UTC | = lv_x_from_utc | |
| X_TO_UTC | = lv_x_to_utc | |
| X_TIMEZONE | = lv_x_timezone | |
| IMPORTING | ||
| Y_STATUS_MIXED_UTC | = lv_y_status_mixed_utc | |
| Y_STATUS_MIXED | = lv_y_status_mixed | |
| . " ISU_EDM_STATUS_INSERT_RANGE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_EDM_STATUS_INSERT_RANGE
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.Search for further information about these or an SAP related objects