SAP UPDATE_HISTORY_DATA Function Module for NOTRANSL: UPDATE HISTORY DATA
UPDATE_HISTORY_DATA is a standard update history data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: UPDATE HISTORY DATA 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 update history data FM, simply by entering the name UPDATE_HISTORY_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME07
Program Name: SAPLME07
Main Program: SAPLME07
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function UPDATE_HISTORY_DATA 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 'UPDATE_HISTORY_DATA'"NOTRANSL: UPDATE HISTORY DATA.
TABLES
PTY_EKBE = "
* PTY_EKBE_SUM = "
* PTY_EKBEH_SUM = "
* PTY_EKBE_MA = "History of Purchasing Document at Account Assignment Level
TABLES Parameters details for UPDATE_HISTORY_DATA
PTY_EKBE -
Data type: EKBEOptional: No
Call by Reference: Yes
PTY_EKBE_SUM -
Data type: EKBEOptional: Yes
Call by Reference: Yes
PTY_EKBEH_SUM -
Data type: EKBEHOptional: Yes
Call by Reference: Yes
PTY_EKBE_MA - History of Purchasing Document at Account Assignment Level
Data type: EKBE_MAOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for UPDATE_HISTORY_DATA 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_pty_ekbe | TYPE STANDARD TABLE OF EKBE, " | |||
| lt_pty_ekbe_sum | TYPE STANDARD TABLE OF EKBE, " | |||
| lt_pty_ekbeh_sum | TYPE STANDARD TABLE OF EKBEH, " | |||
| lt_pty_ekbe_ma | TYPE STANDARD TABLE OF EKBE_MA. " |
|   CALL FUNCTION 'UPDATE_HISTORY_DATA' "NOTRANSL: UPDATE HISTORY DATA |
| TABLES | ||
| PTY_EKBE | = lt_pty_ekbe | |
| PTY_EKBE_SUM | = lt_pty_ekbe_sum | |
| PTY_EKBEH_SUM | = lt_pty_ekbeh_sum | |
| PTY_EKBE_MA | = lt_pty_ekbe_ma | |
| . " UPDATE_HISTORY_DATA | ||
ABAP code using 7.40 inline data declarations to call FM UPDATE_HISTORY_DATA
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