SAP CPE_TERMCONVOUT_READ_MULTI_OW Function Module for CPE_D - Input for Term Conversion - Read Object Work Areas









CPE_TERMCONVOUT_READ_MULTI_OW is a standard cpe termconvout read multi ow 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 - Input for Term Conversion - Read Object Work Areas 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 multi ow FM, simply by entering the name CPE_TERMCONVOUT_READ_MULTI_OW into the relevant SAP transaction such as SE37 or SE38.

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



Function CPE_TERMCONVOUT_READ_MULTI_OW 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_MULTI_OW'"CPE_D - Input for Term Conversion - Read Object Work Areas
  EXPORTING
*  IV_TERMCONVOUT_GUID =  "CPE Term - GUID for Conversion Result
*  IV_DOCITEM_GUID =  "CPE Caller - GUID of Document Item
*  IV_COND_TYPE =  "Condition type
*  IV_TERMNO =  "CPE Term - Number in Formula
*  IV_LANGU =  "Language Key
   IS_DOCUMENT_COM =  "CPE: Communication Structure with Document Fields

 IMPORTING
   ET_TERMCONVOUT_COM =  "CPE - Communication Table for Result of Term Conversion
   ET_INPUT_FIELDNAMES =  "CPE - Names of displayed fields and input fields

EXCEPTIONS
   NOTHING_FOUND = 1    ERROR_OCCURRED = 2
.



IMPORTING Parameters details for CPE_TERMCONVOUT_READ_MULTI_OW

IV_TERMCONVOUT_GUID - CPE Term - GUID for Conversion Result

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

IV_DOCITEM_GUID - CPE Caller - GUID of Document Item

Data type: CPET_DOCITEM_GUID
Optional: Yes
Call by Reference: Yes

IV_COND_TYPE - Condition type

Data type: CPET_COND_TYPE
Optional: Yes
Call by Reference: Yes

IV_TERMNO - CPE Term - Number in Formula

Data type: CPET_TERMNO
Optional: Yes
Call by Reference: Yes

IV_LANGU - Language Key

Data type: LANGU
Optional: Yes
Call by Reference: Yes

IS_DOCUMENT_COM - CPE: Communication Structure with Document Fields

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

EXPORTING Parameters details for CPE_TERMCONVOUT_READ_MULTI_OW

ET_TERMCONVOUT_COM - CPE - Communication Table for Result of Term Conversion

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

ET_INPUT_FIELDNAMES - CPE - Names of displayed fields and input fields

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

EXCEPTIONS details

NOTHING_FOUND - No entries found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_OCCURRED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CPE_TERMCONVOUT_READ_MULTI_OW 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_nothing_found  TYPE STRING, "   
lv_et_termconvout_com  TYPE CPET_TERMCONVOUT_COM_TAB, "   
lv_iv_termconvout_guid  TYPE CPET_TERMCONVOUT_GUID, "   
lv_error_occurred  TYPE CPET_TERMCONVOUT_GUID, "   
lv_iv_docitem_guid  TYPE CPET_DOCITEM_GUID, "   
lv_et_input_fieldnames  TYPE CPET_INPUT_FIELDNAMES_TAB, "   
lv_iv_cond_type  TYPE CPET_COND_TYPE, "   
lv_iv_termno  TYPE CPET_TERMNO, "   
lv_iv_langu  TYPE LANGU, "   
lv_is_document_com  TYPE CPET_DOCUMENT_COM. "   

  CALL FUNCTION 'CPE_TERMCONVOUT_READ_MULTI_OW'  "CPE_D - Input for Term Conversion - Read Object Work Areas
    EXPORTING
         IV_TERMCONVOUT_GUID = lv_iv_termconvout_guid
         IV_DOCITEM_GUID = lv_iv_docitem_guid
         IV_COND_TYPE = lv_iv_cond_type
         IV_TERMNO = lv_iv_termno
         IV_LANGU = lv_iv_langu
         IS_DOCUMENT_COM = lv_is_document_com
    IMPORTING
         ET_TERMCONVOUT_COM = lv_et_termconvout_com
         ET_INPUT_FIELDNAMES = lv_et_input_fieldnames
    EXCEPTIONS
        NOTHING_FOUND = 1
        ERROR_OCCURRED = 2
. " CPE_TERMCONVOUT_READ_MULTI_OW




ABAP code using 7.40 inline data declarations to call FM CPE_TERMCONVOUT_READ_MULTI_OW

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.

 
 
 
 
 
 
 
 
 
 


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!