SAP CPE_EXTENSION_READ_DB Function Module for CPE_D - Extension - Read DB
CPE_EXTENSION_READ_DB is a standard cpe extension read db 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_D - Extension - Read DB 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 extension read db FM, simply by entering the name CPE_EXTENSION_READ_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_EXTENSION_DB
Program Name: SAPLCPE_EXTENSION_DB
Main Program: SAPLCPE_EXTENSION_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CPE_EXTENSION_READ_DB 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_EXTENSION_READ_DB'"CPE_D - Extension - Read DB.
EXPORTING
IV_DOCITEM_GUID = "CPE Caller - GUID of Document Item
IV_COND_TYPE = "CPE: Condition Type for Commodity Pricing
IV_TERMNO = "CPE Term - Number in Formula
IV_REF_TYPE = "CPE Reference Type
IV_REF_KIND = "CPE Reference Kind
IV_REF_GUID = "CPE Reference Guid
* IV_NO_BUFFER = ' ' "Single-Character Flag
IMPORTING
ES_EXTENSION = "CPE Extension Data
ES_EXTENSION_DATA = "CPE Extension - Extension Data Access
EXCEPTIONS
NOT_FOUND = 1 DATA_NOT_FOUND = 2
IMPORTING Parameters details for CPE_EXTENSION_READ_DB
IV_DOCITEM_GUID - CPE Caller - GUID of Document Item
Data type: CPET_DOCITEM_GUIDOptional: No
Call by Reference: Yes
IV_COND_TYPE - CPE: Condition Type for Commodity Pricing
Data type: CPET_COND_TYPEOptional: No
Call by Reference: Yes
IV_TERMNO - CPE Term - Number in Formula
Data type: CPET_TERMNOOptional: No
Call by Reference: Yes
IV_REF_TYPE - CPE Reference Type
Data type: CPET_REF_TYPEOptional: No
Call by Reference: Yes
IV_REF_KIND - CPE Reference Kind
Data type: CPET_REF_KINDOptional: No
Call by Reference: Yes
IV_REF_GUID - CPE Reference Guid
Data type: CPET_REF_GUIDOptional: No
Call by Reference: Yes
IV_NO_BUFFER - Single-Character Flag
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CPE_EXTENSION_READ_DB
ES_EXTENSION - CPE Extension Data
Data type: CPED_EXTENSIONOptional: No
Call by Reference: Yes
ES_EXTENSION_DATA - CPE Extension - Extension Data Access
Data type: CPET_EXTENSION_DATA_ACSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
DATA_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CPE_EXTENSION_READ_DB 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_not_found | TYPE STRING, " | |||
| lv_es_extension | TYPE CPED_EXTENSION, " | |||
| lv_iv_docitem_guid | TYPE CPET_DOCITEM_GUID, " | |||
| lv_iv_cond_type | TYPE CPET_COND_TYPE, " | |||
| lv_data_not_found | TYPE CPET_COND_TYPE, " | |||
| lv_es_extension_data | TYPE CPET_EXTENSION_DATA_ACS, " | |||
| lv_iv_termno | TYPE CPET_TERMNO, " | |||
| lv_iv_ref_type | TYPE CPET_REF_TYPE, " | |||
| lv_iv_ref_kind | TYPE CPET_REF_KIND, " | |||
| lv_iv_ref_guid | TYPE CPET_REF_GUID, " | |||
| lv_iv_no_buffer | TYPE CHAR1. " ' ' |
|   CALL FUNCTION 'CPE_EXTENSION_READ_DB' "CPE_D - Extension - Read DB |
| EXPORTING | ||
| IV_DOCITEM_GUID | = lv_iv_docitem_guid | |
| IV_COND_TYPE | = lv_iv_cond_type | |
| IV_TERMNO | = lv_iv_termno | |
| IV_REF_TYPE | = lv_iv_ref_type | |
| IV_REF_KIND | = lv_iv_ref_kind | |
| IV_REF_GUID | = lv_iv_ref_guid | |
| IV_NO_BUFFER | = lv_iv_no_buffer | |
| IMPORTING | ||
| ES_EXTENSION | = lv_es_extension | |
| ES_EXTENSION_DATA | = lv_es_extension_data | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| DATA_NOT_FOUND = 2 | ||
| . " CPE_EXTENSION_READ_DB | ||
ABAP code using 7.40 inline data declarations to call FM CPE_EXTENSION_READ_DB
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_no_buffer) | = ' '. | |||
Search for further information about these or an SAP related objects