SAP DB6_LOG_CONTINUE Function Module for DB6: Continue main job by child job
DB6_LOG_CONTINUE is a standard db6 log continue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DB6: Continue main job by child job 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 db6 log continue FM, simply by entering the name DB6_LOG_CONTINUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDBALOG
Program Name: SAPLSDBALOG
Main Program: SAPLSDBALOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DB6_LOG_CONTINUE 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 'DB6_LOG_CONTINUE'"DB6: Continue main job by child job.
EXPORTING
ACTION_ID = "Program ID as defined in table SDBAC
STARTTIME = "DB6: Timestamp (Format: YYYYMMDDHHMMSS)
PARTITN = "Partition Number
SYSTEM_ID = "Name of SAP R/3 System
EXCEPTIONS
INVALID_PARAMETER_SET = 1
IMPORTING Parameters details for DB6_LOG_CONTINUE
ACTION_ID - Program ID as defined in table SDBAC
Data type: SDBA_BTYPEOptional: No
Call by Reference: Yes
STARTTIME - DB6: Timestamp (Format: YYYYMMDDHHMMSS)
Data type: DB6TSTAMPOptional: No
Call by Reference: Yes
PARTITN - Partition Number
Data type: IOptional: No
Call by Reference: Yes
SYSTEM_ID - Name of SAP R/3 System
Data type: DB6NAVSYST-SYSIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_PARAMETER_SET -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DB6_LOG_CONTINUE 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_action_id | TYPE SDBA_BTYPE, " | |||
| lv_invalid_parameter_set | TYPE SDBA_BTYPE, " | |||
| lv_starttime | TYPE DB6TSTAMP, " | |||
| lv_partitn | TYPE I, " | |||
| lv_system_id | TYPE DB6NAVSYST-SYSID. " |
|   CALL FUNCTION 'DB6_LOG_CONTINUE' "DB6: Continue main job by child job |
| EXPORTING | ||
| ACTION_ID | = lv_action_id | |
| STARTTIME | = lv_starttime | |
| PARTITN | = lv_partitn | |
| SYSTEM_ID | = lv_system_id | |
| EXCEPTIONS | ||
| INVALID_PARAMETER_SET = 1 | ||
| . " DB6_LOG_CONTINUE | ||
ABAP code using 7.40 inline data declarations to call FM DB6_LOG_CONTINUE
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 SYSID FROM DB6NAVSYST INTO @DATA(ld_system_id). | ||||
Search for further information about these or an SAP related objects