Send IDoc to R3 in Integration Process

Hello everyone,
I want to send some idocs to R3 system's vender from XI Integration Process, but i do not how how to configure in the adapter-specific identifiers. If i set the Idoc Adapter Logical System, the idoc went to the logical system, if i did not set the logic system, it raise an error "Unable to convert sender service BS_SAP_R3 to an ALE logical system". So how can i configure the Integration Process in Integration Directory to send idocs to R3 system's vender?
Regards,
Nick

Hi Nick,
Look at these threads please..
Configuring to receive a iDoc in R/3 sent by XI
How To use External Message To Send IDOC From XI To R/3
Hope these help you!
cheers,
Prashanth

Similar Messages

Missing sender information in message from Integration Process

Hi All,
I am testing a scenario uses Integration Process. This Integration process sends out a async message but this message has empty sender tag in header , Because of this routing rules and agreements defined for this are not triggered and message goes into error state.
There is sender interface Information in message header but not integration process information. I am working on SAP NetWeaver PI 7.1 system. This is working from other synchronous interface in same process.
Routing rule and receiver agreement has sender as mandatory field, so can not define generic set without sender component.
I went through SAP Note 807640 But there is no information about such error.
Am I missing something in configuration? Please let me know how can i configure Routing Rule and Interface Determination for this scenario.

Thanks for replying to the post.
Integration process is used as a async-sync bridge. Following are high level steps.
1. Receive async FI message from sender
2. Map message to BAPI SAP FI document
3. call Sync BAPI.
4. Map the response of BAPI.
5. Post it back to sender in async mode.
I am having problem in step 5 where message is coming out of BPE without its own name (i.e sender name). Thus it does not triggers Routing rules and fails.

Problem converting Integration Process to ALE logical system(acknowledgmen)

Hello,
I have a scenario where a sender SAP system sends an IDoc via an Interface Mapping to an Integration Process.
This worked perfectly fine on our development environment, but after transporting the scenario to our quality systems I got the following acknowledgement error:
Unable to convert the sender service name of integration process to an ALE logical system.
What could be the reason for this? We have a logical system on the sender SAP system set up for the XI system itself but not for the Integration Process.
We also use SYSTAT IDocs and there we set the the logical sender system name to the logical system for SAP XI and not for the integration process.
Is this also necessary for acknowledgements? Where could this be done. Strange thing is that it works perfectly fine on our development environment.

I raised the same question a few months back.Answer to this question is in the same thread.
Idoc Acknowledgements - Logical System Name
You will have to select option "Restore Original Parties for Idoc Acknowledgments " in the Acknowledgment Idoc adapter.
Regards
Bhavesh

Question on BPM Integration Process

Hello Experts,
I am following this BPM article which is very similar to what I want to do.
We are using PI 7.1 without EP1.
I have an XML to IDoc scenario where my XML's external definition resides in a seperate SCV (SCV1) and my imported IDoc resides in a seperate SCV (SCV2). We did this to follow the Sender-Mapper-Receiver model. We have a different SCV for Mapping which holds MM and OM (SCV3). Now, I have my Abstract Service Interfaces for external definition in SCV1 and abstract interface for IDoc in SCV2. And, Integration Process in SCV1 (no good reason). But, now I am not able to access SCV2 abstract interfaces (IDoc abs) in my Integration Process since it sits in SCV1. I am thinking if I have to crate my external definitions, idoc, abstract service interfaces, MM, OM and Ingtration Process in one SCV instead of having them in three different SCVs. I was trying to follow sender-mapper-reciever model but seems like for BPM you need to have all your stuff in one SCV. Please help if you know how to resolve this issue wiithout getting rid of sender-mapper-receiver concept.
Thank you in advance for your help.
- Mayur

Thanks Jose. I think creating dependencies is a away to go. I also found this this where Stefan suggested same thing.
So, now Sender (SCV1) and Receiver (SCV3) have been added under Mapper (SCV2)'s dependencies list and I will have my BPM Integration Process in the SCV2 which will give me access to both sender and receiver abstract service interfaces.
Re: Software Component Dependencies PI 7.1
Thanks,
Mayur

How to configure Integration Builder using an Integration Process?

