N:1 scenario WebsphereMQ to IDOC

Hi All,
I am working on the following scenario.
WebsphereMQ to IDOC (MATMAS05) and need to read 5 queues which have different structures. The 5 queues needs to be read by the JMS adapter at same time and should create one IDOC (to SAP/R3)
I created 5 Message Interfaces.
How many Source Interfaces an Source Message I need to create (in the Interface Mapping)?
How to proceed? Please Help

Hi Eren
have a look at this thread may be helpful for you
Re: XI--WebSphereMQ : Receiver Channel Inactive in MQ
also refer this Pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0cbc490-0201-0010-3bb7-ade73ea39e55
Thanks !!

Similar Messages

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

I have a scenario. Import IDOC into PI and PI transform IDOC to Excel. Using mail adapter attach that Excel using pi and send to customer. Can you please help me on the same?

HI Experts,
I have a scenario. Import IDOC into PI and PI transform IDOC to Excel. Using mail adapter attach that Excel using pi and send to vendor. Can you please help me on the same?
Thanks
SaiSreevastav

Hi Sai,
you can use XSLT or java mapping or adapter module to convert IDOC xml to XLS. Please refer the below blog
Convert incoming XML to Excel or Excel XML – Part 1 - XSLT Way
Convert incoming XML to Excel Sheet Part 2 – Adapter Module way
Convert incoming XML to Excel Sheet
then after converting to Excel, you can use the payloadswap bean in mail adapter
XI: Sender mail adapter - PayloadSwapBean - Step by step
regards,
Harish

IDoc acknowledgement scenario using ALEAUD01 IDoc type

Hi All,
I have a query, regarding IDoc acknowledgement scenario using ALEAUD01 IDoc type as mentioned below.
In a scenario where we configure and send ALEAUD01 to sender as acknowledgement of the IDoc’s received, is there any way how do we make sure that IDoc’s received by target SAP system has sent the acknowledgement successfully. Would there be any key information in the ALEAUD01 IDoc, which refers to the IDoc/data sent?
Thanks
Rajendra

I needed 24 seconds to know the answer
I took the word ALEAUD01 into Google and added site:help.sap.com in the search field
Among the first 10 results was one with the subject
Acknowledgment Messages
one click to open and skimming through the text ....
And opening one of the other hits in Google told me even which field is having this info

Integration scenarios from scratch: idocs or enterprise service

Hello,
We are starting a SAP PI implementation for a new SAP ECC 6.0 system. The implementation is from scratch, so we don't have to consider any historical issues or decisions. One of the first business processes to be integrated with business partners is the Procure-to-Pay process. The old way of implementing this B2B scenario was with idocs (e.g. ORDERS05 and INVOIC03), but nowadays the enterprise service bundles also contain services for this scenario. Should I choose idocs or enterprise services as a technique to get the information send to SAP PI or send the information to SAP ECC? What are the advantages and disadvantages of both techniques? Does anyone have experience with the implementation of the enterprise services for Procure-to-Pay?
Thanks for your response!
Kind Regards,
Mark

Hello,
We are starting a SAP PI implementation for a new SAP ECC 6.0 system. The implementation is from scratch, so we don't have to consider any historical issues or decisions. One of the first business processes to be integrated with business partners is the Procure-to-Pay process. The old way of implementing this B2B scenario was with idocs (e.g. ORDERS05 and INVOIC03), but nowadays the enterprise service bundles also contain services for this scenario. Should I choose idocs or enterprise services as a technique to get the information send to SAP PI or send the information to SAP ECC? What are the advantages and disadvantages of both techniques? Does anyone have experience with the implementation of the enterprise services for Procure-to-Pay?
Thanks for your response!
Kind Regards,
Mark

Integration scenarios from scratch -- idocs or enterprise service bundles

Hello,
We are starting a SAP PI implementation for a new SAP ECC 6.0 system. The implementation is from scratch, so we don't have to consider any historical issues or decisions. One of the first business processes to be integrated with business partners is the Procure-to-Pay process. The old way of implementing this B2B scenario was with idocs (e.g. ORDERS05 and INVOIC03), but nowadays the enterprise service bundles also contain services for this scenario. Should I choose idocs or enterprise services as a technique to get the information send to SAP PI or send the information to SAP ECC? What are the advantages and disadvantages of both techniques? Does anyone have experience with the implementation of the enterprise services for Procure-to-Pay?
Thanks for your response!
Kind Regards,
Mark

