SAP ISP_FI_JOURNAL Function Module for

Search SAP Function Modules

ISP_FI_JOURNAL is a standard isp fi journal SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 isp fi journal FM, simply by entering the name ISP_FI_JOURNAL into the relevant SAP transaction such as SE37 or SE38.

Function Group: JF80
Program Name: SAPLJF80
Main Program: SAPLJF80
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ISP_FI_JOURNAL 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 'ISP_FI_JOURNAL'"
  EXPORTING
   BUKRS =  "
   UEBDT =  "
   UEBNR =  "

TABLES
   XBKPF =  "
   XBSEG =  "

.

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_SAPLJF80_002 IS-M/SD: User Fields for Screen 002 - Revenue Dist. IS-M/SD -> FI
EXIT_SAPLJF80_100 IS-M/SD: User Fields for Screen 100 - Revenue Dist. IS-M/SD -> FI
EXIT_SAPLJF80_106 IS-M/SD: User Fields for Screen 106 - Revenue Dist. IS-M/SD -> FI
EXIT_SAPLJF80_300 IS-M/SD: User Fields for Screen 300 - Revenue Dist. IS-M/SD -> FI
EXIT_SAPLJF80_500 IS-M/SD: User Fields for Screen 100 - Billing Post. IS-M/SD -> FI
EXIT_SAPLJF80_502 IS-M/SD: User Fields for Screen 002 - Billing Post. IS-M/SD -> FI
EXIT_SAPLJF80_900 IS-M/SD: User Fields for Screen 300 - Billing Posting IS-M/SD -> FI
EXIT_SAPLJF80_901 IS-M/SD: User Fields for Screen 301 - Billing Posting IS-M/SD -> FI
EXIT_SAPLJF80_902 IS-M/SD: User Fields for Screen 302 - Billing Posting IS-M/SD -> FI
EXIT_SAPLJF80_912 IS-M/SD: User Fields for Screen 312 - Billing Posting IS-M/SD -> FI

IMPORTING Parameters details for ISP_FI_JOURNAL

BUKRS -

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

UEBDT -

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

UEBNR -

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

TABLES Parameters details for ISP_FI_JOURNAL

XBKPF -

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

XBSEG -

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

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

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