SAP ISU_CHECK_FUTURE_BP_CHANGES Function Module for Checks Whether Changes Exist in Future

Search SAP Function Modules

ISU_CHECK_FUTURE_BP_CHANGES is a standard isu check future bp changes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks Whether Changes Exist in Future 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 check future bp changes FM, simply by entering the name ISU_CHECK_FUTURE_BP_CHANGES into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_CHECK_FUTURE_BP_CHANGES 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_CHECK_FUTURE_BP_CHANGES'"Checks Whether Changes Exist in Future
  EXPORTING
   X_PARTNER =  "Business Partner Number
*  X_OBJ =  "

 IMPORTING
   Y_FUTURE_CHANGES =  "

EXCEPTIONS
   NOT_FOUND = 1    GENERAL_FAULT = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLES01_001 Duplicate Check: Business Partner
EXIT_SAPLES01_030 Before PBO Customer Subscreen
EXIT_SAPLES01_031 After PAI Customer Subscreen

IMPORTING Parameters details for ISU_CHECK_FUTURE_BP_CHANGES

X_PARTNER - Business Partner Number

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

X_OBJ -

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

EXPORTING Parameters details for ISU_CHECK_FUTURE_BP_CHANGES

Y_FUTURE_CHANGES -

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

EXCEPTIONS details

NOT_FOUND - Partner does not exist

Data type:
Optional: No
Call by Reference: Yes

GENERAL_FAULT - General Error

Data type:
Optional: No
Call by Reference: Yes

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

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