EDI challenge

Hello ABAP Gurus,
Implementing EDI is in itself a very big task. I guess the biggest challenge in implementing EDI is testing.
How do you test with someone you may never meet? How do you do your own testing without sending data to your partner? How do you differentiate between a test message and a real one?
Can somepne please foucs some light on my above asked questions ?
Answesr will be surely awarded
Regards,
Tushar.

Well during initial stages of your ALE setup, WE19 is a good tool. You can use it to quickly create temporary idocs and process these for inbound processing. You can even use ABAP debugging to run through the inbound process function module.
For outbound processing, initially you should use the file port in your partner profile for outbound idocs and direct the file port to some temp directory on your app server. This way you can have the idoc in file, which you can easily read again to validate the output and fields in idoc.
Also if you doing an SAP/SAP integration, Idoc and SAP versions are very important. This fact is sometimes overlooked and end result is mysterious system behaviour. Places to look for these are (1) while defining ports, transaction code WE21(you will see radio buttons for different SAP versions) and in you partner profile transaction code WE20 look for field called “Seg. release in IDoc Type” so make sure that you are persistently sending correct versions of Idocs for a smooth system behaviour.
You mentioned a very interesting point that how do you test with someone you never meet, being involved in some situations similar to these all I can suggest is use email frequently. In the initial setup phase it is very important to build trust with your EDI partner because initially both parties are very sensitive about errors ( you will hear things like “it is OK from our side, there is a mistake in your system” etc) So it is important that you present yourself as someone who is helpful and sincere. Always try to work and suggest possible solutions even if the problem is not directly related to your system.  From a more technical side, clarify in the initial stage of project about the technical terms used. For example May be what they are calling plant in there system is actually a company code or warehouse number in your SAP system so make extra effort during the mapping phase.
I hope this will be helpful to you although I couldn’t put it in a more organized way
Cheers

