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

Function PROGRESS_TRACKING 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 'PROGRESS_TRACKING'"Progress Tracking.
EXPORTING
* I_DISPLAY = ' ' "Generic Type
* I_PROFILE = "Expediting Profile
I_OBJECT = "Expediting Object Indicator
T_OBJECTS = "Predefined Type
EXCEPTIONS
DATA_LOCKED = 1 INPUT_INCOMPLETE = 2
IMPORTING Parameters details for PROGRESS_TRACKING
I_DISPLAY - Generic Type
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_PROFILE - Expediting Profile
Data type: TXPDPR-PROFILEOptional: Yes
Call by Reference: Yes
I_OBJECT - Expediting Object Indicator
Data type: TXPDOBJ-EXPOBJOptional: No
Call by Reference: Yes
T_OBJECTS - Predefined Type
Data type: ANY TABLEOptional: No
Call by Reference: Yes
EXCEPTIONS details
DATA_LOCKED -
Data type:Optional: No
Call by Reference: Yes
INPUT_INCOMPLETE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PROGRESS_TRACKING 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_display | TYPE C, " SPACE | |||
| lv_data_locked | TYPE C, " | |||
| lv_i_profile | TYPE TXPDPR-PROFILE, " | |||
| lv_input_incomplete | TYPE TXPDPR, " | |||
| lv_i_object | TYPE TXPDOBJ-EXPOBJ, " | |||
| lv_t_objects | TYPE ANY TABLE. " |
|   CALL FUNCTION 'PROGRESS_TRACKING' "Progress Tracking |
| EXPORTING | ||
| I_DISPLAY | = lv_i_display | |
| I_PROFILE | = lv_i_profile | |
| I_OBJECT | = lv_i_object | |
| T_OBJECTS | = lv_t_objects | |
| EXCEPTIONS | ||
| DATA_LOCKED = 1 | ||
| INPUT_INCOMPLETE = 2 | ||
| . " PROGRESS_TRACKING | ||
ABAP code using 7.40 inline data declarations to call FM PROGRESS_TRACKING
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.| DATA(ld_i_display) | = ' '. | |||
| "SELECT single PROFILE FROM TXPDPR INTO @DATA(ld_i_profile). | ||||
| "SELECT single EXPOBJ FROM TXPDOBJ INTO @DATA(ld_i_object). | ||||
Search for further information about these or an SAP related objects