Scenario Idoc -- JMS (Debmas -- Basis)

Hi everybody.
I have to develop a scenario idoc debmas  --> jms wiht version 7.0.
I´ve never worked with jms and I´d like to know how I have to build the messages. ¿Does any external definition exist to work with customer data with jms or I´ll have to create my own data type, message type and message interface with a determinate structure??
Regards and thanks a lot.

Hi,
In addition to Prateek's reply I would like to add below mentioned point.
Your secnario is IDOC --->JMS but JMS will be sending the data to some third party (legacy system). So try to filnd out what format is needed at legacy side. Once you know the structure required by legacy system then you can create the same data type in XI to deliver the message to JMS.
Regards,
Sarvesh

Similar Messages

  • Party in a scenario IDoc -- XI -- File.?

    Hi folks,
    I have a scenario IDoc <> XI <> File. Some IDOCs are LS, KU and LI type. Do I need a XI party to configure this scenario?
    Thanks in advance,
    Ricardo.

    Thanks for the quick answers
    Remember that I also have File -> XI -> IDoc.
    But, I still don't understand how SAP backend can distinguish the same IDOC for different partner types, ex. ORDERS05 type LS and/or KU. When the IDoc arrives the backend how it knows which type of IDoc is dealing?
    Cheers,
    Ricardo.

  • Can you plz tell m how to write Design Strategy in the scenario IDoc-- File

    Hi,
    can any body plz tell me how to write Design strategy, Preprocessing logic and post processing logic in the scenario IDoc-->File.
        My idoc is:
                Message Type: ZMMIPORDCHG
                Basic Type  : ORDERS05.
    lookup's are available.

    Hi,
    take a look at this document for an IDOC to IDOC Scenario,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    Use it as a template to design one side of the Interface and also take a look at this blog,
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    Regards,
    Bhavesh

  • Scenario IDOC to JDBC

    Hi experts,
    i've scenario IDOC to JDBC:
    the interface receive two idoc's:
    IDOC1: 1field1, 1field2, 1field3
    IDOC2: 2field1, 2field2, 2field3
    and give the data to only one table in the receiver, ie, the table is equally filled by the contents of both idocs,
    the data in this table must be storage by follow:
    field ->       field1        field2        field3
    values ->    1field1      1field2      1field3
                     2field1      2 field2     2 field3
    ¿how can i do this whe i realize the mapping ?
    ¿Is it possible, or it's better to use two interface, one for each idoc?
    very thanks

    If both the idocs are of same basic type, then you may perform Idoc packaging at the sender side. Due to this you could receive idoc at XI with multiple Idoc nodes having data from different idocs. Then you may map directly till node level and achieve the output.
    If the type of idocs are different, use two interfaces or go for BPM to collect.
    Regards,
    Prateek

  • Sample scenarios using JMS Adapters

    Hi Experts,
    Can anyone send me sample step by step scenarios using JMS adapters e.g one scenario using JMS in the sender side and another scenario using JMS in the receiver side.
    Thanks
    Ayan

    Most of the job is to be done in the Channel Adapter module for content conversion.
    There's much more documentation about the File Content Conversion but most of it apply to JMS.
    Can you be more specific in what you're looking for?
    Content Conversion:
    http://help.sap.com/saphelp_nw04/Helpdata/EN/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
    Martin

  • ** File to IDoc scenario - IDoc not created in target system

    Hi friends,
    We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
    We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
    1) SM59 - Connections are OK both application and XI system
    2) IDX1 - In XI System, we have assigned SAP<R/3> port.
    3) IDX2 - IDoc is imported.
    4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
    5) In application system. - Partner Profile maintained correctly.
    6) SM58 - There is no error.
    So, what could be the reason ?
    Kindly reply, friends,
    Thanking you.
    Kind Regards,
    Jeg P.

    Hi,
    Check all the steps ..
    File to IDOC
    Do these configurations in R/3 and in XI...
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Thanks,
    Satya

  • How to serialize the IDoc of DEBMAS by time sequence?

    Hi experts,
    We want to transfer customer master data from one client to the other.
    We have carried out the serialization distribution for message type DEBMAS
    and actived the change point.
    Scenario:
    time 1 : We created one "NEW" customer 100436.
    time 2 : We assigned the Head Office of "existed" customer100435 as 100436
    The time of the distribution job was arrived,
    the job started to run and failed to change "existed" customer 100435
    even though "NEW" customer 100436 has created sucessfully.
    We think the IDoc should be processed by time sequence,
    but it seems not.
    Did you think it is processed by customer key ascendence ?
    How do we define the process sequence of the IDoc?
    Any advice will be appreciated.
    Regards,

    But what if i want to check the format of date that my
    database supports ?
    Actually situation is :
    I am making a form designer by which user will inset
    date to a particular column. okay.
    now the format of date must match with the underlying
    format of database. Then only query will be
    successfull. Is it not so.?No.
    Basically you will be doing the following:
    Browser -> java.util.Date
    java.util.Date -> JDBC -> database
    JDBC does the 'conversion' work for you, you just need to put it in the java.util.Date.
    suppose database table-> column's format is
    YYYY/DD/MM Databases don't store dates like that. They usually (probably always) store it as a signed integer value which is relative to a specific date/time.
    When you use a database tool to look at the value the database tool converts it from the number to a format that looks familar to you.
    and user enters date in the format
    DD/MM/YYYY, then i will have show an error message to
    the user that the format of date that he has entered
    is wrong. No need for that.
    The user does need to put the date in in a form that you understand. So you can convert it to a java.util.Date.
    java.text.SimpleDateFormat can help with that.

  • Request and Response Scenario for JMS adapter

    Hi,
    I am working on IDOC-XI-JMS, JMS(sender)- XI - JMS (receiver)scenario and this is going to be real time. If any record is update in customer master then that record will be sent to JMS provider MQ series and lock the record in the legacy system and then legacy system unlock and send back a message that this has been unlocked.
    This would be request response message, anyone tell me how this can be achived. I think I may have to use BPM for this kind of processing. Can anyone tell me the steps to achive the BPM for such processing.
    Regards
    Please reply back
    Edited by: hema Mehta  on May 23, 2008 2:05 AM

    Hi Hema,
    Reward points if this helps
    Step by Step Porcess of JMS Synchronous Scenario without BPM: Correlation Settings and Transactional JMS Session
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
    How To Correlate JMS Messages
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8060448a-e56e-2910-f588-9af459e7ce21
    Async/Sync Communication using JMS adapter without BPM
    /people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
    STEPS in BPM for synchornous.
    Reward points if this helps
    Regards
    Pragathi.

  • Idoc  - JMS queue using ABAP Mapping

    Hi all,
    I am doing a idoc to JMS queue scenario using ABAP Mapping. I am new to ABAP
    Basically i want to know how to read the OUTBOUND idoc segments and their field values. I have gone through link : IDOC--XI--IDOC Using ABAP MAPPING(Idoc to Idoc using ABAP Mapping).
    If any body could suggest me how to read idoc->segment->fields or give some sample code, it would be very helpful.
    Thanks in advance&
    Regards,
    Mani

    Hi Mani,
    Maybe it would be easier to use graphical mapping. In ABP mapping you have to parse XML and than create target document. If you want to do it I'd strongly advice you to read it:
    http://help.sap.com/saphelp_nw04/helpdata/en/47/b5413acdb62f70e10000000a114084/frameset.htm
    Regards,
    Wojtek

  • Scenario - IDoc - XI - RFC - IDoc

    Hi Experts,
    I am new to BPM.
    We have 2 sap systems...SAP1, SAP2.
    The BPM scenario is,
    When Material changes made in MM02 of SAP1, changepointers creates an IDoc1. IDoc1 is first sent to XI. Now in SAP2, it is to be checked whether that particular changed in SAP1 exists in SAP2 or not. For this, from XI an RFC call is made to SAP2, depending on the return values, the IDoc message that has been reached to XI (from SAP1) is sent to SAP2.
    How to achieve this.
    Any docs, links would help me. I am very new to BPM.
    -Naveen.

    Hi,
    <i>Can any one give me some direction.</i>
    >>>Are you talking about BPM steps ? if so I have given that.
    For Message Interfaces-
    1) Abs, Async, Message Interface of type Idoc
    2) Abs, Sync, Message Interface of type RFC
    3) Abs, Async Message Interface of type Idoc , which is sending to SAP2 system. If you have mapping changes.
    Mapping is outside the BPM, Create a dummy message type for RFC response. To check the response in the BPM
    i.e Idoc to RFC Req Mapping
        RFC Response to Dummy RFC response
    Hope this helps,
    Regards,
    Moorthy

  • Scenario: Idoc - XI - external system (Idoc)

    Hello,
    I am trying to send an idoc from an sap 4.6c system to an external system. The external system is supporting idcos with trfc. This scenario is currently working with ALE. Now i have to set XI between these two systems.
    My problem is to set up the communication channel in the integration builder (configuration) for the external system. The idoc is waitung in XI to transport. So the step XI-> external system causing problems.
    My settings are:
    adapter type: idoc
    transport protocol: idoc
    message protocol: idoc
    adapter engine: integration engine
    rfc destination: xyz (is working fine)
    interface version: sap release 4.0 or higher
    port: ??
    sap release 46c
    My problem is the port. should i set up a port in idx1? But the external system is not an sap system and so i dont have a client.
    In XI i have defined a port in transaction we21 (transactional rfc) for the external system with rfc destination xyz. But if i enter that port in communication channel i got error messages.
    Thanks for any help.

    Hi christian,
    i'm also working in IDOC scenario between ECC to XI to MDM, if u have any document or snapshot then pls fwd it to me.
    [email protected]
    Thanks,
    Jitendra

  • Issues in IDoc Sender Scenario:IDoc  with errors added

    Hi all
             Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
    status 56 : External segment name E2KOMG003 cannot be interpreted
    status 60 : Basic IDoc type COND_A03 could not be found.
    And the segments displayed in data record  are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
    Would any one help in resolving the issue.
    Thanks,
    Chilanka

    Hi,
    >>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
    no you cannot create any partner profiles in XI
    for more about IDOC configuration in XI check :
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • IDoc- XI scenario (IDoc should be sent by XI client 500)

    Hi,
    I'd like to set up a scenario mentioned in the subject. As a source SAP system I'd like to use XI client 500. XI client 100 is used as Integration Engine. How can I generate some IDoc from the source SAP system (XI cl 500) to import it into the repository?
    Or do I have to use the R/3 as the source system?
    Do you know some helpful links about the IDoc creation and so on?
    Thanx, Peter

    Hi Peter,
    To import idocs in the IR, you need to perform the followinf steps:
    1) In a SWCV you have a field Imported objects, right click on the link which then shows import of import of SAP objects, please click on that.
    2) A window appears which for <b>Application Server, Systenm number, Username and Password.</b> Please check the system name and its client before moving further. It should be XIserver and client--500 in your case. If it's not there then double click on your SWCV and change it.
    3) Enter the values in these fields, for example system number would be the same as it is given in the SAP logon window.
    3) Here you can see links for IDOCs and RFCs and you can import the IDOC you want.
    Hope this solves your problem.
    Thanks and Regards,
    Varun Joshi

  • Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

    Hello All,
    One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
    Is the (IDoc) Communication Channel from Sending system to XI required to configured?
    Many thanks in advanced!
    Jochen

    Hi Jochen,
    for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
    Thanks,
    Rajeev Gupta

  • Problem with IDoc scenario - IDocs do not aarive to XI

    Hi guys!
    I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
    REALLY strange...
    Any suggestions?
    IDX2 metadata loaded.. I think, all needed settings are done.
    Question - do I need to set up LS in XI ABAP part?
    Thanx, Olian!
    P.

    Hi Olian ,
    just check if u have followed all the following steps
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name
    Regards,
    AshwinM

Maybe you are looking for