SAP SCMA_UPD_LOG_CLOSE_RECORD Function Module for
SCMA_UPD_LOG_CLOSE_RECORD is a standard scma upd log close record 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 scma upd log close record FM, simply by entering the name SCMA_UPD_LOG_CLOSE_RECORD into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCMA_UPD_LOG
Program Name: SAPLSCMA_UPD_LOG
Main Program: SAPLSCMA_UPD_LOG
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCMA_UPD_LOG_CLOSE_RECORD 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 'SCMA_UPD_LOG_CLOSE_RECORD'".
EXPORTING
IS_MONITOR_KEY = "
* ID_UPD_TOTAL = "Total Number of Updates
IS_EVENT = "
EXCEPTIONS
FATAL_ERROR_IN_UPD_LOG = 1
IMPORTING Parameters details for SCMA_UPD_LOG_CLOSE_RECORD
IS_MONITOR_KEY -
Data type: SCHEDMAN_KEYOptional: No
Call by Reference: Yes
ID_UPD_TOTAL - Total Number of Updates
Data type: SCMAUPDLOG-UPD_TOTALOptional: Yes
Call by Reference: Yes
IS_EVENT -
Data type: SCMA_EVENTOptional: No
Call by Reference: Yes
EXCEPTIONS details
FATAL_ERROR_IN_UPD_LOG -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SCMA_UPD_LOG_CLOSE_RECORD 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_is_monitor_key | TYPE SCHEDMAN_KEY, " | |||
| lv_fatal_error_in_upd_log | TYPE SCHEDMAN_KEY, " | |||
| lv_id_upd_total | TYPE SCMAUPDLOG-UPD_TOTAL, " | |||
| lv_is_event | TYPE SCMA_EVENT. " |
|   CALL FUNCTION 'SCMA_UPD_LOG_CLOSE_RECORD' " |
| EXPORTING | ||
| IS_MONITOR_KEY | = lv_is_monitor_key | |
| ID_UPD_TOTAL | = lv_id_upd_total | |
| IS_EVENT | = lv_is_event | |
| EXCEPTIONS | ||
| FATAL_ERROR_IN_UPD_LOG = 1 | ||
| . " SCMA_UPD_LOG_CLOSE_RECORD | ||
ABAP code using 7.40 inline data declarations to call FM SCMA_UPD_LOG_CLOSE_RECORD
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 UPD_TOTAL FROM SCMAUPDLOG INTO @DATA(ld_id_upd_total). | ||||
Search for further information about these or an SAP related objects