SAP DTL_SEMAPHORE_DEFINE Function Module for API: Assign semaphore values to sender, receiver and DTL system









DTL_SEMAPHORE_DEFINE is a standard dtl semaphore define SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for API: Assign semaphore values to sender, receiver and DTL system 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 dtl semaphore define FM, simply by entering the name DTL_SEMAPHORE_DEFINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DMC_DTL
Program Name: SAPLDMC_DTL
Main Program: SAPLDMC_DTL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function DTL_SEMAPHORE_DEFINE 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 'DTL_SEMAPHORE_DEFINE'"API: Assign semaphore values to sender, receiver and DTL system
  EXPORTING
   I_SUBPROJECT =  "Bezeichner f. Subprojekte
*  I_PACKID =  "Package number to specify CMIS and TDMS packages
   I_SESSION_ID =  "MBT PCL SESSION_ID

 IMPORTING
   E_LOGNUMBER =  "Anwendungs-Log: Protokollnummer
   E_STATUS =  "Status info for MWB activities
   ET_RFC_SETTINGS =  "
   E_NO_OF_JOBS =  "Two digit number

TABLES
*  IT_SEM_PRCT =  "% values applied to host's load values
.



IMPORTING Parameters details for DTL_SEMAPHORE_DEFINE

I_SUBPROJECT - Bezeichner f. Subprojekte

Data type: DMC_SIDENT
Optional: No
Call by Reference: No ( called with pass by value option)

I_PACKID - Package number to specify CMIS and TDMS packages

Data type: DMC_PACKAGE_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SESSION_ID - MBT PCL SESSION_ID

Data type: DMC_SESSION_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for DTL_SEMAPHORE_DEFINE

E_LOGNUMBER - Anwendungs-Log: Protokollnummer

Data type: BALOGNR
Optional: No
Call by Reference: No ( called with pass by value option)

E_STATUS - Status info for MWB activities

Data type: DMC_ACTIVITY_STATUS_INFO
Optional: No
Call by Reference: No ( called with pass by value option)

ET_RFC_SETTINGS -

Data type: DMC_RFC_SETTINGS_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

E_NO_OF_JOBS - Two digit number

Data type: NUMC2
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DTL_SEMAPHORE_DEFINE

IT_SEM_PRCT - % values applied to host's load values

Data type: DTL_SEMAPHORE_PRCT_TAB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for DTL_SEMAPHORE_DEFINE 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_e_lognumber  TYPE BALOGNR, "   
lt_it_sem_prct  TYPE STANDARD TABLE OF DTL_SEMAPHORE_PRCT_TAB, "   
lv_i_subproject  TYPE DMC_SIDENT, "   
lv_e_status  TYPE DMC_ACTIVITY_STATUS_INFO, "   
lv_i_packid  TYPE DMC_PACKAGE_ID, "   
lv_i_session_id  TYPE DMC_SESSION_ID, "   
lv_et_rfc_settings  TYPE DMC_RFC_SETTINGS_TAB, "   
lv_e_no_of_jobs  TYPE NUMC2. "   

  CALL FUNCTION 'DTL_SEMAPHORE_DEFINE'  "API: Assign semaphore values to sender, receiver and DTL system
    EXPORTING
         I_SUBPROJECT = lv_i_subproject
         I_PACKID = lv_i_packid
         I_SESSION_ID = lv_i_session_id
    IMPORTING
         E_LOGNUMBER = lv_e_lognumber
         E_STATUS = lv_e_status
         ET_RFC_SETTINGS = lv_et_rfc_settings
         E_NO_OF_JOBS = lv_e_no_of_jobs
    TABLES
         IT_SEM_PRCT = lt_it_sem_prct
. " DTL_SEMAPHORE_DEFINE




ABAP code using 7.40 inline data declarations to call FM DTL_SEMAPHORE_DEFINE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!