SAP SSC_SR_REPORT_READ Function Module for read persistent layer









SSC_SR_REPORT_READ is a standard ssc sr report read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for read persistent layer 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 ssc sr report read FM, simply by entering the name SSC_SR_REPORT_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function SSC_SR_REPORT_READ 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 'SSC_SR_REPORT_READ'"read persistent layer
EXPORTING
* IX_CRM_NEEDED = ABAP_TRUE "Read CRM data: TRUE (X) and FALSE ( )
* IT_MSGNO = "Range table for message number
* IT_RUNID = "Range table for run ID
* IT_RUNDATE = "Range table for run date
* IT_LINKED_OBJ = "Linked object
* IX_AUTOMATIC = ABAP_UNDEFINED "TRUE (X) and FALSE ( ) and UNDEFINED (-)
* IX_CLOSED = ABAP_UNDEFINED "TRUE (X) and FALSE ( ) and UNDEFINED (-)
I_SCENARIO = "Application
* IT_GROUPID = "Range table for application area
* IT_SRID = "Range table for service request
* IT_CREATEDATE = "Range table for date
* IT_REPORTEDBY = "Range table for reporter
* IT_MSGID = "Range table for message class

IMPORTING
ET_SRALL_LINKOBJ = "service request in backend
.



IMPORTING Parameters details for SSC_SR_REPORT_READ

IX_CRM_NEEDED - Read CRM data: TRUE (X) and FALSE ( )

Data type: BOOLE_D
Default: ABAP_TRUE
Optional: Yes
Call by Reference: Yes

IT_MSGNO - Range table for message number

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

IT_RUNID - Range table for run ID

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

IT_RUNDATE - Range table for run date

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

IT_LINKED_OBJ - Linked object

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

IX_AUTOMATIC - TRUE (X) and FALSE ( ) and UNDEFINED (-)

Data type: ABAP_BOOL
Default: ABAP_UNDEFINED
Optional: Yes
Call by Reference: Yes

IX_CLOSED - TRUE (X) and FALSE ( ) and UNDEFINED (-)

Data type: ABAP_BOOL
Default: ABAP_UNDEFINED
Optional: Yes
Call by Reference: Yes

I_SCENARIO - Application

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

IT_GROUPID - Range table for application area

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

IT_SRID - Range table for service request

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

IT_CREATEDATE - Range table for date

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

IT_REPORTEDBY - Range table for reporter

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

IT_MSGID - Range table for message class

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

EXPORTING Parameters details for SSC_SR_REPORT_READ

ET_SRALL_LINKOBJ - service request in backend

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

Copy and paste ABAP code example for SSC_SR_REPORT_READ 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_ix_crm_needed  TYPE BOOLE_D, "   ABAP_TRUE
lv_et_srall_linkobj  TYPE SSC_T_SRALL_LINKOBJ, "   
lv_it_msgno  TYPE SSC_T_RG_MSGNO, "   
lv_it_runid  TYPE SSC_T_RG_RUNID, "   
lv_it_rundate  TYPE SSC_T_RG_DATE, "   
lv_it_linked_obj  TYPE SSC_T_SRSEARCH_LINK, "   
lv_ix_automatic  TYPE ABAP_BOOL, "   ABAP_UNDEFINED
lv_ix_closed  TYPE ABAP_BOOL, "   ABAP_UNDEFINED
lv_i_scenario  TYPE SSC_SCENARIO, "   
lv_it_groupid  TYPE SSC_T_RG_GROUPID, "   
lv_it_srid  TYPE SSC_T_RG_SRID, "   
lv_it_createdate  TYPE SSC_T_RG_DATE, "   
lv_it_reportedby  TYPE SSC_T_RG_UNAME, "   
lv_it_msgid  TYPE SSC_T_RG_MSGID. "   

  CALL FUNCTION 'SSC_SR_REPORT_READ'  "read persistent layer
    EXPORTING
         IX_CRM_NEEDED = lv_ix_crm_needed
         IT_MSGNO = lv_it_msgno
         IT_RUNID = lv_it_runid
         IT_RUNDATE = lv_it_rundate
         IT_LINKED_OBJ = lv_it_linked_obj
         IX_AUTOMATIC = lv_ix_automatic
         IX_CLOSED = lv_ix_closed
         I_SCENARIO = lv_i_scenario
         IT_GROUPID = lv_it_groupid
         IT_SRID = lv_it_srid
         IT_CREATEDATE = lv_it_createdate
         IT_REPORTEDBY = lv_it_reportedby
         IT_MSGID = lv_it_msgid
    IMPORTING
         ET_SRALL_LINKOBJ = lv_et_srall_linkobj
. " SSC_SR_REPORT_READ




ABAP code using 7.40 inline data declarations to call FM SSC_SR_REPORT_READ

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_ix_crm_needed) = ABAP_TRUE.
 
 
 
 
 
 
DATA(ld_ix_automatic) = ABAP_UNDEFINED.
 
DATA(ld_ix_closed) = ABAP_UNDEFINED.
 
 
 
 
 
 
 


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!