SAP HR_DELETE_PC_VNAME_COMPLETE Function Module for
HR_DELETE_PC_VNAME_COMPLETE is a standard hr delete pc vname complete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hr delete pc vname complete FM, simply by entering the name HR_DELETE_PC_VNAME_COMPLETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHPC
Program Name: SAPLRHPC
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function HR_DELETE_PC_VNAME_COMPLETE 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 'HR_DELETE_PC_VNAME_COMPLETE'".
EXPORTING
I77KD = "Key data of a planning group
* COMMIT_WORK = 'X' "Flag: Execute Commit work if successful
EXCEPTIONS
DB_ERROR = 1
IMPORTING Parameters details for HR_DELETE_PC_VNAME_COMPLETE
I77KD - Key data of a planning group
Data type: T77KDOptional: No
Call by Reference: No ( called with pass by value option)
COMMIT_WORK - Flag: Execute Commit work if successful
Data type: PLOG-HISTODefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_ERROR - Changes were not made to the database
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_DELETE_PC_VNAME_COMPLETE 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_i77kd | TYPE T77KD, " | |||
| lv_db_error | TYPE T77KD, " | |||
| lv_commit_work | TYPE PLOG-HISTO. " 'X' |
|   CALL FUNCTION 'HR_DELETE_PC_VNAME_COMPLETE' " |
| EXPORTING | ||
| I77KD | = lv_i77kd | |
| COMMIT_WORK | = lv_commit_work | |
| EXCEPTIONS | ||
| DB_ERROR = 1 | ||
| . " HR_DELETE_PC_VNAME_COMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM HR_DELETE_PC_VNAME_COMPLETE
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 HISTO FROM PLOG INTO @DATA(ld_commit_work). | ||||
| DATA(ld_commit_work) | = 'X'. | |||
Search for further information about these or an SAP related objects