Adapter type for inbound xml message XI3.0 SP10

Hi,
We are using XI3.0 SP10 and are about to set up a scenario where we will receive an xml to process. Up until now we have only received simple flatfiles  to process.
My question is, can I use adapter type "File" to process this inbound xml file? And are there any special considerations I should be aware of, that is different from processing an textfile?
At the moment I have started to set it up as follows:
Adapter Type: File
Transport Protocol: FTP
Message Protocol: File Content Conversion
Adapter Engine: Integration Server
Transfer Mode: Binary
File type: Binary
Thanks,
Fredrik

Hello,
Yes you can but you don't need "File Content Conversion".
Choose "File" and well done.
Regards,
Chris

Similar Messages

  • What is inbound XML message type and idoc type in Purchase Order response

    Hi ,
    We are on SRM 7 ECS , support pack SAPKIBKV08.
    We have a process in which vendor will send a Purchase Order response  which will be
    converted to XML format by a middleware. This XML message will come to
    SRM and post a POR. I want to do the EDI mapping for this XML message,
    but there is no message type and idoc type in SRM for Purchase Order
    response. How do I map my message type in SRM to the vendor sent fields
    in middleware .
    Please advise
    Rgds
    Sumendra

    Hi,
    You can process with XML without IDoc.
    Vendor->  (XML) -> PI -> (XML) -> SRM.
    Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
    http://esworkplace.sap.com
    Regards,
    Masa

  • What is the logical message type for Inbound Credit Memo (MM)

    Hi Folks,
    What is the logical message type for Inbound Credit Memo (MM)
    Plz explain.
    Thanks,
    Matt

    Hi Mat,
      The logical message types are as follows.
      /DSD/HH_CREDITDATA             DSD Credit Exposure and Credit lLmit
      CREADV                         Credit memo display
      CRESTA                         Copy credit status (DebtorCreditAccount)
      SBINV                          Credit memo procedure with invoice creation
      SBWAP                          SD Credit Memo Procedure with Automatic Postin
    You can search for message types in database table EDMSG.
    Regards,
    Vimal.

  • Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

    What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
    I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
    In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
    My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
    Thanks,
    Veeru.

    Hi,
    IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
    If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
    Msg: INVOIC
    Basic type: INVOIC02
    FM: IDOC_INPUT_INVOIC_FI
    Process code: INVF
    Thanks,
    Kumar

  • Getting different namespace in inbound XML message consumed by BPEL after translated from EDI to XML in B2B using Inbound Agreement

    Hello B2B Gurus,
    I am able to process B2B inbound  files successfully from Trading Partner --> B2B --> BPEL. When it comes to BPEL i am not able to parse/transform the received XML as i am getting selection failures in assign and empty nodes in transformation. When i look at the input XML payload which i received in ReceiveB2BConsume Payload i observed that i am getting namespace as " xmlns="NS_495C37A0921C418BB66A86A6E75B2CA120070312140549" instead of actual namespace xmlns="urn:oracle:b2b:X12/V4010/856" which is in my XSD as well and i am getting the XML start tag <?xml version="1.0" encoding="UTF-8" ?> 2 times. :
    <?xml version="1.0" encoding="UTF-8" ?>
      <?xml version="1.0" encoding="UTF-8" ?>
    <Transaction-856  xmlns="NS_495C37A0921C418BB66A86A6E75B2CA120070312140549" mlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="1.0" Standard="X12" Version="V4010" CreatedDate="2013-08-21T16:33:57" CreatedBy="XEngine_2956" GUID="{00C28978-0AA1-11E3-88B9-80C16E7DC6DA}">
    <Internal-Properties>
    </Transaction-856>
    I went back and checked the XSD which i loaded in the B2B Console and i am having the following namespace
    "<xsd:schema xmlns="urn:oracle:b2b:X12/V4010/856" targetNamespace="urn:oracle:b2b:X12/V4010/856" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">"
    I am not sure why the XML translated from EDI in B2B console has the different namespace and XML start tag 2 times. Can you please help me resolve the issue. Let me know if i am missing anything.
    Thanks in Advance..

    Hi,
    Please set property as b2b.setDynamicNameSpace=false.
    To use EDI ecs and xsd files from Oracle B2B 10g version, set this property to true.
    When using EDI ecs and xsd files in Oracle B2B 11g which were used in Oracle B2B 10g, the XEngine may generate dynamic namespace for the translated xml. For example,
    xmlns="NS_31CA8D0F33324F95A0BF15D85539C27E20060518215520" 
    To turn off dynamic namespace generation for inbound EDI messages, set this property to false.
    Thanks
    Satendra Pare

  • How can I retrieve the inbound XML messages (invoices) by ABAP program?

    Where are the inbound XML messages (invoices) saved in XI box?
    How can I retrieve the inbound XML invoices in XI box by ABAP program?
    Is there any method/BADI/function module to retrieve these XML invoices, so I can output these XML invoices in an ABAP report?
    Thanks in advance for your help!

    Hello Fisher,
    This Webblog will help you.
    /people/alessandro.guarneri/blog/2006/02/14/super-message-monitor-for-sap-xi
    From this blog you will understand the code behind SXMB moni .. which performs the selection from database. You can write a report as well.
    Cheers,
    Himadri

  • Different delivery type for inbound delivery

    Hi,
    Somebody knows if it is possible to assign diferent delivery types for inbound delivery from differents document type of PO?
    for example, delivery type EL for "NB" PO and delivery type "ZEL" for UB (Stock Transp. Order). 
    thanks
    RZ

    Dear,
    Check: Different inbound delivery types from PO conf control keys
    Regards,
    Syed Hussain.

  • Adapter Type For R/3 Receiver

    Hi All,
    I have created a Communication Channel that represents the communication between a Thrid Party System and R/3, where R/3 is receiver.
    Now the parameters I had entered initially for the Commnication Channel were:
    Adapter Type : RFC
    Transport Protocol : RFC
    Message Protocol : RFC (XML)
    Adapter Engine : Central Adapter Engine
    Then I had entered the Target Details As:
    RFC Server Type : SAP System
    & Below I had mentioned the application server, the system number, authentication mode, and login details.
    Now the client has requested me to remove all the hard coding (i.e. all the application server id, system number and login details) and instead use an RFC Destination, so that the interfaces will have no dependency and maintenance would be low, while the configuration is being transported from the development right upto production.
    Now can anyone help me as to which Adapter Type am I to select for this, or how to go about it, so that I can enter the RFC Destination instead of entering system details. I guess it is possible if you select the Adapter Type as IDOC but I cannot select IDOC, for the simple reason, the receiver system is non SAP and is not sending the data in form of an IDOC.
    Kindly Advise...
    Thanks & Regards
    Pablo
    Edited by: Pablo Ghosh Roy on Dec 29, 2008 7:16 AM

    Hi There,
    Thanks for pointing out the mistake, the Receiver is Definitely the R/3 System and the Sender is Non SAP Third Party System.
    So as per your suggestion, if I set the Adapter Type to be XI, then what kind of RFC Connection would have to be created in SM59, can it be of the type ABAP Connection(SM59), or anything specific.
    Kindly Advise...
    Thanks & Regards
    Pablo

  • Proper Data type for transferring XML from ABAP to XI

    Dear Colleagues,
    I have a question on how to wrap XML data, that itself contains an encoding
    declaration, so that it will be properly transferred to XI.
    XML Generation: "always use X"
    I have searched a lot on SDN and other resources but could not find
    information, describing how a web service should wrap unicode-data when
    making it available to XI. The XML processing group emphasizes that all generation of XML should be done using X-bases (HEX) datatypes in ABAP and preferably using UTF-8 as ancoding. This by itself is not a problem.
    But transferring UTF-8-XML - through which interface?
    When a webservice provides an XML Stream and wants to transfer it to XI then there is a bit of a paradox situation, because it has to choose between using an X-based or Character-based type for its interface
    -> as Binary data?
    - when using X-based data types in the interface, I have control of the character encoding, but I expect that the XML-information will probably be wrapped in base64 encoding and then the XI will receive a base64 encoded
    XML-block instead of "plain" XML.
    I did not find any reference information on how the soap interface of XI and the WAS behave when transferring X-based data, however.
    -> as Character data?
    - on the other hand when using Character-based data types (e.g. String), I have no control of the codepage being used. I have then only the choice to generate the default encoding of the application server. Maybe this encoding
    will be transformed later to a different encoding, but usually during this process the header, which declares the encoding in use will not be adapted as well.
    So if I have a unicode machine, it will generate UTF-16 - based XML. I have no other choice, if I use a character-based type for output. And this will also be stated in the header of the XML stream. If the XML stream
    leaves the system it will probably be transformed to UTF-8, but the XML-header will still state the content to be UTF-16, because the header will probably not be auto-converted together while adapting the Character
    encoding.
    Because of these issues I am quite insecure, on how to generate and wrap UTF-8 - based XML, so that I can properly hand it over to XI, ensuring that
    it stays UTF-8 and that XI can really unwrap it automatically.
    Does anyone have a tip in which type to wrap XML-based data on the ABAP stack so it will be usable in XI?
    Thank you very much for your attention and time.
    Yours
    Christian Steinert

    Something like this should work (with a little tweek I imagine)
    This would be in the 'Command on Target':
    OdiFtpGet "-HOST=<%=odiRef.getInfo("SRC_DSERV_NAME")%>" "-USER= '<%=odiRef.getInfo("SRC_USER_NAME")%>'" "-PASSWORD= <%=odiRef.getInfo("SRC_PASS")%>" "-REMOTE_DIR=<%=odiRef.getInfo("SRC_SCHEMA")%>" "-REMOTE_FILE=<%=odiRef.getTable("L", "COLL_NAME", "W")%>" "-PASSIVE_MODE=YES"
    Set the Technology of the 'Command on Source' as File, and the technology of the 'Command on Target' as ODI Tools
    Edited by: Bos on Jun 30, 2011 11:53 AM

  • EDI Seperator Adapter Issue for Inbound EANCOM Scenario

    Hi Experts,
    Am using latest service pack and SP12 and patch 5 it seems.
    Still am getting same error.
    Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'fbesfd4b25331eabe67a1d04ec4acf': Catching exception calling messaging system
    I configured simple scenario.
    I have set up the 2 ID flows :
    - Partner 1 (Sender File) > (Partner 2) Receiver EDISeprator (didnt used any conversion modules)
    - Partner 3 (Sender EDISeparator with Edifact Module) > to SOAP sending B2B XML to another PI system.
    Done B2B **** Pit file Association.
    Tested in B2B COckpit and it is working fine but working in E2E
    Also note that this is not a Custom EDI. This is just Order D93A Standard message file containing multiple Orders in same file.
    Also let me know one thing Is it required to make KEY Associations for standard EDIFACT Structure Secnario as well?
    I understand from the above error that is able to lookUP the 2nd flow EDI Sender Channel ID but it is unable to deliver/despatch the message content to that flow.
    KINDLY HELP ME>

    Hi Dimitri,
    As per your advice raised another...
    http://scn.sap.com/thread/3597980
    Kindly help me
    Regards
    Amarsrinivas Eli

  • Sequenced Sending of Inbound XML Messages

    We are using ABAP proxies which communicate through XML messages. The current problem that we are facing is that from one INVRPT EDI message, it has to be transformed to two different messages and be sent to the same receiver. The main obstacle is that the first type of message should be processed first before the second type should be sent. If the second message is received by the receiving SAP system, that message will be invalidated and raise an issue at the receiver side.
    The current solution we are looking at is for the receiving SAP system to send an acknowledgment message however, as I looked through BPM, it is only capable of having one sending step (we need to send two messages from one outbound message however at different time intervals).
    Any idea on how to circumvent the problem? Your help will be greatly appreciated.
    Many Thanks and Best Regards,
    Rommel Mendoza
    SAP XI Consultant
    HP GDAS GDPC

    Hi Udo,
    Basically, a customer sends an EDI ORDERS file via AS2. When XI receives the message, it will transform the message to 2 XML messages, one is for order promotion while the second is the actual order XML. The order promotion XML should be sent first to SAP SNC (Supply Network Collaboration) for it to be processed there. Now, once the promotion is in place in SNC, that is the only time the order XML should be sent. If the order XML comes first before the promotion, the message will be invalidated and SNC will raise an error. We are using XI Adapters and the ABAP proxies are SAP predevelivered content for XI (so that we don't need to configure or recreate the XML structures in XI).

  • No show message in monitor for processed XML messages

    Hi,
    I get the document 'VALIDANTING A CONNECTION BETWEEN SAP R/3 AND SAP XI WITH RFC' and following the steps until step 9 it's ok but I can execute the step 10 I get 2 problem:
    First Problem - I dont know where see the ABAP code STFC_CONNECTION, How do you know?
    The Second Problem is the step 11 the system not show message and the documentation show message.
    Please Help-me.
    Any Ideas ?
    Regards.
    Mattos.

    Hi, Ashish thanks for anwser my doubt.
    So, the step 10 is "10. Refer to the following ABAP code snippet for executing the STFC_CONNECTION programmatically
    instead of using the user interface shown above.
    Call STFC_CONNECTION to send/receive request/response to/from XI***
    DATA: v_msg_text(80) TYPE C. "Message text
    CLEAR v_msg_text.
    CALL FUNCTION 'STFC_CONNECTION'
    DESTINATION 'XI'
    EXPORTING
    requtext = 'REQUEST_TEXT'
    EXCEPTIONS
    communication_failure = 1 MESSAGE v_msg_text
    system_failure = 2 MESSAGE v_msg_text.
    IF SY-SUBRC NE 0.
    **Write your code here**
    ELSE.
    **Write your code here**
    ENDIF."
    and the setep eleven is "11. Check the Integration Engine monitor for the processed XML messages (SXMB_MONI):
    Shows Sender Interface:"
    But I not see messege in my Monitor.
    Other doubt in step 5 the document order to create the RFC_Sender Communication Channel, this configuration have the parameters PROGRAM ID (mandatory), we dont have any idea what input there, Can you Help-me? How can find this parameters? in document we have the exemple INTEGRATION_SERVER.
    Thanks.
    Regards,
    Mattos.

  • Exchange rate type for version - error message GP541 during confirmation

    Hi FICO Experts,
    I bumped into a problem during confirmation in CO15. (I would like to get the SFG by mvt 101 and consume the raw material by 261).
    The error messase I get is:
    Maintain the exchange rate type for version 000 in 2009
    Message no. GP541
    Diagnosis
    You want to use plan version 000 with controlling area 1000 in fiscal year 2009.
    You have not specified an exchange rate type for this plan version for fiscal year 2009. Since the update of all currencies in 2009 is active in the control indicators of the controlling area, currency conversions are possible and sometimes also needed.
    It is therefore necessary to specify an exchange rate type for plan version 000 in year 2009.
    System Response
    The system will not accept your entry.
    Procedure
    1. Please maintain plan version 000 first using the function 'Change Plan Version', or
    2. correct your typing error.
    I'd like to ask you to please help to resolve this issue.
    Thanks,
    Csaba

    go to Maintain Version at SPRO-Controlling-General Controlling-Organization->Maintan Version and do what ever it says. Provide Exchange rate type P or M would resolve your issue

  • WMTA - Output type for Inbound Deliveries

    I am looking at the output control requirement in WMTA for Inbound Deliveries by considering vendor address
    Scenario:
    Domestic Vendors : Trigger WMTA (ie send immediately) as soon as Inbound Delivery
    is created
    and
    International Vendors: Same Output Type WMTA but  (ie send with application own transaction)
    ie at the time of putaway they change to send immediately and that  creates TO.
    Is this scenario possible with one outtype (WMTA) ie create TO immediately for domestic deliveries and not for International deliveries ie trigger wmta by going to change mode in inbound delivery.
    Please advice
    Thank You
    Thirumal Reddy

    Hello rao,
    Right now they dont have any diffrences between vendors and they manually decid e them.
    Is it possible to create two confirmational control keys ie 0001 and 0004 for domestic and international vendors in creating inbound deliveries.
    and attached them in conditional table and acess seq.
    please advice.
    Thank you
    Thirumal.

  • Split an inbound xml message in to multiple o/b idocs

    HI,
    We have a requirement to split an XML message(Source) into multiple idocs with different order nos and respective item details. We are working on XI 3.0 and we have a restriction not to use the BPM. Could you please let me know whether its possible to do 1:n mapping in XI 3.0 and how can we do this ?
    Thanks,
    Hari

    Then how you can do that in PI,we should know how many Target IDocs required,then we can import it in to PI.
    if you want to genarate same IDoc multiple times then we can do this,like change IDoc occurace to 0 to Unbounded then import as a external def and use it in mapping,logic you have to write in mapping.
    Regards,
    Raj

Maybe you are looking for