2 files scenario design

Hey guys,
I have a simple interface where I need to get 2 files from an FTP directory, and then post it in SAP. Once both files are posted, I need to do an RFC call but only once.
So the flow will be:
FILE1 AND FILE2 --> PI --> FILE1 AND FILE2 IN SAP --> RFC CALL
Is it possible to do this without using BPM? If so, how?
Thanks!

We can do it without BPM.
Step 1: Use a sender file adapter to receive the files in PI.
Step 2: Store the file in the application server of PI.
Step 3: Have a second scenario to read the files using ABAP mapping.
            Source would be a dummy interface.
            Inside the ABAP Class we can use OPEN DATASET to read the files and store the data in separate internal tables.
Step 4: Use the Internal tables to map the RFC.
Step 5: Other configurations for Integration directory will be for the 2 different scenarios ( 1st file being received in PI and the 2nd would be for the dummy file interface to RFC ).
Regards,
Indranil

Similar Messages

  • Issue in IDOC-File Scenario

    Hallo Everybody,
    In one of the requirements,for the interface design which involves IDOC-FILE scenario we have a req as:-
    Multiple IDOCs would be sent from SAP R/3 to SAP XI. Each IDOC can have 0-4 segments and for each segment a file needs to created.
    The files needs to be FTPed to a location, only if all the IDOCs have been processed successfully.
    Requirement:
    1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
    2) We need to send a notification from XI, in case any IDOC processing fails.
    3) How do we check in XI, if all the IDOCs have been processed successfully.
    Please suggest me with some good stategies to resolve this issue.
    Appreciations and Rewards in line.
    Regards,
    Younus

    Hi
    Are you planning to use BPM as it suits your requirement.
    To collect the idocs in small bunches refer
    Collecting IDocs without using BPM
    1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
    BPM will allow you to wait for the time all IDOC are processed
    2) We need to send a notification from XI, in case any IDOC processing fails.
    BPM exception handling will allow this functionality even to the exact field you want to send  notification
    3) How do we check in XI, if all the IDOCs have been processed successfully.
    Set Acknowledgment for IDOC's
    refer
    Posting multiple IDocs with Acknowledgement
    Thanks
    Gaurav

  • File to File scenario

    Hi,
    I have a problem in file to file scenario in which the file is not getting transferred from source to target.
    Source communication channel - Transport protocol - NFS  | Process mode : Delete |  The file is picked but not able to delete from the directory.
    Error: File: d:\test\file.txt deleting after processing failed - retry
    The file is not transferred to target is it because of this CC is not able to delete the file. Does windows also have any authorization issue if so how should one check the authorization. I have the admin access of my system.
    Thanks.

    Hi,
    Firstly, Since the scenario works perfectly while using Test mode, so all your design & configuration are OK.
    Now, there can be Two reasons why PI is not able to delete the file and process it (during Delete Mode):
    (The Problem will persists if you use Archive Mode also)
    Prob 1. The directory is write protected or read only
    Prob 2. The file is write protected or read only
    Solution:
    If Unix System
    Soln for Prob 1. - go to the directory structure
    for ex: if directory where file is kept is /staging/Interface/PI/Test/inbox/
    then go to /staging/Interface/PI/Test/ and give command ls -lrt
    It will show the directory names with permisions.
    use chmod 777 inbox and the permissions willl be changed ( drwxrwxrwx )
    Soln for Prob 2. - Get inside  /staging/Interface/PI/Test/inbox/ and give command ls -lrt
    if the file does not have authorizations as (-rwxrwxrwx) give chmod 777 <filename>  and then give command touch <filename>
    If Windows System
    Soln for Prob 1. - Goto the directoty and right click on the folder and deselect the Read Only Checkbox.
    Soln for Prob 2. - Right Click on the file and deselect the Read Only Checkbox
    Try again and the scenario will work surely. Let me know if any issues.
    Regards,
    Souvik
    Edited by: Souvik Chatterjee on Mar 14, 2011 8:14 AM

  • Warning message in MONI for HTTP to File scenario

    Hey guys
    i have a HTTP to file scenario wherein i m getting file from an extrenal system in XML format outside our landscape,file is coming in properly and its being delivered as desired as well,but everytime i check my payload in moni ,an information message pops up saying that the file may be unsafe,do you want to display,save or cancel?
    even though i get correct payload and the file is also coming from the designated IP and port,why do i keep getting this pop up?
    thanx
    ahmad

    Hi Ahmad,
    Put a break point at line 1,311 in progam RSXMB_DISPLAY_MSG_VERS_NEW_F02 in the form READ_AND_DISPLAY_DOCU2....
    That is where you are getting this popup from...
    Thanks,
    Renjith

  • 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.

  • File to File scenario in PI 7.1

    Hiii...
    iam trying file to file scenario...I have designed in service builder and Integration builder....
    My scenario i just want to tranfer a file from one folder in PI Server to another folder in the same server...My Communication Channel info are
    1.my File type is File adapter.
    2.Transport Protocol is File system
    3.message protocol is File...
    iam not getting any error..I even started my sender and receiver communication channel in RWB....and iam not geeting any error over thr...
    But my file is not picked..but in cluster node it states that my processing is started...What may the issue...May knw ur valuable input..
    With Regards...
    Ramesh....

    Hi,
    Correct log message in cc monitor (with or without files in source path) would be:
    Processing started
    Polling interval started. Length:XXX seconds
    Processing finished successfully
    Processing started
    Polling interval started. Length:XXX seconds
    Processing finished successfully
    If you see only
    Processing started
    Polling interval started. Length:XXX seconds
    Processing started
    Polling interval started. Length:XXX seconds
    Please, recreate your sender cc from integration directory
    Regards,
    Carme.

  • Problem in idoc to file scenario

    hi
    while creating the idoc to file scenario i am facing few problems.
    1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
    2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
    3) i am using my ecc6 training server as my sender and using my XI server as receiver.
    4) i am sending idoc from ecc6 and converting it  to file in XI server and saving it in XI server itself(my receiver in this case).
    my error:
    i send my idoc from we19 transaction, and i see a error message stating
    that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
    my doubts.
    1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
    2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
    3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
    kindly help me with this issue.
    regards
    manoharan

    >
    manoj murugesan wrote:
    > 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
    >
    > 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
    >
    > 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
    >
    >
    > kindly help me with this issue.
    >
    >
    > regards
    > manoharan
    and to 1 & 2 ref. below,
    Configuration steps required for posting idoc's(XI) -
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    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
    3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

  • 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

  • Getting Receiver Agreement issue in IDOC to File scenario

    Hi Gurus,
                Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
    Error Message:
    No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
    Error  Category : Outbounding
    Error ID : CO_TXT_OUTBINDING_NOT_FOUND
    My IR design:
    Sender:
          Interface : VEND_IDOC_OUT_MI
          Message Type : CREMDM.CREMDM04
    Receiver:
          Interface : VEND_FILE_IN_MI
         Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
    My ID Config:
    1. Sender / Outbound  Message:  Service Type --> Business System
                                                  Service  ---> SAPERP
                                                 Interface--> VEND_IDOC_OUT_MI
                                                 Adapter Type : IDOC
    2. Receiver / Inbound Message: Service Type --> Business Service
                                               Service       --> IDOC2FileReceiver
                                               Interface    ---> VEND_FILE_IN_MI
                                               Adapter Type--> File
    3. In Sender Agreement : Specified the Sender Communication Channel
                                         VEND_IDOC_OUT_Channel
    4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
    5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
    6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
    I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
    Can anyone help me identifying what's going wrong. I'm very new to XI and basically this  is the first assignment I'm working on.
      Regards,
    Subhadip

    Hi Babu,
               In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
    Please find the XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
         <xsd:complexType name="VEND_FILE_DT">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   8f584d80456311dccd680018fe79f69b
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb0390c11dc843000188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb4390c11dc84e800188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor name4
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb5390c11dcbe3400188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor City
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb6390c11dc896100188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor PO Box
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0335fd11dc9e9600188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor House No &amp; Street
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0435fd11dc98b000188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Postal Code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0535fd11dc870500188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Country
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7ca8d600403b11dcc9bd00188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Tax Number 1
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7040e611dcce4300188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Telephone number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7140e611dc8f3900188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             VAT Registration Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7240e611dccef700188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Account Number of Vendor or Creditor
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7340e611dcb3bc00188bd09370
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • 37 Status code in  IDoc to File Scenario

    Hi Experts,
    I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
    while I am testing from SAP backend system (All required configuration steps are also good).
    I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
    please help me.
    Thanks in advance,
    Regards,
    Sudeepth.

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • R/3 46C(IDOC) -- XI -- Flat file scenario

    Hi
    Is there anyone who could give me information on a R/3 46C(IDOC) --> XI --> Flat file scenario?
    Many thanks!
    br
    Göran

    Hi Manish
    We are using a standard IDOC called PROACT.PROACT01
    (We are using transaction sa38(Report RSMIPROACT) in R/3 to send our IDOC.)
    First we create the technical and business systems in SLD
    Second we transfer these to the repository.(I think the only thing you need to do is to update the SLD cache to get them there - Design : Integration builder --> Environment --> clear SLD cache)
    Then we just use the configuration wizard(Configuration : Integration builder --> Tools --> configuration wizard) to map everything together - defining sender and receiver etc(You get the configuration wizard tool by patching XI to patch level 4 or 5).
    I assume that you have made all the configurations accordingly to the XI configuration guide which you can download from the service marketplace.
    This is just a hint but maybe it can give you a start.
    br
    Göran

  • Seeburger IDOC-to-File scenario: Error using Classifier module

    Hello,
    I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
    In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
    localejbs/SeeClassifier        classifier
    localejbs/CallBicXIRaBean      bic
    CallSapAdapter                 0
    classifier   attID             classifierAtt
    classifier   destSourceMsg     MainDocument
    classifier   showInAuditLog    true
    bic          classifierAttID   classifierAtt
    bic          destEncoding      UTF8
    bic          destSourceMsg     MainDocument
    bic          destTargetMsg     MainDocument
    bic          mappingName       AUTO
    bic          newLine           true
    bic          srcEncoding       UTF8
    After conversion in XI, the file fails to write to the folder because of this error:
    Message processing failed. Cause: javax.resource.ResourceException: ---
    Conversion of synchronous request from module chain ended with errors
    ---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
    See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
    Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
    BICMapping Error: The mapping [not specified] you are trying to load cannot
    be found in the right path! Maybe you forgot to compile or to activate the
    mapping!
    When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine.  But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
    I am only facing this problem for the IDOC-to-File scenario.  Somehow the same configuration works for a File-to-IDOC scenario.
    I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be.  Has anyone encountered this problem before?
    Any suggestions would be appreciated.
    Thanks,
    Arianne

    Hi Yomesh,
    Here is the payload.
    <?xml version="1.0" encoding="UTF-8"?>
    <LIST>
      <S_ISA>
        <D_I01>00</D_I01>
        <D_I02/>
        <D_I03>00</D_I03>
        <D_I04/>
        <D_I05>ZZ</D_I05>
        <D_I06>CELORGS01</D_I06>
        <D_I05_2>ZZ</D_I05_2>
        <D_I07>AVX</D_I07>
        <D_I08>032008</D_I08>
        <D_I09>1718</D_I09>
        <D_I10>X</D_I10>
        <D_I11>00401</D_I11>
        <D_I12>000000008</D_I12>
        <D_I13>0</D_I13>
        <D_I14>T</D_I14>
        <D_I15>^</D_I15>
        <S_GS>
          <D_479>PO</D_479>
          <D_142>CLS01</D_142>
          <D_124>058895921</D_124>
          <D_373>20080320</D_373>
          <D_337>1718</D_337>
          <D_28>8</D_28>
          <D_455>X</D_455>
          <D_480>004010</D_480>
          <S_ST>
            <D_143>850</D_143>
            <D_329>800001</D_329>
            <S_BEG>
              <D_353>00</D_353>
              <D_92>SA</D_92>
              <D_324>4500005037</D_324>
              <D_373>20051110</D_373>
            </S_BEG>
            <S_CUR>
              <D_98>BY</D_98>
              <D_100>USD</D_100>
            </S_CUR>
            <S_FOB>
              <D_146>CC</D_146>
              <D_309>OR</D_309>
              <D_352>FREE CARRIER</D_352>
              <D_334>02</D_334>
              <D_335>FOB</D_335>
              <D_309_2>DE</D_309_2>
            </S_FOB>
            <S_ITD>
              <D_336>01</D_336>
              <D_333>3</D_333>
              <D_351>45</D_351>
            </S_ITD>
            <G_SN9>
              <S_N9>
                <D_128>L1</D_128>
                <D_369>GEN</D_369>
                <S_MSG>
                  <D_933>TEST</D_933>
                </S_MSG>
                <S_MSG>
                  <D_933>MESSAGE</D_933>
                </S_MSG>
              </S_N9>
            </G_SN9>
            <G_SN1>
              <S_N1>
                <D_98>BY</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
                <S_PER>
                  <D_366>BD</D_366>
                  <D_93>Graham Crawford</D_93>
                </S_PER>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>BT</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>SE</D_98>
                <D_93>3M COMPANY</D_93>
                <D_66>92</D_66>
                <D_67>0000019591</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>ST</D_98>
                <D_93>SAMPLE</D_93>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SPO1>
              <S_PO1>
                <D_350>00010</D_350>
                <D_330>10.000</D_330>
                <D_355>EA</D_355>
                <D_212>10</D_212>
                <D_639>PE</D_639>
                <D_235>BP</D_235>
                <D_234>230-1812-01JDS</D_234>
                <D_235_2>EC</D_235_2>
                <D_234_2>A00000000000002</D_234_2>
                <G_SPID>
                  <S_PID>
                    <D_349>F</D_349>
                    <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
                  </S_PID>
                </G_SPID>
                <S_REF>
                  <D_128>CO</D_128>
                  <D_127>4500005037-00010</D_127>
                </S_REF>
                <G_SSCH>
                  <S_SCH>
                    <D_380>10.000</D_380>
                    <D_355>EA</D_355>
                    <D_374>002</D_374>
                    <D_373>20051208</D_373>
                  </S_SCH>
                </G_SSCH>
              </S_PO1>
            </G_SPO1>
            <G_SCTT>
              <S_CTT>
                <D_354>1</D_354>
              </S_CTT>
            </G_SCTT>
            <S_SE>
              <D_96/>
              <D_329>800001</D_329>
            </S_SE>
          </S_ST>
          <S_GE>
            <D_97>1</D_97>
            <D_28>8</D_28>
          </S_GE>
        </S_GS>
        <S_IEA>
          <D_I16>1</D_I16>
          <D_I12>000000008</D_I12>
        </S_IEA>
      </S_ISA>
    </LIST>
    Thanks,
    Arianne

  • HOW TO TEST SOAP SENDER TO FILE SCENARIO

    Hi gurus,
    I have designed and configured SOAP to file scenario.
    I have used http://xyz namespace in design time.
    I have created two business systems for this sceanrio.
    I have downloaded and installed soap client on my system.
    When I open this soap client it is asking
    1)URL
    2)load request from
    3)In the editor request tab what should i give.
    4)wht is the response tab here
    I want to send data to XI from SOAP and then to file.
    Please help how to give data and how to get the data format to give in the requst editor?
    Points will B rewarded
    Regards
    Sreeni

    Hi,
    You can use a SOAP client like Altova XML spy for posting a message to XI.
    The best way to do this is to use the generated wsdl for creating a soap request.
    once the wsdl file is picked up by the soap client, it automatically generates the url.
    now the response which comes back to the soap client is usually a http status code of successful post. (since u r performing an async scenario)
    also ensure u use the j2ee port while genrating the wsdl using the "Create Webservice" option in Int Directory.
    Also chk the link for the weblog on sender soap scenario.
    /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    Hope this helps.
    Award points if found helpful
    Cheers!!
    Sidharth

  • Testing of SOAP to FILE Scenario

    Hi all
    I have done with SOAP to FILE scenario.
    --> while defining web service what we need to give in the URL????
    --> How to test this SOAP to FILE scenario to see wheather it is working fine or not, what are the all options
    Thanks
    Dheeraj

    Hi Dheeraj,
    Definitely you can test it through the microsoft infopath tool.
    steps to follow:
    Executing wsdl File Using Microsoft Info Path
    1.>Click on the design a from template
    2.>Select the Web service icon and click ok
    3.>Select the radio button u2018receive and submit datau2019 and click on next.
    4.>Enter the path of the generated wsdl which u have saved and click next.
    5.>Select the interface and   click next
    6.>Select the interface and   click next. 
    7.>Double click on parameters.
    8.>Double click on the parameter (which you want to send as request). Then click on the query field and click ok.
    9.>Click next. And click Finish
    10.>Now drag the query fields on the data fields to the left side. And click preview.
    Please follow these steps I hope you will be able to test it.
    Thanks and regards,
    Nutan

  • File to file scenario...in PI7.1

    Hiiii.....
    Its my first file to file scenario...i finished al my design and Integration Builder work...
    In my Runtime workbench...in communiction channel monitoring i have
    started my sender and receiver communication channel no errors found over thr...
    but my input file still not transferred....What may the issue...help me out to sort this problem...
    With Regards....
    Dinesh Babu M

    Hi Abshiek...
    How to Release the channel lock...i checked regarding visual administration where can we find it in PI 7.1...help me out to sort this problem,....
    With Regards...
    Dinesh Babu...

Maybe you are looking for

  • ISight Camera not working after Leopard install

    On my 1st gen Intel 20" iMac, after the Leopard upgrade -- which went very smoothly -- my iSight camera no longer works. I have tried it in Photo Booth and iChat Video and it is the same in each, so it is the camera, apparently, not the application u

  • How can i get & use java true type fonts in my applet

    Hi, I could get the System fonts in my Applet by making use of Toolkit.getFontList() I have used getGraphicsEnvironment to get fonts but my browser doesn't support it.I get ClassNotFoundException. How can I get & make use True Type Fonts in my Java A

  • Line iChart x Axis Values

    Hi, This maybe a most basic and easy to answer problem - We have just started to implement xMII on-site and our problem is: We are trying to create a line grid which will compare two sets of data against each other, basically a Value versus a batch n

  • Material slip Number on Delivery note?

    Hi all,, I have a requirement to print the Material slip number on the Delivery note. Where can I find this information in VL02/ VL03.. Some one please let me know the variable that holds this information. Thanks-

  • Configurator 3 export issue

    I developed a panel, exported it into photoshop cs6 and it worked fine. I have a good grasp of the concept....the problem is that I saved the panel, reopened it in configurator to change something and now it will not export....I have tried everything