SAP ISP_INVOICE_DOCUMENT_ADD Function Module for IS-M/SD: Update Billing Documents









ISP_INVOICE_DOCUMENT_ADD is a standard isp invoice document add 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: Update Billing Documents 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 document add FM, simply by entering the name ISP_INVOICE_DOCUMENT_ADD 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_DOCUMENT_ADD 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_DOCUMENT_ADD'"IS-M/SD: Update Billing Documents
EXPORTING
* I_MSGID = 'JF' "
JFSK_I = "
* WITH_POSTING = ' ' "
TRTYP = "
VKORG = "
* I_WITH_COMMIT = 'X' "
* I_CCARD_RETURN = ' ' "

IMPORTING
JFSK_E = "

TABLES
XJFDFS = "Billing Index
* XJFFDICHT = "
* XJFRKCC = "
XKOMFK = "
XKOMFKGN = "
XKOMV = "Conditions
XTHEAD = "Texts
XJFFS = "Error Log
XJFPA = "
XJFRK = "Billing header
XJFRP = "Billing Item
.




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_DOCUMENT_ADD

I_MSGID -

Data type: JFFS-MSGID
Default: 'JF'
Optional: Yes
Call by Reference: No ( called with pass by value option)

JFSK_I -

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

WITH_POSTING -

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRTYP -

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

VKORG -

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

I_WITH_COMMIT -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CCARD_RETURN -

Data type: XFELD
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_INVOICE_DOCUMENT_ADD

JFSK_E -

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

TABLES Parameters details for ISP_INVOICE_DOCUMENT_ADD

XJFDFS - Billing Index

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

XJFFDICHT -

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

XJFRKCC -

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

XKOMFK -

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

XKOMFKGN -

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

XKOMV - Conditions

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

XTHEAD - Texts

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

XJFFS - Error Log

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

XJFPA -

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

XJFRK - Billing header

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

XJFRP - Billing Item

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

Copy and paste ABAP code example for ISP_INVOICE_DOCUMENT_ADD 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_jfsk_e  TYPE JFSK, "   
lt_xjfdfs  TYPE STANDARD TABLE OF JFDFSVB, "   
lv_i_msgid  TYPE JFFS-MSGID, "   'JF'
lt_xjffdicht  TYPE STANDARD TABLE OF JFFDIVB, "   
lt_xjfrkcc  TYPE STANDARD TABLE OF JFRKCCVB, "   
lv_jfsk_i  TYPE JFSK, "   
lt_xkomfk  TYPE STANDARD TABLE OF JKOMFK, "   
lt_xkomfkgn  TYPE STANDARD TABLE OF JF60_XKOMFKGN_TYPE, "   
lv_with_posting  TYPE XFELD, "   ' '
lv_trtyp  TYPE T180-TRTYP, "   
lt_xkomv  TYPE STANDARD TABLE OF KOMV, "   
lv_vkorg  TYPE JFRK-VKORG, "   
lt_xthead  TYPE STANDARD TABLE OF THEAD, "   
lt_xjffs  TYPE STANDARD TABLE OF JFFS, "   
lv_i_with_commit  TYPE XFELD, "   'X'
lt_xjfpa  TYPE STANDARD TABLE OF JFPAVB, "   
lv_i_ccard_return  TYPE XFELD, "   ' '
lt_xjfrk  TYPE STANDARD TABLE OF JFRKVB, "   
lt_xjfrp  TYPE STANDARD TABLE OF JFRPVB. "   

  CALL FUNCTION 'ISP_INVOICE_DOCUMENT_ADD'  "IS-M/SD: Update Billing Documents
    EXPORTING
         I_MSGID = lv_i_msgid
         JFSK_I = lv_jfsk_i
         WITH_POSTING = lv_with_posting
         TRTYP = lv_trtyp
         VKORG = lv_vkorg
         I_WITH_COMMIT = lv_i_with_commit
         I_CCARD_RETURN = lv_i_ccard_return
    IMPORTING
         JFSK_E = lv_jfsk_e
    TABLES
         XJFDFS = lt_xjfdfs
         XJFFDICHT = lt_xjffdicht
         XJFRKCC = lt_xjfrkcc
         XKOMFK = lt_xkomfk
         XKOMFKGN = lt_xkomfkgn
         XKOMV = lt_xkomv
         XTHEAD = lt_xthead
         XJFFS = lt_xjffs
         XJFPA = lt_xjfpa
         XJFRK = lt_xjfrk
         XJFRP = lt_xjfrp
. " ISP_INVOICE_DOCUMENT_ADD




ABAP code using 7.40 inline data declarations to call FM ISP_INVOICE_DOCUMENT_ADD

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 MSGID FROM JFFS INTO @DATA(ld_i_msgid).
DATA(ld_i_msgid) = 'JF'.
 
 
 
 
 
 
DATA(ld_with_posting) = ' '.
 
"SELECT single TRTYP FROM T180 INTO @DATA(ld_trtyp).
 
 
"SELECT single VKORG FROM JFRK INTO @DATA(ld_vkorg).
 
 
 
DATA(ld_i_with_commit) = 'X'.
 
 
DATA(ld_i_ccard_return) = ' '.
 
 
 


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!