SAP GRPC_API_ORGUNIT_UPDATE Function Module for Update Organization's data
GRPC_API_ORGUNIT_UPDATE is a standard grpc api orgunit update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Organization's data 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 grpc api orgunit update FM, simply by entering the name GRPC_API_ORGUNIT_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_ORGUNIT
Program Name: SAPLGRPC_API_ORGUNIT
Main Program: SAPLGRPC_API_ORGUNIT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function GRPC_API_ORGUNIT_UPDATE 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 'GRPC_API_ORGUNIT_UPDATE'"Update Organization's data.
EXPORTING
* I_SESSION_ID = "GRPC unique session ID
* IS_ORGUNIT_DATA_CHANGED = "The list of the orgunits
* I_ORGUNIT_ID = "GRPC ID of the individual object
I_REGULATION_ID = "GRPC ID of the individual object
IMPORTING
E_RETURN_CODE = "Natural number
TABLES
* IT_ORGUNIT_ROLE_CHANGED = "Obsolete: The list of the orgunits
* IT_ORGUNIT_ECONTROL_CHANGED = "table type of mcontrol-->orgunit
* IT_ORGUNIT_SUBPROCESS_CHANGED = "table type for subprocess local
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_ORGUNIT_UPDATE
I_SESSION_ID - GRPC unique session ID
Data type: GRPC_API_SESSION_IDOptional: Yes
Call by Reference: Yes
IS_ORGUNIT_DATA_CHANGED - The list of the orgunits
Data type: GRPC_S_API_ORGUNIT_DATAOptional: Yes
Call by Reference: Yes
I_ORGUNIT_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REGULATION_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GRPC_API_ORGUNIT_UPDATE
E_RETURN_CODE - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRPC_API_ORGUNIT_UPDATE
IT_ORGUNIT_ROLE_CHANGED - Obsolete: The list of the orgunits
Data type: GRPC_T_API_ENTITY_ROLEOptional: Yes
Call by Reference: Yes
IT_ORGUNIT_ECONTROL_CHANGED - table type of mcontrol-->orgunit
Data type: GRPC_T_API_ORGANUNIT_MCONTROLOptional: Yes
Call by Reference: Yes
IT_ORGUNIT_SUBPROCESS_CHANGED - table type for subprocess local
Data type: GRPC_T_API_SUBPROCESS_LOCALOptional: Yes
Call by Reference: Yes
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GRPC_API_ORGUNIT_UPDATE 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_session_id | TYPE GRPC_API_SESSION_ID, " | |||
lv_e_return_code | TYPE INT4, " | |||
lt_it_orgunit_role_changed | TYPE STANDARD TABLE OF GRPC_T_API_ENTITY_ROLE, " | |||
lv_is_orgunit_data_changed | TYPE GRPC_S_API_ORGUNIT_DATA, " | |||
lt_it_orgunit_econtrol_changed | TYPE STANDARD TABLE OF GRPC_T_API_ORGANUNIT_MCONTROL, " | |||
lv_i_orgunit_id | TYPE GRPC_API_OBJECT_ID, " | |||
lt_it_orgunit_subprocess_changed | TYPE STANDARD TABLE OF GRPC_T_API_SUBPROCESS_LOCAL, " | |||
lt_et_message | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
lv_i_regulation_id | TYPE GRPC_API_OBJECT_ID. " |
  CALL FUNCTION 'GRPC_API_ORGUNIT_UPDATE' "Update Organization's data |
EXPORTING | ||
I_SESSION_ID | = lv_i_session_id | |
IS_ORGUNIT_DATA_CHANGED | = lv_is_orgunit_data_changed | |
I_ORGUNIT_ID | = lv_i_orgunit_id | |
I_REGULATION_ID | = lv_i_regulation_id | |
IMPORTING | ||
E_RETURN_CODE | = lv_e_return_code | |
TABLES | ||
IT_ORGUNIT_ROLE_CHANGED | = lt_it_orgunit_role_changed | |
IT_ORGUNIT_ECONTROL_CHANGED | = lt_it_orgunit_econtrol_changed | |
IT_ORGUNIT_SUBPROCESS_CHANGED | = lt_it_orgunit_subprocess_changed | |
ET_MESSAGE | = lt_et_message | |
. " GRPC_API_ORGUNIT_UPDATE |
ABAP code using 7.40 inline data declarations to call FM GRPC_API_ORGUNIT_UPDATE
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