SAP GJ_BILLING_EXTRACT_READ Function Module for Read billing extract into internal table









GJ_BILLING_EXTRACT_READ is a standard gj billing extract read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read billing extract into internal table 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 gj billing extract read FM, simply by entering the name GJ_BILLING_EXTRACT_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: GJRP
Program Name: SAPLGJRP
Main Program: SAPLGJRP
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GJ_BILLING_EXTRACT_READ 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 'GJ_BILLING_EXTRACT_READ'"Read billing extract into internal table
EXPORTING
RBUKRS = "Company code
RJVNAM = "Joint venture
REGROU = "Equity group
FUNDCURR = "Funding currency
REP_YEAR = "Reporting year
REP_PERIOD = "Reporting period
EXTRACT_TYPE = "Extract type (hard copy / EDI)

TABLES
I_T8JVEXTR = "Table with extract data for reporting

EXCEPTIONS
EXTRACT_NOT_FOUND = 1
.



IMPORTING Parameters details for GJ_BILLING_EXTRACT_READ

RBUKRS - Company code

Data type: T8JVEXTR-RBUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

RJVNAM - Joint venture

Data type: T8JVEXTR-RJVNAM
Optional: No
Call by Reference: No ( called with pass by value option)

REGROU - Equity group

Data type: T8JVEXTR-REGROU
Optional: No
Call by Reference: No ( called with pass by value option)

FUNDCURR - Funding currency

Data type: T8JVEXTR-FUNDCURR
Optional: No
Call by Reference: No ( called with pass by value option)

REP_YEAR - Reporting year

Data type: T8JVEXTR-REP_YEAR
Optional: No
Call by Reference: No ( called with pass by value option)

REP_PERIOD - Reporting period

Data type: T8JVEXTR-REP_PERIOD
Optional: No
Call by Reference: No ( called with pass by value option)

EXTRACT_TYPE - Extract type (hard copy / EDI)

Data type: T8JVEXTR-XTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GJ_BILLING_EXTRACT_READ

I_T8JVEXTR - Table with extract data for reporting

Data type: T8JVEXTR
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

EXTRACT_NOT_FOUND - Extract not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for GJ_BILLING_EXTRACT_READ 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_rbukrs  TYPE T8JVEXTR-RBUKRS, "   
lt_i_t8jvextr  TYPE STANDARD TABLE OF T8JVEXTR, "   
lv_extract_not_found  TYPE T8JVEXTR, "   
lv_rjvnam  TYPE T8JVEXTR-RJVNAM, "   
lv_regrou  TYPE T8JVEXTR-REGROU, "   
lv_fundcurr  TYPE T8JVEXTR-FUNDCURR, "   
lv_rep_year  TYPE T8JVEXTR-REP_YEAR, "   
lv_rep_period  TYPE T8JVEXTR-REP_PERIOD, "   
lv_extract_type  TYPE T8JVEXTR-XTYPE. "   

  CALL FUNCTION 'GJ_BILLING_EXTRACT_READ'  "Read billing extract into internal table
    EXPORTING
         RBUKRS = lv_rbukrs
         RJVNAM = lv_rjvnam
         REGROU = lv_regrou
         FUNDCURR = lv_fundcurr
         REP_YEAR = lv_rep_year
         REP_PERIOD = lv_rep_period
         EXTRACT_TYPE = lv_extract_type
    TABLES
         I_T8JVEXTR = lt_i_t8jvextr
    EXCEPTIONS
        EXTRACT_NOT_FOUND = 1
. " GJ_BILLING_EXTRACT_READ




ABAP code using 7.40 inline data declarations to call FM GJ_BILLING_EXTRACT_READ

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 RBUKRS FROM T8JVEXTR INTO @DATA(ld_rbukrs).
 
 
 
"SELECT single RJVNAM FROM T8JVEXTR INTO @DATA(ld_rjvnam).
 
"SELECT single REGROU FROM T8JVEXTR INTO @DATA(ld_regrou).
 
"SELECT single FUNDCURR FROM T8JVEXTR INTO @DATA(ld_fundcurr).
 
"SELECT single REP_YEAR FROM T8JVEXTR INTO @DATA(ld_rep_year).
 
"SELECT single REP_PERIOD FROM T8JVEXTR INTO @DATA(ld_rep_period).
 
"SELECT single XTYPE FROM T8JVEXTR INTO @DATA(ld_extract_type).
 


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!