BLFM2 SAP (Vendor Master Record: Purchasing Data (Batch Input)) Structure details
Dictionary Type: Structure
Description: Vendor Master Record: Purchasing Data (Batch Input)
Description: Vendor Master Record: Purchasing Data (Batch Input)
Structure field list including key, data, relationships and ABAP select examples
BLFM2 is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Vendor Master Record: Purchasing Data (Batch Input)" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BLFM2 TYPE BLFM2.
The BLFM2 table consists of various fields, each holding specific information or linking keys about Vendor Master Record: Purchasing Data (Batch Input) data available in SAP. These include TBNAM (Table Name), LTSNR (Vendor Subrange), WERKS (Plant), SPERM (Purchasing block at purchasing organization level).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP BLFM2 structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| STYPE | Batch Input Interface Record Type | STYPE_BI | CHAR | 1 | CHAR1 | ||||
| TBNAM | Table Name | TABNAME | CHAR | 30 | Assigned to domain | AS4TAB | DTB | ||
| LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | Assigned to domain | LTSNR | |||
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| SPERM | Purchasing block at purchasing organization level | SPERM_M | CHAR | 1 | XFELD | ||||
| LOEVM | Delete flag for vendor at purchasing level | LOEVM_M | CHAR | 1 | XFELD | ||||
| LFABC | ABC indicator | LFABC | CHAR | 1 | LFABC | ||||
| WAERS | Purchase order currency | BSTWA | CUKY | 5 | Assigned to domain | WAERS | |||
| VERKF | Responsible Salesperson at Vendor's Office | EVERK | CHAR | 30 | TEXT30 | ||||
| TELF1 | Vendor's telephone number | TELFE | CHAR | 16 | TEXT16 | ||||
| MINBW | Minimum order value (batch input field) | MINBW_BI | CHAR | 16 | CHAR16 | ||||
| ZTERM | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
| INCO1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | Assigned to domain | INCO1 | |||
| INCO2 | Incoterms (Part 2) | INCO2 | CHAR | 28 | INCO2 | ||||
| WEBRE | Indicator: GR-Based Invoice Verification | WEBRE | CHAR | 1 | XFELD | ||||
| KZABS | Order Acknowledgment Requirement | KZABS | CHAR | 1 | XFELD | ||||
| KALSK | Group for Calculation Schema (Vendor) | KALSK | CHAR | 2 | Assigned to domain | KALSK | |||
| KZAUT | Automatic Generation of Purchase Order Allowed | KZAUT | CHAR | 1 | XFELD | ||||
| EXPVZ | Mode of Transport for Foreign Trade | EXPVZ | CHAR | 1 | Assigned to domain | EXPVZ | |||
| ZOLLA | Customs Office: Office of Exit/Entry for Foreign Trade | DZOLLS | CHAR | 6 | Assigned to domain | ZOLLS | |||
| MEPRF | Price Determination (Pricing) Date Control | MEPRF | CHAR | 1 | MEPRF | ||||
| EKGRP | Purchasing Group | EKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| BOLRE | Indicator: vendor subject to subseq. settlement accounting | BOLRE | CHAR | 1 | XFELD | ||||
| UMSAE | Comparison/agreement of business volumes necessary | UMSAE | CHAR | 1 | XFELD | ||||
| XERSY | Evaluated Receipt Settlement (ERS) | XERSY | CHAR | 1 | XFELD | ||||
| PLIFZ | Planned Delivery Time in Days (BTCI) | PLIFZ_BI | CHAR | 3 | CHAR03 | ||||
| MRPPP | Planning calendar | MRPPP_W | CHAR | 3 | Assigned to domain | MRPPP | |||
| LFRHY | Planning cycle | LFRHY | CHAR | 3 | Assigned to domain | MRPPP | |||
| LIBES | Order entry by vendor | LIBES | CHAR | 1 | CHAR1 | ||||
| LIPRE | Price marking, vendor | LIPRE | CHAR | 2 | Assigned to domain | LIPRE | |||
| LISER | Rack-jobbing: vendor | LISER | CHAR | 1 | CHAR1 | ||||
| DISPO | MRP Controller (Materials Planner) | DISPO | CHAR | 3 | Assigned to domain | DISPO | DGR | HS_T024D | |
| XDELE | Indicator: Delete entry using batch input ? | XDELE_BI | CHAR | 1 | XFELD | ||||
| BOIND | Indicator: index compilation for subseq. settlement active | BOIND | CHAR | 1 | XFELD | ||||
| BSTAE | Confirmation Control Key | BSTAE | CHAR | 4 | Assigned to domain | BSTAE | |||
| RDPRF | Rounding Profile | RDPRF | CHAR | 4 | Assigned to domain | RDPRF | |||
| MEGRU | Unit of Measure Group | MEGRU | CHAR | 4 | Assigned to domain | MEGRU | |||
| BOPNR | Restriction Profile for PO-Based Load Building | BOPNR | CHAR | 4 | CHAR4 | ||||
| XERSR | Automatic evaluated receipt settlement for return items | XERSR | CHAR | 1 | XFELD | ||||
| ABUEB | Release Creation Profile | ABUEB | CHAR | 4 | Assigned to domain | ABUEB | |||
| PAPRF | Profile for transferring material data via IDoc PROACT | WVMI_PAPRF | CHAR | 4 | Assigned to domain | WVMI_PAPRF | |||
| XNBWY | Revaluation allowed | XNBWY | CHAR | 1 | XFELD | ||||
| LEBRE | Indicator for Service-Based Invoice Verification | LEBRE | CHAR | 1 | XFELD | ||||
| TRANSPORT_CHAIN | Transportation Chain | WRF_PSCD_TC_ID | CHAR | 10 | WRF_PSCD_TC_ID | ||||
| STAGING_TIME | Staging Time in Days (Batch Input) | WRF_PSCD_MST_BI | CHAR | 3 | |||||
| SENDE | Record End Indicator for Batch Input Interface | SENDE_BI | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BLFM2 using ABAP code?
As BLFM2 is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BLFM2 as there is no data to select.How to access SAP table BLFM2
Within an ECC or HANA version of SAP you can also view further information about BLFM2 and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects