SAP BUPA_PSCM_WRITE_DOCUMENT Function Module for CHDO BUPA_PSCM => Gen. by RSSCD000









BUPA_PSCM_WRITE_DOCUMENT is a standard bupa pscm 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 BUPA_PSCM => Gen. 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 bupa pscm write document FM, simply by entering the name BUPA_PSCM_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function BUPA_PSCM_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 'BUPA_PSCM_WRITE_DOCUMENT'"CHDO BUPA_PSCM => Gen. by RSSCD000
  EXPORTING
   OBJECTID =  "
*  UPD_ICDTXT_BUPA_PSCM = ' ' "
   N_CMACBPST =  "
   O_YCMACBPST =  "
*  UPD_CMACBPST = ' ' "
   N_CMACBPST2 =  "
   O_YCMACBPST2 =  "
*  UPD_CMACBPST2 = ' ' "
*  UPD_CMACBPSTCA = ' ' "
*  UPD_CMACBPSTCA2 = ' ' "
   TCODE =  "
   UTIME =  "
   UDATE =  "
   USERNAME =  "
*  PLANNED_CHANGE_NUMBER = ' ' "
*  OBJECT_CHANGE_INDICATOR = 'U' "
*  PLANNED_OR_REAL_CHANGES = ' ' "
*  NO_CHANGE_POINTERS = ' ' "

TABLES
   ICDTXT_BUPA_PSCM =  "
   XCMACBPSTCA =  "
   YCMACBPSTCA =  "
   XCMACBPSTCA2 =  "
   YCMACBPSTCA2 =  "
.



IMPORTING Parameters details for BUPA_PSCM_WRITE_DOCUMENT

OBJECTID -

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

UPD_ICDTXT_BUPA_PSCM -

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

N_CMACBPST -

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

O_YCMACBPST -

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

UPD_CMACBPST -

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

N_CMACBPST2 -

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

O_YCMACBPST2 -

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

UPD_CMACBPST2 -

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

UPD_CMACBPSTCA -

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

UPD_CMACBPSTCA2 -

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

TCODE -

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

UTIME -

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

UDATE -

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

USERNAME -

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

PLANNED_CHANGE_NUMBER -

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

OBJECT_CHANGE_INDICATOR -

Data type: CDHDR-CHANGE_IND
Default: 'U'
Optional: No
Call by Reference: No ( called with pass by value option)

PLANNED_OR_REAL_CHANGES -

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

NO_CHANGE_POINTERS -

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

TABLES Parameters details for BUPA_PSCM_WRITE_DOCUMENT

ICDTXT_BUPA_PSCM -

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

XCMACBPSTCA -

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

YCMACBPSTCA -

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

XCMACBPSTCA2 -

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

YCMACBPSTCA2 -

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

Copy and paste ABAP code example for BUPA_PSCM_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_icdtxt_bupa_pscm  TYPE STANDARD TABLE OF CDTXT, "   
lv_upd_icdtxt_bupa_pscm  TYPE CDPOS-CHNGIND, "   SPACE
lv_n_cmacbpst  TYPE CMACBPST, "   
lv_o_ycmacbpst  TYPE CMACBPST, "   
lv_upd_cmacbpst  TYPE CDPOS-CHNGIND, "   SPACE
lv_n_cmacbpst2  TYPE CMACBPST2, "   
lv_o_ycmacbpst2  TYPE CMACBPST2, "   
lv_upd_cmacbpst2  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_cmacbpstca  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_cmacbpstca2  TYPE CDPOS-CHNGIND, "   SPACE
lv_tcode  TYPE CDHDR-TCODE, "   
lt_xcmacbpstca  TYPE STANDARD TABLE OF VCMACBPSTCA, "   
lv_utime  TYPE CDHDR-UTIME, "   
lt_ycmacbpstca  TYPE STANDARD TABLE OF VCMACBPSTCA, "   
lv_udate  TYPE CDHDR-UDATE, "   
lt_xcmacbpstca2  TYPE STANDARD TABLE OF VCMACBPSTCA2, "   
lv_username  TYPE CDHDR-USERNAME, "   
lt_ycmacbpstca2  TYPE STANDARD TABLE OF VCMACBPSTCA2, "   
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. "   SPACE

  CALL FUNCTION 'BUPA_PSCM_WRITE_DOCUMENT'  "CHDO BUPA_PSCM => Gen. by RSSCD000
    EXPORTING
         OBJECTID = lv_objectid
         UPD_ICDTXT_BUPA_PSCM = lv_upd_icdtxt_bupa_pscm
         N_CMACBPST = lv_n_cmacbpst
         O_YCMACBPST = lv_o_ycmacbpst
         UPD_CMACBPST = lv_upd_cmacbpst
         N_CMACBPST2 = lv_n_cmacbpst2
         O_YCMACBPST2 = lv_o_ycmacbpst2
         UPD_CMACBPST2 = lv_upd_cmacbpst2
         UPD_CMACBPSTCA = lv_upd_cmacbpstca
         UPD_CMACBPSTCA2 = lv_upd_cmacbpstca2
         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
         ICDTXT_BUPA_PSCM = lt_icdtxt_bupa_pscm
         XCMACBPSTCA = lt_xcmacbpstca
         YCMACBPSTCA = lt_ycmacbpstca
         XCMACBPSTCA2 = lt_xcmacbpstca2
         YCMACBPSTCA2 = lt_ycmacbpstca2
. " BUPA_PSCM_WRITE_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM BUPA_PSCM_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_icdtxt_bupa_pscm).
DATA(ld_upd_icdtxt_bupa_pscm) = ' '.
 
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_cmacbpst).
DATA(ld_upd_cmacbpst) = ' '.
 
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_cmacbpst2).
DATA(ld_upd_cmacbpst2) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_cmacbpstca).
DATA(ld_upd_cmacbpstca) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_cmacbpstca2).
DATA(ld_upd_cmacbpstca2) = ' '.
 
"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!