Is multiple recipients allowed for mail type workitem?

I have one "Send Mail" step in my workflow, I want to send the mail to multiple recipients, one of the recipient is &_WF_INITIATOR& the workflow initiator which is dynamically determined at runtime and other recipients &RECIPIENTS& of the mail are determined by application. So can I set the recipients of this "Mail" with expression like this:
&_WF_INITIATOR&;&RECIPIENTS&, split them with ";" like outlook?
Thanks for your answer.

Hi,
If I am not wrong, RECIPIENTS is a MULTI LINE CONTAINER ELEMENT which gets determined from the Application. Why dont you add your WF_INITIATOR logic also to that Application logic, so that RECIPIENTS contain the WF_INITIATOR also?
You cannot set Mail Expression as :&_WF_INITIATOR&;&RECIPIENTS&.
You can only set only one Container(single/multi line) Element for each mail step.
Regards,
Raja Sekhar

Similar Messages

How to select multiple recipients in iPad mail

I have read that I can't create groups, but how to select multiple recipients in iPad mail?
I was looking for this when setting up for two new people who are going to have the iPad as their only device.. and they do need to email a bunch of people at once..
I was sending out the 'I have a new email address' BCC for them.
Thanks.

You can select multiple contacts by tapping on the + sign in the upper right corner in the To: field when you are typing a new email. Just keep tapping the + sign and your contacts will pop up in a window. Select the contact that you want to add, repeat the process in order to add as many recipients as you want.
There are other mail apps that let you creat groups and email to those groups.
https://itunes.apple.com/us/app/group-email!-mail-client-attachments/id380690305 ?l=es&mt=8
https://itunes.apple.com/us/app/mailshot-pro-group-email-done/id445996226?mt=8
I am sure there are other, but those are two that I know of.

Too many recipients found for message type in the ALE model

Hello Friends,
Please help me in solving this error. I have a Outbound sales order confirmation ORDRSP .
In the distribution model i have defined the sender receiver and message type clearly...
But in va01 after creating sales order extras ->Output->Hearder --->Edit
Output type-- BA00
medium --ALE
Dispatch time : Send Immediately
I am getting a error -
Too many recipients found for message type ORDRSP in the ALE model
Message no. B1130
Diagnosis
In the ALE distribution customer model several recipient systems for IDOCs with message type ORDRSP and filter object type 'KUNNR' with value '100' have been modeled from this system, but only one recipient system is allowed.
Procedure
Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.
Please help me in solving this error.
Regards,
jeevan

Hi Jeevan,
In BD64, the said problem occurs, since the message type ORDRSP will be configured to different Logical System.
Since you are creating sales orders & Output type, system doesnt knows, to which Logical system, it has to be sent since the Message type exists more than once.
select Your respective Logical System where the Outbound Sales Order Confirmation ORDRSP has been created.
Under the node ORDRSP, add the filter group for Customer.
Double click the Filter group and add the respective Customer No.s to whom the Order confirmation needs to be sent.
Then create Sales Order Confirmation & Output type. Data will be passed(IDoc) to the respective Customer(where the customer no.) exist in the filter.
Hope it solves your Issues.
Regards,
Anbalagan.

How to have multiple preference files for Mail on one computer

I would like to have multiple preference files for Mail on one computer, one copy for each person in the organization. I want everybody to log in as the same user. Is this possible?
Thanks,
John Link
Cube, 450 MHz, 640 MB Mac OS X (10.3.9)

Since the Mail.app preference file (along with all other application preference files for a user account) is stored in that user's Home folder/directory, I don't believe this is possible.

Set type COMM_PR_UNIT is not allowed for product type

Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
Set type COMM_PR_UNIT is not allowed for product type
What can I do? I think that is an ABAP problem
Thanks in advance
Rosa Rodríguez

Rosa,
This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
Thanks,
Jagadish

Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'

Hi All,
I created the wsdl for mobile and I tried to send a SOAP request from Altova XMLSpy. However when I geive the wsdl in 'wsdl file location' I receive the following.
File http://127.0.0.1:8080/B1iXcellerator/exec/dummy/com.sap.b1i.vplatform.scenarios.setup/vPac.sap.B1Mobile/001sap0003_sap.B1Mobile.wsdl is not valid.
Invalid XML schema: 'Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'.'
Error location: wsdl:definitions / wsdl:types / xs:schema / xs:element / @type
Any Idea?
Vangelis

Hi,
it seems that Altove did not cope with defaultNs prefix that is used for marking default namespace.
just look up in your <xs:schema > tag what namespace prefix is used for your namespace - you shall find there something like this
<xs:schema xmlns:ns0="your.namespace.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
and replace prefix defaultNs with prefix of your namespace (in example above it would be ns0)
There might be several usages of defalutNs iside of WSDL (at least in my case were two) so replace it everywhere using same approach
Best regards, Artem

Transaction CLM1 not allowed for notification type QL

