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

Function PPECD_EQRREL_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_EQRREL_WRITE_DOCUMENT'"NOTRANSL: Änderungsbelege für EQR-Relationen.
EXPORTING
I_OBJECTID = "Object value
* IS_N_PREQR = "RMS-RCP: iPPE Relationship: Equipment Requirement
* IS_O_PREQR = "RMS-RCP: iPPE Relationship: Equipment Requirement
* I_UPD_PREQR = ' ' "Change Type (U, I, E, D)
I_TCODE = "Transaction in which a change was made
I_UTIME = "Time changed
I_UDATE = "Creation date of the change document
I_USERNAME = "User name of the person responsible in change document
* I_PLANNED_CHANGE_NUMBER = ' ' "Planned change number
* I_OBJECT_CHANGE_INDICATOR = 'U' "Application object change type (U, I, E, D)
* I_PLANNED_OR_REAL_CHANGES = ' ' "Application object change type (U, I, E, D)
* I_NO_CHANGE_POINTERS = ' ' "Application object change type (U, I, E, D)
IMPORTING Parameters details for PPECD_EQRREL_WRITE_DOCUMENT
I_OBJECTID - Object value
Data type: CDHDR-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
IS_N_PREQR - RMS-RCP: iPPE Relationship: Equipment Requirement
Data type: PREQROptional: Yes
Call by Reference: No ( called with pass by value option)
IS_O_PREQR - RMS-RCP: iPPE Relationship: Equipment Requirement
Data type: PREQROptional: Yes
Call by Reference: No ( called with pass by value option)
I_UPD_PREQR - Change Type (U, I, E, D)
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TCODE - Transaction in which a change was made
Data type: CDHDR-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
I_UTIME - Time changed
Data type: CDHDR-UTIMEOptional: No
Call by Reference: No ( called with pass by value option)
I_UDATE - Creation date of the change document
Data type: CDHDR-UDATEOptional: No
Call by Reference: No ( called with pass by value option)
I_USERNAME - User name of the person responsible in change document
Data type: CDHDR-USERNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_PLANNED_CHANGE_NUMBER - Planned change number
Data type: CDHDR-PLANCHNGNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_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)
I_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)
I_NO_CHANGE_POINTERS - 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)
Copy and paste ABAP code example for PPECD_EQRREL_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: | ||||
| lv_i_objectid | TYPE CDHDR-OBJECTID, " | |||
| lv_is_n_preqr | TYPE PREQR, " | |||
| lv_is_o_preqr | TYPE PREQR, " | |||
| lv_i_upd_preqr | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_i_tcode | TYPE CDHDR-TCODE, " | |||
| lv_i_utime | TYPE CDHDR-UTIME, " | |||
| lv_i_udate | TYPE CDHDR-UDATE, " | |||
| lv_i_username | TYPE CDHDR-USERNAME, " | |||
| lv_i_planned_change_number | TYPE CDHDR-PLANCHNGNR, " SPACE | |||
| lv_i_object_change_indicator | TYPE CDHDR-CHANGE_IND, " 'U' | |||
| lv_i_planned_or_real_changes | TYPE CDHDR-CHANGE_IND, " SPACE | |||
| lv_i_no_change_pointers | TYPE CDHDR-CHANGE_IND. " SPACE |
|   CALL FUNCTION 'PPECD_EQRREL_WRITE_DOCUMENT' "NOTRANSL: Änderungsbelege für EQR-Relationen |
| EXPORTING | ||
| I_OBJECTID | = lv_i_objectid | |
| IS_N_PREQR | = lv_is_n_preqr | |
| IS_O_PREQR | = lv_is_o_preqr | |
| I_UPD_PREQR | = lv_i_upd_preqr | |
| I_TCODE | = lv_i_tcode | |
| I_UTIME | = lv_i_utime | |
| I_UDATE | = lv_i_udate | |
| I_USERNAME | = lv_i_username | |
| I_PLANNED_CHANGE_NUMBER | = lv_i_planned_change_number | |
| I_OBJECT_CHANGE_INDICATOR | = lv_i_object_change_indicator | |
| I_PLANNED_OR_REAL_CHANGES | = lv_i_planned_or_real_changes | |
| I_NO_CHANGE_POINTERS | = lv_i_no_change_pointers | |
| . " PPECD_EQRREL_WRITE_DOCUMENT | ||
ABAP code using 7.40 inline data declarations to call FM PPECD_EQRREL_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_i_objectid). | ||||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_i_upd_preqr). | ||||
| DATA(ld_i_upd_preqr) | = ' '. | |||
| "SELECT single TCODE FROM CDHDR INTO @DATA(ld_i_tcode). | ||||
| "SELECT single UTIME FROM CDHDR INTO @DATA(ld_i_utime). | ||||
| "SELECT single UDATE FROM CDHDR INTO @DATA(ld_i_udate). | ||||
| "SELECT single USERNAME FROM CDHDR INTO @DATA(ld_i_username). | ||||
| "SELECT single PLANCHNGNR FROM CDHDR INTO @DATA(ld_i_planned_change_number). | ||||
| DATA(ld_i_planned_change_number) | = ' '. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_i_object_change_indicator). | ||||
| DATA(ld_i_object_change_indicator) | = 'U'. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_i_planned_or_real_changes). | ||||
| DATA(ld_i_planned_or_real_changes) | = ' '. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_i_no_change_pointers). | ||||
| DATA(ld_i_no_change_pointers) | = ' '. | |||
Search for further information about these or an SAP related objects