SAP JIT13_READ_V_CJIT01D_ALL Function Module for NOTRANSL: Lesen des DB-Views V_CJIT01D (Abrufsteuerung)
JIT13_READ_V_CJIT01D_ALL is a standard jit13 read v cjit01d all 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: Lesen des DB-Views V_CJIT01D (Abrufsteuerung) 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 jit13 read v cjit01d all FM, simply by entering the name JIT13_READ_V_CJIT01D_ALL into the relevant SAP transaction such as SE37 or SE38.
Function Group: JIT13
Program Name: SAPLJIT13
Main Program: SAPLJIT13
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JIT13_READ_V_CJIT01D_ALL 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 'JIT13_READ_V_CJIT01D_ALL'"NOTRANSL: Lesen des DB-Views V_CJIT01D (Abrufsteuerung).
TABLES
V_CJIT01D_ET = "Generated Table for View
EXCEPTIONS
NO_RECORD_FOUND = 1
TABLES Parameters details for JIT13_READ_V_CJIT01D_ALL
V_CJIT01D_ET - Generated Table for View
Data type: V_CJIT01DOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_RECORD_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JIT13_READ_V_CJIT01D_ALL 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: | ||||
| lt_v_cjit01d_et | TYPE STANDARD TABLE OF V_CJIT01D, " | |||
| lv_no_record_found | TYPE V_CJIT01D. " |
|   CALL FUNCTION 'JIT13_READ_V_CJIT01D_ALL' "NOTRANSL: Lesen des DB-Views V_CJIT01D (Abrufsteuerung) |
| TABLES | ||
| V_CJIT01D_ET | = lt_v_cjit01d_et | |
| EXCEPTIONS | ||
| NO_RECORD_FOUND = 1 | ||
| . " JIT13_READ_V_CJIT01D_ALL | ||
ABAP code using 7.40 inline data declarations to call FM JIT13_READ_V_CJIT01D_ALL
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