SAP SCP_POSSIBLE_DB_COUNTRIES Function Module for









SCP_POSSIBLE_DB_COUNTRIES is a standard scp possible db countries 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 possible db countries FM, simply by entering the name SCP_POSSIBLE_DB_COUNTRIES into the relevant SAP transaction such as SE37 or SE38.

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



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

TABLES
COUNTRY_LIST = "
.



IMPORTING Parameters details for SCP_POSSIBLE_DB_COUNTRIES

LANGUAGES -

Data type: LANGIMP-LANGVECT
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CODEPAGE -

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

TABLES Parameters details for SCP_POSSIBLE_DB_COUNTRIES

COUNTRY_LIST -

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

Copy and paste ABAP code example for SCP_POSSIBLE_DB_COUNTRIES 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_languages  TYPE LANGIMP-LANGVECT, "   '*'
lt_country_list  TYPE STANDARD TABLE OF ABAPTEXT, "   
lv_codepage  TYPE TCP00-CPCODEPAGE. "   '0000'

  CALL FUNCTION 'SCP_POSSIBLE_DB_COUNTRIES'  "
    EXPORTING
         LANGUAGES = lv_languages
         CODEPAGE = lv_codepage
    TABLES
         COUNTRY_LIST = lt_country_list
. " SCP_POSSIBLE_DB_COUNTRIES




ABAP code using 7.40 inline data declarations to call FM SCP_POSSIBLE_DB_COUNTRIES

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 LANGVECT FROM LANGIMP INTO @DATA(ld_languages).
DATA(ld_languages) = '*'.
 
 
"SELECT single CPCODEPAGE FROM TCP00 INTO @DATA(ld_codepage).
DATA(ld_codepage) = '0000'.
 


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!