SAP MASTER_DATA Function Module for DE-EN-LANG-SWITCH-NO-TRANSLATION
MASTER_DATA is a standard master data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DE-EN-LANG-SWITCH-NO-TRANSLATION 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 master data FM, simply by entering the name MASTER_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: IPW0
Program Name: SAPLIPW0
Main Program: SAPLIPW0
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MASTER_DATA 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 'MASTER_DATA'"DE-EN-LANG-SWITCH-NO-TRANSLATION.
EXPORTING
DATENFELD = "Field for master data usage
* PROGRAM = ' ' "Program name
* FIELDVALUE = ' ' "Field content of data field if assignment not ok
IMPORTING
ENTRY_NOT_FOUND = "
TABLES
* IOBJECT = "
EXCEPTIONS
OBJECT_NOT_FOUND = 1 FIELD_IS_INITIAL = 2 NO_AUTHORITY = 3
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_SAPLIPW0_001 Object Permissible for Contract (Copying of Order/Maintenance Order)
EXIT_SAPLIPW0_002 Object Permissible for Order (Copying of Maint. Order/Maint. Order)
EXIT_SAPLIPW0_003 Object Permissible for Contract (Maintenance of Maintenance Contract)
IMPORTING Parameters details for MASTER_DATA
DATENFELD - Field for master data usage
Data type: T354S-INITFIELDOptional: No
Call by Reference: No ( called with pass by value option)
PROGRAM - Program name
Data type: T354T-AGIDVDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FIELDVALUE - Field content of data field if assignment not ok
Data type: T354S-INITFIELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MASTER_DATA
ENTRY_NOT_FOUND -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MASTER_DATA
IOBJECT -
Data type: IOPICKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIELD_IS_INITIAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MASTER_DATA 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: | ||||
| lt_iobject | TYPE STANDARD TABLE OF IOPICK, " | |||
| lv_datenfeld | TYPE T354S-INITFIELD, " | |||
| lv_entry_not_found | TYPE C, " | |||
| lv_object_not_found | TYPE C, " | |||
| lv_program | TYPE T354T-AGIDV, " SPACE | |||
| lv_field_is_initial | TYPE T354T, " | |||
| lv_fieldvalue | TYPE T354S-INITFIELD, " SPACE | |||
| lv_no_authority | TYPE T354S. " |
|   CALL FUNCTION 'MASTER_DATA' "DE-EN-LANG-SWITCH-NO-TRANSLATION |
| EXPORTING | ||
| DATENFELD | = lv_datenfeld | |
| PROGRAM | = lv_program | |
| FIELDVALUE | = lv_fieldvalue | |
| IMPORTING | ||
| ENTRY_NOT_FOUND | = lv_entry_not_found | |
| TABLES | ||
| IOBJECT | = lt_iobject | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| FIELD_IS_INITIAL = 2 | ||
| NO_AUTHORITY = 3 | ||
| . " MASTER_DATA | ||
ABAP code using 7.40 inline data declarations to call FM MASTER_DATA
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 INITFIELD FROM T354S INTO @DATA(ld_datenfeld). | ||||
| "SELECT single AGIDV FROM T354T INTO @DATA(ld_program). | ||||
| DATA(ld_program) | = ' '. | |||
| "SELECT single INITFIELD FROM T354S INTO @DATA(ld_fieldvalue). | ||||
| DATA(ld_fieldvalue) | = ' '. | |||
Search for further information about these or an SAP related objects