SAP JIT14_CREATE_ALR_INPUT_SEQJIT Function Module for NOTRANSL: Alerts erzeugen bei Fehlern im IDOC-Eingang SEQJIT
JIT14_CREATE_ALR_INPUT_SEQJIT is a standard jit14 create alr input seqjit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Alerts erzeugen bei Fehlern im IDOC-Eingang SEQJIT 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 jit14 create alr input seqjit FM, simply by entering the name JIT14_CREATE_ALR_INPUT_SEQJIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JIT14
Program Name: SAPLJIT14
Main Program: SAPLJIT14
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JIT14_CREATE_ALR_INPUT_SEQJIT 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 'JIT14_CREATE_ALR_INPUT_SEQJIT'"NOTRANSL: Alerts erzeugen bei Fehlern im IDOC-Eingang SEQJIT.
EXPORTING
EDIDC_IS = "Control Record (IDoc)
* JITDIAHD_IS = "JIT : Dialog Structure for JITHD
* JITDIAPODEF_IS = "Default Data for Seq.JIT Items
* JIT_MSSG_RET_IS = "Transfer Structure for System Messages
IMPORTING
ALERT_ID_EV = "External ID for an Alert
JIT_MSSG_LOG_ES = "Message from JIT Inbound
EXCEPTIONS
ALERT_NOT_CREATED = 1
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_SAPLJIT14_001 JIT: Mapping the IDoc Data
EXIT_SAPLJIT14_002 Range Processing
IMPORTING Parameters details for JIT14_CREATE_ALR_INPUT_SEQJIT
EDIDC_IS - Control Record (IDoc)
Data type: EDIDCOptional: No
Call by Reference: Yes
JITDIAHD_IS - JIT : Dialog Structure for JITHD
Data type: JITDIAHDOptional: Yes
Call by Reference: Yes
JITDIAPODEF_IS - Default Data for Seq.JIT Items
Data type: JITDIAPODEFOptional: Yes
Call by Reference: Yes
JIT_MSSG_RET_IS - Transfer Structure for System Messages
Data type: MSSG_RETOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for JIT14_CREATE_ALR_INPUT_SEQJIT
ALERT_ID_EV - External ID for an Alert
Data type: SALRTEXTIDOptional: No
Call by Reference: Yes
JIT_MSSG_LOG_ES - Message from JIT Inbound
Data type: JIT_MSSG_LOGOptional: No
Call by Reference: Yes
EXCEPTIONS details
ALERT_NOT_CREATED - Alert Was Not Generated
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for JIT14_CREATE_ALR_INPUT_SEQJIT 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_edidc_is | TYPE EDIDC, " | |||
| lv_alert_id_ev | TYPE SALRTEXTID, " | |||
| lv_alert_not_created | TYPE SALRTEXTID, " | |||
| lv_jitdiahd_is | TYPE JITDIAHD, " | |||
| lv_jit_mssg_log_es | TYPE JIT_MSSG_LOG, " | |||
| lv_jitdiapodef_is | TYPE JITDIAPODEF, " | |||
| lv_jit_mssg_ret_is | TYPE MSSG_RET. " |
|   CALL FUNCTION 'JIT14_CREATE_ALR_INPUT_SEQJIT' "NOTRANSL: Alerts erzeugen bei Fehlern im IDOC-Eingang SEQJIT |
| EXPORTING | ||
| EDIDC_IS | = lv_edidc_is | |
| JITDIAHD_IS | = lv_jitdiahd_is | |
| JITDIAPODEF_IS | = lv_jitdiapodef_is | |
| JIT_MSSG_RET_IS | = lv_jit_mssg_ret_is | |
| IMPORTING | ||
| ALERT_ID_EV | = lv_alert_id_ev | |
| JIT_MSSG_LOG_ES | = lv_jit_mssg_log_es | |
| EXCEPTIONS | ||
| ALERT_NOT_CREATED = 1 | ||
| . " JIT14_CREATE_ALR_INPUT_SEQJIT | ||
ABAP code using 7.40 inline data declarations to call FM JIT14_CREATE_ALR_INPUT_SEQJIT
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