Regarding EDI----XI----IDOC

Hi All,
I have One Requirement here is that
My Client's Customer will send EDI Formated Data (ANSI Type ) to Client. That Data has to be Posted into SAP R/3 Database. So here We are Using XI For that .
Can Any One Explain me what could be the Scenario here And
How to Handle this ANSI Data Format.
Regards
Babu

Hi
Scenario is EDI-XI-IDOC
Data Will come in the Form of ANSI
1) I Will Use IDOC Adapter in the Receiver End
2) For Sender Side Which Adapter I Need to Use & How to do the Conversion From ANSI Format to XML ??????
Can You Provide Any Real time Scenario Or Any thing Which meets this Requirement.
I am Still in Confusion How this ANSI Data Will be Converted into XML Either it Can Happen in Seburger Adapter OR in XI Also
Can You Expalin me How this Conversion in Detailed
>>>>>>>>>>>>>>>>
if you are getting the data in the format like ANSI then you have to first create the XML message with the help of the BIC mapper.
the BIC mapper is basically used to convert the EDI message into the XML message. to convert the EDI message into XML message ypu have to create the mapping using the option createE2xmapping in the BIC mapper.
the mapping that will be generated using the BIC mapper have to be deployed on the server.
and in the adapter you have to used the same mapping name that you have deploy on the XI server in the module tab of the adapter.
if you still face the problem please reply me back.
Thanks
Rinku

