Send Context in BPM

hi,
I have more than 2 conditions in the SWITCH condition in BPM.
For each SWITCH condition i have a SEND step inside.
Branch 1 -> Send 1
Branch 2 -> Send 2 ...
Idea is once the condition is satisifed in the SWITCH condition, using the <b>SEND CONTEXT</b> in the SEND step i will try to use this SEND CONTEXT in my receiver determination.
It seems like it doesn't like the SEND within the SWITCH.
Any other ways?
Thanks,
Tirumal

Hi
When you use Receiver determination step in BPM to get a list of receivers for a send step.
You need to define send context to send messages from the same interface to different receivers in different send steps. As list of receivers is collected using receiver determination.
Now you can use this to set condition(send context) based receiver in ID Receiver determination.
Thanks
Gaurav

Similar Messages

Regarding send step in bpm--"send context"

i want to use the send step in my bpm with send context.
The send context is a freely definable string, which you specify in the send step. You query the send context in a condition in the receiver determination in the Integration Directory. You must specify the send context to be able to send messages from the same message interfaces to different receivers in different send steps.
but i did n't understand regarding the explanation given above.
could u plz help me out

Hi
When you use Receiver determination step in BPM to get a list of receivers for a send step.
You need to define send context to send messages from the same interface to different receivers in different send steps. As list of receivers is collected using receiver determination.
Now you can use this to set condition(send context) based receiver in ID Receiver determination.
Thanks
Gaurav

Receiver determination step - Send context

Hi Experts,
I have understood from SAP library and others threads that send context in the receiver determination step is used to send value for the conditions we have added in ther receiver determination and fetch only receivers those satisfy the cretiria.
Please validate whether my understand is right or not?
If its correct, then my question is can we populate this value dyanmically, say field value from another message.
Please clarify.
Thanks,
Kar

Check if the below link is of any interest to you:
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
From the link:
Condition: when the AirlineID field in the message payload has the value LH, then the message is
forwarded to the receiver business system BUS_100. A context object of the same name from the ES
Repository is used to access the AirlineID field in the message.
It talks about normal receiver determination as against the receiver determination step (of BPM) which you want....

How to determine receivers in the send step in BPM?

Hi Guys,
I have 3 send steps in BPM defined with send context and for each send step i have defined a receiver determination in ID. Each Receiver Determination has a condition based on which identifies multiple receivers.
The BPM is failing and unable to determine the conditional routing. Do i need to add the receiver determination step before each send step so that it identifies the receivers.
Any help would be appreciated.
Thanks,
Raj

Hi Guys,
Thanks for all of you for the quick replies and it is really a great help.
We have resolved the issue. The approach is as below.
we have a generic design used by multiple customers. For the interface where we have the BPM, we are doing conditional routing for each customer before they hit the BPM that is as soon as we receive the Asynchronus request based on the condition we direct the message to a particular BPM. Basically every customer will have different BPM process. ie we create the same BPM with different names specific to each customer and in this way we dont complicate the BPM process and we will know if any particular customer has problems with his process.
Please let me know comments or suggestions on the above approach
Thanks,
Raj

Send Message in BPM gets "logically deleted"

Hi everybody,
we got a message split in BPM. The singel messages are send through "send context".
Strange:
In SXMB_MONI_BPE the message gets logically deleted.
And in SXMB_MONI the BPM does not send the message to the configured receiver.
The message is send back to the process !?
Any suggestions?
Thanks a lot
Regards Mario

The required number in the fork was wrong!

How to use send context in ccBPM

Hello,
I am trying my first BPM process. I am using the send step while I need to specify the receiver using send context. The value of the send context should be:
The send context is a freely definable string, which you specify in the send step. You query the send context in a condition in the receiver determination in the Integration Directory. You must specify the send context to be able to send messages from the same message interfaces to different receivers in different send steps.
My questions is how to query the send context in condition of the receiver determination (RD). The condition of RD is basically variable operator value, while variable could be field of the payload or context object. I don't see how to query the send context in a RD condition. Can somebody explain it?
Thanks
Jayson

