SAP CTS_API_IMPORT_CHANGE_REQUEST Function Module for









CTS_API_IMPORT_CHANGE_REQUEST is a standard cts api import change request 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 cts api import change request FM, simply by entering the name CTS_API_IMPORT_CHANGE_REQUEST into the relevant SAP transaction such as SE37 or SE38.

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



Function CTS_API_IMPORT_CHANGE_REQUEST 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 'CTS_API_IMPORT_CHANGE_REQUEST'"
EXPORTING
SYSTEM = "
CLIENT = "Target Client

IMPORTING
RETCODE = "Return code
MESSAGE = "Error Message

TABLES
REQUESTS = "
.



IMPORTING Parameters details for CTS_API_IMPORT_CHANGE_REQUEST

SYSTEM -

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

CLIENT - Target Client

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

EXPORTING Parameters details for CTS_API_IMPORT_CHANGE_REQUEST

RETCODE - Return code

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

MESSAGE - Error Message

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

TABLES Parameters details for CTS_API_IMPORT_CHANGE_REQUEST

REQUESTS -

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

Copy and paste ABAP code example for CTS_API_IMPORT_CHANGE_REQUEST 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_system  TYPE CHAR3, "   
lv_retcode  TYPE CHAR3, "   
lt_requests  TYPE STANDARD TABLE OF CTS_REQ, "   
lv_client  TYPE CHAR3, "   
lv_message  TYPE TEXT80. "   

  CALL FUNCTION 'CTS_API_IMPORT_CHANGE_REQUEST'  "
    EXPORTING
         SYSTEM = lv_system
         CLIENT = lv_client
    IMPORTING
         RETCODE = lv_retcode
         MESSAGE = lv_message
    TABLES
         REQUESTS = lt_requests
. " CTS_API_IMPORT_CHANGE_REQUEST




ABAP code using 7.40 inline data declarations to call FM CTS_API_IMPORT_CHANGE_REQUEST

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!