SAP CPE_DEFTERM_USERFIELDS_READ_OW Function Module for CPE_D - Default Term User Fields - Read Object Work Area
CPE_DEFTERM_USERFIELDS_READ_OW is a standard cpe defterm userfields read 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 - Default Term User Fields - Read Object Work Area 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 defterm userfields read ow FM, simply by entering the name CPE_DEFTERM_USERFIELDS_READ_OW into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_DEFTERM_USERFIELDS_OW
Program Name: SAPLCPE_DEFTERM_USERFIELDS_OW
Main Program: SAPLCPE_DEFTERM_USERFIELDS_OW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CPE_DEFTERM_USERFIELDS_READ_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_DEFTERM_USERFIELDS_READ_OW'"CPE_D - Default Term User Fields - Read Object Work Area.
EXPORTING
IV_DOC_GUID = "CPE Caller - GUID of Document Header
IV_COND_TYPE = "Condition type
IV_TERMNO = "CPE Term - Number in Formula
* IV_VALIDFROM = "CPE - 'Valid From' Time Stamp of Commodity Pricing Object
* IV_TERMTYPE = "CPE Term - Term Calculation Type
* IV_LANGU = SY-LANGU "R/3 System, current language
IS_DOCUMENT_COM = "CPE: Communication Structure with Document Fields
IMPORTING
ES_DEFTERM_USERFIELDS_COM = "CPE - Communication Structure for Default Term User Fields
ET_INPUT_FIELDNAMES = "CPE - Names of Displayed Fields and Input Fields
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for CPE_DEFTERM_USERFIELDS_READ_OW
IV_DOC_GUID - CPE Caller - GUID of Document Header
Data type: CPET_DOC_GUIDOptional: No
Call by Reference: Yes
IV_COND_TYPE - Condition type
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_VALIDFROM - CPE - 'Valid From' Time Stamp of Commodity Pricing Object
Data type: CPET_VALIDFROMOptional: Yes
Call by Reference: Yes
IV_TERMTYPE - CPE Term - Term Calculation Type
Data type: CPET_TERMTYPEOptional: Yes
Call by Reference: Yes
IV_LANGU - R/3 System, current language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
IS_DOCUMENT_COM - CPE: Communication Structure with Document Fields
Data type: CPET_DOCUMENT_COMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CPE_DEFTERM_USERFIELDS_READ_OW
ES_DEFTERM_USERFIELDS_COM - CPE - Communication Structure for Default Term User Fields
Data type: CPET_DEFTERM_USERFIELDS_COMOptional: No
Call by Reference: Yes
ET_INPUT_FIELDNAMES - CPE - Names of Displayed Fields and Input Fields
Data type: CPET_INPUT_FIELDNAMES_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED - Error occurred during processing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CPE_DEFTERM_USERFIELDS_READ_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_iv_doc_guid | TYPE CPET_DOC_GUID, " | |||
lv_error_occurred | TYPE CPET_DOC_GUID, " | |||
lv_es_defterm_userfields_com | TYPE CPET_DEFTERM_USERFIELDS_COM, " | |||
lv_iv_cond_type | TYPE CPET_COND_TYPE, " | |||
lv_et_input_fieldnames | TYPE CPET_INPUT_FIELDNAMES_TAB, " | |||
lv_iv_termno | TYPE CPET_TERMNO, " | |||
lv_iv_validfrom | TYPE CPET_VALIDFROM, " | |||
lv_iv_termtype | TYPE CPET_TERMTYPE, " | |||
lv_iv_langu | TYPE SY-LANGU, " SY-LANGU | |||
lv_is_document_com | TYPE CPET_DOCUMENT_COM. " |
  CALL FUNCTION 'CPE_DEFTERM_USERFIELDS_READ_OW' "CPE_D - Default Term User Fields - Read Object Work Area |
EXPORTING | ||
IV_DOC_GUID | = lv_iv_doc_guid | |
IV_COND_TYPE | = lv_iv_cond_type | |
IV_TERMNO | = lv_iv_termno | |
IV_VALIDFROM | = lv_iv_validfrom | |
IV_TERMTYPE | = lv_iv_termtype | |
IV_LANGU | = lv_iv_langu | |
IS_DOCUMENT_COM | = lv_is_document_com | |
IMPORTING | ||
ES_DEFTERM_USERFIELDS_COM | = lv_es_defterm_userfields_com | |
ET_INPUT_FIELDNAMES | = lv_et_input_fieldnames | |
EXCEPTIONS | ||
ERROR_OCCURRED = 1 | ||
. " CPE_DEFTERM_USERFIELDS_READ_OW |
ABAP code using 7.40 inline data declarations to call FM CPE_DEFTERM_USERFIELDS_READ_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."SELECT single LANGU FROM SY INTO @DATA(ld_iv_langu). | ||||
DATA(ld_iv_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects