SAP SWJ_VIEW_EDIT_CONDITION Function Module for
SWJ_VIEW_EDIT_CONDITION is a standard swj view edit condition 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 view edit condition FM, simply by entering the name SWJ_VIEW_EDIT_CONDITION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWJ_COND_VIEW
Program Name: SAPLSWJ_COND_VIEW
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWJ_VIEW_EDIT_CONDITION 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_VIEW_EDIT_CONDITION'".
EXPORTING
* DEFAULTS = "Default Values
IMPORTING
CHANGED = "Data was changed
CHANGING
CONDITION_DEF = "Structured Data Type for Parameter Condition
EXCEPTIONS
ACTION_CANCELED = 1
IMPORTING Parameters details for SWJ_VIEW_EDIT_CONDITION
DEFAULTS - Default Values
Data type: SWJ_PDEFLTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SWJ_VIEW_EDIT_CONDITION
CHANGED - Data was changed
Data type: XFLAGOptional: No
Call by Reference: Yes
CHANGING Parameters details for SWJ_VIEW_EDIT_CONDITION
CONDITION_DEF - Structured Data Type for Parameter Condition
Data type: SWJ_PCONDOptional: No
Call by Reference: Yes
EXCEPTIONS details
ACTION_CANCELED - Activity Terminated
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWJ_VIEW_EDIT_CONDITION 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_changed | TYPE XFLAG, " | |||
| lv_defaults | TYPE SWJ_PDEFLT, " | |||
| lv_condition_def | TYPE SWJ_PCOND, " | |||
| lv_action_canceled | TYPE SWJ_PCOND. " |
|   CALL FUNCTION 'SWJ_VIEW_EDIT_CONDITION' " |
| EXPORTING | ||
| DEFAULTS | = lv_defaults | |
| IMPORTING | ||
| CHANGED | = lv_changed | |
| CHANGING | ||
| CONDITION_DEF | = lv_condition_def | |
| EXCEPTIONS | ||
| ACTION_CANCELED = 1 | ||
| . " SWJ_VIEW_EDIT_CONDITION | ||
ABAP code using 7.40 inline data declarations to call FM SWJ_VIEW_EDIT_CONDITION
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