SMS Through Workflow

Wed Dec 5 06:32:37 EST 2007

Hi,

I have following queries:
1. Please explain me about the service provider, i mean do we need to have a
service provider who allow us to use there services.
    More explaination with example will be helpful.

2. While sending message do we need any specific authorization.
3. Is there any specific format of receipent ID and all?
4. Can we send Local/National/Internaltional SMSes?
5. Can you provide me any sample code in ABAP.

Thanks,
JM

On Dec 5, 2007 4:30 PM, רונן פוקס <ronenf at paz.co.il> wrote:

>  Hi,
>
> The steps for configuring SCOT depends on your SMS service provider.
>
> The system needs some sort of an external service in order to be able to
> send outgoing SMS messages.
> Once you set up an account with the service provider, the node at
> transaction SCOT should look something like this:
>
>
>
> I hope this helps. You are welcome to ask further questions.
> Thanks,
> Ronen
>
>  -----Original Message-----
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *JITU MOHAN
> *Sent:* Wednesday, December 05, 2007 12:47 PM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: SMS Through Workflow
>
> Hi Ronen,
>
> The steps provided by you are very useful, could you provide me the steps
> for configuring SCOT for SMS/Pager.
>
> Thanks in advance...
>
> Warm Regards, JM
> On Dec 5, 2007 10:32 AM, רונן פוקס <ronenf at paz.co.il> wrote:
>
> >  Hello David,
> >
> > We have a workflow sending out SMS messages.
> >
> > The way it is set up is as follows:
> >
> > 1. Maintain the mobile number either in the person or the user master
> > data
> > 2. Create a method or an attribute to read that number from the master
> > data record.
> > 3. Create a method for sending the message based on
> > SO_DOCUMENT_SEND_API1 function module. Be sure to pass the parameter
> > sender_address_type        = 'B'
> > 4. Your message is sent via the SCOT mechanism
> >
> > Of course you have to set up in transaction the option to send SMS via
> > the PAG node. We did it with an external service provider that receives an
> > http string from us.
> >
> > It works very good for us (hundreds of messages each day)
> >
> > Good luck !
> >
> > Ronen
> >
> >  -----Original Message-----
> > *From:* sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu] *On
> > Behalf Of *Sudhir Pargaonkar
> > *Sent:* Tuesday, December 04, 2007 6:54 PM
> > *To:* SAP Workflow Users' Group
> > *Subject:* Re: SMS Through Workflow
> >
> > Hi David,
> >
> > I have done it before. Every mobile number has its own email address.
> > You can get it from mobile career. (for example tmobile has :1234567890 at tmomail.com
> > ).
> >
> > Just use send email step to send message to this address. Make sure to
> > keep number of characters limited as per max length of SMS.
> >
> > Regards,
> > Sudhir
> >
> > On Dec 4, 2007 10:38 AM, Bibby, David < david.bibby at linklaters.com>
> > wrote:
> >
> > >  Hi,
> > > Has anyone ever managed to send SMS messages from a workflow?
> > > I believe this is possible reading the SAPConnect documentation on
> > > help.sap.com.
> > >
> > > If so can anyone tell me how this is done?
> > > I have a requirement that when a new project (BUS2001) is released
> > > that we get the mobile number of the project manager from SAP HR and SMS
> > > them to let them know it has been released.
> > >
> > > Many Thanks
> > > David
> > >
> > > _______________________________________________
> > >
> > > This communication, issued by Linklaters LLP or one of its affiliated
> > > firms or other entities carrying on business under or including the name
> > > 'Linklaters' (together "Linklaters"), is confidential and may be privileged
> > > or otherwise protected by work product immunity. If you have received it by
> > > mistake please let us know by reply and then delete it from your system; you
> > > should not copy it or disclose its contents to anyone. All messages sent to
> > > and from Linklaters may be monitored to ensure compliance with internal
> > > policies and to protect our business. Emails are not secure and cannot be
> > > guaranteed to be error free as they can be intercepted, amended, lost or
> > > destroyed, or contain viruses. Anyone who communicates with us by email is
> > > taken to accept these risks.
> > >
> > > Linklaters LLP is a limited liability partnership registered in
> > > England and Wales with registered number OC326345. It is a law firm
> > > regulated by the Solicitors Regulation Authority (see www.sra.org.uk).
> > > The term partner in relation to Linklaters LLP is used to refer to a member
> > > of Linklaters LLP or an employee or consultant of Linklaters LLP or any of
> > > its affiliated firms or entities with equivalent standing and
> > > qualifications. A list of the names of the members of Linklaters LLP
> > > together with a list of those non-members who are designated as partners and
> > > their professional qualifications is open to inspection at its registered
> > > office, One Silk Street, London EC2Y 8HQ or on www.linklaters.com. and
> > > such persons are either solicitors, registered foreign lawyers or European
> > > lawyers.
> > >
> > > Linklaters LLP has taken over the greater part of the practice of
> > > Linklaters the general partnership. For information about this conversion,
> > > including any transfer of your information, and other important information
> > > on our regulatory position, please refer to *
> > > www.linklaters.com/regulation*.
> > >
> > >
> > >
> > > _______________________________________________
> > > SAP-WUG mailing list
> > > SAP-WUG at mit.edu
> > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > >
> > >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> >
>
>
> --
> Thanks & Regards,
> Jitu Mohan
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>

-- 
Thanks & Regards,
Jitu Mohan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071205/54674089/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/bmp
Size: 1764774 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20071205/54674089/attachment.bin