SAP ISP_INVOICE_INDEX_CREATE Function Module for IS-M/SD: Determine Index Data for Billing









ISP_INVOICE_INDEX_CREATE is a standard isp invoice index create 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-M/SD: Determine Index Data for Billing 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 isp invoice index create FM, simply by entering the name ISP_INVOICE_INDEX_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_INVOICE_INDEX_CREATE 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_INVOICE_INDEX_CREATE'"IS-M/SD: Determine Index Data for Billing
EXPORTING
XINDEX = "
XJFDFSI = "

IMPORTING
XJFDFSE = "

EXCEPTIONS
NO_BEGINN_DATE = 1 NO_DATE = 2 NO_END_DATE = 3 NO_FUNCTION = 4 NO_GPNR = 5 NO_GPNR_NAME = 6
.




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_SAPLJF60_001 IS-M/SD: Sort Billing Items
EXIT_SAPLJF60_002 IS-M/SD: New Partners for Billing (New Roles)
EXIT_SAPLJF60_003 IS-M/SD: Modify Fields for Pricing (Header Fields)
EXIT_SAPLJF60_004 IS-M/SD: Modify Fields for Pricing (Item Fields)
EXIT_SAPLJF60_005 IS-M/SD: Determine Alternative Number Range for Billing Document
EXIT_SAPLJF60_006 IS-M/SD: Modify Fields for Account Determination (Header Fields)
EXIT_SAPLJF60_007 IS-M/SD: Modify Fields for Account Determination (Item Fields)
EXIT_SAPLJF60_009 IS-M/SD: User Exit for Summarizing Billing Items
EXIT_SAPLJF60_010 IS-M/SD: Determine Field Collector in Billing
EXIT_SAPLJF60_011 IS-M/SD: User Exits for Header/Item Data for Billing Interface
EXIT_SAPLJF60_012 IS-M/SD: Preparation for Postponing Billing
EXIT_SAPLJF60_013 IS-M/SD: Postpone Billing Due to Suspension
EXIT_SAPLJF60_014 IS-M/SD: Postpone Billing Due to Undershoot of Minimum Amount
EXIT_SAPLJF60_015 IS-M/SD: Influence Billing Date in Billing Index
EXIT_SAPLJF60_016 IS-M/SD: Influence Recalculation Date in Billing Index
EXIT_SAPLJF60_017 IS-M/SD: Item Split Due to Price Change in Delivery Subscription
EXIT_SAPLJF60_018

IMPORTING Parameters details for ISP_INVOICE_INDEX_CREATE

XINDEX -

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

XJFDFSI -

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

EXPORTING Parameters details for ISP_INVOICE_INDEX_CREATE

XJFDFSE -

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

EXCEPTIONS details

NO_BEGINN_DATE -

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

NO_DATE -

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

NO_END_DATE -

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

NO_FUNCTION -

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

NO_GPNR -

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

NO_GPNR_NAME -

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

Copy and paste ABAP code example for ISP_INVOICE_INDEX_CREATE 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_xindex  TYPE RJFINDEX, "   
lv_xjfdfse  TYPE JFDFSVB, "   
lv_no_beginn_date  TYPE JFDFSVB, "   
lv_no_date  TYPE JFDFSVB, "   
lv_xjfdfsi  TYPE JFDFSVB, "   
lv_no_end_date  TYPE JFDFSVB, "   
lv_no_function  TYPE JFDFSVB, "   
lv_no_gpnr  TYPE JFDFSVB, "   
lv_no_gpnr_name  TYPE JFDFSVB. "   

  CALL FUNCTION 'ISP_INVOICE_INDEX_CREATE'  "IS-M/SD: Determine Index Data for Billing
    EXPORTING
         XINDEX = lv_xindex
         XJFDFSI = lv_xjfdfsi
    IMPORTING
         XJFDFSE = lv_xjfdfse
    EXCEPTIONS
        NO_BEGINN_DATE = 1
        NO_DATE = 2
        NO_END_DATE = 3
        NO_FUNCTION = 4
        NO_GPNR = 5
        NO_GPNR_NAME = 6
. " ISP_INVOICE_INDEX_CREATE




ABAP code using 7.40 inline data declarations to call FM ISP_INVOICE_INDEX_CREATE

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!