Idoc to jms scenario issue

Hi All,
I have a scenario where I have PAYEXT IDocs and EUPEXR Idocs coming to XI which needs to be delivered to same target JMS queue.
I have used two mapping as they are two different IDocs. The target message structure is same for both.
Now at runtime I receive IDocs in random order, what I need to ensure is for a set of PAYEXT IDocs I have a following 1 EUPEXR IDoc. So I need to first guarantee that all PAYEXT IDocs have been sent then I can sent the EUPEXR IDoc for that set.
There is a relation between PAYEXT and EUPEXR where for a set of messages coming to XI, for number of PAYEXT there will be one EUPEXR and the EUPEXR.E1EDRD1 contains all the IDoc numbers of PAYEXT.
Thanks in advance.
Ravijeet

Ravijeet,
As you mentioned earlier you both messages are relevant. You have two options..
1. Create BPM so that you can decide which message need to send first.
2. Or as suggested by michael at SAR R/3 level make sure you send PAYEXT before EUPEXR . However SAP XI side you need to assign one single dedicated queue so that all messages will be queue in one single Message queue. You can set dedicated queue to your interface ( SXMB_ADM-->Manage Queues) so that the messages willl be process in the sequence they have received.
Hope this will help.
Thanks,
Nilesh

Similar Messages

  • IDOC acknowlegment IDOC-PI-JMS Scenario

    Hi,
    I have a IDOC-PI-JMS scenario. (With msg branching, PI 7.1 EHP1)
    The message are processing but it seems that there is no acknolegment sent back to the ECC system; the outbound IDOC remains in status 03.
    By turning acknologement off in IDX_NOALE everything is OK except the IDOC remaining in status 03.
    I found this how-to document for the IDOC-PI-IDOC scenario, but I need to configure IDOC acknowlegment for IDOC-PI-JMS scenario, someone can point to some guide/how-to? Do I need to still do all the ALE Audit configuration?
    http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    Thanks,
    Martin

    Hi Martin,
    Please go this article [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true] and [http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm] for information about How to handle the Idocs acknowledgements.
    Regards,
    Kalpana.

  • Idoc-xi-jms scenario

    Hi
    I want sender service name in the receiver payload header. How should we go abt ? I am talking abt the scenario like idoc-xi-jms.
    thanks
    kumar

    have a look at the following
    http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/frameset.htm
    Thanx
    Aamir

  • Character Encoding for IDOC to JMS scenario with foreign characters

    Dear Experts,
    The scenario is desribed as follows:
    Issue Description:
    There is an IDOC which is created after extracting data from different countries (but only one country at a time). So, for instance first time the data is picked in Greek and Latin and corresponding IDOC is created and sent to PI, the next time plain English and sent to PI and next Chinese and so on. As of now every time this IDOC reaches PI ,it comes with UTF-8 character encoding as seen in the IDOC XML.
    I am converting this IDOC XML into single string flat file (currently taking the default encoding UTF-8) and sending it to receiver JMS Queue (MQ Series). Now when this data is picked up from the end recepient from the corresponding queue in MQ Series, they see ? wherever there is a Greek/latin characters (may be because that should be having a different encoding like ISO-8859_7). This is causing issues at their end.
    My Understanding
    SAP system should trigger the IDOC with the right code page i.e if the IDOC is sent with Greek/Latin code page should be ISO-8859_7, if this same IDOC is sent with Chinese characters the corresponding code page else UTF-8 or default code page.
    Once this is sent correctly from SAP, Java Mapping should have to use the correct code page when righting the bytes to outputstream and then we would also need to set the right code page as JMS Header before putting the message in the JMS queue so that receiver can interpret it.
    Queries:
    1. Is my approach for the scenario correct, if not please guide me to the right approach.
    2. Does SAP support different code page being picked for the same IDOC based on different data set. If so how is it achieved.
    3. What is the JMS Header property to set the right code page. I think there should be some JMS Header defined by MQ Series for Character Encoding which I should be setting correctly) I find that there is a property to set the CCSID in JMS Receiver Adapter but that only refers to Non-ASCII names and doesn't refer to the payload content.
    I would appreciate if anybody can give me pointers on how to resolve this issue.
    Thanks,
    Pratik

    Hi Pratik,
         http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
    This link might help.
    regards
    Anupam

  • IDoc To JMS Scenario

    Hi,
    My Scenario is to recieve IDocs from SAP Backend System and send it to MQ queue via JMS Adapter.
    When recieving the IDoc messages in XI from SAP Backend system I get the following error message in transaction SXMB_MONI:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=KMD_SAPR3_Z52002;TS=KMD_MQ;AN=IA_XITEST;ANS=http://kmd.dk/gfx/vl906/LoadTest/SingleClient/MQ;</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have checked that receiver agreement has been set up correctly.
    Hope that someone can help.
    Regards,
    Morten

    Hi,
    Check the receiver agreement is properly configured and edit  it then save and activate and try it out
    Regards
    Agasthuri Doss

  • IDOC TO JMS CONFIGURATION

    Hello ,
               can any help me "HOW TO CONFIGURE THE IDOC TO JMS "
    plz send the screen shots for idoc to file
    thanking u

    in case of IDOCs involved you need to consider the following;
    Sent/Receive IDOC:
    you need to do the following:
    In XI
    SM59 - R3 connection pointing to R3
    IDX1 - define the port with the above dest.
    In R3
    SM59 - R3 connection pointing to XI
    WE21 - define the port with the above dest.
    WE20 - Partner profile type outbound/Inbound
    IDOC -> File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    At the JMS end, ref:
    https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are many how to guides on JMS here.
    Go through Following Weblog’s its very helpful in implementing you IDOC to JMS scenario.
    /people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

  • 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

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

  • 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

  • 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

  • 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

Maybe you are looking for

  • How can I take a picture of a camera output on the Front panel

    Hi all, I've been fighting this one for a while, But I have a DataRay WinCamD CCD image in my front panel, I need a way of saving that image to a file. I've been crawling through NI Vision and IMAQ VIs and I can seem to piece the process together. Th

  • IPhoto "sync" from MacBook Pro to Mac Mini

    Hello all, Looking for some creative advice. We have a Mac Mini as a media server where the family likes to view iPhoto stuff as well use them for the screen saver. But my wife (the family iPhoto Manager) must have the iPhoto library local on her Mac

  • How to add check box to list screen in SYCLO Agentry?

    Hi, How can I add a check box to the list screen. I want to add a new column which allows the user to select the check box. I have tried with "Allow Multi-Row Select" option. When I selected this option I am getting an error "The For Object defined f

  • Verizon Customer Care EPIC FAIL!!!! An hour I'll NEVER get back

    Got a new phone for my birthday, Optimus 2.  automated system would not allow activation unless i buy a $45 a month plan, i want to pay by the minute.  Was told about a month ago over the phone by a customer care rep named Megan that we could use the

  • Need help converting ithmb pics to jpg

    We just got back from vacation and most of our pictures were taken with the iPhone4. The problem is, when we moved the pics to our PC, they won't open. Any idea how to convert them? From what I've read in a few online posts, I'd have to download at l