SAP PLM_PS_CALL_PROJECT_BUILDER Function Module for NOTRANSL: Aufruf Project Builder









PLM_PS_CALL_PROJECT_BUILDER is a standard plm ps call project builder 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: Aufruf Project Builder 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 plm ps call project builder FM, simply by entering the name PLM_PS_CALL_PROJECT_BUILDER into the relevant SAP transaction such as SE37 or SE38.

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



Function PLM_PS_CALL_PROJECT_BUILDER 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 'PLM_PS_CALL_PROJECT_BUILDER'"NOTRANSL: Aufruf Project Builder
EXPORTING
I_PAROBTYP = "Object Type
I_PARKEY1 = "
I_PARKEY2 = "
I_ATTR1 = "
I_ATTR2 = "
I_ATTR3 = "
I_ATTR4 = "
I_ACTVT = "Screens, Function Code That Triggered PAI

IMPORTING
E_TRANSACTION_CODE = "ABAP Program, Current Transaction Code
.



IMPORTING Parameters details for PLM_PS_CALL_PROJECT_BUILDER

I_PAROBTYP - Object Type

Data type: SWOTENTRY-OBJTYPE
Optional: No
Call by Reference: Yes

I_PARKEY1 -

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

I_PARKEY2 -

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

I_ATTR1 -

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

I_ATTR2 -

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

I_ATTR3 -

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

I_ATTR4 -

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

I_ACTVT - Screens, Function Code That Triggered PAI

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

EXPORTING Parameters details for PLM_PS_CALL_PROJECT_BUILDER

E_TRANSACTION_CODE - ABAP Program, Current Transaction Code

Data type: SY-TCODE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PLM_PS_CALL_PROJECT_BUILDER 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_parobtyp  TYPE SWOTENTRY-OBJTYPE, "   
lv_e_transaction_code  TYPE SY-TCODE, "   
lv_i_parkey1  TYPE C, "   
lv_i_parkey2  TYPE C, "   
lv_i_attr1  TYPE C, "   
lv_i_attr2  TYPE C, "   
lv_i_attr3  TYPE C, "   
lv_i_attr4  TYPE C, "   
lv_i_actvt  TYPE C. "   

  CALL FUNCTION 'PLM_PS_CALL_PROJECT_BUILDER'  "NOTRANSL: Aufruf Project Builder
    EXPORTING
         I_PAROBTYP = lv_i_parobtyp
         I_PARKEY1 = lv_i_parkey1
         I_PARKEY2 = lv_i_parkey2
         I_ATTR1 = lv_i_attr1
         I_ATTR2 = lv_i_attr2
         I_ATTR3 = lv_i_attr3
         I_ATTR4 = lv_i_attr4
         I_ACTVT = lv_i_actvt
    IMPORTING
         E_TRANSACTION_CODE = lv_e_transaction_code
. " PLM_PS_CALL_PROJECT_BUILDER




ABAP code using 7.40 inline data declarations to call FM PLM_PS_CALL_PROJECT_BUILDER

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 OBJTYPE FROM SWOTENTRY INTO @DATA(ld_i_parobtyp).
 
"SELECT single TCODE FROM SY INTO @DATA(ld_e_transaction_code).
 
 
 
 
 
 
 
 


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!