SAP ISM_UPDATE_COLL_BILLING_RUN Function Module for IS-M/SD: Update Collective Runs After Billing Document Transfer









ISM_UPDATE_COLL_BILLING_RUN is a standard ism update coll billing run 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 Collective Runs After Billing Document Transfer 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 ism update coll billing run FM, simply by entering the name ISM_UPDATE_COLL_BILLING_RUN into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_UPDATE_COLL_BILLING_RUN 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 'ISM_UPDATE_COLL_BILLING_RUN'"IS-M/SD: Update Collective Runs After Billing Document Transfer
EXPORTING
I_EVENT = "
* I_XSETTLEMENT = "
I_SAMMG_TAB = "
.




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_SAPLJF23_001 IS-M/SD: Billing Document Transfer - Header Data
EXIT_SAPLJF23_002 IS-M/SD: Billing Document Transfer - Tax Line
EXIT_SAPLJF23_003 IS-M/SD: Billing Document Transfer - G/L Account Line
EXIT_SAPLJF23_004 IS-M/SD: Billing Document Transfer - Provisions
EXIT_SAPLJF23_005 IS-M/SD: Billing Transfer - Payment Card Line
EXIT_SAPLJF23_006 IS-M/SD: Billing Transfer - Sub-Ledger Account Line (Accounts Receivable)
EXIT_SAPLJF23_007 IS-M/SD: Billing Transfer - Document
EXIT_SAPLJF23_008 IS-M/SD: Billing Document Transfer - General Ledger Account Posting
EXIT_SAPLJF23_009 IS-M/SD: Revenue Accrual Transfer - Document
EXIT_SAPLJF23_010 IS-M/SD: Contract Postings at End of Liability Account Cycle
EXIT_SAPLJF23_011 IS-M/SD: Determine CO Order for Closure of Del.-Related Liability Acct
EXIT_SAPLJF23_012 IS-M/SD: User Exit for Billing Doc.Transfer - Split Criteria Cust.Line

IMPORTING Parameters details for ISM_UPDATE_COLL_BILLING_RUN

I_EVENT -

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

I_XSETTLEMENT -

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

I_SAMMG_TAB -

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

Copy and paste ABAP code example for ISM_UPDATE_COLL_BILLING_RUN 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_i_event  TYPE TJU01-EVENT, "   
lv_i_xsettlement  TYPE JF23_XFIELD, "   
lv_i_sammg_tab  TYPE JF23_SAMMG_TAB. "   

  CALL FUNCTION 'ISM_UPDATE_COLL_BILLING_RUN'  "IS-M/SD: Update Collective Runs After Billing Document Transfer
    EXPORTING
         I_EVENT = lv_i_event
         I_XSETTLEMENT = lv_i_xsettlement
         I_SAMMG_TAB = lv_i_sammg_tab
. " ISM_UPDATE_COLL_BILLING_RUN




ABAP code using 7.40 inline data declarations to call FM ISM_UPDATE_COLL_BILLING_RUN

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 EVENT FROM TJU01 INTO @DATA(ld_i_event).
 
 
 


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!