SAP GTR_NOTIFICATION_BY_TRIGGER Function Module for Grantor Management : Billing off cycle CRM notification

Search SAP Function Modules

GTR_NOTIFICATION_BY_TRIGGER is a standard gtr notification by trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Grantor Management : Billing off cycle CRM notification 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 gtr notification by trigger FM, simply by entering the name GTR_NOTIFICATION_BY_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

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

Function GTR_NOTIFICATION_BY_TRIGGER 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 'GTR_NOTIFICATION_BY_TRIGGER'"Grantor Management : Billing off cycle CRM notification
  EXPORTING
*  IV_SCENARIO = 'GRANTOR' "CRM Proxy scenario
   IT_PSM_RETURN =  "Grantor Management: PSM return table

EXCEPTIONS
   SCENARIO_NOT_FOUND = 1    SAME_BRI_ACC_DOC_DIFF_CURRENCY = 2    MULTI_BP_NOT_ACTIVE = 3 

.

IMPORTING Parameters details for GTR_NOTIFICATION_BY_TRIGGER

IV_SCENARIO - CRM Proxy scenario

Data type: GTRT_CRM_PROXY_SCENARIO
Default: 'GRANTOR'
Optional: No
Call by Reference: Yes

IT_PSM_RETURN - Grantor Management: PSM return table

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

EXCEPTIONS details

SCENARIO_NOT_FOUND - Scenario is unknown

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

SAME_BRI_ACC_DOC_DIFF_CURRENCY - Posting of amount with a different currency for same accounting doc and BRI

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

MULTI_BP_NOT_ACTIVE - Multiple Payment Recipient not activated in IMG

Data type:
Optional: No
Call by Reference: Yes

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

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