Hi Mark,
here are my 2 cents to your very interesting disussion.
The IDOC was designed to customize EDI data distributions between SAP Systems via messagetypes and transaktioncodes (Vorgangscodes) in the partnerdetermination which itself is mapped (the "Vorgangscode") to functional modules to do "something". The complete customizing of IDOC distribution might sometimes seems to be complex (and we both know it is more than that but it is FULL CUSTOMIZABLE from a consulting point of view.
The Enterprise Service (my personal view multiplied with the last TechEds and RampUp Delta courses) have another focus. An Enterprise Service is (mostly) some entity which is consumable from the outside world such that they are implemented with Request-Response patterns. When you only want to distribute information why will one use something like Request Response Patterns? One could argue to get back any response, any confirmation or something else....but this is also possible with IDOCs and their acks.
Another argument against to use an ES for P2P outbound scenario is, if yet not seen any ES which is triggert while create a purchase order in its related transaction. Is the BADI for such Transaction triggering the ES while the save event has been processed? If you could find out this fact and if the BADI (or some new kind of user exit for transactions) is implemented and fully supported from SAP I would choose the ES in the P2P processs. Otherwise why using the ES instead of the IDOC when using a PI as Middleware which is converting the source message type (ES or IDOC) into its proparitary legacy system format. Please let me know when you found such userexit/BADI for ES.
Please don't missunderstand my point of view, I would really throw away these IDOCS and using a couple of ES instead but what is the fully supported STANDARD from a customizable and manageable point of view. When you are familiar with proxy technology you know how easy to implement, monitor and manageble theses technology is - BUT - you always have to code some (maybe not release independent) proxy method and you maybe have to invest some knowledge for error handling, rollbacks or additional commit works - all of these stuff will be handled (mostly ) by the SAP standard delivered functions.
Last but not least - if there is any standard out there to trigger an ES from a transaction without coding I would rather use the ES instead of the IDOC. If there is no such standard I would discuss the functionality with the customer (if to complex implement an inbound or outbound proxy=ES) or extend the IDOC or use a BAPI (and extend the BAPI if needed) - mostly the proxy will the be the easiest choice if the needed field count is not to much (<30).
So long, let me know about your findings and your decision.
Regards,
Dries

SOAP to IDocs Scenario...IDocs getting locked at SAP

Dear Experts
We are sending measuring point details to SAP system from 3rd Party. Scenario is working fine for small amount of load. If more number of messages triggered (say 100) IDocs at SAP are getting stuck u201CMeasPoint 10000211 currently locked -> document processing not possibleu201D.
I tried configuring Sender SOAP adapter as EOIO and specified the Queue name as Test Queue. Still IDocs are getting stuck at SAP ECC. Now one more issues messages are getting stuck in queue SMQ2. We can control the flow by using BPM in PI. I donu2019t want to use BPM for this. Can we control this from SAP or using Trigger by background program in Partner profiles?
Please suggest. Thank You.
SAP Error Details:-MeasPoint 10000211 currently locked -> document processing not possible
Message no. IR007
Diagnosis
The object you want to access is locked, either
u2022     By yourself in another session, or
u2022     By another user
u2022     or by the system, which is still processing data for this object
System Response
The system cannot access the object.
Procedure
u2022     If you are locking the object yourself in another session, exit processing in the other session and continue processing in this session.
u2022     If the object is locked by another user, you can
o     contact the other user
o     wait until the other user has finished processing the object
u2022     If the object is locked because the system is still processing its data, wait a while, and then call up the object again.

1. Create a new process code "Z" and check the enque state of the objects before passing back to standard processing modules. Id also change to process immediate as part of this change
or
2. I think assuming RBDAPP01 is still used you may be able to make use of an exit there to do the same thing .. check and wait before processing.
or
3. In message mapping place a UDF that has some kind of wait timer in it (this is random and wont always work cause you wont know when the lock is dropped) but should work.
or
4. Dont use IDOC's create an abap proxy to do the work as a sync process. Processing will need to finish in the proxy and return to the PI stack before the next message is processed in the EOIO queue - this would be the prefered option as far as im concerned, it guarenteed to work and as long as your proxy sticks to the standard rouintes it should be upgrade friendly.
or
5. Use a proxy as above but dont do any processing, just use the proxy to build the IDOC and post it - then check the status of the locks until you are ready then rinse and repeat ..... but like scratching your right ear with your left hand .. but it will work.

XI 2.0 problem: scenario xml - xi - idoc

Hi!
my scenario is xml -> xi -> idoc1, idoc2.
when the interface start, if I call SXMB_MONI I see that idoc1 is correct; for idoc2 the system generate an error: idoc.adapter.generic, "MSGGUID 587E007DA385D54697B3F02220A78987: Tag ORDERHEADER found instead of tag IDOC BEGIN=.</"
Can you help me to undestand the problem?
10 points for you!
Thanks,
Gianluca

Bruer,
I use an interface mapping between xml (imported from SAP BBPCRM 4.0, data type OrderCreateOrChangeVendorOut) and Idoc custom. My mapping is graphical mapping without java class or xsl.
My scenario work with one xml and two different idocs. Today I have added a second idoc. The problem is that the first one work correctly, for the new idoc generate an error for idoc_adapter.generic.
The jar file for the mapping is mandatory for my new idoc?
Thans you very mutch,
Gianluca

Error in TRFC for IDoc to File scenario while sending IDoc

Hi,
Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
Can anybody help me out in resoving the error?
Regards,
Suraj Kumar

Hi,
Thanks for your reply.
It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
Hope I am clear.
Please let me know, if you need any further information.
Regards,
Suraj

Error in executing scenario File to Idoc

Hi,
I did File to Idoc scenario.
In that I got error in status record at r/3 system...
status record code is 51....Error is <i>Application document not posted</i>
regards,
pavani

Hi Ravi,
i mapped some of the data fields. Control fields i disabled them....
Can you giv me wat are the importent fields for Cremas04...
I did all the field that are indicated in red color..
still i m getting error
Message was edited by:
Pavani Kumari Kokkiragedda

Scenario R/3 (Idoc) to XI to (Idoc) JCO External Server (non sap system)

Is this scenario possible ?
We currently have issue with downloading metadata of idoc from external JCO server.
Thanks in advance

Hello Jean-Charles,
Perhaps you can use flatfile instead of JCO connection.
Check this doc: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Regards,
Chris

Scenario Mail to Idoc with many Attachment.

Hello,
         I have a **Mail to Idoc** Scenario. The Mail that I receive contains 3 attachment in XI.
         Please let me know how to configure this sender mail adapter to capture all the attachment and send them to the BPM.
         I have seen many examples, but any of them helps me.
         Regards,

Hi Federico
As stated in the blog
Try with or without mail package. Set your outbound interface name as default interface name and use Keep attachments.
Pi will be able to receive Payload with 3 attachments.
In PI attachments are dealt separately then payload. You can access payload in Xi mappings but not attachments.
Moreover your case is Mail to IDOC, where you want to handle attachments. This can be passed to R/3 as attachments only.
As per my knowledge IDOC's cannot handle attachments only BDOC can. How you are trying to achieve this?
Thanks
Gaurav

Scenario:file to idoc

dear experts
here my scenario is file to idoc
message is sent successfully from sender but which is not received in receiver i.e,in r/3.
the error which i found id
error category:idoc_adopter
error code:attribute_inv_rcv_serv.
plz any one can help me?????????
regards
somesh

hi
Receiver service cannot be converted into an ALE logical system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
In Business System(R/3) 'Adapter specific identifiers' chooset 'Compare System Landscap Directory' refersh cache and activate objetcs
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Scenario: File To Idoc & Idoc To File

Hi,
Can any body explain file to idoc and idoc to file scenario's with screen shots which incluses setting at R/3 side and XI side. Starting from SLD to ID.
Thanks in advance.
Regards,
Prems.S

Also u can follow the settings on Xi and R/3 side
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.

BMP scenario for Multi Idocs

Hi ,
Iam working on Idoc to File scenario for sending multiple Idocs. Iam using BMP for sending the Idocs. The problem is when I test only one Idoc is seen at the target file. ie., the first Idoc sent. The second Idoc is not getting transferred to the receiver.
In BPM Iam using loop and when the stop message is sent then it comes out of the loop.
Can some one help in resolving the problem.
Best Regards
Suresh Kasu

Hi,
Iam using only one IDOC type.
Iam using the following steps:
Start->
Fork->
Loop->
Receive->Transformation->Container operation->
Loop->
Fork->
Transformation->
Send->
Stop.
one more Receive for Stop Message
Click the link to get the image.
http://www.mediafire.com/?sharekey=d6de576d1148fe26d2db6fb9a8902bda
Best Regards
Suresh

N:1 scenario WebsphereMQ to IDOC

Similar Messages

Maybe you are looking for