JMS -- PI -- IDOC Party Communication

Hi,
I have a scenario JMS --> PI --> IDOC and vice-versa. JMS is an external system, so using PARTY communication. SAP System is within customer landspace.
My doubt is - I have to import a Business System in ID for the IDOC (SAP system). Now where should I import this Business System? Should I import the SAP Business System under Party or under Without Party?
If I am not wrong Business Component for JMS will come under the Party; have a doubt about the Business System.
Thank you,
Pankaj.

If this is in another landscape then use Party..
Ok. So nowI have imported the Business System (SAP ECC) under Without Party and will create the Business Component for JMS under Party.
Thank you,
Pankaj.

Similar Messages

Problems in IDOC receiver communication channel

Hi,
I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
Please assist.
Rgds
Kishore

OK in that case, we are getting the following error in the Message monitoring:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
<SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
Please check and assist.
Rgds
Kishore

JMS to IDOC scenario...

Hi,
I am doing an JMS to IDOC scenario...
where will i mention saying there is a logical system in R3(Partner profile).The IDoc should reach that Logical system only.I have a doubt on this....Because we are disabling the IDOC EDIDC segemnt in Recever segment.so.
Please guide me.

You fill the mandt field like SNDRPRT, RCVRPRT and others in the mapping and you can take care of rest in the R/3 side.
You could fill up it in mapping and apply the Check box as mark for considering the control record from Payload in communication channel. Just pass the mandatory fields as you have used the details to configure the prtner profile and port.
You could also specify the Adapter specific attributes with the same logical system name in Busines system or service that could fill-up the control records internally.
Refer
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/frameset.htm
SAP Network Blog: Manipulating Idoc Control Records from Payload
Manipulating Idoc Control Records from Payload
changing IDOC control record by XSL Mapping

How to implement this Scenario(JMS to IDOC)

Hi Frnds,
I am working on one scenario JMS to IDOC .based on JMS Message my XSLT Mapping will genarate Multiple Idocs(max 3) or 2 or one.
I have to send this IDOCS based on some conditions,the conditions mentioned below.
xslt mapping genarats one message ,but this contains 3 IDOCS or 2 or 1.(Order Create , Order Change and Order Response),
what is the best approach to implement this scenario
1)f Order Create segment exists (new PO), first check SAP to see if PO does actually exist using RFC Z_BBPR46_GET_PO_FROM_FPA ,If it does not exist, pass Order Create idoc to SAP to create new purchase order
If it does exist, retrieve PO details from RFC and pass Order Change idoc to SAP to update existing purchase order
2)If Order Change segment exists (change PO), retrieve PO details using RFC Z_BBPR46_GET_PO_FROM_FPA and pass Order Change idoc to SAP to update existing purchase order
3)If Order Response segment exists (goods movement), retrieve PO details using RFC Z_BBPR46_GET_PO_FROM_FPA and pass Order Response idoc to SAP to create goods movement.
Above logic i implemented in one mesage mapping Source is XSLT Mapping Output and Receiver message in message mapping is Multimapping selected 3 IDOCS.
Regards,
raj

thanks

How to reduce processing time in case of jms to idoc scenario

hi all,
i am doing jms to idoc scenario.
in this i'm using xslt and graphical mapping.
while perfroming E2E testing the messages are taking lot of time to get processed.
please tell me as how can i reduce this processing time or in short how can i overcome this problem.this is a critical issue in production.
regards
madhu

Hi,
1. To reduce the processing time for JMS -> IDOC scenario, try to get the Average processing time taken by JMS adapter, IE, IDOC adapter for the messages that are processed so far by going thro the Adapter Audit logs, SXMB_MONI race and Time in WE02 in R/3 system. Calculate this for 5 - 10 messages at different time to get the clear idea of which step is consuming more time. Then it will be helpful to focus on tuning that specific step. If you are using BPM, check the processing time taken by PE.
2. Check the Inbound and Outbound queues used by this interface, if required try to configure Prioritized Queue with more time allocated for this interface in Integration Engine.
3. Check the load on the Integration Server when this Interface messages are getting processed, to understand/ isolate the interfaces which are consuming more processing time and system resources.
4. If this is not in Production try to perform the Mapping/ transformation in graphical mapping itself, it will be helpful to minimise use of XSLT mapping to get better performance.
5. Check if the Archive and Delete jobs are running successfully in the Integration Server, since this will free up the occupied resources in the system.
6. If possible post seperate Forum questions for issues in different Interface scenarios, it will be easy to understand the problem for all of us.
Hope this will be helpful,
Regards,
S.Santhosh Kumar

JMS - PI - IDoc scenario: possible to disable check for duplicate JMS message ID?

