SAP T001W_ORGANIZATIONAL_CHECK Function Module for NOTRANSL: Prüfen Organisationsdaten Werk
T001W_ORGANIZATIONAL_CHECK is a standard t001w organizational check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfen Organisationsdaten Werk processing and below is the pattern details for this FM, 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 t001w organizational check FM, simply by entering the name T001W_ORGANIZATIONAL_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: WR26
Program Name: SAPLWR26
Main Program: SAPLWR26
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function T001W_ORGANIZATIONAL_CHECK 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 'T001W_ORGANIZATIONAL_CHECK'"NOTRANSL: Prüfen Organisationsdaten Werk.
EXPORTING
I_T001W_EKORG = "Purchasing Organization
I_T001W_VKORG = "Sales organization for intercompany billing
I_T001W_VTWEG = "Distribution Channel for Internal Clearing
I_T001W_SPART = "Division for intercompany billing
I_T001K_BUKRS = "Company Code
* I_T001W_VLFKZ = ' ' "Plant Category
* I_RETURN_CODE = "Message Code
IMPORTING
O_RETURN_CODE = "Message Code
TABLES
* O_ERROR_TABLE = "Return Parameter
IMPORTING Parameters details for T001W_ORGANIZATIONAL_CHECK
I_T001W_EKORG - Purchasing Organization
Data type: T001W-EKORGOptional: No
Call by Reference: No ( called with pass by value option)
I_T001W_VKORG - Sales organization for intercompany billing
Data type: T001W-VKORGOptional: No
Call by Reference: No ( called with pass by value option)
I_T001W_VTWEG - Distribution Channel for Internal Clearing
Data type: T001W-VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
I_T001W_SPART - Division for intercompany billing
Data type: T001W-SPARTOptional: No
Call by Reference: No ( called with pass by value option)
I_T001K_BUKRS - Company Code
Data type: T001K-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_T001W_VLFKZ - Plant Category
Data type: T001W-VLFKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RETURN_CODE - Message Code
Data type: BAPIRETURN-CODEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for T001W_ORGANIZATIONAL_CHECK
O_RETURN_CODE - Message Code
Data type: BAPIRETURN-CODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for T001W_ORGANIZATIONAL_CHECK
O_ERROR_TABLE - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for T001W_ORGANIZATIONAL_CHECK 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_i_t001w_ekorg | TYPE T001W-EKORG, " | |||
lt_o_error_table | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_o_return_code | TYPE BAPIRETURN-CODE, " | |||
lv_i_t001w_vkorg | TYPE T001W-VKORG, " | |||
lv_i_t001w_vtweg | TYPE T001W-VTWEG, " | |||
lv_i_t001w_spart | TYPE T001W-SPART, " | |||
lv_i_t001k_bukrs | TYPE T001K-BUKRS, " | |||
lv_i_t001w_vlfkz | TYPE T001W-VLFKZ, " SPACE | |||
lv_i_return_code | TYPE BAPIRETURN-CODE. " |
  CALL FUNCTION 'T001W_ORGANIZATIONAL_CHECK' "NOTRANSL: Prüfen Organisationsdaten Werk |
EXPORTING | ||
I_T001W_EKORG | = lv_i_t001w_ekorg | |
I_T001W_VKORG | = lv_i_t001w_vkorg | |
I_T001W_VTWEG | = lv_i_t001w_vtweg | |
I_T001W_SPART | = lv_i_t001w_spart | |
I_T001K_BUKRS | = lv_i_t001k_bukrs | |
I_T001W_VLFKZ | = lv_i_t001w_vlfkz | |
I_RETURN_CODE | = lv_i_return_code | |
IMPORTING | ||
O_RETURN_CODE | = lv_o_return_code | |
TABLES | ||
O_ERROR_TABLE | = lt_o_error_table | |
. " T001W_ORGANIZATIONAL_CHECK |
ABAP code using 7.40 inline data declarations to call FM T001W_ORGANIZATIONAL_CHECK
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 EKORG FROM T001W INTO @DATA(ld_i_t001w_ekorg). | ||||
"SELECT single CODE FROM BAPIRETURN INTO @DATA(ld_o_return_code). | ||||
"SELECT single VKORG FROM T001W INTO @DATA(ld_i_t001w_vkorg). | ||||
"SELECT single VTWEG FROM T001W INTO @DATA(ld_i_t001w_vtweg). | ||||
"SELECT single SPART FROM T001W INTO @DATA(ld_i_t001w_spart). | ||||
"SELECT single BUKRS FROM T001K INTO @DATA(ld_i_t001k_bukrs). | ||||
"SELECT single VLFKZ FROM T001W INTO @DATA(ld_i_t001w_vlfkz). | ||||
DATA(ld_i_t001w_vlfkz) | = ' '. | |||
"SELECT single CODE FROM BAPIRETURN INTO @DATA(ld_i_return_code). | ||||
Search for further information about these or an SAP related objects