SAP MASTERIDOC_CREATE_REQ_GLMAST Function Module for









MASTERIDOC_CREATE_REQ_GLMAST is a standard masteridoc create req glmast SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 masteridoc create req glmast FM, simply by entering the name MASTERIDOC_CREATE_REQ_GLMAST into the relevant SAP transaction such as SE37 or SE38.

Function Group: KS03
Program Name: SAPLKS03
Main Program: SAPLKS03
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MASTERIDOC_CREATE_REQ_GLMAST 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 'MASTERIDOC_CREATE_REQ_GLMAST'"
EXPORTING
RCVPFC = "Receiver - Partner Role
RCVPRN = "Receiver - Partner Number
RCVPRT = "Receiver - Partner Type
SNDPFC = "Sender - Partner Role
SNDPRN = "Sender - Partner Number
SNDPRT = "Sender - Partner Type
MESSAGE_TYPE = "Message Types of Reduced IDOCs

IMPORTING
COUNT = "Number of created basic IDOCs
CREATED_COMM_IDOCS = "Number of generated communcation IDOCs

TABLES
SKKEY = "Key fields of accounts to be sent
.



IMPORTING Parameters details for MASTERIDOC_CREATE_REQ_GLMAST

RCVPFC - Receiver - Partner Role

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

RCVPRN - Receiver - Partner Number

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

RCVPRT - Receiver - Partner Type

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

SNDPFC - Sender - Partner Role

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

SNDPRN - Sender - Partner Number

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

SNDPRT - Sender - Partner Type

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

MESSAGE_TYPE - Message Types of Reduced IDOCs

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

EXPORTING Parameters details for MASTERIDOC_CREATE_REQ_GLMAST

COUNT - Number of created basic IDOCs

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

CREATED_COMM_IDOCS - Number of generated communcation IDOCs

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

TABLES Parameters details for MASTERIDOC_CREATE_REQ_GLMAST

SKKEY - Key fields of accounts to be sent

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

Copy and paste ABAP code example for MASTERIDOC_CREATE_REQ_GLMAST 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_count  TYPE SY-TABIX, "   
lt_skkey  TYPE STANDARD TABLE OF BDISKB1KPL, "   
lv_rcvpfc  TYPE BDALEDC-RCVPFC, "   
lv_rcvprn  TYPE BDALEDC-RCVPRN, "   
lv_created_comm_idocs  TYPE SY-TABIX, "   
lv_rcvprt  TYPE BDALEDC-RCVPRT, "   
lv_sndpfc  TYPE BDALEDC-SNDPFC, "   
lv_sndprn  TYPE BDALEDC-SNDPRN, "   
lv_sndprt  TYPE BDALEDC-SNDPRT, "   
lv_message_type  TYPE TBDME-MESTYP. "   

  CALL FUNCTION 'MASTERIDOC_CREATE_REQ_GLMAST'  "
    EXPORTING
         RCVPFC = lv_rcvpfc
         RCVPRN = lv_rcvprn
         RCVPRT = lv_rcvprt
         SNDPFC = lv_sndpfc
         SNDPRN = lv_sndprn
         SNDPRT = lv_sndprt
         MESSAGE_TYPE = lv_message_type
    IMPORTING
         COUNT = lv_count
         CREATED_COMM_IDOCS = lv_created_comm_idocs
    TABLES
         SKKEY = lt_skkey
. " MASTERIDOC_CREATE_REQ_GLMAST




ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_REQ_GLMAST

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 TABIX FROM SY INTO @DATA(ld_count).
 
 
"SELECT single RCVPFC FROM BDALEDC INTO @DATA(ld_rcvpfc).
 
"SELECT single RCVPRN FROM BDALEDC INTO @DATA(ld_rcvprn).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_created_comm_idocs).
 
"SELECT single RCVPRT FROM BDALEDC INTO @DATA(ld_rcvprt).
 
"SELECT single SNDPFC FROM BDALEDC INTO @DATA(ld_sndpfc).
 
"SELECT single SNDPRN FROM BDALEDC INTO @DATA(ld_sndprn).
 
"SELECT single SNDPRT FROM BDALEDC INTO @DATA(ld_sndprt).
 
"SELECT single MESTYP FROM TBDME INTO @DATA(ld_message_type).
 


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!