SAP BUP_CHECK_XBLOCK Function Module for
BUP_CHECK_XBLOCK is a standard bup check xblock 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 bup check xblock FM, simply by entering the name BUP_CHECK_XBLOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUD_CHECK
Program Name: SAPLBUD_CHECK
Main Program: SAPLBUD_CHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUP_CHECK_XBLOCK 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 'BUP_CHECK_XBLOCK'".
EXPORTING
IV_XBLOCK = "Central block for business partner
* IV_PARTNER = ' ' "Business Partner Number
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for BUP_CHECK_XBLOCK
IV_XBLOCK - Central block for business partner
Data type: BU_XBLCKOptional: No
Call by Reference: Yes
IV_PARTNER - Business Partner Number
Data type: BU_PARTNERDefault: ' '
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BUP_CHECK_XBLOCK 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_xblock | TYPE BU_XBLCK, " | |||
| lv_not_found | TYPE BU_XBLCK, " | |||
| lv_iv_partner | TYPE BU_PARTNER. " ' ' |
|   CALL FUNCTION 'BUP_CHECK_XBLOCK' " |
| EXPORTING | ||
| IV_XBLOCK | = lv_iv_xblock | |
| IV_PARTNER | = lv_iv_partner | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " BUP_CHECK_XBLOCK | ||
ABAP code using 7.40 inline data declarations to call FM BUP_CHECK_XBLOCK
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_iv_partner) | = ' '. | |||
Search for further information about these or an SAP related objects