Any EDI scenario example?

Hi,
Im in need of a edi scenario example, like a how-to guide.
Any end to end scenario with EDI adapter like step by step is highly appreciated.
Please help.

Hi
Available 3rd Party Adapters and Adapter Modules for SAP NetWeaver PI 7.1 provided by SAP via Reseller Agreement
As in the past, SAP continues to rely also for SAP NetWeaver PI 7.1 on partners to provide connectivity solutions for other applications and certain industry standards. With regards to adapters and adapter modules SAP has currently reseller agreements with the companies Informatica, iWay, and SEEBURGER. The connectivity solutions that are covered by the reseller agreements are sold and delivered through SAP, and also technical support for these partner solutions is available via the SAP Support Portal.
SEEBURGER
From the company SEEBURGER all adapters that are covered by the reseller agreement between SAP and SEEBURGER are already certified for SAP NetWeaver PI 7.1; to be more specific, the following SEEBURGER adapters for SAP NetWeaver PI 7.1 that are covered by the reseller agreement are available:
Technical EDI Adapters
AS2 (EDIINT/HTTP(S))
OFTP (OFTP / ISDN, OFTP / TCPIP)
VAN Access (P7 / X.400, VAN FTP)
Business EDI Adapters
Generic EDI
Protocol converter for OFTP / ISDN or VAN Access
Data format converter for ANSI X12, EDIFACT
Mapping templates for purchase order, invoice etc.
Payment
Protocol converter for OFTP / ISDN, VAN Access
Data format converter for EDIFACT, SWIFT
Mapping templates for payment orders, debit advice etc.
Industry specific EDI Adapters
Aerospace & Defense
Automotive
Chemicals
Consumer Products
High-Tech
Paper
Pharmaceutical
Retail
SAP NetWeaver Process Integration 7.1: Available Adapters and Adapter Modules
Handling EDI interfaces using Seeburger BIC modules
Handling EDI interfaces using Seeburger BIC modules
Regards
sandeep