Dear experts,
I have problems configuring the Integration builder using a Integration process.
Scenario = idoc to PI, integration process transforms idoc to file, file to external system.
My integration process starts with an abstract interface (structure of idoc) and ends with an abstract interface (structure of file). But I just can not configure the integration builder correctly...
I did it as follows:
Sender agreement: comm.component = SAP system; interface = Idoc;
receiver determination: comm.component = SAP system; interface = Idoc; configured receiver = my integration process;
interface determination: comm.component = SAP system; interface = Idoc; receiver = target system comm.component;
Receiver agreement: comm.component = SAP system; receiver = target system comm.component; interface = filestructure of target
This does not work unfortunately. How can I pass the Idoc to my abstract interface? And how can I pass the result of my integration process (abstract interface) to the inbound interface? In the interface determination I can not select my Operation Mapping (but that should not be nessesary as I already created an Integration Process)...
Hope anyone can help.
Thanks and regards
William

Just consider your BPM is receiver, and sender:
Src --> BPM (BPM is Receiver)
==========
Sender Agreement (If it is IDOC or HTTP, then you do not have to create)
Commnunication Channel
Receiver Determination
Interface Determination
BPM --> Target (BPM is sender)
============
Receiver Determination
Interface Determination
Communication Channel
Receiver Agreement
If your BPM interact with other systems, you will have more Receiver Determination and Interface determination, possible Receiver agreement
Hope this clear your doubts
Liang

Integration process in configuration is in Error

Hi all,
 I am doing an SOAP to RFC scenario using BPM on PI7.1 . When I am importing the BPM into Configuration it is not showing me interfaces in the sender and receiver interfaces of Integration process. In transaction SXI_CACHE I am not able to see my integration process in Cache I checked Cache Status in integration directory there in ChangeListView tab everything is green but in Problem and ObjectView tabs my integration process is in error. Error's short description displays there is Serialization error.
Detailed error shown
Thrown:
com.sap.aii.ibdir.server.serialization.cpa.ProcessRefreshException: Serialization error
 at com.sap.aii.ibdir.server.serialization.cpa.HmiProcessCacheRefreshClient.call(HmiProcessCacheRefreshClient.java:85)
 at com.sap.aii.ibdir.server.serialization.cpa.InternalSerializationServiceService.serializeForCache(InternalSerializationServiceService.java:281)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:594)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:208)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:599)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:487)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:222)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:149)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.setXmlDataAndBufferSize(CacheRefreshSession.java:123)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.<init>(CacheRefreshSession.java:40)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.getInstance(CacheRefreshSession.java:54)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshServlet.doGet(CacheRefreshServlet.java:47)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
 at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: com.sap.aii.utilxi.hmi.api.HmiMethodFault: Serialization error
 at com.sap.aii.utilxi.hmi.api.HmiMethodFault.parseGdi(HmiMethodFault.java:156)
 at com.sap.aii.utilxi.hmi.core.msg.HmiResponse.setState(HmiResponse.java:181)
 at com.sap.aii.utilxi.hmi.core.msg.HmiResponse.parseGdi(HmiResponse.java:132)
 at com.sap.aii.utilxi.hmi.api.HmiHttpJDKClient.sendRequestAndReceiveResponse(HmiHttpJDKClient.java:256)
 at com.sap.aii.utilxi.hmi.api.HmiClientAdapter.invokeMethod(HmiClientAdapter.java:92)
 at com.sap.aii.ibdir.server.serialization.cpa.HmiProcessCacheRefreshClient.call(HmiProcessCacheRefreshClient.java:67)
 ... 43 more
