SAP PVSDBENG_PNODID_GET_SINGLE Function Module for NOTRANSL: PVS-Knoten Identifikation von DB lesen









PVSDBENG_PNODID_GET_SINGLE is a standard pvsdbeng pnodid get single 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: PVS-Knoten Identifikation von DB lesen 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 pvsdbeng pnodid get single FM, simply by entering the name PVSDBENG_PNODID_GET_SINGLE into the relevant SAP transaction such as SE37 or SE38.

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



Function PVSDBENG_PNODID_GET_SINGLE 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 'PVSDBENG_PNODID_GET_SINGLE'"NOTRANSL: PVS-Knoten Identifikation von DB lesen
EXPORTING
* I_MSG_HANDLING = 'A' "Generic Type
I_PNODID = "iPPE Node: Identification
* I_APPLOBJ_TYPE = "Application Object Type for iPPE
* I_GUID_MISMATCH = PPET_FALSE "Generic Type

IMPORTING
E_PNODID = "iPPE Node: Identification
.



IMPORTING Parameters details for PVSDBENG_PNODID_GET_SINGLE

I_MSG_HANDLING - Generic Type

Data type: C
Default: 'A'
Optional: Yes
Call by Reference: Yes

I_PNODID - iPPE Node: Identification

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

I_APPLOBJ_TYPE - Application Object Type for iPPE

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

I_GUID_MISMATCH - Generic Type

Data type: C
Default: PPET_FALSE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PVSDBENG_PNODID_GET_SINGLE

E_PNODID - iPPE Node: Identification

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

Copy and paste ABAP code example for PVSDBENG_PNODID_GET_SINGLE 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_e_pnodid  TYPE PNODID, "   
lv_i_msg_handling  TYPE C, "   'A'
lv_i_pnodid  TYPE PNODID, "   
lv_i_applobj_type  TYPE PVS_APPLOBJ_TYPE, "   
lv_i_guid_mismatch  TYPE C. "   PPET_FALSE

  CALL FUNCTION 'PVSDBENG_PNODID_GET_SINGLE'  "NOTRANSL: PVS-Knoten Identifikation von DB lesen
    EXPORTING
         I_MSG_HANDLING = lv_i_msg_handling
         I_PNODID = lv_i_pnodid
         I_APPLOBJ_TYPE = lv_i_applobj_type
         I_GUID_MISMATCH = lv_i_guid_mismatch
    IMPORTING
         E_PNODID = lv_e_pnodid
. " PVSDBENG_PNODID_GET_SINGLE




ABAP code using 7.40 inline data declarations to call FM PVSDBENG_PNODID_GET_SINGLE

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.

 
DATA(ld_i_msg_handling) = 'A'.
 
 
 
DATA(ld_i_guid_mismatch) = PPET_FALSE.
 


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!