SAP MASTERIDOC_CREATE_REQ_BLAREL Function Module for NOTRANSL: Erzeugen Masteridoc BLAREL aus Anforderung









MASTERIDOC_CREATE_REQ_BLAREL is a standard masteridoc create req blarel 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: Erzeugen Masteridoc BLAREL aus Anforderung 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 blarel FM, simply by entering the name MASTERIDOC_CREATE_REQ_BLAREL into the relevant SAP transaction such as SE37 or SE38.

Function Group: EINM
Program Name: SAPLEINM
Main Program: SAPLEINM
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MASTERIDOC_CREATE_REQ_BLAREL 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_BLAREL'"NOTRANSL: Erzeugen Masteridoc BLAREL aus Anforderung
  EXPORTING
*  RCVPFC = ' ' "Partner Function of Receiver
*  RCVPRN = ' ' "Partner Number of Receiver
*  RCVPRT = ' ' "Partner Type of Receiver
*  PARALLEL = ' ' "Indicator: Parallel processing yes/no
*  READ_HISTORY = ' ' "Test Flag

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

TABLES
   T_EKAB_ALL =  "Transfer Structure for Table EKAB (BSEW in R/2)
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEINM_001 Customer Enhancements for Control Record: Purchasing Document (Outbound)
EXIT_SAPLEINM_002 Customer Enhancements to Data Segments: Purchasing Document (Outbound)
EXIT_SAPLEINM_003 Customer Enhancements of Data Segment for Release Documentation (Outbound)
EXIT_SAPLEINM_004 Customer Enhancements for Release Documentation (Inbound)
EXIT_SAPLEINM_005 Customer Enhancements for Order Acknowledgment (Inbound)
EXIT_SAPLEINM_006 Customer Enhancements for Shipping Notification (Inbound)
EXIT_SAPLEINM_007 Customer Enhancements for Inbound Order Acknowledgment: Read IDOC Segments
EXIT_SAPLEINM_008 Customer Enhancements for Inbound Order Acknowledgment: Concluding Actions
EXIT_SAPLEINM_009 MM EDI ORDRSP: Custotmer Enhancement: Tolerances (Quantities/Dates/Prices)
EXIT_SAPLEINM_010 Cust. Enhancement for Inbound Shipping Notif.: Adopt Item Data from IDoc
EXIT_SAPLEINM_011 Concluding Customer Enhancement: EDI Outbound Purchase Order
EXIT_SAPLEINM_012 MM EDI ORDERS/ORDCHG: Customer Enhancement Transfer Configuration
EXIT_SAPLEINM_013 MM EDI ORDERS/ORDCHG: Customer Enhancement Configuration Structures
EXIT_SAPLEINM_014 MM EDI ORDRSP: Customer Enhancement: Price Tolerances
EXIT_SAPLEINM_015 MM EDI ORDRSP: Customer Enhancement: Vendor Material Change
EXIT_SAPLEINM_016 ALE Contract Distribution: Outbound: Enhancement of IDoc Segments
EXIT_SAPLEINM_017 Concluding Customer Enhancement for ALE Contract Distribution: Outbound
EXIT_SAPLEINM_018 Inbound Order Acknowledgment: Modify Segment E1EDK01
EXIT_SAPLEINM_019 Final User Exit: FRC
EXIT_SAPLEINM_020 Final User Exit: JIT

IMPORTING Parameters details for MASTERIDOC_CREATE_REQ_BLAREL

RCVPFC - Partner Function of Receiver

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

RCVPRN - Partner Number of Receiver

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

RCVPRT - Partner Type of Receiver

Data type: BDALEDC-RCVPRT
Default: SPACE
Optional: Yes
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)

READ_HISTORY - Test Flag

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

EXPORTING Parameters details for MASTERIDOC_CREATE_REQ_BLAREL

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)

CREATED_MASTER_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_BLAREL

T_EKAB_ALL - Transfer Structure for Table EKAB (BSEW in R/2)

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

Copy and paste ABAP code example for MASTERIDOC_CREATE_REQ_BLAREL 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, "   SPACE
lt_t_ekab_all  TYPE STANDARD TABLE OF BDIEKAB, "   
lv_created_comm_idocs  TYPE SY-TABIX, "   
lv_rcvprn  TYPE BDALEDC-RCVPRN, "   SPACE
lv_created_master_idocs  TYPE SY-TABIX, "   
lv_rcvprt  TYPE BDALEDC-RCVPRT, "   SPACE
lv_parallel  TYPE BDFIELDS-PARALLEL, "   SPACE
lv_read_history  TYPE BDALEDC-TEST. "   SPACE

  CALL FUNCTION 'MASTERIDOC_CREATE_REQ_BLAREL'  "NOTRANSL: Erzeugen Masteridoc BLAREL aus Anforderung
    EXPORTING
         RCVPFC = lv_rcvpfc
         RCVPRN = lv_rcvprn
         RCVPRT = lv_rcvprt
         PARALLEL = lv_parallel
         READ_HISTORY = lv_read_history
    IMPORTING
         CREATED_COMM_IDOCS = lv_created_comm_idocs
         CREATED_MASTER_IDOCS = lv_created_master_idocs
    TABLES
         T_EKAB_ALL = lt_t_ekab_all
. " MASTERIDOC_CREATE_REQ_BLAREL




ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_REQ_BLAREL

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).
DATA(ld_rcvpfc) = ' '.
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_created_comm_idocs).
 
"SELECT single RCVPRN FROM BDALEDC INTO @DATA(ld_rcvprn).
DATA(ld_rcvprn) = ' '.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_created_master_idocs).
 
"SELECT single RCVPRT FROM BDALEDC INTO @DATA(ld_rcvprt).
DATA(ld_rcvprt) = ' '.
 
"SELECT single PARALLEL FROM BDFIELDS INTO @DATA(ld_parallel).
DATA(ld_parallel) = ' '.
 
"SELECT single TEST FROM BDALEDC INTO @DATA(ld_read_history).
DATA(ld_read_history) = ' '.
 


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!