SAP PPECD_POBON_WRITE_DOCUMENT Function Module for CHDO PPEPOBON => Generated by RSSCD000









PPECD_POBON_WRITE_DOCUMENT is a standard ppecd pobon 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 CHDO PPEPOBON => Generated by RSSCD000 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 pobon write document FM, simply by entering the name PPECD_POBON_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function PPECD_POBON_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_POBON_WRITE_DOCUMENT'"CHDO PPEPOBON => Generated by RSSCD000
  EXPORTING
   I_OBJECTID =  "Object Value
*  IS_N_PNODID =  "iPPE Nodes: Identification
*  IS_O_PNODID =  "iPPE Nodes: Identification
*  I_UPD_PNODID = ' ' "Change Type (U, I, E, D)
*  I_UPD_PNODTX = ' ' "Change Type (U, I, E, D)
*  IS_N_PNPOBO =  "RMS-RCP:  Attributes of POB Node Process Operation
*  IS_O_PNPOBO =  "RMS-RCP:  Attributes of POB Node Process Operation
*  I_UPD_PNPOBO = ' ' "Change Type (U, I, E, D)
   I_TCODE =  "Transaction in Which a Change Was Made
   I_UTIME =  "Changed at
   I_UDATE =  "Creation Date of Change Document
   I_USERNAME =  "User Name of 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)

TABLES
*  IT_XPNODTX =  "
*  IT_YPNODTX =  "
.



IMPORTING Parameters details for PPECD_POBON_WRITE_DOCUMENT

I_OBJECTID - Object Value

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

IS_N_PNODID - iPPE Nodes: Identification

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

IS_O_PNODID - iPPE Nodes: Identification

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

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

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

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

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

IS_N_PNPOBO - RMS-RCP: Attributes of POB Node Process Operation

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

IS_O_PNPOBO - RMS-RCP: Attributes of POB Node Process Operation

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

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

Data type: CDPOS-CHNGIND
Default: 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-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

I_UTIME - Changed at

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

I_UDATE - Creation Date of Change Document

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

I_USERNAME - User Name of Person Responsible in Change Document

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

I_PLANNED_CHANGE_NUMBER - Planned Change Number

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

TABLES Parameters details for PPECD_POBON_WRITE_DOCUMENT

IT_XPNODTX -

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

IT_YPNODTX -

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

Copy and paste ABAP code example for PPECD_POBON_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_it_xpnodtx  TYPE STANDARD TABLE OF CDPNODTX, "   
lv_i_objectid  TYPE CDHDR-OBJECTID, "   
lv_is_n_pnodid  TYPE PNODID, "   
lv_is_o_pnodid  TYPE PNODID, "   
lv_i_upd_pnodid  TYPE CDPOS-CHNGIND, "   SPACE
lv_i_upd_pnodtx  TYPE CDPOS-CHNGIND, "   SPACE
lv_is_n_pnpobo  TYPE PNPOBO, "   
lv_is_o_pnpobo  TYPE PNPOBO, "   
lv_i_upd_pnpobo  TYPE CDPOS-CHNGIND, "   SPACE
lv_i_tcode  TYPE CDHDR-TCODE, "   
lt_it_ypnodtx  TYPE STANDARD TABLE OF CDPNODTX, "   
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_POBON_WRITE_DOCUMENT'  "CHDO PPEPOBON => Generated by RSSCD000
    EXPORTING
         I_OBJECTID = lv_i_objectid
         IS_N_PNODID = lv_is_n_pnodid
         IS_O_PNODID = lv_is_o_pnodid
         I_UPD_PNODID = lv_i_upd_pnodid
         I_UPD_PNODTX = lv_i_upd_pnodtx
         IS_N_PNPOBO = lv_is_n_pnpobo
         IS_O_PNPOBO = lv_is_o_pnpobo
         I_UPD_PNPOBO = lv_i_upd_pnpobo
         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
    TABLES
         IT_XPNODTX = lt_it_xpnodtx
         IT_YPNODTX = lt_it_ypnodtx
. " PPECD_POBON_WRITE_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM PPECD_POBON_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_pnodid).
DATA(ld_i_upd_pnodid) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_i_upd_pnodtx).
DATA(ld_i_upd_pnodtx) = ' '.
 
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_i_upd_pnpobo).
DATA(ld_i_upd_pnpobo) = ' '.
 
"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



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!