SAP HRXSS_IN_CL_REQ_RENDER Function Module for Gets the Rendering Information
HRXSS_IN_CL_REQ_RENDER is a standard hrxss in cl req render SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets the Rendering Information 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 hrxss in cl req render FM, simply by entering the name HRXSS_IN_CL_REQ_RENDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPBSINNEWCLAIMS
Program Name: SAPLHRPBSINNEWCLAIMS
Main Program: SAPLHRPBSINNEWCLAIMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function HRXSS_IN_CL_REQ_RENDER 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 'HRXSS_IN_CL_REQ_RENDER'"Gets the Rendering Information.
EXPORTING
IFD_RQOPR = "Request Operation for Request Customizing RFC
IFD_CASRE = "Is ASREF Changed
* IFD_APERN = "Personnel number
* IFD_RQCAN = '00001' "Request Created from Application
IMPORTING
EST_REQCH = "Request Characteristics at Front End
EST_RDMSG = "Request Data Messages
ETB_RSNCD = "Table to hold the Reason Code and Text
ETB_VFTYP = "Table Type to Store Allowed File Types on ESS
EST_ATTAT = "Attributes of Attachment Functionality
EST_GADAT = "General Application Structure
ETB_ERRTB = "Return Parameter
ETB_HLDCR = "Header level dynamic content configuration
ETB_MLDCR = "Multiple line item level dynamic content configuration
ETB_HLDCO = "F4 Help/Drop down options for Header level dynamic fields
ETB_MLDCO = "F4 Help/Drop down options for multiple line item level
EST_DEPDR = "Dependent Information Visibility
ETB_HLSCR = "Table Type to store Standard Header Field View Attributes
ETB_DCLTX = "Declaration Text Table Type
EST_REQTX = "Texts for Reimbursement, Request and Scheme Type
CHANGING
CST_REQDT = "Emp Table table for RFC
IMPORTING Parameters details for HRXSS_IN_CL_REQ_RENDER
IFD_RQOPR - Request Operation for Request Customizing RFC
Data type: PIN_RQOPROptional: No
Call by Reference: No ( called with pass by value option)
IFD_CASRE - Is ASREF Changed
Data type: FLAGOptional: No
Call by Reference: No ( called with pass by value option)
IFD_APERN - Personnel number
Data type: P_PERNROptional: Yes
Call by Reference: No ( called with pass by value option)
IFD_RQCAN - Request Created from Application
Data type: PIN_RQCANDefault: '00001'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HRXSS_IN_CL_REQ_RENDER
EST_REQCH - Request Characteristics at Front End
Data type: PIN_REQCHOptional: No
Call by Reference: No ( called with pass by value option)
EST_RDMSG - Request Data Messages
Data type: PIN_RDMSGOptional: No
Call by Reference: No ( called with pass by value option)
ETB_RSNCD - Table to hold the Reason Code and Text
Data type: HRESSIN_REASONOptional: No
Call by Reference: No ( called with pass by value option)
ETB_VFTYP - Table Type to Store Allowed File Types on ESS
Data type: HRESSIN_VFTYPOptional: No
Call by Reference: No ( called with pass by value option)
EST_ATTAT - Attributes of Attachment Functionality
Data type: PIN_ATTATOptional: No
Call by Reference: No ( called with pass by value option)
EST_GADAT - General Application Structure
Data type: PIN_GENAPP_STRUCTOptional: No
Call by Reference: No ( called with pass by value option)
ETB_ERRTB - Return Parameter
Data type: BAPIRET2_TABOptional: No
Call by Reference: No ( called with pass by value option)
ETB_HLDCR - Header level dynamic content configuration
Data type: HRESSIN_CUSTOM_FE_FIELDSOptional: No
Call by Reference: No ( called with pass by value option)
ETB_MLDCR - Multiple line item level dynamic content configuration
Data type: HRESSIN_CUSTOM_FE_FIELDSOptional: No
Call by Reference: No ( called with pass by value option)
ETB_HLDCO - F4 Help/Drop down options for Header level dynamic fields
Data type: HRESSIN_CUSTOM_FLD_VALUESOptional: No
Call by Reference: No ( called with pass by value option)
ETB_MLDCO - F4 Help/Drop down options for multiple line item level
Data type: HRESSIN_CUSTOM_FLD_VALUESOptional: No
Call by Reference: No ( called with pass by value option)
EST_DEPDR - Dependent Information Visibility
Data type: PIN_IV_DEPDTOptional: No
Call by Reference: No ( called with pass by value option)
ETB_HLSCR - Table Type to store Standard Header Field View Attributes
Data type: HRESSINSHVAOptional: No
Call by Reference: No ( called with pass by value option)
ETB_DCLTX - Declaration Text Table Type
Data type: HRESSIN_DECLARATION_DATAOptional: No
Call by Reference: No ( called with pass by value option)
EST_REQTX - Texts for Reimbursement, Request and Scheme Type
Data type: PIN_ALW_RETYPOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for HRXSS_IN_CL_REQ_RENDER
CST_REQDT - Emp Table table for RFC
Data type: PIN_EMP_STRUCTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRXSS_IN_CL_REQ_RENDER 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_cst_reqdt | TYPE PIN_EMP_STRUCT, " | |||
| lv_est_reqch | TYPE PIN_REQCH, " | |||
| lv_ifd_rqopr | TYPE PIN_RQOPR, " | |||
| lv_est_rdmsg | TYPE PIN_RDMSG, " | |||
| lv_etb_rsncd | TYPE HRESSIN_REASON, " | |||
| lv_etb_vftyp | TYPE HRESSIN_VFTYP, " | |||
| lv_est_attat | TYPE PIN_ATTAT, " | |||
| lv_est_gadat | TYPE PIN_GENAPP_STRUCT, " | |||
| lv_etb_errtb | TYPE BAPIRET2_TAB, " | |||
| lv_etb_hldcr | TYPE HRESSIN_CUSTOM_FE_FIELDS, " | |||
| lv_ifd_casre | TYPE FLAG, " | |||
| lv_etb_mldcr | TYPE HRESSIN_CUSTOM_FE_FIELDS, " | |||
| lv_ifd_apern | TYPE P_PERNR, " | |||
| lv_etb_hldco | TYPE HRESSIN_CUSTOM_FLD_VALUES, " | |||
| lv_ifd_rqcan | TYPE PIN_RQCAN, " '00001' | |||
| lv_etb_mldco | TYPE HRESSIN_CUSTOM_FLD_VALUES, " | |||
| lv_est_depdr | TYPE PIN_IV_DEPDT, " | |||
| lv_etb_hlscr | TYPE HRESSINSHVA, " | |||
| lv_etb_dcltx | TYPE HRESSIN_DECLARATION_DATA, " | |||
| lv_est_reqtx | TYPE PIN_ALW_RETYP. " |
|   CALL FUNCTION 'HRXSS_IN_CL_REQ_RENDER' "Gets the Rendering Information |
| EXPORTING | ||
| IFD_RQOPR | = lv_ifd_rqopr | |
| IFD_CASRE | = lv_ifd_casre | |
| IFD_APERN | = lv_ifd_apern | |
| IFD_RQCAN | = lv_ifd_rqcan | |
| IMPORTING | ||
| EST_REQCH | = lv_est_reqch | |
| EST_RDMSG | = lv_est_rdmsg | |
| ETB_RSNCD | = lv_etb_rsncd | |
| ETB_VFTYP | = lv_etb_vftyp | |
| EST_ATTAT | = lv_est_attat | |
| EST_GADAT | = lv_est_gadat | |
| ETB_ERRTB | = lv_etb_errtb | |
| ETB_HLDCR | = lv_etb_hldcr | |
| ETB_MLDCR | = lv_etb_mldcr | |
| ETB_HLDCO | = lv_etb_hldco | |
| ETB_MLDCO | = lv_etb_mldco | |
| EST_DEPDR | = lv_est_depdr | |
| ETB_HLSCR | = lv_etb_hlscr | |
| ETB_DCLTX | = lv_etb_dcltx | |
| EST_REQTX | = lv_est_reqtx | |
| CHANGING | ||
| CST_REQDT | = lv_cst_reqdt | |
| . " HRXSS_IN_CL_REQ_RENDER | ||
ABAP code using 7.40 inline data declarations to call FM HRXSS_IN_CL_REQ_RENDER
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_ifd_rqcan) | = '00001'. | |||
Search for further information about these or an SAP related objects