File to file scenario..............file lost if target directory incorrect?

hi forum experts,
i have a file to file scceanrio....without BPM....
there is only one mapping ...in the receiver determination......
the problem is........
when in the receiver communication channel....in the <target directory>....i give something absurd.....e.g. '-', the file cant be put to the desired directory...
and the file is lost.............moreover nowhere in the rwb i can see what the error is.......in rwb it shows file delivered successfully........
now how can i retrive the lost messgae.....how can i resend the message from rwb or MDT............
is it possible from MDT to resend the message payload again????
pls help

Dhar,
Is this is development or production? Also why you have given the target direcotry as '-' ?  Is this your requirement?
Anyway you can post the same message once again from RWB. Since it is file to file scenario you can post from RWB.
Go to sxmb_moni and open your message. From the source payload right click and select view source. Then copy this payload and go to RWD ---> Adapter Engine ---> Test Message ---> Here you give your Source business system, Target business sytem and all the parameters. Also you paste the payload here. Also give your user name and password and select Quality of service BE. Then send the message. You will see a new message in sxmb_moni.
Also would recommend to give a name for target directory.
Check this weblog for some help on this:
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
---Satish

Similar Messages

  • File not getting created in Target Directory..........

    Hi All,
               We are trying a IDOC-File scenario & trying to create a XML file on the receiver side........All the mappings have been checked & everything is working fine.It shows success in SXMB_MONI. But the file is not getting created at the target directory..... Checked the component Monitoring and message  monitoring as well, which is also successful...
    What could be the reason of such behaviour, and is there a way to track the where the target file is getting placed?
    Please Help
    Regards,
    Jayashri

    >
    Jayashri Rade wrote:
    > Hi All,
    >            We are trying a IDOC-File scenario & trying to create a XML file on the receiver side........All the mappings have been checked & everything is working fine.It shows success in SXMB_MONI. But the file is not getting created at the target directory..... Checked the component Monitoring and message  monitoring as well, which is also successful...
    i
    Did you check the receiver communication channel in communication channel monitoring?
    Are there any errors?

  • Placing the file in UTF-8 format in Target Directory

    Hi Experts,
    Can any one please tell me how to place a file in Target Directory by PI in UTF-8 format.
    It is a file to file PassThrough (no IR part) scenario and in receiver File Adapter I have used File Encoding as UTF-8
    but still PI is not placing the file in UTF-8 format in the Target Directory.
    Are there any modules by which the files are converted to UTF-8 format.
    Can anyone please help me out.
    Thanks and Regards,
    Prajwal

    Hi,
    Please let me know if I need to change the TransferMode,File Type and FileEncoding in both sender and receiver channel.
    I tried the below settings but still the file is not being placed in UTF-8.
    Sender CHannel:    TransferMode         Text
                                   FileType                  Text
                                   FileEncoding            UTF-8
    Receiver Channel    TransferMode         Binary
                                     FileType                  Text
                                     FileEncoding           tried with UTF-8 once and tried with blank
    Can any one throw some light here.
    Thanks and Regards,
    Prajwal

  • Peculiar behaviour in picking file from FTP in File-IDoc scenario

    Dear XI Expert,
    I have successfully completed configuration of FTP --> XI --> IDoc scenario. I have noticed a peculiar behaviour in picking the file from FTP. I placed a file on FTP and activated File Adapter with poll interval '60' secs and processing mode as 'Archive'. For the first time it has picked the file with expected behaviour and IDoc got posted to SAP successfully. But when I placed file for the second time and when refreshed the FTP directory, immediately file got archived without waiting for 60 secs. But in sxi_monitor I could not see any activity of processing this scenario. Surprise is that, file got archived in target directory. This goes on and on... without registering any activity of processing the message in Message monitoring.
    In adapter monitoring it shows the message as described below:
    <i>History:
    2006-05-09 22:57:25 : Processing started
    2006-05-09 22:57:25 : Error: Processing interrupted due to error: FTPEx: No such file
    2006-05-09 22:57:24 : Processing started
    2006-05-09 22:57:24 : Error: Processing interrupted due to error: FTPEx: No such file</i>
    For your information my SAP XI system is on SP16.
    Please find below the parameters of sender adapter:
    <i>Quality of service: Exactly once
    Poll interval: 60 secs
    Processing mode: Archive
    Connect Mode: Per File Transfer
    Transfer Mode: Binary</i>
    Can anybody help me out in resolving such a problem in this scenario?

    Hi Jayakrishnan,
    Thanks for your reply.
    Once again the same problem is noticed. i.e., for the first time when file adapter is activated the file got picked, activities were logged in monitoring and IDoc got posted to destination system. For the second time when file is placed, before 60 secs got completed the file is picked and archived in the target directory. No activities in monitoring are logged.
    I have tried it checking the message at adapter level, but it is showing 'No results' (even in the case of successful pick of the file for the first time, not even it is showing other file adapters).
    I was not able to understand where the problem could lie?
    Regards,
    Suraj Kumar

  • Unable to  convert the file name in Target directory

    Dear Experts,
    Currently iam facing a problem with some files.my interface is a File to file .As per the interface the sender will pick the flatfiles from source directory which the file name was BNP_NE201.txt once my file reached to target directory the name of the file willrenamed as VENDOR_Payment.NE201 automatically  for this they have done some OS level script in receiver communication channel of the first interface which we have added "un operating system command after message processing" in processing parameters tab.again one more sender comm channel wil pick the file from first target directory which is having naming  convesion of "VENDOR_Payment.NE201 " and post it to target. all the two interfaces are file to file (NFS) . for a parctuclar day files has been posted to 1 st target directory and the receiver communication channel is not yet convert the file names bcz of that the second communication channel can't able to pick the files from target directory. for some times that is working fine and some times it is unable to convert.
    from our side i check every thing .could you please suggest me the way to approch
    Reagrs,
    Kiran tanuku

    >> for a parctuclar day files has been posted to 1 st target directory and the receiver communication channel is not yet convert the file names bcz of that the second communication channel can't able to pick the files from target directory. for some times that is working fine and some times it is unable to convert.
    You need to wait until the file is converted. After when it is converted then the second interface sender communication channel will pick the files.
    What do u mean by unable to convert?
    Is it unable to do the content conversion? if so then check the data as you said that it sometimes it works fine.
    > The best approach is to change the name of the file in the receiver communciation channel instead of using a script.
    Thanks,

  • Adapter moduler in file adapter receiver - get Target Directory from param

    Hi everybody,
    We are in PI 7.1
    I need in an adapter module (file adapter receiver) to access to the Target Directory comming from parameters
    I foound the code in a weblog
    /people/sap.user72/blog/2005/07/15/copy-a-file-with-same-filename-using-xi
    Here is the code I found
    public ModuleData process(
              ModuleContext moduleContext,
              ModuleData inputModuleData)
              throws ModuleException {
              Object obj = null;
              Message msg = null;
              try {
                   Channel ch = new Channel(moduleContext.getChannelID());
                   obj = inputModuleData.getPrincipalData();
                   msg = (Message) obj;
                   XMLPayload xmlpayload = msg.getDocument();
                   String path = ch.getValueAsString("file.targetDir");
                   if (!path.endsWith("
    ") && !path.endsWith("/"))                    
                             if(path.indexOf("
    ")!=-1)
                                  path+="
                             else
                                  path += "/";
                   if (xmlpayload != null) {
                        convert(xmlpayload.getContent(), path);
                   inputModuleData.setPrincipalData(msg);
              } catch (Exception e) {}
              return null;
         private void convert(byte[] bs, String path) throws Exception {
              String bs_out = new String(bs);
              String filename =
                   bs_out.substring(
                        bs_out.indexOf("<FileName>") + 10,
                        bs_out.lastIndexOf("</FileName>"));
              bs_out =
                   bs_out.substring(
                        bs_out.indexOf("<Base64>") + 8,
                        bs_out.lastIndexOf("</Base64>"));
              byte bb[] = com.sap.aii.utilxi.base64.api.Base64.decode(bs_out);
              File f1 = new File(path + filename);
              FileOutputStream fos = new FileOutputStream(f1);
              fos.write(bb);
              fos.close();
    The object Channel come s from the package import com.sap.aii.af.service.cpa.Channel;
    The jar is in the build path (com.sap.aii.af.service.cpa.jar);
    When I write in NWDS
    Channel ch = new Channel(moduleContext.getChannelID());
    NDWS gives me an error "Cannot instantiate the type Channel".
    Can somebody help me about that, please?
    Does that code dosn't work in pi 7.1?
    Thanks in Advance for your help.
    Best Regards.
    E. Koralewski
    Edited by: Eric Koralewski on Feb 3, 2011 1:40 PM

    > When I write in NWDS
    > Channel ch = new Channel(moduleContext.getChannelID());
    > NDWS gives me an error "Cannot instantiate the type Channel".
    it should be:
    Channel ch = (Channel) LookupManager.getInstance().getCPAObject(CPAObjectType.CHANNEL, moduleContext.getChannelID());
    (taken from sample module ConvertCRLFfromToLF)
    http://help.sap.com/javadocs/pi/pi711sp03/index.html?com/sap/aii/af/service/cpa/Channel.html
    Edited by: Stefan Grube on Feb 3, 2011 2:02 PM

  • File to idoc scenario with controls

    I am working on file to idic scenario.
    file has four types of lines :
    Begin of file.
    header.
    items.
    end of file.
    each line has a element Record type and some other elements.for header record type is A , for item its B , for Begin of file its C and for end of file its D.
    we have to check for every line that it should have record type as one of these four and if not so we have to send a mail through alert functionality.we have to send a mail which has all errors by checking the whole file for record types.we have to ignore these lines in the file and proceed with the rest.
    how can we implement this?
    regards,
    rohit

    Hi,
    Please go through these links
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    /people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Thanks
    Vikranth Khimavath

  • ** File to IDoc scenario - IDoc not created in target system

    Hi friends,
    We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
    We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
    1) SM59 - Connections are OK both application and XI system
    2) IDX1 - In XI System, we have assigned SAP<R/3> port.
    3) IDX2 - IDoc is imported.
    4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
    5) In application system. - Partner Profile maintained correctly.
    6) SM58 - There is no error.
    So, what could be the reason ?
    Kindly reply, friends,
    Thanking you.
    Kind Regards,
    Jeg P.

    Hi,
    Check all the steps ..
    File to IDOC
    Do these configurations in R/3 and in XI...
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Thanks,
    Satya

  • Trouble shooting File to Idoc scenario: wrong Idoc structure in target

    Hi All,
                 I am working in an file to idoc scenario. Now the scenario is running but the idoc I am sending from SAP XI is not matching with one received in SAP R/3 system. This is not a new scenario. The  scenario was already existing. I have done structural changes in Idoc structure and re-imported it in SAP XI. When the iodoc reaches SAP R/3 system I check its structure and data content. 4 of its fields are missing all 4 were newly added fields. Data from some fields are getting merged into one field within Idoc. data from one field is moving onto other fields in target. I have refreshed the metadata using IDX2 transcation within SAP XI but still getting same result.

    Hi All,
    I am able to see the changed idoc structure in IR. I have also tried cache refresh. I am trying to explain my problem once again with example.
    Source Idoc in XI
          fieldname                            data
           f1                                       d1
           f2                                       d2
           f3                                       d33
           f4                                       d4
           f5                                       d5
    Idoc structure received in SAP R/3 system. I am seeing through we02 transcation, inbound idoc
          fieldname                            data
           f1                                       d1
           f2                                       d2
           f4                                       d33d4
    I have tried cache refresh, IDx2 metadata refresh, but no improvement of the situation.

  • BPM Scenario how to wait til file deleted in Target Directory

    Hi Frnds,
    I am working on one JMS to File scenario,my requirement is i am sending JMS message to File Directory,when i placed meg in target directory some vent wil read the message it wil process in to SAP.
    When i receive once again mesage in JMS scenario will start execute , is previous message still in File Directory i have to wait to event occured,after procesing only i have to place next message.
    How many different ways i can achieve this.
    many thanks,
    RAJ

    Hi,
    you can create a java proxy in your BPM that would check the file and if so wait for some time
    and check once more
    Regards,
    Michal Krawczyk

  • How to populate target directory from the source XML in Receiver File Adap?

    Hi All,
    Our scenario is IDoc - XI -(Receiver File adapter) File. Is it possible to populate complete "Target Directory" from the source XML message??
    Lets say we added field to maintain target directory in Idoc structure and some how populated value to it, then grab this target directory from the IDoc-XML and pass in Comunication Channel. I think its possible through Variable Substitation ...just want to make sure and if sombody has done the similar scenario their inputs would be great.
    Thanx
    Navin

    Hi,
    Please see the belowlinks
    /people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
    /people/sriram.vasudevan3/blog/2005/11/21/effective-xsl-for-multimapping-getting-source-filenames-in-legacy-legacy-scenarios
    Re: Dynamic  File Name for Receiver File Adapter
    Variable Substitution
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    try with adapter specific
    Example code...
    String newfilename="";
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
    // Get Sourcefilename
    String oldfilename=conf.get(key);
    //extract first 3 chars of source filename
    newfilename=oldfilename.substring(0,2);
    //get the date
    java.text.SimpleDateFormat dateformat = new java.text.SimpleDateFormat( "yyyyMMdd" );
    dateformat.format( new java.util.Date() );
    //append sourcedateL
    newfilename=newfilenamedateformat"L";
    // determine if prod/ dev / qa
    map = container.getTransformationParameters();
    senderService = (String) map.get("SenderService");
    if(senderServcie.equald("Prod"){
    newfilename=newfilename+"P";
    // change to new file name
    conf.put(key, newfilename+".tmp");
    Change it according to your requirement
    Regards
    Chilla..

  • Target Directory in File Receiver Adapter

    Experts,
    I am trying for a scenario (File to File) and I am not sure if the target directory is a directory in XI server or my local machine. I used HTML client to send the message to the adapter. Also if any of you could give clear idea about source and target direcory without pointing to any weblog, I would greatly appreciate it. As I have tried every weblog available with a word File in it.
    Thanks
    Thilothama

    Thilothama,
    I've seen your previous posts and you never assigned any points. People in the forum spend their valuable time answering questions.
    I request u to reward the people who have replied to your posts. IF u consider that the replies have helped u , u can assign,
    2 points -- helpful
    6 points -- very helpful
    10 points -- problem solved..
    If u are not able to see the assign point s button refer to this thread...
    Unable to award points
    regards
    Shravan

  • Test cases for File to JDBC scenario?

    Hi Experts,
    I would like to know what are the things needs to be tested to ensure that the File to JDBC scenario holds good in the PI box. Your valuable inputs are required to verify /check my scenario configuration is free of errors.
    Thanks & Regards,
    Pcv.

    Hi,
    You can try the following:
    1) If the end systems require authentication and the same is not provided in PI then it should throw an error.
    2) Check what happens when you dont give a mandatory field.
    3) check what result you will get when you give a wrong input.
    4) Check whether all your restrictions (in mapping and/or in receiver determination) are working properly.
    5) Check what you need to do when the target system is down.
    6) If using any FCC then check whether the conversion is done properly.....
    7) See to it that you have defined a proper DB structure when you are communication with JDBC
    8) Check with the end system whether your statement (Insert/Update/Delete etc) is performed properly
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Dec 4, 2008 9:58 AM

  • Problem in text file to xml scenario

    hi,
    while executing the Flat file (txt) to xml file scenario, the txt file picked up from my source directory, but i could not find in my target directory.
    when i check message monitoring, it is showing successful.
    Audit Log for Message: af840930-3fa2-11dc-a345-000423c7753d
    Time Stamp Status Description
    2007-07-31 16:14:47 Success Channel CC_sender: Entire file content converted to XML format
    2007-07-31 16:14:47 Success Send text file "xi_input.txt" from FTP server "64.72.230.130:/praba_source", size 353 bytes with QoS EO
    2007-07-31 16:14:47 Success Application attempting to send an XI message asynchronously using connection AFW.
    2007-07-31 16:14:47 Success Trying to put the message into the send queue.
    2007-07-31 16:14:47 Success Message successfully put into the queue.
    2007-07-31 16:14:47 Success The application sent the message asynchronously using connection AFW. Returning to application.
    2007-07-31 16:14:47 Success The message was successfully retrieved from the send queue.
    2007-07-31 16:14:47 Success File "xi_input.txt" deleted after processing
    2007-07-31 16:14:47 Success The message status set to DLNG.
    2007-07-31 16:14:48 Success The message was successfully transmitted to endpoint http://xiserver1:8000/sap/xi/engine?type=entry using connection AFW.
    2007-07-31 16:14:48 Success The message status set to DLVD.
    2007-07-31 16:14:48 Success The message was successfully delivered.
    I followed the Venkat Donela blog
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    IN sender CC, i used file content conversion(mesage protocol), file name scheme xi_input.txt
    In receiver CC , I used file (message protocol),file name scheme xi_output.xml
    In both CC , transport protocol is FTP.
    so i gave server name, port, username, password.
    could you help me out to find the error for this scenario also?
    Thanks in advance

    hi,
    when i click on this adapeter engine xiserver1, it is changing to green color,
    if i double click nothing is happening as u said
    but it is showing like this Central CCMS monitor not available
    anyway i giving all my values in sender CC:
    in sender communication channel
    TP : FTP
    MP: File content conversion
    AE: IS
    File access parameters:
    sD: /praba_source
    FN: xi_input.txt
    FTP access parameters:
    server: xx.xx.xxx.xxx
    port:  xx
    username: xxxxx
    password: xxxx
    connection mode: permanently
    transfer mode: Binary
    Processing Parameters:
    QoS: exactly once
    poll interval: 60
    Processing mode: Test
    File type: Binary
    Content Conversion Parameters:
    Document name dt_outbound
    Document namespace urn:xxxxxx
    record name: record
    recordset str: row,*
    recordset seq:Ascending
    key fiedl type: string(case-sensitive)
    name:                value
    row.fieldNames:     FirstName,LastName,MiddleName,City,Place,State,Country
    row.fieldSeperator:     ,
    row.processConfiguration: FromConfiguration
    row.endSeperator: 'nl'
    my input file which i kept in source directory is xi_input.txt
    content of this file (xi_input.txt) is
    Samuel,J,Jackson,Lakefront Drive,Earth City,Missouri,USA
    Kenny,m,George,North Beauregard street,Alexandria,Virginia,USA
    my dt_outbound structure like this,
    dt_outbound (complex type)
    then lower element is record
    then lower elemnt is row
    then FirstName
    LastName
    MiddleName
    City
    Place
    State
    Country
    anyway i pasted my sxd dt_outbound type
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:praba_flatfile2xml07"
    targetNamespace="urn:praba_flatfile2xml07">
         <xsd:complexType name="dt_outbound">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   2bc3c190404611dc88a3000423c7753d
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="record">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             35982b703f7911dc871cd71bc0a8016d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="row"
    maxOccurs="unbounded">          
                             <xsd:annotation>
                                            <xsd:appinfo
    source="http://sap.com/xi/TextID">
    359f57603f7911dcca2ed71bc0a8016d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element
    name="FirstName" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57613f7911dc8d9cd71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                                 <xsd:element
    name="LastName" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57623f7911dca6e8d71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                                 <xsd:element
    name="MiddleName" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57633f7911dcc31ed71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                                 <xsd:element
    name="City" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57643f7911dc8c7ad71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                                 <xsd:element
    name="Place" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57653f7911dca7dbd71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                                 <xsd:element
    name="State" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57663f7911dcbd52d71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                                 <xsd:element
    name="Country" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    359f57673f7911dca78ad71bc0a8016d
    </xsd:appinfo>
    </xsd:annotation>
                                                 </xsd:element>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • Steps required in File to Idoc Scenario

    Hey guys i m doin a file to Idoc scenario and just wanna make sure my steps r correct.
    steps done on the XI server
    1.Create RFC destination(test the destination by giving the target host as the R/3 server).
    2.Create port for the RFC destination.
    steps on the R/3 side
    1.Create/verify logical system name.
    and finally create business system for this logical system in SLD.
    now do i need to do partner profile as well or not? and if i have to do it how is it accomplished.
    thanx
    ahmad

    Hi,
    The following are needed for idoc to file scenario...
    In R3...
    RFC dest to XI (sm59)
    Logical system (bd54)
    Port to XI (we21)
    Partner profile for the logical system (we20)
    In XI...
    RFC dest to R3 (sm59)
    Port to R3 (idx1)
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3.
    Regards,
    Uma

