SAP DD_LOGNPROT_NAME_GET Function Module for Module which determines log name and job name for activat./convers. prog.
DD_LOGNPROT_NAME_GET is a standard dd lognprot name get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Module which determines log name and job name for activat./convers. prog. 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 dd lognprot name get FM, simply by entering the name DD_LOGNPROT_NAME_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDAP
Program Name: SAPLSDAP
Main Program: SAPLSDAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_LOGNPROT_NAME_GET 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 'DD_LOGNPROT_NAME_GET'"Module which determines log name and job name for activat./convers. prog..
EXPORTING
* TASK = 'CNV' "ACT (activate), TAC (TACOB), CNV (DB util.)
* SINGLE_OR_MASS = 'S' "S = SINGLE, M = MASS
* OBJ_TYPE = 'TABL' "TABL,INDX,VIEW,SQLT,DTEL,DOMA
* ONLINE_PUT = 'O' "O = Online, TACOB, TBATG, P = Upgrade
* OBJ_NAME = ' ' "name of table, view, ...
* IND_NAME = ' ' "name of index, if any
* DATE_IN = ' ' "
* TIME_IN = ' ' "
* READ = "
IMPORTING
PROTNAME = "name of ddic protocol for single processing
PROTNAME_TEMPLATE = "template name of ddic protocol
JOBNAME = "name of batch job for single procesing
JOBNAME_TEMPLATE = "template name of batch job
EXCEPTIONS
INPUT_ERROR = 1
IMPORTING Parameters details for DD_LOGNPROT_NAME_GET
TASK - ACT (activate), TAC (TACOB), CNV (DB util.)
Data type:Default: 'CNV'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SINGLE_OR_MASS - S = SINGLE, M = MASS
Data type:Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE - TABL,INDX,VIEW,SQLT,DTEL,DOMA
Data type:Default: 'TABL'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ONLINE_PUT - O = Online, TACOB, TBATG, P = Upgrade
Data type:Default: 'O'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_NAME - name of table, view, ...
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IND_NAME - name of index, if any
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATE_IN -
Data type: SY-DATUMDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TIME_IN -
Data type: SY-UZEITDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
READ -
Data type: DDBOOL_DOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_LOGNPROT_NAME_GET
PROTNAME - name of ddic protocol for single processing
Data type: TSTRF01-FILEOptional: No
Call by Reference: No ( called with pass by value option)
PROTNAME_TEMPLATE - template name of ddic protocol
Data type: TSTRF01-FILEOptional: No
Call by Reference: No ( called with pass by value option)
JOBNAME - name of batch job for single procesing
Data type: TBTCJOB-JOBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
JOBNAME_TEMPLATE - template name of batch job
Data type: TBTCJOB-JOBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INPUT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_LOGNPROT_NAME_GET 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_task | TYPE STRING, " 'CNV' | |||
| lv_protname | TYPE TSTRF01-FILE, " | |||
| lv_input_error | TYPE TSTRF01, " | |||
| lv_single_or_mass | TYPE TSTRF01, " 'S' | |||
| lv_protname_template | TYPE TSTRF01-FILE, " | |||
| lv_jobname | TYPE TBTCJOB-JOBNAME, " | |||
| lv_obj_type | TYPE TBTCJOB, " 'TABL' | |||
| lv_online_put | TYPE TBTCJOB, " 'O' | |||
| lv_jobname_template | TYPE TBTCJOB-JOBNAME, " | |||
| lv_obj_name | TYPE TBTCJOB, " ' ' | |||
| lv_ind_name | TYPE TBTCJOB, " ' ' | |||
| lv_date_in | TYPE SY-DATUM, " ' ' | |||
| lv_time_in | TYPE SY-UZEIT, " ' ' | |||
| lv_read | TYPE DDBOOL_D. " |
|   CALL FUNCTION 'DD_LOGNPROT_NAME_GET' "Module which determines log name and job name for activat./convers. prog. |
| EXPORTING | ||
| TASK | = lv_task | |
| SINGLE_OR_MASS | = lv_single_or_mass | |
| OBJ_TYPE | = lv_obj_type | |
| ONLINE_PUT | = lv_online_put | |
| OBJ_NAME | = lv_obj_name | |
| IND_NAME | = lv_ind_name | |
| DATE_IN | = lv_date_in | |
| TIME_IN | = lv_time_in | |
| READ | = lv_read | |
| IMPORTING | ||
| PROTNAME | = lv_protname | |
| PROTNAME_TEMPLATE | = lv_protname_template | |
| JOBNAME | = lv_jobname | |
| JOBNAME_TEMPLATE | = lv_jobname_template | |
| EXCEPTIONS | ||
| INPUT_ERROR = 1 | ||
| . " DD_LOGNPROT_NAME_GET | ||
ABAP code using 7.40 inline data declarations to call FM DD_LOGNPROT_NAME_GET
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.| DATA(ld_task) | = 'CNV'. | |||
| "SELECT single FILE FROM TSTRF01 INTO @DATA(ld_protname). | ||||
| DATA(ld_single_or_mass) | = 'S'. | |||
| "SELECT single FILE FROM TSTRF01 INTO @DATA(ld_protname_template). | ||||
| "SELECT single JOBNAME FROM TBTCJOB INTO @DATA(ld_jobname). | ||||
| DATA(ld_obj_type) | = 'TABL'. | |||
| DATA(ld_online_put) | = 'O'. | |||
| "SELECT single JOBNAME FROM TBTCJOB INTO @DATA(ld_jobname_template). | ||||
| DATA(ld_obj_name) | = ' '. | |||
| DATA(ld_ind_name) | = ' '. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date_in). | ||||
| DATA(ld_date_in) | = ' '. | |||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_time_in). | ||||
| DATA(ld_time_in) | = ' '. | |||
Search for further information about these or an SAP related objects