LEGACY TO IDOC

•     Legacy to SAP interface: Developed the Interface in XI where in (Legacy) is sending invoice data to SAP. Using File/idoc adapters
Here, the actual content of the invoice data is in the text format for which I have to send it to SAP system so I have developed an interface in XI and used File adapter on the legacy part and IDOC adapter on the sap part
pls can any one give the details step wise.....

IR
1. Import idoc from the SAP System from imported objects.
2. Create Data Type, Message Type, Message Interface for the Outbound File.
3. Create Message Mapping with file Message and idoc 
5.Create Interface mapping between File Interface and the idoc.
(no Messge interface for idoc , it acts as an interface)
other steps
1.Create a RFC Destination in SM59 .
2.In transaction IDX1 ,create a port for the client of XI server.
3. The port has to be displayed in the idx2 transaction and we should be able to view the idoc’s which we imported through integration repository.
(idoc metadata gets loaded as u import the idoc in IR)
Steps in Configuration
1. Goto service without party, right click->Assign a business system.
2. Choose the business system to be added.
3. Create a File Sender Service with communication channel for the same.(Follow http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm  for Communication channel parameters)
4. Create an idoc receiver channel under the business system.
7. The Idoc type is mentioned as inbound parameter.
8. Mention the logical Name in the Service->Adapter Specific Parameters of file  Sender Service .
9. Make the Sender Agreement for theFile Sender with communication channel.
10.Create the Receiver Determination and Interface Determination for the business system.
11.Create the Receiver Agreement for the Business system.
Step for Configuration fo IDOC in R/3
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing

