IDoc to AS2 scenario connection issue

Hi Experts,
IDoc to AS2 scenario.
i am geeting below connection  error  while sending data from PI to Third Party Partner.Please help me on this issue i will appriciate you .
MP: exception caught with cause javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: java.net.SocketException: Connection reset # , SEEBURGER AS2: java.net.SocketException: Connection reset #
Thanks,
Aadi

Hi Srini,
Thanks for your reply.
after changing the timeout also i am getting same error
Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: java.net.SocketException: Connection reset # , SEEBURGER AS2: java.net.SocketException: Connection reset # .
Please help me on this issue.

Similar Messages

  • Error is Receiver AS2 adaptor used for Idoc to AS2 scenario

    Hello Experts,
       I am doing Idoc to AS2 B2B scenario where I am getting below error message in runtime workbench comm channel monitoring.
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
    Sending failed.
    Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 10/16/09 9:06 AM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321)
    AS2 Adapter failure
    Processing task
    Sending called. 
    Message processing started
    Basis has already configured the AS2 Server with Certificates and provided me the below details for receiver agreement and those are put in Receiver agreement.
    AS2 sender Configuration:
    Authentication certificate à TRUSTEDAS2certAS2_datapool
    AS2 Receiver Configuration:
    Decryption Key à TRUSTEDAS2certXXXenterprise2008
    Signing Key à TRUSTEDAS2certXXXenterprise2008
    XXX is my receiver partner
    For the Receiver party XXX I have maintained the Identifier as given below
    *Agency----
    Scheme-------Name*
    http://sap.com/xi/XI--XIParty--
    XXX
    Seeburger----
    AS2ID----
    XXX_AS2ID
    There is no need for sender agreement for Sender IDoc but still I tried to created R3 as sender party and R3 Business system, used it for the scenario and created sender agreement for sender Idoc but received same error message in Runtime workbench.
    R2 system sender party is also set with identifier with AS2 ID.
    MDN mode is set to no MDN in the receiver AS2 communication channel.
    Please suggest me if something is missing or wrong in the configuration.
    Thanks in advance.
    Vinit

    Hi Larry,
       The solution was very simple.
    It was problem with the basic understanding of system and configuration.
    Idoc is send sent by R3 ERP system and target is Partner Party. As ERP system is Business system and not the party w.r.t XI/PI terminology, we are not supposed to use Sender party as Sender ERP system but just use Business system as sender without any sender party. So in this way PI system could recognize that the data is coming from R3 system which is nothing but PI Business system.
    Now question comes where to user the Serder Party which was defined with AS2 ID? So answer is in the receiver determination we have to mention the Sender party and sender service in the header mapping part (Also mention receiver party and service).    
    So in my case problem was with sernder party. I mentioned sender party in all receiver determination, Interface determination, Sender Agreement and receiver agreement where only sender service ie sender system was required. And as I configured my scenario without sender party it worked because PI could recognize the sender R3 system and AS2 ID was recognized form the Header mapping of Receiver Agreement.
    Kindly let me know if it works and if you require snap shots of my configuration then I can send you the same.
    Regards,
    Vinit

  • IDOC to SOAP Scenario : Connection Refused

    Hi Everybody,
    I am working on Idoc to SOAP Asynchronous scenario.
    I have an issue with the connection from SOAP to the websystem at the receiver.
    Around 60% of the messages are processed successfully and the rest of the messages throws up errors at the receiver Adapter.
    Below is the log from Communication channel for the unsuccessful messages.
    Message processing started
    request entering
    SOAP: call failed: java.io.EOFException: Connection closed by remote host.
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connection closed by remote host.: java.io.EOFException: Connection closed by remote host.
    Is there any setting we need to make for the SOAP adapter to reduce these failures?
    Or is it a problem with the receiver websystem?
    Can somebody help me out on this?
    Thanks & Regards,
    Zabiulla

    Hi,
    For some reason the client (from the server's point of view - it might be some other device between the actual client and the server) is closing connection during the SSL handshake. As we can't get more info from the standard J2EE Dispatcher log files, we need more detailed info.
    Please check
    1. Execute network router trace utility (tracert for Windows systems or traceroute for UNIX flavours) to the J2EE Engine's host. It will show the active and non stealth routers between the client and the server:
    c:\> tracert [J2EE_host]   (windows)
    $ traceroute [J2EE_host]   (UNIX)
    2. Activated low level SSL tracing
    regards
    Aashish Sinha

  • Mapping issue in idoc to JDBC scenario

    mapping issue in idoc to JDBC scenario
    source structure
    E1KNB1M
      BUKRS = 1000
    E1KNB1M
      BUKRS=  9000
    E1KNB1M
      BUKRS=  2000
    THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
    TARGET field : ISFRANCHISE
    if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
    if BUKRS = 9000   THEN ISFRANCHISE= Y
                   ELSE
                ISFRANCHISE=N
    I've done the mapping as below
    BUKRS = 9000--> IF THEN Y ELSE N--
    > ISFRANCHISE
    BUT everry time the target value is N only
    pl suggest
    rgds
    mojib

    mapped like this
    BUKRS--->SORT---->
                                                 EQUALS --------IF---THEN    Y
    9000------------------------>                                               ----------------->ISFRANCHISE
                                                                  ELSE   N
    context of BUKRS set to parent node
    its worked
    thanks to all for valuable suggestions
    rgds
    mojib

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

  • Storage Issue in Database while executing Idoc to Jdbc scenario

    Hi,
    I am testing an Idoc to JDBC scenario. The scenario executes correctly, but the number of records getting stored in the database are not equalling the data present in the Idoc.
    Eg: If the Idoc has data for around 75000 records to be saved, only around 50000 records are getting saved in JDBC SQl server database.
    Please let me know what could be the issue and how to resolve it.
    Regards
    Kiran.

    Check the output XML in XI;ie, the output of your mapping. Does it have the same number of records as the Idoc? if no the issue is in the mapping.
    Regards
    Bhavesh

  • RFC Destination not getting connected - IDoc to XI scenario

    Hi Everybody,
    I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
    Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
    I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
    Please give me step by step solutions.... Thanks in Advance...
    Regards/Guru

    Requirements in R3 system:
    1. Create RFC destination pointing to XI in SM59
    2. Create port for XI using we21
    3. create Outbound Entry in partner Profile for XI in we20.
    Requirements in XI system:
    1. Create Technical System pointing to the R3 system.
    2. create Business System pointing to the R3 system.
    If you want to send IIDOC out of XI,
    1. SM59 - Create RFC destination
    2. IDX1 - Create port
    3. IDX2 - Import Metadata.
    Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
    Check dis link for more info:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    please refer to michel book on IDCO usage in XI
    Message was edited by:
            Sreeram Reddy

  • Issues in IDOC to File scenario using bussiness service

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

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

  • Issues in SAP(Idoc)-XI-File scenario

    Dear All,
    I am working on SAP(Idoc)-XI-File scenario. But in the Receiver agreement i am not able to see the idoc in order to specify some conditions there. 
    Please suggest if I have to do any settings in order to specify some conditions in the idoc.
    Warm Regards,
    N.Jain

    Hi nishu jain  ,
    U can specify the conditions in Reciever Determination.
    1.Go to Scenarios
    2.Choose your business scenario
    3.Click Service without party
    4.Double click Reciever Determination
    5.U wil get  screen in which there is a option called Configured Recievers.
    6.Click there.then u wil get the screen with
         Left Operand  Op Right Operand
    7.There u can specify the condition.
    Reward points if u find this useful.......
    Regards,
    gyanaraj

  • PI : Idoc to JDBC scenario : repeating segments mapping issue

    Experts
    Please help.
    Question reg. mapping for ECC idoc to JDBC scenario.
    I am using the ORDRSP idoc which has multiple segments as below.
    IDOC -> multiple E1EDK14 segments with 2 fields (QUALF and ORGID)
    Depending on the value of the QUALF field i need to populate the column in my target structure.
    QUALF 001  => Colmn a
    QUALF 002 => Colmn b
    For now my graphical mapping is very simple - QUALF => column a (done just to find out how PI mapping works)
    What happens in my case, is the PI Payload shows all the E1EDK14 segments however only the value 006 present in the first occurence goes into the target column.
    How do I repeat a mapping between QUALF and target col. for multiple occurences of the same segment?
    Please can you guide me reg. use of context, loop over segment, UDF = which will be the best solution to achieve this?

    Hi
    My mapping is as below. I will take an example of a sales order that has 2 line items 00010, 00020. The payload is as follows
    I see this payload in the SXMB_MONI transaction => Receiver grouping => Payloads
    - <ZORDRES>
    - <IDOC BEGIN="1">
    + <EDI_DC40 SEGMENT="1">
    + <E1EDK01 SEGMENT="1">
    + <E1EDK14 SEGMENT="1">
      <QUALF>006</QUALF>
      <ORGID>01</ORGID>
      </E1EDK14>
    + <E1EDK14 SEGMENT="1">
      <QUALF>007</QUALF>
      <ORGID>01</ORGID>
      </E1EDK14>+ <E1EDK03 SEGMENT="1">
    + <E1EDK03 SEGMENT="1">
    + <E1EDK03 SEGMENT="1">
    + <E1EDK03 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDKA1 SEGMENT="1">
    + <E1EDK02 SEGMENT="1">
    + <E1EDK02 SEGMENT="1">
    + <E1EDK17 SEGMENT="1">
    + <E1EDK18 SEGMENT="1">
    + <E1EDK18 SEGMENT="1">
    + <E1EDP01 SEGMENT="1">
      <POSEX>000010</POSEX>
    + <E1EDP01 SEGMENT="1">
      <POSEX>000020</POSEX>
      </E1EDP01>+ <E1EDS01 SEGMENT="1">
      <SUMID>001</SUMID>
      <SUMME>2</SUMME>
      </E1EDS01>
    + <E1EDS01 SEGMENT="1">
      <SUMID>002</SUMID>
      <SUMME>1100.00</SUMME>
      <SUNIT>GBP</SUNIT>
      </E1EDS01>
      </IDOC>
      </ZORDRES>
    There are 2 problems. First one which I discovered after posting the query. I can see only the line item 10 in the query that gets contructed in PI to insert the data into the target jdbc table. Please see jdbc receiver communication channel log below
    If you see above there are 2 E1EDP01 segments for line 00010, 00020.
    INSERT INTO  tblOItem  (IDocDate, IDocTime, SalesOrderNo, ItemNo, Plant, ItemCategory, UnitSellPrice, QuantityOrdered, QuantityAllocated, ScheduledDeliveryDate) VALUES (20111206, 135530, 0015002085, 000010, 0086, ZTAN, 0.00, 1.000, 1.000, 20111201)
    My source and target mappings are as below.
    ZSALORD
        IDOC
           BEGIN
             E1EDK01
             E1EDP01
               POSEX               =============>  SalOrdItm table column itemno
    My target side structure (idoc to jdbc scenario is as follows)
    I have mapped the E1EDP01 to Statement - I thought this will build one query per line item (per occurence of E1EDP01) but this is not working.
    MT_OITEM
      Statement
        dbtablename       ============> SalOrdItm
          action      =================> Insert
          table
          access
            Itemno      (this is one of the columns from the table)
    The occurence of E1EDP01 is 0..9999999 while the occurence of Statement node is 1...unbounded.
    Please is there any email address where I can send you screen shots if the above is not clear.
    I need to get this interface delivered as soon as possible but am STUCK.
    Edited by: gary jojo on Dec 6, 2011 3:06 PM

  • IDOC-XI-JDBC scenario,   jdbc sent too slow

    i have a IDOC-XI-JDBC scenario,
    the problem is that near 5 Lac IDOC is sent to XI, each IDOC is processes by an instance of the scenario, and the sent to the Database is too clow...means 4000 records per hour,
    can i configure the JDBC receiver adapter in a way, so that it becomes faster/more concurrent,

    Hey,
    First raise the issue to the  DBA he might help resolve the ISSUE more efficently.
    Secondly check in the JDBC adapter -> Adavance mode -> Disconnect from the data base after processing each message shouldn't be set.
    Even check with Database Transaction Isolation Level -> default is value of the connected database.
    <b>The isolation level  determines how transactions running in parallel can influence each other</b>
    http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
    Why not  the other way around > Collect multiple idocs in a file restrict maxium number of idocs to required value then send the file ?
    Stefan Grube Example:
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    if it is with bpm then collect multiple idoc with occurance change and send them.
    <b>Cheers,
    *RAJ*
    **REWARD POINTS IF FOUND USEFULL <b>

  • Wi-Fi connection issues since securing network

    Hi all,
    Hoping to get some solutions as I have tried to troubleshoot this issue with other posts and google searches. Here is my scenario :
    I'm running OS Lion 10.7.5 on my MBP and have been connected to our home wi-fi for about 12 months on a connection that wasn't secured by password.
    Since having some download issues and fearing that someone is connecting outside our household, we have secured our wi-fi and added a password.
    Both mine and my sister's iPhones got prompted to select a network, selected the appropriate one, punched in the password and were connected with no issues. My iPad Mini, Dad's laptop and both my parents' phones all connected with no issue.
    When I booted my MBP, I was prompted with needing to join a new network and upon selecting our home network was met with an immediate 'Connection timeout' response.
    I try to connect manually through Network in the System Preferences and got the same 'Connection Timeout'. When I click 'Assist me' and try to connect that way, I am finally prompted to input the password, which I do correctly and I get 'Invalid Password' etc etc response ... then after about 5 seconds it connects me !!
    So even though the connection timed out and I wasn't able to put a password in, manually doing it told me the password was wrong etc then I get connection like normal. If I switch my laptop off/reboot/log out/turn wi-fi off then back on, I'm back to square one and can't connect unless I follow the same tedious steps.
    Fearing it was an issue with our router, we have since bought a new one, installed it and reconnected all the devices as mentioned above, however my MBP connection issue still exists.
    How can I get it to connect automatically like it used to and recognize our home network with a correct password, without continually having to go through all those steps ?
    I have tried to delete that entry in my preferred networks and tried to re-establish it etc. Keychain Access doesn't list my router and input password.
    I'd like to be able to solve the issue asap if possible and hopefully without having to delete all of my other known networks that I connect to as I travel all over the country for work and have about 6-8 routers I connect to, depending on what city/office I'm in.
    Any assistance would be appreciated !

    Some users with various Wi-Fi connection problems have reported that they were given the following instructions by Apple Support, sometimes with success. I can't vouch for this procedure myself. After completing the procedure, you'll have to recreate all your settings in the Network preference pane. Make sure you know how to do that before you begin. Taking screenshots of the preference pane may be helpful.
    Step 1
    Back up all data.
    Triple-click the line below on this page to select it:
    /Library/Preferences/SystemConfiguration
    Right-click or control-click the highlighted line and select
    Services ▹ Reveal
    from the contextual menu.* A folder should open with an item named "SystemConfiguration" selected. Move the selected item to the Trash. You may be prompted for your administrator password.
    *If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). In the Finder, select
    Go ▹ Go to Folder...
    from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.
    Step 2
    Reset the System Management Controller

  • Error in IDoc to file scenario

    Hi Experts,
    I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
      <SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Please suggest me in this issue.
    Thanks,
    Bhuvan.

    Check this link:
    http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
    You might want to refer to the SAP NOTE: 316877
    Regards,
    Ravi

  • 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

  • Idoc to file scenario error

    Hell Experts,
    I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
    Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But  I didn't get successful results, always the error message shows in SXMB_MONI as follows:
    Ackn Status  contains system error
    During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
    tion in Message-Mapping transformatio~
    Exception of class CX_XMS_SYSERR_MAPPING
    My system Patche level as follows:
    SAP_BASIS     640        0012        SAPKB64012
    SAP_ABA     640     0012                SAPKA64012
    PI_BASIS     2004_1_640 0009        SAPKIPYI69
    SAP_BW     350     0009                SAPKW35009
    The above error is related to patches problems or any Mapping  problems ?
    Please  help me.
    Advanced Thanks.
    Regards,
    Chandra

    Hi,
      This may be a mapping issue, try this:
    a)in interface mapping see if grids are formed at source and target after executing the test option,
    b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
    i am not sure of the patch levels.
    Regards,
    Anirban.

