SAP SWJ_CONDDEF_MODIFY Function Module for









SWJ_CONDDEF_MODIFY is a standard swj conddef modify 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 swj conddef modify FM, simply by entering the name SWJ_CONDDEF_MODIFY into the relevant SAP transaction such as SE37 or SE38.

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



Function SWJ_CONDDEF_MODIFY 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 'SWJ_CONDDEF_MODIFY'"
EXPORTING
CONDITION_GUID = "ID for Parameter Condition
* DO_COMMIT = ' ' "Checkbox Field
CONDITION_DEF = "Condition definition
* DELETE = 'X' "

EXCEPTIONS
CONDITION_DOES_NOT_EXIST = 1
.



IMPORTING Parameters details for SWJ_CONDDEF_MODIFY

CONDITION_GUID - ID for Parameter Condition

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

DO_COMMIT - Checkbox Field

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

CONDITION_DEF - Condition definition

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

DELETE -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

CONDITION_DOES_NOT_EXIST - Condition does not exist

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SWJ_CONDDEF_MODIFY 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_condition_guid  TYPE SWJ_CONDID, "   
lv_condition_does_not_exist  TYPE SWJ_CONDID, "   
lv_do_commit  TYPE XFELD, "   SPACE
lv_condition_def  TYPE SWBCONDTAB, "   
lv_delete  TYPE XFELD. "   'X'

  CALL FUNCTION 'SWJ_CONDDEF_MODIFY'  "
    EXPORTING
         CONDITION_GUID = lv_condition_guid
         DO_COMMIT = lv_do_commit
         CONDITION_DEF = lv_condition_def
         DELETE = lv_delete
    EXCEPTIONS
        CONDITION_DOES_NOT_EXIST = 1
. " SWJ_CONDDEF_MODIFY




ABAP code using 7.40 inline data declarations to call FM SWJ_CONDDEF_MODIFY

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_do_commit) = ' '.
 
 
DATA(ld_delete) = 'X'.
 


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!