SAP EXIT_SAPLJHAG_001 Function Module for IS-M/AM: Fill Billing Interface - Order-Related
EXIT_SAPLJHAG_001 is a standard exit sapljhag 001 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: Fill Billing Interface - Order-Related 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 exit sapljhag 001 FM, simply by entering the name EXIT_SAPLJHAG_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJHF
Program Name: SAPLXJHF
Main Program: SAPLXJHF
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLJHAG_001 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 'EXIT_SAPLJHAG_001'"IS-M/AM: Fill Billing Interface - Order-Related.
EXPORTING
IN_XKOMV_ITAB = "Conditions
* IN_RJHAPP = "Package Item
IN_RJHAGA = "Billing dataset
IN_RJHAGPZ_ITAB = "Business partner assignment (order)
IN_RJHAE_ITAB = "Selected schedule lines (for all orders)
IN_RJHAEA_ITAB = "Selected schedule lines (for all orders)
IN_RJHAES_ITAB = "Selected schedule lines (for all orders)
IN_RJHAEW_ITAB = "Selected schedule lines (for all orders)
IN_RJHAEV_ITAB = "Selected schedule lines (for all orders)
IN_RJHAEO_ITAB = "Selected schedule lines (for all orders)
IN_KOMK = "Communication Header for Pricing
IN_RJHAK = "Order header
IN_KOMP = "Pricing communication item
IN_RJHKOMFKG = "Billing interface record SAP
IN_RJHAP = "Order item
IN_RJHAPA = "Ad item
IN_RJHAPD = "Service item
IN_RJHAPS = "Ad insert item
IN_RJHAPW = "Commercial item
IN_RJHAPV = "Benefit Split Item
IN_RJHAPO = "Online Item
IMPORTING
OUT_RJHKOMFKG = "Billing interface record changed
EXCEPTIONS
SKIP_ENTRY = 1
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISMAM_CCARD_ORDER_AUTHORIZE IS-M/AM: Payment Cards: Batch Authorization of Orders
ISMAM_ORDER_ENQUEUE IS-M/AM: Lock Order
ISMAM_ORDER_GVX_COMMISSION IS-M/AM: Update Sales Agent Settlement Index from Sales Agent Settlement
ISMAM_ORDER_GVX_INVOICE IS-M/AM: Update Sales Agent Settlement Index from Billing Document
ISMAM_ORDER_MEMORY_RJH_IMPORT IS-M/AM: Import R-Tables for ISP_ORDER_UPDATE_FROM_BILLING
ISM_ORDER_BILLING_MEMORY_EXPRT IS-M: Export Global Tables for ISP_ORDER_READ_FOR_BILLING
ISM_ORDER_BILLING_MEMORY_IMPRT IS-M: Import Global Tables for ISP_ORDER_READ_FOR_BILLING
ISPAM_AVM_PRICING_COPY_INVOICE IS-M/AM: Access Function Module ISPAM_PRICING_COPY
ISPAM_BULK_CHANGE_CURRENCY IS-M/AM: Mass Change for Order
ISP_AVM_ROLLE_AUS_GPZ IS-M/AM: Determine Role from OPM Business Partner Assignment
ISP_ORDER_BILLING_MEMORY_INIT IS-M/AM: Init Global Memory from Func.Mod. ISP_ORDER_READ_FOR_BILLING_CPY
ISP_ORDER_BILLING_MEMORY_UPD IS-M/AM: Update Global Memory for FuBa ISP_ORDER_READ_FOR_BILLING_CPY
ISP_ORDER_GA_STR_GET IS-M/AM: Read Billing Dataset from Order Environment
ISP_ORDER_GVX_STR_GET IS-M/AM: Read Sales Agent Settlement Index from Order Environment
ISP_ORDER_GVX_STR_SET IS-M/AM: Change Sales Agent Settlement Index from Order Environment
ISP_ORDER_GVZ_STR_GET IS-M/AM: Read Sales Agent Assignment from Order Environment
ISP_ORDER_PA_STR_GET IS-M/AM: Read Ad Item from Order Environment
ISP_ORDER_READ_FOR_BILLING IS-M/AM: Create Order Environment for Billing Document
ISP_ORDER_UPDATE_FROM_BILLING IS-M/AM: Update Order for Billing Document
IMPORTING Parameters details for EXIT_SAPLJHAG_001
IN_XKOMV_ITAB - Conditions
Data type: JHF1_XKOMV_TABOptional: No
Call by Reference: Yes
IN_RJHAPP - Package Item
Data type: JHA1_RJHAPP_STROptional: Yes
Call by Reference: No ( called with pass by value option)
IN_RJHAGA - Billing dataset
Data type: JHA1_RJHAGA_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAGPZ_ITAB - Business partner assignment (order)
Data type: JHA1_RJHAGPZ_TABOptional: No
Call by Reference: Yes
IN_RJHAE_ITAB - Selected schedule lines (for all orders)
Data type: JHA1_RJHAE_TABOptional: No
Call by Reference: Yes
IN_RJHAEA_ITAB - Selected schedule lines (for all orders)
Data type: JHA1_RJHAEA_TABOptional: No
Call by Reference: Yes
IN_RJHAES_ITAB - Selected schedule lines (for all orders)
Data type: JHA1_RJHAES_TABOptional: No
Call by Reference: Yes
IN_RJHAEW_ITAB - Selected schedule lines (for all orders)
Data type: JHA1_RJHAEW_TABOptional: No
Call by Reference: Yes
IN_RJHAEV_ITAB - Selected schedule lines (for all orders)
Data type: JHA1_RJHAEV_TABOptional: No
Call by Reference: Yes
IN_RJHAEO_ITAB - Selected schedule lines (for all orders)
Data type: JHA1_RJHAEO_TABOptional: No
Call by Reference: Yes
IN_KOMK - Communication Header for Pricing
Data type: KOMKOptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAK - Order header
Data type: JHA1_RJHAK_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_KOMP - Pricing communication item
Data type: KOMPOptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHKOMFKG - Billing interface record SAP
Data type: RJHKOMFKGOptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAP - Order item
Data type: JHA1_RJHAP_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAPA - Ad item
Data type: JHA1_RJHAPA_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAPD - Service item
Data type: JHA1_RJHAPD_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAPS - Ad insert item
Data type: JHA1_RJHAPS_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAPW - Commercial item
Data type: JHA1_RJHAPW_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAPV - Benefit Split Item
Data type: JHA1_RJHAPV_STROptional: No
Call by Reference: No ( called with pass by value option)
IN_RJHAPO - Online Item
Data type: JHA1_RJHAPO_STROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLJHAG_001
OUT_RJHKOMFKG - Billing interface record changed
Data type: RJHKOMFKGOptional: No
Call by Reference: Yes
EXCEPTIONS details
SKIP_ENTRY - Skip interface record
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLJHAG_001 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_skip_entry | TYPE STRING, " | |||
lv_in_xkomv_itab | TYPE JHF1_XKOMV_TAB, " | |||
lv_out_rjhkomfkg | TYPE RJHKOMFKG, " | |||
lv_in_rjhapp | TYPE JHA1_RJHAPP_STR, " | |||
lv_in_rjhaga | TYPE JHA1_RJHAGA_STR, " | |||
lv_in_rjhagpz_itab | TYPE JHA1_RJHAGPZ_TAB, " | |||
lv_in_rjhae_itab | TYPE JHA1_RJHAE_TAB, " | |||
lv_in_rjhaea_itab | TYPE JHA1_RJHAEA_TAB, " | |||
lv_in_rjhaes_itab | TYPE JHA1_RJHAES_TAB, " | |||
lv_in_rjhaew_itab | TYPE JHA1_RJHAEW_TAB, " | |||
lv_in_rjhaev_itab | TYPE JHA1_RJHAEV_TAB, " | |||
lv_in_rjhaeo_itab | TYPE JHA1_RJHAEO_TAB, " | |||
lv_in_komk | TYPE KOMK, " | |||
lv_in_rjhak | TYPE JHA1_RJHAK_STR, " | |||
lv_in_komp | TYPE KOMP, " | |||
lv_in_rjhkomfkg | TYPE RJHKOMFKG, " | |||
lv_in_rjhap | TYPE JHA1_RJHAP_STR, " | |||
lv_in_rjhapa | TYPE JHA1_RJHAPA_STR, " | |||
lv_in_rjhapd | TYPE JHA1_RJHAPD_STR, " | |||
lv_in_rjhaps | TYPE JHA1_RJHAPS_STR, " | |||
lv_in_rjhapw | TYPE JHA1_RJHAPW_STR, " | |||
lv_in_rjhapv | TYPE JHA1_RJHAPV_STR, " | |||
lv_in_rjhapo | TYPE JHA1_RJHAPO_STR. " |
  CALL FUNCTION 'EXIT_SAPLJHAG_001' "IS-M/AM: Fill Billing Interface - Order-Related |
