SAP CPE_SD_VALID_TERMRULE_READ_CB Function Module for CPE_C - Valid Term Rule for SD - Read Customizing Buffer
CPE_SD_VALID_TERMRULE_READ_CB is a standard cpe sd valid termrule read cb 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 - Valid Term Rule for SD - Read Customizing Buffer 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 termrule read cb FM, simply by entering the name CPE_SD_VALID_TERMRULE_READ_CB into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_SD_VALID_TERMRULE_CB
Program Name: SAPLCPE_SD_VALID_TERMRULE_CB
Main Program: SAPLCPE_SD_VALID_TERMRULE_CB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CPE_SD_VALID_TERMRULE_READ_CB 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_TERMRULE_READ_CB'"CPE_C - Valid Term Rule for SD - Read Customizing Buffer.
EXPORTING
IV_LOGSYS = "Logical system
IV_TERMRULE = "CPE Term - Term Rule
IV_VALIDTO = "CPE - Valid to Time Stamp of Object
IS_SD_VALIDAREA = "Area of Validity for Commodity Pricing Parts in SD
* IV_LANGU = SY-LANGU "R/3 System, current language
* IV_NO_BUFFER = ' ' "Single-character flag
IMPORTING
ES_TERMRULE = "CPE Term - Term Rule
EV_RULETEXT = "Description
EXCEPTIONS
NOT_FOUND = 1 MISSING_BASIS_AUTHORIZATION = 2
IMPORTING Parameters details for CPE_SD_VALID_TERMRULE_READ_CB
IV_LOGSYS - Logical system
Data type: LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
IV_TERMRULE - CPE Term - Term Rule
Data type: CPET_TERMRULEOptional: No
Call by Reference: No ( called with pass by value option)
IV_VALIDTO - CPE - Valid to Time Stamp of Object
Data type: CPET_VALIDTOOptional: No
Call by Reference: No ( called with pass by value option)
IS_SD_VALIDAREA - Area of Validity for Commodity Pricing Parts in SD
Data type: CPET_SD_VALIDAREAOptional: No
Call by Reference: No ( called with pass by value option)
IV_LANGU - R/3 System, current language
Data type: LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_BUFFER - Single-character flag
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CPE_SD_VALID_TERMRULE_READ_CB
ES_TERMRULE - CPE Term - Term Rule
Data type: CPEC_TERMRULEOptional: No
Call by Reference: No ( called with pass by value option)
EV_RULETEXT - Description
Data type: CPEC_TERMRULE_T-RULETEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - no valid entry found
Data type:Optional: No
Call by Reference: Yes
MISSING_BASIS_AUTHORIZATION - The needed authorization for CPE BASIS functionality is missing
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CPE_SD_VALID_TERMRULE_READ_CB 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_iv_logsys | TYPE LOGSYS, " | |||
| lv_not_found | TYPE LOGSYS, " | |||
| lv_es_termrule | TYPE CPEC_TERMRULE, " | |||
| lv_ev_ruletext | TYPE CPEC_TERMRULE_T-RULETEXT, " | |||
| lv_iv_termrule | TYPE CPET_TERMRULE, " | |||
| lv_missing_basis_authorization | TYPE CPET_TERMRULE, " | |||
| lv_iv_validto | TYPE CPET_VALIDTO, " | |||
| lv_is_sd_validarea | TYPE CPET_SD_VALIDAREA, " | |||
| lv_iv_langu | TYPE LANGU, " SY-LANGU | |||
| lv_iv_no_buffer | TYPE CHAR1. " ' ' |
|   CALL FUNCTION 'CPE_SD_VALID_TERMRULE_READ_CB' "CPE_C - Valid Term Rule for SD - Read Customizing Buffer |
| EXPORTING | ||
| IV_LOGSYS | = lv_iv_logsys | |
| IV_TERMRULE | = lv_iv_termrule | |
| IV_VALIDTO | = lv_iv_validto | |
| IS_SD_VALIDAREA | = lv_is_sd_validarea | |
| IV_LANGU | = lv_iv_langu | |
| IV_NO_BUFFER | = lv_iv_no_buffer | |
| IMPORTING | ||
| ES_TERMRULE | = lv_es_termrule | |
| EV_RULETEXT | = lv_ev_ruletext | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| MISSING_BASIS_AUTHORIZATION = 2 | ||
| . " CPE_SD_VALID_TERMRULE_READ_CB | ||
ABAP code using 7.40 inline data declarations to call FM CPE_SD_VALID_TERMRULE_READ_CB
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.| "SELECT single RULETEXT FROM CPEC_TERMRULE_T INTO @DATA(ld_ev_ruletext). | ||||
| DATA(ld_iv_langu) | = SY-LANGU. | |||
| DATA(ld_iv_no_buffer) | = ' '. | |||
Search for further information about these or an SAP related objects