Comm channels between edi siebel subsystems to sap r/3

hi
how to establish communication channels between siebel EDI SUBSYSTEMS TO SAP R/3 AND SAP BW systems how to integrate SAP system with people soft

Hi,
Go into service marketplace and try to find people soft adapter.
Regards,
wojtek

Similar Messages

  • Replacing EDI subsystem with SAP XI

    Hi Everyone,
    I have a scenario in place where i want to replace the EDI subsystem with SAP XI.
    I know that using Content Master is one of the solution but i have also heard that Content Master is having some license issues. Now after Content Master what is the next best solution for parsing the EDIFACT and X12 format files.
    Thanks and Regards
    Rahul Nawale

    Hi Rahul,
    SAP Conversion Agent by Itemfield is a data conversion system that enables you to create interfaces between any data formats and XML-based systems. The Conversion Agent can convert unstructured, semi-structured, and structured formats to XML, and the other way around.
    Have a look at these links:
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
    These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
    For more i would suggest you to go through these links:
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
    The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
    1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
    2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
    3. create a one to one mapping between input en output.
    4. export the metadata in xsd or sda format for import in XI.
    5. generate an SDA which can be deployed in XI and used as a module.
    Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    There are also a few ways to use EDI with the ALE system of R3.
    inbound EDI to R3
    1.use a 3rd party adapter for the EDI protocol(eg.SEEBURDER) from the EDI system,send the produced XML to the XI ,map the xml message to a matching IDoc using the IDoc adapter.
    outbound ALE message from R3 to EDI system
    1. Configure the ALE system to point to the XI the relevant IDoc (SM59,WE21,WE20...)
    2.use a file adapter3rd party EDI adapter and map the fields to the target structure.
    have a look at this example:
    http://www.ean.se/EANCOM%202000/iftmin/example.htm
    Details on how to configure can be found on SDN
    I hope this helps....
    Regards,
    Abhy

  • Relation between EDI and SAP MM

    Hello Gurus,
    Is there any relation between SAP MM and EDI...?
    Omkar--

    Hello Omkar,
    There is no specific relation between EDI and SAP MM. SAP MM module is for your internal data while Industry EDI is communication media.
    E.g.
    If you create a PO in your system , it is related to your MM part while information with regards to craeted PO is supplied to vendor by EDI _ Electronic data interchange.
    Hope this will help you.
    Amit C kulkarni.

  • Using URL Parameters with HTTP Comms Channel

    Hi,
    I need to build a new interface (HTTP - RFC) which will use several URL parameters. I've created a HTTP communications channel and Sender Service and this works. I'm able to define several URL Parameters by checking 'Adapter-Sepcific Message Attributes' and then 'Apply URL Parameters' then specifying the individual parameters.
    This is straight forward so far but in usual SAP fashion the documentation on HTTP Comms Channels and URL Parameters is non existent. My question is how do I use these parameters once they are passed. I need to use the values as input parameters for the RFC which means I'll need to map these in the Integration Repository I can't find anything on SDN or SAP help that answers the question.
    I know I could include these values in the XML payload but that would mean my 'customer' would need to amend their application and I'd rather keep things as they are.
    Looking forward to your replies.
    Thanks in advance.

    May be this could help you to refference . .
    For each process template, you can define interactive or composite form reference objects that can optionally be executed at runtime.
    To be able to see and execute the reference object at runtime, you must add an appropriate runtime view.
    Prerequisites
    You can only attach standalone interactive forms to a process. For more information, see Interactive Form Types.
    Activities
    To attach an interactive form to a process:
           1.      Open the gallery and select a process template. To open its design time, choose Open…
           2.      To switch to edit mode, choose  (Edit).
           3.      Open the Forms tab page.
           4.      Choose Add and select the type of reference object you want to add. You can choose between Callable Object and Development Object.
    Browse and select the reference object, and choose Add once again.
           5.      Repeat step 4 to add more objects.
           6.      To define parameter mapping, select an entry and choose Map Parameters. Select a parameter from the left-hand table, and then select the parameter you want to map from the right-hand table. This groups the input parameters of the form reference object to the relevant input parameters of the process.
    If the process does not define input parameters, you can set default values.
           7.      When you have defined the required mappings, choose Done.
           8.      Whenever a newer version of the form reference object is available, its status on the Forms tab page changes to  (Deprecated). To update the object, select it from the list and choose Update. The status changes to  (Active).
    Parameter mapping is preserved unless the parameters of the new object version are different. In this case, you need to define mappings again.
           9.      Finally, choose  (Save).

  • Hi gurus what is the difference between EDI & ALE.

    hi gurus what is the difference between EDI & ALE.

    HI,
    EDI is a technique used to communicate business and information transactions between computer systems of different companies and organizations. These transactions include such documents as purchase orders, invoices, inquiries, planning, acknowledgements, pricing, order status, scheduling, test results, shipping and receiving, payments, and financial reporting
    EDI Introduction
    The EDI interface is intended to connect an EDI subsystem with the SAP system. EDI subsystems perform the following tasks related to EDI processing:
    1·Conversion of data·
    2.Message and Interchange Handling.
    3.Communication·
    4.Administration of partner profiles·
    5.Monitoring of processing
    From the SAP side, the EDI interface is based on IDoc technology, which is independent of EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem. Synchronous RFC (Remote Function Call) is implemented to define the time of transfer for a file between the two systems.
    EDI u2013 Benefits
    Improves data accuracy u2013
    With EDI business can eliminate the need to re-enter data from paper documents and thus prevent potential data entry errors. Additionally, the cost of processing an electronic requisition is estimated to be one-tenth the cost of handling its paper equivalent
    Lowers personnel costs-
    EDI can help companies reduce the need for personnel involved in orders and accounting processing. Speeds up information exchange- EDI systems can shorten the lead time between receipt and fulfillment  of orders. When  scheduling information is transmitted with ordering  data, companies can plan production more accurately and thus reduce stock investments.
    Reduces technical complexity related to data interchange u2013
    With EDI companies use standardized data formats to exchange documents. EDI allows companies using different business applications and systems to achieve computer-to-computer electronic exchange of business documents.
    Application Link Enabling
    ALE Objectives u2013 ALE incorporates controlled exchange of data messages ensuring data consistency across loosely coupled applications. ALE comprises of three layers.  Application Services  Distribution Services  Communication Services
    Basic principle of ALE is to provide a distributed and fully integrated R/3 system. Each application is self-sufficient. The use of self-sufficient system implies a certain measure of data redundancy.Hence data has to be both distributed and synchronized.
    General Steps Involved in Configuring EDI u2013 ALE Interface
    - Maintaining the Condition Table
    - Maintaining the Access Sequences
    - Maintaining the Output types
    - Assign output types to the partner functions
    - Maintain output determination procedure
    - Assign output determination Procedures

  • What is Ale, Edi,IDoc tech for sap

    Hi all,
    What is Ale, Edi,IDoc tech for sap?
    Thanks.

    hi deniz,
    <b>ALE</b>
    ALE
    Triggering OB via Change Pointers:
          When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
    Outbound Process:
    When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
    Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
         To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
    Asynchronous Communication:
    The data  that is IDocs and the function module are  stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
    Inbound Process:
    The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
    In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
         Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
    In the table TBD51 there will be entries to find which option is used.
    Transactions:
    SALE - IMG ALE Configuration root
    •     WE20 - Manually maintain partner profiles
    •     BD64 - Maintain customer distribution model
    •     BD71 - Distribute customer distribution model
    •     SM59 - Create RFC Destinations
    •     BDM5 - Consistency check (Transaction scenarios)
    •     BD82 – Generate Partner Profiles
    •     BD61 – Activate Change Pointers - Globally
    •     BD50 – Activate Change Pointer for Msg Type
    •     BD52 – Activate change pointer per change.doc object
    •     BD59 – Allocation object type -> IDOC type
    •     BD56 – Maintain IDOC Segment Filters
    •     BD53 – Reduction of Message Types
    •     BD21 – Select Change Pointer
    •     BD87 – Status Monitor for ALE Messages
    •     SALE – Display ALE Customizing     WEDI - ALE IDoc Administration
    •     WE60 - IDoc documentation
    •     SARA - IDoc archiving (Object type IDOC)
    •     WE47 - IDoc status maintenance
    •     WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    •     WE05 - IDoc overview
    •     BD87 - Inbound IDoc reprocessing
    •     BD88 - Outbound IDoc reprocessing
    •     BDM2 - IDoc Trace
    •     BDM7 - IDoc Audit Analysis
    •     BD21 - Create IDocs from change pointers
    •     SM58 - Schedule RFC Failures
    <b>EDI</b>
    EDI(Electronic Data Interchange )
    RFC DESTINATION:
                           A logical name used to identify the remote system on which a function needs to be executed.
    Partner Profile:
          It defines the characteristics of data being exchanged with the business partner.
    Partner Function:
         Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
    Partner type:
              The type of your business partner .
         EDI        – KU/LI
         ALE     --  LS.
    Archiving:
         -Need to archive the important transmitted document
    -Created in SARA
         -Assigned in WE20.
    PartnerProfile Tips:
    •     RSECHK07- Consistency check for Partner Profile.
    •     If you want to modify partner profile; copy it and then modify. If you can’t modify it , u have  to delete it.
    •     To move partner profile to production system choose Partner ->  Transport
    Port defintion:
         It defines the medium through which data is exchanged between systems.
    •     tRFC    -   Used by ALE
    •     FILe     -   Used by EDI
    •     R/2 system system port  – For R/2 system
    •     Internet port           - to connect with internet applications
    •     It also depends on the  receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
    Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
    Startrfc                                         -   Program to execute RFC – enabled Fun.mod. in SAP
    EDI_DATA_INCOMING             -   To send data as inbound
    EDI_STATUS_INCOMING         -   To send status to SAP
    RSPARAM               -   To know the gateway service of the SAP system.
    Message Control:
    •     Output controller
    •     A service program for determining the output type
    •     To generate and manage various outputs from an application and control their medium and timing of exchange.
    •     To retransmit the document without duplicating it
    Procedure:
    •     A procedure defines a set of possible outputs for an application
    •     There may be more than one procedure but only one can be active
    •     Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
    Output type:
    Defines the characteristics and attributes of the output.
    Access Sequence :
    Defines  a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
    Sapfans Q & A
    SREL_GET_NEXT_RELATIONS   -
    Function Module that will provide me the number of the document that was created by an IDoc
    RLSUB020
    Program which uses the above function module.
    Upgradation problem
    When the old version program is upgraded in to newer version(4.0b &#61664; 4.6c) the SE38 editor won’t allow u get thru’ the programs normally to get rid of this.
    Solution:
    EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
    When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
    this fixes the links
    ALE( Application Link Enabling )
    Disk Mirroring:
    Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disk’s contents.
    Replicas:
    Maintaining redundant data across multiple systems.
    ALE:
      It provides distributed environment to integrate non-SAP systems
      Provides guaranteed delivery of data regardless of network problem to application.
    Logical system :
         The systems involved in distributed environment  are assigned a logical name which uniquely identifies a system in a distributed  environment.
    Data Mapping:
         Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
    Message Types:
    •     Represents a business function
    •     Technical structure is the IDoc type
    •     Or can say an instance of IDoc.
    <b>IDoc  :</b>
         They are containers used to exchange data between any two process.
         It represents an IDoc type and IDoc data
         IDoc type is structure and IDoc data is an instance of it.
    <b>Pls reward if helpful.</b>

  • Hosts file is being cached - comm channel is using an old version

    We are on XI 7.0.
    I wonder if anybody has encountered this problem before. We are using the file adapter to send a file to another server and the server has been moved and now has a new IP address.
    We just changed the IP address in the hosts file and the communication channel is still trying to send the data to the old IP address. No changes have been made to the comm channel (so this is definitely not a cpa cache issue!).
    The (unix aix) OS recognises that the host has been changed - if we ping the hostname from the OS it resolves to the new IP address.
    I have seen this once before and the only way we were able to resolve it was by re-starting the java stack.
    Please let me know whether there is another way we can resolve this issue.
    Thanks
    Richard

    Here is what SAP said:
    The mapping between physical hostname and IP address might be cached
    in the JVM itself using class "InetAddress".
    Besides the jdk 1.4 documentation for InetAddress has relevant
    information to share, maybe you wish to review the same.
    Please refer the info via:
    http://java.sun.com/j2se/1.4.2/docs/api/java/net/InetAddress.html
    To help resolve clearing the Java Cache you need to reset the JDK
    property "sun.net.inetaddr.ttl".
    Detailed information can be sourced via access of link:
    http://www.rgagnon.com/javadetails/java-0445.html
    To overcome such kind of issue, SAP has High Availability for its
    landscape. For instance, two machines share the same Virtual Hostname.
    Under this situation, the switchover can be done smoothly. And JVM
    does not need to be restarted.
    This works fine - we set the time out to 2 days so that the cache refreshes itself periodically.

  • Problem in File Receiver comm channel

    Hi,
    I can't see anything in the Recevier communication channel in the RWB > Component Monitoring>Comm. channel monitoring-->Comm. channels.
    I do have selected my comm channel.Its showing the message as "Comm. channel is configured correctly and started". But I cant see msgID and Explanation or error. Even, I cant fine any info in Error log.
    The diagnosis i did as follows. Let me know if u come across any thing.
    Checked the logs in VA but i didnt found any information and is not upto date. Bad luck
    *Recreated the Rcvr comm channel again and teste. Nohope.
    In the MONI its showing successfull, but i cant see output at destination.
    *cache is uptodate
    I have checked the queues, nothing got stuck.All queues are clear.
    *I cant restart the Server since it is in production.
    Your suggestions are highly appreciated.
    Thanks
    SRI

    Nilesh,
    All the things you mentioned are done by XI IS.  FYI plz chk below..
    Send binary file "/home/dpiadm/xi/tmp/passthru/EDI_250123.rpz", size 60, character encoding 8859_1 with QoS EO
    2007-10-19 13:48:43 Success MP: Entering module processor
    2007-10-19 13:48:43 Success MP: Processing local module localejbs/SFTPFileUploadDownloadAdapterModule
    2007-10-19 13:48:43 Success 192.133.217.6 /XI/SFTPTest pimsp kuljasimsim EDI_250123.rpz   /home/dpiadm/SridharRajuMahali /home/dpiadm/xi/tmp/passthru/ EDI_250123.rpz Enable
    2007-10-19 13:48:43 Success EDI_250123.rpz
    2007-10-19 13:48:43 Success SFTPOutBoundEDIFileToFile
    2007-10-19 13:48:43 Success SFTP_Sender_File
    2007-10-19 13:48:43 Success 8878c990-7e6b-11dc-8137-001a4b065b86
    2007-10-19 13:48:43 Success SFTPServerNameOrIpAddress  192.133.217.6
    2007-10-19 13:48:43 Success Indiashining.txt SFTPOutBoundEDIFileToFile SFTP_Sender_File 8878c990-7e6b-11dc-8137-001a4b065b86 SFTPOutBoundEEIFileToFile
    UNDEFINED
    2007-10-19 13:48:43 Success Host Key Verified
    2007-10-19 13:48:43 Success Socket Opened for Transport and connected..
    2007-10-19 13:48:43 Success SFTP SshClient is connected
    2007-10-19 13:48:43 Success Authentication Method is Public Key
    2007-10-19 13:48:43 Success Ssh2 Client is Connected and Authenticated
    2007-10-19 13:48:43 Success pimsp kuljasimsim
    2007-10-19 13:48:43 Success /XI/SFTPTest
    2007-10-19 13:48:43 Success /XI/SFTPTest
    2007-10-19 13:48:43 Success localFolder2 + dropFileName2  /home/dpiadm/xi/tmp/passthru/EDI_250123.rpz
    Entering to download file
    2007-10-19 13:48:43 Success Current Directory before LCD0 : /home/dpiadm
    2007-10-19 13:48:43 Success Current Directory After LCD0 :/home/dpiadm/xi/tmp/passthru
    2007-10-19 13:48:43 Success download completed
    2007-10-19 13:48:43 Success MP: Processing local module localejbs/CallSapAdapter
    2007-10-19 13:48:43 Success Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
    2007-10-19 13:48:43 Success Trying to put the message into the send queue.
    2007-10-19 13:48:43 Success Message successfully put into the queue.
    2007-10-19 13:48:43 Success The application sent the message asynchronously using connection File_http://sap.com/xi/XI/System. Returning to application.
    2007-10-19 13:48:43 Success MP: Leaving module processor
    The message was successfully retrieved from the send queue.
    2007-10-19 13:48:43 Success Confirmation mode test found. File sent.
    2007-10-19 13:48:43 Success The message status set to DLNG.
    2007-10-19 13:48:44 Success The message was successfully transmitted to endpoint http://quark:8005/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
    2007-10-19 13:48:44 Success The message status set to DLVD.
    2007-10-19 13:48:44 Success The message was successfully delivered.
    Note:- I AM NOT ABLE TO SEE ANYTHING IN THE RCVR COMM CHANNEL(RWB).
    any Idea about, where can I see the message if it got stuck in Integration server apart from logs
    Thanks
    Sri Raj

  • Adapter engine field blank in File Comm channel (Sender)

    Hi,
    I am not getting any value in drop-down list of adapter engine in file adapter communication channel.System is allowing me to save the comm channel but when I am trying to create sender agreement, system is giving me following error
    <b>Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.s01., string], target element type: SAP_XIIntegrationServer)</b>
    I m getting values of adapter engine when I select some other adpter like IDOC or RFC.
    Please help...

    Hi,
    1) Can you check your Post Installation.
    2) Look for SAP NOTES.
    3) Try cache refresh
       a)Start transaction SXI_CACHE.
       b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
    If you still face issue try this .
    Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
    To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
    Regards
    Agasthuri Doss

  • BIC Module Error in Sender Communication channel for EDI to File scenario.

    Hi Experts,
    We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
    Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
    Thanks & Regards,
    Abhishek

    Hi Abhishek,
    Is there any special character present in the EDI file?
    the parser is not able to parse the data.
    you can check the BIC conversion log for more information.
    Regards,
    Harish

  • Sync/Async - JMS receiver comm. channel not processing

    I have a Sync/Async scenario (without bpm) in PI 7.11:
    RFC -> PI -> JMS
    whereby the JMS receiver comm. channel does not fully process the message. 
    More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
    - Message processing started
    The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
    - Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
    - Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6  correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
    - Message processing started
    (but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
    - Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
    Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
    When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
    14.02.2011 12:50:19 Information Transform: transforming the payload ...
    14.02.2011 12:50:19 Information Transform: successfully transformed
    14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
    14.02.2011 12:50:19 Information ROB: forwarding the request message
    14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
    14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
    14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
    14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
    14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
    wheras the non-success msg shows only:
    14.02.2011 12:55:30 Information Transform: transforming the payload ...
    14.02.2011 12:55:30 Information Transform: successfully transformed
    14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
    14.02.2011 12:55:30 Information ROB: forwarding the request message
    14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
    So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
    And also the  sxi_monitor shows these messages with a status of "Log version".
    Keith

    Hi Siddhesh - yes that was a while back and am trying to remember the resolution.  I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver.  I can then compare to mine if you'd like.  Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
    Regards,
    Keith

  • Comm Channel Variable Substitution - Use of wildcards to reference payload

    Hi!
    I am building a solution to write out tagged / XML IDOCs to a file adapter. I am using variable substitution to build the file name to include the message type, sending partner etc... in the target directory and filename.
    Is there a way to wildcard nodes in the variable substitution? For example:
    <i>Currently</i>
    payload:WMMBID01,1,IDOC,1,EDI_DC40,1,RCVPRN,1
    <i>Desired</i>
    payload:*,1,IDOC,1,EDI_DC40,1,RCVPRN,1
    where * is any wildcard.
    Reason is that we have multiple IDOC types and I want to avoid having to create multiple communication channels.
    Help appreciate and rewarded. Many thanks, Duncan.

    Hi Duncan !
    You can create the desired target filename and target directory by using dynamic configuration via java UDF in mapping. This allows you to create a target filename and/or directory based on a string..then you could use only one comm channel.
    to access info:
    // access dynamic configuration
          DynamicConfiguration conf = (DynamicConfiguration) param.get(
              StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey KEY_FILENAME = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","<b>FileName</b>");
          // read value
          String Filename = conf.get(KEY_FILENAME);
    // to write value:
    conf.put(KEY_FILENAME, "MyNewFileName");
    Regards,
    Matias

  • Comm Channel - "requested resource does not exist"

    Good day,
    Can someone help me with this error I get. We have a file to file scenario and everything works fine but the file never gets created on the receiver side, all messages says successful but in the comm channel monitor for the receiver adapter I get "Message processing completed successfully" but if I click on the message ID it say's " The requested resource does not exist." [Screen Print|http://www.photostand.co.za/images/t6432okl1tu6wzubwymj.gif]
    Thanks,
    Jan

    Hi Jan,
    Are you able to process messages from other interfaces? If not then there is an issue with the post installation. Please Check the SAP Note: 817920
    If you are not able to process messages only for this interface then there might be a configuration issue..
    Follow the link provided by the other SDNer. Please check and let us know the results.
    Thanks,

  • File adapter in comm.channel green, but no message collecting

    Hello,
    looks like this is something really at the roots.
    Ok, we are in NW2004s PI 7.0.
    One IDOC process is successfully implemented.
    Now we started with a file to file communication!
    File sender adapter is configured and shown in status green in comm.channel monitoring which would bring me to the idea that the comm.channel is configured well  (To be sure we changed the directory path in the comm.channel to a wrong one which results in an error. Ok, corrected. Now all lamps are green). Comm channel is activated and polling.
    But... nothing happens. The Adapter is not collecting the file in the source directory (existing) and there is no entry in monitoring on RWB or SXMB_MONI.
    In Adapter monitoring all adapters except the JPR (red) are with a GREY lamp!
    As we had an issue with activating the adapters (adapter monitoring before did not show any adapter (except JPR) ) two days ago we are not sure if the current issue belongs to a mistake in the configuration or in basis environment.
    From XI 3.0 side we would expect that the adapter monitoring should show adapters used in green.
    Do you have experience with such a behaviour?
    Any help is welcome!
    regards
    Dirk

    Hi Bhavesh,
    we are near to bumping our heads against the server.
    In comm.channel:
    directory is :      /      (as simple as possible)
    file name is : *.001
    The file in the directory is named it_test.001 so it should be catched.
    What can we do wrong?
    By the way: If we change the directory to  /out   which is existing we have an (file is in this directory too) error message:  'com.sap.aii.adapter.file.ftp.FTPEx: 550 /out: The system cannot find the file specified. '.
    Cache is fine!
    regards
    Dirk

  • FTP - Receiver Comm channel error

    Scenario: Send a file to a 3rd party via FTP adapter
    Error: MONI is OK but comm channel monitor is in error state and error is displayed as:
    An error occurred while connecting to the FTP server 'xxx.xx.xx.xxx:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Permission denied on server.  You are restricted to your account.'. For details, contact your FTP server vendor.
    Things checked:
    1> Our Firewall is configured to send the file from our system to 3rd party.
    2> I could logon to 3rd party FTP server from web browser.
    FYI, 3rd party FTP server is hosted on Yahoo.
    Any ideas, why I am not able to FTP the file to 3rd party system?
    Thanks
    Bhaven

    Bhaven Shah wrote:>
    > 2> I could logon to 3rd party FTP server from web browser.
    It does not mean that XI will be able to access the FTP server.
    You have to grant access for Adapter Engine user which is used for FTP communication.
    Regards,
    Jakub

Maybe you are looking for

  • How do I make phone calls through my computer?

    I have a Lenovo U530 and it is equipped with bluetooth. My phone is an iPhone 5S and I was wondering how to make phone calls through my laptop. Please help!

  • Idoc 2 file - file content conversion in receiver

    Hi, My scenario is idoc to file. if i want to use file content conversion at receiver side, so i need to create record set according to sender side data type or receiver data type? plz give some inputs reg. this. Thanks

  • Can't I use a WRT610N as a bridge or AP?

    Inherited this WRT610N from someone, and want to deploy it in a preexisting LAN (172.21.1.x) with a pre-existing DHCP server. Can I use the "Internet" port if I assign it static IP on my LAN, and create a new DHCP scope (192.168.1.x) for Wireless cli

  • Problem with E-Business Control Center

    Hi, I am trying to create a content selector using the e-business control cnter. When I try to save it I get the following error. The content selector is not complete. Please complete before saving. Could not save the rule. Could not find GlobalConte

  • DHCP scope in WLC.

    hi all, please any one confirm ,is it possible to configure the DHCP scope for APs in WLC ? i am having 5508 controller connected to L3 switch..if it is possible what need to be done for that. thanks in advance. venkat