SAP BUP_CHECK_ORGNAME Function Module for
BUP_CHECK_ORGNAME is a standard bup check orgname 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 orgname FM, simply by entering the name BUP_CHECK_ORGNAME 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_ORGNAME 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_ORGNAME'".
EXPORTING
IV_NAME_ORG1 = "
IV_NAME_ORG2 = "
IV_NAME_ORG3 = "
IV_NAME_ORG4 = "
EXCEPTIONS
NAME_TOO_LONG = 1
IMPORTING Parameters details for BUP_CHECK_ORGNAME
IV_NAME_ORG1 -
Data type: BU_NAMEOR1Optional: No
Call by Reference: Yes
IV_NAME_ORG2 -
Data type: BU_NAMEOR2Optional: No
Call by Reference: Yes
IV_NAME_ORG3 -
Data type: BU_NAMEOR3Optional: No
Call by Reference: Yes
IV_NAME_ORG4 -
Data type: BU_NAMEOR4Optional: No
Call by Reference: Yes
EXCEPTIONS details
NAME_TOO_LONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BUP_CHECK_ORGNAME 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_name_org1 | TYPE BU_NAMEOR1, " | |||
| lv_name_too_long | TYPE BU_NAMEOR1, " | |||
| lv_iv_name_org2 | TYPE BU_NAMEOR2, " | |||
| lv_iv_name_org3 | TYPE BU_NAMEOR3, " | |||
| lv_iv_name_org4 | TYPE BU_NAMEOR4. " |
|   CALL FUNCTION 'BUP_CHECK_ORGNAME' " |
| EXPORTING | ||
| IV_NAME_ORG1 | = lv_iv_name_org1 | |
| IV_NAME_ORG2 | = lv_iv_name_org2 | |
| IV_NAME_ORG3 | = lv_iv_name_org3 | |
| IV_NAME_ORG4 | = lv_iv_name_org4 | |
| EXCEPTIONS | ||
| NAME_TOO_LONG = 1 | ||
| . " BUP_CHECK_ORGNAME | ||
ABAP code using 7.40 inline data declarations to call FM BUP_CHECK_ORGNAME
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