SAP CMS_API_STATUS_GET_CHANGE_FLG Function Module for Logic to get status change flag

Search SAP Function Modules

CMS_API_STATUS_GET_CHANGE_FLG is a standard cms api status get change flg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Logic to get status change flag 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 status get change flg FM, simply by entering the name CMS_API_STATUS_GET_CHANGE_FLG into the relevant SAP transaction such as SE37 or SE38.

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

Function CMS_API_STATUS_GET_CHANGE_FLG 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_STATUS_GET_CHANGE_FLG'"Logic to get status change flag
  EXPORTING
   I_OBJECT_ID =  "Object Identification number

 IMPORTING
   E_FLG_CHANGE =  "Indicator

.

IMPORTING Parameters details for CMS_API_STATUS_GET_CHANGE_FLG

I_OBJECT_ID - Object Identification number

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

EXPORTING Parameters details for CMS_API_STATUS_GET_CHANGE_FLG

E_FLG_CHANGE - Indicator

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

Copy and paste ABAP code example for CMS_API_STATUS_GET_CHANGE_FLG 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 CMS_API_STATUS_GET_CHANGE_FLG

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