SAP CJDW_PRPS_STATUS_SET Function Module for NOTRANSL: PSP-Elementstatus setzen









CJDW_PRPS_STATUS_SET is a standard cjdw prps status set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: PSP-Elementstatus setzen 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 cjdw prps status set FM, simply by entering the name CJDW_PRPS_STATUS_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function CJDW_PRPS_STATUS_SET 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 'CJDW_PRPS_STATUS_SET'"NOTRANSL: PSP-Elementstatus setzen
EXPORTING
I_POSID = "Project Definition
I_ACTIVITY = "Business Transaction

TABLES
E_ACTIVITY_MESSAGE = "Message Collector

EXCEPTIONS
ERROR_OCCURED = 1 POSID_EMPTY = 2 WBS_ELEM_NOT_FOUND = 3
.



IMPORTING Parameters details for CJDW_PRPS_STATUS_SET

I_POSID - Project Definition

Data type: PRPS-POSID
Optional: No
Call by Reference: Yes

I_ACTIVITY - Business Transaction

Data type: TJ01-VRGNG
Optional: No
Call by Reference: Yes

TABLES Parameters details for CJDW_PRPS_STATUS_SET

E_ACTIVITY_MESSAGE - Message Collector

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

EXCEPTIONS details

ERROR_OCCURED -

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

POSID_EMPTY -

Data type:
Optional: No
Call by Reference: Yes

WBS_ELEM_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CJDW_PRPS_STATUS_SET 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_i_posid  TYPE PRPS-POSID, "   
lv_error_occured  TYPE PRPS, "   
lt_e_activity_message  TYPE STANDARD TABLE OF SMESG, "   
lv_i_activity  TYPE TJ01-VRGNG, "   
lv_posid_empty  TYPE TJ01, "   
lv_wbs_elem_not_found  TYPE TJ01. "   

  CALL FUNCTION 'CJDW_PRPS_STATUS_SET'  "NOTRANSL: PSP-Elementstatus setzen
    EXPORTING
         I_POSID = lv_i_posid
         I_ACTIVITY = lv_i_activity
    TABLES
         E_ACTIVITY_MESSAGE = lt_e_activity_message
    EXCEPTIONS
        ERROR_OCCURED = 1
        POSID_EMPTY = 2
        WBS_ELEM_NOT_FOUND = 3
. " CJDW_PRPS_STATUS_SET




ABAP code using 7.40 inline data declarations to call FM CJDW_PRPS_STATUS_SET

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 POSID FROM PRPS INTO @DATA(ld_i_posid).
 
 
 
"SELECT single VRGNG FROM TJ01 INTO @DATA(ld_i_activity).
 
 
 


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!