SAP GRPC_API_SIGNOFF_ISSUE_GET Function Module for Get all or open issues in current sign-off timeframe for a orgunit









GRPC_API_SIGNOFF_ISSUE_GET is a standard grpc api signoff issue get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get all or open issues in current sign-off timeframe for a orgunit 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 signoff issue get FM, simply by entering the name GRPC_API_SIGNOFF_ISSUE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_API_SIGNOFF
Program Name: SAPLGRPC_API_SIGNOFF
Main Program: SAPLGRPC_API_SIGNOFF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GRPC_API_SIGNOFF_ISSUE_GET 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_SIGNOFF_ISSUE_GET'"Get all or open issues in current sign-off timeframe for a orgunit
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
   IV_REGULATION_ID =  "Regulation ID
   IV_ORGUNIT_ID =  "GRPC ID of the individual object
   IV_ORGUNIT_ID_WF =  "GRPC ID of the individual object
   IV_DISPLAY =  "Display only
*  IV_OPEN = ' ' "Open issues or not

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_MESSAGE =  "Table with BAPI Return Information
*  ET_ISSUE =  "Issue information of Sign-Off
.



IMPORTING Parameters details for GRPC_API_SIGNOFF_ISSUE_GET

I_SESSION_ID - GRPC unique session ID

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

IV_REGULATION_ID - Regulation ID

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

IV_ORGUNIT_ID - GRPC ID of the individual object

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

IV_ORGUNIT_ID_WF - GRPC ID of the individual object

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

IV_DISPLAY - Display only

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

IV_OPEN - Open issues or not

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

EXPORTING Parameters details for GRPC_API_SIGNOFF_ISSUE_GET

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_SIGNOFF_ISSUE_GET

ET_MESSAGE - Table with BAPI Return Information

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

ET_ISSUE - Issue information of Sign-Off

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

Copy and paste ABAP code example for GRPC_API_SIGNOFF_ISSUE_GET 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:
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_i_session_id  TYPE GRPC_API_SESSION_ID, "   
lv_e_return_code  TYPE INT4, "   
lt_et_issue  TYPE STANDARD TABLE OF GRPC_T_SIGNOFF_ISSUE_LIST, "   
lv_iv_regulation_id  TYPE GRFN_API_OBJECT_ID, "   
lv_iv_orgunit_id  TYPE GRPC_API_OBJECT_ID, "   
lv_iv_orgunit_id_wf  TYPE GRPC_API_OBJECT_ID, "   
lv_iv_display  TYPE XFELD, "   
lv_iv_open  TYPE XFELD. "   ' '

  CALL FUNCTION 'GRPC_API_SIGNOFF_ISSUE_GET'  "Get all or open issues in current sign-off timeframe for a orgunit
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         IV_REGULATION_ID = lv_iv_regulation_id
         IV_ORGUNIT_ID = lv_iv_orgunit_id
         IV_ORGUNIT_ID_WF = lv_iv_orgunit_id_wf
         IV_DISPLAY = lv_iv_display
         IV_OPEN = lv_iv_open
    IMPORTING
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_MESSAGE = lt_et_message
         ET_ISSUE = lt_et_issue
. " GRPC_API_SIGNOFF_ISSUE_GET




ABAP code using 7.40 inline data declarations to call FM GRPC_API_SIGNOFF_ISSUE_GET

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_open) = ' '.
 


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!