Outbound Interface(Applicaion server)

Hi all,
currently iam working on outbound interface,in which i have the data in one internal table,now i need to download this to application server with this path
'/usr/sap/ED1/file.txt',can anyone give me the logic or code to do this.
Points assured...

Hi srinivas,
I have done it like this,but still its not working
u can check the code if u want..
    Open dataset '/usr/sap/ED1/file.txt' for output in text mode ENCODING DEFAULT.
    IF SY-SUBRC <> 0.
    MESSAGE E111.
    WRITE :/ 'UNABLE TO OPEN'.
    ENDIF.
    Loop AT I_DOWNTAB.
      TRANSFER I_DOWNTAB-RESULT to '/usr/sap/ED1/file.txt'.
      IF SY-SUBRC <> 0.
      G_FLAG = 'F'.
      ENDIF.
    ENDLOOP.
  close dataset '/usr/sap/ED1/file.txt'.
  IF G_FLAG IS INITIAL.
  MESSAGE S113.
  ELSE.
  MESSAGE E111.
  ENDIF.
  ENDIF.
  OPEN DATASET '/usr/sap/ED1/file.txt' FOR input
             IN TEXT MODE
             ENCODING DEFAULT
             MESSAGE G_MESSAGE.
  IF SY-SUBRC <> 0.           "ERROR WHILE OPENING THE FILE
             WRITE: / G_MESSAGE.
             EXIT.
  ENDIF.
  DO.
             READ DATASET '/usr/sap/ED1/file.txt' INTO I_UNIX_INTAB.
             IF SY-SUBRC NE 0.
                  EXIT.
                  ELSE.
                  APPEND I_UNIX_INTAB.
             ENDIF.
  ENDDO.
  CLOSE DATASET '/usr/sap/ED1/file.txt'.
  LOOP AT I_UNIX_INTAB.
  REPLACE ALL OCCURRENCES OF '"' IN I_UNIX_INTAB WITH ''.
      CONDENSE I_UNIX_INTAB NO-GAPS.
    SPLIT I_UNIX_INTAB-FIELD AT CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB INTO I_DOWNTAB-RBUKRS
    I_DOWNTAB-PRCTR I_DOWNTAB-RFAREA I_DOWNTAB-ACCN_TYP I_DOWNTAB-RASSC I_DOWNTAB-PPRCTR
      I_DOWNTAB-RLDNR I_DOWNTAB-RRCTY I_DOWNTAB-RVERS
      I_DOWNTAB-POPER I_DOWNTAB-GJAHR.
     I_DOWNTAB-HSLVT I_DOWNTAB-KSLVT I_DOWNTAB-HSL01 I_DOWNTAB-KSL01.
    APPEND I_DOWNTAB.
    CLEAR I_UNIX_INTAB.
  ENDLOOP.

