SAP J_7L_FISCAL_YEAR_DATAB_DATBI Function Module for NOTRANSL: Berechnet die Periodengrenzen für eine Geschäftsjahresvariantenp

Search SAP Function Modules

J_7L_FISCAL_YEAR_DATAB_DATBI is a standard j 7l fiscal year datab datbi 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: Berechnet die Periodengrenzen für eine Geschäftsjahresvariantenp 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 fiscal year datab datbi FM, simply by entering the name J_7L_FISCAL_YEAR_DATAB_DATBI 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_FISCAL_YEAR_DATAB_DATBI 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_FISCAL_YEAR_DATAB_DATBI'"NOTRANSL: Berechnet die Periodengrenzen für eine Geschäftsjahresvariantenp
  EXPORTING
*  IN_BUKRS =  "
   IN_PERINR =  "
   IN_GJAHR =  "
*  IN_PERIV =  "Fiscal Year Variant

 IMPORTING
   O_DATAB =  "
   O_DATBI =  "
   O_PERIODENZAHL =  "
   O_GVARIANTE =  "

EXCEPTIONS
   KEINE_BUKRS_ZUORDNUNG = 1    VARIANTE_FALSCH_GEPFLEGT = 2    BUKRS_PERIV_NOT_SUPPLIED = 3 

.

IMPORTING Parameters details for J_7L_FISCAL_YEAR_DATAB_DATBI

IN_BUKRS -

Data type: J_7LMS-BUKRS
Optional: Yes
Call by Reference: Yes

IN_PERINR -

Data type: J_7LMS-PERINR
Optional: No
Call by Reference: Yes

IN_GJAHR -

Data type: J_7LMS-GJAHR
Optional: No
Call by Reference: Yes

IN_PERIV - Fiscal Year Variant

Data type: J_7LE09-PERIV
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for J_7L_FISCAL_YEAR_DATAB_DATBI

O_DATAB -

Data type: SY-DATUM
Optional: No
Call by Reference: Yes

O_DATBI -

Data type: SY-DATUM
Optional: No
Call by Reference: Yes

O_PERIODENZAHL -

Data type: T009-ANZBP
Optional: No
Call by Reference: Yes

O_GVARIANTE -

Data type: T009-PERIV
Optional: No
Call by Reference: Yes

EXCEPTIONS details

KEINE_BUKRS_ZUORDNUNG -

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

VARIANTE_FALSCH_GEPFLEGT -

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

BUKRS_PERIV_NOT_SUPPLIED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for J_7L_FISCAL_YEAR_DATAB_DATBI 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.

ABAP code using 7.40 inline data declarations to call FM J_7L_FISCAL_YEAR_DATAB_DATBI

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