SAP GRRM_XMII_API_HEAT_MAP Function Module for Heat map api

Search SAP Function Modules

GRRM_XMII_API_HEAT_MAP is a standard grrm xmii api heat map SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Heat map api 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 grrm xmii api heat map FM, simply by entering the name GRRM_XMII_API_HEAT_MAP into the relevant SAP transaction such as SE37 or SE38.

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

Function GRRM_XMII_API_HEAT_MAP 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 'GRRM_XMII_API_HEAT_MAP'"Heat map api
  EXPORTING
*  I_FOCUS_DATE = SY-DATUM "Focus date
*  I_REPORT =  "To include finished activities and cancelled activities
*  I_SCENARIO =  "Before Response or after response

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
   ET_RESULT =  "Risk heat map
   ET_MESSAGE =  "Error Messages

.

IMPORTING Parameters details for GRRM_XMII_API_HEAT_MAP

I_FOCUS_DATE - Focus date

Data type: GRFN_DATE
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_REPORT - To include finished activities and cancelled activities

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

I_SCENARIO - Before Response or after response

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

EXPORTING Parameters details for GRRM_XMII_API_HEAT_MAP

E_RETURN_CODE - Natural number

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

TABLES Parameters details for GRRM_XMII_API_HEAT_MAP

ET_RESULT - Risk heat map

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

ET_MESSAGE - Error Messages

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

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

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