SAP CNVCF_PROGRESS Function Module for Progress indicator
CNVCF_PROGRESS is a standard cnvcf progress 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 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 cnvcf progress FM, simply by entering the name CNVCF_PROGRESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNVC_VS_BASE
Program Name: SAPLCNVC_VS_BASE
Main Program: SAPLCNVC_VS_BASE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CNVCF_PROGRESS 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 'CNVCF_PROGRESS'"Progress indicator.
EXPORTING
* TEXT = "
* VAR1 = "
* VAR2 = "
* VAR3 = "
* VAR4 = "
* POSITION = "
* MAXIMUM = "
IMPORTING Parameters details for CNVCF_PROGRESS
TEXT -
Data type:Optional: Yes
Call by Reference: Yes
VAR1 -
Data type:Optional: Yes
Call by Reference: Yes
VAR2 -
Data type:Optional: Yes
Call by Reference: Yes
VAR3 -
Data type:Optional: Yes
Call by Reference: Yes
VAR4 -
Data type:Optional: Yes
Call by Reference: Yes
POSITION -
Data type:Optional: Yes
Call by Reference: Yes
MAXIMUM -
Data type:Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CNVCF_PROGRESS 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_text | TYPE STRING, " | |||
| lv_var1 | TYPE STRING, " | |||
| lv_var2 | TYPE STRING, " | |||
| lv_var3 | TYPE STRING, " | |||
| lv_var4 | TYPE STRING, " | |||
| lv_position | TYPE STRING, " | |||
| lv_maximum | TYPE STRING. " |
| CALL FUNCTION 'CNVCF_PROGRESS' "Progress indicator |
| EXPORTING | ||
| TEXT | = lv_text | |
| VAR1 | = lv_var1 | |
| VAR2 | = lv_var2 | |
| VAR3 | = lv_var3 | |
| VAR4 | = lv_var4 | |
| POSITION | = lv_position | |
| MAXIMUM | = lv_maximum | |
| . " CNVCF_PROGRESS | ||
ABAP code using 7.40 inline data declarations to call FM CNVCF_PROGRESS
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