SAP CPE_TERMCONVIN_MAINTAIN_MUL_OW Function Module for CPE_D - Term Conversion Input - Maintain Object Work Area
CPE_TERMCONVIN_MAINTAIN_MUL_OW is a standard cpe termconvin maintain mul 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 - Term Conversion Input - Maintain 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 termconvin maintain mul ow FM, simply by entering the name CPE_TERMCONVIN_MAINTAIN_MUL_OW into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_TERMCONVIN_OW
Program Name: SAPLCPE_TERMCONVIN_OW
Main Program: SAPLCPE_TERMCONVIN_OW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CPE_TERMCONVIN_MAINTAIN_MUL_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_TERMCONVIN_MAINTAIN_MUL_OW'"CPE_D - Term Conversion Input - Maintain Object Work Area.
EXPORTING
IT_TERMCONVIN_COM = "CPE - Communication Table for Term Conversion Input
* IV_PERFORM_CHECK = 'X' "Single-character flag
IT_CHANGED_FIELDNAMES = "CPE - Names of changed fields
IS_DOCUMENT_COM = "CPE: Communication Structure with Document Fields
IV_VALIDFROM = "CPE - 'Valid From' Time Stamp of Commodity Pricing Object
* IT_CHANGED_CONVIN = "CPE - Communication Table for Changed Conversion Input Keys
IMPORTING
ET_MSG_COM = "CPE - Log: Communication Table for Messages
ET_TERMCONVIN_COM = "CPE - Communication Table for Input for Term Conversion
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for CPE_TERMCONVIN_MAINTAIN_MUL_OW
IT_TERMCONVIN_COM - CPE - Communication Table for Term Conversion Input
Data type: CPET_TERMCONVIN_COM_TABOptional: No
Call by Reference: Yes
IV_PERFORM_CHECK - Single-character flag
Data type: CHAR1Default: 'X'
Optional: No
Call by Reference: Yes
IT_CHANGED_FIELDNAMES - CPE - Names of changed fields
Data type: CPET_CHANGED_FIELDNAMES_TABOptional: No
Call by Reference: Yes
IS_DOCUMENT_COM - CPE: Communication Structure with Document Fields
Data type: CPET_DOCUMENT_COMOptional: No
Call by Reference: Yes
IV_VALIDFROM - CPE - 'Valid From' Time Stamp of Commodity Pricing Object
Data type: CPET_VALIDFROMOptional: No
Call by Reference: Yes
IT_CHANGED_CONVIN - CPE - Communication Table for Changed Conversion Input Keys
Data type: CPET_CHANGED_CONVIN_KEY_TABOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CPE_TERMCONVIN_MAINTAIN_MUL_OW
ET_MSG_COM - CPE - Log: Communication Table for Messages
Data type: CPET_MSG_COM_TABOptional: No
Call by Reference: Yes
ET_TERMCONVIN_COM - CPE - Communication Table for Input for Term Conversion
Data type: CPET_TERMCONVIN_COM_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CPE_TERMCONVIN_MAINTAIN_MUL_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_et_msg_com | TYPE CPET_MSG_COM_TAB, " | |||
| lv_error_occurred | TYPE CPET_MSG_COM_TAB, " | |||
| lv_it_termconvin_com | TYPE CPET_TERMCONVIN_COM_TAB, " | |||
| lv_iv_perform_check | TYPE CHAR1, " 'X' | |||
| lv_et_termconvin_com | TYPE CPET_TERMCONVIN_COM_TAB, " | |||
| lv_it_changed_fieldnames | TYPE CPET_CHANGED_FIELDNAMES_TAB, " | |||
| lv_is_document_com | TYPE CPET_DOCUMENT_COM, " | |||
| lv_iv_validfrom | TYPE CPET_VALIDFROM, " | |||
| lv_it_changed_convin | TYPE CPET_CHANGED_CONVIN_KEY_TAB. " |
|   CALL FUNCTION 'CPE_TERMCONVIN_MAINTAIN_MUL_OW' "CPE_D - Term Conversion Input - Maintain Object Work Area |
| EXPORTING | ||
| IT_TERMCONVIN_COM | = lv_it_termconvin_com | |
| IV_PERFORM_CHECK | = lv_iv_perform_check | |
| IT_CHANGED_FIELDNAMES | = lv_it_changed_fieldnames | |
| IS_DOCUMENT_COM | = lv_is_document_com | |
| IV_VALIDFROM | = lv_iv_validfrom | |
| IT_CHANGED_CONVIN | = lv_it_changed_convin | |
| IMPORTING | ||
| ET_MSG_COM | = lv_et_msg_com | |
| ET_TERMCONVIN_COM | = lv_et_termconvin_com | |
| EXCEPTIONS | ||
| ERROR_OCCURRED = 1 | ||
| . " CPE_TERMCONVIN_MAINTAIN_MUL_OW | ||
ABAP code using 7.40 inline data declarations to call FM CPE_TERMCONVIN_MAINTAIN_MUL_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.| DATA(ld_iv_perform_check) | = 'X'. | |||
Search for further information about these or an SAP related objects