SAP ISU_END_OF_BACKBI_PERIOD_CHECK Function Module for INTERNAL: Check Whether End of Backbilling Period is Reached
ISU_END_OF_BACKBI_PERIOD_CHECK is a standard isu end of backbi period check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Check Whether End of Backbilling Period is Reached 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 isu end of backbi period check FM, simply by entering the name ISU_END_OF_BACKBI_PERIOD_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: EAUT
Program Name: SAPLEAUT
Main Program: SAPLEAUT
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_END_OF_BACKBI_PERIOD_CHECK 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 'ISU_END_OF_BACKBI_PERIOD_CHECK'"INTERNAL: Check Whether End of Backbilling Period is Reached.
EXPORTING
X_END_OF_FIRST_PERIOD = "
X_END_OF_PERIOD = "
X_PERIOD_LENGTH = "
X_PERIOD_LENGTH_D = "Period length in days
X_PERIOD_TYPE = "
X_NUMBER_OF_PERIODS = "
IMPORTING
Y_BBP_END = "
EXCEPTIONS
PARAMETER_FAULT = 1
IMPORTING Parameters details for ISU_END_OF_BACKBI_PERIOD_CHECK
X_END_OF_FIRST_PERIOD -
Data type: TE420-TERMERSTOptional: No
Call by Reference: No ( called with pass by value option)
X_END_OF_PERIOD -
Data type: TE417-TERMTDATOptional: No
Call by Reference: No ( called with pass by value option)
X_PERIOD_LENGTH -
Data type: TE420-PERIODEWOptional: No
Call by Reference: No ( called with pass by value option)
X_PERIOD_LENGTH_D - Period length in days
Data type: TE420-PERIODEDOptional: No
Call by Reference: No ( called with pass by value option)
X_PERIOD_TYPE -
Data type: TE420-PERIODETOptional: No
Call by Reference: No ( called with pass by value option)
X_NUMBER_OF_PERIODS -
Data type: ETTA-NUMPERBBOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_END_OF_BACKBI_PERIOD_CHECK
Y_BBP_END -
Data type: REGEN-KENNZXOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_END_OF_BACKBI_PERIOD_CHECK 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_y_bbp_end | TYPE REGEN-KENNZX, " | |||
| lv_parameter_fault | TYPE REGEN, " | |||
| lv_x_end_of_first_period | TYPE TE420-TERMERST, " | |||
| lv_x_end_of_period | TYPE TE417-TERMTDAT, " | |||
| lv_x_period_length | TYPE TE420-PERIODEW, " | |||
| lv_x_period_length_d | TYPE TE420-PERIODED, " | |||
| lv_x_period_type | TYPE TE420-PERIODET, " | |||
| lv_x_number_of_periods | TYPE ETTA-NUMPERBB. " |
|   CALL FUNCTION 'ISU_END_OF_BACKBI_PERIOD_CHECK' "INTERNAL: Check Whether End of Backbilling Period is Reached |
| EXPORTING | ||
| X_END_OF_FIRST_PERIOD | = lv_x_end_of_first_period | |
| X_END_OF_PERIOD | = lv_x_end_of_period | |
| X_PERIOD_LENGTH | = lv_x_period_length | |
| X_PERIOD_LENGTH_D | = lv_x_period_length_d | |
| X_PERIOD_TYPE | = lv_x_period_type | |
| X_NUMBER_OF_PERIODS | = lv_x_number_of_periods | |
| IMPORTING | ||
| Y_BBP_END | = lv_y_bbp_end | |
| EXCEPTIONS | ||
| PARAMETER_FAULT = 1 | ||
| . " ISU_END_OF_BACKBI_PERIOD_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISU_END_OF_BACKBI_PERIOD_CHECK
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 KENNZX FROM REGEN INTO @DATA(ld_y_bbp_end). | ||||
| "SELECT single TERMERST FROM TE420 INTO @DATA(ld_x_end_of_first_period). | ||||
| "SELECT single TERMTDAT FROM TE417 INTO @DATA(ld_x_end_of_period). | ||||
| "SELECT single PERIODEW FROM TE420 INTO @DATA(ld_x_period_length). | ||||
| "SELECT single PERIODED FROM TE420 INTO @DATA(ld_x_period_length_d). | ||||
| "SELECT single PERIODET FROM TE420 INTO @DATA(ld_x_period_type). | ||||
| "SELECT single NUMPERBB FROM ETTA INTO @DATA(ld_x_number_of_periods). | ||||
Search for further information about these or an SAP related objects