Thrown:
com.sap.aii.utilxi.hmi.api.HmiMethodFault: Serialization error
 at com.sap.aii.utilxi.hmi.api.HmiMethodFault.parseGdi(HmiMethodFault.java:156)
 at com.sap.aii.utilxi.hmi.core.msg.HmiResponse.setState(HmiResponse.java:181)
 at com.sap.aii.utilxi.hmi.core.msg.HmiResponse.parseGdi(HmiResponse.java:132)
 at com.sap.aii.utilxi.hmi.api.HmiHttpJDKClient.sendRequestAndReceiveResponse(HmiHttpJDKClient.java:256)
 at com.sap.aii.utilxi.hmi.api.HmiClientAdapter.invokeMethod(HmiClientAdapter.java:92)
 at com.sap.aii.ibdir.server.serialization.cpa.HmiProcessCacheRefreshClient.call(HmiProcessCacheRefreshClient.java:67)
 at com.sap.aii.ibdir.server.serialization.cpa.InternalSerializationServiceService.serializeForCache(InternalSerializationServiceService.java:281)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:594)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:208)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:599)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:487)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:222)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:149)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.setXmlDataAndBufferSize(CacheRefreshSession.java:123)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.<init>(CacheRefreshSession.java:40)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.getInstance(CacheRefreshSession.java:54)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshServlet.doGet(CacheRefreshServlet.java:47)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
 at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
 at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Please give me a valid solution that can help me to overcome this error.
Thanks in advance
Regards,
Sami

Hi Sami,
just go to IR........open your BPM............from the menu, choose check option........see if you get any errors for your bpm process..........if there are any error, then edit your bpm and do the changes and save and activate it........if there is no error then also just edit your BPM description and save and activate it again......now in SXI_CACHE you should see your integration process.........if still SXI_CACHE does not show your BPM process then do a complete cache refresh....then rerun SXI_CACHE and now you should see your BPM process.....then in ID just import your BPM process and do the required configuration..........
Regards,
Rajeev Gupta

Correlate MDN to AS2 message using an integration process

Hello,
I had a similar question in a previous thread but closed it as the problem might have not been to clear.
Problem is that we have to use BPM for an AS2 scenario and correlate the MDN back to the process as we need BPM functionalities such as error handling and time-outs as well as some data enrichment.
Problem is even when I request the MDN synchronously on Adapter Level it is delivered as asynchronous message back. So I need to figure out how to correlate it.
MDN contains the messageID so I tried to use the messageID of the original message as correlation. However problem is that a new message ID is assigned when the message is sent by the integration process and the second on is used then as ID in the MDN.
It seems to me that it is therefore not possible at alle to correlate the MDN? However this is a definitive requirement so I am really stuck at the moment.
Do you have any idea?
Thank you very much!

Hello,
well, actually the correlation itself would work as I extract the messageID in a transformation step and then activate the correlation in a send step.
If I check the flag "Refer MDN to XI" in AS2 receiver channel the MDN is delivered back to the integration server and the original messageID is then part of the MDN message payload.
However, and that is the big problem, the MDN uses the second messageID that is created when sending the message from the integration process (and not the first one when the message is sent from sender and process by the integration process).

Receiver Agreement for Integration Process

Dear All
I am facing a strange problem when I am sending a message via proxy to SAP PI whci is then supposed to forward it to a legacy system.
I am using a BPM and am getting an error like no receiver agreement found between the sender SAPECC system and receiver integration process

Hi,
>>>a BPM and am getting an error like no receiver agreement found between the sender SAPECC system and receiver integration process
use the integration directory wizard and create two configurations
- ECC - PI (integration process)
- PI (BPM) - to the legacy
then it will work - this is not an error but lack of configuration
Regards,
Michal Krawczyk

Idoc to flat file using Integration process does not show up at all

Hello All,
I created a scenario IDOC to Flat File using Integration Process and one without IntegrationProcess. I am able to execute the one without Integration Process easily.
However when I send the IDOC from SAP then the Integration Process scenario just does not work.
I Checked SXMB_MONI There is no entry for the Integration Process.I can see entry for other without Integration Process.
SXI_CACHE : I can see my Integration Process active
SWEQADM : I have activated the Event Queue and Background job
SWF_XI_ADM_BPE : ALL BPE is showing green status.
All syntax check on IP are fine.
There is no Basis Help for me so there could be some additional basis steps which need to be configured. Has anyone faced such an issue with Integration Process?
Regards
Prashanta