Hi Jayson
You must specify the send context to be able to send messages from the same interface to different receivers in different send steps.
Check this
http://help.sap.com/saphelp_nw04/helpdata/en/11/13283fd0ca8443e10000000a114084/content.htm
Thanks
Gaurav

Send context - Urgent

Hi,
We are using a send context to send message from one BPM to another BPM in XI.
I know that we can use any arbitary name as the send context.
But whats the meaning of giving the special charcter ' * '.
SW015_TO_SW007*.
Thanks,
John

Hi,
>>SW015_TO_SW007*.
It might be possible that in the configuration part there are more then one configured receiver.
SW015_TO_SW007_AAA
SW015_TO_SW007_BBB
SW015_TO_SW007_CCC
Thanks
Farooq

How to query send context of ccBPM in IR?

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.
My question is, the send context is not a part of the payload of xml, how to query the send context in IR?
Thanks in advance.

Hi YiNing Mao,
   Were you able to solve the problem?
   I am also facing a similar issue where i have to receiver determination with condition ProcessStep = ASNtoAII. ASNtoAII is defined as send context in IR in the BPM.
   What is the right way to give the condition
1. In concerned receiver determination for the receiver service you give this condition
2. when we select the condition do we need to select XPATH node or the other node to give condition ProcessStep in left operand.
3. Do we need to give the send context against ProcessStep as ASNtoAII or 'ASNtoAII' ? The difference between two is one is without quotes other is with quotes.
Looking forward to help from you.
Thanks and regards,
Amit Deshpande

Fault message in synchronous send step in BPM

Hi,
When executing a synchronous send step in BPM it is possible to handle application errors (fault messages) with an exception branch. But how do you get hold of the actual data in the Fault message(faultText, faultURL, faultDetail etc) for further processing (mapping)?
Kind regards Johan

Johan,
u have to define another container element in integration process.
For that container element an Async Abstract interface has to created with falult message as the message.
Do u have the fault message defined already...
Also go through this thread.
Fault message handling in BPM
-Naveen.

Send step in BPM is "logical deleted"

Hi everybody,
we are sending IDOCs from BPM to receiver determination (R/3 Backend).
The BPM protocol marks the send step as "logically deleted".
In SXMB_MONI strange!
Sender = Receiver = BPM
Any ideas?
Regards Mario

The required number in the fork was wrong!

Transport Acknowledgement in an Ansynchronous Send Step in BPM

I tried this scenario /people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments for a file acknowledgement in an ansynchronous send step in BPM and it worked fine.
This made me think of something else...
This SAP help site http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm
says - for a "Permanent negative acknowledgment" the "Send step triggers system error for which you can define a specific exception handling."
I understood this as saying "If the tartget file is not placed, a system error is thrown for which we can write our own exception handling"
In the scenario explained in the blog the 'deadline branch' was made to wait for a few miutes and once exceeded, made to throw an exception "NegAck" which is handled in the "Exception handler branch"
So what i tried was, I removed the 'deadline branch' and retained only the 'exception handler branch' and made the 'send step' to throw a system error "NegAck" so that if the "Send Step" recieves a negative acknowledgement, it would throw this error "NegAck" which I have handled in the "Exception Handler Branch"
However, this did not work. Can anyone kindly explain where was my mistake?

Dear Bharath,
hmmm nice question...
The answer to this is....whenever you configure a async send step with "transport ack" it will never go into error..
the send step will either get a positive ack(if the file reaches correctly) or a negative ack(if there is some problem like password expires) but it will will never go into error and hence directly the control will never go to exception handler block...
consider the cases :
1. Async send step with transport ack and file reaches correctly : +ve ack is generated and BPM will stop
2. Async send step with transport ack and passowrd expires : the send step will not go in error but you will get error in adapter engine(RWB) so it will keep on restarting and corresponding negative ack will keep on getting generated but here also the send step has not gone to error but the message in AE has gone into error and hence control will not pass directly to exception handler block....what you can do is keep a timelimit thru deadline branch so that after that much time control goes to exception branch...
This should solve your problem...
do not forget to close the thread marking useful answers after your query is resolved
Edited by: Tarang Shah on Mar 30, 2009 4:10 PM

Were can i see synchronous send in the BPM editor

