SAP SCP_FUTURE_CP_FOR_LANG_COUNTRY Function Module for









SCP_FUTURE_CP_FOR_LANG_COUNTRY is a standard scp future cp for lang country 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 future cp for lang country FM, simply by entering the name SCP_FUTURE_CP_FOR_LANG_COUNTRY into the relevant SAP transaction such as SE37 or SE38.

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



Function SCP_FUTURE_CP_FOR_LANG_COUNTRY 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_FUTURE_CP_FOR_LANG_COUNTRY'"
EXPORTING
LANGUAGE = "Language key
FUTURE_0D = "Adjustment of an installed database according to country

IMPORTING
CODEPAGE = "

TABLES
FUTURE_DB = "

EXCEPTIONS
NO_CODEPAGE = 1 UNICODE_SYSTEM = 2
.



IMPORTING Parameters details for SCP_FUTURE_CP_FOR_LANG_COUNTRY

LANGUAGE - Language key

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

FUTURE_0D - Adjustment of an installed database according to country

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

EXPORTING Parameters details for SCP_FUTURE_CP_FOR_LANG_COUNTRY

CODEPAGE -

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

TABLES Parameters details for SCP_FUTURE_CP_FOR_LANG_COUNTRY

FUTURE_DB -

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

EXCEPTIONS details

NO_CODEPAGE -

Data type:
Optional: No
Call by Reference: Yes

UNICODE_SYSTEM -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCP_FUTURE_CP_FOR_LANG_COUNTRY 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_codepage  TYPE CPCODEPAGE, "   
lv_language  TYPE SPRAS, "   
lt_future_db  TYPE STANDARD TABLE OF UMGTCP, "   
lv_no_codepage  TYPE UMGTCP, "   
lv_future_0d  TYPE TCP0D-COUNTRY, "   
lv_unicode_system  TYPE TCP0D. "   

  CALL FUNCTION 'SCP_FUTURE_CP_FOR_LANG_COUNTRY'  "
    EXPORTING
         LANGUAGE = lv_language
         FUTURE_0D = lv_future_0d
    IMPORTING
         CODEPAGE = lv_codepage
    TABLES
         FUTURE_DB = lt_future_db
    EXCEPTIONS
        NO_CODEPAGE = 1
        UNICODE_SYSTEM = 2
. " SCP_FUTURE_CP_FOR_LANG_COUNTRY




ABAP code using 7.40 inline data declarations to call FM SCP_FUTURE_CP_FOR_LANG_COUNTRY

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 COUNTRY FROM TCP0D INTO @DATA(ld_future_0d).
 
 


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!