SAP MASTERIDOC_CREATE_REQ_ADR3MAS Function Module for

Search SAP Function Modules

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

Function Group: SZAM
Program Name: SAPLSZAM
Main Program: SAPLSZAM
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MASTERIDOC_CREATE_REQ_ADR3MAS 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_ADR3MAS'"
  EXPORTING
   OBJ_TYPE_P =  "Person object BOR object type
   OBJ_ID_P =  "Person object BOR object key
   OBJ_TYPE_C =  "Company address owner BOR object type
   OBJ_ID_C =  "BOR company address owner object key
*  OBJ_ID_EXT = ' ' "BOR object key extension (GUID)
*  CONTEXT = 0 "Semantic meaning of the addresses (-> constants)

TABLES
   RECEIVERS =  "

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

.

IMPORTING Parameters details for MASTERIDOC_CREATE_REQ_ADR3MAS

OBJ_TYPE_P - Person object BOR object type

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

OBJ_ID_P - Person object BOR object key

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

OBJ_TYPE_C - Company address owner BOR object type

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

OBJ_ID_C - BOR company address owner object key

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

OBJ_ID_EXT - BOR object key extension (GUID)

Data type: BAPI4003_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: BAPI4003_1-CONTEXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MASTERIDOC_CREATE_REQ_ADR3MAS

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)

PERSON_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_ADR3MAS 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.

ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_REQ_ADR3MAS

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.

Search for further information about these or an SAP related objects