Similar Messages

  • ALE Error

    HI All
    This is a very common error and I have searched for the solution in the earlier blogs in SDN.
    My scenario is File ( Legacy ) to IDOC ( ECC) using PI. I have done all the configurations and when doing the testing I get this error in SXI_MONI.
    unable to convert the sender service to an ALE logical system.
    I am using a business service for the sender and a business system at the receiver. For the business system I have done the adapter specfic identifier ( compare the LS with SLD ).
    After this I still get the same error. Is there any other thing that needs to be looked into. I am using a Business service (sender ) so do I need to do compare with SLD for the business service also. But if I do the same it says that the LS already exists for the business system and cannot be used again. Please advice.
    I also tried using the header
    Thanks
    Amit

    And if the problem is not resolved and your XI is <= SP10 then check:
    a) go to the TCODE: SXI_CACHE and check your Receiver Agreements
    b) find the one that's causing the problem and check if the header mapping is visible (if you've configured it in your BPM)
    c) if not... then probably you'll need to implement OSS note: 791181 (which deals with an error caused by a header mapping)

  • IDOC/BAPI for Production order creation from Legacy system

    Hi all
    We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
    thanks a bunch

    Hi John,
    For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
    If there is an inbound IDoc available, I would recommend to use an IDoc.
    IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
    BAPI is also good approach to use and fast in term of  processing.
    For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
    Hope this will help.
    Regards,
    Ferry Lianto

  • How to send outbound ASN IDoc with all the delivery info on legacy system??

    Hi EDI-Gurus,
    I have a small question.
    We accept inbound sales orders into SAP and send outbound Order Acknowledgments out of SAP. We don't really maintain shipping and billing info on SAP. They are being maintained on legacy. But we have to send Outbound ASN, Invoice out of SAP for them.
    Can you please let me know how exactly we can do that in detail.
    thanks,
    Matt

    Can we do this way, correct me if i am wrong.
    We'll send ASN when we issue Goods right??. If we get all the Goods issues details  relevant to an order from legacy using LSMW using IDoc method, can we send it out of SAP.
    I am just wondering if it is possible or not.
    Or get the Shipping and Billing details from legacy (using which method i don't know), and using a custom function module can we send the outbound 856 and 810 out of SAP.
    Can you throw some light on this?
    Thanks,
    Matt

  • How to relate IDOC generated in sap through ALE from legacy system

    Hi all,
    can any one tell me how can relate an idoc generated in SAP with the new idoc generated in a legacy system. I mean how could I identify, which idoc is generated for a particular idoc in legacy system and vice versa.
    Thanks,
    Nilanjana

    Thanks Suhas but when i am getting error message related to partnr profile when pressing this 'TRACE IDOC' button even with idoc in status 53.
    Edited by: nilanjana sinha on Nov 11, 2011 8:20 AM

  • Upload data from legacy system to SAP through ALE IDOC

    Hello All,
    I have a requirement where i need to upload the data from legacy system to SAP. So i am using ALE IDOC.
    In my requirement i need to extend the Standard IDOC. I have extended the IDOC and even found the exit for the updation of the extended fields to SAP. My data would be be placed in the application server.
    Can anybody tell me how to retrieve the data and update in the tables for the extended fields.
    Could you please provide a sample program for retrieving data for IDOC.
    Thanks

    Hi,
    You can find the sample code in the following link.
    Re: calling idoc_input_creditor
    Regards
    Sajid

  • Idoc missing Legacy

    Hi,
       My senario is SAP sending  IDOC to PI from PI to Legacy,SAP posted 30 idocs but only 28 reached to Legacy but i see evry thing ok in MONI,smq1,smq2,sm58.
    What i need to do in this case help me.
    Regards,
    Prasad.

    Hi,
    As you did not precise if you did these tests, and I ask you:
    in PI, tcode SXMB_MONI, check if you received 30 idocs (same figure than in ECC).
    if it's not the case, your problem in ECC. So have a look on:
    in ECC, tcode WE02: check that you have 30 idocs with status "03" correctly treated (or 39 if PI returned an Ack).
    in ECC, tcode SM58: check this queue, even if you have a "03" status for your idoc !, coz "03" = correctly generated, but not "correctly sent to PI or received by PI"...
    if the count is good in PI, do the check list providen by Shabarish
    Regards
    Mickael

  • Legacy data(mapping to be done by xi (in xml format)) to sap using idoc .

    hi all,
    I need to work in an object in which requirement is like , the source data is directly extracted from legacy and input file is made. now i need to create an interface program which will be used to create purchase req. in weekly basis.  now according to functional specification xi team will  map the source data in xml format and then  through idoc data is to be pushed into sap. i am confused about the step by step senario from source data to final pr creation . please clarify if somebody had worked on this kind of situation.

    Hi i encounter like this but in SD side,
    from legacy ->XI -> SAP (create SO)
    then from created SO via IDOC my requirement is to post delivery then billing.
    I think in your case the PR is already created and to be process to PO.. better check and fully understand the flow with your team.

  • IDOC not reachig Legacy

    Hi Experts,
             My senario is Idoc coming from SAP to PI,from PI must reach Legacy(Jms adapter),SAP has posted Idoc but it is not reaching legacy,Even I dont see any message related to that interface in MONI,I have taken the idoc number and checked in IDX5 it is i red status and error Receiver not found.In payload there is filed missing "<SNDLAD>IND<SNDLAD> ,BUT IN rECIVER DTERMINATION THERE IS NO condition may be this is the issue or any thing else kindly help me.
    Regards,
    Prasad.

    hi,
       No Reciver aggrement found for Sender.
    first you need to check configuration objects..reciver determination and interface determination.is it working fine you have to some changes in re activate it.
    i hope this will help you.
    regards,
    ganesh.

  • Receiving IDOC from Legacy

    Hi guys,
    I have requirement that POD will be send by the customer to the legacy system, where order processing is happening.
    The legacy system will send the POD to the ECC system by using EDIFACT.
    there is a integration layer where EDIFACT will be converted to IDOC.
    Does the legacy sytem sends the IDOC automatically after conversion to ECC, or do we need to use any function module for this to receive IDOC in ECC.
    If the Legacy system is sending the IDOC automatically in the ECC, where does it post to which table it has to update.
    do we need to do any setting for this.

    Hi,
    There is no BAPI that will split the IDoc and post. You have to do it manually. One way is
    1) Split the IDoc into two or more IDocs based on the maximum items you need. Later post these IDocs.
    2) Post FI invoices as and when you reach max count(without actually creating new IDocs).
    I guess first one would be better as you can tract which IDoc resulted in which FI document(Invoice).
    I worked on this before. When we process an IDoc with more items, we flag that IDoc with a custom message with status 51. We have a scheduled job that picks the IDocs with this status and split the IDocs to 2 or more new IDocs.
    These new IDocs are processed later.
    Hope this helps
    Vamsi

  • Legacy flat file - XI - R/3 (IDocs)

    Hi Liu,
    I was trying to have some hands-on with XI 3.0 demo.
    I tried with the following scenario-
    Legacy flat file -> XI -> R/3 (IDocs)
    e.g., say to create BOM data or material Master.
    I take the flat file - create my own External Data Type, message type & message Interface for it in Design(Repository).
    And try to map it with the required IDoc Type(msg. type) imported from R/3.
    But while mapping, I found certain unknown fields like BEGIN (mandatory), inside the Control Record EDI_DC40- certain fields like SEGMENT, TABNAM, etc.
    Al these fields are unknown & I could not figure what to map & how to map them.
    Also how do we map Sender port/ receiver- dow e need to hard-code them or we can assign them/map them dynamically.
    Would appreciate ur sppedy reply.
    Thanks.

    For BEGIN you map a constant with no value.
    For the attributes SEGMENT you have to choose:
    1. Is the IDOC segment available only once (occurence 1..1), just map constant '1'
    2. Is the IDOC segment available multi times (occurence 1..unbounded), map arithmetic function 'counter' to make sure, that each attribut SEGMENT has an increasing number.
    Regards
    Stefan

  • IDOC approach (Basic type : CREMAS01) to upload legacy vendors

    I am using the IDOC approach (Basic type : CREMAS01) to upload legacy vendors.The LSMW then creates default partner functions.
    However i need to modify the partner function.
    My question is ...Is there a way to delete an entry through LSMW using IDOC approach (or even modify would help) but not append????
    Thanks in advance ,
    naval kishore  bhatt.

    Hi,
    Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
    The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
    The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
    The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    Regards,
    Gowri.S

  • Legacy flat file to IDOC into SAP

    after been given the task of converting a flat file structure to SAP idocs my research as lead me into the daunting world of CAPS. Basically I would like to know if using CAPS is the best choice for me
    and if so what is actually involved to make this happen?
    Thanks
    Michael

    hi michael,
    from my point of view "the right thing to do" would be:
    consider if this is the only task for you that is somehow EAI ish...
    if it is do not care about technology... just do it with a very simple program
    if you have to evolve choose a tool that is capeable of your systems you own: e.g. SAP AS400 .......
    in caps you would typically do this:
    setup CAPS
    write an ftp2queue component
    write a converter (custom otd + convertion logic + IDOC OTD)
    write a idoc 2 sap component via TRFC
    run ;-)
    a good starting point would be:
    http://developers.sun.com/docs/javacaps/index.jsp
    or
    http://wikis.sun.com/display/JavaCAPS/Grok+Java+CAPS
    or try to convince your boss that sun will implement it for you if you have the money to do so.
    we did that when introducing CAPS (we got it for free besides the CAPS licences of course ;-)).
    regards chris

  • PO Creation, with same Legacy Item No : LSMW-IDOC

    Dear all,
    I am creatin PO's using LSMW IDOC Method - BUS2012.
    I could create PO's . But issue is , but issue is PO's are created with Item No in Sequence( 10,20 etc).
    We need to create PO with same Item No as in Input File.
    Eg: If Item No are 40 , 50 in input file. PO is created with Item 10 and 20.
    I need to create them with 40 & 50.
    Is there any option to achieve this.
    Thanks
    Praveen

    Hi,
    If you are using the BAPI method in the LSMW,
    Set the parameter ITEM_INTVL = 'X' which is in the parameter POHEADERX.
    This should allow external PO line item numbering.
    Please check.
    Thanks
    Naren

  • IDOCs in status 12 not reaching the Legacy System

    Hi Experts,
    I am facing problem with a specific set of IDOCs in R/3.
    the IDOCs are with status 12.
    Queues are fine. SMQ1, SMQ2 are clear.
    Also I don’t find any communication errors : (SM58 in XI)
    All adapters were also working fine
    <b>And in SXMB_MONI we found messages with “still waiting acknowledgement”</b>
    Can anybody give me an idea about what might went Wrong.
    I performed all the necessary checking but couldn't trace any errors.

    Hi Santosh
    There may be a problem in ur configurations. Please check the status of our idoc in the tcode : sm58 (in R/3).
    I think your IDOC was strucked here. Check the status.
    **Award the Points if it is useful**
    Cheers...
    Vasu

Maybe you are looking for