SAP SWJ_API_EDIT_PCONDITION Function Module for









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

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



Function SWJ_API_EDIT_PCONDITION 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_API_EDIT_PCONDITION'"
EXPORTING
GUID = "
* DEFAULTS = "Default Values
* COPY_ON_MODIFY = ' ' "

IMPORTING
NEW_GUID = "

CHANGING
* TR_ORDER = "Transport Request

EXCEPTIONS
CONDITION_NOT_FOUND = 1 CANCELLED = 2
.



IMPORTING Parameters details for SWJ_API_EDIT_PCONDITION

GUID -

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

DEFAULTS - Default Values

Data type: SWJ_PDEFLT
Optional: Yes
Call by Reference: Yes

COPY_ON_MODIFY -

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

EXPORTING Parameters details for SWJ_API_EDIT_PCONDITION

NEW_GUID -

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

CHANGING Parameters details for SWJ_API_EDIT_PCONDITION

TR_ORDER - Transport Request

Data type: E070-TRKORR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

CONDITION_NOT_FOUND - Not Found

Data type:
Optional: No
Call by Reference: Yes

CANCELLED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SWJ_API_EDIT_PCONDITION 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_guid  TYPE SWJ_CONDID, "   
lv_new_guid  TYPE SWJ_CONDID, "   
lv_tr_order  TYPE E070-TRKORR, "   
lv_condition_not_found  TYPE E070, "   
lv_defaults  TYPE SWJ_PDEFLT, "   
lv_cancelled  TYPE SWJ_PDEFLT, "   
lv_copy_on_modify  TYPE XFELD. "   SPACE

  CALL FUNCTION 'SWJ_API_EDIT_PCONDITION'  "
    EXPORTING
         GUID = lv_guid
         DEFAULTS = lv_defaults
         COPY_ON_MODIFY = lv_copy_on_modify
    IMPORTING
         NEW_GUID = lv_new_guid
    CHANGING
         TR_ORDER = lv_tr_order
    EXCEPTIONS
        CONDITION_NOT_FOUND = 1
        CANCELLED = 2
. " SWJ_API_EDIT_PCONDITION




ABAP code using 7.40 inline data declarations to call FM SWJ_API_EDIT_PCONDITION

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 TRKORR FROM E070 INTO @DATA(ld_tr_order).
 
 
 
 
DATA(ld_copy_on_modify) = ' '.
 


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!