Similar Messages

  • AS2 Adapter EDI scenario - question

    I am working on a EDI scenario, involving AS2 adapter.
    Could anyone tell me any steps to be done on ABAP engine.
    reg

    Hi Naveen,
    follow the below steps:
    1) First deploye the Std seeburger mapping provided by see burger on XI
    2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
    3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
    5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
    steps in IR and ID.
    In IR:
    You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
    In ID:
    This is the scenario for AS2
    Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
    Example of mapping:
    See_E2X_INVOIC_UN_D96A
    See_E2X_INVOIC_UN_D99A
    See_E2X_ORDERS_UN_D96A
    See_E2X_OSTRPT_EAN_D96A.
    1) After deploying mapping program.
    We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
    1)The value of the Agency field must be Seeburger.
    2)The value of the Schema field must be AS2ID.
    Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
    Configuration in adapter:
    Under the party identifiere tab
    Agency will be seeburger
    Scheme=AS2ID
    Name = WAN network no of the partner who is sending the file
    Sender AS2 adapter configuration:
    Few changes in the module parameter tab.
    localejbs/CallBicXIRaBean bic
    CallSapAdapter 0
    Module configuration:
    bic= destSourceMsg = MainDocument
    bic= destTargetMsg = MainDocument
    bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
    Receiver AS2 adapter configuration:
    When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
    1. Define the channel as a Receiver channel on the Parameters tab
    2. The last step ensures the module sequence is complete:
    Make sure the module ModuleProcessorExitBean does exist in the module sequence:
    Module Name=localejbs/ModuleProcessorExitBean
    Type=L
    Module Key=Exit
    • with the following module parameter:
    Module Key=Exit
    Parameter Name=JNDIName
    Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    You can refer my thread reply:
    Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
    Re: Seeburger AS2 adapter...
    Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
    AS2 adpater-- Configuration details for both SND and RCV.
    AS2 Sender Adapter -- Need few details.
    EDI-SEEberger-XI-IDOc-R/3
    flow of the data from EDi to SAp r/3 using seeburger:
    1) Data will be coming thorugh WAN or mailbox.
    2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
    3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
    4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
    5) Once you XML is generated then it will be used in MM
    6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
    Thnx
    Chirag

  • IDOC to EDI scenario

    Dear All,
    need your help on how to configure and deploy a scenario for a IDOC to EDI (856)  .  I believe this is like "IDoc to X12 - > X12 to EDI" using AS2 adapter.  BASIS has configured the B2B addon installation and I am not sure about the EDI part in this scenario..
    can you please inform what that the steps (A to Z) needs to be followed and would be great if example scenarios can be uploaded .
    Thanks
    Fernando

    Hi Fernando,
    I guess you're referring to this thread: IDOC to EDI scenario
    For that reason, please do close this one.
    Thank you.
    Dimitri

  • Xml to EDI without  any  EDI adapter!

    Hi ,
    can we do  <b>xml to EDI</b> without any EDI adapter like SEEBURGER or GENTRAN?
    and just with Conversion agent?
    if so ,would it be a xml to file scenario?please explain little about the process.
    thank you,
    regards,
    Babu

    Amir,
    I was trying to add some comments what I felt.
    I mean,with Conversion Agent we cant send or recieve EDI documents. and we can use it for just to get the structure of the EDI document as XSD with Conversion Agent which we want to use in mapping.And once we have structure for the EDI document we can use a file adapter and can generate XML files.
    And we do mapping only, if we don't have predelivered mapping( Seeburger provides some mappings for standard document sets).
    I am sorry ,if I am still unclear.
    and to your comments above
    >>"you may also use conversion agent from Itemfiled,it much like seeburger and i guess now its owned by SAP itself"
    Seeburger has lot of features than Conversion agent.
    Conversion agent just can get xsd from EDI structure and EDI structure from xsd,correct?

  • Business area and its sample scenario / example.

    Hi SAP GURUS,  please suggest ASAP.
    scope of business area with any simple scenario or example which we will used

    Hi,
    business area is an organizational unit within accounting that represents a separate area of
    operations or responsibilities in a business organization.
    In a client, you can set up several business areas to which the system
    can assign the postings made in all company codes defined in this
    client.
    Business Area Account Assignment
        Both revenue accounting in Financial Accounting and value postings for
        goods movements in Inventory Accounting can be represented separately
        for each business area.
        In the following menu options, you define the rules according to which
        the SAP System should determine the business area automatically.
        To do this, you allocate business areas to sales areas according to
        different criteria.
        Note
        A business area is defined in the module FI. You should therefore
        collaborate with the financial accounting department here.
        Default settings
        The standard SAP R/3 System contains three rules for determining a
        business area:
        o   Rule 1: Allocation of business area for each plant and division
        o   Rule 2: Allocation of business area for each sales area
        o   Rule 3: Allocation of business area for each plant and item division
    Regards,
    Sasikanth.Ch

  • XI receiving scenario example

    Hi Friends,
    I had searched on sdn for different scenario in XI , most of them are for sendin message out of system, but I didnt got any scenario which shows receiving of message from external system...
    So can you please provide some link where I can get receiving scenario example..
    Thanks ,
    Brijesh......

    Hi Brijesh,
    Any scenario involving XI will have always XI at one end as reciever and at another end as sender.
    Consider the simple Idoc to file scenario where you get Idoc into XI from any R3 system and XI is the receiver system for that R3 system.
    Similarly there are other scenarios (lets say SOAP to RFC)where you get SOAP requests from Third party system into XI via SOAP sender channel and then from XI Box to R3 via RFC receiver channel.
    You can refer to the link below for SOAP to SOAP scenario.  Invoke Webservices using SAPXI and search on sdn you will get many more examples.
    Thanks!

  • Message mapping challenge in IDOC to EDI scenario

    Dear PI message mapping experts,
    I'm a newbie in PI and facing a mapping problem using graphical message mapping.
    I'm in an IDOC (INVOIC.INVOICE02) to FILE (EDI) scenario.
    Here after is the mapping i need to perform :
    Source structure IDOC :
    <E1EDKA1> (0..99)
       <NAME1> A </NAME1>  (0..1)
       <NAME2> B </NAME2>  (0..1)
       <NAME3> C </NAME3>  (0..1)
       <NAME4> D </NAME4>  (0..1)
    </E1EDKA1>
    Target structure :
    <AccountingCustomerParty>  (1..1)
       <Party> (0..1)
          <PartyName> (0..unbounded)
              <Name>A</Name> (1..1)
          </PartyName>
          <PartyName>
              <Name>B</Name>
          </PartyName>
          <PartyName>
              <Name>C</Name>
          </PartyName>
          <PartyName>
              <Name>D</Name>
          </PartyName>
       </Party>
    </AccountingCustomerParty>
    I know i have to play with context and queues with stanard function or UDF but cannot succeed to do it.
    Could you please help me ?
    Thanks in advance,
    Alysee

    One approach out of available few ways to implement this:
    NAME1 - Exists - CreateIf - PartyName[0]
    NAME2 - Exists - CreateIf - PartyName[1] (Create deuplicate segment)
    NAME3 - Exists - CreateIf - PartyName[2] (Create deuplicate segment)
    NAME4 - Exists - CreateIf - PartyName[3] (Create deuplicate segment)
    Srikanth Srinivasan

  • Idoc to edi scenarios (mapping help is required)

    hi expects ,
        i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
    INPUT IDOC :
                        Name                         M/C     Min Use      Max Use        Description                                                                               
    INPUT*                                              M               1           1                                                                               
    Record EDI_DC40*                                 C               0           1                       Control Record                                                                               
    Record E2EDK01*                                  C               0           1                       Document Header General Data                                                                 
         Record E2EDK14*                                  C               0          12                       Header Organizational Data                                                                   
         Record E2EDK03*                                  C               0          10                       Header Date Segment                                                                               
    Record TEMP_DATE*                                C               0           1                       Temporary Date Segment                                                                       
         Record DEL_DATE*                                 C               0           1                       Temporary Date Segment                                                                       
         Record E2EDK04*                                  C               0          10                       Header Taxes                                                                               
    Record E2EDK05*                                  C               0          16                       Header Conditions                                                                               
    Record E2EDKA1*                                  C               0       99999                       Header Partner Info                                                                               
    Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info                                                                               
    Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info                                                                               
    Record TEMP_PAYER*                               C               0           1                       Payer Info                                                                               
    Record TEMP_CARRIER*                             C               0           1                       Carrier Info                                                                               
    Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info                                                                       
         Record TEMP_NOTIFY*                              C               0           1                       Notify Info                                                                               
    Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info                                                                               
    Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info                                                                               
    Record TEMP_CONSIGNEE*                           C               0           1                       Consignee                                                                               
    Record TEMP_SHIPPER_INFO*                        C               0           1                                                                               
    Record E2EDK02*                                  C               0          10                       Header Reference Data                                                                        
         Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02                                                                               
    Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING                                                                               
    Record E2EDK17*                                  C               0         999                       Header Terms of Delivery                                                                     
         Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms                                                                    
         Record E2EDK18*                                  C               0          99                       Header Terms of Payment                                                                      
         Record TEMP_TERMS*                               C               0           1                                                                               
    Record E2EDK35*                                  C               0          10                       Additional Data                                                                               
    Group E2EDKT1:2*       
    OUTPUT FIELD:
    Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION                                       
         Segment B2A*                                     C               0           1                       SET PURPOSE                                                                               
    Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment CUR*                                     C               0           1                       CURRENCY                                                                               
    Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE                                                         
         Group DTM_GROUP*                                 C               0           1                                                                               
    Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE                                                                               
    Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE                                                                               
    Segment DTM:3*

    Hi,
    To do the mapping,,,,even you can go for graphical mapping....
    But some of the context handling issues you need to deal with,
    like....
    1.Never map set context of source fields to element level but Segment level.
    2. Always you need to check for qualifiers while mapping it to Traget field.
    Thanks & Regards
    Akshay.
    Dont Forget TO Give Points.

  • EDI Scenarios

    Hi,
    With regarding to EDI scenarios with XI and seeburger, would like to get input on the following.
    As the technical stuffs of conversion can be done with seeburger, is it easy or hard to prepare the mapping specifications from EDI to idoc xml.
    Do we require functional knowledge to prepare EDI mapping?
    I believe as most of the standards are available in internet, it is going to be just one to one mapping .
    Do let me know the challenges ahead on preparing edi mapping.

    Krish,
    My experience says it is a combination of both funtional and techincal experience required. Technically you can google it and can know what each field. But functionality wise you may need to take the help of functional consultnat because of all the looping in the EDI. If you know that it should not be a big problem in writing the mapping specification.
    You can find some techincal help here :
    http://www.tsilogistics.com/edi.htm
    Regards,
    ---Satish

  • Implementing an EDI scenario with XI

    Hi,
    I need to implement an EDI scenario with a non SAP system. I would like to know what are the "components" that I should have in order to acomplish the task ?
    (how is it different from an ALE scenario)
    I'm new to EDI ! (so take is slow...)
      Thanks, Nir.

    Hi,
    I need to implement an EDI scenario with a non SAP system. I would like to know what are the "components" that I should have in order to acomplish the task ?
    (how is it different from an ALE scenario)
    I'm new to EDI ! (so take is slow...)
      Thanks, Nir.

  • When do we use CE plan operators in HANA? any specific scenario?

    when do we use CE plan operators in HANA? any specific scenario?

    With current versions of SAP HANA you can avoid using CE-functions completely.
    There's usually no need to choose them over plain SQL code,
    - Lars

  • Is there any blog or examples to handle the errors without using ESB tool kit.

    Hello,
    I have been trying to work with error handling since last week but I dont understand how to construct the error message. Is there any blog or examples to explain handle the errors step by step from scratch without using ESB tool kit.Can anybody help me out.
    Thanks in advance.

    You can use option 3 to construct the error message inside orchestration.
    Before using a BizTalk XML Message inside an orchestration, it must first be constructed. In fact this is just populating the message with XML. If there is an attempt to use this message before it is constructed, the above error will come. Some messages
    come pre-constructed, such as messages that originate from a send port
    There are several ways to construct a message inside an orchestration:
    Create a new message from an existing message using BizTalk map
    Assign one message to other(i.e. creating a copy of an existing message)
    Creating a message with the help of a System.XML.XMLDocument variable
    We have to first declare an orchestration variable of type XmlDocument. Then in a message assignment shape, we need to do something like this:
    myxmlDoc = new XmlDocument();
    myxmlDoc.LoadXML("<somexmlhere></somexmlhere>")
    myMsgBeingConstructed = myxmlDoc;
    Abhijit Mahato - Microsoft Community Contributor 2011 - MCTS BizTalk Server blog: http://abhijitmahato.wordpress.com/ Please "Mark as Answer" if Post has Answered the Question

  • IDOC to EDI Scenario using Seeburger....

    Hi Experts,
    On the Scenario IDOC to EDI when will I use As2 adapters or SFTP adapters of seeburger or just a simple FIle adapter?
    and any idea what are the modules I need to import on my comm channel using file adapter?
    Thanks.

    Hello
    Check this blog: /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    Regards
    Mark

  • EDI Seperator Issue for INbound EDI Scenario

    Hi Experts,
    Am using latest service pack and SP12 and patch 5 it seems.
    Still am getting same error.
    Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'fbesfd4b25331eabe67a1d04ec4acf': Catching exception calling messaging system
    I configured simple scenario.
    I have set up the 2 ID flows :
    - Partner 1 (Sender File) > (Partner 2) Receiver EDISeprator (didnt used any conversion modules)
    - Partner 3 (Sender EDISeparator with Edifact Module) > to SOAP sending B2B XML to another PI system.
    Done B2B **** Pit file Association.
    Tested in B2B COckpit and it is working fine but working in E2E
    Also note that this is not a Custom EDI. This is just Order D93A Standard message file containing multiple Orders in same file.
    Also let me know one thing Is it required to make KEY Associations for standard EDIFACT Structure Secnario as well?
    I understand from the above error that is able to lookUP the 2nd flow EDI Sender Channel ID but it is unable to deliver/despatch the message content to that flow.
    KINDLY HELP ME>

    Hi Dimitri,
    I tested again now with changing control key association.
    am getting below error::
    Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'a9e6939add043c39883683175abea3ba': Catching exception calling messaging system
    I delcared key associations for both flows.
    FILE-->EDI Seperator and EDI Seperator to SOAP.
    Could you please review it and guide me?
    Regards
    Amarsrinivas Eli

  • Change in background MRP time with EDI scenario for sale order booking

    Hi All,
                  I have a scenario where  Sales orders are booked through EDI. Now because of some reasons duplicate orders are getting booked in SAP. Now users are  manually deleting the duplicate sales orders.
              Now MRP is running at Night with  duplicate orders in background. So users wanted to run MRP after deleting the duplicate SO.( i.e. during office Hrs)
             Should i change MRP timings to suit the user requirement? what will be the pros & cons if change MRP timings.will it throw errors in EDI.
    Thanks & regards,
    dev

    Dear,
    If you change the MRP run time for periodic job in MDBT it would not affect any where only system will create the procrument after MRP run only.
    Please try to find out the reason why  duplicate orders are getting booked?
    Regards,
    R.Brahmankar

Maybe you are looking for

  • My laptop has no disk drive, so how do I install Photoshop CS5 without using a external disk drive?

    I've recently bought a laptop that does not have a disk drive. Is there any way to install Adobe Design Premium CS5 that I bought as a Disk last time without buying an external Disk drive?

  • FAST Entry- A/P

    Hi Gurus Pls let me know whether we can post different vendor invoices and payments at a time, but document numbers should be different for every entry. eg:-  Rent payment Vendor a/c DR. [many vendors are there- need to post as if one    document but

  • Help needed with GTS questionare

    Hello SAP gurus I am a SAP SD consultant looking for an opportunity to get into SAP GTS. Could someone please help me with the sample interview questionnaire. I have the basic  knowledge of what SAP GTS can do and what functions it performs but reall

  • Editable regions in templates. How do I edit the CSS in a new page from the template?

    I am new to Dreamweaver and Web design. I have made a template and have two editable regions they work fine. When I create a page from this template, I can't edit the CSS. What do I need to do to edit the div tags that are specific to the editable re

  • Statisticla Internal Order posting

    Hi all, We have created few statistical internal orders..for Controlling Area CO1. Can we use these internal orders for the cost centers that are created in a different controlling area C02 ? If we cannot, is there a way we can change the Controlling