SAP CPE_SD_VALID_TERM_F4_HELP Function Module for CPE_C - F4-Help for Valid Terms in SD
CPE_SD_VALID_TERM_F4_HELP is a standard cpe sd valid term f4 help SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CPE_C - F4-Help for Valid Terms in SD 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 cpe sd valid term f4 help FM, simply by entering the name CPE_SD_VALID_TERM_F4_HELP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_SD_VALID_TERM_CB
Program Name: SAPLCPE_SD_VALID_TERM_CB
Main Program: SAPLCPE_SD_VALID_TERM_CB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CPE_SD_VALID_TERM_F4_HELP 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 'CPE_SD_VALID_TERM_F4_HELP'"CPE_C - F4-Help for Valid Terms in SD.
EXPORTING
IV_LOGSYS = "Logical system
* IV_COND_TYPE = ' ' "Condition type
IV_VALIDTO = "CPE - Valid to Time Stamp of Object
IS_SD_VALIDAREA = "Area of Validity for Commodity Pricing Parts in SD
* IV_SELECTION = 'X' "Allow Selection
* IV_NO_BUFFER = ' ' "Single-character flag
IMPORTING
EV_TERMID = "CPE Term - Key
EXCEPTIONS
NOTHING_FOUND = 1 NOTHING_CHOSEN = 2
IMPORTING Parameters details for CPE_SD_VALID_TERM_F4_HELP
IV_LOGSYS - Logical system
Data type: LOGSYSOptional: No
Call by Reference: Yes
IV_COND_TYPE - Condition type
Data type: KSCHLDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_VALIDTO - CPE - Valid to Time Stamp of Object
Data type: CPET_VALIDTOOptional: No
Call by Reference: Yes
IS_SD_VALIDAREA - Area of Validity for Commodity Pricing Parts in SD
Data type: CPET_SD_VALIDAREAOptional: No
Call by Reference: Yes
IV_SELECTION - Allow Selection
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_NO_BUFFER - Single-character flag
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CPE_SD_VALID_TERM_F4_HELP
EV_TERMID - CPE Term - Key
Data type: CPET_TERMIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTHING_FOUND - No values found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOTHING_CHOSEN - No value chosen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CPE_SD_VALID_TERM_F4_HELP 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_ev_termid | TYPE CPET_TERMID, " | |||
| lv_iv_logsys | TYPE LOGSYS, " | |||
| lv_nothing_found | TYPE LOGSYS, " | |||
| lv_iv_cond_type | TYPE KSCHL, " ' ' | |||
| lv_nothing_chosen | TYPE KSCHL, " | |||
| lv_iv_validto | TYPE CPET_VALIDTO, " | |||
| lv_is_sd_validarea | TYPE CPET_SD_VALIDAREA, " | |||
| lv_iv_selection | TYPE C, " 'X' | |||
| lv_iv_no_buffer | TYPE CHAR1. " ' ' |
|   CALL FUNCTION 'CPE_SD_VALID_TERM_F4_HELP' "CPE_C - F4-Help for Valid Terms in SD |
| EXPORTING | ||
| IV_LOGSYS | = lv_iv_logsys | |
| IV_COND_TYPE | = lv_iv_cond_type | |
| IV_VALIDTO | = lv_iv_validto | |
| IS_SD_VALIDAREA | = lv_is_sd_validarea | |
| IV_SELECTION | = lv_iv_selection | |
| IV_NO_BUFFER | = lv_iv_no_buffer | |
| IMPORTING | ||
| EV_TERMID | = lv_ev_termid | |
| EXCEPTIONS | ||
| NOTHING_FOUND = 1 | ||
| NOTHING_CHOSEN = 2 | ||
| . " CPE_SD_VALID_TERM_F4_HELP | ||
ABAP code using 7.40 inline data declarations to call FM CPE_SD_VALID_TERM_F4_HELP
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_iv_cond_type) | = ' '. | |||
| DATA(ld_iv_selection) | = 'X'. | |||
| DATA(ld_iv_no_buffer) | = ' '. | |||
Search for further information about these or an SAP related objects