SAP CC_POPUP_INT_INPUT Function Module for
CC_POPUP_INT_INPUT is a standard cc popup int input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 cc popup int input FM, simply by entering the name CC_POPUP_INT_INPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CONTROL_COMPOSER_FG
Program Name: SAPLCONTROL_COMPOSER_FG
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CC_POPUP_INT_INPUT 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 'CC_POPUP_INT_INPUT'".
EXPORTING
PROPERTY_NAME = "
IMPORTING
VALUE_CHANGED = "
CHANGING
INT_VALUE = "
IMPORTING Parameters details for CC_POPUP_INT_INPUT
PROPERTY_NAME -
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CC_POPUP_INT_INPUT
VALUE_CHANGED -
Data type: AS4FLAGOptional: No
Call by Reference: Yes
CHANGING Parameters details for CC_POPUP_INT_INPUT
INT_VALUE -
Data type: IOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CC_POPUP_INT_INPUT 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_int_value | TYPE I, " | |||
| lv_property_name | TYPE STRING, " | |||
| lv_value_changed | TYPE AS4FLAG. " |
|   CALL FUNCTION 'CC_POPUP_INT_INPUT' " |
| EXPORTING | ||
| PROPERTY_NAME | = lv_property_name | |
| IMPORTING | ||
| VALUE_CHANGED | = lv_value_changed | |
| CHANGING | ||
| INT_VALUE | = lv_int_value | |
| . " CC_POPUP_INT_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM CC_POPUP_INT_INPUT
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