SAP /IXOS/DC_D_EXAMPLE_CHANGE Function Module for Example for userexit in changing screens









/IXOS/DC_D_EXAMPLE_CHANGE is a standard /ixos/dc d example change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Example for userexit in changing screens 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 /ixos/dc d example change FM, simply by entering the name /IXOS/DC_D_EXAMPLE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /IXOS/DC_D
Program Name: /IXOS/SAPLDC_D
Main Program: /IXOS/SAPLDC_D
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /IXOS/DC_D_EXAMPLE_CHANGE 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 '/IXOS/DC_D_EXAMPLE_CHANGE'"Example for userexit in changing screens
EXPORTING
PI_PROJECT = "Project
PI_VERSION = "Version
PI_TREE_NUM = "View
PI_FKTCODE = "The function code which was pressed
PI_TABNAME = "Structure of PC_RECORD
PI_DATASOURCE = "Data source

IMPORTING
PE_TENSION = "Intension ...

CHANGING
PC_RECORD = "Original Record
PC_USR_REC = "User changed Record

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for /IXOS/DC_D_EXAMPLE_CHANGE

PI_PROJECT - Project

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

PI_VERSION - Version

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

PI_TREE_NUM - View

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

PI_FKTCODE - The function code which was pressed

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

PI_TABNAME - Structure of PC_RECORD

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

PI_DATASOURCE - Data source

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

EXPORTING Parameters details for /IXOS/DC_D_EXAMPLE_CHANGE

PE_TENSION - Intension ...

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

CHANGING Parameters details for /IXOS/DC_D_EXAMPLE_CHANGE

PC_RECORD - Original Record

Data type: /IXOS/DC_E_RECORD
Optional: No
Call by Reference: Yes

PC_USR_REC - User changed Record

Data type: /IXOS/DC_E_RECORD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR - internal_error

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

Copy and paste ABAP code example for /IXOS/DC_D_EXAMPLE_CHANGE 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_pc_record  TYPE /IXOS/DC_E_RECORD, "   
lv_pe_tension  TYPE /IXOS/DC_E_RECORD, "   
lv_pi_project  TYPE /IXOS/DC_EC_PROJECT, "   
lv_internal_error  TYPE /IXOS/DC_EC_PROJECT, "   
lv_pc_usr_rec  TYPE /IXOS/DC_E_RECORD, "   
lv_pi_version  TYPE /IXOS/DC_EC_VERSION, "   
lv_pi_tree_num  TYPE /IXOS/DC_EC_VIEW, "   
lv_pi_fktcode  TYPE SY-UCOMM, "   
lv_pi_tabname  TYPE TABNAME, "   
lv_pi_datasource  TYPE /IXOS/DC_EC_DATASOURCE. "   

  CALL FUNCTION '/IXOS/DC_D_EXAMPLE_CHANGE'  "Example for userexit in changing screens
    EXPORTING
         PI_PROJECT = lv_pi_project
         PI_VERSION = lv_pi_version
         PI_TREE_NUM = lv_pi_tree_num
         PI_FKTCODE = lv_pi_fktcode
         PI_TABNAME = lv_pi_tabname
         PI_DATASOURCE = lv_pi_datasource
    IMPORTING
         PE_TENSION = lv_pe_tension
    CHANGING
         PC_RECORD = lv_pc_record
         PC_USR_REC = lv_pc_usr_rec
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " /IXOS/DC_D_EXAMPLE_CHANGE




ABAP code using 7.40 inline data declarations to call FM /IXOS/DC_D_EXAMPLE_CHANGE

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 UCOMM FROM SY INTO @DATA(ld_pi_fktcode).
 
 
 


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!