SAP ISP_FI_CLEARING_DOCUMENT Function Module for
ISP_FI_CLEARING_DOCUMENT is a standard isp fi clearing document 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 clearing document FM, simply by entering the name ISP_FI_CLEARING_DOCUMENT 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): Normal Function Module
Update:
Function ISP_FI_CLEARING_DOCUMENT 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_CLEARING_DOCUMENT'".
EXPORTING
GPNR = "
DOCUMENT = "
CANCELLATION = "
BUKRS = "
WAERS = "
TABLES
BDCTAB = "
EXCEPTIONS
NO_DOCUMENT = 1 NO_CANCELLATION = 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_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_CLEARING_DOCUMENT
GPNR -
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
DOCUMENT -
Data type: JYPSDFI-BELNROptional: No
Call by Reference: No ( called with pass by value option)
CANCELLATION -
Data type: JYPSDFI-ISPSFAKTOptional: No
Call by Reference: No ( called with pass by value option)
BUKRS -
Data type: JYPSDFI-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
WAERS -
Data type: JYPSDFI-WAERSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_FI_CLEARING_DOCUMENT
BDCTAB -
Data type: BDCDATAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DOCUMENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CANCELLATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_FI_CLEARING_DOCUMENT 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_gpnr | TYPE KNA1-KUNNR, " | |||
lt_bdctab | TYPE STANDARD TABLE OF BDCDATA, " | |||
lv_no_document | TYPE BDCDATA, " | |||
lv_document | TYPE JYPSDFI-BELNR, " | |||
lv_no_cancellation | TYPE JYPSDFI, " | |||
lv_cancellation | TYPE JYPSDFI-ISPSFAKT, " | |||
lv_bukrs | TYPE JYPSDFI-BUKRS, " | |||
lv_waers | TYPE JYPSDFI-WAERS. " |
  CALL FUNCTION 'ISP_FI_CLEARING_DOCUMENT' " |
EXPORTING | ||
GPNR | = lv_gpnr | |
DOCUMENT | = lv_document | |
CANCELLATION | = lv_cancellation | |
BUKRS | = lv_bukrs | |
WAERS | = lv_waers | |
TABLES | ||
BDCTAB | = lt_bdctab | |
EXCEPTIONS | ||
NO_DOCUMENT = 1 | ||
NO_CANCELLATION = 2 | ||
. " ISP_FI_CLEARING_DOCUMENT |
ABAP code using 7.40 inline data declarations to call FM ISP_FI_CLEARING_DOCUMENT
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 KUNNR FROM KNA1 INTO @DATA(ld_gpnr). | ||||
"SELECT single BELNR FROM JYPSDFI INTO @DATA(ld_document). | ||||
"SELECT single ISPSFAKT FROM JYPSDFI INTO @DATA(ld_cancellation). | ||||
"SELECT single BUKRS FROM JYPSDFI INTO @DATA(ld_bukrs). | ||||
"SELECT single WAERS FROM JYPSDFI INTO @DATA(ld_waers). | ||||
Search for further information about these or an SAP related objects