SAP SCP_CODEPAGE_INFO Function Module for









SCP_CODEPAGE_INFO is a standard scp codepage info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 scp codepage info FM, simply by entering the name SCP_CODEPAGE_INFO into the relevant SAP transaction such as SE37 or SE38.

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



Function SCP_CODEPAGE_INFO 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 'SCP_CODEPAGE_INFO'"
EXPORTING
* CODEPAGE = '0000' "

IMPORTING
NAME = "
CPNLSMAJOR_TEXT = "
CPSOURCE_TEXT = "
HTTP_NAME = "
JAVA_NAME = "
MIME_NAME = "
CPG_NAME = "RTF: /cpg Value
FCHA_NAME = "RTF: /fcharsetN Value
MATCHING_ASCII = "
ENTRY00 = "
CPISINF1 = "Code page is in F1 converter
CPUSEDBYF1 = "
CPISINF4 = "Code page is in F4 memory
CPISINF5 = "Code page is in F4 memory
CPENCODING_TEXT = "
CPBYTEIND_TEXT = "
CPEXTMETH_TEXT = "

EXCEPTIONS
INVALID_CODEPAGE = 1 INTERNAL_ERROR = 2
.



IMPORTING Parameters details for SCP_CODEPAGE_INFO

CODEPAGE -

Data type: TCP00-CPCODEPAGE
Default: '0000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SCP_CODEPAGE_INFO

NAME -

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

CPNLSMAJOR_TEXT -

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

CPSOURCE_TEXT -

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

HTTP_NAME -

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

JAVA_NAME -

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

MIME_NAME -

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

CPG_NAME - RTF: /cpg Value

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

FCHA_NAME - RTF: /fcharsetN Value

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

MATCHING_ASCII -

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

ENTRY00 -

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

CPISINF1 - Code page is in F1 converter

Data type: RSCPTYPE-CPISINF1
Optional: No
Call by Reference: No ( called with pass by value option)

CPUSEDBYF1 -

Data type: TCP00-CPCODEPAGE
Optional: No
Call by Reference: Yes

CPISINF4 - Code page is in F4 memory

Data type: RSCPTYPE-CPISINF4
Optional: No
Call by Reference: No ( called with pass by value option)

CPISINF5 - Code page is in F4 memory

Data type: RSCPTYPE-CPISINF5
Optional: No
Call by Reference: No ( called with pass by value option)

CPENCODING_TEXT -

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

CPBYTEIND_TEXT -

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

CPEXTMETH_TEXT -

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

EXCEPTIONS details

INVALID_CODEPAGE -

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

INTERNAL_ERROR - Internal Error

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

Copy and paste ABAP code example for SCP_CODEPAGE_INFO 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_name  TYPE C, "   
lv_codepage  TYPE TCP00-CPCODEPAGE, "   '0000'
lv_invalid_codepage  TYPE TCP00, "   
lv_cpnlsmajor_text  TYPE C, "   
lv_cpsource_text  TYPE C, "   
lv_http_name  TYPE C, "   
lv_java_name  TYPE C, "   
lv_mime_name  TYPE C, "   
lv_cpg_name  TYPE C, "   
lv_fcha_name  TYPE C, "   
lv_matching_ascii  TYPE C, "   
lv_entry00  TYPE TCP00, "   
lv_internal_error  TYPE TCP00, "   
lv_cpisinf1  TYPE RSCPTYPE-CPISINF1, "   
lv_cpusedbyf1  TYPE TCP00-CPCODEPAGE, "   
lv_cpisinf4  TYPE RSCPTYPE-CPISINF4, "   
lv_cpisinf5  TYPE RSCPTYPE-CPISINF5, "   
lv_cpencoding_text  TYPE C, "   
lv_cpbyteind_text  TYPE C, "   
lv_cpextmeth_text  TYPE C. "   

  CALL FUNCTION 'SCP_CODEPAGE_INFO'  "
    EXPORTING
         CODEPAGE = lv_codepage
    IMPORTING
         NAME = lv_name
         CPNLSMAJOR_TEXT = lv_cpnlsmajor_text
         CPSOURCE_TEXT = lv_cpsource_text
         HTTP_NAME = lv_http_name
         JAVA_NAME = lv_java_name
         MIME_NAME = lv_mime_name
         CPG_NAME = lv_cpg_name
         FCHA_NAME = lv_fcha_name
         MATCHING_ASCII = lv_matching_ascii
         ENTRY00 = lv_entry00
         CPISINF1 = lv_cpisinf1
         CPUSEDBYF1 = lv_cpusedbyf1
         CPISINF4 = lv_cpisinf4
         CPISINF5 = lv_cpisinf5
         CPENCODING_TEXT = lv_cpencoding_text
         CPBYTEIND_TEXT = lv_cpbyteind_text
         CPEXTMETH_TEXT = lv_cpextmeth_text
    EXCEPTIONS
        INVALID_CODEPAGE = 1
        INTERNAL_ERROR = 2
. " SCP_CODEPAGE_INFO




ABAP code using 7.40 inline data declarations to call FM SCP_CODEPAGE_INFO

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.

 
"SELECT single CPCODEPAGE FROM TCP00 INTO @DATA(ld_codepage).
DATA(ld_codepage) = '0000'.
 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single CPISINF1 FROM RSCPTYPE INTO @DATA(ld_cpisinf1).
 
"SELECT single CPCODEPAGE FROM TCP00 INTO @DATA(ld_cpusedbyf1).
 
"SELECT single CPISINF4 FROM RSCPTYPE INTO @DATA(ld_cpisinf4).
 
"SELECT single CPISINF5 FROM RSCPTYPE INTO @DATA(ld_cpisinf5).
 
 
 
 


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!