Hello guys,
one of our user try to open the transaction CLM1/CLM2/CLM3 he getting error message Transaction CLM1 not allowed for notification type QL
please any one give solution for this issue.
find the error screen shot for your reference.
Thanks
Surya

Hello Surya,
Have you done Basic configuration for Claims processing in SAP Project System.
SPRO > Project System > Claim > Notification - Claim > Notification creation
Also check config for Settings for Claims.
Refer sap help for more details
SAP Library - Claim Management
Regards
Tushar

Transaction QM03 not allowed for notification type MQ

HI Dears,
The following error is appearing when i want to view my notification created through defects
Transaction QM03 not allowed for notification type MQ
How to rectify it ?
Alagesan

Hi,
Check IQS3 transaction also....
Cheers,
Tushar

Too many recipients found for message type ORDERS in the ALE model

Hi all ,
please help me to solve this issue .
i done with ale settings .
orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

> orders message type is used in 2 different model view for 2 different systems
do both of them carter diffrent needs or is it the same idoc which is being sent to diffrent systems?
if yes, then use a single model view with noth receiver systems defined in it.
if not, i would suggest, copying the standard idoc and create a zidoc and then use different ones for diffrent receivers....
or u can use diff versions of the orders message type...
say orders05 for one.... receiver and orders02 for another one....
hope this helps!!
Cheers!!
Sidharth

ALE settings error "Too many recipients found for message type" urgent

Hi all ,
please help me to solve this issue !!!!!!!!
i done with ale settings .
in the bd64 , orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

Hi,
Try to redefine your distribution model to have both receivers of your message type ORDERS in one "model view".
Regards,
Jakub

Too many recipients found for message type (Distribution model)

Hi,
I wanna send Dilvery note using message type DESADV from a SAP system to another non-SAP System.
I have Created port partner profile and distribution model.
But the Problem is the same message type DESADV is used to send Dilvery from SAP System to another SAP Client.
Idoc getting failed and throwing error stating Too many recipients found for message type DESADV in the ALE model .
I am sure we can create the more than one recipients for same message types. I have done it some time back. Any help highly appreciated.
Regards
Raj

This message pops up when SAP can't identify how to distribute the IDoc based on the settings in BD64. Take a look at the settings there, most likely you'll need to add a filter.
The big ALE/EDI/IDoc book suggests that the same IDoc may be distributed to 2 different systems but specific details are not clear. It seems that one system should be configured first (it does mention a need to use a filter) and then somehow menu Edit -> Model View -> Distribute should be used.
I've never done it myself though and have only run into that error when I missed some filter settings in BD64. Hope this helps.

Status profile not allowed for object type

hi
i had created a status profile (for having 2 statuses before production order release) and assigned in the order type.
but while creating the production order i receive the following error.
Message no - CO622
status profile not allowed for object type
please provide your inputs
regards
Ramesh

Ramesh,
once you cerate a Status profile in BS02 and add status to the same. in the tollbar you will see OBJECT TYPE push button, select teh obejcts like PP/PM order header / operation /comepeoent and PRT ect where that staus can be applied.
Then assign the statsu profile to order type.

TS4498 I JUST, 9 July 13, bought Logic Pro... Any change Apple will allow for some type of upgrade to Pro X, since we had NO Fore Knowledge of its release...

I JUST, 9 July 13, bought Logic Pro... Any change Apple will allow for some type of upgrade to Pro X, since we had NO Fore Knowledge of its release...

I bought Logic Pro 9 a few days ago and they just sent me a response with a big NO! Twice! so far!
see this threads:
https://discussions.apple.com/message/22496383#22496383
https://discussions.apple.com/message/22490113#22490113
https://discussions.apple.com/message/22490862#22490862
https://discussions.apple.com/message/22500131#22500131
https://discussions.apple.com/message/22494804#22494804
This is no way to treat your customers.

Invalid rights for existing type: workitem

Hi,
Yesterday I installed the SP1 for idm 6.0.
Since then i'm getting a WavesetException printout for "invalid rights for existing type: workitem" when I call: Server.getServer().
Has anyone expierenced the same problem or perhaps know how to avoid the exception?
regards
Kevin

I'm getting the exception everywhere now.
Did I do something wrong in the installation perhaps?
When I start the BPE I get the exception, also for the lh console.

The default account option in iOS for contacts is missing; while I have multiple account options for mail and contacts are turned on for iCloud and other accounts.

The default account option in iOS for contacts is missing; while I have multiple account options for mail and contacts are turned on for iCloud and other accounts. I previously was able to select between my Microsoft Exchange Contacts (work account) and iCloud (personal), but both those options are now gone. I tried turning contacts for both off and on and rebooting, but it didn't help. Any ideas?

Just a guess but if the exchange account is from your employer, your employer may have installed a security profile to your device preventing you from adding or editing contacts in the exchange account by removing the Default Account setting. You would need to check with your employer's IT department to confirm this. You could also test this by adding a Gmail account and turning on contacts syncing with Gmail to see if the setting reappears.

Is multiple recipients allowed for mail type workitem?

Similar Messages

Maybe you are looking for