EXPORTING | ||
IN_XKOMV_ITAB | = lv_in_xkomv_itab | |
IN_RJHAPP | = lv_in_rjhapp | |
IN_RJHAGA | = lv_in_rjhaga | |
IN_RJHAGPZ_ITAB | = lv_in_rjhagpz_itab | |
IN_RJHAE_ITAB | = lv_in_rjhae_itab | |
IN_RJHAEA_ITAB | = lv_in_rjhaea_itab | |
IN_RJHAES_ITAB | = lv_in_rjhaes_itab | |
IN_RJHAEW_ITAB | = lv_in_rjhaew_itab | |
IN_RJHAEV_ITAB | = lv_in_rjhaev_itab | |
IN_RJHAEO_ITAB | = lv_in_rjhaeo_itab | |
IN_KOMK | = lv_in_komk | |
IN_RJHAK | = lv_in_rjhak | |
IN_KOMP | = lv_in_komp | |
IN_RJHKOMFKG | = lv_in_rjhkomfkg | |
IN_RJHAP | = lv_in_rjhap | |
IN_RJHAPA | = lv_in_rjhapa | |
IN_RJHAPD | = lv_in_rjhapd | |
IN_RJHAPS | = lv_in_rjhaps | |
IN_RJHAPW | = lv_in_rjhapw | |
IN_RJHAPV | = lv_in_rjhapv | |
IN_RJHAPO | = lv_in_rjhapo | |
IMPORTING | ||
OUT_RJHKOMFKG | = lv_out_rjhkomfkg | |
EXCEPTIONS | ||
SKIP_ENTRY = 1 | ||
. " EXIT_SAPLJHAG_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJHAG_001
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