E1LFM1M is a standard Vendor Master Structure in SAP LO application. Below you can view the Table Structure, columns(fields), SAP Wiki pages, discussion threads, related TCodes, FMs, ABAP Reports, BW Datasources, and Authorization Objects for E1LFM1M. You can use the transaction code SE11 to view the fields in this structure.
E1LFM1M — Meta Data
Description: | Segment for purchasing organization data vendor SMD |
Main Category: | LO |
Sub Category: | Vendor Master |
Table type: | Structure (INTTAB) |
E1LFM1M — Table Structure, Fields(Columns) and Definitions
Position | Column Name | Description | Primary Key | Data Type | Length | Check Table |
---|---|---|---|---|---|---|
1 | MSGFN | Function | CHAR | 3 | ||
2 | LIFNR | Vendor | CHAR | 10 | ||
3 | EKORG | Purchasing Org. | CHAR | 6 | ||
4 | ERDAT | Created on | CHAR | 8 | ||
5 | ERNAM | Created by | CHAR | 12 | ||
6 | SPERM | Centrally imposed purchasing block | CHAR | 1 | ||
7 | LOEVM | Deletion Indicator | CHAR | 1 | ||
8 | LFABC | Updated information in related user data field | CHAR | 1 | ||
9 | WAERS | Currency | CHAR | 5 | ||
10 | VERKF | Responsible Salesperson at Vendor's Office | CHAR | 30 | ||
11 | TELF1 | First telephone number | CHAR | 16 | ||
12 | MINBW | Minimum order value (CHAR13) | CHAR | 13 | ||
13 | ZTERM | Payt terms | CHAR | 4 | ||
14 | INCO1 | Incoterms | CHAR | 3 | ||
15 | INCO2 | Incoterms 2 | CHAR | 28 | ||
16 | WEBRE | GR-Based IV | CHAR | 1 | ||
17 | KZABS | Updated information in related user data field | CHAR | 1 | ||
18 | KALSK | Updated information in related user data field | CHAR | 2 | ||
19 | KZAUT | Updated information in related user data field | CHAR | 1 | ||
20 | EXPVZ | Updated information in related user data field | CHAR | 1 | ||
21 | ZOLLA | Single-Character Flag | CHAR | 6 | ||
22 | MEPRF | Updated information in related user data field | CHAR | 1 | ||
23 | EKGRP | Purch. Group | CHAR | 3 | ||
24 | BOLRE | Updated information in related user data field | CHAR | 1 | ||
25 | UMSAE | Updated information in related user data field | CHAR | 1 | ||
26 | XERSY | ERS | CHAR | 1 | ||
27 | PLIFZ | Planned delivery time in days | CHAR | 5 | ||
28 | MRPPP | PPC planning calendar | CHAR | 3 | ||
29 | LFRHY | Planning cycle | CHAR | 3 | ||
30 | LIEFR | Delivery cycle | CHAR | 4 | ||
31 | LIBES | Updated information in related user data field | CHAR | 1 | ||
32 | LIPRE | Updated information in related user data field | CHAR | 2 | ||
33 | LISER | Updated information in related user data field | CHAR | 1 | ||
34 | BOIND | Updated information in related user data field | CHAR | 1 | ||
35 | PRFRE | Relevant for price determination ID | CHAR | 1 | ||
36 | NRGEW | Updated information in related user data field | CHAR | 1 | ||
37 | BLIND | Block | CHAR | 1 | ||
38 | KZRET | Updated information in related user data field | CHAR | 1 | ||
39 | SKRIT | Updated information in related user data field | CHAR | 1 | ||
40 | BSTAE | Updated information in related user data field | CHAR | 4 | ||
41 | RDPRF | Rounding Profile | CHAR | 4 | ||
42 | MEGRU | Updated information in related user data field | CHAR | 4 | ||
43 | VENSL | Updated information in related user data field | CHAR | 7 | ||
44 | BOPNR | Updated information in related user data field | CHAR | 4 | ||
45 | XERSR | Updated information in related user data field | CHAR | 1 | ||
46 | EIKTO | Shipper's (Our) Account Number at the Customer or Vendor | CHAR | 12 | ||
47 | PAPRF | Updated information in related user data field | CHAR | 4 | ||
48 | AGREL | Updated information in related user data field | CHAR | 1 | ||
49 | XNBWY | Updated information in related user data field | CHAR | 1 | ||
50 | VSBED | Shipping Cond. | CHAR | 2 | ||
51 | LEBRE | Indicator for Service-Based Invoice Verification | CHAR | 1 | ||
52 | MINBW2 | CHAR | 16 | |||
53 | ACTIVITY_PROFIL | Updated information in related user data field | CHAR | 4 | ||
54 | TRANSPORT_CHAIN | Transportation Chain | CHAR | 10 | ||
55 | STAGING_TIME | Staging Time in Days | CHAR | 4 | ||
56 | VENDOR_RMA_REQ | Updated information in related user data field | CHAR | 1 | ||
57 | INCOV | Incoterms Version | CHAR | 4 | ||
58 | INCO2_L | Incoterms Location 1 | CHAR | 70 | ||
59 | INCO3_L | Incoterms Location 2 | CHAR | 70 |
SAP Help, Wiki Resources, and Forum Discussions on E1LFM1M
-
XI IDOC missing segment definition in type E1LFM1M | SCN
Actually it does not matter what are your systems' versions, PI can always handle an IDoc properly. All you need to do is perform the following steps in your PI system:
http://scn.sap.com/message/10989406
-
UDF to Handle multiple occurences of segments E1LFM1B & E1LFM1M in CREMAS04
we are working on CREMAS IDOC to flat file scenario and in it we have a requirement as mentioned below.
http://scn.sap.com/message/6928321
Related Tables
TABLE | Description | Functional Area |
---|---|---|
E1LFA1M | Segment for general vendor data | LO - Vendor Master |
E1LFB1M | Segment for company code data for vendors SMD | LO - Vendor Master |
E1WYT3M | Segment for addresses of vendors MMS SMD | LO - Vendor Master |
EDI_DC40 | IDoc Control Record for Interface to External System | BC - ALE Integration Technology |
E1LFBKM | Segment for bank details of vendor SMD | LO - Vendor Master |
E1LFA1A | Segment for standard vendor data - enhancement | LO - Vendor Master |
E1LFASM | Segment for EU tax numbers vendors | LO - Vendor Master |
Transaction Codes for SAP Table E1LFM1M
TCODE | Description | Functional Area |
---|---|---|
WE05 | IDoc Lists | Basis - ALE Integration Technology |
WE19 | Test tool | Basis - ALE Integration Technology |
XK01 | Create Vendor (Centrally) | FI - Basic Functions |
BD14 | Send vendor | LO - Vendor Master |
SM58 | Asynchronous RFC Error Log | Basis - RFC |
SXI_CACHE | Integration Directory Cache | Basis - Integration Builder - Configuration |
SXMB_MONI | Integration Engine - Monitoring | Basis - Integration Engine |
BD64 | Maintenance of Distribution Model | Basis - ALE Integration Technology |
FMs for SAP Table E1LFM1M
FM | Description | Functional Area |
---|---|---|
EXIT_SAPLVV01_001 | Create Export of Additional Customer Master Segments | Logistics - Business Partners |
BAPI_ACC_DOCUMENT_POST | Accounting: Posting | Accounting - Accounting Interface |
SSF_FUNCTION_MODULE_NAME | Basis - Smart Forms | |
SXMB_GET_XMB_USE | Verwendung des XMB (zentral, lokal) ermitteln | Basis - Integration Engine |
GUI_UPLOAD | Upload for Data Provider | Basis - Graphical User Interface |
BAPI_ACC_GL_POSTING_POST | Accounting: General G/L Account Posting | Accounting - Accounting Interface |
MDM_METADATA_MAINTAIN | MDM Pflege der Metadaten im Quellsystem | Master Data Mgmt - Client-System Adapter |
SXMS_ASYNC_EXEC | Asynchroner Ablauf der XI Runtime | Basis - Integration Engine |
ABAP Reports for SAP Table E1LFM1M
ABAP REPORT | Description | Functional Area |
---|---|---|
SAPMF02K | Vendor Master Data | FI - Basic Functions |
RBDSECOS | Send cost center | CO - Cost Center Accounting |
SAPMSCC1 | Copy Client-Specific Tables from a Client | Basis - Client Copy |
RFBIKR00 | Batch Input Interface for Vendors | FI - Financial Accounting |
RSNAST00 | Selection Program for Issuing Output | SD - Output Determination |
MDM_METADATA_MAINTAIN | MDM Metadata Maintenance | Master Data Mgmt - Client-System Adapter |
SAPLSPO1 | ?... | |
SAPLSCCR | Central Client Copy Functions |
Most searched SAP Logistics - General Tables
- Material Master Tables
- Handling Unit Tables
- Bom Tables
- Material Document Tables
- Storage Location Tables
- Material Group Tables
- Serial Number Tables
- Batch Tables
- Material Type Tables
- Inventory Tables
- Valuation Class Tables
- Plant Storage Location Tables
- Master Data Tables
- Physical Inventory Tables
- Customer Master Contact Person Tables
- Stock Tables
- Distribution Channel Tables
- Bom Component Tables
- Material Status Tables
- Product Group Tables
- Mara Tables
- Se16 Tables List Tables