SAP MASTERIDOC_CREATE_REQ_SCEMAS Function Module for NOTRANSL: Verteilen von IDOCs für SCE-Wissensbasen









MASTERIDOC_CREATE_REQ_SCEMAS is a standard masteridoc create req scemas SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verteilen von IDOCs für SCE-Wissensbasen 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 masteridoc create req scemas FM, simply by entering the name MASTERIDOC_CREATE_REQ_SCEMAS into the relevant SAP transaction such as SE37 or SE38.

Function Group: CUAL
Program Name: SAPLCUAL
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MASTERIDOC_CREATE_REQ_SCEMAS 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_SCEMAS'"NOTRANSL: Verteilen von IDOCs für SCE-Wissensbasen
EXPORTING
RCVPFC = "Partner Function of Receiver
RCVPRN = "Partner Number of Receiver
RCVPRT = "Partner Type of Receiver
SNDPFC = "Partner Function of Sender
SNDPRN = "Partner Number of Sender
SNDPRT = "Partner type of sender
MESSAGE_TYPE = "Message Type
* PARALLEL = ' ' "Indicator: Parallel processing yes/no

IMPORTING
CREATED_COMM_IDOCS = "ABAP System Field: Row Index of Internal Tables

TABLES
KNOWLEDGE_BASES = "SCEKB key fields - transfer IDoc
.



IMPORTING Parameters details for MASTERIDOC_CREATE_REQ_SCEMAS

RCVPFC - Partner Function of Receiver

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

RCVPRN - Partner Number of Receiver

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

RCVPRT - Partner Type of Receiver

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 - Message Type

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

PARALLEL - Indicator: Parallel processing yes/no

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

EXPORTING Parameters details for MASTERIDOC_CREATE_REQ_SCEMAS

CREATED_COMM_IDOCS - ABAP System Field: Row Index of Internal Tables

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

TABLES Parameters details for MASTERIDOC_CREATE_REQ_SCEMAS

KNOWLEDGE_BASES - SCEKB key fields - transfer IDoc

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

Copy and paste ABAP code example for MASTERIDOC_CREATE_REQ_SCEMAS 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_rcvpfc  TYPE BDALEDC-RCVPFC, "   
lt_knowledge_bases  TYPE STANDARD TABLE OF ASCEKB, "   
lv_created_comm_idocs  TYPE SY-TABIX, "   
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, "   
lv_parallel  TYPE BDFIELDS-PARALLEL. "   SPACE

  CALL FUNCTION 'MASTERIDOC_CREATE_REQ_SCEMAS'  "NOTRANSL: Verteilen von IDOCs für SCE-Wissensbasen
    EXPORTING
         RCVPFC = lv_rcvpfc
         RCVPRN = lv_rcvprn
         RCVPRT = lv_rcvprt
         SNDPFC = lv_sndpfc
         SNDPRN = lv_sndprn
         SNDPRT = lv_sndprt
         MESSAGE_TYPE = lv_message_type
         PARALLEL = lv_parallel
    IMPORTING
         CREATED_COMM_IDOCS = lv_created_comm_idocs
    TABLES
         KNOWLEDGE_BASES = lt_knowledge_bases
. " MASTERIDOC_CREATE_REQ_SCEMAS




ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_REQ_SCEMAS

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


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!