SAP GRPC_API_ORGUNIT_RETRIEVE Function Module for Retrieve Organization's data









GRPC_API_ORGUNIT_RETRIEVE is a standard grpc api orgunit retrieve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve 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 retrieve FM, simply by entering the name GRPC_API_ORGUNIT_RETRIEVE 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_RETRIEVE 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_RETRIEVE'"Retrieve Organization's data
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
   I_ORGUNIT_ID =  "GRPC ID of the individual object
*  I_EDITABLE =  "Boolean Variable (X=True, -=False, Space=Unknown)
   I_REGULATION_ID =  "GRPC ID of the individual object

 IMPORTING
   ES_ORGUNIT_DATA =  "The list of the orgunits
   ES_ORGUNIT_LOCATION =  "Country / Region
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_ORGUNIT_ROLE =  "Obsolete: The list of the orgunits
*  ET_MESSAGE =  "Table with BAPI Return Information
*  ET_ORGUNIT_ECONTROL =  "table type of mcontrol-->orgunit
*  ET_ORGUNIT_SUBPROCESS =  "table type for subprocess local
*  ET_ORGUNIT_BCONTROL =  "Table type for Process-process step data for API service
.



IMPORTING Parameters details for GRPC_API_ORGUNIT_RETRIEVE

I_SESSION_ID - GRPC unique session ID

Data type: GRPC_API_SESSION_ID
Optional: Yes
Call by Reference: Yes

I_ORGUNIT_ID - GRPC ID of the individual object

Data type: GRPC_API_OBJECT_ID
Optional: No
Call by Reference: Yes

I_EDITABLE - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

I_REGULATION_ID - GRPC ID of the individual object

Data type: GRPC_API_OBJECT_ID
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for GRPC_API_ORGUNIT_RETRIEVE

ES_ORGUNIT_DATA - The list of the orgunits

Data type: GRPC_S_API_ORGUNIT_DATA
Optional: No
Call by Reference: No ( called with pass by value option)

ES_ORGUNIT_LOCATION - Country / Region

Data type: GRPC_S_API_ORGUNIT_LOCATION
Optional: No
Call by Reference: No ( called with pass by value option)

E_RETURN_CODE - Natural number

Data type: INT4
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GRPC_API_ORGUNIT_RETRIEVE

ET_ORGUNIT_ROLE - Obsolete: The list of the orgunits

Data type: GRPC_T_API_ENTITY_ROLE
Optional: Yes
Call by Reference: Yes

ET_MESSAGE - Table with BAPI Return Information

Data type: BAPIRETTAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

ET_ORGUNIT_ECONTROL - table type of mcontrol-->orgunit

Data type: GRPC_T_API_ORGANUNIT_MCONTROL
Optional: Yes
Call by Reference: Yes

ET_ORGUNIT_SUBPROCESS - table type for subprocess local

Data type: GRPC_T_API_SUBPROCESS_LOCAL
Optional: Yes
Call by Reference: Yes

ET_ORGUNIT_BCONTROL - Table type for Process-process step data for API service

Data type: GRPC_T_API_CONTROL_BDATA
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for GRPC_API_ORGUNIT_RETRIEVE 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_es_orgunit_data  TYPE GRPC_S_API_ORGUNIT_DATA, "   
lt_et_orgunit_role  TYPE STANDARD TABLE OF GRPC_T_API_ENTITY_ROLE, "   
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_i_orgunit_id  TYPE GRPC_API_OBJECT_ID, "   
lv_es_orgunit_location  TYPE GRPC_S_API_ORGUNIT_LOCATION, "   
lv_i_editable  TYPE BOOLEAN, "   
lv_e_return_code  TYPE INT4, "   
lt_et_orgunit_econtrol  TYPE STANDARD TABLE OF GRPC_T_API_ORGANUNIT_MCONTROL, "   
lv_i_regulation_id  TYPE GRPC_API_OBJECT_ID, "   
lt_et_orgunit_subprocess  TYPE STANDARD TABLE OF GRPC_T_API_SUBPROCESS_LOCAL, "   
lt_et_orgunit_bcontrol  TYPE STANDARD TABLE OF GRPC_T_API_CONTROL_BDATA. "   

  CALL FUNCTION 'GRPC_API_ORGUNIT_RETRIEVE'  "Retrieve Organization's data
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_ORGUNIT_ID = lv_i_orgunit_id
         I_EDITABLE = lv_i_editable
         I_REGULATION_ID = lv_i_regulation_id
    IMPORTING
         ES_ORGUNIT_DATA = lv_es_orgunit_data
         ES_ORGUNIT_LOCATION = lv_es_orgunit_location
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_ORGUNIT_ROLE = lt_et_orgunit_role
         ET_MESSAGE = lt_et_message
         ET_ORGUNIT_ECONTROL = lt_et_orgunit_econtrol
         ET_ORGUNIT_SUBPROCESS = lt_et_orgunit_subprocess
         ET_ORGUNIT_BCONTROL = lt_et_orgunit_bcontrol
. " GRPC_API_ORGUNIT_RETRIEVE




ABAP code using 7.40 inline data declarations to call FM GRPC_API_ORGUNIT_RETRIEVE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!