E1WYT3M is a standard Vendor Master Structure in SAP LO application. On this page, you can view the Table Structure, Columns(Fields), links to SAP Documentation, Wiki & Help Pages, Q&A, similar/related TCodes, Tables, FMs, ABAP Reports for E1WYT3M. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition.

E1WYT3M — Table Structure, Fields(Columns) and Definitions

    Position Column Name Description Data Element Primary Key Data Type Length Check Table
    1 MSGFN Function MSGFN CHAR 3
    2 LIFNR Vendor LIFNR CHAR 10
    3 EKORG Purchasing Org. CHAR6 CHAR 6
    4 LTSNR Single-Character Flag LTSNR CHAR 6
    5 WERKS Plant CHAR6 CHAR 6
    6 PARVW Partner function PARVW CHAR 2
    7 PARZA Partner counter CHAR3 CHAR 3
    8 ERNAM Created by ERNAM CHAR 12
    9 ERDAT Created on CHAR8 CHAR 8
    10 LIFN2 Account Number of Vendor or Creditor LIFN2 CHAR 10
    11 DEFPA Default partner DEFPA CHAR 1
    12 PERNR Personnel No. CHAR 8

SAP Help, Wiki, Q&A and other resources for E1WYT3M

Click the above link for the full list of resources and help pages, only the first few are posted below

  • CREMAS IDOC structure function module | SAP Blogs

    4 2 14,763

    "A second challenge is the fact that all segments in the IDOCs must adhere to a prescribed sequence incl. dependencies among segments, e.g. contact persons (segment E1WYT3M) must be assigned to a purchase organization (segment E1FLM1M)."

    https://blogs.sap.com/2018/05/07/cremas-idoc-structure-function-module

  • Partner Function for Vendor through IDOC - SAP Q&A

    I have a requirement in which I need to create the vendor master through IDOC. I am using CREMAS basic type for that. In its functionality, I need to assign different partner functons to it. I identified the segment as E1WYT3M in it at hierarchy level 3. I passed the partner function like OA or PI in the PARVW field of it and provided the vendor number which I want to assign as partner function in the LIFN2 field.

    https://answers.sap.com/questions/8162523/partner-function-for-vendor-through-idoc.html

  • Context Problem when using Use One As Many - SAP Q&A

    i have got a requirement in an IDOC To File Interface where the segments in the IDOC are like E1LFA1M->E1LFM1M->E1WYT3M

    https://answers.sap.com/questions/7821701/context-problem-when-using-use-one-as-many.html

  • Table Control in LSMW - SAP Q&A

    I have used XK01 tcode to upload vendor details as well bank details.Bank details are in Table Control. Here in this table control the number of visible rows are 5. And I did LSMW, recording for one vendor with 5 bank details.

    "E1WYT3M Segment for addresses of vendors MMS SMD"

    https://answers.sap.com/answers/1308108/view.html

  • Partner functions updation through CREMAS - SAP Q&A

    IN E1WYT3M segment we are populating 005 field value for MSGFN so that partner function details are updated by deleting old records and replacing with new records. Idocs are failing due to mandatory partner function like PI .

    https://answers.sap.com/questions/9337982/partner-functions-updation-through-cremas.html

  • Permitted Payee | SAP Community

    SAP Community Groups will be in read-only mode from 4AM UTC (12 am ET) September 27, 2022 until approximately 6PM UTC (2pm ET) the same day. During this time, no engagement activities will be possible.

    https://answers.sap.com/questions/4710780/permitted-payee.html

  • USE One as Many | SAP Community

    i have got a requirement in an IDOC To File Interface ,the IDOC Structure will be like

    https://answers.sap.com/questions/7804535/use-one-as-many.html

  • Issue in IDOC CREMAS01 - SAP Q&A

    I am creating an inbound IDOC for Vendor master. I am using CREMAS01 for Vendor master data, However I am not able to update the contact person data because there is no segment for the same as it is for customer master (debmas04).

    "i think You have segment E1WYT3M for contact person..."

    https://answers.sap.com/questions/6997622/issue-in-idoc-cremas01.html

  • IDOC_INPUT_DEBITOR_MDM shortcomings? - SAP Q&A

    We're sending DEBMAS messages from MDM to R/3, handled by function IDOC_INPUT_DEBITOR_MDM on the R/3 side. If changing a Business Partner (segment KNVP) in MDM, it does not get deleted in R/3, only added. Debugging IDOC_INPUT_DEBITOR_MDM shows that there's indeed no deletion of such segments; is this a bug or a "feature"?

    https://answers.sap.com/questions/4122328/idocinputdebitormdm-shortcomings.html

  • ALE error using CREMEAS when sending Vendor Master with Partner functions - SAP Q&A

    I am creating 3 vendors (A, B and C) all together at the same time (a minute apart) with partners among themselves in one SAP instance (System 1)

    https://answers.sap.com/questions/12318161/ale-error-using-cremeas-when-sending-vendor-master.html

  • View the full list of resources, SAP Help/Wiki pages and Q&A for E1WYT3M


Related Tables

TABLE Description Functional Area
E1LFM1M Segment for purchasing organization data vendor SMD LO - Vendor Master
E1LFA1M Segment for general vendor data LO - Vendor Master
E1LFB1M Segment for company code data for vendors SMD LO - Vendor Master
E1LFA1A Segment for standard vendor data - enhancement LO - Vendor Master
E1LFBKM Segment for bank details of vendor SMD LO - Vendor Master

Transaction Codes for SAP Table E1WYT3M

TCODE Description Functional Area
XK01 Create Vendor (Centrally) FI - Basic Functions
WE05 IDoc Lists Basis - ALE Integration Technology
XK03 Display vendor (centrally) LO - Vendor Master
FPL9 Display Account Balance FI - Contract Accounts Receivable and Payable
FQEVENTS Events FI - Contract Accounts Receivable and Payable
WE30 IDoc Type Development Basis - ALE Integration Technology

FMs for SAP Table E1WYT3M

FM Description Functional Area
FKK_SAMPLE_1200 Muster: Kopfinformationen bei Einzelposten f FI - Contract Accounts Receivable and Payable
IDOC_INPUT_DEBITOR_MDM MDM: ALE Inbound Processing: DEBMAS IDocs (MDM Plugin Version) Logistics - Business Partners
IDOC_INPUT_CREDITOR_MDM MDM: ALE Inbound Processing: CREMAS IDocs (MDM Plugin Version) Logistics - Business Partners
MASTER_IDOC_DISTRIBUTE Application interface to the ALE layer on outbound processing side Basis - ALE Integration Technology
MASTERIDOC_CREATE_CREMAS Logistics - Business Partners

ABAP Reports for SAP Table E1WYT3M

ABAP REPORT Description Functional Area
LKD02F01 INCLUDE LKD02F01
SAPMF02K Vendor Master Data FI - Basic Functions

Most searched SAP Logistics - General Tables