SAP ISMAM_RR_BILLING Function Module for IS-M/AM: RR: Billing Document
ISMAM_RR_BILLING is a standard ismam rr billing 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/AM: RR: Billing Document 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 ismam rr billing FM, simply by entering the name ISMAM_RR_BILLING into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHER
Program Name: SAPLJHER
Main Program: SAPLJHER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISMAM_RR_BILLING 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 'ISMAM_RR_BILLING'"IS-M/AM: RR: Billing Document.
EXPORTING
PS_JHTFK = "
PT_JHTFP = "IS-M/AM: Billing/Settlement Documents - Item
PV_VBELN = "IS-M: Billing / Settlement Document
PV_VBELN_VF = "Billing Documents
PV_POSNR = "Accounting Document Line Item Number
CHANGING
PT_XACCIT = "
PT_XACCCR = "
PT_XKOMV = "
PT_XACCHD = "
PT_RR_XACCIT = "
PT_RR_XACCCR = "
EXCEPTIONS
NO_POSTING = 1 NEW_ACCOUNT = 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_SAPLJHER_001 IS-M/AM: Billing SD Number Assignment
EXIT_SAPLJHER_002 IS-M/AM: Order: SD Number Range Interval
EXIT_SAPLJHER_003 IS-M/AM: Order G/L Account Determination
IMPORTING Parameters details for ISMAM_RR_BILLING
PS_JHTFK -
Data type: JHF1_JHTFK_STROptional: No
Call by Reference: Yes
PT_JHTFP - IS-M/AM: Billing/Settlement Documents - Item
Data type: JHF1_JHTFP_TABOptional: No
Call by Reference: Yes
PV_VBELN - IS-M: Billing / Settlement Document
Data type: JHTFK-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
PV_VBELN_VF - Billing Documents
Data type: VBELN_VFOptional: No
Call by Reference: No ( called with pass by value option)
PV_POSNR - Accounting Document Line Item Number
Data type: ACCIT-POSNROptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISMAM_RR_BILLING
PT_XACCIT -
Data type: JHF1_XACCIT_TABOptional: No
Call by Reference: Yes
PT_XACCCR -
Data type: JHF1_XACCCR_TABOptional: No
Call by Reference: Yes
PT_XKOMV -
Data type: JHF1_XKOMV_TABOptional: No
Call by Reference: Yes
PT_XACCHD -
Data type: JHF1_XACCHD_TABOptional: No
Call by Reference: Yes
PT_RR_XACCIT -
Data type: JHF1_XACCIT_TABOptional: No
Call by Reference: Yes
PT_RR_XACCCR -
Data type: JHF1_XACCCR_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_POSTING -
Data type:Optional: No
Call by Reference: Yes
NEW_ACCOUNT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISMAM_RR_BILLING 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_ps_jhtfk | TYPE JHF1_JHTFK_STR, " | |||
| lv_pt_xaccit | TYPE JHF1_XACCIT_TAB, " | |||
| lv_no_posting | TYPE JHF1_XACCIT_TAB, " | |||
| lv_pt_jhtfp | TYPE JHF1_JHTFP_TAB, " | |||
| lv_pt_xacccr | TYPE JHF1_XACCCR_TAB, " | |||
| lv_new_account | TYPE JHF1_XACCCR_TAB, " | |||
| lv_pt_xkomv | TYPE JHF1_XKOMV_TAB, " | |||
| lv_pv_vbeln | TYPE JHTFK-VBELN, " | |||
| lv_pt_xacchd | TYPE JHF1_XACCHD_TAB, " | |||
| lv_pv_vbeln_vf | TYPE VBELN_VF, " | |||
| lv_pv_posnr | TYPE ACCIT-POSNR, " | |||
| lv_pt_rr_xaccit | TYPE JHF1_XACCIT_TAB, " | |||
| lv_pt_rr_xacccr | TYPE JHF1_XACCCR_TAB. " |
|   CALL FUNCTION 'ISMAM_RR_BILLING' "IS-M/AM: RR: Billing Document |
| EXPORTING | ||
| PS_JHTFK | = lv_ps_jhtfk | |
| PT_JHTFP | = lv_pt_jhtfp | |
| PV_VBELN | = lv_pv_vbeln | |
| PV_VBELN_VF | = lv_pv_vbeln_vf | |
| PV_POSNR | = lv_pv_posnr | |
| CHANGING | ||
| PT_XACCIT | = lv_pt_xaccit | |
| PT_XACCCR | = lv_pt_xacccr | |
| PT_XKOMV | = lv_pt_xkomv | |
| PT_XACCHD | = lv_pt_xacchd | |
| PT_RR_XACCIT | = lv_pt_rr_xaccit | |
| PT_RR_XACCCR | = lv_pt_rr_xacccr | |
| EXCEPTIONS | ||
| NO_POSTING = 1 | ||
| NEW_ACCOUNT = 2 | ||
| . " ISMAM_RR_BILLING | ||
ABAP code using 7.40 inline data declarations to call FM ISMAM_RR_BILLING
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 VBELN FROM JHTFK INTO @DATA(ld_pv_vbeln). | ||||
| "SELECT single POSNR FROM ACCIT INTO @DATA(ld_pv_posnr). | ||||
Search for further information about these or an SAP related objects