AII - XI Scenarios

Hi All,
Please provide some links for small scenarios to start working with AII. I want to transfer some data from AII to R3 through XI. It will be better if i find some "How to" docs.
(I have referred blogs by Sheng Wang)
Thanks,
Uma

Have you seen the Master Guide on SAP Service Marketplace at service.sap.com/instguides : SAP Components : SAP Solutions for RFID.

Similar Messages

  • Configurations for AII

    Hi,
      Is there any document to configure the complete
      R/3/ECC-XI-AII delivery scenario involving configurations in R/3/ECC, XI, AII??? I'm sure many would ahve done it!! I'm doing a demo b4 implementing this... Kindly share any documents u have.
    Regards,
      PB

    Hi,
    Documentation on configuring ECC-AII for various scenarios is available in service.sap.com>RFID>Product Information.
    Regards,
    Ashish

  • Will ECC 4.X is enough for Auto ID RTI and Integrated Scenarios or ECC6.0 ?

    Hi Friends,
    Will all Auto ID Scenarios work with < ECC 6.0 or we need only ECC 6.0 ? Please clarify
    Thanks & Regards
    V.Rangarajan

    For SAP AII RTI Scenario you dont need SAP ECC at all.
    Except for Product tracking and authentication which requires SAP ECC 6.0 all other scenario's in SAP AII is supported by lower versions of SAP back end. R/3 4.6C is the minimum requirement.
    Regards,
    Vivek

  • XI Configuration for AII Flexible Delivery scenario

    Hi,
       I am configuring AII flexible Delivery scenario.I have succesfully tested the outbound delivery part and trying to run the ASN and inbound delivery in customer system.
       I am using One XI system to achieve this scenario.
       To achieve ASN and inbound delivery scenario,I have configured component view ASNElectronicLabelPost & ASNElectronicLabelEnrichment.
      I want to know
    1. what is the IDOC which is used to send the ASN from supplier system to XI?   
        <b>My answer:</b> The supplier's system send the IDoc DESADV.DELVRY05 or DESADV.DELVRY03. Please correct me if I am wrong.
    Also what are the precautions which i need to take if I am using single XI system.
    Thanks and regards,
    Amit Deshpande

    >>>>>>>1. Send ASN
    The supplier’s ERP system sends the IDoc DELINF.DELVRY03 or DELINF.DELVRY05 to the XI system (message interface DespatchedDeliveryNotificationOut).
    >>>as it's true
    >>>but with the info that I've mentioned (no EPC in case or delvry03)
    My understanding was that the supplier system sends the Idoc DESADV.DELVRY03 or DESADV.DELVRY05 when a ASN is created in Supplier system.
    Because when PGI happens i see the IDOC which get triggered is of type DESADV and not DELINF.. My understanding may be wrong.
    I have made the changes suggested by you but my Supplier system is down for sometime now.  
    Is it necessary that both supplier as well customer system should use same type of IDOC ?
    Does ECC 5.0 support DELVRY5.0? I cannt find it in my system but i have DELVRY04 which has the segment for EPC information. But this wont be supported by XI I believe in the integration scenario.
    Thanks and regards,
    Amit Deshpande

  • Need help for configuring integration scenario for AII

    Hi,
    We are referring to "RFID-Enabled Outbound Processing: Configuration Guide" for transferring materials from ECC to AII through XI.
    So far we have been successful sending the IDOC to XI.
    When we display the XML message in XI using IDX5, we get the error message "No receiver could be determined".
    I request you to help us with the configuration of the integration scenario in XI.
    Regards.
    Gaurav

    Hi Yogesh,
    Thanks for reply.
    Maintaining XI Directory configuration
    u2022 Generate business scenario using business scenario configurator
    u2022 Creating a scenario
                      It is fine upto these two steps
    u2022 assigning business systems
                      We have assigned "AII" business system
                      only (receiver)
    u2022 creating communication channels
                       Following parameters are set for comm channel
                        Adapter type: HTTP
                        Configured as Receiver
                        Transport Protocol: HTTP: 1.0
                        Message Protocol: XI payload in HTTP Body
                        Adapter engine: Integration server
                        Addressing type: URL Address
                        Target host: <name of AII system>
                        Service number: <service no>
                        path prefix: /sap/xi/engine?type=entry
    u2022 defining receiver determinations
    u2022 defining interface determinations
    u2022 defining receiver agreements
                       All these were generated automatically
    Are these configurations alright?
    Regards,
    Gaurav

  • AII--- XI--- Mainframe  is the scenario

    Hi experts,
                      Iam having a scenario, in which flow is AII->XI->Mainframe . for integrating Mainframe , we have telnet adapter. which sort of delivery scenario can be used for AII---->XI. and how can we configure it.

    Hi ,
    Please find links below for JMS adapters ,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20use%20the%20content%20conversion%20module%20with%20the%20xi%203%20j2ee%20jms%20adapter
    JMS Adapter
    Thanks ,
    Suvarna

  • Online Meet-up 17.What skills are needed to develop scenarios inside AII ?

    JAVA: to develop, enhance scenarios on the java stack:
    XI, AII
    ABAP: to enhnace idoc, etc on the abap stack (r3, ERP)
    XML: to understand flows in the XI and AII
    Regards,
    michal

    Others are welcome to jump in!
    Thanks and stay tuned to for results next week<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/developerareas/technology">The Technology HomePage</a> for tally and scores

  • AII Flex Del Scenario DESADV.DELVRY03 IDOC

    Hi 
    I am working on IDOC-TO-IDOC scenario in flexible delivery scenario.
    When an ASN is sent from supplier system to customer system via XI the idoc DESADV.DELVRY03 is used to create inbound delivery against the purchase order
    While executing IDOC in target system, the system gave error  with error status 51.
    <b>the error is POSEX field is empty.</b>
    I tried to test execute this IDOC in transaction we19 by filling value of POSEX.
    What should be the value of this field so that IDOC is executed properly?
    Looking forward to pointers to above query.
    Thanks in advance.
    Amit Deshpande

    Hello Amit,
    There are 2 POSEX fields in the DELVRY03 Idoc,
    E1EDL24-POSEX is External item number
    E1EDL41-POSEX is Item Number of the Underlying Purchase Order
    Go to WE60 and put in DELVRY03 and look this up.
    In the IDOC it should show which segment is in error.
    Regards

  • SAP AII (Auto-ID Infrastructure) to  BizTalk RFID  scenario

    Hi Everyone,
    did some one work on this type of project ....
    This project is <b>to develop a connector between SAP AII (Auto-ID Infrastructure) and BizTalk RFID for handling RFID related activities.</b>
    Quick response would be appreaciated.....
    Cheers,
    Raghavesh

    Hi Raghavesh,
    If you want to use a Connector to communicate between Biztalk and SAP AII..you can use .Net connector available.
    The other way is SAP AII uses XI for Communication...so you can use webservices between Biztalk and XI. The below document should be helpful
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7521a237-0701-0010-499b-b3285b789c0d
    Use SOAP adapter for  BIZTALK .
    Use  plainHttp adapter for XI .
    Regards
    Satish

  • Problem in JDBC to JDBC scenario

    Hello all,
    I am working on a JDBC 2 JDBC Scenario.
    Everything gone fine, data is picked from source, but it is not updated in the destination.
    I could not see any message related to this in SXMB_MONI it shows only messages related to IDOC, on search I fould, we need to add trace level,etc in SXMB_ADM but still couldnot found any message (I restarted the system, cleared cache also).
    In RWB(communication channel monitoring) I could find that sender is sucessful, but no message for receiver.
    In RWB (message monitoring) I checked my business system, i could see sender entries but no receiver entries, there is only one error message as :
    <b> transmitting the message to endpoint http://xisystem:50100/sap/xi/engine?type=entry using connectio</b>
    For which I found we need to change XI businesssystem's pipeline port no from some 54+++ to 4+++ (but I could see only 50100 in the pipeline so i did'nt)
    we are using R/3, was7.0 sp11,XI3.0,
    Can any body help me in this regard
    Thanks,
    Sai.k.k

    Hi,
    Error in SXMB_MONI :
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_JDBC2JDBC_MM_: RuntimeException in Message-Mapping transformatio~
    Error in Integration repository when I test with the payload :
    <pre>
    13:01:52 Start of test
    Document start
    Start tag [ns0:Receiver_JDBC_MT]
    Add raw attribute [ xmlns:ns0="http://xyz.com/JDBC2JDBC_NMSP"]
    Start tag [Statement]
    Start tag [dbTable]
    Add attribute: [action]=[INSERT]
    Start tag [table]
    Put value [Example]
    Close tag [table]
    Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)com.sap.aii.utilxi.misc.api.
    BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
    at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException:Fatal
    Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) ->
    com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
    at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
    at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    13:01:52 End of test
    </pre>
    Query : Select * from Employee fetches all the fields
    Payload :
    <pre>   <?xml version="1.0" encoding="utf-8" ?>
    - <resultset>
    - <row>
      <PerNer>t</PerNer>
      <Initials>t</Initials>
      <Name>t</Name>
      <DOB>t</DOB>
      <State>t</State>
      <Country>t</Country>
      </row>
      </resultset>
    </pre>
    Regards,
    Sai.k.k

  • Com.sap.aii.af.ra.ms.api.DuplicateMessageException - Msg Successful

    Hi all,
    We have a scenario where JDBC sender adapter polls - DB2 data base.
    Picks up the records. Updates the records.Messages are sent out.
    Everything is fine. The message is sent to IE and then to the receiver.
    But I see a com.sap.aii.af.ra.ms.api.DuplicateMessageException in the audit log.
    2008-11-21 00:00:26 Error Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException:
    Message ID 56149940-20b1-472f-0905-893a906a65cf(OUTBOUND) already exists in database:
    com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: #XIR1N5J;000000030F.
    2008-11-21 00:00:26 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DuplicateMessageException:
    Message ID 56149940-20b1-472f-0905-893a906a65cf(OUTBOUND) already exists in database:
    com.sap.sql.DuplicateKeyException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: #XIR1N5J;000000030F

    HI
    I think there is some issue with your query. Its either updating the same field or database got some error.
    Check notes 962578 & 831162
    Thanks
    Gaurav

  • Mapping related errors in SOAP Adapter scenario

    Hello Friends
    I have done this several times and in this particular case I am getting some errors.
    Here is the scenario
    External  --- (SOAP) ---  XI  -
    (RFC) -
    SAP TABLE.
    Program
    I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
    I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
    When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
    However, it is failing with some mapping errors.
    Here is the error message I got in SXMB_MONI
    Any help will be greatly appreciated.
      <Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description>Main XML document</SAP:Description>
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>

    Hi Ram,
    This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
    Thanks,
    Bhargav.
    Note:Award Points if found useful

  • File to RFC - error while processing message to remote system:com.sap.aii.

    Hi
    i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      Screen output without connection to user.    
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      Screen output without connection to user.   
    It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
    But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
    could anyone help.

    Hi
    I am Facing  Following Error When I am trying to call SAP Screen through JCO.jar
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
    Please Guide Whethere it is possible to call SAP screen Through JCO.jar  ot NOT
    Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
    Thanks
    Vivek

  • HTTP to File Scenario using URL parameters.

    Hi,
    I am working on a HTTP to file scenario where POST method is hirring the XI server with authentication parameters.
    CAD application is trying to hot our XI server using POST Method and the application does not have ability to send XML payload to XI server directly.
    So we are simply receiving parameters in plain text in inbound payload.
    I need to convert this payload to XML format and am tring to work this out using dynamic configuration.
    But It is throwing parser error.
    BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 73, 75, 62(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:770)
    Here I have to use HTTP sender adapter.
    Please suggest how can I acheive this.??
    Regards,
    Sachi

    Hi Mark and Maciej,
    The Inbpound payload we are reciving is of the kind:
    sap-user=<UserID>&sap-password=<Pwd>&Param1=Sachi&submit=submit
    As in HTML we ar using hidden parameters to given authentication details and submmit button to hit XI serrver.
    Can you please help me to out how can I add prolog and epilog.
    How can I change my payload to XML format.
    Regards,
    Sachi

  • Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550

    Hi Experts,
    We have many File to EDI scenarios wherein XI System pick up the XML and sent to customers via EDI. Recently we faced a problem so created a Back-up System (Production copy) and tested successfully. After sometime the messages were routed to this back-up system and when we notice it and then stopped the back-up system. All the messages that were routed to back-up system, we try to send the same messages from the actually Production system to our customers. Now the problem is XI system (Production system) is unable to pick these files and I check the communication monitoring and encountered the below error message.
    Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550.550
    Can anyone let me know how to fix the issue or what needs to be done?
    Your help is highly appreciated.
    Regards
    Faisal

    Hi,
    It seems to be problem with permission of files. Please ask your basis to do following:
    1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
    2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
    3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
    Regards
    Aashish Sinha

