SAP BBP_TOLERANCE_CHECK_VALIDITY Function Module for Toleranzprüfung Gültigkeitszeitraum









BBP_TOLERANCE_CHECK_VALIDITY is a standard bbp tolerance check validity SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Toleranzprüfung Gültigkeitszeitraum 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 bbp tolerance check validity FM, simply by entering the name BBP_TOLERANCE_CHECK_VALIDITY into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_TOLERANCE_CHECK_VALIDITY 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 'BBP_TOLERANCE_CHECK_VALIDITY'"Toleranzprüfung Gültigkeitszeitraum
EXPORTING
I_TOL_GROUP = "Toleranz Gruppe
I_TOL_KEY = "Toleranzschluessel
I_POSTING_DATE = "Belegdatum (Buchungsdatum des Logistik-Geschäftsvorgangs)
I_VALIDITY_FROM = "Belegdatum (Buchungsdatum des Logistik-Geschäftsvorgangs)
I_VALIDITY_TO = "Belegdatum (Buchungsdatum des Logistik-Geschäftsvorgangs)
* I_USE_MESSAGE_LOG = "'X': write messages also in log
* IV_MESSAGE_TYPE = 'E' "Type der Fehlermeldung

IMPORTING
E_RETURNCODE = "Rückgabewert, Rückgabewert nach ABAP-Anweisungen

TABLES
* E_MESSAGES = "Fehlermeldungen zu einer PD-Methode
.



IMPORTING Parameters details for BBP_TOLERANCE_CHECK_VALIDITY

I_TOL_GROUP - Toleranz Gruppe

Data type: BBP_TOL_GROUP
Optional: No
Call by Reference: Yes

I_TOL_KEY - Toleranzschluessel

Data type: BBP_TOLERANCE_KEY
Optional: No
Call by Reference: Yes

I_POSTING_DATE - Belegdatum (Buchungsdatum des Logistik-Geschäftsvorgangs)

Data type: BBP_POSTING_DATE
Optional: No
Call by Reference: Yes

I_VALIDITY_FROM - Belegdatum (Buchungsdatum des Logistik-Geschäftsvorgangs)

Data type: BBP_POSTING_DATE
Optional: No
Call by Reference: Yes

I_VALIDITY_TO - Belegdatum (Buchungsdatum des Logistik-Geschäftsvorgangs)

Data type: BBP_POSTING_DATE
Optional: No
Call by Reference: Yes

I_USE_MESSAGE_LOG - 'X': write messages also in log

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IV_MESSAGE_TYPE - Type der Fehlermeldung

Data type: SYMSGTY
Default: 'E'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BBP_TOLERANCE_CHECK_VALIDITY

E_RETURNCODE - Rückgabewert, Rückgabewert nach ABAP-Anweisungen

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

TABLES Parameters details for BBP_TOLERANCE_CHECK_VALIDITY

E_MESSAGES - Fehlermeldungen zu einer PD-Methode

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

Copy and paste ABAP code example for BBP_TOLERANCE_CHECK_VALIDITY 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:
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_tol_group  TYPE BBP_TOL_GROUP, "   
lv_e_returncode  TYPE SY-SUBRC, "   
lv_i_tol_key  TYPE BBP_TOLERANCE_KEY, "   
lv_i_posting_date  TYPE BBP_POSTING_DATE, "   
lv_i_validity_from  TYPE BBP_POSTING_DATE, "   
lv_i_validity_to  TYPE BBP_POSTING_DATE, "   
lv_i_use_message_log  TYPE XFELD, "   
lv_iv_message_type  TYPE SYMSGTY. "   'E'

  CALL FUNCTION 'BBP_TOLERANCE_CHECK_VALIDITY'  "Toleranzprüfung Gültigkeitszeitraum
    EXPORTING
         I_TOL_GROUP = lv_i_tol_group
         I_TOL_KEY = lv_i_tol_key
         I_POSTING_DATE = lv_i_posting_date
         I_VALIDITY_FROM = lv_i_validity_from
         I_VALIDITY_TO = lv_i_validity_to
         I_USE_MESSAGE_LOG = lv_i_use_message_log
         IV_MESSAGE_TYPE = lv_iv_message_type
    IMPORTING
         E_RETURNCODE = lv_e_returncode
    TABLES
         E_MESSAGES = lt_e_messages
. " BBP_TOLERANCE_CHECK_VALIDITY




ABAP code using 7.40 inline data declarations to call FM BBP_TOLERANCE_CHECK_VALIDITY

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 SUBRC FROM SY INTO @DATA(ld_e_returncode).
 
 
 
 
 
 
DATA(ld_iv_message_type) = 'E'.
 


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!