Hi All,
When we reach a certain level of experience, we are expected to deliver the solution from scratch.
Have you ever faced any situation where you are given a very fresh BW system and asked to start with the initial configuration? At that point, this document would be handy in understanding those basic steps.
These days we have 2 broad landscapes available:
a) BW on Traditional data base
b) BW on HANA.
In this document, I will try to cover the concepts in General (Application layer) and some topics exclusively for BW on HANA systems will be added to this document at a later stage.The values mentioned in this series of documents must be considered for reference purpose only and should be finalized after having a detailed discussion with the client team.
Before starting the document, I would recommend you to go through the following wonderful documents written by our colleagues. I will try to cover only those points which are not mentioned in the below reference documents.
1) SAP BW 7.3 Configuration after installation of BW Part 1 --> http://scn.sap.com/docs/DOC-55967
2) SAP BW 7.3 Configuration after installation of BW Part 2 --> http://scn.sap.com/docs/DOC-55956
3) SAP BW Configuration – Basic System Settings --> http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30422873-8369-2d10-ddb5-e51635925...
So here we go....
1) Maintain and CHECK SOURCE SYSTEM CONNECTION:
Check RFC connection between BW-ECC/CRM/or any other systems in your landscape.
TCODE: RSA1 --> Source System --> Check.
Rectify the errors(if any). This step anyway might need your Basis help.
2) CHECK BICS CONNECTION BETWEEN BW AND BO USING A SERVICE USER
This Step is important if you have a BW-BO integration(BICS) in place.
Try using a service user here as it will avoid the confusions related to Passwords.
3) TRANSFER APPLICATION COMPONENT HIERARCHY(IN BW)
YES
TCODE: SPRO. Do the same steps in Source Sytems and BW.
In this step, we transfer and activate the application component hierarchy delivered by SAP. This is a one-time activity and only needs to be done once at the beginning. Do this is BW system also, as sometimes BW will act as a source system.
This will help the system to arrange all objects application components accordingly. Otherwise, replicated objects will go and collect under NODESCONNECTED
4) UNICODE:
Ensure that system is Unicode, else languages like Arabic will not work.
5) ARABIC LANGUAGE PACKS:(For Middle East Customers)
Ensure that Arabic language packs are installed.
TCODE: SMLT
6) TRANSPORT SETTINGS:
Set the Transport to Switch OFF Standard. So that the system does not prompt for package/req, every time a new object is created or edited.
7) POSTING MODE FOR MASTER DATA
TCODE: RSCUSTV9 --> Posting Mode for Master Data
By making this setting, if master data does not exist in the system, the corresponding entries are created.
For example – We have the InfoObject MATERIAL, which has the navigation attribute COLOR. We want to create a new entry in the master data maintenance MATERIAL 4711 with the color RED. The value RED is not yet available in the master data table of the navigation attribute COLOR. With this setting on Data records are updated. Navigation attribute values that do not exist are created. This ensures that master data attribute load does not stop because there are new attributes and the attribute load has not been completed yet.
😎 Tcode: SNRO
Maintain Proper Number Ranges.
9) THRESHOLD VALUE FOR DATA LOAD
TCODE: RSCUSTV6 --> Threshold Value for Data load
NOTE: The Values mentioned above is just some dummy values. Actual Values should be entered after discussing with the client team.
• The Frequency Status value controls after how many data IDocs an info IDoc is to be sent to the BI system. This enables a user to monitor the status of data loads online.
• The Package size contains the number of data records within a package that are delivered when you load data from the source system.
• Since we would be doing data loads using process chain mostly in background, the parameters can been set on a relatively higher side.
10) PROJECT SPECIFIC PACKAGES
Create Development package with project specific naming convention:
TCODE: SE21, SE80
11) ACTIVATING/DEACTIVATING PERSONALIZATION IN BEX
TCODE: RS_PERS_ACTIVATE
We use this activity to activate personalisation in BEx. The following have been activated
- BEx history, so that the last report you executed is saved.
- Variables, so that certain variables selected by you are proposed.
- Web applications, so that report drilldowns are saved.
12) INCREASE THE TIME OUT IN BW SERVER FOR DEVELOPMENT ACTIVITIES
During the development Phase, it would be a good idea to increase the timeout in BW system. This will avoid the developer to perform the activities without any timeout issues. Please ensure that it is set to standard/default values post the go live.
TCODE: RZ11 --> parameter name: rdisp/gui_auto_logout
13) CONTROL PARAMETERS FOR THE DATA TRANSFER.(IN SOURCE SYSTEMS)
The control parameters for data transfer have to be maintained in the source systems.
This is a manual activity and needs to be done manually in DEV, QA and PRD.
Path: Source system --> TCODE: SPRO --> IMG
Maintain the following entries:
Save the changes.
14) VERSIONING OF OBJECTS
TCODE: SPRO
Versioning is set for the required objects and is saved and moved to higher environments.
If you could go through the above mentioned points and reference documents, I believe you would be able to cover most of the important BW configuration steps.
Points exclusive to BW on HANA would be added to this document at a later stage.
Please refer to Roland's document for getting more information on this topic
--> SAP BW Installation/Configuration (also on HANA) --> http://scn.sap.com/docs/DOC-28504
Hope this document was helpful.
BR
Prabhith
- SAP Managed Tags:
2 Comments
