SAP BUX_TD_CHECK_MAINTAIN_DATA Function Module for Perform TD Check on a data
BUX_TD_CHECK_MAINTAIN_DATA is a standard bux td check maintain 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 Perform TD Check on a 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 bux td check maintain data FM, simply by entering the name BUX_TD_CHECK_MAINTAIN_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUX_TD_CHECK
Program Name: SAPLBUX_TD_CHECK
Main Program: SAPLBUX_TD_CHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUX_TD_CHECK_MAINTAIN_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_TD_CHECK_MAINTAIN_DATA'"Perform TD Check on a data.
EXPORTING
* IV_KEY = "
* IV_VALID_FROM_NAME = "Field Name
* IV_VALID_TO_NAME = "Field Name
IT_PARENT_VALIDITY = "Table type containing validity periods
* IV_DELETE_ALL = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IV_DATE_FROM = "Validity date (valid from)
IV_DATE_TO = "Validity Date (Valid To)
IV_CONSTRAINT = "Version Number Component
IV_ACTION = "Single-Character Flag
* IS_DATA = "
* IS_DATA_X = "
* IV_KEY_NAME = "Field Name
IV_STRUCTURE_NAME = "Table Name
IMPORTING
ET_RETURN = "Return parameter table
EV_TIMESLICE_ADJUSTED = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
CHANGING
CT_DATASET = "
IMPORTING Parameters details for BUX_TD_CHECK_MAINTAIN_DATA
IV_KEY -
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VALID_FROM_NAME - Field Name
Data type: FIELDNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VALID_TO_NAME - Field Name
Data type: FIELDNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_PARENT_VALIDITY - Table type containing validity periods
Data type: BUX_TD_VALIDITY_TOptional: No
Call by Reference: Yes
IV_DELETE_ALL - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
IV_DATE_FROM - Validity date (valid from)
Data type: BU_DATFROMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DATE_TO - Validity Date (Valid To)
Data type: BU_DATTOOptional: No
Call by Reference: Yes
IV_CONSTRAINT - Version Number Component
Data type: CHAR2Optional: No
Call by Reference: Yes
IV_ACTION - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
IS_DATA -
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA_X -
Data type: ANYOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_KEY_NAME - Field Name
Data type: FIELDNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_STRUCTURE_NAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BUX_TD_CHECK_MAINTAIN_DATA
ET_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
EV_TIMESLICE_ADJUSTED - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
CHANGING Parameters details for BUX_TD_CHECK_MAINTAIN_DATA
CT_DATASET -
Data type: ANYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUX_TD_CHECK_MAINTAIN_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: | ||||
| lv_iv_key | TYPE ANY, " | |||
| lv_et_return | TYPE BAPIRET2_T, " | |||
| lv_ct_dataset | TYPE ANY, " | |||
| lv_iv_valid_from_name | TYPE FIELDNAME, " | |||
| lv_iv_valid_to_name | TYPE FIELDNAME, " | |||
| lv_it_parent_validity | TYPE BUX_TD_VALIDITY_T, " | |||
| lv_iv_delete_all | TYPE BOOLE-BOOLE, " | |||
| lv_iv_date_from | TYPE BU_DATFROM, " | |||
| lv_ev_timeslice_adjusted | TYPE BOOLE-BOOLE, " | |||
| lv_iv_date_to | TYPE BU_DATTO, " | |||
| lv_iv_constraint | TYPE CHAR2, " | |||
| lv_iv_action | TYPE CHAR1, " | |||
| lv_is_data | TYPE ANY, " | |||
| lv_is_data_x | TYPE ANY, " | |||
| lv_iv_key_name | TYPE FIELDNAME, " | |||
| lv_iv_structure_name | TYPE TABNAME. " |
|   CALL FUNCTION 'BUX_TD_CHECK_MAINTAIN_DATA' "Perform TD Check on a data |
| EXPORTING | ||
| IV_KEY | = lv_iv_key | |
| IV_VALID_FROM_NAME | = lv_iv_valid_from_name | |
| IV_VALID_TO_NAME | = lv_iv_valid_to_name | |
| IT_PARENT_VALIDITY | = lv_it_parent_validity | |
| IV_DELETE_ALL | = lv_iv_delete_all | |
| IV_DATE_FROM | = lv_iv_date_from | |
| IV_DATE_TO | = lv_iv_date_to | |
| IV_CONSTRAINT | = lv_iv_constraint | |
| IV_ACTION | = lv_iv_action | |
| IS_DATA | = lv_is_data | |
| IS_DATA_X | = lv_is_data_x | |
| IV_KEY_NAME | = lv_iv_key_name | |
| IV_STRUCTURE_NAME | = lv_iv_structure_name | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| EV_TIMESLICE_ADJUSTED | = lv_ev_timeslice_adjusted | |
| CHANGING | ||
| CT_DATASET | = lv_ct_dataset | |
| . " BUX_TD_CHECK_MAINTAIN_DATA | ||
ABAP code using 7.40 inline data declarations to call FM BUX_TD_CHECK_MAINTAIN_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.| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_delete_all). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ev_timeslice_adjusted). | ||||
Search for further information about these or an SAP related objects