Dear all,
we have a scenario JMS - PI - IDoc. We are on 7.4 SP 7 AEX.
Once and again we get this error in PI Logs
com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(MessageFilterContext filterCtx)
Duplicated and already processed JMS message with JMSMessageID ID:414d512053415050523120202020202053f0f4852000fb39 and XI message id b0beffdbcee64c2605779eaacf27b335 detected.
We are currently investigating the error and it seems that the duplicate message IDs already exist on the JMS (MQ) side. The messages with the same ID reside in the same queue but have different payloads, so really are different messages
While it's certainly true that we need to get rid of those duplicate IDs in the long run, I'd like to ask if it is possible to tackle the problem from both sides.
My sender JMS Adapter looks like this:
Transactional JMS Session = Checked
Set PI Message ID (MessageID) to = GUID
Set PI conversation ID (ConversationID) to = No Value
Enable Duplicate Handling = Unchecked
Prefix Channel ID = Unchecked
--> Is there any way to tell PI to just ignore the duplicate JMS ID and continue processing?
Many thanks
Kind regards
Jens

Hi Jens - Please have a look at the below note if it helps.
If you want the duplicate messages received from different channels (that is JMS Messages with the same Message ID) to be processed as a distinct JMS messages and not as duplicate messages, select Prefix Channel ID to JMS Message ID
Reference :
Configuring the Sender JMS Adapter - Advanced Adapter Engine - SAP Library

RFC Look Up APIs for a IDOC Receiver Communication Channel

Hi,
Can we use RFC Look Up APIs in UDF for a IDOC Receiver Communication Channel. (File to IDOC Scenario). Requirement is to send a notificaiton when IDOC got posted with IDOC number.
Best Regards,
Madan Agrawal

As the name suggests, RFC lookup uses RFC receiver channel only. In mapping of your File to Idoc scenario, you may perform this lookup.
Requirement is to send a notificaiton when IDOC got posted with IDOC number.
Configure ALEAudit for this requirement. How were you planning to use RFC lookup for such a requirement?
Regards,
Prateek

JMS to IDOC error

I am doing a JMS to IDOC scenario...
i am getting an error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_ECC_TTG_CREATE_:
RuntimeException in Message-Mapping transformatio~
Before it was working fine...
i dont why this is happening...

Hi PSRK,
It looks like it is a message mapping error.
take the raw payload from SXMB_MONI and run in the test tab of the message mapping. To know the exact issue.
Regards,
ravi

IDOC to JMS and JMS to IDOC.

Hi All,
I read most of the thread and found also some good link . But failed to get the exact thing that i need to carry out for this implementation. So , i am looking forward for your valuable help to get a clear understanding on this.
Scenerio : IDOC to JMS.
1. What need to carry out for configuring the JMS adapter as the receiver.
I know the configuration side from SAP[IDOC] to XI side. But dont have any idea on configuring the JMS adapter.
2. What drivers that i need to instal on ? & how can i know which driver should i use for my scenerio ?
3. What details do i need from the client ?
Scenerio : JMS to IDOC.
1. I have the same thing to configure from JMS to SAP[IDOC], SO for this what else do i need to configure?
2. What need to carry out for configuring the JMS adapter as sender?
Can anyone, please provide me the details on this..
Thanks in advance.
Jay.

Hi,
Check the links
http://help.sap.com/saphelp_nw2004s/helpdata/en/c1/739c4186c2a409e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/65/52693cab05e079e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/f8/24ee41c334c717e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm
Thanks!

JMS to IDOC xslt mapping

Hi,
We have a JMS to IDOC scenario. We are using PI7.1. We are currently using XSLT Mapping . This needs to be replaced by Graphical mapping as XSLT mapping is consuming more memory.
If we remove the XSLT Mapping between source and target would we need content conversion for the soruce file ?
Please advice.
Thanks,
Teresa

Hi Teresa,
File Content conversion(fcc) is used to convert Any format file to XML format, while sending the data into PI.
& XML format to Any required output format, while sending data out of PI.
B'cos, PI only understands XML language.
So, this has nothing to do with XSLT mapping in your case.
change XSLT mapping to Graphical mapping. that should accomplish your task.
-santosh.

JMS to IDOC

Hi,
I'm working on JMS to Idoc scenario, this is going to be a huge volume scenario( may be 50K messages at a time from legacy). So SAP folks needed the maximum records in a Idoc would be "10000" and should processed for 5 times something like that.
How can I achieve the same in XI. Please help me out.
-Xavier

First of all you have to create an external definition in which you have to change the occurrence of IDOC as 1...unbounded. Then use the UDF as mentioned below to create a context change after 5000 records for example. And then map the UDF to "IDOC" segment.
While creating the UDF select the Cache as "Queue".
int count = 0;
for (int i = 0; i<input.length; i++)
count = count + 1;
if(count == 5000)
result.addValue(" ");
result.addValue(ResultList.CC);
Count = 0;
//if at any time records are less then 5000 then also an idoc should be created
if(input.length < 5000)
result.addValue(" ");
While doing the mapping you have to set the context of source node at higher level or use removeContext. e.g.
SourceNode -
>RemoveContext -
>UDF -
> IDOC.
To change the occurrence of IDOC follow step1 to 4 from below mentioned blog...
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Regards,
Sarvesh

