SAP MATERIAL_BTCI_SELECTION_NEW Function Module for
MATERIAL_BTCI_SELECTION_NEW is a standard material btci selection new 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 material btci selection new FM, simply by entering the name MATERIAL_BTCI_SELECTION_NEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: MGCT
Program Name: SAPLMGCT
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MATERIAL_BTCI_SELECTION_NEW 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 'MATERIAL_BTCI_SELECTION_NEW'".
EXPORTING
MATERIAL = "Material Number
* MATERIALART = 'ROH' "Material Type
SELECTION = "Maintenance status
TCODE = "Transaction Code
IMPORTING
SELSTATUS = "Maintenance status
SELSTATUS_IN = "Maintenance status
TABLES
BTCI_D0070 = "Batch input: New table field structure
EXCEPTIONS
MATERIAL_NOT_FOUND = 1 MATERIAL_NUMBER_MISSING = 2 MATERIAL_TYPE_MISSING = 3 MATERIAL_TYPE_NOT_FOUND = 4 NO_ACTIVE_DYNPRO_SELECTED = 5 NO_AUTHORITY = 6
IMPORTING Parameters details for MATERIAL_BTCI_SELECTION_NEW
MATERIAL - Material Number
Data type: MARA-MATNROptional: No
Call by Reference: No ( called with pass by value option)
MATERIALART - Material Type
Data type: MARA-MTARTDefault: 'ROH'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SELECTION - Maintenance status
Data type: T130M-PSTATOptional: No
Call by Reference: No ( called with pass by value option)
TCODE - Transaction Code
Data type: T130M-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MATERIAL_BTCI_SELECTION_NEW
SELSTATUS - Maintenance status
Data type: T130M-PSTATOptional: No
Call by Reference: No ( called with pass by value option)
SELSTATUS_IN - Maintenance status
Data type: T130M-PSTATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MATERIAL_BTCI_SELECTION_NEW
BTCI_D0070 - Batch input: New table field structure
Data type: BDCDATAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MATERIAL_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MATERIAL_NUMBER_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MATERIAL_TYPE_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MATERIAL_TYPE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ACTIVE_DYNPRO_SELECTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MATERIAL_BTCI_SELECTION_NEW 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_material | TYPE MARA-MATNR, " | |||
| lv_selstatus | TYPE T130M-PSTAT, " | |||
| lt_btci_d0070 | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_material_not_found | TYPE BDCDATA, " | |||
| lv_materialart | TYPE MARA-MTART, " 'ROH' | |||
| lv_selstatus_in | TYPE T130M-PSTAT, " | |||
| lv_material_number_missing | TYPE T130M, " | |||
| lv_selection | TYPE T130M-PSTAT, " | |||
| lv_material_type_missing | TYPE T130M, " | |||
| lv_tcode | TYPE T130M-TCODE, " | |||
| lv_material_type_not_found | TYPE T130M, " | |||
| lv_no_active_dynpro_selected | TYPE T130M, " | |||
| lv_no_authority | TYPE T130M. " |
|   CALL FUNCTION 'MATERIAL_BTCI_SELECTION_NEW' " |
| EXPORTING | ||
| MATERIAL | = lv_material | |
| MATERIALART | = lv_materialart | |
| SELECTION | = lv_selection | |
| TCODE | = lv_tcode | |
| IMPORTING | ||
| SELSTATUS | = lv_selstatus | |
| SELSTATUS_IN | = lv_selstatus_in | |
| TABLES | ||
| BTCI_D0070 | = lt_btci_d0070 | |
| EXCEPTIONS | ||
| MATERIAL_NOT_FOUND = 1 | ||
| MATERIAL_NUMBER_MISSING = 2 | ||
| MATERIAL_TYPE_MISSING = 3 | ||
| MATERIAL_TYPE_NOT_FOUND = 4 | ||
| NO_ACTIVE_DYNPRO_SELECTED = 5 | ||
| NO_AUTHORITY = 6 | ||
| . " MATERIAL_BTCI_SELECTION_NEW | ||
ABAP code using 7.40 inline data declarations to call FM MATERIAL_BTCI_SELECTION_NEW
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 MATNR FROM MARA INTO @DATA(ld_material). | ||||
| "SELECT single PSTAT FROM T130M INTO @DATA(ld_selstatus). | ||||
| "SELECT single MTART FROM MARA INTO @DATA(ld_materialart). | ||||
| DATA(ld_materialart) | = 'ROH'. | |||
| "SELECT single PSTAT FROM T130M INTO @DATA(ld_selstatus_in). | ||||
| "SELECT single PSTAT FROM T130M INTO @DATA(ld_selection). | ||||
| "SELECT single TCODE FROM T130M INTO @DATA(ld_tcode). | ||||
Search for further information about these or an SAP related objects