SAP CPE_TERMCONVOUT_READ_DB Function Module for CPE_D - Term Conversion Result - Read DB









CPE_TERMCONVOUT_READ_DB is a standard cpe termconvout 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 - Term Conversion Result - 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 termconvout read db FM, simply by entering the name CPE_TERMCONVOUT_READ_DB into the relevant SAP transaction such as SE37 or SE38.

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



Function CPE_TERMCONVOUT_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_TERMCONVOUT_READ_DB'"CPE_D - Term Conversion Result - Read DB
EXPORTING
IV_TERMCONVOUT_GUID = "Globally Unique Identifier
IV_CONVPLACE = "CPE - Conversion Place
* IV_NO_BUFFER = ' ' "Single-character flag

IMPORTING
ES_TERMCONVOUT = "table type of table CPED_TERMCONVOUT

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for CPE_TERMCONVOUT_READ_DB

IV_TERMCONVOUT_GUID - Globally Unique Identifier

Data type: CPET_TERMCONVOUT_GUID
Optional: No
Call by Reference: Yes

IV_CONVPLACE - CPE - Conversion Place

Data type: CPET_CONVPLACE
Optional: No
Call by Reference: Yes

IV_NO_BUFFER - Single-character flag

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CPE_TERMCONVOUT_READ_DB

ES_TERMCONVOUT - table type of table CPED_TERMCONVOUT

Data type: CPED_TERMCONVOUT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CPE_TERMCONVOUT_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_termconvout  TYPE CPED_TERMCONVOUT, "   
lv_iv_termconvout_guid  TYPE CPET_TERMCONVOUT_GUID, "   
lv_iv_convplace  TYPE CPET_CONVPLACE, "   
lv_iv_no_buffer  TYPE CHAR1. "   ' '

  CALL FUNCTION 'CPE_TERMCONVOUT_READ_DB'  "CPE_D - Term Conversion Result - Read DB
    EXPORTING
         IV_TERMCONVOUT_GUID = lv_iv_termconvout_guid
         IV_CONVPLACE = lv_iv_convplace
         IV_NO_BUFFER = lv_iv_no_buffer
    IMPORTING
         ES_TERMCONVOUT = lv_es_termconvout
    EXCEPTIONS
        NOT_FOUND = 1
. " CPE_TERMCONVOUT_READ_DB




ABAP code using 7.40 inline data declarations to call FM CPE_TERMCONVOUT_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



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!