SAP SGT_MD_WRITE_DOCUMENT Function Module for CHDO SGT_MD => Gen. by RSSCD000









SGT_MD_WRITE_DOCUMENT is a standard sgt md 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 SGT_MD => 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 sgt md write document FM, simply by entering the name SGT_MD_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function SGT_MD_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 'SGT_MD_WRITE_DOCUMENT'"CHDO SGT_MD => Gen. by RSSCD000
  EXPORTING
   OBJECTID =  "
*  UPD_SGT_MADKA = ' ' "
*  UPD_SGT_MARM = ' ' "
*  UPD_SGT_MLGN = ' ' "
*  UPD_SGT_MLGT = ' ' "
*  UPD_SGT_MRP = ' ' "
*  UPD_SGT_MRP_GN = ' ' "
*  UPD_SGT_MVKE = ' ' "
   TCODE =  "
   UTIME =  "
   UDATE =  "
   USERNAME =  "
*  PLANNED_CHANGE_NUMBER = ' ' "
*  OBJECT_CHANGE_INDICATOR = 'U' "
*  PLANNED_OR_REAL_CHANGES = ' ' "
*  NO_CHANGE_POINTERS = ' ' "

TABLES
*  XSGT_MADKA =  "
*  YSGT_MRP =  "
*  XSGT_MRP_GN =  "
*  YSGT_MRP_GN =  "
*  XSGT_MVKE =  "
*  YSGT_MVKE =  "
*  YSGT_MADKA =  "
*  XSGT_MARM =  "
*  YSGT_MARM =  "
*  XSGT_MLGN =  "
*  YSGT_MLGN =  "
*  XSGT_MLGT =  "
*  YSGT_MLGT =  "
*  XSGT_MRP =  "
.



IMPORTING Parameters details for SGT_MD_WRITE_DOCUMENT

OBJECTID -

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

UPD_SGT_MADKA -

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

UPD_SGT_MARM -

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

UPD_SGT_MLGN -

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

UPD_SGT_MLGT -

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

UPD_SGT_MRP -

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

UPD_SGT_MRP_GN -

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

UPD_SGT_MVKE -

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

OBJECT_CHANGE_INDICATOR -

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

PLANNED_OR_REAL_CHANGES -

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

NO_CHANGE_POINTERS -

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

TABLES Parameters details for SGT_MD_WRITE_DOCUMENT

XSGT_MADKA -

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

YSGT_MRP -

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

XSGT_MRP_GN -

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

YSGT_MRP_GN -

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

XSGT_MVKE -

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

YSGT_MVKE -

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

YSGT_MADKA -

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

XSGT_MARM -

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

YSGT_MARM -

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

XSGT_MLGN -

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

YSGT_MLGN -

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

XSGT_MLGT -

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

YSGT_MLGT -

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

XSGT_MRP -

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

Copy and paste ABAP code example for SGT_MD_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_xsgt_madka  TYPE STANDARD TABLE OF VSGT_MADKA, "   
lt_ysgt_mrp  TYPE STANDARD TABLE OF VSGT_MRP, "   
lv_upd_sgt_madka  TYPE CDPOS-CHNGIND, "   SPACE
lt_xsgt_mrp_gn  TYPE STANDARD TABLE OF VSGT_MRP_GN, "   
lv_upd_sgt_marm  TYPE CDPOS-CHNGIND, "   SPACE
lt_ysgt_mrp_gn  TYPE STANDARD TABLE OF VSGT_MRP_GN, "   
lv_upd_sgt_mlgn  TYPE CDPOS-CHNGIND, "   SPACE
lt_xsgt_mvke  TYPE STANDARD TABLE OF VSGT_MVKE, "   
lv_upd_sgt_mlgt  TYPE CDPOS-CHNGIND, "   SPACE
lt_ysgt_mvke  TYPE STANDARD TABLE OF VSGT_MVKE, "   
lv_upd_sgt_mrp  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_sgt_mrp_gn  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_sgt_mvke  TYPE CDPOS-CHNGIND, "   SPACE
lv_tcode  TYPE CDHDR-TCODE, "   
lt_ysgt_madka  TYPE STANDARD TABLE OF VSGT_MADKA, "   
lv_utime  TYPE CDHDR-UTIME, "   
lt_xsgt_marm  TYPE STANDARD TABLE OF VSGT_MARM, "   
lv_udate  TYPE CDHDR-UDATE, "   
lt_ysgt_marm  TYPE STANDARD TABLE OF VSGT_MARM, "   
lv_username  TYPE CDHDR-USERNAME, "   
lt_xsgt_mlgn  TYPE STANDARD TABLE OF VSGT_MLGN, "   
lt_ysgt_mlgn  TYPE STANDARD TABLE OF VSGT_MLGN, "   
lv_planned_change_number  TYPE CDHDR-PLANCHNGNR, "   SPACE
lt_xsgt_mlgt  TYPE STANDARD TABLE OF VSGT_MLGT, "   
lv_object_change_indicator  TYPE CDHDR-CHANGE_IND, "   'U'
lt_ysgt_mlgt  TYPE STANDARD TABLE OF VSGT_MLGT, "   
lv_planned_or_real_changes  TYPE CDHDR-CHANGE_IND, "   SPACE
lt_xsgt_mrp  TYPE STANDARD TABLE OF VSGT_MRP, "   
lv_no_change_pointers  TYPE CDHDR-CHANGE_IND. "   SPACE

  CALL FUNCTION 'SGT_MD_WRITE_DOCUMENT'  "CHDO SGT_MD => Gen. by RSSCD000
    EXPORTING
         OBJECTID = lv_objectid
         UPD_SGT_MADKA = lv_upd_sgt_madka
         UPD_SGT_MARM = lv_upd_sgt_marm
         UPD_SGT_MLGN = lv_upd_sgt_mlgn
         UPD_SGT_MLGT = lv_upd_sgt_mlgt
         UPD_SGT_MRP = lv_upd_sgt_mrp
         UPD_SGT_MRP_GN = lv_upd_sgt_mrp_gn
         UPD_SGT_MVKE = lv_upd_sgt_mvke
         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
         XSGT_MADKA = lt_xsgt_madka
         YSGT_MRP = lt_ysgt_mrp
         XSGT_MRP_GN = lt_xsgt_mrp_gn
         YSGT_MRP_GN = lt_ysgt_mrp_gn
         XSGT_MVKE = lt_xsgt_mvke
         YSGT_MVKE = lt_ysgt_mvke
         YSGT_MADKA = lt_ysgt_madka
         XSGT_MARM = lt_xsgt_marm
         YSGT_MARM = lt_ysgt_marm
         XSGT_MLGN = lt_xsgt_mlgn
         YSGT_MLGN = lt_ysgt_mlgn
         XSGT_MLGT = lt_xsgt_mlgt
         YSGT_MLGT = lt_ysgt_mlgt
         XSGT_MRP = lt_xsgt_mrp
. " SGT_MD_WRITE_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM SGT_MD_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_sgt_madka).
DATA(ld_upd_sgt_madka) = ' '.
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_sgt_marm).
DATA(ld_upd_sgt_marm) = ' '.
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_sgt_mlgn).
DATA(ld_upd_sgt_mlgn) = ' '.
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_sgt_mlgt).
DATA(ld_upd_sgt_mlgt) = ' '.
 
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_sgt_mrp).
DATA(ld_upd_sgt_mrp) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_sgt_mrp_gn).
DATA(ld_upd_sgt_mrp_gn) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_sgt_mvke).
DATA(ld_upd_sgt_mvke) = ' '.
 
"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!