SAP MASTERIDOC_CREATE_REQ_VTAMAS Function Module for









MASTERIDOC_CREATE_REQ_VTAMAS is a standard masteridoc create req vtamas 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 vtamas FM, simply by entering the name MASTERIDOC_CREATE_REQ_VTAMAS into the relevant SAP transaction such as SE37 or SE38.

Function Group: CLD3
Program Name: SAPLCLD3
Main Program: SAPLCLD3
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MASTERIDOC_CREATE_REQ_VTAMAS 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_VTAMAS'"
  EXPORTING
*  KEY_DATE = SY-DATUM "Date of change
*  PARALLEL = ' ' "Parallel processing
*  DLOCK_IGNORE =  "New input values
   RCVPFC =  "Partner function of recipient
   RCVPRN =  "Partner number of recipient
   RCVPRT =  "Partner type of recipient
   SNDPFC =  "Partner function of sender
   SNDPRN =  "Partner number of sender
   SNDPRT =  "Partner type of sender
   MESSAGE_TYPE =  "Logical output type

 IMPORTING
   CREATED_COMM_IDOCS =  "Number of IDocs created

TABLES
   VAR_TABLES =  "Variant tables to distribute
.



IMPORTING Parameters details for MASTERIDOC_CREATE_REQ_VTAMAS

KEY_DATE - Date of change

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

PARALLEL - Parallel processing

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

DLOCK_IGNORE - New input values

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

RCVPFC - Partner function of recipient

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

RCVPRN - Partner number of recipient

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

RCVPRT - Partner type of recipient

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

SNDPFC - Partner function of sender

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

SNDPRN - Partner number of sender

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

SNDPRT - Partner type of sender

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

MESSAGE_TYPE - Logical output type

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

EXPORTING Parameters details for MASTERIDOC_CREATE_REQ_VTAMAS

CREATED_COMM_IDOCS - Number of IDocs created

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

TABLES Parameters details for MASTERIDOC_CREATE_REQ_VTAMAS

VAR_TABLES - Variant tables to distribute

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

Copy and paste ABAP code example for MASTERIDOC_CREATE_REQ_VTAMAS 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_key_date  TYPE SY-DATUM, "   SY-DATUM
lt_var_tables  TYPE STANDARD TABLE OF API_CLASS, "   
lv_created_comm_idocs  TYPE SY-TABIX, "   
lv_parallel  TYPE BDFIELDS-PARALLEL, "   SPACE
lv_dlock_ignore  TYPE XFLAG, "   
lv_rcvpfc  TYPE BDALEDC-RCVPFC, "   
lv_rcvprn  TYPE BDALEDC-RCVPRN, "   
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_VTAMAS'  "
    EXPORTING
         KEY_DATE = lv_key_date
         PARALLEL = lv_parallel
         DLOCK_IGNORE = lv_dlock_ignore
         RCVPFC = lv_rcvpfc
         RCVPRN = lv_rcvprn
         RCVPRT = lv_rcvprt
         SNDPFC = lv_sndpfc
         SNDPRN = lv_sndprn
         SNDPRT = lv_sndprt
         MESSAGE_TYPE = lv_message_type
    IMPORTING
         CREATED_COMM_IDOCS = lv_created_comm_idocs
    TABLES
         VAR_TABLES = lt_var_tables
. " MASTERIDOC_CREATE_REQ_VTAMAS




ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_REQ_VTAMAS

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 DATUM FROM SY INTO @DATA(ld_key_date).
DATA(ld_key_date) = SY-DATUM.
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_created_comm_idocs).
 
"SELECT single PARALLEL FROM BDFIELDS INTO @DATA(ld_parallel).
DATA(ld_parallel) = ' '.
 
 
"SELECT single RCVPFC FROM BDALEDC INTO @DATA(ld_rcvpfc).
 
"SELECT single RCVPRN FROM BDALEDC INTO @DATA(ld_rcvprn).
 
"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!