Maybe you are looking for

  • Error while deleting Instance

    During the deleting of an SAP instance, I receive these messages.  I am using the SAPinst to perform the delete.  I receive this error during the Drop instance phase.  The instance is an SCS instance.  This is the last instance to be removed.  Can an

  • 3G phone doesn't fit Apple Bluetooth Headset Dock

    I bought an Apple iphone bluetooth headset and dock from the Apple Store in Regent Street yesterday to go with my new 3G iphone. I got home and find I can't fit the 3G iphone into the dock!!! The dock should fit both the phone and the headset for cha

  • How/where do I get /usr/bin/make for lion?

    Previous OS X releases came with a DVD that included an "SDK" package to support normal unix software development (gcc, make and so on). Having just bought a new macbook pro with lion pre-installed, there's no DVD, no SDK.  Does this exist anywhere?

  • Photoshop CS3 10.0.1 - Launch hangs on Registration Screen, All menu items grayed out

    I'm using Adobe Photoshop CS3 10.0.1. When launching, the window labeled "Adobe Design Suite Premium CS3" opens - it's only filled with white, and no text or graphics (I think it's usually the window asking me if I want to register, which always come

  • Updating Feed URL :- Inadvertantly Updated Two Seperate Feeds to Same Feed

    There are two seperate feeds in iTunes Music Store for Immaculate Heart of Mary Podcasts. [1] http://itunes.apple.com/us/podcast/immaculate-heart-mary-homily/id294766875 [2] http://itunes.apple.com/us/podcast/immaculate-heart-mary-homily/id295664714