SAP EXIT_SAPLJHA14_001 Function Module for IS-M: Payment Relevance for FD Update
EXIT_SAPLJHA14_001 is a standard exit sapljha14 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: Payment Relevance for FD Update 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 sapljha14 001 FM, simply by entering the name EXIT_SAPLJHA14_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJHA
Program Name: SAPLXJHA
Main Program: SAPLXJHA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLJHA14_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_SAPLJHA14_001'"IS-M: Payment Relevance for FD Update.
EXPORTING
PS_RJHAK = "
PS_RJHAP = "
PS_RJHAGA = "
CHANGING
PV_ORVALTYPE = "Value type of purchase order/sales order values
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISM_ACC_AVM_DOCUMENT_INPUT
IMPORTING Parameters details for EXIT_SAPLJHA14_001
PS_RJHAK -
Data type: JHA1_RJHAK_STROptional: No
Call by Reference: Yes
PS_RJHAP -
Data type: JHA1_RJHAP_STROptional: No
Call by Reference: Yes
PS_RJHAGA -
Data type: JHA1_RJHAGA_STROptional: No
Call by Reference: Yes
CHANGING Parameters details for EXIT_SAPLJHA14_001
PV_ORVALTYPE - Value type of purchase order/sales order values
Data type: ORVTPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLJHA14_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_ps_rjhak | TYPE JHA1_RJHAK_STR, " | |||
| lv_pv_orvaltype | TYPE ORVTP, " | |||
| lv_ps_rjhap | TYPE JHA1_RJHAP_STR, " | |||
| lv_ps_rjhaga | TYPE JHA1_RJHAGA_STR. " |
|   CALL FUNCTION 'EXIT_SAPLJHA14_001' "IS-M: Payment Relevance for FD Update |
| EXPORTING | ||
| PS_RJHAK | = lv_ps_rjhak | |
| PS_RJHAP | = lv_ps_rjhap | |
| PS_RJHAGA | = lv_ps_rjhaga | |
| CHANGING | ||
| PV_ORVALTYPE | = lv_pv_orvaltype | |
| . " EXIT_SAPLJHA14_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJHA14_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