XML to IDoc scenario

Hi all,
for a customer I'm building an xml to IDoc scenario. The xml-file looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
<ROOT>
  <ROW>
    <_5731 />
    <_5735 />
    <EMPLOYEE_SALARYNR>test</EMPLOYEE_SALARYNR>
  </ROW>
</ROOT>
The message type I created in the message mapping looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ROOT xmlns:ns0="http://wartsila.com/i-protect">
   <ROW>
    <_5731 />
    <_5735 />
    <EMPLOYEE_SALARYNR>test</EMPLOYEE_SALARYNR>
  </ROW>
</ROOT>
My problem is I'm not able to translate the customer xml-file in my message mapping, unless I add the namespace "xmlns:ns0="http://wartsila.com/i-protect"" to the file. I tried to solve the problem by deleting the namespace declaration in the message mapping. After that I receive an error when I import the changed structure into the message mapping.
Is anyone familiair with this problem? Is there someway to add a namespace to the sourcefile or to change the message mapping such a way that it corresponds to the source file?
Thanks in advance!
Regards,
Ivo van Ee

My problem is I'm not able to translate the customer xml-file in my message mapping, unless I
add the namespace "xmlns:ns0="http://wartsila.com/i-protect"" to the file. I tried to solve the problem by
deleting the namespace declaration in the message mapping. After that I receive an error when I import
the changed structure into the message mapping.
Since you have created a Message Type corresponding to the sender structure you have the option of deleting the namespace from the Message Type itself.....it is not to be deleted from the message mapping as you mentioned above.....changes made to the MT may cause an initial inconsistency in the mapping......but once done it will be fixed :)...just refer the blog given by Aamir...
Regards,
Abhishek.

