This post describes generic standards and guidelines that apply to the use of standard BI objects delivered by SAP as part of the BI business content. Again, these may change as per your client’s BW system standards.
Activating Business Content
Anyone with access to the sandbox may activate business content there. If you activate content in sandbox, make sure that you do not activate the content in the background (batch mode.) Instead, activate the content in the foreground and always keep any existing customization for the objects you activate.
No one except the people allowed may activate business content in SAP BW development system.
If you need business content activated, contact one of those people and explain what you need activated.
General Standards and SAP Business Content – Summary
- No objects in development system may reside in the $TMP package (development class).
- All queries must run against a MultiProvider, unless you intend to use a large number of business content workbooks or web templates that reference business content queries.
- Your solution must include an Enterprise Data Warehouse level, implemented as a first level DSO, unless SAP has configured the business content extractor so that it cannot write to a DSO.
- You must partition all InfoCubes.
- You must turn off the BEx Reporting (Generate SIDs) flag on DSO’s unless you intend to run reports against them.
Business Content Configuration
We use SAP business content to save time and money. Instead of building and maintaining solutions ourselves, we take advantage of solutions that SAP has built and maintains.
The following standards apply when using SAP business content objects:
- MultiProviders for Queries – If your solution does not use SAP delivered web templates, and then you must adhere to the standard that requires every query to run against a MultiProvider. Activate the queries from business content, create a MultiProvider, and then copy the queries to the MultiProvider using transaction RSZC.
If you intend to use a large number of business content web templates that reference business content queries, then you do not have to copy the queries to run against a MultiProvider.
- Line Item Dimensions – If an SAP delivered InfoCube does not have a line item dimension, you do not have to remodel the cube to include one.
- Naming Standards – You may use SAP business content objects as delivered, without copying them to conform to client naming standards.
- Enterprise Data Warehouse Level – If an SAP business content solution does not include an unfiltered data warehouse layer implemented in DataStore Objects, you must add one (unless this proves technically infeasible due the nature of the extractors provided.)
- ABAP in Transformation Routines – You do not have to implement SAP delivered ABAP routines as INCLUDE modules. If, however, you choose to make changes to an SAP delivered ABAP transformation routine, then you must implement it as an INCLUDE.
- Process Chain Standards – All client process chain standards apply to business content process chains. For example, you must modify SAP business content process chains to notify support teams of their failure.
You must also add PSA deletion and Change Log deletion processes to SAP business content process chains where necessary to conform to your client standards.
Courtesy: SAP help and Project Documents