SAP UMB_API_WRITE_LOCK_REQUEST Function Module for

Search SAP Function Modules

UMB_API_WRITE_LOCK_REQUEST is a standard umb api write lock request 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 umb api write lock request FM, simply by entering the name UMB_API_WRITE_LOCK_REQUEST into the relevant SAP transaction such as SE37 or SE38.

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

Function UMB_API_WRITE_LOCK_REQUEST 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 'UMB_API_WRITE_LOCK_REQUEST'"
  EXPORTING
   I_SCARD =  "
   IS_ELEMENT =  "
   I_CURPER =  "
   I_TARPER =  "
   I_DETAIL =  "

 IMPORTING
   E_OUTPUT =  "

EXCEPTIONS
   INVALID_SCARD = 1    INVALID_ELEMENT = 2    LOCKING_FAILED = 3    NOT_AUTHORISED = 4 

.

IMPORTING Parameters details for UMB_API_WRITE_LOCK_REQUEST

I_SCARD -

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

IS_ELEMENT -

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

I_CURPER -

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

I_TARPER -

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

I_DETAIL -

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

EXPORTING Parameters details for UMB_API_WRITE_LOCK_REQUEST

E_OUTPUT -

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

EXCEPTIONS details

INVALID_SCARD -

Data type:
Optional: No
Call by Reference: Yes

INVALID_ELEMENT -

Data type:
Optional: No
Call by Reference: Yes

LOCKING_FAILED -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORISED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UMB_API_WRITE_LOCK_REQUEST 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.

ABAP code using 7.40 inline data declarations to call FM UMB_API_WRITE_LOCK_REQUEST

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