SAP PPECD_BAL_WRITE_DOCUMENT Function Module for NOTRANSL: Änderungsbelege für die Abtaktung









PPECD_BAL_WRITE_DOCUMENT is a standard ppecd bal 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 die Abtaktung 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 bal write document FM, simply by entering the name PPECD_BAL_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function PPECD_BAL_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_BAL_WRITE_DOCUMENT'"NOTRANSL: Änderungsbelege für die Abtaktung
  EXPORTING
   OBJECTID =  "Object value
*  UPD_LBVALID = ' ' "Change Type (U, I, E, D)
*  N_LINEBAL =  "Line Balance Versions in iPPE
*  O_LINEBAL =  "Line Balance Versions in iPPE
*  UPD_LINEBAL = ' ' "Change Type (U, I, E, D)
*  UPD_LINEBALT = ' ' "Change Type (U, I, E, D)
*  UPD_PRELID = ' ' "Change Type (U, I, E, D)
*  UPD_PRRES = ' ' "Change Type (U, I, E, D)
*  UPD_PRBAL = ' ' "Change Type (U, I, E, D)
   TCODE =  "Transaction in which a change was made
   UTIME =  "Time changed
   UDATE =  "Creation date of the change document
   USERNAME =  "User name of the 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 = ' ' "Application object change type (U, I, E, D)

TABLES
*  XLBVALID =  "Change Document Structure; Generated by RSSCD000
*  YPRBAL =  "Change Document Structure; Generated by RSSCD000
*  YLBVALID =  "Change Document Structure; Generated by RSSCD000
*  XPRELID =  "Change Document Structure; Generated by RSSCD000
*  YPRELID =  "Change Document Structure; Generated by RSSCD000
*  XPRRES =  "Change Document Structure; Generated by RSSCD000
*  YPRRES =  "Change Document Structure; Generated by RSSCD000
*  XLINEBALT =  "Change Document Structure; Generated by RSSCD000
*  YLINEBALT =  "Change Document Structure; Generated by RSSCD000
*  XPRBAL =  "Change Document Structure; Generated by RSSCD000
.



IMPORTING Parameters details for PPECD_BAL_WRITE_DOCUMENT

OBJECTID - Object value

Data type: CDHDR-OBJECTID
Optional: No
Call by Reference: No ( called with pass by value option)

UPD_LBVALID - Change Type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

N_LINEBAL - Line Balance Versions in iPPE

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

O_LINEBAL - Line Balance Versions in iPPE

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

UPD_LINEBAL - Change Type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPD_LINEBALT - Change Type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPD_PRELID - Change Type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPD_PRRES - Change Type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPD_PRBAL - Change Type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCODE - Transaction in which a change was made

Data type: CDHDR-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

UTIME - Time changed

Data type: CDHDR-UTIME
Optional: No
Call by Reference: No ( called with pass by value option)

UDATE - Creation date of the change document

Data type: CDHDR-UDATE
Optional: No
Call by Reference: No ( called with pass by value option)

USERNAME - User name of the person responsible in change document

Data type: CDHDR-USERNAME
Optional: No
Call by Reference: No ( called with pass by value option)

PLANNED_CHANGE_NUMBER - Planned change number

Data type: CDHDR-PLANCHNGNR
Default: 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_IND
Default: '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_IND
Default: 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_IND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for PPECD_BAL_WRITE_DOCUMENT

XLBVALID - Change Document Structure; Generated by RSSCD000

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

YPRBAL - Change Document Structure; Generated by RSSCD000

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

YLBVALID - Change Document Structure; Generated by RSSCD000

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

XPRELID - Change Document Structure; Generated by RSSCD000

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

YPRELID - Change Document Structure; Generated by RSSCD000

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

XPRRES - Change Document Structure; Generated by RSSCD000

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

YPRRES - Change Document Structure; Generated by RSSCD000

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

XLINEBALT - Change Document Structure; Generated by RSSCD000

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

YLINEBALT - Change Document Structure; Generated by RSSCD000

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

XPRBAL - Change Document Structure; Generated by RSSCD000

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

Copy and paste ABAP code example for PPECD_BAL_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_objectid  TYPE CDHDR-OBJECTID, "   
lt_xlbvalid  TYPE STANDARD TABLE OF CDBALLBVALID, "   
lt_yprbal  TYPE STANDARD TABLE OF CDBALPRBAL, "   
lv_upd_lbvalid  TYPE CDPOS-CHNGIND, "   SPACE
lv_n_linebal  TYPE LINEBAL, "   
lv_o_linebal  TYPE LINEBAL, "   
lv_upd_linebal  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_linebalt  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_prelid  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_prres  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_prbal  TYPE CDPOS-CHNGIND, "   SPACE
lv_tcode  TYPE CDHDR-TCODE, "   
lt_ylbvalid  TYPE STANDARD TABLE OF CDBALLBVALID, "   
lv_utime  TYPE CDHDR-UTIME, "   
lt_xprelid  TYPE STANDARD TABLE OF CDBALPRELID, "   
lv_udate  TYPE CDHDR-UDATE, "   
lt_yprelid  TYPE STANDARD TABLE OF CDBALPRELID, "   
lt_xprres  TYPE STANDARD TABLE OF CDBALPRRES, "   
lv_username  TYPE CDHDR-USERNAME, "   
lt_yprres  TYPE STANDARD TABLE OF CDBALPRRES, "   
lv_planned_change_number  TYPE CDHDR-PLANCHNGNR, "   SPACE
lt_xlinebalt  TYPE STANDARD TABLE OF CDBALLINEBALT, "   
lv_object_change_indicator  TYPE CDHDR-CHANGE_IND, "   'U'
lt_ylinebalt  TYPE STANDARD TABLE OF CDBALLINEBALT, "   
lv_planned_or_real_changes  TYPE CDHDR-CHANGE_IND, "   SPACE
lt_xprbal  TYPE STANDARD TABLE OF CDBALPRBAL, "   
lv_no_change_pointers  TYPE CDHDR-CHANGE_IND. "   SPACE

  CALL FUNCTION 'PPECD_BAL_WRITE_DOCUMENT'  "NOTRANSL: Änderungsbelege für die Abtaktung
    EXPORTING
         OBJECTID = lv_objectid
         UPD_LBVALID = lv_upd_lbvalid
         N_LINEBAL = lv_n_linebal
         O_LINEBAL = lv_o_linebal
         UPD_LINEBAL = lv_upd_linebal
         UPD_LINEBALT = lv_upd_linebalt
         UPD_PRELID = lv_upd_prelid
         UPD_PRRES = lv_upd_prres
         UPD_PRBAL = lv_upd_prbal
         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
         XLBVALID = lt_xlbvalid
         YPRBAL = lt_yprbal
         YLBVALID = lt_ylbvalid
         XPRELID = lt_xprelid
         YPRELID = lt_yprelid
         XPRRES = lt_xprres
         YPRRES = lt_yprres
         XLINEBALT = lt_xlinebalt
         YLINEBALT = lt_ylinebalt
         XPRBAL = lt_xprbal
. " PPECD_BAL_WRITE_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM PPECD_BAL_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_lbvalid).
DATA(ld_upd_lbvalid) = ' '.
 
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_linebal).
DATA(ld_upd_linebal) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_linebalt).
DATA(ld_upd_linebalt) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_prelid).
DATA(ld_upd_prelid) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_prres).
DATA(ld_upd_prres) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_prbal).
DATA(ld_upd_prbal) = ' '.
 
"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) = ' '.
 


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!