SAP CP_INPUT_START_POINT_DET Function Module for Run dialog to specify starting point and determine starting point









CP_INPUT_START_POINT_DET is a standard cp input start point det SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Run dialog to specify starting point and determine starting point 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 cp input start point det FM, simply by entering the name CP_INPUT_START_POINT_DET into the relevant SAP transaction such as SE37 or SE38.

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



Function CP_INPUT_START_POINT_DET 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 'CP_INPUT_START_POINT_DET'"Run dialog to specify starting point and determine starting point
EXPORTING
* FLG_INT = ' ' "Indicator: call from internal proc
* OBJECT_IMP = ' ' "Object which is searched for
* PLNAW_IMP = '*' "Routing/plan/network application (
* PLNTY_IMP = '*' "Routing type (screen determination
RCPLS_IMP = "Key of the dialog table

IMPORTING
FLG_GREATER = "only next to greater data record f
INDEX_DT_EXP = "Index on dialog table to starting

EXCEPTIONS
ESC = 1 NOT_FOUND = 2
.



IMPORTING Parameters details for CP_INPUT_START_POINT_DET

FLG_INT - Indicator: call from internal proc

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

OBJECT_IMP - Object which is searched for

Data type: RCLST-OBJECT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLNAW_IMP - Routing/plan/network application (

Data type: TCA01-PLNAW
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLNTY_IMP - Routing type (screen determination

Data type: TCA01-PLNTY
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

RCPLS_IMP - Key of the dialog table

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

EXPORTING Parameters details for CP_INPUT_START_POINT_DET

FLG_GREATER - only next to greater data record f

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

INDEX_DT_EXP - Index on dialog table to starting

Data type: SY-TABIX
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ESC - Abnormal termination

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

NOT_FOUND - No data record found

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

Copy and paste ABAP code example for CP_INPUT_START_POINT_DET 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_esc  TYPE STRING, "   
lv_flg_int  TYPE STRING, "   SPACE
lv_flg_greater  TYPE STRING, "   
lv_not_found  TYPE STRING, "   
lv_object_imp  TYPE RCLST-OBJECT, "   SPACE
lv_index_dt_exp  TYPE SY-TABIX, "   
lv_plnaw_imp  TYPE TCA01-PLNAW, "   '*'
lv_plnty_imp  TYPE TCA01-PLNTY, "   '*'
lv_rcpls_imp  TYPE RCPLS. "   

  CALL FUNCTION 'CP_INPUT_START_POINT_DET'  "Run dialog to specify starting point and determine starting point
    EXPORTING
         FLG_INT = lv_flg_int
         OBJECT_IMP = lv_object_imp
         PLNAW_IMP = lv_plnaw_imp
         PLNTY_IMP = lv_plnty_imp
         RCPLS_IMP = lv_rcpls_imp
    IMPORTING
         FLG_GREATER = lv_flg_greater
         INDEX_DT_EXP = lv_index_dt_exp
    EXCEPTIONS
        ESC = 1
        NOT_FOUND = 2
. " CP_INPUT_START_POINT_DET




ABAP code using 7.40 inline data declarations to call FM CP_INPUT_START_POINT_DET

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_flg_int) = ' '.
 
 
 
"SELECT single OBJECT FROM RCLST INTO @DATA(ld_object_imp).
DATA(ld_object_imp) = ' '.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_index_dt_exp).
 
"SELECT single PLNAW FROM TCA01 INTO @DATA(ld_plnaw_imp).
DATA(ld_plnaw_imp) = '*'.
 
"SELECT single PLNTY FROM TCA01 INTO @DATA(ld_plnty_imp).
DATA(ld_plnty_imp) = '*'.
 
 


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!