SAP FERC_LOG_WRITE Function Module for IS-U/FERC: Write log entries for FERC step execution

Search SAP Function Modules

FERC_LOG_WRITE is a standard ferc log write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U/FERC: Write log entries for FERC step execution 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 log write FM, simply by entering the name FERC_LOG_WRITE 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_LOG_WRITE 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_LOG_WRITE'"IS-U/FERC: Write log entries for FERC step execution
  EXPORTING
   RUN_ID =  "
*  DD_DIR =  "
*  DD_TRC =  "
   RECORD_TYPE =  "
   FERC_STEP =  "
   RUN_NO =  "
   STATUS =  "
*  ARCHIVE_SESSION =  "
*  REVERSAL =  "
*  TEST_LOG =  "
*  EXPORT_MESSAGES =  "

EXCEPTIONS
   SYSTEM_ERROR = 1    PARAMETERS_NOT_INITIALIZED = 2 

.

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_LOG_WRITE

RUN_ID -

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

DD_DIR -

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

DD_TRC -

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

RECORD_TYPE -

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

FERC_STEP -

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

RUN_NO -

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

STATUS -

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

ARCHIVE_SESSION -

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

REVERSAL -

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

TEST_LOG -

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

EXPORT_MESSAGES -

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

EXCEPTIONS details

SYSTEM_ERROR -

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

PARAMETERS_NOT_INITIALIZED -

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

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

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