Similar Messages

  • How to place Outbound Interface file in APPS SERVER?

    Hi Guys,
             Actually I'm running the below pl\sql procedure for the OutBound interface file.
    CREATE OR REPLACE procedure GE_INV_Out_BAL(Errbuf OUT varchar2,
                                           Retcode ouT varchar2,
                f_id    in number,
                t_id    in varchar2) as
    cursor c1 is select
           msi.segment1 item,
        msi.inventory_item_id Itemid,
        msi.description  itemdesc,
        msi.primary_uom_code Uom,
        ood.organization_name name,
        ood.organization_id   id,
        mc . segment1||','||mc.segment2 Category
        from
        mtl_system_items_b           msi,
        org_organization_definitions ood,
        mtl_item_categories          mic,
        mtl_categories               mc
        where
        msi.organization_id       = ood.organization_id
        and msi.inventory_item_id = mic.inventory_item_id
        and msi.organization_id   = mic.organization_id
        and mic.category_id       = mc.category_id
        and msi.purchasing_item_flag = 'Y'
        and msi.organization_id between f_id and t_id;
    x_id     utl_file.file_type;
    l_count  number(8) default 0;
    begin
              x_id:=utl_file.fopen('/u02/oracle/SUPPORT1','invoutdata.dat','W');
               --select * from v$parameter where name like '%utl_file%'
    for x1 in c1 loop
    l_count:=l_count+1;
    utl_file.put_line(x_id,x1.item    ||'-'||
            x1.itemid  ||'-'||
            x1.itemdesc||'-'||
            x1.uom   ||'-'||
            x1.name   ||'-'||
            x1.id   ||'-'||
            x1.category   );
    end loop;
    utl_file.fclose(x_id);
    Fnd_file.Put_line(Fnd_file.output,'No of Records transfered to the data file :'||l_count);
    Fnd_File.Put_line(fnd_File.Output,' ');
    Fnd_File.Put_line(fnd_File.Output,'Submitted User name  '||Fnd_Profile.Value('USERNAME'));
    Fnd_File.Put_line(fnd_File.Output,' ');
    Fnd_File.Put_line(fnd_File.Output,'Submitted Responsibility name '||Fnd_profile.value('RESP_NAME'));
    Fnd_File.Put_line(fnd_File.Output,' ');
    Fnd_File.Put_line(fnd_File.Output,'Submission Date :'|| SYSDATE);
    Exception
    WHEN utl_file.invalid_operation THEN
      fnd_file.put_line(fnd_File.log,'invalid operation');
      utl_file.fclose_all;
    WHEN utl_file.invalid_path THEN
      fnd_file.put_line(fnd_File.log,'invalid path');
      utl_file.fclose_all;
    WHEN utl_file.invalid_mode THEN
      fnd_file.put_line(fnd_File.log,'invalid mode');
      utl_file.fclose_all;
    WHEN utl_file.invalid_filehandle THEN
      fnd_file.put_line(fnd_File.log,'invalid filehandle');
      utl_file.fclose_all;
    WHEN utl_file.read_error THEN
      fnd_file.put_line(fnd_File.log,'read error');
      utl_file.fclose_all;
    WHEN utl_file.internal_error THEN
      fnd_file.put_line(fnd_File.log,'internal error');
      utl_file.fclose_all;
    WHEN OTHERS THEN
      fnd_file.put_line(fnd_File.log,'other error');
      utl_file.fclose_all;
    End GE_INV_Out_BAL;
                                     It is working nice.The interface file is going and placed in the given path of the DB server.But the Requirement is the file should be placed in the app server.Is their method to place the file Directly in App server.please convey your suggestions.

    Hi,
    The requirement seems to be similar to the one posted in the link https://forums.oracle.com/thread/848476. Please check.

  • Outbound interface using dataset

    Hi,
         Please send me example program for outbound interface to maintain file in application server.
    Thanks
    Ali

    Hi,
    the code should look like below.
    declare:
    filepath_name TYPE rlgrap-filename,
    internal table itab.
    **Populate data to itab.
    OPEN DATASET filepath_name FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
          IF sy-subrc = 0.
            LOOP AT itab.
              TRANSFER itab TO filepath_name .
            ENDLOOP.
          ELSE.
            MESSAGE i001(00) WITH 'Error writing to file in remote computer'.
          ENDIF.
          CLOSE DATASET filepath_name .

  • Outbound interface program for downl;oading text file

    Hi,
    I m working with outbound interface program which downloads text file into application and presentation server upon the selection.
    My probelm is
    The data format in the text file
    Whenever interface sends 1 record to the text file and next record should start continuation to the first record with
    seperator like some synbol.
    Please tel me posr the sent for this

    Hi,
    I m working with outbound interface program which downloads text file into application and presentation server upon the selection.
    My probelm is
    The data format in the text file
    Whenever interface sends 1 record to the text file and next record should start continuation to the first record with
    seperator like some synbol.
    Please tel me posr the sent for this

  • Driver program for outbound interfaces

    hi
    i am having 5 outbound interfaces for which i need to make a driver program
    in my driver pgm i need to make a selection screen which consists of 2 radio buttons
    1 . presentation server
    2. application server
    when we select presentation server all the 5 inerfaces prestation server down load path must execute at a time .
    in the same way if we select application server all 5 interfaces application servers must execute
    can any one help with sample code
    urgent
    regards
    sachin

    Hi sachin,
    can you explain a little more about ur req, like what do you mean by "down load path must execute at a time"
    Regards
    Raj

  • Messages are Archived but cannot be seen in Outbound Interface in RWB

    Hi Experts,
    I am having File to RFC scenario......where files are successfully pinged from FTP server and getting archived.....
    but when I check in RWB the files are not found in Outbound Interface in Message Monitoring...........
    Then I am deleting the Archived files and placing again manually in FTP server......Then files are archived and seen in
    outbound interface successfully......
    I m not getting where the exact problem is.........From 2 days I m placing manually the files after checking the files are not
    seen in Outbound Interface....
    Please help me out.....
    Regards,
    Sudheer

    Hi Sandeep,
    I have checked the File Communication Channel.......
    Tick check-box of "Add Time Stamp". --- OK
    Give path of Archive Directory correctly & complete. -- OK
    Also choose "Empty file Handling" for Process Empty file. -- Not Checked.
    Regards,
    Sudheer

  • Outbound interface configuration in ID

    Hi Friends,
    What configuration I need to do in ID for outbound interface???

    I had definied outbound interface but when I am testing the configuration by giving sender service,interface namespace and receiver service, and payload,
    its giving error in Interface determination and mapping .
    trace file for that is as follows... kindly suggest when the error can be..
    Interface Mapping
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy209.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -&gt; com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MSG_ORD_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy209.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy209.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -&gt; com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more

  • Outbound interface to XI

    Hi all,
    I am developing an Outbound interface in HR. I need to send the data retreived to XI system.
    What is the procedure for sending this to XI after i retrieve the records into one Inetrnal Table. Is there any Functional Module for this...
    Pls, Provide your suggestions,
    Thanks
    Phani
    Edited by: Phani B on Oct 16, 2008 11:29 AM

    Write to the data in al11 or to an FTP server ( Say sapout/hr/ XXXXXX ) . Ask the XI consultant to process the files that are wriiten in that path path , he will use an file adapter to pick up these files and it will get processed.

  • How to maintain an errors in Outbound Interface

    Hi,
    I m Doing One Interface (Outbound From SAP) to Application Server?
    whenever the File(TXT) in Created in Legacy Application Server with Succeesfull Record i have to Send an Email Notification to my Payroll 
    Adminisatrtor Of the legacy System.
    Can any one Pls tell me the steps Howto DO this?
    An also
    If there is any error records found which tranferring Data to ths Legacy System.An Output shoul be display with error records.
    How to maintain this in Interface Program.
    Regards
    Uday Kiran

    Hello,
             You can follow the below procedure as one of the Error Notification mechanism.
    1. If you are using a Standard Selection Program, then you can find the relevant exit to populate all the Errors in an Internal Table with
      Error Field Name
      Error Segment Name
      Error Message.
    2. Then, you can append all the errors (data mismatch , inconsistency) to that Internal Table, I_ERR_TAB per say.
    3. After that, Export the same to Memory ID.
    4. In an Outbound Interface, after the Selection Program is processed, a Standard Function Module is Called, that is IDOC_CREATE_ON_DATABASE.
    5. Go to that Function Module, and Create an Enhancement Implementation (In case of ECC 6.0) where you'll IMPORT the I_ERR_TAB from Memory ID.
    6. Check if the I_ERR_TAB is initial. If it is not, then you can probably use the FM SO_OBJECT_SEND or SO_DOCUMENT_SEND_API1 or any other FM available for Sending Mails to the respective Persons / Users.
    7. Along with sending mail, you can also error out the IDoc by Calling the FM IDOC_STATUS_WRITE_TO_DATABASE where you'll update the IDOC_STATUS table with the errors that you have in your I_ERR_TAB table and set the Status as 26.
    Hope it was helpful.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • Creation of one outbound interface for two diferent senders

    helo.
    i just want to conform ont thing that .
    my scenario is  two diferent files from 2 diferent business systems are sending to one Rfc.
    so i was created only one outbound interface for both senders and one message type bcos the file structure is same for both senders.
    so is there any thing wrong in creating only one datatype,message type,message interface for both senders.
    waiting for your response.
    cheers.
    seeta ram.

    Hi Ram,
    That is perfectly correct when you have two senders and one receiver Scenario and <b>Business Service is different</b>. Then you can use the same Interface.
    Just keep in mind that the key for XI to recognise the Right interface is combination of these 3 parameters:
    Sender Service, Sender Interface and Namespace. These cannot be duplicated.
    When the Message type is same in the sender input data then you can create just one Message Type and One Data type and RFC is anyhow the imported RFC which you need not have to worry.
    In Configuration Scenario you need to configure separately the RD, ID, CC and Agreements for the Interfaces.
    Hope this answers your query. Let us know if you need anymore clarification
    Thanks
    Srini

  • In PI 7.1, condition editor does not show the outbound interface structure

    Hello,
    I am using PI 7.1, I need to use condition whild determing receivers. So I opened the condition editor, then open the expression editor, select XPath instead of Context object. I would expect that the outbound interface structure appears in the box underneath the XPath, so that I can navigate the structure to choose the field I want to use. However nothing appears here. Do you knwo why is that? Or do I need to do anything to bring up the outbound interface structure in the expression editor?
    Thanks
    Jayson

    Hi Jayson,
    I had the same problem
    the use of context objects and the value help for xpath is available for XI3.0 interfaces in PI 7.10 only. The functionality for "new" interfaces has been implemented in 7.11 only.
    you have to use xpath w/o value help.
    I have created a context object in one of our 7.10 test systems, and indeed I was unable to use it in a receiver determination unless the service interface pattern is "Stateles (XI 3.0 compatible)". If you were to change the service interface to that pattern, you have to change the operation name unless it is already identical to the interface name. So that may not be an option for you.
    It was possible to use the context object in a receiver rule but then I could not activate the receiver determination because the software component version was supposedly unknown. I will check with my PI contacts - please let me know if the change to "XI 3.0" interface would be a possible workaround for you.
    Try the steps which I am giving below, although it's a workaround and don't know the exact reason why it is failing.
    1. Open your Outbound Message Interface (which you are using in your Receiver Determination) in IR, edit it and change the Interface pattern (which is there just below the category "Outbound") to "Stateless (XI30 - Compatible)" , save it activate it.
    2. Follow the same step for your Inbound Message Interface. Change the Interface Pattern from "Sateless" to "Stateless (XI30 - Compatible)" .
    3. Go to ID. Remove your Outbound and Inbound Message Interface from their respective Business Service/Comp and add it again.
    4. Create your your receiver determination again using the Outbound and Inbound MI you have changed.
    5. Open condition editor of your receiver determination.You should be able to see your Message Interface and can choose the XPath.
    Thanks,
    Raj
    Edited by: raj reddy on Jan 21, 2009 5:41 PM

  • Outbound interface determination in file adapter?

    In my scenario files with different schemas can be send to XI from the same directory using the file adapter (so each file has a different interface that must be mapped etc.).
    I cannot add multiple interfaces to the file adapter in sender agreement and determine the outbound interface by some condition. Interface must not be "*".
    I thought about creating multiple file adapters (all listening to the same directory) and sender agreements. Each adapter is listenig to specific file type only (e.g. *.yxz, *.abc). So before putting the files to the input directory the file extension must be changed so that only the right adapter reads the file and XI gets the right interface.
    Is there abetter way to do this???

    These blogs will be usefull i guess..
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi
    /people/ravikumar.allampallam/blog/2005/02/17/bridging-the-sync-async-bridge-with-fork-xi
    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    /people/daniel.graversen/blog/2006/09/07/using-a-bpm-to-collect-messages-for-a-set-interval-of-time
    Reward points if usefull........

  • Outbound interface file for the employeesu0092 deduction information from the d

    How to Create an Outbound interface file for the employees’ deduction information from the different Payroll Companies.
    Thanks in advance.
    Regards
    vamsi.

    Hi,
    The requirement seems to be similar to the one posted in the link https://forums.oracle.com/thread/848476. Please check.

  • Problem with Outbound Interface for Party in Standard XI Content for SNC

    Hi All,
    I am configuring a standard XI Content for SNC, the ASN Processing (DIMP ERP Backend). The provided Integration scenario involves three swim lanes which corresponds to an ERP, SCM and an external system. The external system is as an application component that is designed for B2B communication, i.e. a service with party which is called Supplier. 
    The first action within the scenario is Create ASN in the Supplier swim lane and send a message to the action "Receive ASN and update inventory(in transit)" within the SCM system swim lane. I have created a sender party that corresponds to the Supplier swim lane and also a receiver party that corresponds to the SCM system.  I used the Integration Scenario Configurator to assign services and also all the comm. channel. However, when i try to generate the logical routing objects and collaboration agreements, i get the error message that there was no outbound interface associated with the sender(the external system) defined for the first action. There is no option within the Integration Scenario Configurator on how to assign/define the outbound interface that I want to use for the sender.
    I have no idea how to assign the outbound interface to the action for the Supplier swim lane in an Integration Scenario that is from an XI Content. Has anybody configured something similar or come across the same problem?  Any info will be much appreciated.
    Luqman

    Hi,
    This could be the problem of confilting namespace or combinations.
    in receive action just check that right message interface is configured at Inbound side.
    just check any place void ?
    1)just check the name as case sensitive.
    2)Just check is there interface belongs to right software component.
    3)Just check mapping assigned to the right combination or not.
    its better to cross check all the component are assigned to right place or not.
    ****if helpful then rewards points
    Regards,
    Sumit Gupta

  • More than one outbound interface for the webservice scenario

    Hi Experts,
    Is it possible to have more than one outbound interface for the Webservice synchronous scenario? I have tried it , but I couldn't implement it.
    I would like to have your suggestions.
    Regards
    Sara

    Hey,
    Creation of a wsdl file
    /people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
    N:1 seemz he was refering to multimapping scenario.
    <b>Cheers,
    *RAJ*
    *REWARD POINTS IF FOUND USEFULL*</b>

Maybe you are looking for