SAP ISJP_CHECK_SELECTION Function Module for Check if a line item is candidate for invoice summary









ISJP_CHECK_SELECTION is a standard isjp check selection SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if a line item is candidate for invoice summary 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 isjp check selection FM, simply by entering the name ISJP_CHECK_SELECTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: ISJP_UTILITY
Program Name: SAPLISJP_UTILITY
Main Program: SAPLISJP_UTILITY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISJP_CHECK_SELECTION 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 'ISJP_CHECK_SELECTION'"Check if a line item is candidate for invoice summary
  EXPORTING
   IV_BUKRS =  "Selection of line items for Invoice Summary
*  IV_STBLG =  "Reverse Document Number
*  IV_CATEGORY =  "Set/Get parameter
*  IV_UMSKS =  "Special G/L Transaction Type
*  IV_BLART =  "Document type
*  IV_BSCHL =  "Posting Key
*  IV_UMSKZ =  "Special G/L Indicator
*  IV_KOART =  "Account type
*  IV_KUNNR =  "Customer Number 1
*  IV_LIFNR =  "Account Number of Vendor or Creditor
*  IV_BELNR =  "Assignment of Item Numbers: Material Doc. - Purchasing Doc.
*  IV_AUGBL =  "Document Number of the Clearing Document

 IMPORTING
   EV_CANDIDATE =  "Single-Character Flag
   EV_PAYER =  "Invoice Summary Payer
   EV_RECIPIENT =  "Invoice Summary Recipient
   EV_CUSTOMER =  "Customer Number 1
.



IMPORTING Parameters details for ISJP_CHECK_SELECTION

IV_BUKRS - Selection of line items for Invoice Summary

Data type: BUKRS
Optional: No
Call by Reference: Yes

IV_STBLG - Reverse Document Number

Data type: STBLG
Optional: Yes
Call by Reference: Yes

IV_CATEGORY - Set/Get parameter

Data type: CHAR_02
Optional: Yes
Call by Reference: Yes

IV_UMSKS - Special G/L Transaction Type

Data type: UMSKS
Optional: Yes
Call by Reference: Yes

IV_BLART - Document type

Data type: BLART
Optional: Yes
Call by Reference: Yes

IV_BSCHL - Posting Key

Data type: BSCHL
Optional: Yes
Call by Reference: Yes

IV_UMSKZ - Special G/L Indicator

Data type: UMSKZ
Optional: Yes
Call by Reference: Yes

IV_KOART - Account type

Data type: KOART
Optional: Yes
Call by Reference: Yes

IV_KUNNR - Customer Number 1

Data type: KUNNR
Optional: Yes
Call by Reference: Yes

IV_LIFNR - Account Number of Vendor or Creditor

Data type: LIFNR
Optional: Yes
Call by Reference: Yes

IV_BELNR - Assignment of Item Numbers: Material Doc. - Purchasing Doc.

Data type: BELNR_D
Optional: Yes
Call by Reference: Yes

IV_AUGBL - Document Number of the Clearing Document

Data type: AUGBL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISJP_CHECK_SELECTION

EV_CANDIDATE - Single-Character Flag

Data type: FLAG
Optional: No
Call by Reference: Yes

EV_PAYER - Invoice Summary Payer

Data type: ISJPINVSUMPAYER
Optional: No
Call by Reference: Yes

EV_RECIPIENT - Invoice Summary Recipient

Data type: ISJPINVSUMRECIP
Optional: No
Call by Reference: Yes

EV_CUSTOMER - Customer Number 1

Data type: KUNNR
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISJP_CHECK_SELECTION 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_iv_bukrs  TYPE BUKRS, "   
lv_ev_candidate  TYPE FLAG, "   
lv_iv_stblg  TYPE STBLG, "   
lv_iv_category  TYPE CHAR_02, "   
lv_iv_umsks  TYPE UMSKS, "   
lv_ev_payer  TYPE ISJPINVSUMPAYER, "   
lv_iv_blart  TYPE BLART, "   
lv_iv_bschl  TYPE BSCHL, "   
lv_ev_recipient  TYPE ISJPINVSUMRECIP, "   
lv_iv_umskz  TYPE UMSKZ, "   
lv_ev_customer  TYPE KUNNR, "   
lv_iv_koart  TYPE KOART, "   
lv_iv_kunnr  TYPE KUNNR, "   
lv_iv_lifnr  TYPE LIFNR, "   
lv_iv_belnr  TYPE BELNR_D, "   
lv_iv_augbl  TYPE AUGBL. "   

  CALL FUNCTION 'ISJP_CHECK_SELECTION'  "Check if a line item is candidate for invoice summary
    EXPORTING
         IV_BUKRS = lv_iv_bukrs
         IV_STBLG = lv_iv_stblg
         IV_CATEGORY = lv_iv_category
         IV_UMSKS = lv_iv_umsks
         IV_BLART = lv_iv_blart
         IV_BSCHL = lv_iv_bschl
         IV_UMSKZ = lv_iv_umskz
         IV_KOART = lv_iv_koart
         IV_KUNNR = lv_iv_kunnr
         IV_LIFNR = lv_iv_lifnr
         IV_BELNR = lv_iv_belnr
         IV_AUGBL = lv_iv_augbl
    IMPORTING
         EV_CANDIDATE = lv_ev_candidate
         EV_PAYER = lv_ev_payer
         EV_RECIPIENT = lv_ev_recipient
         EV_CUSTOMER = lv_ev_customer
. " ISJP_CHECK_SELECTION




ABAP code using 7.40 inline data declarations to call FM ISJP_CHECK_SELECTION

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!