were can i see synchronous send in the BPM editor
i can see the send and receive ast the left top
but could nt find out synchronous send

Hi,
When u select Send step, it is by default selected as Asynchronous. U may deselect it and select Synchronous there in the same step (Properties Window on right)
Regards,
Prateek

Getting Error : Exception sending context initialized event to listener

I am using JWSDP1.2 and tomcat that's bundled with it.
I am trying out a simple jsf appln very similar to the "Usernamebean" example.Each time i deploy my war file and try to access my webapp, i get the following error in tomcat's log. Driving me nuts !
Jun 12, 2003 12:23:04 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /finaljsf from URL jar:file:/C:/jwsdp-1.2/webapps/finaljsf.war!/
Jun 12, 2003 12:23:05 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigListener
javax.faces.FacesException: javax.faces.application.ApplicationFactory
     at javax.faces.FactoryFinder.getImplementationName(FactoryFinder.java:400)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:203)
     at com.sun.faces.config.ConfigParser.parseConfig(ConfigParser.java:91)
     at com.sun.faces.config.ConfigListener.contextInitialized(ConfigListener.java:127)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3670)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4106)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:843)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:827)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:623)
     at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:315)
     at org.apache.catalina.core.StandardHost.install(StandardHost.java:837)
     at org.apache.catalina.manager.ManagerServlet.install(ManagerServlet.java:712)
     at org.apache.catalina.manager.HTMLManagerServlet.install(HTMLManagerServlet.java:306

I was using an older version of tiles.jar. Hence the error. Started working after I moved to the latest version of struts.jar

SEVERE: Exception sending context initialized event to listener instance

Hi,
I am seeing the following error when trying to deploy my war file using tomcat 6.0.18. War file is built with JSF 1.2 and Java 1.6.0_12. Could anyone please let me know what could be the reason.
Thanks.
Jun 12, 2009 3:09:37 PM com.sun.faces.config.ConfigureListener contextInitialized
WARNING: JSF1059: WARNING! The com.sun.faces.verifyObjects feature is to aid developers not using tools. It shouldn''t be enabled if using an IDE, or if this application is being deployed for production as it will impact application start times.
Jun 12, 2009 3:09:37 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
     at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:213)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
     at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
     at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
     at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
     at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
     at org.apache.catalina.core.StandardService.start(StandardService.java:516)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.xml.sax.SAXParseException: cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1951)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685)
     at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:273)
     at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:240)
     at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:186)
     at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:100)
     at javax.xml.validation.Validator.validate(Validator.java:127)
     at com.sun.faces.config.ConfigManager$ParseTask.getDocument(ConfigManager.java:434)
     at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:394)
     at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:351)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:619)

More logs:
Jun 12, 2009 3:09:37 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
     at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:213)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
     at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
     at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
     at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
     at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
     at org.apache.catalina.core.StandardService.start(StandardService.java:516)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.xml.sax.SAXParseException: cvc-elt.2: The value of {abstract} in the element declaration for 'faces-config' must be false.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1951)
     at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685)
     at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:273)
     at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:240)
     at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:186)
     at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:100)
     at javax.xml.validation.Validator.validate(Validator.java:127)
     at com.sun.faces.config.ConfigManager$ParseTask.getDocument(ConfigManager.java:434)
     at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:394)
     at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:351)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:619)

How to start a "File Sender" in a BPM?

Hi Experts,
Is there a way to start/trigger a File sender from a BPM i.e start it from the BPM? Or even trigger a Communication channel in a BPM?
The scenario is as follows:
We need to trigger the File Sender only when XI receives an IDoc from SAP.
Many thanks in advance.
Regards,
Tush

Thanks Prateek,
Okay let me explain the full scenario, as follows:
- IDoc sent to XI -> A file is created in the FTP
- IDoc is triggered through Change pointers and sent to XI
- Then, we should check the lines (records) of the file(currently in FTP) for the Material number in the IDoc.
-If the material number is already in the file, replace that record.
-If the material number is not yet in the file, add a new record.
Can you please suggest a way in achiving this?
Many thanks for your help.
Best regards,
Tush

Send Context in BPM

Similar Messages

Maybe you are looking for