EDI configuration responsibilities

Hi,
When a team is configuring EDI interface, what tasks are done by
1. functional people
2. technical people
3. basis people
Basically I would like to know the roles of the functional, technical, and the basis teams regarding EDI configuration
Thank you.

Hi Jagadish,
Based on my experience (working in an EDI project) following are my inputs:
1) The core of EDI is the mapping between the IDoc and the standard EDI message format (ANSI, EDIFACT etc). Generally the IDoc file is generated by the
SAP system. This IDoc file (control and data segment) needs to be mapped to the EDI message.
The EDI mapper (who has experience with the mapping tool - Gentran, Mercator etc) needs to sit with the techie guy (having knowledge about the IDoc segments and fields) to design an excel mapping.
2) Once the excel mapping is complete the EDI mapper can configure the mapping in the mapping tool and parallely configurations can be done in SAP system to generate IDoc file.
3) The functionaly people need to do necessary configuration (like ship-to conversion table (transaction VOE4) to convert external ship-to number to internal ship-to number, maintaining customer/material info records (transaction VD51) - these were some of the setting done in our case for Purchase order IDoc).
4) The technical person will do the message control (output control) settings (transaction NACE), partner profile settings. Also if some enhancement need to be made then the technical person needs to extend the IDoc and write custom logic in user exit to populate extensions.
5) About the basis guy I am not exactly sure. I believe he needs to set up the port (file port so that the IDoc file gets written to a particular location in the application server). The logical system in partner profile should be correctly maintained.
Hope this is useful.
Regards,
Gajendra.

