SAP EXIT_SAPLJHAB_001 Function Module for IS-M: Update Customer-Specific Contract Data









EXIT_SAPLJHAB_001 is a standard exit sapljhab 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: Update Customer-Specific Contract Data 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 sapljhab 001 FM, simply by entering the name EXIT_SAPLJHAB_001 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLJHAB_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_SAPLJHAB_001'"IS-M: Update Customer-Specific Contract Data
EXPORTING
UPDATE_TASK = "Start update task?
COA_HEAD = "
COA_POS = "
PARTNERS = "
SALES_AREAS = "
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISMAM_COA_ADMGMTCOA_EXPORT
ISMAM_COA_CHANGED
ISMAM_COA_FORGET
ISMAM_COA_POST
ISMAM_COA_POST_MULTIPLE
ISMAM_COA_READ
ISMAM_COA_REFRESH
ISM_COA_CUST_DEQUEUE
ISM_COA_CUST_SET
ISM_COA_DONT_READ_PREPARE
ISP_JHTVB_DIRECT_READ
ISP_JHTVB_READ
ISP_JHTVB_READ_BUFFERED
ISP_JHTVB_READ_SINGLE
ISP_JHTVB_READ_WITH_POS
ISP_JHTVKO_DIRECT_READ
ISP_JHTVKO_INS_READ
ISP_JHTVKO_READ_WITH_POS
ISP_JHTVPO_READ

IMPORTING Parameters details for EXIT_SAPLJHAB_001

UPDATE_TASK - Start update task?

Data type: JPAM_XFELD_VAR
Optional: No
Call by Reference: Yes

COA_HEAD -

Data type: JHW1_HEAD_TAB
Optional: No
Call by Reference: Yes

COA_POS -

Data type: JHW1_POS_TAB
Optional: No
Call by Reference: Yes

PARTNERS -

Data type: JHW1_GPZ_TAB
Optional: No
Call by Reference: Yes

SALES_AREAS -

Data type: JHW1_VVB_TAB
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXIT_SAPLJHAB_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_update_task  TYPE JPAM_XFELD_VAR, "   
lv_coa_head  TYPE JHW1_HEAD_TAB, "   
lv_coa_pos  TYPE JHW1_POS_TAB, "   
lv_partners  TYPE JHW1_GPZ_TAB, "   
lv_sales_areas  TYPE JHW1_VVB_TAB. "   

  CALL FUNCTION 'EXIT_SAPLJHAB_001'  "IS-M: Update Customer-Specific Contract Data
    EXPORTING
         UPDATE_TASK = lv_update_task
         COA_HEAD = lv_coa_head
         COA_POS = lv_coa_pos
         PARTNERS = lv_partners
         SALES_AREAS = lv_sales_areas
. " EXIT_SAPLJHAB_001




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJHAB_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



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!