SAP CNV_TDMS_01_FIND_ACTIVE_OC Function Module for For finding the active operating concerns
CNV_TDMS_01_FIND_ACTIVE_OC is a standard cnv tdms 01 find active oc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for For finding the active operating concerns 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 cnv tdms 01 find active oc FM, simply by entering the name CNV_TDMS_01_FIND_ACTIVE_OC into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_TDMS_01_SCEN_X
Program Name: SAPLCNV_TDMS_01_SCEN_X
Main Program: SAPLCNV_TDMS_01_SCEN_X
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function CNV_TDMS_01_FIND_ACTIVE_OC 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 'CNV_TDMS_01_FIND_ACTIVE_OC'"For finding the active operating concerns.
TABLES
LT_ERKRS = "Controlling Areas
EXCEPTIONS
SYSTEM_FAILURE = 1 COMMUNICATION_FAILURE = 2
TABLES Parameters details for CNV_TDMS_01_FIND_ACTIVE_OC
LT_ERKRS - Controlling Areas
Data type: CNVTDMS_01_PERIOOptional: No
Call by Reference: Yes
EXCEPTIONS details
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_TDMS_01_FIND_ACTIVE_OC 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: | ||||
lt_lt_erkrs | TYPE STANDARD TABLE OF CNVTDMS_01_PERIO, " | |||
lv_system_failure | TYPE CNVTDMS_01_PERIO, " | |||
lv_communication_failure | TYPE CNVTDMS_01_PERIO. " |
  CALL FUNCTION 'CNV_TDMS_01_FIND_ACTIVE_OC' "For finding the active operating concerns |
TABLES | ||
LT_ERKRS | = lt_lt_erkrs | |
EXCEPTIONS | ||
SYSTEM_FAILURE = 1 | ||
COMMUNICATION_FAILURE = 2 | ||
. " CNV_TDMS_01_FIND_ACTIVE_OC |
ABAP code using 7.40 inline data declarations to call FM CNV_TDMS_01_FIND_ACTIVE_OC
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