SAP PPECD_RCPV_WRITE_DOCUMENT Function Module for NOTRANSL: Änderungsbelege für Rezept-Variante
PPECD_RCPV_WRITE_DOCUMENT is a standard ppecd rcpv write document 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: Änderungsbelege für Rezept-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 ppecd rcpv write document FM, simply by entering the name PPECD_RCPV_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: PVSDBRCP
Program Name: SAPLPVSDBRCP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PPECD_RCPV_WRITE_DOCUMENT 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 'PPECD_RCPV_WRITE_DOCUMENT'"NOTRANSL: Änderungsbelege für Rezept-Variante.
EXPORTING
OBJECTID = "Object Value
* UPD_PVRCPD = ' ' "Change Type (U, I, E, D)
* UPD_POSVTX = ' ' "Change Type (U, I, E, D)
* UPD_RESCREATX = ' ' "Change Type (U, I, E, D)
TCODE = "Transaction in which a change was made
UTIME = "Changed At
UDATE = "Creation Date of Change Document
USERNAME = "User Name of Person Responsible in Change Document
* PLANNED_CHANGE_NUMBER = ' ' "Planned change number
* OBJECT_CHANGE_INDICATOR = 'U' "Application object change type (U, I, E, D)
* PLANNED_OR_REAL_CHANGES = ' ' "Application object change type (U, I, E, D)
* NO_CHANGE_POINTERS = PPET_TRUE "Application object change type (U, I, E, D)
TABLES
* XPVRCPD = "Change Document Structure: Generated by RSSCD000
* YPVRCPD = "Change Document Structure: Generated by RSSCD000
* XPOSVTX = "Change Document Structure; Generated by RSSCD000
* YPOSVTX = "Change Document Structure; Generated by RSSCD000
* XRESCREATX = "Change Document Structure; Generated by RSSCD000
* YRESCREATX = "Change Document Structure; Generated by RSSCD000
IMPORTING Parameters details for PPECD_RCPV_WRITE_DOCUMENT
OBJECTID - Object Value
Data type: CDHDR-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
UPD_PVRCPD - Change Type (U, I, E, D)
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
UPD_POSVTX - Change Type (U, I, E, D)
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
UPD_RESCREATX - Change Type (U, I, E, D)
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TCODE - Transaction in which a change was made
Data type: CDHDR-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
UTIME - Changed At
Data type: CDHDR-UTIMEOptional: No
Call by Reference: No ( called with pass by value option)
UDATE - Creation Date of Change Document
Data type: CDHDR-UDATEOptional: No
Call by Reference: No ( called with pass by value option)
USERNAME - User Name of Person Responsible in Change Document
Data type: CDHDR-USERNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PLANNED_CHANGE_NUMBER - Planned change number
Data type: CDHDR-PLANCHNGNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_CHANGE_INDICATOR - Application object change type (U, I, E, D)
Data type: CDHDR-CHANGE_INDDefault: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PLANNED_OR_REAL_CHANGES - Application object change type (U, I, E, D)
Data type: CDHDR-CHANGE_INDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_CHANGE_POINTERS - Application object change type (U, I, E, D)
Data type: CDHDR-CHANGE_INDDefault: PPET_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PPECD_RCPV_WRITE_DOCUMENT
XPVRCPD - Change Document Structure: Generated by RSSCD000
Data type: CDPVRCPDOptional: Yes
Call by Reference: Yes
YPVRCPD - Change Document Structure: Generated by RSSCD000
Data type: CDPVRCPDOptional: Yes
Call by Reference: Yes
XPOSVTX - Change Document Structure; Generated by RSSCD000
Data type: CDRMSAT_POSVTXOptional: Yes
Call by Reference: Yes
YPOSVTX - Change Document Structure; Generated by RSSCD000
Data type: CDRMSAT_POSVTXOptional: Yes
Call by Reference: Yes
XRESCREATX - Change Document Structure; Generated by RSSCD000
Data type: CDRMSAT_RESCREATXOptional: Yes
Call by Reference: Yes
YRESCREATX - Change Document Structure; Generated by RSSCD000
Data type: CDRMSAT_RESCREATXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for PPECD_RCPV_WRITE_DOCUMENT 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_xpvrcpd | TYPE STANDARD TABLE OF CDPVRCPD, " | |||
| lv_objectid | TYPE CDHDR-OBJECTID, " | |||
| lv_upd_pvrcpd | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_upd_posvtx | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_upd_rescreatx | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_tcode | TYPE CDHDR-TCODE, " | |||
| lt_ypvrcpd | TYPE STANDARD TABLE OF CDPVRCPD, " | |||
| lv_utime | TYPE CDHDR-UTIME, " | |||
| lt_xposvtx | TYPE STANDARD TABLE OF CDRMSAT_POSVTX, " | |||
| lv_udate | TYPE CDHDR-UDATE, " | |||
| lt_yposvtx | TYPE STANDARD TABLE OF CDRMSAT_POSVTX, " | |||
| lv_username | TYPE CDHDR-USERNAME, " | |||
| lt_xrescreatx | TYPE STANDARD TABLE OF CDRMSAT_RESCREATX, " | |||
| lt_yrescreatx | TYPE STANDARD TABLE OF CDRMSAT_RESCREATX, " | |||
| lv_planned_change_number | TYPE CDHDR-PLANCHNGNR, " SPACE | |||
| lv_object_change_indicator | TYPE CDHDR-CHANGE_IND, " 'U' | |||
| lv_planned_or_real_changes | TYPE CDHDR-CHANGE_IND, " SPACE | |||
| lv_no_change_pointers | TYPE CDHDR-CHANGE_IND. " PPET_TRUE |
|   CALL FUNCTION 'PPECD_RCPV_WRITE_DOCUMENT' "NOTRANSL: Änderungsbelege für Rezept-Variante |
| EXPORTING | ||
| OBJECTID | = lv_objectid | |
| UPD_PVRCPD | = lv_upd_pvrcpd | |
| UPD_POSVTX | = lv_upd_posvtx | |
| UPD_RESCREATX | = lv_upd_rescreatx | |
| TCODE | = lv_tcode | |
| UTIME | = lv_utime | |
| UDATE | = lv_udate | |
| USERNAME | = lv_username | |
| PLANNED_CHANGE_NUMBER | = lv_planned_change_number | |
| OBJECT_CHANGE_INDICATOR | = lv_object_change_indicator | |
| PLANNED_OR_REAL_CHANGES | = lv_planned_or_real_changes | |
| NO_CHANGE_POINTERS | = lv_no_change_pointers | |
| TABLES | ||
| XPVRCPD | = lt_xpvrcpd | |
| YPVRCPD | = lt_ypvrcpd | |
| XPOSVTX | = lt_xposvtx | |
| YPOSVTX | = lt_yposvtx | |
| XRESCREATX | = lt_xrescreatx | |
| YRESCREATX | = lt_yrescreatx | |
| . " PPECD_RCPV_WRITE_DOCUMENT | ||
ABAP code using 7.40 inline data declarations to call FM PPECD_RCPV_WRITE_DOCUMENT
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 OBJECTID FROM CDHDR INTO @DATA(ld_objectid). | ||||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_pvrcpd). | ||||
| DATA(ld_upd_pvrcpd) | = ' '. | |||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_posvtx). | ||||
| DATA(ld_upd_posvtx) | = ' '. | |||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_rescreatx). | ||||
| DATA(ld_upd_rescreatx) | = ' '. | |||
| "SELECT single TCODE FROM CDHDR INTO @DATA(ld_tcode). | ||||
| "SELECT single UTIME FROM CDHDR INTO @DATA(ld_utime). | ||||
| "SELECT single UDATE FROM CDHDR INTO @DATA(ld_udate). | ||||
| "SELECT single USERNAME FROM CDHDR INTO @DATA(ld_username). | ||||
| "SELECT single PLANCHNGNR FROM CDHDR INTO @DATA(ld_planned_change_number). | ||||
| DATA(ld_planned_change_number) | = ' '. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_object_change_indicator). | ||||
| DATA(ld_object_change_indicator) | = 'U'. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_planned_or_real_changes). | ||||
| DATA(ld_planned_or_real_changes) | = ' '. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_no_change_pointers). | ||||
| DATA(ld_no_change_pointers) | = PPET_TRUE. | |||
Search for further information about these or an SAP related objects