SAP ALM_MEREP_ML_090_GETDETAIL Function Module for NOTRANSL: Multilingual Support









ALM_MEREP_ML_090_GETDETAIL is a standard alm merep ml 090 getdetail 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: Multilingual Support 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 alm merep ml 090 getdetail FM, simply by entering the name ALM_MEREP_ML_090_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function ALM_MEREP_ML_090_GETDETAIL 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 'ALM_MEREP_ML_090_GETDETAIL'"NOTRANSL: Multilingual Support
EXPORTING
CUSTOMIZING_USER = "User Name

IMPORTING
USER_CUSTOMIZING_HEAD = "

TABLES
* PARTNER_LINKS = "Partner Key
* WSAP_EXTENSION = "
* Y1_ML_VARIANCES = "
* Y1_ML_WORKCENTERS = "
* Y1_ML_ACTIVITY_TYPES = "
* Y1_ML_CE_USER_DATA = "
* Y1_ML_WSAP_EXTENSION = "
* FUNCLOC_LINKS = "
* EQUIPMENT_LINKS = "
* MEASUREMENT_LINKS = "
* CE_USER_DATA = "
* RETURN = "Return Parameter
* VARIANCES = "
* WORKCENTERS = "
* ACTIVITY_TYPES = "
.



IMPORTING Parameters details for ALM_MEREP_ML_090_GETDETAIL

CUSTOMIZING_USER - User Name

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

EXPORTING Parameters details for ALM_MEREP_ML_090_GETDETAIL

USER_CUSTOMIZING_HEAD -

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

TABLES Parameters details for ALM_MEREP_ML_090_GETDETAIL

PARTNER_LINKS - Partner Key

Data type: ALM_ME_PARTNER_KEY_STRUCT
Optional: Yes
Call by Reference: Yes

WSAP_EXTENSION -

Data type: ALM_ME_SAP_EXTENSION
Optional: Yes
Call by Reference: Yes

Y1_ML_VARIANCES -

Data type: ALM_ME_ML_90_VARIANCES
Optional: Yes
Call by Reference: Yes

Y1_ML_WORKCENTERS -

Data type: ALM_ME_ML_90_WORKCENTERS
Optional: Yes
Call by Reference: Yes

Y1_ML_ACTIVITY_TYPES -

Data type: ALM_ME_ML_90_ACTIVITY_TYPES
Optional: Yes
Call by Reference: Yes

Y1_ML_CE_USER_DATA -

Data type: ALM_ME_ML_CUSTOMER_ENHANCEMENT
Optional: Yes
Call by Reference: Yes

Y1_ML_WSAP_EXTENSION -

Data type: ALM_ME_ML_SAP_EXTENSION
Optional: Yes
Call by Reference: Yes

FUNCLOC_LINKS -

Data type: ALM_ME_FUNCLOC_HEADER_STRUCT
Optional: Yes
Call by Reference: Yes

EQUIPMENT_LINKS -

Data type: ALM_ME_EQUIPMENT_HEADER_STRUCT
Optional: Yes
Call by Reference: Yes

MEASUREMENT_LINKS -

Data type: ALM_ME_MEASMNT_PT_KEY
Optional: Yes
Call by Reference: Yes

CE_USER_DATA -

Data type: ALM_ME_CUSTOMER_ENHANCEMENT
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

VARIANCES -

Data type: ALM_ME_CATALOG_VARIANCES
Optional: Yes
Call by Reference: Yes

WORKCENTERS -

Data type: ALM_ME_WORKCENTERS
Optional: Yes
Call by Reference: Yes

ACTIVITY_TYPES -

Data type: ALM_ME_CUST_ACTIVITY_TYPE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for ALM_MEREP_ML_090_GETDETAIL 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_partner_links  TYPE STANDARD TABLE OF ALM_ME_PARTNER_KEY_STRUCT, "   
lv_customizing_user  TYPE MAM_20_USER_DATA-USERID, "   
lv_user_customizing_head  TYPE MAM_20_USER_DATA, "   
lt_wsap_extension  TYPE STANDARD TABLE OF ALM_ME_SAP_EXTENSION, "   
lt_y1_ml_variances  TYPE STANDARD TABLE OF ALM_ME_ML_90_VARIANCES, "   
lt_y1_ml_workcenters  TYPE STANDARD TABLE OF ALM_ME_ML_90_WORKCENTERS, "   
lt_y1_ml_activity_types  TYPE STANDARD TABLE OF ALM_ME_ML_90_ACTIVITY_TYPES, "   
lt_y1_ml_ce_user_data  TYPE STANDARD TABLE OF ALM_ME_ML_CUSTOMER_ENHANCEMENT, "   
lt_y1_ml_wsap_extension  TYPE STANDARD TABLE OF ALM_ME_ML_SAP_EXTENSION, "   
lt_funcloc_links  TYPE STANDARD TABLE OF ALM_ME_FUNCLOC_HEADER_STRUCT, "   
lt_equipment_links  TYPE STANDARD TABLE OF ALM_ME_EQUIPMENT_HEADER_STRUCT, "   
lt_measurement_links  TYPE STANDARD TABLE OF ALM_ME_MEASMNT_PT_KEY, "   
lt_ce_user_data  TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_variances  TYPE STANDARD TABLE OF ALM_ME_CATALOG_VARIANCES, "   
lt_workcenters  TYPE STANDARD TABLE OF ALM_ME_WORKCENTERS, "   
lt_activity_types  TYPE STANDARD TABLE OF ALM_ME_CUST_ACTIVITY_TYPE. "   

  CALL FUNCTION 'ALM_MEREP_ML_090_GETDETAIL'  "NOTRANSL: Multilingual Support
    EXPORTING
         CUSTOMIZING_USER = lv_customizing_user
    IMPORTING
         USER_CUSTOMIZING_HEAD = lv_user_customizing_head
    TABLES
         PARTNER_LINKS = lt_partner_links
         WSAP_EXTENSION = lt_wsap_extension
         Y1_ML_VARIANCES = lt_y1_ml_variances
         Y1_ML_WORKCENTERS = lt_y1_ml_workcenters
         Y1_ML_ACTIVITY_TYPES = lt_y1_ml_activity_types
         Y1_ML_CE_USER_DATA = lt_y1_ml_ce_user_data
         Y1_ML_WSAP_EXTENSION = lt_y1_ml_wsap_extension
         FUNCLOC_LINKS = lt_funcloc_links
         EQUIPMENT_LINKS = lt_equipment_links
         MEASUREMENT_LINKS = lt_measurement_links
         CE_USER_DATA = lt_ce_user_data
         RETURN = lt_return
         VARIANCES = lt_variances
         WORKCENTERS = lt_workcenters
         ACTIVITY_TYPES = lt_activity_types
. " ALM_MEREP_ML_090_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM ALM_MEREP_ML_090_GETDETAIL

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 USERID FROM MAM_20_USER_DATA INTO @DATA(ld_customizing_user).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!