File to Idoc and Jdbc

Hi Guys,
             Can I implement a scenario wherein the data is sent to Idoc and JDBC parallelly without using BPM?
Regards,
Ashish

Ashish,
><i>If i add multiple recievers in receiver determination step without any condition, then how do i add multiple interface determinations in the area below?</i>
Once you add multiple Receivers and save the same, the Receivers will be available in the Window Below and you would need to create an Interface Determination for each of these Receivers.
As you do not have any condition, no need to add conditions.
><i>created seperate Receiver determinations</i>
You would need only ONE RECEIVER DETERMINATION and this receiver determination would in turn have multiple Interface Determinations.
Like mentioned, add multiple receivers save the Receiver Determination and in the window below, you will nopw be able to add an Interface determination for each of the receiver.
Regards,
Bhavesh

Similar Messages

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

  • Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

    Hi Experts,
    Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
    What objects i can skip.
    My PI system is 7.3 dual stack.
    I have seen below blogs, still its confusing to me.
    When and how to create an scenario in SAP PI without mapping objects.
    Pass Through Scenario with no Mapping in PI 7.1
    Appreciate your help on this.
    Regards,
    Mohan.

    Hi Mohan
    In pass thru interface you don't need to create any ESR objects, only ID objects are required.
    Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
    Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
    Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
    Regards
    Osman

  • File to idoc and no mapping?

    Hi
    We are using PI 7.0
    IDOCFileSender->PI7.0->ALERECEIVER
    we have a file in the "native" file format for an idoc, we now would like to process this file through PI and sending it to our SAP systems ALE layer. We are not allowed to call the ALE adapter directly in our SAP system from the system generating the native idoc format - it must be done only through PI !
    My question is if it is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping? In that case what should the Message Type we are using in the file-sender adapter look like?
    Hope for some help.
    Thx

    Hi,
    >is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping?
    yes
    >In that case what should the Message Type we are using in the file-sender adapter look like?
    If you have no mapping it doesnt matter, the message type will not be validated during runtime. You can take the IDoc type imported from the SAP system
    Regards,
    Udo

  • File to (IDOc and File)

    Hi,
    I have to design a File to IDoc Sceanrio in PI. From the file, i llpick up the vendor(during mapping) thorough RFC look up. If the more than one vendor comes for the particular condition then I should throw an error log(in the form of file) and no idoc should get posted. If one comes, then idoc should get posted. they do not need BPM.Is there any way to do without BPM?
    Points will be awarded for sure.
    Regards
    Manikandan

    No there isn't another way.

  • How to upload an html file using jsp and jdbc

    Hi,
    im trying to upload an html page using JSP and jdbc. but of no success.
    my aim is to keep some important html pages in the database.the file size can vary.the file has to be selected from a local machine (through the browser) and uploaded to a remote machine(where the databse resides).
    any help/sample code or pointer to any helpful link is appreciated.
    thanks in advance
    javajar2003

    When uploading a file, I use a byte array as a temporary buffer..
    So, you should then be able to store the byte array in the
    database as binary data.
    example>
    //Temporary Buffer To Store File
    byte[] tmpbuffer = new byte[860];
    //Some Code To Upload File...
    //File Should Now Be In Byte Array
    //Get DB Connection and execute Prepared Statement
    Connection con=//GET DB CONNECTION;
    String sql=insert into TABLE(page) values(?);
    PreparedStatement ps=con.prepareStatement(sql);
    ps.setBytes(1,tempbuffer);
    ps.executeUpdate();
    //Close PS and Free DB Connection
    ..... and this method looks like you dont even have
    to store the file in a byte array, you can just give
    it the input stream.
    ps.setBinaryStream(int, inputStream, int);
    You may have to make several attempts at this. I have
    uploaded a file and temporarily stored it in a byte array,
    but have never from there stored it in the DB as binary
    data.. but this looks like it'll work.
    Good Luck!

  • JAR files for SQLJ and JDBC drivers: what is the best practice?

    starting a migration from IAS 10 to WebLogic 11g.
    Apparently the jar files for SQLJ are not on the classpath by default.
    java.lang.NoClassDefFoundError: sqlj/runtime/ref/DefaultContextwhich is the better practice: putting the SQLJ runtime jar into the lib subdirectory of the domain directory, or using a shared library reference? (usage of SQLJ is pretty prevalent in our apps, though we may be getting away from it)
    are the Oracle JDBC drivers on the classpath by default?
    if not, then the same question: put them into the lib subdirectory of the domain directory, or use a shared library reference?

    I'm looking at the setDomainEnv, especially the big note at the top:
    >
    # WARNING: This file is created by the Configuration Wizard.
    # Any changes to this script may be lost when adding extensions to this configuration.
    >
    and am getting squeamish about editing it...
    http://www.bea-weblogic.com/how-do-i-disable-wls-automatically-adding-to-classpath.html looks like the default behaviour is for WebLogic to put $DOMAIN/lib;$WL_HOME/common/lib/ext;$WL_HOME/server/lib/ext on the classpath; there is also a reference to setting weblogic.ext.dirs= when starting weblogic (which means I set the WEBLOGIC_EXTENSION_DIRS environment variable).
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/libraries.html#wp1067450 also refers at the bottom to using the domain /lib subdirectory.
    so am I correct that a good practice is to just put the jars I think I will globally need into $DOMAIN/lib, rather than putting them in $WL_HOME/common/lib/ext, $WL_HOME/server/lib/ext, or fiddling with the WEBLOGIC_EXTENSION_DIRS environment variable?
    Edited by: user8652010 on Feb 10, 2011 1:08 PM

  • Regarding file content conversion and jdbc adapters

    hi
    can any one send me the details about the sender jdbc adapter and the receiver jdbc adapter.
    i need the output of sender jdbc adapter(structure)also fro the receiver jdbc adapter.
    for file content conversion -
    can any one send abt the sender and receiver of the FCC adapter.
    also provide some links abt these in blogs.
    thanks in advance .

    Hi..
       You can search those links in SDN.
    FILE to JDBC Adapter using SAP XI 3.0 --Receiver Jdbc adapter .
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/jdbcTOJDBC& ---for both sender and receiver jdbc adapter configuration
    Content Conversion (Pattern/Random content in input file) ---for FCC
    Regards,
    Leela

  • Steps for File to IDOC and IDOC to file Scenario

    Settings to be done at R/3 like SM59,WE21,WE20
    Setting to be done at XI
    Can pls somebody send good blog for it.
    Regards
    Raj

    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.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    Cheers..
    Vonkolu

  • My scenario is file to Idoc and we are using multiple receivers.

    Whenever we executes the scenario, getting the error u201CATTRIBUTE_IDOC_METADATA u201Cin sxmb_moni 
    Any suggestions on how to do solve this?

    Hi,
    >>>>Error: Copy Receiver from Payload: Receiver Is Missing in Payload
    Have you checked "Apply control records from payload " in IDOc receiver communication channel?? If so please make sure that you've mapped RCVPRN accordingly  in control record of IDOC.
    Refer below discussions
    Error in SXMB_MONI as"Copy Sender from Payload: Sender Is Missing in Payloa
    IDOC Error - Copy Sender from Payload: Sender Is Missing in Payload
    Regards,
    Priyanka

  • Problem with Sender Agreement for EDI File to Idoc scenario

    I'm configuring PI for EDI with Seeburger Adapter (Calling as a Module) and I'm having an issue with the Sender Agreement using File Adapter.
    Process used is File to IDOC. EDI data will be picked up from VAN (Using existing FTP process rather than using Seeburger FTP) and stored in a folder which is being accessed by PI  to send to R/3 to create orders.
    All my inbound EDI will be stored in same folder which should be picked up by XI and distribute the same depending upon the respective scenario's in ID and respective mapping/config in IR.
    The whole process IR & ID works fine and also creates Idoc in R/3, if I configure for one customer for EDI 850, but when I try to configure for second customer for same EDI 850 having same ANSIX12 version (V4010) as previous customer, I get stuck at the Sender Agreement part for this second customer because I use the same CC for File read for both the customers (Scenarios) and since there is a limitation with File Adapter "sender channel must not be assigned to more than one sender agreement ".
    How can I create the Sender Agreement using the same CC for my other scenario?
    I tried creating multiple CC for different scenario but when I place a test file for customer A, I see that its being picked up by both CC's.
    Pl Advise.
    Thanks!
    PSR

    You need to configure splitter as module in sender file adapter (classifier->bic->splitter) as well as define a message splitter(with partner number and Seeburger mapping) in Seeburger workbench.
    Thank you for the reply Aamir,
    Do you have any document which can guide me through the process?
    Does Seeburger Workbench play any role here? because I'm not using See FTP adapter to connect to my VAN. We get the data from the VAN using FTP process but not using See FTP. I'm using BIC to generate an XSD and SDA file, rest everything is in XI using File to idoc and IDOC to file process.
    Thx
    PSR

  • File- to -IDoc   scenario  EXPLINATION   in a  INTERVIEW

    Hi  ,
        What are the configurations done on XI, on R3, on XI's SLD, what is the protocol used for File, Content Conversion, Serialization , etc
    I know how to  do the step by step procedure... but plz let me know how can we explain  the same thing in an  interview..
    plz give a small explination about all  the above  steps..
    thanks
    Babu

    > Hi  ,

    hi babu,
    <i>> What are the configurations done on XI, on R3,</i>
    configuration on XI
    RFC destination to R3
    Loading metadata
    configuration on R3
    create a logical system
    RFC destination to XI
    create a Transaction Rfc pointing to XI RFC Destination
    <i>>>what is the protocol used for File</i>
    Here it depends on the where the file is located. If the file is in same Local network as XI is then NFS (Network File system is best suited)
    Otherwise FTP
    FTP protocol is used more frequently
    <i>>Content  Conversion</i>
    In case of File to IDoc and suppose if the file that need to be picked up is not in XML format then we will go for Sender File Content conversion, otherwise not
    <i>>>XI's SLD</i>
    You will create a technical system for
    R/3 system
    Third party system (file system)
    You need to create a business system for the R/3 Technical system
    regards
    Ramesh P

  • ATTRIBUTE_IDOC_METADEATA Error: File  to IDOC Java Mapping

    I have done a Java Mapping from File to Idoc and I get the following error in sxmb_moni:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
    <SAP:P1>I::000</SAP:P1>
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Fehler: I::000</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    The Idoc structure that I generate in my mapping makes no fullfil of the IDOC tags.
    For example:
    <IDOC BEGIN="1">
                   <EDI_DC40 SEGMENT="1">
                        <TABNAM/>
                        <MANDT/>
                        <DOCNUM/>
                        <DOCREL/>
                        <STATUS/>
                        <DIRECT/>
                        <OUTMOD/>
                        <EXPRSS/>
                        <TEST/>
                        <IDCOTYP/>
                        <CIMTYP/>
                        <MESTYP/>
                        <MESCOD/>
                        <MESFCT/>
                        <STD/>
                        <STDVRS/>
                        <STDMES/>
                        <SNDPOR/>
                        <SNDPRT/>
                        <SNDPFC/>
                        <SNDPRN/>
                        <SNDSAD/>
                        <SNDLAD/>
                        <RCVPOR/>
                        <RCVPRT/>
                        <RCVPFC/>
                        <RCVPRN/>
                        <RCVSAD/>
                        <RCVLAD/>
                        <CREDAT/>
                        <CRETIM/>
                        <REFINT/>
                        <REFGRP/>
                        <REFMES/>
                        <ARCKEY/>
                        <SERIAL/>
                   </EDI_DC40>
    Should I complete these values in my mapping program?
    Which values should I complete?
    Thank You.

    Antonio,
    you can ignore whole EDIDC Segement make disabled in our mapping still it works . but the problem is not with this is our meta data chekc in IDX2 t/c code of XI box.
          it has some problem the strcuture you generate and R/3 accepts are not same their is mismatch in structure
    Regards
    Sreeram.G.Reddy
    Message was edited by:
            Sreeram Reddy

  • How to convert XML into idocs and post in ECC using PI

    Hello All,
    I want to configure the scenario like this MDM->PI->ECC. Using FTP I am getting able to fetch the xml file from MDM Server Ready folder. Now, I need to convert this XML file into Idocs and post it in ECC. Can anyone provide me step by step configuration in PI to achieve this. I have configured communication channel with adapter type Idoc in Itegration Builder. But, I am not sure where it will do the conversion of XML into Idoc and how do post it to ECC. I am working first time on PI 7.1. I have worked on XI 3.0 in 2006-2007. Any help to configure this step by step shall be appreciated.
    Thanks & Regards,
    Hemal

    In you have the XML from MDM you have to use the mapping provided by the funtionals in the Funtional specification documents. once you did it you must configure the Receiver IDoc Adapter. and later dont fonget to configure properly the ReceiverAgreement.
    as you receive the docuement from MDM via FTP, thats not a SAP System that means that you have to define PI as the sender of the IDoc,otherwise you will have the Error "Unable to convert the sender service to an ALE logical system"
    to do that in the receiver Agreement>Header Mapping>Sender System-->Select PI server.
    Take in mind to send IDocs to any SAP System, the system that send it must be a SAP system too. thats why you configure it
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/frameset.htm
    Another thing is you have configure the ALE distribution Model.
    se this:
    http://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Let us know
    Rodrigo P-.

  • Multi mapping.. is it possible File to Idoc & FIle .. its urgent?????

    Hi All,
    File to Idoc & File.
    I need to pick the file and i need to do multi mapping, so that from the file we can generate
    one idoc which has to go to SAP and
    one acknowledgment's file and sent back to partner.
    Based on the below blog, looks like we can't use Idoc adapter when the target message is Idoc using Multi mapping.
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    Can anyone suggest me how i can achieve this scenario without using BPM.??
    Regards
    Seema.

    Hi,
    The Multi mapping is possible without BPM but not for IDOC as its not part of Java Stack. IDOC adapter is on ABAP stack.
    As Raj have suggested,
    You could create two different Mappings one for file to IDOC and another for file to file as an acknowledgment.
    In Receiver determination you need to use multiple receivers as IDOC --R/3 receiver and the File receiver system.
    It will create the IDOC as well as push the acknowledgment to file also.
    But incase if you get any problem with sending the IDOC then also you will get successful acknowledgment via file. So directly there will not be any relation between these IDOC and File receivers as an delivery recipt of IDOC.
    Here either you have to use the IDOC acknowledgment feature or BPM or Alert notification to get the exact notification about the IDOC posting to receiver system.
    Please refer below links
    1. IDOC acknowledgment
    This Feature is Available under SP 18 and we are on SP16
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    Check this document on handling IDOC acknowledgements. This might give you some pointers.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    This Feature is Available under SP 18 and we are on SP16
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    Check this document on handling IDOC acknowledgements. This might give you some pointers.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    How to Handle Acknowledgments for IDoc (NW7.0)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    IDOC acknowledgements
    2. BPM
    File to IDOC with BPM
    File to idoc with BPM
    Problem in BPM implementation
    Use Aleaud in BPM
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    3. Alert Notification
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
    Thanks
    Swarup

Maybe you are looking for