Difference between Master Idoc and Communication Idoc.

Can anyone list out the difference between Master Idoc and Communication Idoc?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
Layout of an IDoc control record
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

Party to Party communication

Hi All ,
Can i define an internal system as party ?
Here goes details of my scenario -
1)Internal system ( SAP R/3 system part of land scape ) defined as Party
2)Communication party ( external system ) connect thru HTTP adapter .
What are the various ways of sending data from R/3 system to XI system ?
Do i need to configure any sender adapter ?
Cheers,
Reddy

hi,
Can i define an internal system as party ?
u dnt define a system as a party. rather u define a party representing a larger unit like organization. n then assign systems to that party. so in ur scenario u can definitely have two parties, ur organization n the other company.
ways of sending data from R/3 system to XI system ?
3 ways-- idoc, rfc and proxies (for WAS>= 6.20)
Do i need to configure any sender adapter ?
for idoc- no. for rfc -rfc adapter. for proxy-generally no--xi adapter (depends)
also refer this:
Settings for proxy scenarios
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
ABAP ProxyFile
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
File ABAP Proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
[reward if helpful]
regards,
latika.
Message was edited by:
Latika Sethi

CRM To ECC Sold to party Communication Details Not populated in ECC

Hi All
i have one problem when we create sales order through crmd_order we need to give sold to party and ship to party numbers suppose like
8000002166 for both and status i keep as order created and in partner tab i i seem all partner funtions(sold to, ship to ,bill to, payer)with 8000002166
in header overivew i given posting date as feature date like 30-09-2013 then i try to save this order.
the order generated sucussfully but problem is i am not getting sold to party details in ECC when i check VA03 And open cretaed order in CRM and clicking on sold to party and i seem details for this but i am not getting communication details like telephone number and email id extension number.
for this sold to party we already maintained all communication details in CRM.When i open this sold to party BP i am able to see all details
didnt understand why these details not replicated to ECC?
We implemented one custom class there we implemented badi.
IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
i am not getting BAPI ADDRESS Table values into CT_BAPIADDR1
how can i send communciation details to ECC For sold to party?
The code part we follow like below
TYPES : BEGIN OF t_otc, " Type to create a table with the given columns.
 bpid TYPE bu_partner, " variable of store processed business partner ID's
 otcid TYPE bu_partner, " variable of store processed OTC ID's
 otcguid TYPE bu_partner_guid, " variable of store processed OTC GUID's
 address TYPE bapibus1006_address,
 tel1_numbr TYPE ad_tlnmbr1,
 tel1_ext TYPE ad_tlxtns1,
 e_mail TYPE ad_smtpadr,
 END OF t_otc.
*& V A R I A B L E S &*
DATA : lv_bp_payer TYPE bu_partner, " Variable To Cast the payer Id into BU_Partner data type.
 lv_partner_fct TYPE crmt_partner_fct, " Variable To Store Partner Function Number.
 lv_partner TYPE bu_partner, " Variable To Store Current Business Partner ID.
 lv_process_type TYPE crmt_process_type, " Variable to Store process type.
 lv_sales_org TYPE crmt_sales_org, " Variable to store sales org. name of order
 lv_dis_channel TYPE crmt_distribution_channel, " Variable to store distribution channel of order.
 lv_division TYPE crmt_division, " Variable to store division of sales org. data.
 lv_role TYPE comt_partner_parvw, " Variable to store retrieved role from FM.
 lv_role_value TYPE parvw, " Variable to store the role value of Partner Functions.
 lv_otc_guid TYPE bu_partner_guid, " Variable to store OTC GUIDs for the OTC ID.
 lv_otc_id TYPE kunnr. " Varaible to OTC ID revocered from Table.
DATA: lv_busspartner TYPE bapibus1006_head-bpartner,
 lw_central_data TYPE bapibus1006_central,
 lw_centraldata_person TYPE bapibus1006_central_person.
*& W O R K A R E A S &*
DATA : lw_address TYPE bapibus1006_address, " Work Area to store address recovered for BPID.
*Start of code change for Defect 904 Fix
 lw_tel TYPE bapiadtel,
 lw_email TYPE bapiadsmtp.
*End of code change for Defect 904 Fix
*& INTERNAL TABLES &*
DATA : li_otc TYPE TABLE OF t_otc, " Internal Table to Store the OTC IDs and BPS.
 li_values TYPE zconst_values_t,