Maybe you are looking for

  • Exporting AutoComplete from Office 2010 issue

    Scenario: New Computer - Running Outlook 2010. Old Computer - Running Outlook 2010. Both using Office 365 AutoComplete I have been made aware is part of the .pst file. I copied over and everything was fine, other than all AutoComplete group entries b

  • Using S_RS_AUTH in VALUE HELP ?

    Hi, thanks for your time. I have problems with the use of the subject to S_RS_AUTH in BI 7. For example, my object is ZCOUNTRY_CL and used 0COUNTRY with the "CL". In the "Value Help" from Visual Composer displays all countries, while in BI7 shows onl

  • Alternative approach to tree business model

    Hi JHS Team, When generating tree-forms with JHeadstart, we need two VO instances in the model for each node we want to present: one for rendering the Tree and another to show on the form, after the user selects a node. I understand that this is nece

  • Form Based Role Validation

    I am trying to use the form based security role validation. I am using JDeveloper's built in OC4J. I am getting to my login form but when I try to submit I get the following: java.lang.IllegalArgumentException: Resource /j_security_check?j_username=m

  • Cabinet file error while trying to instal itunes 9 on vista

    So I have been trying multiple times and doing a variety of things to try and install itunes 9 on vista. While it is copying new files I always get the same error at the same place. The error reads, "The cabinet file 'AppleMobileDeviceSupport.cab' re