SAP CMS_API_AST_GET_MLT Function Module for Fetch details on an Asset









CMS_API_AST_GET_MLT is a standard cms api ast get mlt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fetch details on an Asset 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 cms api ast get mlt FM, simply by entering the name CMS_API_AST_GET_MLT into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_API_AST_GET_MLT 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 'CMS_API_AST_GET_MLT'"Fetch details on an Asset
EXPORTING
I_TAB_AST_GUID = "Asset Identification Number
* I_FLG_LOCK = "Indicator: Lock the Asset
* I_FLG_DB = 'X' "Flag: Indicates that the data is to be fetched from database
* I_STR_AST_REQD_DATA = "Data that is required for an Asset fetch

IMPORTING
E_TAB_AST_DETAILS = "Asset details (API Layer and above)
E_TAB_RC = "Return Code and corresponding Message
E_TAB_SAS_DETAILS = "Sub-asset details (API Layer and above)
E_TAB_AST_BP = "Business Partners for an Asset
E_TAB_SAS_BP = "Sub-asset - Business partner data
E_TAB_AST_DOC = "Documents for an Asset
E_TAB_SAS_DOC = "Documents for the Sub-assets
E_TAB_AST_NOTES = "Text lines
E_TAB_AST_SYS_STAT = "System status of the Asset
E_TAB_AST_USR_STAT = "User status of the Asset
.



IMPORTING Parameters details for CMS_API_AST_GET_MLT

I_TAB_AST_GUID - Asset Identification Number

Data type: CMS_TAB_AST_PKY
Optional: No
Call by Reference: Yes

I_FLG_LOCK - Indicator: Lock the Asset

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

I_FLG_DB - Flag: Indicates that the data is to be fetched from database

Data type: CMS_DTE_FLG_FETCH_FROM_DB
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_STR_AST_REQD_DATA - Data that is required for an Asset fetch

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

EXPORTING Parameters details for CMS_API_AST_GET_MLT

E_TAB_AST_DETAILS - Asset details (API Layer and above)

Data type: CMS_TAB_AST_DETAILS_API
Optional: No
Call by Reference: Yes

E_TAB_RC - Return Code and corresponding Message

Data type: CMS_TAB_MSG_COL_MESSAGE
Optional: No
Call by Reference: Yes

E_TAB_SAS_DETAILS - Sub-asset details (API Layer and above)

Data type: CMS_TAB_SAS_DETAILS_API
Optional: No
Call by Reference: Yes

E_TAB_AST_BP - Business Partners for an Asset

Data type: CMS_TAB_AST_BP
Optional: No
Call by Reference: Yes

E_TAB_SAS_BP - Sub-asset - Business partner data

Data type: CMS_TAB_SAS_BP
Optional: No
Call by Reference: Yes

E_TAB_AST_DOC - Documents for an Asset

Data type: CMS_TAB_AST_DOC
Optional: No
Call by Reference: Yes

E_TAB_SAS_DOC - Documents for the Sub-assets

Data type: CMS_TAB_SAS_DOC
Optional: No
Call by Reference: Yes

E_TAB_AST_NOTES - Text lines

Data type: CMS_TAB_AST_TXT_LINES
Optional: No
Call by Reference: Yes

E_TAB_AST_SYS_STAT - System status of the Asset

Data type: CMS_TAB_AST_SYS_STAT
Optional: No
Call by Reference: Yes

E_TAB_AST_USR_STAT - User status of the Asset

Data type: CMS_TAB_AST_USR_STAT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CMS_API_AST_GET_MLT 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_i_tab_ast_guid  TYPE CMS_TAB_AST_PKY, "   
lv_e_tab_ast_details  TYPE CMS_TAB_AST_DETAILS_API, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_flg_lock  TYPE CMS_DTE_FLG_LOCK, "   
lv_e_tab_sas_details  TYPE CMS_TAB_SAS_DETAILS_API, "   
lv_i_flg_db  TYPE CMS_DTE_FLG_FETCH_FROM_DB, "   'X'
lv_e_tab_ast_bp  TYPE CMS_TAB_AST_BP, "   
lv_e_tab_sas_bp  TYPE CMS_TAB_SAS_BP, "   
lv_i_str_ast_reqd_data  TYPE CMS_STR_AST_REQD_DATA, "   
lv_e_tab_ast_doc  TYPE CMS_TAB_AST_DOC, "   
lv_e_tab_sas_doc  TYPE CMS_TAB_SAS_DOC, "   
lv_e_tab_ast_notes  TYPE CMS_TAB_AST_TXT_LINES, "   
lv_e_tab_ast_sys_stat  TYPE CMS_TAB_AST_SYS_STAT, "   
lv_e_tab_ast_usr_stat  TYPE CMS_TAB_AST_USR_STAT. "   

  CALL FUNCTION 'CMS_API_AST_GET_MLT'  "Fetch details on an Asset
    EXPORTING
         I_TAB_AST_GUID = lv_i_tab_ast_guid
         I_FLG_LOCK = lv_i_flg_lock
         I_FLG_DB = lv_i_flg_db
         I_STR_AST_REQD_DATA = lv_i_str_ast_reqd_data
    IMPORTING
         E_TAB_AST_DETAILS = lv_e_tab_ast_details
         E_TAB_RC = lv_e_tab_rc
         E_TAB_SAS_DETAILS = lv_e_tab_sas_details
         E_TAB_AST_BP = lv_e_tab_ast_bp
         E_TAB_SAS_BP = lv_e_tab_sas_bp
         E_TAB_AST_DOC = lv_e_tab_ast_doc
         E_TAB_SAS_DOC = lv_e_tab_sas_doc
         E_TAB_AST_NOTES = lv_e_tab_ast_notes
         E_TAB_AST_SYS_STAT = lv_e_tab_ast_sys_stat
         E_TAB_AST_USR_STAT = lv_e_tab_ast_usr_stat
. " CMS_API_AST_GET_MLT




ABAP code using 7.40 inline data declarations to call FM CMS_API_AST_GET_MLT

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.

 
 
 
 
 
DATA(ld_i_flg_db) = 'X'.
 
 
 
 
 
 
 
 
 


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!