SAP FTR_JUMP_PIN Function Module for Goto Position Indicator
FTR_JUMP_PIN is a standard ftr jump pin SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Goto Position Indicator 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 jump pin FM, simply by entering the name FTR_JUMP_PIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_IRATE
Program Name: SAPLFTR_IRATE
Main Program: SAPLFTR_IRATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_JUMP_PIN 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_JUMP_PIN'"Goto Position Indicator.
EXPORTING
PI_APPL_CTRL = "TR Transaction Management: Application Control
* PI_TAB_PS_TERMS = "Table with Position-Differentiating PS Acct Assignments
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for FTR_JUMP_PIN
PI_APPL_CTRL - TR Transaction Management: Application Control
Data type: CL_FTR_APPL_CTRLOptional: No
Call by Reference: Yes
PI_TAB_PS_TERMS - Table with Position-Differentiating PS Acct Assignments
Data type: TRGY_PS_TERMSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_JUMP_PIN 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_failed | TYPE STRING, " | |||
| lv_pi_appl_ctrl | TYPE CL_FTR_APPL_CTRL, " | |||
| lv_pi_tab_ps_terms | TYPE TRGY_PS_TERMS. " |
|   CALL FUNCTION 'FTR_JUMP_PIN' "Goto Position Indicator |
| EXPORTING | ||
| PI_APPL_CTRL | = lv_pi_appl_ctrl | |
| PI_TAB_PS_TERMS | = lv_pi_tab_ps_terms | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " FTR_JUMP_PIN | ||
ABAP code using 7.40 inline data declarations to call FM FTR_JUMP_PIN
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