SAP FERC_COST_ELEMENT_CHECK Function Module for Determine the cost element type
FERC_COST_ELEMENT_CHECK is a standard ferc cost element check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine the cost element type 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 ferc cost element check FM, simply by entering the name FERC_COST_ELEMENT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FE01
Program Name: SAPLFE01
Main Program: SAPLFE01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FERC_COST_ELEMENT_CHECK 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 'FERC_COST_ELEMENT_CHECK'"Determine the cost element type.
EXPORTING
CONTROLLING_AREA = "
COST_ELEMENT = "
IMPORTING
COST_ELEMENT_TYPE = "Cost element category
COST_ACCOUNTING_TYPE = "Cost accounting type
EXCEPTIONS
NO_COST_ELEMENT = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLFE01_001 Determine regulatory indicator or specify as clearing object
EXIT_SAPLFE01_002 Specific standard cost adjustment order and cost element of cost center
EXIT_SAPLFE01_004 Check if posting to G/L account is possible
IMPORTING Parameters details for FERC_COST_ELEMENT_CHECK
CONTROLLING_AREA -
Data type: CSKB-KOKRSOptional: No
Call by Reference: No ( called with pass by value option)
COST_ELEMENT -
Data type: CSKB-KSTAROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FERC_COST_ELEMENT_CHECK
COST_ELEMENT_TYPE - Cost element category
Data type: KATYPOptional: No
Call by Reference: No ( called with pass by value option)
COST_ACCOUNTING_TYPE - Cost accounting type
Data type: KOTYPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_COST_ELEMENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FERC_COST_ELEMENT_CHECK 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_no_cost_element | TYPE STRING, " | |||
| lv_controlling_area | TYPE CSKB-KOKRS, " | |||
| lv_cost_element_type | TYPE KATYP, " | |||
| lv_cost_element | TYPE CSKB-KSTAR, " | |||
| lv_cost_accounting_type | TYPE KOTYP. " |
|   CALL FUNCTION 'FERC_COST_ELEMENT_CHECK' "Determine the cost element type |
| EXPORTING | ||
| CONTROLLING_AREA | = lv_controlling_area | |
| COST_ELEMENT | = lv_cost_element | |
| IMPORTING | ||
| COST_ELEMENT_TYPE | = lv_cost_element_type | |
| COST_ACCOUNTING_TYPE | = lv_cost_accounting_type | |
| EXCEPTIONS | ||
| NO_COST_ELEMENT = 1 | ||
| . " FERC_COST_ELEMENT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FERC_COST_ELEMENT_CHECK
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 KOKRS FROM CSKB INTO @DATA(ld_controlling_area). | ||||
| "SELECT single KSTAR FROM CSKB INTO @DATA(ld_cost_element). | ||||
Search for further information about these or an SAP related objects