Similar Messages

  • EDI configuration for automatic IV

    Hi,
    What all are the steps to do EDI configuration for automatic
    IV in an intercompany scenario. In an STO scenario I
    want the invoice to generated automatically in the receiving
    company based on the issuing company's invoice.
    regards
    Magi

    HI,
    I have done these setttings . I have done the settings for partner type KU (customer) and partner type LI (vendor) in
    WE20.
    But IDOCs are not getting generated. Is there anything else
    to do to trigger the generation of IDOCS?
    regards
    magi

  • How to create a Sales Order through an EDI configuration.

    Hi
    How to create a Sales Order through an EDI configuration.
    Tell me the step-by-step procedure for this.
    Any power point presentation would be fine.
    Cheers
    Maruthi

    Hi,
    You can go to these links to know little bit about sales order creation through EDI/ALE by means of IDOCS.
    http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
    Sales Order Idoc Extension.
    http://www.*******************/2007/11/abap-idocs-basic-tools.html
    For any specific information, just do a google search(information like message t ype, IDOC type, Functoin module, etc. You will definitely get the information you are looking for
    Please reward if this helps you

  • SD EDI configuration for sending invoice to customers

    Hi,
    Could anybody please tell me what all SD configuration i need to do  in
    SPRO-->Electronic Data Interchange section for sending invoice through EDI?
    I have already done output type configuration and able to generate IDOC when i save my invoice.
    Thanks,
    Regards,
    Satya

    Hi All,
    Thanks for the response.
    But majorily i am looking for SPRO>Sales&Distribution>EDI configuration.
    Do i need to do it?
    Is it mandatory?
    Thanks in Advance.
    Regards,
    Satya

  • EDI Configuration

    Hi ,
    I am doing new EDI configuration .I just wanted to confirm how the transaction SM59 (RFC destination)
    and we21 (Port config) are related .
    What are the settings we need to do here for :
    1) Inbound
    2) Outbound .
    Antcipating reply asap .
    Thanks
    Shounak M.

    Hi,
    SM59 and WE21 is required when you are communicating between different R/3 servers or SAP environment.
    SM59 for RFC connction between servers.
    WE21 ports for connection between servers.
    If you are communicating with NON SAP then you don't need these settings.
    REgards,
    Wasim Ahmed

  • Step by step of EDI configuration

    Hi all,
    can any one tell me or send me a document  the step by step procedure of EDI Configuration.
    My email id  is
    [email protected]
    Thanks in advance

    Hi
    http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
    http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
    http://www.erpgenie.com/sapedi/index.htm
    http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
    Creation of Custom IDOc type and message Type
    First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
    take the Basis help to create them.
    1.First create segments in WE31 Tcode with the required dataelements
    2.Create the Basic Idoc Type in WE30
       release the Segments and IDOC type.
    3.Create Message type in We81
    4.Assign the message type to IDOC type in WE82 T code
    5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
    6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for    Inbound) Outbound Fun module
    7.Create  Workflow setting if needed ..
    8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
    9.Define setting for fun module in BD51
    10.In BD51 Define the settings for Fun module..
    10.Assign the Processs Code to Fun mod`ule
    check the following thread:
    /message/2222912#2222912 [original link is broken]
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/e6/04c03e7856b300e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    Reward points if useful
    Regards
    Anji

  • Step by step SAP EDI Configuration

    Hi,
    Can you please shar step by step SAP EDI Configuration deatils.
    Regards,
    Nitin Patil

    Hi
    Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
    The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
    1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
    2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
    3. create a one to one mapping between input en output.
    4. export the metadata in xsd or sda format for import in XI
    5. generate an SDA which can be deployed in XI and used as a module.
    Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    Integrating XI with SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
    Thoughts on EDI in an SAP XI Environment
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
    regards,
    Kishore

  • ALE / EDI configuration scenario

    Hi,
    this is my scenario.
    we are using a many edi partners with the same outbound and inbound partner profile.
    Example.
    Partnertype: KU
    Partner: Z1
    Outbound-Idoc: MATMAS, ARTMAS, INFREC
    Partner: Z2
    Outbound-Idoc: MATMAS, ARTMAS, INFREC
    Partner: Zxxxxx
    Outbound-Idoc: MATMAS, ARTMAS, INFREC
    The reason why there is a partner profile for each Z-partner ?
    Every Z-Partner gets it´s own port.
    Every Z-Partner get´s it´s own TCP/IP connection via program id (gateway).
    Is it possible to maintain the partner profil for Partner: Z1 and distribute the settings to each Partner zxxx ?
    I know the method to copy a complete partner but maybe you have another idea.
    thx,
    Gordon

    You can use program RSEINB00 and a file port.  As for the other ALE config steps, you can find those in the help docs or by searching on the program name which will bring up multiple threads/links covering the topic.

  • EDI Basic configuration settings for Third party sales

    Dear All,
    Could you help step by step how to configure EDI to send PO automatically to outsourcing company for the Third party sales order.
    Thanks
    CG Balaji

    Hi roberto
    Please send me basic EDI configuration document to my mail id [email protected] this will help me a lot.
    Thanks and regards,
    CG Balaji

  • IDoc output type not getting configured in IDoc-File scenario

    Hello
    I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
    1] Created output type
    2] Created partner function as EDI LS for this output type
    3] Configured RSNASTED as Processing Routines for output type
    4] Included this output type in the Header output procedure
    5] Configured XI system as the partner in partner profile with appropriate Message control
    Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
    I checked in SPRO but could not find such flag.
    Does anyone had came across such output type configuration.
    Thanks in advance.
    I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
    Regards
    Rajeev

    Hi,
    Please check the following
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    Copy NEU to ZNEU or YNEU
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
    G.Ganesh Kumar

  • EDI:Sale order and delivery order

    hi friends
    1.Our process is  customer send the PO Through B2B Server (third party system)
    my how i  get the notification throgh mail..what i do for configuration.....iam sure this is for inbound message ..is it require EDI Configuration or master data
    2. Parner profile WE20
    MESSAGE CONTROL
    MESSAGE TYPE--RD04      What is the purpose maintain there
    PROCESS CODE -SD09      What is the purpose maintain there
    3..During  delivery document
    Partner profile shall i maitain out boud parameter is DESADV For Partner function SP, INVOIC For Partner function BP, DESADVI For Partner function SH.
    Isit right way? any thing missing pls suggest me to maintain the data
    wiht regards
    dinesh

    You are right. If your customer is sending you a purchase order, then it can come thro' EDI.
    For this, you should have your customer in WE20 with inbound. Partner is KU. It is standard. You can go to WE60/61 to see the documentation on the same. If you have the connections properly done (which Basis has to help you with), you should be able to get the sales order into the system.
    For delivery, desadv is correct. However, WE20 should have to be configured on SH.
    RD04 is usually used for intercompany invoice posting to MM within SAP. You need not have to use it. You can use a diffient out put type configured to EDI output. INVOIC01 is the one used to send the customer invoices out of SAP.
    Invoices are usually configured on BP or PY. Usually BP and PY are same in most of the scenarios.

  • Is model view(BD64) necessary for EDI

    is model view created using BD64 necessary for a EDI transactions? I have created a logical system, a RFC destination and a EDI File Port.
    After all this i am trying to push a material master data using BD10 to the file port. When i do that the system gives me a message saying that master idoc created but it does not create a communication idoc. Only if i have a Model view set up in BD64 it creates a communication idoc. So my question is do we need a model view for EDI configuration?
    ~Suresh

    Hi,
    BD64 is required for master data distribution..
    If you are having a interface that sends IDOCs to the customer or receive IDOCs from the vendor..You don't require BD64 setup..
    Thanks,
    Naren

  • Customer , vendor 0000049256 not known (EDI process)

    We are trying to send an IDoc type INVOIC from one SAP R/3 system to
    another using the SAP XI/PI.
    Right now we are experience an error “Customer , vendor 0000049256 not
    known”, after have check all ALE/EDI configuration between the source
    system (SAP R/3 4.6B), the middleware (SAP XI/PI 7.0) and the receiver
    system (SAP R/3 4.6B with IS-OIL) we still don’t find the solution.
    We applied the note 117814, with the following code (file attach).
    Source (SD module sends an IDoc type INVOIC) SAP R/3 4.6B
    BASIS 53
    ABAP 53
    APPL 53
    Middleware (SAP XI/PI 7.0)
    BASIS 12
    ABAP 12
    Target (MM module receives an IDoc type INVOIC) SAP R/3 4.6B
    BASIS 38
    ABAP 38
    APPL 37
    IS-OIL 37
    Can someone help us?
    Thanks in advance
    Un Saludo/Regards/Mit freundlichen Grüssen,
    João Paulo Reis
    Accenture – SI SAP - Technology
    Edificio Accenture
    C/Ramírez de Arellano, 35
    Madrid - Spain 28043
    T: +34 915966000
    F: +34 91 596 6695
    Mobile : + 34 606432447

    Hello Joao,
    Check your logical system which represent the R/3 did you Configured the Customer Distribution Model correctly?Do an initial check  for ports,partner profile and inbound/outbound parameters.
    Regards,
    jafer

  • EDI Inbound Interface

    Dear Friends,
    In our organization, there is a third party involved into stocktake and provide us input flat files for each plant separately. These files are loaded into SAP automatically as iDoc, this is working good.
    Some details of EDI configuration are
    Partner Type KU: (Each Plant is being configured as a customer Partner Type KU)
    Inbound Parameter, Message Type : WVINVE
    Process Code: WVIN
    Identification: IDOC_INPUT_STORE_INVENTORY
    Option ALE: Radio Button "Processing with ALE Services"
    Processing Type: Radio Button "Processing by function module"
    I am trying to find out where is these automation done? (I mean how incoming data is being loaded into sap automatically?)
    and where(directly etc) initially incoming data is being stored into SAP?
    Regards,
    Sunny

    Hi,
    IDocs are nothing more than structured ASCII data, you could always process them directly with an ABAP. This is certainly the quick and dirty solution, bypassing all the internal checks and processing mechanisms. We will not reinvent the wheel here..
    Please check the below link...
    http://www.idocs.de/www5/EDI/HTML/IDocBook.htm#_Toc8400370
    Hope it may help you.
    Kuber

  • Invoice in EDI format

    A customer of my company wants us to send invoices in 810 EDI format from SAP. Does any one know how to do the necessary set ups/configuration in SAP to send the invoice IDoc?
    Points rewarded for helpful answers.
    Thanks,
    Archana

    Hi,
    For configuring of EDI for Invoice, you have to do following things :
    1. Use Outbound IDOC type u2013 INVOIC01 (Message type u2013 INVOIC)
    2. Maintain Condition Record for Billing Output (EDI)
               Transaction Code : VV31 / VV32 / VV33
               Output Type : RD00
    3. Port in IDOC processing
               Transaction Code : WE21
               Port Type - > File Port : For eg . - EDIFACT
               Maintain all the relevant field like physical path for directory, Functional module for file name.
    4. Create Partner Profile
               Transaction Code u2013 WE20
               Select Partner type KU (Customer) and maintain outbound parameters for Outbound IDoc - INCOIC01
    Some Important Transaction Codes for EDI Configuration which you have to know.
               WE63 - Documentation IDOC Type
               WE46 - IDOC Administration
               WE16 - Trigger Inbound processing
               WE19 - Test Tools for IDOC Processing
               WE02 u2013 IDOC Status
               WE05 u2013 IDOC Status
               We07 u2013 IDOC Statistic
    Hope you can configure now.
    Cheers.....
    Imran

Maybe you are looking for