SAP MASTERIDOC_CREATE_REQ_ADRMAS Function Module for









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

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



Function MASTERIDOC_CREATE_REQ_ADRMAS 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_ADRMAS'"
EXPORTING
OBJ_TYPE = "Address owner BOR object type
OBJ_ID = "Address owner BOR object key
* OBJ_ID_EXT = ' ' "BOR object key extension (GUID)
* CONTEXT = 1 "Semantic meaning of the addresses (-> constants)

TABLES
RECEIVERS = "

EXCEPTIONS
ADDRESS_NOT_FOUND = 1 PARAMETER_ERROR = 2 NO_DISTRIBUTION = 3 DISTRIBUTION_ERROR = 4 INTERNAL_ERROR = 5
.



IMPORTING Parameters details for MASTERIDOC_CREATE_REQ_ADRMAS

OBJ_TYPE - Address owner BOR object type

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

OBJ_ID - Address owner BOR object key

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

OBJ_ID_EXT - BOR object key extension (GUID)

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

CONTEXT - Semantic meaning of the addresses (-> constants)

Data type: BAPI4001_1-CONTEXT
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MASTERIDOC_CREATE_REQ_ADRMAS

RECEIVERS -

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

EXCEPTIONS details

ADDRESS_NOT_FOUND -

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

PARAMETER_ERROR -

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

NO_DISTRIBUTION -

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

DISTRIBUTION_ERROR -

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for MASTERIDOC_CREATE_REQ_ADRMAS 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_obj_type  TYPE BAPI4001_1-OBJTYPE, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_address_not_found  TYPE BDI_LOGSYS, "   
lv_obj_id  TYPE BAPI4001_1-OBJKEY, "   
lv_parameter_error  TYPE BAPI4001_1, "   
lv_obj_id_ext  TYPE BAPI4001_1-EXTENSION, "   SPACE
lv_no_distribution  TYPE BAPI4001_1, "   
lv_context  TYPE BAPI4001_1-CONTEXT, "   1
lv_distribution_error  TYPE BAPI4001_1, "   
lv_internal_error  TYPE BAPI4001_1. "   

  CALL FUNCTION 'MASTERIDOC_CREATE_REQ_ADRMAS'  "
    EXPORTING
         OBJ_TYPE = lv_obj_type
         OBJ_ID = lv_obj_id
         OBJ_ID_EXT = lv_obj_id_ext
         CONTEXT = lv_context
    TABLES
         RECEIVERS = lt_receivers
    EXCEPTIONS
        ADDRESS_NOT_FOUND = 1
        PARAMETER_ERROR = 2
        NO_DISTRIBUTION = 3
        DISTRIBUTION_ERROR = 4
        INTERNAL_ERROR = 5
. " MASTERIDOC_CREATE_REQ_ADRMAS




ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_REQ_ADRMAS

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 OBJTYPE FROM BAPI4001_1 INTO @DATA(ld_obj_type).
 
 
 
"SELECT single OBJKEY FROM BAPI4001_1 INTO @DATA(ld_obj_id).
 
 
"SELECT single EXTENSION FROM BAPI4001_1 INTO @DATA(ld_obj_id_ext).
DATA(ld_obj_id_ext) = ' '.
 
 
"SELECT single CONTEXT FROM BAPI4001_1 INTO @DATA(ld_context).
DATA(ld_context) = 1.
 
 
 


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!