SAP RESTORE_SMODISRC_PROTOCOL Function Module for
RESTORE_SMODISRC_PROTOCOL is a standard restore smodisrc protocol 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 restore smodisrc protocol FM, simply by entering the name RESTORE_SMODISRC_PROTOCOL into the relevant SAP transaction such as SE37 or SE38.
Function Group: LOCAL_EDT1
Program Name: SAPLLOCAL_EDT1
Main Program: SAPLLOCAL_EDT1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RESTORE_SMODISRC_PROTOCOL 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 'RESTORE_SMODISRC_PROTOCOL'".
EXPORTING
STATE = "ABAP: Program Status (Active, Saved, Transported...)
* OBJTYPE = "Object Type
* OBJNAME = "ABAP/4 Development Workbench: LIMU name
SUBTYPE = "Object Type
SUBNAME = "ABAP/4 Development Workbench: LIMU name
TABLES
SMODILOG_TAB = "Log of Customer Modifications to Dev. Env. Objects
NEW_SOURCE = "ABAP Text Line with Length 255
SMODISRC_TAB = "Customer Modification Log: Object Data (Active)
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLLOCAL_EDT1_001 User Exit for Editor (Dynamic Pattern)
EXIT_SAPLLOCAL_EDT1_002 User's Own Function Code in ABAP Editor
IMPORTING Parameters details for RESTORE_SMODISRC_PROTOCOL
STATE - ABAP: Program Status (Active, Saved, Transported...)
Data type: PROGDIR-STATEOptional: No
Call by Reference: Yes
OBJTYPE - Object Type
Data type: SMODILOG-OBJ_TYPEOptional: Yes
Call by Reference: Yes
OBJNAME - ABAP/4 Development Workbench: LIMU name
Data type: SMODILOG-OBJ_NAMEOptional: Yes
Call by Reference: Yes
SUBTYPE - Object Type
Data type: SMODILOG-SUB_TYPEOptional: No
Call by Reference: Yes
SUBNAME - ABAP/4 Development Workbench: LIMU name
Data type: SMODILOG-SUB_NAMEOptional: No
Call by Reference: Yes
TABLES Parameters details for RESTORE_SMODISRC_PROTOCOL
SMODILOG_TAB - Log of Customer Modifications to Dev. Env. Objects
Data type: SMODILOGOptional: No
Call by Reference: Yes
NEW_SOURCE - ABAP Text Line with Length 255
Data type: ABAPTXT255Optional: No
Call by Reference: Yes
SMODISRC_TAB - Customer Modification Log: Object Data (Active)
Data type: SMODISRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RESTORE_SMODISRC_PROTOCOL 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_state | TYPE PROGDIR-STATE, " | |||
lt_smodilog_tab | TYPE STANDARD TABLE OF SMODILOG, " | |||
lv_objtype | TYPE SMODILOG-OBJ_TYPE, " | |||
lt_new_source | TYPE STANDARD TABLE OF ABAPTXT255, " | |||
lv_objname | TYPE SMODILOG-OBJ_NAME, " | |||
lt_smodisrc_tab | TYPE STANDARD TABLE OF SMODISRC, " | |||
lv_subtype | TYPE SMODILOG-SUB_TYPE, " | |||
lv_subname | TYPE SMODILOG-SUB_NAME. " |
  CALL FUNCTION 'RESTORE_SMODISRC_PROTOCOL' " |
EXPORTING | ||
STATE | = lv_state | |
OBJTYPE | = lv_objtype | |
OBJNAME | = lv_objname | |
SUBTYPE | = lv_subtype | |
SUBNAME | = lv_subname | |
TABLES | ||
SMODILOG_TAB | = lt_smodilog_tab | |
NEW_SOURCE | = lt_new_source | |
SMODISRC_TAB | = lt_smodisrc_tab | |
. " RESTORE_SMODISRC_PROTOCOL |
ABAP code using 7.40 inline data declarations to call FM RESTORE_SMODISRC_PROTOCOL
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 STATE FROM PROGDIR INTO @DATA(ld_state). | ||||
"SELECT single OBJ_TYPE FROM SMODILOG INTO @DATA(ld_objtype). | ||||
"SELECT single OBJ_NAME FROM SMODILOG INTO @DATA(ld_objname). | ||||
"SELECT single SUB_TYPE FROM SMODILOG INTO @DATA(ld_subtype). | ||||
"SELECT single SUB_NAME FROM SMODILOG INTO @DATA(ld_subname). | ||||
Search for further information about these or an SAP related objects