SAP BUX_CONVERT_TECHNICAL_DATA Function Module for Return of Historical Data for a Business Object

Search SAP Function Modules

BUX_CONVERT_TECHNICAL_DATA is a standard bux convert technical 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 Return of Historical Data for a Business Object 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 bux convert technical data FM, simply by entering the name BUX_CONVERT_TECHNICAL_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function BUX_CONVERT_TECHNICAL_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 'BUX_CONVERT_TECHNICAL_DATA'"Return of Historical Data for a Business Object
  EXPORTING
   IV_OBJECTCLASS =  "Object class
*  IV_OBJECTID =  "Object value
   IV_TABLENAME =  "
   IV_TECHNICAL_DATE =  "
*  IV_TECHNICAL_TIME = '235959' "Time
   IT_CURRENT_DATA =  "
   IS_KEY_STRUCTURE =  "Changed table record key
   IV_EXCL_FIRST_KEY =  "Field Name

 IMPORTING
   ET_HISTORY_DATA =  "

EXCEPTIONS
   ERROR_WHILE_CONVERSION = 1 

.

IMPORTING Parameters details for BUX_CONVERT_TECHNICAL_DATA

IV_OBJECTCLASS - Object class

Data type: CDHDR-OBJECTCLAS
Optional: No
Call by Reference: Yes

IV_OBJECTID - Object value

Data type: CDHDR-OBJECTID
Optional: Yes
Call by Reference: Yes

IV_TABLENAME -

Data type: CDPOS-TABNAME
Optional: No
Call by Reference: Yes

IV_TECHNICAL_DATE -

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

IV_TECHNICAL_TIME - Time

Data type: SY-UZEIT
Default: '235959'
Optional: Yes
Call by Reference: Yes

IT_CURRENT_DATA -

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

IS_KEY_STRUCTURE - Changed table record key

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

IV_EXCL_FIRST_KEY - Field Name

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

EXPORTING Parameters details for BUX_CONVERT_TECHNICAL_DATA

ET_HISTORY_DATA -

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

EXCEPTIONS details

ERROR_WHILE_CONVERSION - Error during conversion

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM BUX_CONVERT_TECHNICAL_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