SAP PLM_PS_MATERIAL_TRANS Function Module for NOTRANSL: Anzeigen Material auf Portal heraus
PLM_PS_MATERIAL_TRANS is a standard plm ps material trans 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: Anzeigen Material auf Portal heraus 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 material trans FM, simply by entering the name PLM_PS_MATERIAL_TRANS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PLM_PS_PORTAL_TRANS
Program Name: SAPLPLM_PS_PORTAL_TRANS
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PLM_PS_MATERIAL_TRANS 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_MATERIAL_TRANS'"NOTRANSL: Anzeigen Material auf Portal heraus.
EXPORTING
I_PAROBTYP = "Object Type
I_TRANS_TYPE = "
I_PARKEY1 = "
I_PARKEY2 = "
I_INFOITEM = "
I_AKTTYPE = "Screens, Function Code That Triggered PAI
I_ATTR1 = "
I_ATTR2 = "
I_ATTR3 = "
I_ATTR4 = "
IMPORTING
E_TRANSACTION_CODE = "ABAP Program, Current Transaction Code
TABLES
ET_BDCDATA = "Batch Input: New Table Field Structure
IMPORTING Parameters details for PLM_PS_MATERIAL_TRANS
I_PAROBTYP - Object Type
Data type: SWOTENTRY-OBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_TRANS_TYPE -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_PARKEY1 -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_PARKEY2 -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_INFOITEM -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_AKTTYPE - Screens, Function Code That Triggered PAI
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
I_ATTR1 -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_ATTR2 -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_ATTR3 -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_ATTR4 -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PLM_PS_MATERIAL_TRANS
E_TRANSACTION_CODE - ABAP Program, Current Transaction Code
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PLM_PS_MATERIAL_TRANS
ET_BDCDATA - Batch Input: New Table Field Structure
Data type: BDCDATAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PLM_PS_MATERIAL_TRANS 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: | ||||
| lt_et_bdcdata | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_i_parobtyp | TYPE SWOTENTRY-OBJTYPE, " | |||
| lv_e_transaction_code | TYPE SY-TCODE, " | |||
| lv_i_trans_type | TYPE C, " | |||
| lv_i_parkey1 | TYPE C, " | |||
| lv_i_parkey2 | TYPE C, " | |||
| lv_i_infoitem | TYPE C, " | |||
| lv_i_akttype | TYPE SY-UCOMM, " | |||
| lv_i_attr1 | TYPE C, " | |||
| lv_i_attr2 | TYPE C, " | |||
| lv_i_attr3 | TYPE C, " | |||
| lv_i_attr4 | TYPE C. " |
|   CALL FUNCTION 'PLM_PS_MATERIAL_TRANS' "NOTRANSL: Anzeigen Material auf Portal heraus |
| EXPORTING | ||
| I_PAROBTYP | = lv_i_parobtyp | |
| I_TRANS_TYPE | = lv_i_trans_type | |
| I_PARKEY1 | = lv_i_parkey1 | |
| I_PARKEY2 | = lv_i_parkey2 | |
| I_INFOITEM | = lv_i_infoitem | |
| I_AKTTYPE | = lv_i_akttype | |
| I_ATTR1 | = lv_i_attr1 | |
| I_ATTR2 | = lv_i_attr2 | |
| I_ATTR3 | = lv_i_attr3 | |
| I_ATTR4 | = lv_i_attr4 | |
| IMPORTING | ||
| E_TRANSACTION_CODE | = lv_e_transaction_code | |
| TABLES | ||
| ET_BDCDATA | = lt_et_bdcdata | |
| . " PLM_PS_MATERIAL_TRANS | ||
ABAP code using 7.40 inline data declarations to call FM PLM_PS_MATERIAL_TRANS
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). | ||||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_i_akttype). | ||||
Search for further information about these or an SAP related objects