SAP ISU_BBP_INPUT_LOCK_REASON Function Module for
ISU_BBP_INPUT_LOCK_REASON is a standard isu bbp input lock reason 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 isu bbp input lock reason FM, simply by entering the name ISU_BBP_INPUT_LOCK_REASON into the relevant SAP transaction such as SE37 or SE38.
Function Group: EA61EFF
Program Name: SAPLEA61EFF
Main Program: SAPLEA61EFF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_BBP_INPUT_LOCK_REASON 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 'ISU_BBP_INPUT_LOCK_REASON'".
EXPORTING
X_PROID = "
* X_REA61 = "
* X_REA63 = "
CHANGING
XY_LOCKLINE = "
XY_EABPS = "
IMPORTING Parameters details for ISU_BBP_INPUT_LOCK_REASON
X_PROID -
Data type: DFKKLOCKS-PROIDOptional: No
Call by Reference: Yes
X_REA61 -
Data type: REA61Optional: Yes
Call by Reference: Yes
X_REA63 -
Data type: REA63Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for ISU_BBP_INPUT_LOCK_REASON
XY_LOCKLINE -
Data type: ISU25_LOCKLINEOptional: No
Call by Reference: Yes
XY_EABPS -
Data type: EABPSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_BBP_INPUT_LOCK_REASON 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_x_proid | TYPE DFKKLOCKS-PROID, " | |||
| lv_xy_lockline | TYPE ISU25_LOCKLINE, " | |||
| lv_x_rea61 | TYPE REA61, " | |||
| lv_xy_eabps | TYPE EABPS, " | |||
| lv_x_rea63 | TYPE REA63. " |
|   CALL FUNCTION 'ISU_BBP_INPUT_LOCK_REASON' " |
| EXPORTING | ||
| X_PROID | = lv_x_proid | |
| X_REA61 | = lv_x_rea61 | |
| X_REA63 | = lv_x_rea63 | |
| CHANGING | ||
| XY_LOCKLINE | = lv_xy_lockline | |
| XY_EABPS | = lv_xy_eabps | |
| . " ISU_BBP_INPUT_LOCK_REASON | ||
ABAP code using 7.40 inline data declarations to call FM ISU_BBP_INPUT_LOCK_REASON
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 PROID FROM DFKKLOCKS INTO @DATA(ld_x_proid). | ||||
Search for further information about these or an SAP related objects