SAP SD_CONDITION_CHANGE_DOCS_DISPL Function Module for Change Documents









SD_CONDITION_CHANGE_DOCS_DISPL is a standard sd condition change docs displ SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Documents 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 sd condition change docs displ FM, simply by entering the name SD_CONDITION_CHANGE_DOCS_DISPL into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_CONDITION_CHANGE_DOCS_DISPL 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 'SD_CONDITION_CHANGE_DOCS_DISPL'"Change Documents
EXPORTING
UCOMM = "
* NEW_DISPLAY = ' ' "
.



IMPORTING Parameters details for SD_CONDITION_CHANGE_DOCS_DISPL

UCOMM -

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

NEW_DISPLAY -

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

Copy and paste ABAP code example for SD_CONDITION_CHANGE_DOCS_DISPL 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_ucomm  TYPE STRING, "   
lv_new_display  TYPE C. "   ' '

  CALL FUNCTION 'SD_CONDITION_CHANGE_DOCS_DISPL'  "Change Documents
    EXPORTING
         UCOMM = lv_ucomm
         NEW_DISPLAY = lv_new_display
. " SD_CONDITION_CHANGE_DOCS_DISPL




ABAP code using 7.40 inline data declarations to call FM SD_CONDITION_CHANGE_DOCS_DISPL

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.

 
DATA(ld_new_display) = ' '.
 


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!