SAP J_7L_READ_CONSECUTIVE_DOC_DATA Function Module for NOTRANSL: Liest Positionen zum Beleg aus der DB in eine transiente Datenst
J_7L_READ_CONSECUTIVE_DOC_DATA is a standard j 7l read consecutive doc data 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: Liest Positionen zum Beleg aus der DB in eine transiente Datenst 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 j 7l read consecutive doc data FM, simply by entering the name J_7L_READ_CONSECUTIVE_DOC_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: J7LD
Program Name: SAPLJ7LD
Main Program: SAPLJ7LD
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_7L_READ_CONSECUTIVE_DOC_DATA 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 'J_7L_READ_CONSECUTIVE_DOC_DATA'"NOTRANSL: Liest Positionen zum Beleg aus der DB in eine transiente Datenst.
EXPORTING
IN_VBELN = "REA Declaration: Document Number
TABLES
O_J7LV1A = "REA Document: Consecutive Document Types for Main Doc. Type
EXCEPTIONS
BELEG_NICHT_GEFUNDEN = 1
IMPORTING Parameters details for J_7L_READ_CONSECUTIVE_DOC_DATA
IN_VBELN - REA Declaration: Document Number
Data type: J_7LV1P-VBELNOptional: No
Call by Reference: Yes
TABLES Parameters details for J_7L_READ_CONSECUTIVE_DOC_DATA
O_J7LV1A - REA Document: Consecutive Document Types for Main Doc. Type
Data type: J_7LV1AOptional: No
Call by Reference: Yes
EXCEPTIONS details
BELEG_NICHT_GEFUNDEN - 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 J_7L_READ_CONSECUTIVE_DOC_DATA 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_in_vbeln | TYPE J_7LV1P-VBELN, " | |||
| lt_o_j7lv1a | TYPE STANDARD TABLE OF J_7LV1A, " | |||
| lv_beleg_nicht_gefunden | TYPE J_7LV1A. " |
|   CALL FUNCTION 'J_7L_READ_CONSECUTIVE_DOC_DATA' "NOTRANSL: Liest Positionen zum Beleg aus der DB in eine transiente Datenst |
| EXPORTING | ||
| IN_VBELN | = lv_in_vbeln | |
| TABLES | ||
| O_J7LV1A | = lt_o_j7lt1a | |
| EXCEPTIONS | ||
| BELEG_NICHT_GEFUNDEN = 1 | ||
| . " J_7L_READ_CONSECUTIVE_DOC_DATA | ||
ABAP code using 7.40 inline data declarations to call FM J_7L_READ_CONSECUTIVE_DOC_DATA
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.| "SELECT single VBELN FROM J_7LV1P INTO @DATA(ld_in_vbeln). | ||||
Search for further information about these or an SAP related objects