Hope this might help you. when u configure an IDoc as Sender with BPM this is how you proceed.
1. let us split the scenario into two.
a. Sender to BPM ( Integration Process).
b. BPM to Receiver.
2. First let us configure the first Sender to BPM.
a. Sender Agreement( Not required ).
b. Receiver Agreement( NOT Required).
c. Receiver Determination( Sender Service, Outbound Interface, Receiver Service(Integration Process).
d. Interface Determination( Inbound Interface(Sender Abstract Interface), Message Mapping(NOT Required if your using transformation stepin Integration Process)).
3. Now let us configure the Second BPM to Receiver.
a. Sender Agreement( NOT Required)
b. Receiver Agreement( Sender Service(Integration process), Receiver Abstarct Interface,Receiver service, Inbound Interface).
c. Receiver Determination( Sender Service(Integration Process), Receiver Abstarct Interface,Receiver Service).
d. Interface Determination( Inbound Interface, Message Mapping(NOT Required)).
So Finally we have One Receiver Agreement, Two Receiver Determinations, Two Interface Determinations.
Please let me know if you have any more queries.
Regards
Gopi

Sending step in Integration Process waiting for Acknowledgement infinitely

In process I had to send an MATMAS, CLFMAS and CNPMAS. The data for
this IDoc comes in one message from third party system. So, my
Integration Process has receive step (to collect a data), and three
send-steps (for MATMAS, for CLFMAS, for CNPMAS), one by one. The
receive-step catch an inbound message and then (without transforms)
send this message to each of this three send-steps in Asynchronous
mode. The inbound message transforms in Interface Determination to
IDoc. Three steps, one Interface Determination with three conditions,
that looks
like «ProcessStep=send_matmas», «ProcessStep=send_clfmas», «ProcessStep=s
end_cnpmas», and in this place I set a mapping to transform inbound
message to IDoc. All send-steps has property Acknowledgement, which set
to Transport value. So in first send-step MATMAS goes to R3, then R3 in
response send ALEAUD IDoc (trans WE05 shows an incoming MATMAS and
outgoing ALEAUD); ALEAUD comes to XI (trans IDX5 shows inbound and
outbound messages), but ALEAUD didnu2019t transforms to XI Acknowledgement.
And there is no any CLFMAS or CNPMAS, because all processes sleeps in
their first send-steps (trans SWWL shows a many STARTED processes).
Each send-step waits for event u2018SEND_OK_TRANSPORTu2019. Moreover, if I use
trans sxmb_moni to monitor this situation and if I press refresh (F5
button) every time, sxmb_moni every time requests a status of
Acknowledgements, XI transform ALEAUD to Ack, send-step in process
catch this status, process wake up and moves to next send-step (which
sends an CLFMAS and waits for Ack). By continuously pressing refresh
(F5) in sxmb_moni all process becomes COMPLETED (trans SWWL), all
ALEAUD transforms to XI Ack and all IDocs goes to R3. But pressing F5
itu2019s not a solution for integration.

Hi Igor,
I dont think your manual refresh changes the status . The status changes is the status change of GUI . The system will take how much so ever it needs to take and not as per your manual refresh.
Regards
joel

IDoc creation in Integration Process ...

Hello guys,
I have a question for you. Is it possible to create Integration Process with one loop that will generate and send one specific IDoc every 5 minutes. I've created new process and I put new loop between Start and Stop marks. The loop has condition "true = true" and it contains a Wait (waiting interval is 5 minutes) and Send step. How could I configure parameters of the Send step? I want the Send step to create new IDoc (IDoc type will be still same and its content also) and send it to a receiver (receiver will be also still same). Where can I specify the IDoc type and IDoc's content?
Regards,
Zbynek

Hi,
You can check the Idoc status using the transactions WE02 OR WE05.
When the Inbound Idoc is created then the status will be 64(IDoc ready to be transferred to application) then after you process the Idoc then the status will change to 53(Application document posted).
Thanks,
Srinivas

Receiver From Field of Send Step of Integration Process

Could somebody please explain how this works? I cannot get receiver determination to work for a synchronous send of an Integration Process, and I think this is the problem.
Documentation states the following:
Calling a Receiver Determination Defined in the Integration Directory
 1. In the Receiver From field of the properties area of the send step, select Send Context.
 2. In the Send Context field, specify a character string for the send context.
You can choose the character string yourself. You must specify the send context to be able to send messages from the same message interfaces to different receivers in different send steps.
 3. Query the send context in a corresponding condition in the receiver determination in the Integration Directory.
I just don't get this; if I choose the character string myself, how do I use it in step 3? I cannot see any way to query the send context in a condition. Is the Send Context the name of the receiver?
If somebody can walk me through this step I would be very greatful!
Kind Regards,
Tony.

Tony,
An example
Integration Repository
I have a synchronous send step with the Send Context set to ABCDE
Integration Directory
In the Receiver Determination, Configured Receivers, enter the Condition Editor
Select Left Operand and enter the Expression Editor
Select the radio button for Context Object
Use the dropdown to select ProcessStep
Select OK
Select Right Operand and enter your value, eg ABCDE
Runtime
When I run my scenario an entry can be seen in SXMB_MONI corresponding to my send step. In my case it is displayed in the top Window
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......old attachment XI_Context found</Trace>
<Trace level="3" type="T">Append context with name =ProcessStep and value =ABCDE</Trace>
You can see here that the ProcessStep has the value ABCDE
Hope this helps

Reuse message after send step in integration process

Hi all,
I have a strange problem....
In my integration process, after some steps, I send a message asynch (in config an FTP receiver). After this I need to reuse the message just sent for a transformation, but the ip dumps. If I delete the send step, everything ends without error!
Is it possible that I cannot reuse a message after a send step? If so, why?
Thanks for any help...
Ilaria

> ReceiveTransformAToBSendBTransformBToCSendC
TransformAToB...ok
But in Step TransformBToC...you have to specify the Interface Mapping..it means
the Interface mapping should be between Outbound Interface for B and Inbound Interface C.
So u can store the B Abstract Message in the Container.
SO your BPM Look like this way...
StartReceiveTranAtoBSendToBContainerToStoreTheValueofBTranBtoCSendtoC--Stop
ContainerToStoreTheValueofB store the value of transformed message(that is B )
THen in TranBtoC (source=message stored in container and Target = C message)
I do hope it will work as per your requirement.
Thanks
Farooq.

SOAP to EMAIL and sending the response to SOAP by integration process

Hi,
I need to design a scenario from SOAP TO EMAIL and based on the status of the EMAIL being sent i need to send the response to SOAP using integration.If it is SUCCESSFUL message i need to send success and if the mail is not sent i need to send error .
could some one help how to design the Integration process for this scenario?will help me what steps i need to use for this .
Thanks
Rajesh

Hi Rajesh,
You can achieve this by making synchronous Interfaces.
1) create Synchronous Outbound and Inbound Service Interface.
2) So you will need to create a response mapping as well.
You get a response from mail adapter in the following format, use this as response Message Type:
- <xim:MailReceipt xmlns:xim="http://sap.com/xi/XI/Mail/30">
<Server>smtp://xx.xxx.xx.xx</Server>
<Greeting>wlg-exht2.XYZ.com Microsoft ESMTP MAIL Service ready at Fri, 28 Jan 2011 20:10:28 +1300</Greeting>
<Format>XIALL</Format>
<UseMailPackage>false</UseMailPackage>
<Encoding>base64</Encoding>
<Subject>Sync Test</Subject>
<From>"From e mail address</From>
<To>"To e mail address"</To>
<Date>2011-01-28T07:10:29Z</Date>
<MailID>1.2.3</MailID>
</xim:MailReceipt>
By this I think you can give the status of Mail.
Regards,
Aravind

Sending Email from Integration Process

I have an Integration Process created which looks at outbound messages and sends information to my alert inbox under certain conditions. Is it possible to take the text I am sending to the Alert Inbox and have this email me also, or does this process need to generate a new message which is routed through the email adapter?
Regards

Then Configure a Mail receiver adapter with the SMTP/IMAP address of your mail server and user authentcation and provide the recipient name in the TO address.
Check the HOW TO guides for MAIL adapter in Service market place for configuration details.
Best practice is to have a standard mail box configured on ur the Mail server to manage all sent mails.
oops missed out the stuff on CCBPM, Just add...a send step pointing to Mail service after the exception is trapped and Alert raised.

Send IDoc to R3 in Integration Process

Similar Messages

Maybe you are looking for