SAP PVSDBENG_PXARCID_GET Function Module for NOTRANSL: Existenzprüfung für Archivierungsvormerkung









PVSDBENG_PXARCID_GET is a standard pvsdbeng pxarcid get 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: Existenzprüfung für Archivierungsvormerkung 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 pxarcid get FM, simply by entering the name PVSDBENG_PXARCID_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function PVSDBENG_PXARCID_GET 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_PXARCID_GET'"NOTRANSL: Existenzprüfung für Archivierungsvormerkung
IMPORTING
EV_EXISTS = "Generic Type

CHANGING
CS_PXARCID = "Archiving Indicator

EXCEPTIONS
PARAMETER_ERROR = 1
.



EXPORTING Parameters details for PVSDBENG_PXARCID_GET

EV_EXISTS - Generic Type

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

CHANGING Parameters details for PVSDBENG_PXARCID_GET

CS_PXARCID - Archiving Indicator

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

EXCEPTIONS details

PARAMETER_ERROR - Input data missing

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PVSDBENG_PXARCID_GET 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_ev_exists  TYPE C, "   
lv_cs_pxarcid  TYPE PPET_PXARCID_LI, "   
lv_parameter_error  TYPE PPET_PXARCID_LI. "   

  CALL FUNCTION 'PVSDBENG_PXARCID_GET'  "NOTRANSL: Existenzprüfung für Archivierungsvormerkung
    IMPORTING
         EV_EXISTS = lv_ev_exists
    CHANGING
         CS_PXARCID = lv_cs_pxarcid
    EXCEPTIONS
        PARAMETER_ERROR = 1
. " PVSDBENG_PXARCID_GET




ABAP code using 7.40 inline data declarations to call FM PVSDBENG_PXARCID_GET

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.

 
 
 


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!