SAP SMS Configuration
- SCOT Configuration.
- HTTP Virtual host Configuration via SICF.
- Maintaining the Pager service.
- TCODE SPRO (in configuration client).
- Check the configuration by Composing a SMS.
- Monitor the queue using Tcode SCOT.
- Automating the process.
The pager/SMS messages can be transferred to the provider both via HTTP and also via (E)SMTP. This note relates to the HTTP channel. The SMTP channel is described in note 455140(455140 – Configuration of e-mail, fax, paging or SMS using SMTP). When e-mails are transferred using SMTP, the SAP Web Application Server communicates directly with a mail server. No gateway or connector is necessary.
You can use any SMTP-compatible product as a mail server.The first thing is a Basis configuration with third party SMS gateway provider. SMS from ECC SMS configuration needs to be done by Basis administrators. After if it successful can trigger SMS from the ABAP program directly.
The step by step procedure to configure SAP SMS though HTTP is as below.
Version : Net viewer version : 7.0
Provider : mobitel , Dialog (Sri Lanka)
1. SCOT Configuration
Go to T-code Scot
Then click PAG –> Then click on create button. Then provide HTTP for Node and give a description.
Continue à Select HTTP Node
continue –> Then provide the URL provided by the provider.
You can provide SAPconnect variables as you need.
Continue -> This screen will ask the password for the URL provided. If you give it on previous screen keep the password blank.
Provide the maximum length. Enter the maximum length (in bytes) that a SMS message can have.
Specify which text your provider returns in the status message (HTTP response) to indicate that:
a) The message was sent successfully
b) An error occurred
Specify the address area for which the node is to be responsible.
The node receives only those messages with recipient addresses that are within th enode address area, from the SAPconnect send process.Generic address areas can end or (only Internet addresses) begin with ‘*’.
Provide * on field address area.
Continue –> failed send attempt:
If a node cannot be reached currently because of a temporary error, the system tries to send the message again for a period of time that is specified individually for each node (at the earliest, after 10 minutes).
Specify the maximum time period for this repeat send attempt procedure (in hours and minutes).These values are initially set to zero
Continue –> Specify if the HTTP node is active.
A node that is not activated does not receive messages from the SAPconnect send process.
1. HTTP Virtual host Configuration via SICF
Then go to logon data and provide a user [better to use a service user.]
Then go to the handler list and provide following handers.
Then save it and activate it.
If your network environment has an proxy then provide the proxy setting to reach it to the given URL.
Proxy settings screen
Provide credentials in HTTP log tab.
OK – >
2. Maintaining the Pager service.
Use Tcode SA14 (The best practice is to go to 000 client and do this).
Provide detail as shown below – New Entry
Pager Serv: BAL
Use :SMS Service
Or use as follow.
3. TCODE SPRO (in configuration client)
Then provide following details
Pager serv : SMS
Pager service : SMS
Use : SMS Service
Now you are finished configuring the SMS though SAP.
4. Check the configuration by Composing a SMS
Go to T-code SBWP.
- –> Send and check the mobile.
5. Monitor the queue using Tcode SCOT.
Your composed sms can be seen on waiting queue.
Click on process icon on top to send it.
Then Start –>
6. Automating the process.
The SMS process can be automating though a background job.
It can be done by clicking on job icon in same screen. Then double click on the SAPCONNECT PAG SEND.
Then schedule the job
Would you like to access Full Article?
If you are already a member in this website, Please Click here to loginIf you are not yet a member, Please Click here to Sign up
New NetWeaver Information at SAP.com