SAP BP_CHECK_REPORT_VALUES Function Module for

Search SAP Function Modules

BP_CHECK_REPORT_VALUES is a standard bp check report values SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bp check report values FM, simply by entering the name BP_CHECK_REPORT_VALUES into the relevant SAP transaction such as SE37 or SE38.

Function Group: BTCH
Program Name: SAPLBTCH
Main Program: SAPLBTCH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BP_CHECK_REPORT_VALUES 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 'BP_CHECK_REPORT_VALUES'"
  EXPORTING
   CHECK_TYPE =  "Type of check: check report / report + variant
   CHKRP_DIALOG =  "Online mode (yes = BTC_YES / no = BTC_NO )
   REPORT_NAME =  "report name to be checked
*  VARIANT_NAME = ' ' "Variant to be checked or selected online
*  NO_AUTH_CHECK =  "

 IMPORTING
   VARIANT_NAME =  "Variant to be checked or selected online

EXCEPTIONS
   INVALID_CHECK_TYPE = 1    VARIANT_CHECK_HAS_FAILED = 10    VARIANT_NAME_MISSING = 11    VARIANT_SELECTION_ABORTED = 12    INVALID_DIALOG_TYPE = 2    INVALID_REPORT_NAME = 3    INVALID_VARIANT_NAME = 4    NO_PLAN_AUTHORITY = 5    NO_VARIANTS_DEFINED = 6    REPORT_CAN_NOT_BE_SCHEDULED = 7    REPORT_HAS_NO_VARIANTS = 8    REPORT_NAME_MISSING = 9 

.

IMPORTING Parameters details for BP_CHECK_REPORT_VALUES

CHECK_TYPE - Type of check: check report / report + variant

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

CHKRP_DIALOG - Online mode (yes = BTC_YES / no = BTC_NO )

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

REPORT_NAME - report name to be checked

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

VARIANT_NAME - Variant to be checked or selected online

Data type: RALDB-VARIANT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_AUTH_CHECK -

Data type: BTCH0000-CHAR1
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BP_CHECK_REPORT_VALUES

VARIANT_NAME - Variant to be checked or selected online

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

EXCEPTIONS details

INVALID_CHECK_TYPE - Check category is invalid (see notes)

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

VARIANT_CHECK_HAS_FAILED - Variant check failed due to internal error

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

VARIANT_NAME_MISSING - Variant specification is missing

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

VARIANT_SELECTION_ABORTED - online variant choice cancelled

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

INVALID_DIALOG_TYPE - Interactive category is invalid

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

INVALID_REPORT_NAME - Report name is invalid

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

INVALID_VARIANT_NAME - Variant name is invalid

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

NO_PLAN_AUTHORITY - User must not plan report as a background job

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

NO_VARIANTS_DEFINED - no variants were defined up to now

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

REPORT_CAN_NOT_BE_SCHEDULED - Report cannot be planned as background job

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

REPORT_HAS_NO_VARIANTS - Report has no variants

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

REPORT_NAME_MISSING - Report specification is missing

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

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

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