SAP RSCONEW_AREA_ENCODE Function Module for FM for Encoding of various Hier Names
RSCONEW_AREA_ENCODE is a standard rsconew area encode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM for Encoding of various Hier Names 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 rsconew area encode FM, simply by entering the name RSCONEW_AREA_ENCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSCONEW
Program Name: SAPLRSCONEW
Main Program: SAPLRSCONEW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSCONEW_AREA_ENCODE 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 'RSCONEW_AREA_ENCODE'"FM for Encoding of various Hier Names.
EXPORTING
I_AREA = "Name of InfoArea or Application Component
I_TOPNODE = "Name of InfoArea or Application Component
I_REL = "Relase
* I_VALUE = "Level Indicator
* I_AREACODE = "No: of Objects in Encoded Format
* I_ENCODE = "No: of Objects in Encoded Format
* I_APPCOM = "boolean variable (X=true, -=false, space=unknown)
* I_DECODEINDICATOR = "boolean variable (X=true, -=false, space=unknown)
IMPORTING
E_ENCODE = "Name of InfoArea or Application Component
E_ENCODE_NOLEVEL = "No: of Objects in Encoded Format
E_EXCEPTION = "boolean variable (X=true, -=false, space=unknown)
E_AREA = "InfoArea
E_APPLNM = "Application Component
IMPORTING Parameters details for RSCONEW_AREA_ENCODE
I_AREA - Name of InfoArea or Application Component
Data type: RSCEWHIERNAMEOptional: No
Call by Reference: Yes
I_TOPNODE - Name of InfoArea or Application Component
Data type: RSCEWHIERNAMEOptional: No
Call by Reference: Yes
I_REL - Relase
Data type: RSCEWRELOptional: No
Call by Reference: Yes
I_VALUE - Level Indicator
Data type: RSCEWVALUEOptional: Yes
Call by Reference: Yes
I_AREACODE - No: of Objects in Encoded Format
Data type: RSCEWENCODESTRINGOptional: Yes
Call by Reference: Yes
I_ENCODE - No: of Objects in Encoded Format
Data type: RSCEWENCODESTRINGOptional: Yes
Call by Reference: Yes
I_APPCOM - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
I_DECODEINDICATOR - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSCONEW_AREA_ENCODE
E_ENCODE - Name of InfoArea or Application Component
Data type: RSCEWENCODESTRINGOptional: No
Call by Reference: Yes
E_ENCODE_NOLEVEL - No: of Objects in Encoded Format
Data type: RSCEWENCODESTRINGOptional: No
Call by Reference: Yes
E_EXCEPTION - boolean variable (X=true, -=false, space=unknown)
Data type: RSCEWEXCEPTIONOptional: No
Call by Reference: Yes
E_AREA - InfoArea
Data type: RSCEWHIERNAMEOptional: No
Call by Reference: Yes
E_APPLNM - Application Component
Data type: RSCEWHIERNAMEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSCONEW_AREA_ENCODE 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_area | TYPE RSCEWHIERNAME, " | |||
| lv_e_encode | TYPE RSCEWENCODESTRING, " | |||
| lv_i_topnode | TYPE RSCEWHIERNAME, " | |||
| lv_e_encode_nolevel | TYPE RSCEWENCODESTRING, " | |||
| lv_i_rel | TYPE RSCEWREL, " | |||
| lv_e_exception | TYPE RSCEWEXCEPTION, " | |||
| lv_e_area | TYPE RSCEWHIERNAME, " | |||
| lv_i_value | TYPE RSCEWVALUE, " | |||
| lv_e_applnm | TYPE RSCEWHIERNAME, " | |||
| lv_i_areacode | TYPE RSCEWENCODESTRING, " | |||
| lv_i_encode | TYPE RSCEWENCODESTRING, " | |||
| lv_i_appcom | TYPE BOOLEAN, " | |||
| lv_i_decodeindicator | TYPE BOOLEAN. " |
|   CALL FUNCTION 'RSCONEW_AREA_ENCODE' "FM for Encoding of various Hier Names |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_TOPNODE | = lv_i_topnode | |
| I_REL | = lv_i_rel | |
| I_VALUE | = lv_i_value | |
| I_AREACODE | = lv_i_areacode | |
| I_ENCODE | = lv_i_encode | |
| I_APPCOM | = lv_i_appcom | |
| I_DECODEINDICATOR | = lv_i_decodeindicator | |
| IMPORTING | ||
| E_ENCODE | = lv_e_encode | |
| E_ENCODE_NOLEVEL | = lv_e_encode_nolevel | |
| E_EXCEPTION | = lv_e_exception | |
| E_AREA | = lv_e_area | |
| E_APPLNM | = lv_e_applnm | |
| . " RSCONEW_AREA_ENCODE | ||
ABAP code using 7.40 inline data declarations to call FM RSCONEW_AREA_ENCODE
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