SAP CME_API_DSCOPE_PROVIDE Function Module for CME Definition Scope - Read Definition Scope









CME_API_DSCOPE_PROVIDE is a standard cme api dscope provide SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CME Definition Scope - Read Definition Scope 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 cme api dscope provide FM, simply by entering the name CME_API_DSCOPE_PROVIDE into the relevant SAP transaction such as SE37 or SE38.

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



Function CME_API_DSCOPE_PROVIDE 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 'CME_API_DSCOPE_PROVIDE'"CME Definition Scope - Read Definition Scope
  EXPORTING
*  IS_KEY =  "CME Distr. Scope - Key Fields in Internal/External Format
*  I_LANGUAGE =  "ISO Language
*  I_COUNTRY =  "ISO Country Key
*  I_TIMESTAMP =  "Time Stamp for Reading from History Table
*  IS_CHANGE_ORDER =  "Data for Change State
*  IS_PROCESS =  "CME Def.Scope - Bit String for Controlling Def.Scope Data
*  IT_TEXT_TYPES =  "Text Types for Definition Scope
*  IT_EXTENSIONS =  "List of Extension Data To Be Read

 IMPORTING
   ES_KEY =  "CME Distr. Scope - Key Fields in Internal/External Format
   ES_HEADER_DATA =  "Header Data of Definition Scope
   ET_STATUS =  "Status of Definition Scope
   ET_TEXT =  "Data Type -Texts-
   ET_DOCUMENTS =  "CME -Documents for a CME Object-
   ET_EXTENSIONS =  "CME Extension Concept -Structure for Including XSTRING-
   ET_CHARACTERISTICS =  "CME Characteristics for Definition Scope
   ET_EXTENSIONS_TEXTS =  "Definition Scope -Texts for Extensions-

TABLES
*  ET_RETURN =  "Messages

EXCEPTIONS
   EX_ERROR = 1
.



IMPORTING Parameters details for CME_API_DSCOPE_PROVIDE

IS_KEY - CME Distr. Scope - Key Fields in Internal/External Format

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

I_LANGUAGE - ISO Language

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

I_COUNTRY - ISO Country Key

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

I_TIMESTAMP - Time Stamp for Reading from History Table

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

IS_CHANGE_ORDER - Data for Change State

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

IS_PROCESS - CME Def.Scope - Bit String for Controlling Def.Scope Data

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

IT_TEXT_TYPES - Text Types for Definition Scope

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

IT_EXTENSIONS - List of Extension Data To Be Read

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

EXPORTING Parameters details for CME_API_DSCOPE_PROVIDE

ES_KEY - CME Distr. Scope - Key Fields in Internal/External Format

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

ES_HEADER_DATA - Header Data of Definition Scope

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

ET_STATUS - Status of Definition Scope

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

ET_TEXT - Data Type -Texts-

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

ET_DOCUMENTS - CME -Documents for a CME Object-

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

ET_EXTENSIONS - CME Extension Concept -Structure for Including XSTRING-

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

ET_CHARACTERISTICS - CME Characteristics for Definition Scope

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

ET_EXTENSIONS_TEXTS - Definition Scope -Texts for Extensions-

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

TABLES Parameters details for CME_API_DSCOPE_PROVIDE

ET_RETURN - Messages

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

EXCEPTIONS details

EX_ERROR - An error has occurred

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

Copy and paste ABAP code example for CME_API_DSCOPE_PROVIDE 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_es_key  TYPE CME_S_DSCOPE_KEY_INT_EXT, "   
lv_is_key  TYPE CME_S_DSCOPE_KEY_INT_EXT, "   
lv_ex_error  TYPE CME_S_DSCOPE_KEY_INT_EXT, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_language  TYPE DML_TEXT_LANGU, "   
lv_es_header_data  TYPE DML_S_KEY_BODY, "   
lv_et_status  TYPE DML_T_STATUS, "   
lv_i_country  TYPE DML_TEXT_COUNTRY, "   
lv_et_text  TYPE CME_T_TEXT, "   
lv_i_timestamp  TYPE DML_TMSTMP_MODIFY, "   
lv_et_documents  TYPE CME_T_OBJECT_DOCUMENTS, "   
lv_is_change_order  TYPE DML_S_API_ECM, "   
lv_is_process  TYPE CME_S_PROCESS_DSCOPE_PROVIDE, "   
lv_et_extensions  TYPE CME_T_EXTENSIONS, "   
lv_it_text_types  TYPE DML_T_TEXT_TYPES, "   
lv_et_characteristics  TYPE CME_T_DEFSCOPE_CHARACTER, "   
lv_it_extensions  TYPE DML_T_API_SETTYPE_LIST, "   
lv_et_extensions_texts  TYPE CME_T_TEXT_EXTENSIONS. "   

  CALL FUNCTION 'CME_API_DSCOPE_PROVIDE'  "CME Definition Scope - Read Definition Scope
    EXPORTING
         IS_KEY = lv_is_key
         I_LANGUAGE = lv_i_language
         I_COUNTRY = lv_i_country
         I_TIMESTAMP = lv_i_timestamp
         IS_CHANGE_ORDER = lv_is_change_order
         IS_PROCESS = lv_is_process
         IT_TEXT_TYPES = lv_it_text_types
         IT_EXTENSIONS = lv_it_extensions
    IMPORTING
         ES_KEY = lv_es_key
         ES_HEADER_DATA = lv_es_header_data
         ET_STATUS = lv_et_status
         ET_TEXT = lv_et_text
         ET_DOCUMENTS = lv_et_documents
         ET_EXTENSIONS = lv_et_extensions
         ET_CHARACTERISTICS = lv_et_characteristics
         ET_EXTENSIONS_TEXTS = lv_et_extensions_texts
    TABLES
         ET_RETURN = lt_et_return
    EXCEPTIONS
        EX_ERROR = 1
. " CME_API_DSCOPE_PROVIDE




ABAP code using 7.40 inline data declarations to call FM CME_API_DSCOPE_PROVIDE

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



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!