SAP GRPC_ESA_CREATE_ISSUE Function Module for Obsolete: PC create issue









GRPC_ESA_CREATE_ISSUE is a standard grpc esa create issue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obsolete: PC create issue 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 esa create issue FM, simply by entering the name GRPC_ESA_CREATE_ISSUE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_ESA
Program Name: SAPLGRPC_ESA
Main Program: SAPLGRPC_ESA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function GRPC_ESA_CREATE_ISSUE 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_ESA_CREATE_ISSUE'"Obsolete: PC create issue
  EXPORTING
   I_ASSMNT_GUID =  "Case ID
*  I_ISSUE_TITLE =  "Issue
*  I_ISSUE_PRIORITY =  "Issue Priority
*  I_ISSUE_PROCESSOR =  "Processor for an Issue
*  I_ISSUE_DESCR_D =  "Description
*  I_ISSUE_IMPLICATION_D =  "Implication
*  I_ISSUE_COMP_CNTR_D =  "Description
*  I_ISSUE_COMMENT_D =  "Comment If No Remediation Plan
   I_DO_COMMIT =  "

 IMPORTING
   E_CREATE_ISSUE_RESULT =  "
.



IMPORTING Parameters details for GRPC_ESA_CREATE_ISSUE

I_ASSMNT_GUID - Case ID

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

I_ISSUE_TITLE - Issue

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

I_ISSUE_PRIORITY - Issue Priority

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

I_ISSUE_PROCESSOR - Processor for an Issue

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

I_ISSUE_DESCR_D - Description

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

I_ISSUE_IMPLICATION_D - Implication

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

I_ISSUE_COMP_CNTR_D - Description

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

I_ISSUE_COMMENT_D - Comment If No Remediation Plan

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

I_DO_COMMIT -

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

EXPORTING Parameters details for GRPC_ESA_CREATE_ISSUE

E_CREATE_ISSUE_RESULT -

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

Copy and paste ABAP code example for GRPC_ESA_CREATE_ISSUE 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_assmnt_guid  TYPE GRPC_CASE_ID, "   
lv_e_create_issue_result  TYPE XFELD, "   
lv_i_issue_title  TYPE GRPC_REP_ISSUE_TEXT, "   
lv_i_issue_priority  TYPE GRPC_ISSUE_PRIORITY, "   
lv_i_issue_processor  TYPE GRPC_REP_ISSUE_PROC, "   
lv_i_issue_descr_d  TYPE GRPC_LONG_TEXT, "   
lv_i_issue_implication_d  TYPE GRPC_UI_IMPLICATION, "   
lv_i_issue_comp_cntr_d  TYPE GRPC_LONG_TEXT, "   
lv_i_issue_comment_d  TYPE GRPC_COMMENT_NO_REMPL, "   
lv_i_do_commit  TYPE XFELD. "   

  CALL FUNCTION 'GRPC_ESA_CREATE_ISSUE'  "Obsolete: PC create issue
    EXPORTING
         I_ASSMNT_GUID = lv_i_assmnt_guid
         I_ISSUE_TITLE = lv_i_issue_title
         I_ISSUE_PRIORITY = lv_i_issue_priority
         I_ISSUE_PROCESSOR = lv_i_issue_processor
         I_ISSUE_DESCR_D = lv_i_issue_descr_d
         I_ISSUE_IMPLICATION_D = lv_i_issue_implication_d
         I_ISSUE_COMP_CNTR_D = lv_i_issue_comp_cntr_d
         I_ISSUE_COMMENT_D = lv_i_issue_comment_d
         I_DO_COMMIT = lv_i_do_commit
    IMPORTING
         E_CREATE_ISSUE_RESULT = lv_e_create_issue_result
. " GRPC_ESA_CREATE_ISSUE




ABAP code using 7.40 inline data declarations to call FM GRPC_ESA_CREATE_ISSUE

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!