Information Broadcasting Part 1 System Parameter Setting Applies to: SAP BW 3.5 Summary This article covers the information broadcasting (IB) setup process. Starting with system parameters, then different transaction settings and lastly how to use IB (I will be covering transactions settings and how to schedule reports and workbooks in sequel to this article). I have tried to be as detailed as possible with all the information that I have collected and tried. Author: Purvang Zinzuwadia Company: Patni Computer Systems Ltd Created on: 24 January 2008 Author Bio Purvang Zinzuwadia is working with Patni for the last 1.5 years. He is currently working on SAP-BW 3.5 and BI 7.0. he also worked on different areas in BW like modeling, reporting, production support, ETL process, and also tried some new things like information broadcasting. 2008 SAP AG 1
Table of Contents Introduction...3 1. Set Profile Parameters (Tx : RZ10)...3 2. User Maintenance (Tx: SU01)...3 a. Service user...3 b. User addresses...3 3. Assigning the client (Tx: SICF)...4 a. Host Data...4 b. Service Data...4 c. Handler List...5 4. SAP connect Administration (Tx: SCOT)...6 a. Default Domain...6 b. Nodes...6 5. Send Job Configuration (Tx SCOT)...7 Related Content...10 Disclaimer and Liability Notice...11 2008 SAP AG 2
Introduction This article covers the information broadcasting (IB) setup process. Starting with system parameters, then different transaction settings and lastly how to use IB (I will be covering transactions settings and how to schedule reports and workbooks in sequel to this article). I have tried to be as detailed as possible with all the information that I have collected and tried. 1. Set Profile Parameters (Tx : RZ10) 1. icm/server_port_<*> = PROT=SMTP,PORT=<port> This parameter opens a TCP/IP port for receiving mails through the SMTP plug-in. <port> describes the number of the port that is to be used. Optionally, you can use TIMEOUT to define a maximum waiting time (in seconds) To be applied until the mail server responds. 2. is/smtp/virt_host_<*> = <host>:<port>,<port>,...; This parameter defines a virtual mail host for receiving mails. In this instance, is/smtp/virt_host_0 = *:25; is used by default. If multiple clients are to be used as recipients, a virtual host has to be created for each of these clients. <host> describes the name of the host to which incoming mails are addressed. You can enter * here if the mails are to be sent independently of the host being addressed. <port> describes the number of the port to which the incoming mails are addressed. 2. User Maintenance (Tx: SU01) a. Service user It is required for processing incoming mails in every SAP system 1. Create a user with type Service/Communication 2. Assign the profile S_A.SCON and communication method as Remote Mail b. User addresses Every user that is to receive e-mails in an SAP system requires an Internet mail address. (If username is used at the time of broadcast) This is also used as a sender address. Specify mail address for a user, under E-Mail on the tab page Address. 2008 SAP AG 3
3. Assigning the client (Tx: SICF) Every SAP system client that is to receive and process incoming mails must have an SMTP server. One SMTP server (SAPconnect) has already been created in transaction SICF and is delivered with every SAP system. Use this to configure the following settings on the SMTP server (double click on SAPconnect, a popup window will appear, it will have following tabs) a. Host Data Enter the sequence number of a parameter is/smtp/virt_host_<*> from the profile. b. Service Data Enter the client and System User logon information for the incoming mails 2008 SAP AG 4
c. Handler List Enter CL_SMTP_EXT_SAPCONNECT at position 1. Note that each SMTP server must be activated (Service/Virt. Host -> Activate) after being created or changed. Inactive servers are grayed out. 2008 SAP AG 5
4. SAP connect Administration (Tx: SCOT) a. Default Domain Under Settings -> Default Domain, define the domain of the SAP system client. b. Nodes Each client has an SMTP node. This node is created by the SAP system and cannot be deleted. Follow the below steps to configure the node to send Internet mail. 1. Make sure you are in the Node view. 2. Double-click the node name. Choose Node in use 3. In the Mail Host and Mail Port fields, specify the mail server to which the outbound mails are to be sent. 4. Next to Internet, choose Set Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all e-mails are to be sent using SMTP. 2008 SAP AG 6
5. Enter the output format for SAP documents as shown. 6. Confirm your selections 5. Send Job Configuration (Tx SCOT) E-mails sent from an SAP application are first stored in a queue. A periodical background process, the SAPconnect send job, gets the e-mails from this queue and sends them over the Internet. To schedule this job in SAPconnect: Administration (SCOT), proceed as follows a. Choose View -> Jobs. (To go back, View -> System Status) 2008 SAP AG 7
b. If no other job has been scheduled, choose Job -> Create. c. Enter a job name and confirm. d. Select the variant SAP&CONNECTALL by positioning the cursor on it. e. Choose Schedule Job. f. Choose Schedule periodically. g. Select the interval you require, such as 5 or 10 minutes. h. Choose Create. i. Jobs will start executing as per the set interval. 2008 SAP AG 8
2008 SAP AG 9
Related Content http://help.sap.com/saphelp_nw04/helpdata/en/ef/4c0b40c6c01961e10000000a155106/frameset.htm 2008 SAP AG 10
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2008 SAP AG 11