Similar Messages

  • XML to IDOC scenario in SAP PI 7.31

    HI Team,
      I am new to Sap PI. I have one scenario xml to idoc in sap pi. Can anyone please help me step by step for this scenario.
    Thanks in Adnavce
    Kallu

    There are ample examples on the internet. Search by giving your exact requirement.
    Try this and see if it helps.
    XI/PI: Simple IDoc Communication using SAP XI

  • File to idoc scenario (split message)

    hello everybody
    i have a file (xml) -> XI -> Idoc scenario
    sometimes idoc message is so much big and i have problem to process it.
    so i would like split message in more idoc but i need decide a cut-point
    example in file i have 200 row and i don't want create 200 idocs but example 4.
    So i need cut file every 50 rows.
    It's possible?
    thanks
    Alex

    Hi Alessandro ,
    We had the same problem in HR implementation where we used to get data for thousands of employees in a single file.
    As Idoc was not able to hold this much of data,data used to be truncated.
    Then we had taken a field (employee number) as a criteria to generate IDocs,and now we have an IDoc generated for each employee record.
    This was helpful as for a single employee,there were a number of change records.
    The logic used was:
    Employeecode -> splitByValue(value changed) -> collapseContexts -> IDoc.
    Does it suit your requirement as well?I mean,may be you can find such field for splitting IDocs.
    Kindly let us know.
    Thanks.
    Regards,
    Shweta

  • Multimapping n:1 (XML to IDOC) Issue - Cannot use map in the scenario

    Hi! I have created a multimapping in the directory. Source message is 0...unbounded and destination message is 1. The intention is to bring a single file into XI that contains mutliple XML messages. I then need to map this into a single IDOC. I have the mapping working. However, when I try and bring this into my integration scenario, XI cannot find the message interface.
    I am not 100% convinced that this will all hang together =) But Cannot even prove that 'cos I cannot set this up in the scenario.
    Any ideas would be greatly appreciate and rewarded.
    Thx
    Duncan

    Apologies for getting all my terminology screwed up. Here is what I have:
    <u>Integration Repository</u>
    Imported Objects - Target IDOC
    Interface Objects : External Definitions - XML schema of source message
    Interface Objects : Message Interface - For source XML; Outbound + Asynch
    Message Objects : Message Mapping - XML (0..unbounded) to IDOC (1) map
    Message Objects : Interface Mapping - XML message interface (0..unbounded) -> XML to IDOC mapping -> IDOC (1)
    <u>Integration Directory</u>
    Interface Determination...
    I select Type of Interface Determination = Extended but when I pull down the dropdown I do not see the multimap.
    I have this working OK for one IDOC to multiple XML messages, doing the same as above. I have checked SCV, namespace etc... and they are correct. I am sure I am missing something very simple.
    Again, any ideas appreciated.
    Thx
    Duncan

  • ALE IDOC to XML IDOC scenario using XML port

    Hi,
    I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
    Can anybody help me on the steps.
    Regards
    Kumar
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

    U can give a try as follows.
    In the Partner Profile of Sender R/3 system,
    Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
    In XI, Party Definition of P_Party
    Give the following Alternative Identifier
    Agency  -   Sender R/3  Business System       
    Scheme -   ALE#GP
    Value    -    P_Party

  • Error in File to IDOC Scenario

    Hi,
    I have File to IDOC scenario.
    I am getting error in sender file channel.
    "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
    Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
    Despite of this error in sender channel I am receiving the message in XI.
    But in XI also it throws error :
    "Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
    Any help on this ?
    Thanks,
    Vikas

    Hello Vikas,
    I am getting error in sender file channel.
    "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
    Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
    Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e.  keyFieldValue.
    "Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
    regarding the above error refer this
    https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
    Regards,
    Prasanna

  • Xml of IDOC in R/3

    Scenario is IDOC to File. My ABAP team given some ref Idoc numbers which are there in R/3 system for test data.They are not posting Idoc from R/3 system to XI.They are asking me to take the data from R/3 system and post it thru XI RWB.
    So,how can I get xml (of Idoc) from R/3 system.so that i can the xml(of idoc) from RWB.

    Hi Naresh,
    Hasnt ALE configuration been done?
    I think you cant download XML if you have IDoc numbers.
    If ALE Configuration has not been done. Do the same. Wont take more than 10-15 minutes to do.
    Then using WE19 you can send the idocs.
    Regards,
    Sumit

  • Sender Namespace and Sender Interface in the IDOC to IDOC scenario

    My question maybe very basic...
    It is SAP IDOC to SAP IDOC scenario.
    Lets assume that I have done config in XI for:
                 Sender  = A,
                 Interface = B,
                 Namespace = C.
    My question is:
    Is there a place in the source system or somewhere to point that
    when an IDOC e.g. DEBMAS is triggered in the source system,
    then the Interface should be B and  Namespace should be C in the xml file ?
    Cheers
    Agnie

    Hi Agnieszka,
         Check these threads/blogs from you may get some help:
    /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    Idoc-to-idoc scenario
    IDoc to IDoc scenario  necessary configuration steps
    For A-Z help on IDOC, you can refer Michal's book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
    Regards,
    Subhasha Ranjan

  • Regarding RFC connection in File to IDOC Scenario

    Hi everyone,
               I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. <i>But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. </i><b>Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario</b>
         <b>!!! Note:  RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!</b>
    Regards,
    Varun Reddy.K

    Hi Varun
    Follow these steps
    First - Maintain the Sender R/3 System:
    SM59 : Create a RFC destination to XI
    WE21 : Create a TRFC Port ->Specify the RFC Destination Created
    BD54 : Create a Logical System for the Idoc Receiver
    WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
    Second - Log on to XI System:
    SM59 : RFC Destination for Sender System
    IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
    IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
    Regards,
    Santosh

  • IDocs not created in file to IDoc scenario

    Hi all
    I am trying this file to IDoc scenario.
    File picked up successfully and sent to R/3 Backend…But Idoc is not posted…the status records
    In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
    I created/tested all basics like RFC dest, port etc.
    File service that I am using is a business service …hence I am specifying a Logical system name in
    <b>Adapter specific Identifiers</b> of the file service.
    I disabled EDI_DC40 control tag record as IDoc adapter
    takes care of it.
    So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
    But SXMB monitor gave an error regarding this control record tag…I guess as we have disabled it so there won’t be any values
    for control record in payload (correct me if I am wrong).
    So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
    But in the backend I am getting this error regarding partner profile.
    I also tried to use an existing profile (<b>LS</b> type) by modifying it’s inbound parameters to accept <b>CREMAS</b> Idoc.
    But the error is as persistent as me
    Pls help
    Sudhir

    Hi
    Sender --> LEGACY, maintained in SLD (Logical system).
    Receiver--> ENI maintained in SLD with logical sys name M700.
    Partner Profile LEGACY maintained in R3.
    <b>Following is the IDocOutbound in SXMB monitor in XI</b>.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>100</SAP:MANDT>
      <SAP:DOCREL>640</SAP:DOCREL>
      <SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>CREMAS</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
      <SAP:SNDPRN>LEGACY</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPENI</SAP:RCVPOR>
      <SAP:RCVPRN>M700</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS />
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
      </SAP:IDocOutbound>
    <b>Control record of IDoc in R3</b>
    Tab: Typeinfo
         Basic type-->CREMAS03
         Message Type-->CREMAS
    Tab: Partner
         Recipient
          Port  -->SAPENI
          Partner Number--> M700
          Partner Type-->LS
         Sender
          Port  -->SAPAXI
          Partner Number--> LEGACY
          Partner Type-->LS
    Pls help
    Regards
    Sudhir

  • Receive acknowledgement in file-to-idoc scenario

    Hello!
    I'm using guide "How to handle acknowledgement for IDOC", and for the first time I want to see an acknowledgement status in sxmb_moni.
    I have passed all steps:
    In CRM I have logical system P1DFILE, this is the system that sends an idoc to CRM.
    Also, I have logical system C2DCLNT100 - this is CRM system.
    First, I go to BD64, create new model view XI_CRM. Then, add message type:
    Sender system - C2DCLNT100
    Receiver system - P1DFILE
    Message type - ALEAUD.
    Then I create RFC destination P1D_001 to my PI server.
    Then I create port SAPP1D using WE21
    Then I go to WE20, choose my Logical System - P1DFILE. I already have the inbound message types (CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M). I add new outbound message - ALEAUD with receiver port SAPP1D.
    Then I go to RBDSTATE, create variant SAP_AUDIT_SEND and enter:
    Confirmation to system: P1DFILE
    Message type: CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M
    Then, in SM36 I shedule SAP_AUDIT_SEND as a hourly job (does this mean, that I will receive confirmations only every hour?)
    So, what should I do to see ack in sxmb_moni?

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • Problem in File to IDOC Scenario

    Hi,
    I am trying to test the demo example for Flight Booking using the "File Sender to IDoc" Scenario. I have done all the settings. As a last step after I copy the file in
    [XI-hostname]\sapmnt\trans\tmp\fileadapter\group[XX] as per the Demo example guide and activate the changes for File_Sender communication channel, no action is triggered.
    The file remains in the directory. When I want to see if my adapter is fine and I check the Adapter Lists in the Adapter Monitoring, it shows only JPR Adapter and that too in RED.
    Then I check the tracefiles and find this error.
    Date : 04/05/2006
    Time : 16:44:52:264
    Category : /Applications/ExchangeInfrastructure/Directory
    Message ID : 00B0D03E9B4F005A0000000D000001F4000410AB0985C603
    Severity : Error
    Location : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler
    Source Name : /Applications/ExchangeInfrastructure/Directory
    Thread : SAPEngine_Application_Thread[impl:3]_3
    Message : Failure at Cache-Refresh data consumption !!!
    <?xml version="1.0" encoding="UTF-8"?>
    <CacheRefreshError>
      <EngineType>AE</EngineType>
      <EngineName>af.aba.singdemo1</EngineName>
      <RefreshMode>C</RefreshMode>
      <Channel>
        <PartyName></PartyName>
        <ServiceName>XI_LEGACY_BS_00</ServiceName>
        <ChannelName>File_Sender</ChannelName>
        <ChannelObjectId>838401f3335236bbadd7086c6711b070</ChannelObjectId>
        <ChannelError>
          <Message>
            Could not parse Channel 'File_Sender'(ObjectId: 838401f3335236bbadd7086c6711b070) AdapterType: File|http://sap.com/xi/XI/System|3b787a8035c111d6bbe0efe50a1145a5:
          </Message>
          <Trace>
            com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.
         at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)
         at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)
         at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)
         at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
         at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)
         at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)
         at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)
         at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
           </Trace>
        </ChannelError>
      </Channel>
    </CacheRefreshError>
    Datasource : 48696150:E:\usr\sap\ABA\DVEBMGS04\j2ee\cluster\server0\log\applications.log
    Application : sap.com/com.sap.xi.directory
    Argument Objs :
    Arguments :
    Dsr Component : singdemo1_ABA_48696150
    Dsr Transaction : 72d10590c48011da8a7100b0d03e9b4f
    Dsr User : Guest
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler
    Resource Bundlename :
    Session : 3816
    Source : /Applications/ExchangeInfrastructure/Directory
    ThreadObject : SAPEngine_Application_Thread[impl:3]_3
    Transaction : SAP J2EE Engine JTA Transaction : [2ffffffe7b5600a31]
    User : XIAFUSER
    Any help will be great.
    Regards,
    Shubham

    Hi Manish,
    I updated the same and now when I activate the changes in my File_Sender communication channel its still not working.
    I checked the Message Monitoring and the message fails to get delivered.
    Here is the Message Audit Log.
    2006-04-11 13:21:51 Success Channel File_Sender: Send binary file "
    singdemo1\sapmnt\trans\tmp\fileadapter\group00\Booking00.xml". Size 526 with QoS EO
    2006-04-11 13:21:54 Success Application attempting to send an XI message asynchronously using connection AFW.
    2006-04-11 13:21:55 Success Trying to put the message into the send queue.
    2006-04-11 13:21:56 Success Message successfully put into the queue.
    2006-04-11 13:21:56 Success The application sent the message asynchronously using connection AFW. Returning to application.
    2006-04-11 13:21:56 Success Confirmation mode test found. File will be resent next time
    2006-04-11 13:21:56 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:21:57 Success The message status set to DLNG.
    2006-04-11 13:23:01 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:23:03 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:28:01 GMT+08:00 2006.
    2006-04-11 13:23:06 Success The message status set to WAIT.
    2006-04-11 13:28:02 Success Retrying to send message. Retry: 1
    2006-04-11 13:28:02 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:28:02 Success The message status set to DLNG.
    2006-04-11 13:29:04 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:29:04 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:34:04 GMT+08:00 2006.
    2006-04-11 13:29:04 Success The message status set to WAIT.
    2006-04-11 13:34:12 Success Retrying to send message. Retry: 2
    2006-04-11 13:34:12 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:34:12 Success The message status set to DLNG.
    2006-04-11 13:35:15 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:35:15 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:40:15 GMT+08:00 2006.
    2006-04-11 13:35:15 Success The message status set to WAIT.
    2006-04-11 13:40:15 Success Retrying to send message. Retry: 3
    2006-04-11 13:40:15 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:40:15 Success The message status set to DLNG.
    2006-04-11 13:41:17 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:41:17 Error The message status set to NDLV.
    What can be the problems?
    Regards,
    Shubham

  • System Level Acknowledgement in File to IDOC Scenario

    Hi All,
    I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI  should send a acknowlement file back to the sender system.
    Could someone suggest how to design this scenario?
    Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • Doubt in file 2 idoc scenario

    hi,
    I am trying to execute to file 2 idoc scenario.
    I created DT,MT for XML file outbound system.
    After importing idoc
    how can i create DT, MT for idoc to connect oubound DT,MT (file side)?
    I am following this wiki guide
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

    hi Raj,
    It means in Idoc, for each field Mesage type, data type are defined, no need to create to once again here in XI.
    plz if i understood wrongly means correct me.
    ONE MORE THING
    i imported cremas04 idoc,
    in that EDI_DC40 contains control record
    E1LFA1M contain data record
    is it correct?

  • Error in File-PI-Idoc scenario

    Dear All,
    While working on File-PI-Idoc scenario, I am getting the error as
    <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have checked various other posts on the same error but still I am not able to resolve this.
    Please help me in resolving this error.
    reg,
    nj

    Nishu,
    Please check whether you have assigned the following roles to the particular user you are using for data communication.
    Roles:
    SAP_XI_IS_SERV_USER,
    SAP_XI_APPL_SERV_USER
    Regards,
    Sugata

Maybe you are looking for

  • Cant send Email when using WIFI

    My primary internet connection is my G4 and a 24.4K dial up. I bought a Dual USB port iBook with 10.4.11 to take to the local library download large files I am sometimes sent. The iBook connects normally on the WIFI, I can browse and work web sites.

  • How to disable a table in oracle?

    Hi, Can anyone tell me if its possible to disable table in oracle> Thanks and Regards

  • Provisioning user from oim to database getting error

    java.lang.NullPointerException at oracle.iam.connectors.icfcommon.protocol.oimjar.OimjarURLConnection.getInputStream(OimjarURLConnection.java:73) at java.net.URL.openStream(URL.java:1010) at org.identityconnectors.framework.impl.api.local.LocalConnec

  • F-58: Restrict the selection of no. of open items

    Is it possible to restrict the number of selected open items (to a max of 10 items at a time) in F-58 transaction?

  • Error while starting DRM webclient

    Hi I have installed DRM and trying to start the web client. The web client does not show up and and error message comes on the page Object reference not set to an instance of an object Description: An unhandled exception occurred during the execution