Similar Messages

  • ALE, EDI and IDOCS

    Hi
    I am learning some stuff on ALE,EDI and IDOCS... are there any good sites which gives clear step by step procedure for the above.
    Thanks in Advance.
    Sudhi

    Hi Sudhi
    You can find details on SAP courses from your country's sap.com site. You can find links from http://www.sap.com/contactsap/countries/index.aspx .
    Also some Education Partners of SAP give courses. Some info about these will also be there...
    Regards...
    *--Serdar

  • ALE , EDI and IDOC with MM??

    hii
    What is ALE, EDI and IDOC in SAP??
    How its linked with MM??
    Explain the above things with example
    Thanks

    Hi!
    IDOC = Intermediate Document
    IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
    For more detailled information look in SAPNET under
    http://service.sap.com/EDI
    For exapmle in purchasing:
    The IDoc message type ORDERS is used to send a purchase order to a vendor.
    EDI = Electronic Data Interchange
    EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
    Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
    In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
    Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
    If the partners have agreed using a special EDI standard, mapping between IDoc and  the  EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
    If both systems use SAP software, there is usually no need for mapping  (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
    If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
    For example:
    Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
    ALE  = Application Link Enabling
    ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
    To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
    With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
    Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
    For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
    Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types  for distribution of master data are:
    MATMAS (ARTMAS in retail system) for material master
    CREMAS for Vendor master
    INFREC for  info record
    SRCLST for source list
    COND_A for conditions of info record
    SRVMAS for service master data
    Technical documentation to ALE can be found by path:
              Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
    The most important Transactions for testing Idoc:
    WE02 Display IDOC
    WE05 IDOC list
    WE19 Testing IDOCs
    BD87 Status Monitor for ALE Messages (reprocess)
    Notes:
    456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
    536411 Sample scenario for ALE contract distribution (only internally released)
    I hope I could help you fruther
    Best regards
    Erika

  • Conversion Agent -   (EDI - XI - IDOC)   -  Help

    Hi Experts,
    I am working on the scenario (EDI - XI - IDOC)  using Conversion Agent for Converting EDI data into XML.
    I am facing many problems in Real Time,  can any one who has already worked on the same scenario  send me complete scenario with screen shots,
    I need immediate help, really it is very urgent for me.
    Regards,
    Study SAP

    Hi Kishore,
    Thanks for your reply, We are using Standard IDOC Orders05 and EDI message ANSI X12 - Message Type 850 for Purchase Order.
    Posting EDI Data of Purchase Order in R/3 Sales Order as INBOUND Message.
    Using Conversion Agent Parser for the same and deployed this project at Integration Server in ServiceDB Directory.
    The Conversion Module CMTransformBean is also deployed at XI Server.
    When we are puting file at FTP Server, our XI System is not picking up file while using Conversion Agent Module,
    while it is picking up without conversion module successfully.
    Please help,
    Regards,
    Study SAP
    [email protected]

  • Roll Out,EDI,ALE,IDOC,BAPI

    HI FRNDS, HOW R U
    would u plz send me about the ROLL OUT means,
    what is mean of EDI,ALE,IDOCs&BAPI.
    what is the difference of these things& what is the use of these things
    thank u
    with regards
    nagesh

    Hi
    Roll out- Same client is having business in different countries.Instead of customizing again for the countries, we can copy the customizing from the parent country and configure all related to the country specific settings.
    EDI-Electronic Data Interchange (EDI) is about doing business and carrying out transactions with your trading partners electronically. EDI covers most things that are traditionally done using paper-based communication.
    ALE-ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
    ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
    ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
    The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
    ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
    BAPI -BAPIs provide a stable, standardized method for third-party applications and components to integrate into the Business Framework. These interfaces are being specified as part of SAP's initiative with customers, partners and leading standards organizations. Also, SAP has implemented the emerging Object Application Group (OAG) specifications with BAPIs.
    IDOC-IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
    Assgn points if useful.
    Regards
    Vardhini

  • EDI and IDOCs

    Hi all!
    I have to work on EDIs and everything is setup at my client(incoming invoice 810 , inbound and rejection notice 864(outbound) ….) and I have to deal with the issues that may come up regarding EDI s
    Could please someone send me the documents on EDI,IDOCs and also let me know what kind of issues we get with EDIs and what we need to do if we get an issue with EDI( like how to see the IDOC error message , researching where its going wrong , correcting it and reprocessing.. etc..)
    I will be really thankful, if someone could help me regarding this.
    Points guaranteed
    Regards.

    Hi,
    Good evening and greetings,
    You can use the TCode WEDI, which deals only with the IDOC and EDI...Normally the major error is failure of processing and you can reprocess using the T.Code BD87 and also check for the configuration in WE20.
    Please reward points if found useful.
    Thanking you,
    With kindest regards
    Ramesh Padmanabhan

  • What is DME,EDI and IDOCs, and anybody can tell the differences among them

    Hai
    I would likt to know in detail exactly how does these DME, EDI and IDOC do work and in what way they serve the purpose of meeting the payment requirements.
    I appreciate the early response and I will extend my Gratitude in advance.
    Regards,
    Akash Narayana

    Hi Akash,
    The
    Data Medium Exchange (DME) Engine enables you to define file formats that meet the requirements of your financial institution. By doing so, you model an externally defined bank format in the R/3 System, which allows you to send or receive data in the form of DME files in this format.
    The ability to define these formats in the R/3 System is particularly important as there is no worldwide or regional standard format. In some cases, no country standard exists and the file must comply with bank-specific standards. Covering such numerous and varied local format requirements is very difficult in standard software, but the DME Engine now enables you to define your particular local format yourself – without any ABAP programming knowledge or coding. With this Customizing tool, in the form of a graphical editor, you can define new formats flexibly and, as format requirements change, modify existing ones efficiently.
    Integration
    Once you have modeled an external file format as a format tree in the DME Engine, calling applications can use it to:
    · Generate an outgoing DME file as a flat file or an XML file
    · Convert an incoming DME file to a format that the R/3 System can process
    Features
    The system comes complete with predefined format trees, which represent the file format requirements in a number of countries.
    You can also transport format trees to other systems, or alternatively upload and download as XML files.
    Electronic Data Interchange (EDI) is a set of standards for structuring information 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.
    Despite being relatively unheralded, in this era of technologies such as XML services, the Internet and the World Wide Web, EDI is still the data format used by the vast majority of electronic commerce transactions in the world.
    IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions. 
    I hope the above helps.
    Do not forget to award the points please.
    Regards,
    Jacob

  • Urgenthelp on edi and idocs

    Hi experts,
    Can any provide me with simple and easy document(not pdf) i.; .doc for edi and idocs with screenshots and steps.
    Points will be rewarded strictly on basis of first come first and .doc format only.
    Regards,
    Ameet

    Hi,
            Creation of IDoc
    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.
    Create IDOC Type
    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 the link...
    http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
    http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
    Chk the links below...
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://www.erpgenie.com/sapedi/edi_sap_training.htm
    <b>Reward points</b>
    Regards

  • Seeburger EDI to IDoc

    Hi,
    The actual payload is not getting generated in the EDI to IDoc scenario.
    The acknowledgment is getting generated.
    What could be the possible error?

    Anu,
    is your mapping determined automatically or are you explicitly stating the mapping name in your
    module configuration?
    If you set mappingName to Auto BIC tries determine the correct mapping by looking at the
    the UNH segments, e.g. UNH1ORDERS:D:97A:AA'. If your mapping has been labeled
    differently in the Mapping Designer, for instance E2X_ORDERS_UN_D97A the system
    won't be able to find the mapping and therefore you won't get any payload.
    As I suggested before try using the parameter u2018logAttIDu2019 Value u2018ConverterLogu2019 in your
    module chain that will most likely tell you what the problem is.
    Sven
    Edited by: Sven Buttler on Jul 9, 2010 10:26 AM

  • In EDI to IDOC or Idoc to EDI can we go for Dynamic recevier determination

    Hi all
       I am doing an EDI to IDOC scenario involving SEEBURGER( AS2) adapter .can we go for extended receiver determination
    Regars
    Saurabh

    Saurabh,
    You can not use Extended Receiver Determination coz AS2 connection is like point-to-point connection which requires AS2 id of both sender and receiver. Therefore you can not use the Extended receiver determination.
    Reagrds,
    Sarvesh

  • Regarding ALE and IDOC

    Iam an Infant as far as ABAP is concerned. I have some basic ABAP knowlegde and i know SAP scripts and smart forms. But no idea about data transfer techniques. I have one silly question :
    Is it possible to learn ALE and IDOC on a home PC. I mean can i practice them at home. I dont have any network access so i wanted to know can i practice at home on my personal system.
    Can my home PC behave as both sender and receiver system. If it is possible pls let me know how to go about it guys.
    I know this is a very very silly question, but as i said, iam still learning to crawl in ABAP. It will take some time before i walk.
    Thank You.

    Hi guys,
    I must thank every one of you for sending such quick and helpful responses. I bought the book "ALE, EDI and IDOC" from Aravind Nagpal and its a great book for beginner as well as for an expert. I have started practising ALE my PC by logging into 2 clients and it is working fine. I was able to send and receive the IDOC.
    Thank you again.
    This is a great forum,
    Cheers,
    Mahesh.
    Edited by: Mahesh Kumar on Jan 21, 2009 3:32 PM

  • Regarding EDI: Syntax error in IDoc (segment cannot be identified)

    Hi,
    My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
    I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
    Please find the following error details using TCODE "WE02".
    *EDI: Syntax error in IDoc (segment cannot be identified)*
    *Message no. E0 078*
    *Diagnosis*
    *The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
    *This error can have several reasons:*
    *The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
    *The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (extension ).*
    *The sequence of segments in the group in which the segment appears is incorrect.*
    *Previous errors ('mandatory' segment or group missing) may be due to this error.*
    Please help me to resolve this problem. <REMOVED BY MODERATOR>
    Regards,
    Skumar.
    Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

    It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
    Hope that helps,
    Michael

  • EDI invoice idoc error "Enter a tax code in item 000001"

    Hello,
    I am trying ot post the EDI  invoice but the idoc getting failed by giving error "Enter a tax code in item 000001".
    Even i entered the tax code in my idoc, system not taking and also as i have maintained the table OBCD & OBCE but system not consider it.
    If i maintained the tax code in my PO then it is posting the invoice with PO tax code sucessfully.
    Please let me know, Is their any other setting needs tobe done for idoc to post the invoice without maintained TAX CODE  in PO ?
    Thanks in advance
    Regards,
    Satish

    No option available .you have to maintain tax code in PO.
    Try your luck with following option Still not sure as it works only if you call transaction MIRO
    OLMR -- incoming invoice -- maintain default value for tax codes

  • Debugging EDI output (IDOC creation) for purchase order...

    Hi,
    We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
    Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
    Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
    Regards,
    Rajesh

    Hi
    Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
    Save.
    Set the break point in your user exit.
    Go to se 38 -> Run RSNAST00,
    Give the object id (Your PO #)
    Give the output type  and execute, the control will stop at break point.
    Regards,
    Baburaj

  • EDI 823 - IDOC FINSTA01Mapping problem

    While processing inbound IDOC for lockbox program i am able to create payment advice. but payment advice type is taking as '05'(Payment advice from Credit memo) it sholud be '06'(Payment advice for customer(EDI)) in AVIK table
    i am not able to map this properly and suggestions please.
    Regards
    Muthappan

    Hi Luis -
    Another option to consider is <a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/frameset.htm">Mapping Lookups</a>....   RFC based lookup in your case.   You can do this in your mapping to complete the target IDOC without bpm.
    However, I will say I personally prefer avoiding the use of mapping lookups within the source or target system of the same scenario (since this seems a bit redundant), but sometimes it's unavoidable.  If you only have to do one or a few, it's acceptable...    a series of lookups, I'd start considering and weighing other options since this could be costly in terms of performance.
    If possible, if the remaining data to complete the message is in the target system, I'd also consider trying to complete it once the message arrives there.  For the IDOC in ECC, have you found out if there's a preprocessing routine or exit that would give you a chance to complete the IDOC.  There's also what Krishna suggested of converting the target interface into an async proxy, within which you can also complete the data.  In either of these cases, there's custom application development to consider.
    Regards,
    Jin

Maybe you are looking for

  • Ifs-21030 Database operation timed out

    Hi, We have installed cmsdk 9.0.4.2.2 with oas10g 10.1.2.0.2. The application runs fine, but sometimes we got the following error: [AJPRequestHandler-ApplicationServerThread-6] ERROR cmsdk.CmsdkUtil - Error with gettting document oracle.ifs.common.If

  • Creating tmp files on unix servers root while reading from MQ?

    Hi All, I have developed a interface in ODI for extracting messages from MQ and loading into oracle tables. recently i have observed that ,some temp file are creating with names start with "jms*" on my servers root directory (i.e /tmp). not getting a

  • What are some of the Oracle provided packages that DBAs should be aware of?

    Can anybody let me know what are the ORacle packages that one should aware of in case oracle 9i/10g

  • Restrict use of payment terms

    Is there a way where I could restrict use/view of payment term in the customer master data entry (FD01, XD01)?  I  have created an authorization object for ZTERM (SU20, SU21) and assigned this object (SU24) to tcode FD01, XD01.  The authorization ass

  • Having trouble editing iweb HTML. Help!

    Hello, I have been trying repeatedly to edit my websites html that I created with iweb. I bought the domain with godaddy.com and changed the cname to web.mac.com so that I could create pages and publish them to .mac, which would then show up on my .c