SAP RFC_PUT_CODEPAGE Function Module for

Search SAP Function Modules

RFC_PUT_CODEPAGE is a standard rfc put codepage 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 rfc put codepage FM, simply by entering the name RFC_PUT_CODEPAGE into the relevant SAP transaction such as SE37 or SE38.

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

Function RFC_PUT_CODEPAGE 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 'RFC_PUT_CODEPAGE'"
  EXPORTING
   FROMPAGE =  "Source code page
*  PATHNAME = ' ' "
   TOPAGE =  "Target code page

EXCEPTIONS
   BAD_TABLE_SHAPE = 1    CODEPAGE_NOT_FOUND = 2    OUTPUT_FAILED = 3    STRING_CONCATENATE = 4 

.

IMPORTING Parameters details for RFC_PUT_CODEPAGE

FROMPAGE - Source code page

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

PATHNAME -

Data type: RFCPUT-PATH
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TOPAGE - Target code page

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

EXCEPTIONS details

BAD_TABLE_SHAPE - Ambiguous character allocation in table

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

CODEPAGE_NOT_FOUND -

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

OUTPUT_FAILED - Output is not possible

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

STRING_CONCATENATE -

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

Copy and paste ABAP code example for RFC_PUT_CODEPAGE 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.

ABAP code using 7.40 inline data declarations to call FM RFC_PUT_CODEPAGE

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