SAP OCS_DELETE_BATCH_SEMAPHORE Function Module for
OCS_DELETE_BATCH_SEMAPHORE is a standard ocs delete batch semaphore 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 ocs delete batch semaphore FM, simply by entering the name OCS_DELETE_BATCH_SEMAPHORE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OCS_BATCH
Program Name: SAPLOCS_BATCH
Main Program: SAPLOCS_BATCH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OCS_DELETE_BATCH_SEMAPHORE 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 'OCS_DELETE_BATCH_SEMAPHORE'".
EXPORTING
IV_TOOL = "
* IV_SEM_STATE = 'A' "Status of the OCS Semaphore Entry
EXCEPTIONS
FOREIGN_LOCK = 1 NO_OCS_SEMAPHORE = 2 INTERNAL_ERROR = 3
IMPORTING Parameters details for OCS_DELETE_BATCH_SEMAPHORE
IV_TOOL -
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_SEM_STATE - Status of the OCS Semaphore Entry
Data type: PAT10B-SEM_STATEDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: Yes
NO_OCS_SEMAPHORE -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OCS_DELETE_BATCH_SEMAPHORE 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_iv_tool | TYPE SY-TCODE, " | |||
| lv_foreign_lock | TYPE SY, " | |||
| lv_iv_sem_state | TYPE PAT10B-SEM_STATE, " 'A' | |||
| lv_no_ocs_semaphore | TYPE PAT10B, " | |||
| lv_internal_error | TYPE PAT10B. " |
|   CALL FUNCTION 'OCS_DELETE_BATCH_SEMAPHORE' " |
| EXPORTING | ||
| IV_TOOL | = lv_iv_tool | |
| IV_SEM_STATE | = lv_iv_sem_state | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| NO_OCS_SEMAPHORE = 2 | ||
| INTERNAL_ERROR = 3 | ||
| . " OCS_DELETE_BATCH_SEMAPHORE | ||
ABAP code using 7.40 inline data declarations to call FM OCS_DELETE_BATCH_SEMAPHORE
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 TCODE FROM SY INTO @DATA(ld_iv_tool). | ||||
| "SELECT single SEM_STATE FROM PAT10B INTO @DATA(ld_iv_sem_state). | ||||
| DATA(ld_iv_sem_state) | = 'A'. | |||
Search for further information about these or an SAP related objects