SAP CCMSBI_CPH_PTR_CHK_FOR_UPDATE Function Module for
CCMSBI_CPH_PTR_CHK_FOR_UPDATE is a standard ccmsbi cph ptr chk for update 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 ccmsbi cph ptr chk for update FM, simply by entering the name CCMSBI_CPH_PTR_CHK_FOR_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCCMSBI_EXTRACTORS
Program Name: SAPLSCCMSBI_EXTRACTORS
Main Program: SAPLSCCMSBI_EXTRACTORS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCMSBI_CPH_PTR_CHK_FOR_UPDATE 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 'CCMSBI_CPH_PTR_CHK_FOR_UPDATE'".
EXPORTING
CPH_SEL_DATE_LOW = "
CPH_SEL_DATE_HIGH = "
* XDAYS_AGGR_X_VALUE = "
* NO_DQ = ' ' "
* DATE_NOW = "
CHANGING
POINTER = "
* POINTER2 = "
TABLES
SEL_CPH_DATA = "
EXCEPTIONS
DATE_OR_TIMEZONE_MISSING = 1 CANT_CALCULATE_NEXT_PTR_DATE = 10 INVALID_SELECTION_DATE_RANGE = 11 CPH_SEL_DATA_MISSING = 2 NO_SEL_CPH_DATA_SPECIFIED = 3 CPH_DATA_SEL_CRITERIA_MISMATCH = 4 CAN_NOT_UPDATE_POINTER = 5 POINTER_KEY_NOT_SPECIFIED = 6 INVALID_RECTYPE = 7 CANT_READ_YOUNGEST_CPH_DATA = 8 XDAYS_AGGR_X_VALUE_MISSING = 9
IMPORTING Parameters details for CCMSBI_CPH_PTR_CHK_FOR_UPDATE
CPH_SEL_DATE_LOW -
Data type: ALDATEOptional: No
Call by Reference: Yes
CPH_SEL_DATE_HIGH -
Data type: ALDATEOptional: No
Call by Reference: Yes
XDAYS_AGGR_X_VALUE -
Data type: IOptional: Yes
Call by Reference: Yes
NO_DQ -
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: Yes
DATE_NOW -
Data type: ALDATEOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for CCMSBI_CPH_PTR_CHK_FOR_UPDATE
POINTER -
Data type: CCMSBI_CPH_BWPTROptional: No
Call by Reference: Yes
POINTER2 -
Data type: CCMSBI_BWPTR_CPHOptional: Yes
Call by Reference: Yes
TABLES Parameters details for CCMSBI_CPH_PTR_CHK_FOR_UPDATE
SEL_CPH_DATA -
Data type: ALPF_OUTTAB_STROptional: No
Call by Reference: Yes
EXCEPTIONS details
DATE_OR_TIMEZONE_MISSING -
Data type:Optional: No
Call by Reference: Yes
CANT_CALCULATE_NEXT_PTR_DATE -
Data type:Optional: No
Call by Reference: Yes
INVALID_SELECTION_DATE_RANGE -
Data type:Optional: No
Call by Reference: Yes
CPH_SEL_DATA_MISSING -
Data type:Optional: No
Call by Reference: Yes
NO_SEL_CPH_DATA_SPECIFIED -
Data type:Optional: No
Call by Reference: Yes
CPH_DATA_SEL_CRITERIA_MISMATCH -
Data type:Optional: No
Call by Reference: Yes
CAN_NOT_UPDATE_POINTER -
Data type:Optional: No
Call by Reference: Yes
POINTER_KEY_NOT_SPECIFIED -
Data type:Optional: No
Call by Reference: Yes
INVALID_RECTYPE -
Data type:Optional: No
Call by Reference: Yes
CANT_READ_YOUNGEST_CPH_DATA -
Data type:Optional: No
Call by Reference: Yes
XDAYS_AGGR_X_VALUE_MISSING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CCMSBI_CPH_PTR_CHK_FOR_UPDATE 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_pointer | TYPE CCMSBI_CPH_BWPTR, " | |||
| lt_sel_cph_data | TYPE STANDARD TABLE OF ALPF_OUTTAB_STR, " | |||
| lv_cph_sel_date_low | TYPE ALDATE, " | |||
| lv_date_or_timezone_missing | TYPE ALDATE, " | |||
| lv_cant_calculate_next_ptr_date | TYPE ALDATE, " | |||
| lv_invalid_selection_date_range | TYPE ALDATE, " | |||
| lv_pointer2 | TYPE CCMSBI_BWPTR_CPH, " | |||
| lv_cph_sel_date_high | TYPE ALDATE, " | |||
| lv_cph_sel_data_missing | TYPE ALDATE, " | |||
| lv_xdays_aggr_x_value | TYPE I, " | |||
| lv_no_sel_cph_data_specified | TYPE I, " | |||
| lv_no_dq | TYPE CHAR1, " ' ' | |||
| lv_cph_data_sel_criteria_mismatch | TYPE CHAR1, " | |||
| lv_date_now | TYPE ALDATE, " | |||
| lv_can_not_update_pointer | TYPE ALDATE, " | |||
| lv_pointer_key_not_specified | TYPE ALDATE, " | |||
| lv_invalid_rectype | TYPE ALDATE, " | |||
| lv_cant_read_youngest_cph_data | TYPE ALDATE, " | |||
| lv_xdays_aggr_x_value_missing | TYPE ALDATE. " |
|   CALL FUNCTION 'CCMSBI_CPH_PTR_CHK_FOR_UPDATE' " |
| EXPORTING | ||
| CPH_SEL_DATE_LOW | = lv_cph_sel_date_low | |
| CPH_SEL_DATE_HIGH | = lv_cph_sel_date_high | |
| XDAYS_AGGR_X_VALUE | = lv_xdays_aggr_x_value | |
| NO_DQ | = lv_no_dq | |
| DATE_NOW | = lv_date_now | |
| CHANGING | ||
| POINTER | = lv_pointer | |
| POINTER2 | = lv_pointer2 | |
| TABLES | ||
| SEL_CPH_DATA | = lt_sel_cph_data | |
| EXCEPTIONS | ||
| DATE_OR_TIMEZONE_MISSING = 1 | ||
| CANT_CALCULATE_NEXT_PTR_DATE = 10 | ||
| INVALID_SELECTION_DATE_RANGE = 11 | ||
| CPH_SEL_DATA_MISSING = 2 | ||
| NO_SEL_CPH_DATA_SPECIFIED = 3 | ||
| CPH_DATA_SEL_CRITERIA_MISMATCH = 4 | ||
| CAN_NOT_UPDATE_POINTER = 5 | ||
| POINTER_KEY_NOT_SPECIFIED = 6 | ||
| INVALID_RECTYPE = 7 | ||
| CANT_READ_YOUNGEST_CPH_DATA = 8 | ||
| XDAYS_AGGR_X_VALUE_MISSING = 9 | ||
| . " CCMSBI_CPH_PTR_CHK_FOR_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM CCMSBI_CPH_PTR_CHK_FOR_UPDATE
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_no_dq) | = ' '. | |||
Search for further information about these or an SAP related objects