Content Inside :
Typographic Conventions : Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Technical System Landscape : The following graphics illustrate the important components that are used when SAP BW is implemented and the communication between these components. Technical system landscape for SAP BW without external data sources, User Administration and Authentication SAP BW uses the user management delivered for SAP NetWeaver application platforms ABAP and Java (see the tables on user administration tools under User Management [SAP NetWeaver Security Guide]. Authentication
SAP NetWeaver supports various authentication mechanisms. SAP BW uses a user ID and a password for logon. SAP logon tickets
SAP BW supports SAP logon tickets. To make Single Sign-On available for several systems, users can issue themselves an SAP logon ticket after they have authenticated themselves with the SAP system. Security with Data Storage. Communication Destinations Connection destinations are particularly important in SAP BW for connecting data sources to SAP BW. These destinations are usually not delivered but are created by customers. If you want to connect SAP systems and non-SAP data sources as source systems to SAP BW, you usually need RFC destinations.
Tags : sap business information warehouse, sap bw, business information warehouse, sap logon, external data sources, authentication mechanisms, sap systems, sap system, system landscape, typographic conventions, application platforms, screen titles, warehouse security, menu paths, sap netweaver
If you see unrelated pdf files with the description or copyrighted material published, please report to us, we'll correct/delete it it as soon as possible.NONE OF THOSE MATERIALS ARE HOSTED IN THIS SERVER NOR UPLOADED BY ME IN SOMEONE'S SERVERS. Read our DISCLAIMER for more detail.
We are neither affiliated with authors and brands nor responsible for its content and change of content.
Information contained herein is provided "as is" without warranty of any kind, either expressed or implied, including any warranty of merchantability or fitness for a particular purpose. In no event shall ANYONE be held liable for any loss of profit, special, incidental, consequential, or other similar claims.