*Start of code change for Defect 904 Fix
 li_tel TYPE STANDARD TABLE OF bapiadtel,
 li_email TYPE STANDARD TABLE OF bapiadsmtp.
*End of code change for Defect 904 Fix
* F I E L D - S Y M B O L S *
FIELD-SYMBOLS: <f_orderadm> TYPE bad_orderadm_h_mess,
 <f_otc> TYPE t_otc, " Field-Symbol to Read the OTC TABLE data.
 <f_partner> TYPE bad_partner_mess, " Field-Symbol of Partner Table For Looping.
 <f_bapiparnr3> TYPE bapiparnr3, " Field-Symbol to Store The Row of BAPIPARNR3.
 <f_bapiaddr1> TYPE bapiaddr1,
 <f_orgman> TYPE bad_orgman_mess, " Field-Symbol to Read the ORGMAN table.
 <f_values> TYPE zcr_const_values.
*& C O N S T A N T S &*
CONSTANTS : lc_program_name TYPE progname VALUE 'ZOTC',
 lc_param_payer TYPE paramname VALUE 'PAYER', " Constant to Store Payer Parameter name.
 lc_ref_kind TYPE crmt_object_kind VALUE 'A',
 lc_req_1 TYPE zrequest_no VALUE '1',
 lc_req_2 TYPE zrequest_no VALUE '2'.
* Retrieving the general and Common Data for a Order.
READ TABLE it_bus_trans_msg-orderadm_h INDEX 1 ASSIGNING <f_orderadm>.
IF sy-subrc EQ 0.
 lv_process_type = <f_orderadm>-process_type.
ENDIF.
* Reading the Orgnisation Details from ORGMAN Table.
READ TABLE it_bus_trans_msg-orgman WITH KEY ref_kind = lc_ref_kind ASSIGNING <f_orgman>.
IF sy-subrc EQ 0.
* Storing the Sales Organisational Data to find the OTC_ID.
 lv_sales_org = <f_orgman>-sales_org.
 lv_dis_channel = <f_orgman>-dis_channel.
 lv_division = <f_orgman>-division.
ENDIF.
* Retrieving the partner function number for the payer by giving requirement no 2 and rule no 1.
CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
 EXPORTING
 pi_program_name = lc_program_name
 pi_req_no = lc_req_2
 IMPORTING
 po_const_values = li_values.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* Reading the value for the constant with the name as PAYER.
READ TABLE li_values WITH KEY param_name = lc_param_payer ASSIGNING <f_values>.
IF sy-subrc NE 0.
 RETURN.
ENDIF.
* Retrieving the Partner ID for the PAYER.
READ TABLE it_bus_trans_msg-partner ASSIGNING <f_partner> WITH KEY ref_partner_fct = <f_values>-constant_value.
IF sy-subrc EQ 0.
* Storing the current partner ID.
 lv_bp_payer = <f_partner>-ref_partner_no.
ENDIF.
REFRESH li_values.
* Retrieving the Partner Function Number which are to be checked for replacing with the OTC ID with request no 1 and rule no 01.
CALL FUNCTION 'ZCRAN_GET_CONSTANT_VALUES'
 EXPORTING
 pi_program_name = lc_program_name
 pi_req_no = lc_req_1
 IMPORTING
 po_const_values = li_values.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* Transferring the constant value to our table for Partner Fucntion.
LOOP AT li_values ASSIGNING <f_values>.
* Read Partner table for Header data and the reference partner function retrieved.
 READ TABLE it_bus_trans_msg-partner WITH KEY ref_kind = lc_ref_kind ref_partner_fct = <f_values>-constant_value ASSIGNING <f_partner>.
 IF sy-subrc EQ 0.
* Storing Current Partner Function.
 lv_partner_fct = <f_partner>-ref_partner_fct.
* Storing Current Partner No.
 lv_partner = <f_partner>-ref_partner_no.
* Retrieving the Partner Role (R/3) for the current partner function of CRM.
 CALL FUNCTION

The problem is in the Lotus Notes security level, not in SAP.

Multi Mapping without BPM (JMS 2 IDoc)

Hi,
i have a JMS-Query where it is necessary to map the given data to two different IDoc Types.
Therefore i have to mappings in two different namespaces. Is it possible to use these insde of the interface Mapping?! Or does the target types have to be in one mapping and one namespace?!
Can i use context objects?!
Please guide me! br, Jens

HI,
Ingeneral multi mapping in IM , we can use , to do it it should satisfies accordingly .. i mean see the below link
/people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
Multiple message mappings in one integration scenario
With context object , we can route based on condition , this will be used in interface determination with condition , to this condition , we can use Context object, but it should be configured in MI.
Regards
Chilla

JMS -- PI -- IDOC Party Communication

Similar Messages

Maybe you are looking for