Maybe you are looking for

  • VAT and CST problem

    Hi All, I am facing two problems one with order and one with the invoice, 1.While creating sales order for and intra state customer by default the system is picking the amount of the CST also along with VAT condition.Can any one help.And the same is

  • How to get BI background jobs to utilize parallel processing

    Each step in our BI process chains creates exactly 1 active batch job (SM37) with in turn utilizes only 1 background process (SM50). How do we get the active BI batch job to use more than 1 background process similar to parallel processing (RZ20) in

  • I have problems with Gmail when I open it in Firefox. The button "write a letter" doesn't work

    Dear Firefox team, I have problems with Gmail when I open it in Firefox. The button "write a letter" doesn't work. On the page it is seen as if the page is being downloaded but in fact not. As a result, I can't neither write new letters no reply to r

  • [svn:fx-4.x] 15204: TLF 1.1 Build 602

    Revision: 15204 Revision: 15204 Author:   [email protected] Date:     2010-04-02 10:41:12 -0700 (Fri, 02 Apr 2010) Log Message: TLF 1.1 Build 602 Fix 2594609 Poor text delete performance when pasting large blocks of code, selecting all, and deleting

  • Let macbook go to sleep during calibration

    hi, I've searched and searched, but could not find the answer to this question: Is it OK during calibration to let the computer go to sleep BEFORE the battery is empty? In other words, once I've unplugged it, do I have to use it for 3-4 consecutive h