SAP BU_CHANGE_NUMBER_READ Function Module for









BU_CHANGE_NUMBER_READ is a standard bu change number read 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 bu change number read FM, simply by entering the name BU_CHANGE_NUMBER_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function BU_CHANGE_NUMBER_READ 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 'BU_CHANGE_NUMBER_READ'"
EXPORTING
* I_AENNR = "

IMPORTING
O_AENR = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for BU_CHANGE_NUMBER_READ

I_AENNR -

Data type: AENR-AENNR
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BU_CHANGE_NUMBER_READ

O_AENR -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for BU_CHANGE_NUMBER_READ 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_o_aenr  TYPE AENR, "   
lv_i_aennr  TYPE AENR-AENNR, "   
lv_not_found  TYPE AENR. "   

  CALL FUNCTION 'BU_CHANGE_NUMBER_READ'  "
    EXPORTING
         I_AENNR = lv_i_aennr
    IMPORTING
         O_AENR = lv_o_aenr
    EXCEPTIONS
        NOT_FOUND = 1
. " BU_CHANGE_NUMBER_READ




ABAP code using 7.40 inline data declarations to call FM BU_CHANGE_NUMBER_READ

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 AENNR FROM AENR INTO @DATA(ld_i_aennr).
 
 


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!