SAP FTR_ENTRY_GET_DEAL_ACTIVITY Function Module for FM to get the permitted activities for a deal









FTR_ENTRY_GET_DEAL_ACTIVITY is a standard ftr entry get deal activity SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM to get the permitted activities for a deal 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 ftr entry get deal activity FM, simply by entering the name FTR_ENTRY_GET_DEAL_ACTIVITY into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_ENTRY_GET_DEAL_ACTIVITY 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 'FTR_ENTRY_GET_DEAL_ACTIVITY'"FM to get the permitted activities for a deal
EXPORTING
* I_BUKRS = "Company Code
* I_RFHA = "Financial Transaction
* I_SANLF = "Product Category

IMPORTING
FTR_ENTRY_TAB_DEAL_ACTIVITY = "Table type for deal activity

EXCEPTIONS
NOTFOUND = 1
.



IMPORTING Parameters details for FTR_ENTRY_GET_DEAL_ACTIVITY

I_BUKRS - Company Code

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

I_RFHA - Financial Transaction

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

I_SANLF - Product Category

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

EXPORTING Parameters details for FTR_ENTRY_GET_DEAL_ACTIVITY

FTR_ENTRY_TAB_DEAL_ACTIVITY - Table type for deal activity

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

EXCEPTIONS details

NOTFOUND - Activity not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FTR_ENTRY_GET_DEAL_ACTIVITY 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_bukrs  TYPE BUKRS, "   
lv_notfound  TYPE BUKRS, "   
lv_ftr_entry_tab_deal_activity  TYPE FTR_ENTRY_DEAL_ACTIVITY_T, "   
lv_i_rfha  TYPE TB_RFHA, "   
lv_i_sanlf  TYPE SANLF. "   

  CALL FUNCTION 'FTR_ENTRY_GET_DEAL_ACTIVITY'  "FM to get the permitted activities for a deal
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_RFHA = lv_i_rfha
         I_SANLF = lv_i_sanlf
    IMPORTING
         FTR_ENTRY_TAB_DEAL_ACTIVITY = lv_ftr_entry_tab_deal_activity
    EXCEPTIONS
        NOTFOUND = 1
. " FTR_ENTRY_GET_DEAL_ACTIVITY




ABAP code using 7.40 inline data declarations to call FM FTR_ENTRY_GET_DEAL_ACTIVITY

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!