SAP PVSCUST_PVTYPE_BY_CRITERIA Function Module for NOTRANSL: Lesen der Typinformationen zu einer PVS-Variante
PVSCUST_PVTYPE_BY_CRITERIA is a standard pvscust pvtype by criteria 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: Lesen der Typinformationen zu einer PVS-Variante 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 pvscust pvtype by criteria FM, simply by entering the name PVSCUST_PVTYPE_BY_CRITERIA into the relevant SAP transaction such as SE37 or SE38.
Function Group: PVSCUST
Program Name: SAPLPVSCUST
Main Program: SAPLPVSCUST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PVSCUST_PVTYPE_BY_CRITERIA 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 'PVSCUST_PVTYPE_BY_CRITERIA'"NOTRANSL: Lesen der Typinformationen zu einer PVS-Variante.
EXPORTING
* IM_LAYER = "iPPE Level
* IM_MSG_HANDLING = 'A' "Generic Type
* IM_LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
* IV_BUFFER_RESET = "Generic Type
TABLES
EX_PVTYPE_TAB = "Generated Table for View
EXCEPTIONS
UNKNOWN_LAYER = 1
IMPORTING Parameters details for PVSCUST_PVTYPE_BY_CRITERIA
IM_LAYER - iPPE Level
Data type: CPVTYPE-PVSLAYEROptional: Yes
Call by Reference: No ( called with pass by value option)
IM_MSG_HANDLING - Generic Type
Data type: CDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_LANGU - ABAP System Field: Language Key of Text Environment
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_BUFFER_RESET - Generic Type
Data type: COptional: Yes
Call by Reference: Yes
TABLES Parameters details for PVSCUST_PVTYPE_BY_CRITERIA
EX_PVTYPE_TAB - Generated Table for View
Data type: V_CPVTYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
UNKNOWN_LAYER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PVSCUST_PVTYPE_BY_CRITERIA 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_im_layer | TYPE CPVTYPE-PVSLAYER, " | |||
| lt_ex_pvtype_tab | TYPE STANDARD TABLE OF V_CPVTYPE, " | |||
| lv_unknown_layer | TYPE V_CPVTYPE, " | |||
| lv_im_msg_handling | TYPE C, " 'A' | |||
| lv_im_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_iv_buffer_reset | TYPE C. " |
|   CALL FUNCTION 'PVSCUST_PVTYPE_BY_CRITERIA' "NOTRANSL: Lesen der Typinformationen zu einer PVS-Variante |
| EXPORTING | ||
| IM_LAYER | = lv_im_layer | |
| IM_MSG_HANDLING | = lv_im_msg_handling | |
| IM_LANGU | = lv_im_langu | |
| IV_BUFFER_RESET | = lv_iv_buffer_reset | |
| TABLES | ||
| EX_PVTYPE_TAB | = lt_ex_pvtype_tab | |
| EXCEPTIONS | ||
| UNKNOWN_LAYER = 1 | ||
| . " PVSCUST_PVTYPE_BY_CRITERIA | ||
ABAP code using 7.40 inline data declarations to call FM PVSCUST_PVTYPE_BY_CRITERIA
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 PVSLAYER FROM CPVTYPE INTO @DATA(ld_im_layer). | ||||
| DATA(ld_im_msg_handling) | = 'A'. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_im_langu). | ||||
| DATA(ld_im_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects