Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

Similar Messages

  • Logical System in IDOC-XI scenario

    Hi,
         I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
        we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No.  2) Logical System. 
    my questions are
    a) Are we use Logical System in B to B scenario ?
    b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
    Thanks and Regards
    Mahesh.

    Hay Kumar,
    Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
    a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
    b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
    Have a Good One,
    Uri Lifshitz.

  • Problem IDOC to File scenario:  No service for system SAPIDC, clnt in ID

    in IDOC to File scenario, when IDOCis triggered from R/3 to XI, it gives error in SM58 transaction 
    "No service for system SAPIDC, client 800 in Integration Directory"

    In a scenario, i have a BPM which has a transformation step which contains a mutimapping ...means 2 messages mapped to 1 messgaes, here in the mapping i m using an UDF and written code to extract the file name from dynamic configuration.....
    the problem is ...the same BPM contains another transformation step which contains a message mapping (which is not multi mapping), and here the code (UDF) works to fetch the file name...
    the code is all correct....and it looks like
    DynamicConfiguration conf = (DynamicConfiguration)
    container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
    String sourceFileName = conf.get(key);
    if (sourceFileName == null ){
         sourceFileName = "ErrorFile.xml";}
    return  sourceFileName;

  • In idoc to file scenario, if XI system is down where do idocs pile up?

    In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
    what tcode can I use to reprocess it?

    Sender System ,Check  BD87 .. you will see alll the IDOCs in Yellow state ..
    You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
    regards
    PS

  • Which all configurations you need to do in R/3 for an Idoc to file scenario

    which all configurations you need to do in R/3 for an Idoc to file scenario?
    Rgds
    Ruchitha

    Hi ruchitha thakur  ,
    A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
    First - Maintain the Sender R/3 System:
    SM59 : Create a RFC destination to XI
    WE21 : Create a TRFC Port ->Specify the RFC Destination Created
    BD54 : Create a Logical System for the Idoc Receiver
    WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
    Second - Log on to XI System:
    SM59 : RFC Destination for Sender System
    IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
    IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
    To Enable Acknowledgement:
    SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
    Category: RUNTIME
    Parameters: ACK_SYSTEM_FAILURE
    Current Value: 1
    GO TO SLD:
    Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
    Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
    Business System Role: Application System
    Related Integration Server: Integration Server
    Integration Builder
    Integration Directory:
    Add Business System:  Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System  
    IDoc Receiver Communication Channel: port the same as XI System IDX1
    The following web-sites give u step-by-step solution to configure R/3 :
    ALE configuration for pushing idocs from SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    IDOCs (Multiple Types) Collection in BPM
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    Step by Step Procedure of IDOC to File Scenario using BPM
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
    cheers!
    gyanaraj
    ****Pls reward points if u find this useful

  • ALEAUD in IDOC to File Scenario

    Hi,
    I have a IDOC to file scenario in which im sending the PAYEXT IDOC from SAP to a bank as the IDOC-XML.
    ie the user will create a payment in the SAP system , this shoud trigger an IDOC to XI. XI puts the IDOC-XML sturcture into a FTP folder path from which the bank will pick it up. Now the bank has to send an acknowledgement(asynchronously) that the payment was processed. And this response should be captured and returned to the user.
    can we use ALEAUD as the acknowledgement or does using ALEAUD make no sense here?

    Hi,
    Assuming that the bank will send you a file to the FTP server you can simply pick up this file and mapi it to the Systat IDoc. I would assumt that the IDoc status's would not be in the file so you would have to do some value mapping or other logic to determine the IDoc status codes that you want.
    The IDoc is very simple with few fields so the mapping should not be a problem.
    Please note you do not use BPM for this scenario. In essence this would be a new flow of File --> PI --> IDoc
    Import the STATUS.SYSTAT IDoc into the Design and play from there, you can make a POC now and test the functionality which would probably be best for you at this point.
    Let me know if you need more details
    Edited by: Alexander Ong on Jul 14, 2009 4:57 PM

  • IDoc-to-File scenario with external Partner ... PCK necessary?

    Hi all,
    I have a question concerning to a IDoc-to-File Scenario with an external Partner. Here is a short Description of the Scenario:
    The SAP ERP System creates an IDoc which should be send to the SAP Integration Server. The Integration Server respectively the IDoc-Adapter transform the IDoc in IDoc-XML. The Integration Server executes a Mapping and so on. In the final step the Integration Server should send the XML-File to a FTP Server in New York (external Partner) with the File/FTP-Adapter.
    Have I to install the Partner Connectivity Kit at a Server in New York or is it working without the PCK? Which are my possibilities?
    Thanks for your help
    with kind regards
    Christopher

    Hello,
    If the FTP server has connectivity to XI and if the
    port is open XI can directly do the FTP using File
    Adapter.
    Thanks,
    Himadri
    Hi,
    thanks for your quick answer.
    What means "connectivity to XI"? Our SAP-Environment is in Germany and the FTP-Server is in New York. Is it enough to open the port in the firewall?
    Thanks for your answer
    Christopher Kühn

  • IDOC to FILE Scenario-Error in defining Adapter specific Identfier

    Hi All,
    I am configuring IDOC to FILE scenario where IDOC will be send from ECC to PI System.I did following configuration
    I created RFC,PORT,LS and Partner Profile on R/3 System. I had maintained SLD and IR. In ID I created Configuration scenario and business system.When I click on menu->Adapter specific Identfier where I want to specify IDOC Adapter and RFC Adapter. But it is not allowing to edit it is not editable. As we provide LOGICAL SYSTEM,sender system ID and client number of the sender system.

    Hi Kavi,
    I assume you correctly filled the Logical System of your Business System in the SLD...
    Then in Integration Direction, use menu "SLD clear cache".
    Always in Integration Direction, open your Business System, go to menu "adapter specific identifier", and... close to button "close", you should have another button like something ''check'' or "compare to SLD' or ''retreive SDL data'' (I have not an openned PI to check the right term). Use this button to get value stored in SLD to this local definition.
    Mickael

  • Question on IDoc to File scenario

    Hi Guys
    I am doing an IDoc to File Scenario, and my sender system is maintained in the SLD as a business system, an I have created my RFC destination and Port acording this blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1310. [original link is broken] [original link is broken] [original link is broken] but when I use transaction idx2 the is niothing on a LOADED METADAT.
    I have imported the idoc to integration repository : "FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01"
    My file will be created on the FTP Server directory.
    My question is, do I have to created the RFC connection of type 3 or type T.
    Thanks
    Yonela

    Hi Yonela,
    Go thru the following threads and troubleshoot..
    IDoc was saved but cannot or should not be sent
    "IDOC saved but cannot be sent"
    Regds,
    Pinangshuk.

  • Error/Doubts in Idoc-XI-File scenario

    Dear All,
    I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
    For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
    Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
    Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
    In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
    Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
    Can anybody guide if I have followed the correct steps & where I am doing the error.
    Warm Regards,
    N.Jain

    Hi ,
    Plese refer the following blogs ,
    IDoc to File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    You have to do all this settings mentioned in the docuemnt:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    Also can you check this weblogs on the same:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Thanks ,
    Suvarna
    Award pts if  it helps .

  • IDOC to file scenario

    Hi Experts,
    In IDOC to file scenario i did in this way.
    1)created logical system.
    2)Using SALE tcode I assign logical system to client ,created RFC destination,Port and Partner's profile.
    It is showing all the thing correct.
    3) In XI system , I configured using IDX1 and IDX2.
    Then I created the material and checked the status which is green in we05.
    But in tcode IDX5, the material is not coming.
    Here I am confused that why data is not coming to XI system.
    can anyone help me?
    Thanks
    Rabi

    Hi,
    The Following are the Possible checks
    1) Check in R/3 side SMQ1 & SMQ2
    2) Check in R/3 side SM58
       In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
       If the entry is available then select it and press F6, to push it manually.
        This happens normally if IDOC stuck up in queues.
    3) Check in PI SMQ2 and IDX5
    regards,
    ganesh.

  • PI 7.1 scenario -- File to File , File to IDOC  and IDoc to File Scenario

    Hi All,
    *I have PI 7.0 . I have in that File to File , File to IDOC  and IDoc to File Scenarios*
    File to File -- This scenario is working fine.
    File to IDOC   --  Setting done in PI 7.0 like SM59,  IDXI, IDX2  and in R/3 like SALE (logical system)---  This scenario is working fine.
    IDoc to File  --  Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
    Now I need to move to PI 7.1  -- for File to File , File to IDOC  and IDoc to File Scenarios.
    Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
    If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
    Regards

    >
    Rickkk wrote:
    > Hi,
    >
    > Idoc metadeta is updated through idx2?
    >
    > Regards
    If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
    You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

  • Issues in IDOC to File scenario using bussiness service

    Hi Team
    I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent).  The setting which have done on SAP side are as below
    SAP SIDE CONFIGURATIONS
    1. Created RFC destination : RFC_XI_SYSTEM
    2. Created port : PORT_TEST
    3. created logical system: IDOC2FILE
    4. created partner profiles: IDOC2FILE
    XI side configurations
    1. Created RFC destination: RFC_SAP_SYSTEM
    2. Created port : by using IDX1 t-code
    DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
    3. metadata: by using idx2.
    DOUBT: here it is asking for IDOC type and source port,  i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know,  please find the SAP and XI system details below and suggest accordingly.
    SAP system details
    Client: 800
    User name: sapuser
    system id: DEV
    system number:10
    XI system details
    Client:100
    username:xisuper
    system id: SXI
    system numebr: 00
    I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
    Thanks in advance.
    Raju

    To complete your scenario successfully with better understanding of Idoc adapter
    read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
    for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

  • Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

    Hi All,
    I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an error
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>FILE_BC</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are  getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
    Thanks,
    Geetha

    Thanks everybody! It has got fixed. I just requested No acknowledgements.
    Geetha
    Edited by: Geetha on Nov 11, 2009 5:45 PM

  • IDoc to File scenario Monitoring Problem

    Hi,
    I have a problem in monitoring. In my IDoc to file scenario the ftp server is not reachable (wrong ip) but still in sxmb_moni I get a successful processed message with acknowledgement system error.
    Now, why dont I get an normal error in sxmb_moni?
    Thanks in advance...

    Hi,
    >>Now, why dont I get an normal error in sxmb_moni?
    Why because in MONI we generally get the Errors related to the Message Processing like mapping, and pipe line Services.
    But the error which u got is related to the Receiver, so this we can find out in the Receiver File Adapter monitoring( CC monitoring)
    MONI Shows the Errors those are related to the ABAP Satck means if any Errors occurs while going the process on ABAP Stack
    But the error which u got is on Adapter Engine Process, so Definately the Error finding place is on Receiver CC monitoring
    REgards
    Seshagiri
    Edited by: N V Seshagiri on Sep 26, 2008 1:17 PM

Maybe you are looking for

  • ICloud with os lion 10.5.8 and IPhone 3Gs

    What a pain in the A**.  Is there anyone out there that can assist me? I would soooooo appreciate the feedback.  Not sure if its fully functional with this combination. (ICloud, Lion 10.5.8, IPhone 3Gs)  I dont want MobileMe.  I have an Mac email. I

  • How to get Exchange Distribution Groups in Mail on iPad / iPad 2

    Hello... Maybe I'm missing something, but for some reason, the distribution groups I create for myself in Exchange 2010 ( personal mailbox ) are NOT showing in Mail on my iPad. Is there something that I need to do in order for them to sync? I appreci

  • Variable scope in package

    I have some procedures in a package that need almost the same type of variables. Now, lets say I put them in the package spec in the private variable declaration part so that all the procedures use the same variables instead of declaring them inside

  • Purchase Order Conversion

    Is there any standard program available to convert PO's directly in SRM. We are implementing extended classic scenario EBP 5.0

  • Email new password problem

    Hi I have recently had to change my BT email password because I got hacked. I can log into my email online no problem with the new password. I've changed the password, in Windows Live Mail but it only works some of the time. Yesterday all emails were