Similar Messages

  • EDI Challenging Question

    We are using EDI 860 for PO Change.
    I wanted to know which field from IDoc should we use to map the change qualifiers code picked up correctly.
    For example, if we make changes in line item of PO, it should pick up CA qualifier.
    If we add new line item in existing PO, it should pick up AI qualifier.
    So for which field these change response types code should be mapped so that vendors would know what exactly we are changing in PO.
    Currently we have mapped ACTION field from IDoc to these qualifier, which is not working. It is giving 001 value all the time which is mapped to AI code, so even if we do No Change in PO or just change the quantity then also it is picking up AI.
    Please let me know if you need more elaboration.
      CA
    Changes to Line Items
    AI
    Add Additional Items
    NC
    No Change
    Message was edited by:
            RS

    > Can you please tell me what is the way out for it?
    > How can we acheive it..
    > also send me info on [email protected]
    >
    > Thanks

  • EDI Challenges

    Good People
    Will you- Gurus-help me or explain to me these 2 activities:::: developing inbound and outbound function modules, and implementation of new IDOC types?
    Rash

    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

  • 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

  • Update "Delivery Completed" Indicator in PO Item via EDI

    Hello
    We have another challenging task regarding purchase order confirmations that we would like to tackle (SAP Release is ERP 6.0).
    The 2 partner in our scenario are distribution companies (= DC) which order goods and production companies (= PC) which deliver the goods:
    (1) DC sends purchase oder via EDI (ORDERS IDoc)
        -> creates sales order in ERP of PC
    (2) PC splits sales order into multiple deliveries.
       Each delivery is sent as outbound DESADV
       -> creates inbound delivery in ERP of DC.
    (3) At some point the PC has completed the sales order
       yet it is possible that less was delivered than was ordered
          (i.e. we can have under-deliveries).
    Now the question is:
    How can the PC transmit the final information "SalesOrder completed" implying that the "Delivery Completed" indicator in the PO items should be updated (= 'X')?
    My assumption is that we need to look at the sales order (ERP of PC) because this is the document which "collects" the information from all the split deliveries.
    Any help related to understanding how the (standard) business process would look like and how to translate this into a technical solution (EDI / IDoc) is more than welcome.
    Regards
      Uwe

    Hello Uwe,
    As you mentioned, I tried to check with the Workflow solution by tracking the events through Business Object BUS2032 (Order) or LIKP (Outbound Delivery) but failed to get successful results.
    Problem with BUS2032, event CHANGED is that it doesn't get triggered when the Header/Item level status changed during delivery Processing. 
    While using BO- LIKP (Outbound Delivery Processing), Events - Changed,Created, I am successful in triggering the event, but the problem with BO-LIKP is that, it does not have the item level details in the ATTRIBUTES list.  To get the balance quantity available for order line item (mentioned in my earlier reply)Item details are necessary to findout the Reference Sales Order & Line item.  With this, the Option of Triggering of Workflow using LIKP didn't give the required result.

  • Common Issues in IDOC/EDI

    Hi can some one please tell me the most common issues faced while setting up output detrmination through EDI in SD and also most common issues faced once EDI is configured..Please dont post Output detremination configuration process as i am aware of it.I am Concerned about the challenges and issues faced while setting up EDI and issues once EDI is configured (In SD point of view) .
    Thanks,
    Babu.
    Edited by: babu madina on May 29, 2008 1:57 PM

    Hi San Rao,
    1.Has the data request reached the SAP R/3..?
    -check for the queue entries in the  CRM out bound- SMQ1.
    -check the destination for R/3 or ECC in CRM-SM59.
    2.Has the data been extracted in R/3..?
    -check for the short dumps in ST22 in R/3
    3.Has the data been sent to the CRM..?
    -check for the queue entries in the qRFC out bound queue- SMQ1.
    4.If the the block number in the down load monitor shows 0 blocks in R3AM1 check the following
    - check the destination for CRM in R/3- SM59.
    -check which consumer is used for the object in the object management.
    -check the table CRMCONSUM in R/3 if the consumer is active.
    -check for the given consumer in table CRMFCPAR in R/3 if an entry exists for the object.
    5.Has the data reached CRM..?
    -check for the queue entries in the CRM inbound queue-SMQ2
    -check in the flow trace SMW01 if there are Bdocs in error state.
    -check for the short dumps in ST22 in CRM.
    6.Check the table CRMFCPAR
    -Table CRMFCPAR is valuated in the way that an entryfor a specific objectwill always be taken if it exists. If no specific entry exists, an entry with the object name ' * ' will be taken.the same goes for load type. If no entry exists, the initial load will be roll back to SMQ1 in CRM with a sysfail saying that no CRM is connected.
    -If the flag 'DISCARDDAT is set to 'X' , no data is sent.
    7. Status of the queue entries
    -Queue name for a initial load start with R3AI.
    -If queue entries exist in status READY, check SMQR (for SMQ1) orSMQR(for SMQ2). If the queue entries exists with the status SYSFAIL, analyse the error and restart the queue.
    -If queue entries exists in the status 'RUNNING' wait for the load to finish.
    -Never delete a queue entry manually.
    Reward points if its helpful.
    Regards
    Nadh.

  • EDI Mapping

    Hi,
    As my client is implementing EDI through a trusted link, they had asked me to take care of the mapping section along with the development of interfaces.
    As generally the middleware or translator people would do the mapping processes, it is totally new for me.
    Please advise me in this regard where to start and what is the my job into this. 
    Do i have to map the incoming or outgoing edi standards to idoc segments.
    If so, what are the all things i need to know and do.
    As i have ample time, it would be nice for a quick start into it.
    Please help me in this regard.
    Thanks in advance,
    Anandh.B
    Points would be awarded for everyone ............

    Anandha,
    As you mentioned, EDI mapping is typically done using a middleware tool or EDI Translator.  Are they asking you to do mapping in ABAP or is there another tool you are going to use?
    If you are going to write ABAP programs to do your mapping you have a big challenge ahead of you.  You will need to become familiar with whatever EDI standards you will be mapping from.  These standards will have the layout of the messages that you will receive.
    If you are going to code all of this in ABAP you don't necessarily have to go to IDOCs however it can be very helpful when loading data.  By using SAP's IDOC technology and processing you have better traceability into the transaction posting in your system.
    In general this is what you will probably need to know:
    1.  Which EDI messages you will need to translate
    2.  Which IDOC types those messages correspond with
    3.  The structures of both the EDI messages and IDOCs
    4.  Setup of SAP IDOC system.  (Execute area menu WEDI from the main screen in SAP)
    5.  Set up of the application data for IDOC processing - particularly in the outbound - which partners will be recieving which messages
    I am sure there is a lot more but this will hopefully get you started.
    Chris

  • 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

  • Difference btw idoc ale and edi

    Hi all,
    I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
    Also do send some materials for the same.

    Hi,
    ALE (Application Linking and Enabling)
    Ale Technology is SAP’s technology to support distributed yet integrated processes across several SAP systems.
    Distributed Process:
    A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
    Need for Distributed Process:
    • Business in Different Geographical Locations.
    • Non availability of dedicated network.
    • Cultural and language differences in Geographical locations.
    • Running of Mission-critical Applications (Like Maintenance downtime etc.).
    • Separate up gradation of Modules.
    Distributed SAP SYSTEM – CHALLENGES
    • A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
    • Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
    • Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
    • Receiving systems that can handle their own problems and not tie up the sending system.
    • Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
    • A sound technology and methodology that can be used in all distribution scenarios.
    SAP Distributed environment:
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    • Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    • IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    • Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    • Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    • Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    • Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    • Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    • Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).
    • IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    • Basic integrity check: A basic integrity check is performed on the control record.
    • Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    • Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    • IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    • IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
    IDOC:
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm]
    [http://www.sappoint.com/presentation.html]
    [http://www.allsaplinks.com/idoc_search.html]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://www.erpgenie.com/sapedi/idoc_abap.htm]
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    [Re: How to create IDOC;
    Check below link. It will give the step by step procedure for IDOC creation.
    [http://www.supinfo-projects.com/cn/2005/idocs_en/2/]
    ALE/ IDOC
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.sappoint.com/abap/ale.pdf]
    [http://www.sappoint.com/abap/ale2.pdf]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sappoint.com/abap.html]
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs]
    go trough these links.
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.sappoint.com/abap/ale.pdf]
    [http://www.sappoint.com/abap/ale2.pdf]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
    [http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sappoint.com/abap.html]
    [http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    [http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
    [http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    [http://www.allsaplinks.com/idoc_sample.html]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [www.sappoint.com]
    --here u can find the ppts and basic seetings for ALE
    [http://sappoint.com/presentation.html]
    [www.sapgenie.com]
    [http://www.sapgenie.com/ale/index.htm]
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    RFC:
    RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
    and you will be passing an Import parameter DESTINATION to it.
    Other code and usage will be similar to any fun module;
    Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
    Refer this link:
    [http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
    check out the following link it might help you
    [http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
    EDI:
    Electronic Data Interchange
    Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
    Refer
    [http://www.erpgenie.com/sapedi/index.htm]
    [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]
    EDI FLOW :
    Here is some thing which helps you and here the purchase order is taken as example too..
    Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
    What parts of the business cycle can be supported by EDI?
    Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
    How does EDI get started?
    EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
    What is the flow of EDI?
    The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
    check this.
    [http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
    [http://www.sapgenie.com/sapedi/idoc_abap.htm]
    [http://www.sapgenie.com/sapedi/index.htm]
    [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]
    [ALE / IDOC / RFC / EDI]
    [SAP ABAP and EDI/ALE/IDOC]
    [Re: IDOC/BAPI/ALE/EDI]
    Regards,
    Dhruv Shah

  • EDI maps migration to B2B/BPEL?

    Hi,
    Is there any feature in B2B/BPEL which can help me migrate existing EDI ANSI X12 Harbinger maps to BPEL/B2B XSL format?
    or
    Is there any way other than manual to migrate these maps.
    Thanks,
    Sachin Sutar

    Hello Sachin,
    If you are using the XSLT maps in the Harbinger you can directly make use of the same in BPEL as long as the data feed to the map in BPEL Process is same as the feed in your harbinger System.
    Another challenge is how to you get the data to be transofrmed into the BPEL process, you might have to look at either FILE/FTP/JMS or any of the technology adapter in BPEL.
    HTH. Let me know.
    Rgds,Ramesh

  • EDI over WCF request-response port - how to catch failed messages and send response over a 2 way port

    I'm using BizTalk 2009.  I've written an orchestration for accepting 270's and returning 271's, and another for 276's and 277's.  The incoming and outgoing EDI stream is wrapped in XML.  I've published the schema using the WCF publishing wizard,
    and I am using the WCF-WSHttp adapter.  I have custom pipeline components to unwrap and wrap the XML, and to handle the NACK generated by the adapter.  Everything works fine if valid EDI is received. 
    However, I'm challenged with handling failures from the EDI disassambler.  The specification I've been given is to return a 271 or 277 in all cases (or as many as possible).  What I would like to do is catch the failed message, generate a (271
    or 277) response, and return that response over the 2-way port.  I know how to enable failed message routing and how to subscribe to the message if it were to come in over a one-way port.  It seems that this cannot be done when the message comes
    in over a 2-way port. 
    Any suggestions on how this can be done?

    I should have mentioned that turning off as much EDI validation as I can in the pipeline is already part of my approach.  However, to my knowledge, there are some validations (such as incorrect segment count in the SE) that cannot be disabled. 
    Regarding the TA1/997/999 - because this is a real time transaction, I'm not generating any.  Still, to take your suggest, I decided to generate a 997, thinking I could at least subscribe to it and if the 997 indicated a failure, to
    generate the response (in the form of a 271 or 277) that my trading partner is expecting.  What I found was that the 997 was being returned through the send pipeline of the 2 way port, EVEN WHEN I set RouteAckOn2WayPort to False on the receive pipeline! 
    This produces even more work for me, because now I have to "eat" the acknowledgement so that the 271 or 277 can get through.

  • EDI Clearinghouse using BTS 2013, need ESB toolkit ?

    Hi ,
    We are thinking of building EDI Clearinghouse for Third Party Health Care Administrators (TPA), Payers and Individual Providers with HIPAA compliance. Please guide me
    1) Is BTS 2013 is right choice to build clearinghouse?
    2) Do we need to use ESB toolkit in order to make new parties addition to the clearinghouse seamless and not manually creating parties, send ports and receive ports each time we add new parties in to the system?
    3) Link to any proven clearinghouse architecture using BizTalk that is running in production
    4) Is Microsoft Azure BizTalk Services (MABS) is ready to take up all the cloud challenges that Clearinghouse would throw to it ?
    Thanks in advance
    Vivek

    Hi Vivek,
    1) Is BTS 2013 is right choice to build clearinghouse? – BTS 2013 is
    alsoproduct which can handle clearing house cases. BizTalk has all the capabilities to handle the integration and add different
    parties/clients dynamically. Many of the clients are using BizTalk specific to clearinghouse and HIPAA. But if you’re evaluating another products and you have a specific requirements which you want to implement in clearinghouse and HIPAA and see which tool/product
    can better server that purpose.
    2) Do we need to use ESB toolkit in order to make new parties addition to the clearinghouse seamless and not manually creating parties, send ports and receive ports each time we add new parties in to the system? –
    ESB toolkit does provide options to add parties seamlessly. I think you’re still in product/tool evaluation phase. First check whether BizTalk as product can handle all your requirements before considering ESB toolkit
    on top it. If BizTalk can offer all the features you look for, then evaluate the feature with ESB toolkit and see how best it can fit in your solution.
    3) Link to any proven clearinghouse architecture using BizTalk that is running in production.  -
    You got to ask this question to Microsoft. As them for any proven use case. BizTalk product team is very responsive team, I’m sure they can guide you better. Create a support call or contact Microsoft Sales. If I
    remember “BizTalk 2013 EDI for Health Care” book has some reference around ClearingHouse. Have a check
    4) Is Microsoft Azure BizTalk Services (MABS) is ready to take up all the cloud challenges that Clearinghouse would throw to it ?
    - Again it depends on your requirement. When you consider MABS for clearinghouse you also need to consider about security implication involved in it. So I’ll give a better thought about this. Use MABS where it actually
    required. May be in hybrid scenario but after ensuring the security implications around it.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Regarding EDI and EAI

    Hello Masters,
    What makes exact differecnce between the EDI and EAI. Please if possible take simple example and explain in simple manner.
    Thank You

    Hi Ravi Kumar,
    EAI:
    Enterprise Application Integration (EAI) is defined as the uses of software and computer systems architectural principles to integrate a set of enterprise computer applications.
    Supply chain management applications (for managing inventory and shipping), customer relationship management applications (for managing current and potential customers), business intelligence applications (for finding patterns from existing data from operations), and other types of applications (for managing data such as human resources data, health care, internal communications, etc) typically cannot communicate with one another in order to share data or business rules. For this reason, such applications are sometimes referred to as islands of automation or information silos. This lack of communication leads to inefficiencies, wherein identical data are stored in multiple locations, or straightforward processes are unable to be automated.
    Enterprise application integration (EAI) is the process of linking such applications within a single organization together in order to simplify and automate business processes to the greatest extent possible, while at the same time avoiding having to make sweeping changes to the existing applications or data structures. EAI is the u201Cunrestricted sharing of data and business processes among any connected application or data sources in the enterprise.u201D[1]
    One large challenge of EAI is that the various systems that need to be linked together often reside on different operating systems, use different database solutions and different computer languages, and in some cases are legacy systems that are no longer supported by the vendor who originally created them. In some cases, such systems are dubbed "stovepipe systems" because they consist of components that have been jammed together in a way that makes it very hard to modify them in any way.
    EAI can be used for different purposes:
    Data (information) Integration: Ensuring that information in multiple systems is kept consistent. This is also known as EII (Enterprise Information Integration).
    Process Integration: Linking business processes across applications.
    Vendor independence: Extracting business policies or rules from applications and implementing them in the EAI system, so that even if one of the business applications is replaced with a different vendor's application, the business rules do not have to be re-implemented.
    Common Facade: An EAI system could front-end a cluster of applications, providing a single consistent access interface to these applications and shielding users from having to learn to interact with different applications
    EDI:
    An inter-company, application-to-application communication of data in standard format for business transactions, Electronic Data Interchange (EDI) is a set of standards for structuring information that is to be electronically exchanged between and within businesses, organizations, government entities and other groups. The standards describe structures that emulate documents, for example purchase orders to automate purchasing. The term EDI is also used to refer to the implementation and operation of systems and processes for creating, transmitting, and receiving EDI documents.
    if found worth pls do the req
    Thanx
    Sampath

  • Automatic PO creation through EDI

    Hi experts,
    Please clarify me on the setup of creating PO's thru EDI in Purchasing automatically once PR is created in the system.
    My client is more or less a trading company. They buy from vendor & sell to their customer, like third party order process.
    So they create Sales Order & then PReq is created through ME57 & then they create PO through ME59.
    They want to create PO's automatically thru EDI as this can speed up the process so as the vendor is also looking for creating SO in their BaaN system automatically.
    I have configured the EDI setup for creating PO manually, meaning when I create manual PO the idoc xml file is ready for transfer.
    But I am looking for the steps so that once they create the PReq, EDI should automatically create PO in SAP & the idoc should be ready for transfer.
    Please suggest if this can be done thru any BAPI or BDC programs.
    Thanks in advance !
    Priyadarshini

    Hi Krishna,
    This is for automatically creating normal PO thru PReq. Since I have setup the EDI configs for creating PO thru manual process  thru Me21N then idoc gets generated.
    But my client is looking for the idocs to be generated automatically once the PReq are created thru Me57.
    is there a way?
    Rgds,
    Pri

  • EDI for creation of Sales Order and sending copy of Invoice

    Hello Experts,
    I am working on EDI. We have a scenario, where the purchase order created in the 3rd party system has to be converted into a sales order in our SAP system.
    Then, the regular flow would follow uptil delivery and creation of invoice in SAP.
    We have to send a copy of this Invoice back to the 3rd party system.
    So, in effect, we would have EDI at two points, while capturing the PO from the 3rd party and another when sending a copy of the Invoice back to the 3rd party.
    Please advise on how to go about implementing EDI in the above mentioned scenarios.
    Regards,
    Divyata

    Use EDI 850 Process code ORDE FM IDOC_INPUT_ORDERS for PO (Inbound)
    use EDI 810 Process code SD09  FM IDOC_OUTPUT_INVOIC for Invoic (Outbound)
    Edited by: srini korada on Jun 9, 2011 4:51 PM

Maybe you are looking for