SAP CEV4_PROCESS_IN_TECHNOLOGY Function Module for NOTRANSL: Verfahrenszuordnung für Technologie

Search SAP Function Modules

CEV4_PROCESS_IN_TECHNOLOGY is a standard cev4 process in technology 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: Verfahrenszuordnung für Technologie 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 cev4 process in technology FM, simply by entering the name CEV4_PROCESS_IN_TECHNOLOGY into the relevant SAP transaction such as SE37 or SE38.

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

Function CEV4_PROCESS_IN_TECHNOLOGY 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 'CEV4_PROCESS_IN_TECHNOLOGY'"NOTRANSL: Verfahrenszuordnung für Technologie
  EXPORTING
*  ACTIVITY_TYPE = 'A' "Activity type (H, V, A)
*  ARBPL = ' ' "Work center
*  FIRST_TIME_IMP = 'X' "FM used for the first time
*  KTEXT = ' ' "
*  OBJID = 0 "Object ID
*  RCR01_IMP = ' ' "
*  WERKS = ' ' "Plant

 IMPORTING
   CHANGED =  "Data was changed
   FCODE =  "Returned OK code
   FIRST_TIME_EXP =  "
   PROCESS_LINES =  "Number of allocated procedure

EXCEPTIONS
   NOT_EXPECTED_ACTIVITY = 1    NO_LINES_TO_SHOW = 2    NO_OBJID = 3 

.

IMPORTING Parameters details for CEV4_PROCESS_IN_TECHNOLOGY

ACTIVITY_TYPE - Activity type (H, V, A)

Data type: TC10-TRTYP
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARBPL - Work center

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

FIRST_TIME_IMP - FM used for the first time

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

KTEXT -

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

OBJID - Object ID

Data type: CRHD-OBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

RCR01_IMP -

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

WERKS - Plant

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

EXPORTING Parameters details for CEV4_PROCESS_IN_TECHNOLOGY

CHANGED - Data was changed

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

FCODE - Returned OK code

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

FIRST_TIME_EXP -

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

PROCESS_LINES - Number of allocated procedure

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

EXCEPTIONS details

NOT_EXPECTED_ACTIVITY - unknown activity type

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

NO_LINES_TO_SHOW - Display selected, but no lines exist

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

NO_OBJID - Object ID not entered

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

Copy and paste ABAP code example for CEV4_PROCESS_IN_TECHNOLOGY 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.

ABAP code using 7.40 inline data declarations to call FM CEV4_PROCESS_IN_TECHNOLOGY

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