SAP CMS_API_SHP_GET_BY_SKEY Function Module for Gets the GUID(s) for the semantic key passed (API Layer)









CMS_API_SHP_GET_BY_SKEY is a standard cms api shp get by skey SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets the GUID(s) for the semantic key passed (API Layer) 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 shp get by skey FM, simply by entering the name CMS_API_SHP_GET_BY_SKEY into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_API_SHP_GET_BY_SKEY 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_SHP_GET_BY_SKEY'"Gets the GUID(s) for the semantic key passed (API Layer)
EXPORTING
I_SHP_ID = "Ship ID
I_SHP_TYPE = "Ship Type

IMPORTING
E_SHP_GUID = "Ship GUID
E_TAB_RC = "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_API_SHP_GET_BY_SKEY

I_SHP_ID - Ship ID

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

I_SHP_TYPE - Ship Type

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

EXPORTING Parameters details for CMS_API_SHP_GET_BY_SKEY

E_SHP_GUID - Ship GUID

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

E_TAB_RC - Return Code and corresponding Message

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

Copy and paste ABAP code example for CMS_API_SHP_GET_BY_SKEY 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_shp_id  TYPE CMS_DTE_SHP_ID, "   
lv_e_shp_guid  TYPE CMS_DTE_SHP_GUID, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_shp_type  TYPE CMS_DTE_SHP_TYP. "   

  CALL FUNCTION 'CMS_API_SHP_GET_BY_SKEY'  "Gets the GUID(s) for the semantic key passed (API Layer)
    EXPORTING
         I_SHP_ID = lv_i_shp_id
         I_SHP_TYPE = lv_i_shp_type
    IMPORTING
         E_SHP_GUID = lv_e_shp_guid
         E_TAB_RC = lv_e_tab_rc
. " CMS_API_SHP_GET_BY_SKEY




ABAP code using 7.40 inline data declarations to call FM CMS_API_SHP_GET_BY_SKEY

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



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!