SAP CEV3_HELP_ORIGIN Function Module for NOTRANSL: Hilfe zum Feld Parameterherkunft









CEV3_HELP_ORIGIN is a standard cev3 help origin SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Hilfe zum Feld Parameterherkunft 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 cev3 help origin FM, simply by entering the name CEV3_HELP_ORIGIN into the relevant SAP transaction such as SE37 or SE38.

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



Function CEV3_HELP_ORIGIN 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 'CEV3_HELP_ORIGIN'"NOTRANSL: Hilfe zum Feld Parameterherkunft
EXPORTING
* ORIGIN = ' ' "Origin (formula or table)
* ORIGIN2 = ' ' "Table field
* ORIGIN_KEY = ' ' "Origin key
* PARAMETER_NAME = ' ' "Parameter name
* TOP_FORMULA = ' ' "Higher-level formula (may not be replaced)
* PARAMETER_BEZEICHNUNG = ' ' "

IMPORTING
FLG_ESC = "X if F12 abnormal termination
ORIGIN = "Origin (formula or table)
ORIGIN2 = "Table field
ORIGIN_KEY = "Origin key

EXCEPTIONS
ORIGIN_KEY_WRONG = 1
.



IMPORTING Parameters details for CEV3_HELP_ORIGIN

ORIGIN - Origin (formula or table)

Data type: RCEVF-PAHER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ORIGIN2 - Table field

Data type: RCEVF-PAHE2
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ORIGIN_KEY - Origin key

Data type: RCEVF-PAHSC
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARAMETER_NAME - Parameter name

Data type: RCEVF-ATNAM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TOP_FORMULA - Higher-level formula (may not be replaced)

Data type: VFORK-FOMNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARAMETER_BEZEICHNUNG -

Data type: CABNT-ATBEZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CEV3_HELP_ORIGIN

FLG_ESC - X if F12 abnormal termination

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

ORIGIN - Origin (formula or table)

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

ORIGIN2 - Table field

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

ORIGIN_KEY - Origin key

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

EXCEPTIONS details

ORIGIN_KEY_WRONG - Origin key is incorrect

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

Copy and paste ABAP code example for CEV3_HELP_ORIGIN 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_origin  TYPE RCEVF-PAHER, "   SPACE
lv_flg_esc  TYPE RCEVF, "   
lv_origin_key_wrong  TYPE RCEVF, "   
lv_origin  TYPE RCEVF-PAHER, "   
lv_origin2  TYPE RCEVF-PAHE2, "   SPACE
lv_origin2  TYPE RCEVF-PAHE2, "   
lv_origin_key  TYPE RCEVF-PAHSC, "   SPACE
lv_origin_key  TYPE RCEVF-PAHSC, "   
lv_parameter_name  TYPE RCEVF-ATNAM, "   SPACE
lv_top_formula  TYPE VFORK-FOMNR, "   SPACE
lv_parameter_bezeichnung  TYPE CABNT-ATBEZ. "   SPACE

  CALL FUNCTION 'CEV3_HELP_ORIGIN'  "NOTRANSL: Hilfe zum Feld Parameterherkunft
    EXPORTING
         ORIGIN = lv_origin
         ORIGIN2 = lv_origin2
         ORIGIN_KEY = lv_origin_key
         PARAMETER_NAME = lv_parameter_name
         TOP_FORMULA = lv_top_formula
         PARAMETER_BEZEICHNUNG = lv_parameter_bezeichnung
    IMPORTING
         FLG_ESC = lv_flg_esc
         ORIGIN = lv_origin
         ORIGIN2 = lv_origin2
         ORIGIN_KEY = lv_origin_key
    EXCEPTIONS
        ORIGIN_KEY_WRONG = 1
. " CEV3_HELP_ORIGIN




ABAP code using 7.40 inline data declarations to call FM CEV3_HELP_ORIGIN

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 PAHER FROM RCEVF INTO @DATA(ld_origin).
DATA(ld_origin) = ' '.
 
 
 
"SELECT single PAHER FROM RCEVF INTO @DATA(ld_origin).
 
"SELECT single PAHE2 FROM RCEVF INTO @DATA(ld_origin2).
DATA(ld_origin2) = ' '.
 
"SELECT single PAHE2 FROM RCEVF INTO @DATA(ld_origin2).
 
"SELECT single PAHSC FROM RCEVF INTO @DATA(ld_origin_key).
DATA(ld_origin_key) = ' '.
 
"SELECT single PAHSC FROM RCEVF INTO @DATA(ld_origin_key).
 
"SELECT single ATNAM FROM RCEVF INTO @DATA(ld_parameter_name).
DATA(ld_parameter_name) = ' '.
 
"SELECT single FOMNR FROM VFORK INTO @DATA(ld_top_formula).
DATA(ld_top_formula) = ' '.
 
"SELECT single ATBEZ FROM CABNT INTO @DATA(ld_parameter_bezeichnung).
DATA(ld_parameter_bezeichnung) = ' '.
 


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!