Process Management

Process management in SAP BW includes the following areas:

  • Administration of the loading process You can find more information under Scheduler and InfoPackage Group. 
  • Monitoring the loading process and processing of data requests in SAP BW You can find more information under Monitor. 
  • Managing Data Targets
  • Process Control We recommend that you use Process Chains for automated process control in SAP BW.
  • Data Archiving
Data Warehouse Management

For management of most Data Warehouse Management processes, the Administrator Workbench of SAP is the central entry point. It provides tools and functions for metadata and process management. Data Warehouse Management in SAP BW incorporates various tools and functions:

Process management
With the help of functions and tools for process management, you can: manage and monitor both loading processes and as further processing of data in SAP BW, manage data targets, control processes in SAP BW centrally and automatically and archive data.

Authorizations
An authorization is the empowerment to carry out a certain activity in the Business Information Warehouse. Each authorization refers to an authorization object and defines one or more values for each field that is contained in the authorization object. Individual authorizations are summarized into authorization profiles by system administration. You can copy the roles delivered by SAP and adjust them when you want. The system administrator creates these authorizations and enters them into individual users' master records in the form of profiles. The authorizations in the SAP BW are based on the standard SAP authorization concept.

Documents and texts for BW objects
Information on BW objects (metadata, master data, InfoProvider data) can be managed in the form of documents. In Reporting, documents can be created, displayed and found using full- text search. In the Documents function area of the Administrator Workbench, in addition to the functions for creating, importing and exporting documents and searching within documents, there are also functions for the administration of the BW document management. In the Translation function area of the Administrator Workbench, you can translate short and long texts for BW objects.

Transport of BW objects and delivery of content objects
Transport system: 
Development projects for the Business Information Warehouse are usually not implemented in a productive system, but in a system landscape with one or more development and test systems. Using the transport connection, you can collect newly created or changed BW objects in the respective development system and then transport it into the required target system - usually a test or productive system) using the Change and Transport Organizer (CTO). 

The concept of transporting and using SAP objects in various versions, which is used in the transport system, is also relevant for delivery and use of SAP Business Content. SAP delivers Business Content in the SAP Delivery Version (D version).  During installation or import of the delivered Business Content, modified or active objects are thus not changed. During import of customer transports into the target system, the objects are imported either directly into the active version (A version) or into a modified version (M version). Customer- specific changes are also saved in the modified version (M version). In order to be able to use the Business Content that has been delivered or changed according to customer specifications, a customer has to convert the desired objects to an active version (A version). The Install Business Content function area of the Administrator Workbench allows you to select (or “collect”) the objects from Business Content supplied by SAP and to activate (or “install”) them.  While doing this, the customer can determine which objects from Business Content he wants to copy, compare with customer-specific modified objects or those that he does not want to install The system automatically considers all necessary objects as well as the sequence of their activation. 

Content that the customer or a consulting partner for the SAP Business Information Warehouse delivers to his business areas or customers himself is called Customer- and Partner Content. The functionality of the customer or partner content expands and enhances the possibilities of use for the Business Content delivered by SAP.

BW statistics and analysis of BW objects and data consistency
In addition to Business Content, SAP also delivers Technical Content. On the one hand, this includes objects that allow you to analyze the processes in the BW system and to optimize them for performance (BW statistics, BW data slices, BW features characteristics) On the other hand, technical content also includes special ODS objects in which data is provided, for example for BEx personalization or for the generation of reporting authorizations. 

BW Statistics provides data for Reporting from the data warehousing (warehouse management) and OLAP areas from several BW statistic InfoCubes via a BW Statistic MultiProvider Within technical content, appropriate BW statistic queries and diagrams are also supplied for the evaluation of data. 

For consistency checks of data and metadata stored in a BW system, SAP BW provides an extensive Analysis and Repair Environment.

Comments

Post a Comment

Popular posts from this blog

SAP Datasphere Data Integration - Part 1 - Introduction and Integration using Remote Tables

Image
SAP Datasphere provides a large set of default connections to access data from a wide range of sources, source from SAP as well as non-SAP sources or partner tools, residing in an cloud as well as on-premise environment. Connections are defined in a separate view which can be found in the main navigation window of the left. Connections are individual objects in SAP Datasphere. They are created and maintained per SAP Datasphere Space which means only members of a specific Space are able to make use of the related connections. These connections can be then be used within the different tools (like SQL View Builder, Graphical View Builder or Data Flow) for creating your data models. SAP Datasphere can integrate with both SAP or Non-SAP Source systems and it can be either cloud or on-premise. We have multiple connection types in SAP Datasphere. Each connection type supports a defined set of features. Depending on the connection type and the connection configuration, a connection can be used...
Read more

SAP Datasphere - Data Integration - Part 2 - Data Integration based on Data Flows and External Sources

Image
Data Integration based on Data Flows: A Data Flow is used as per SAP Definition “to move and transform data in an intuitive graphical interface”. The Data Flow is created within the part of the Data Builder in SAP Datasphere, and it currently supports the following operators to be used within your transformation process:  Join Operator  Union Operator  Projection Operator  Aggregation Operator  Script Operator  As we are coming from a strong Business Warehouse background, we are always comparing things to the past. Which in our case would be a classical SAP BW on HANA or SAP BW/4HANA. We currently see the Data Flow as a substitute for what used to be in a BW system the transformation.   In the data flows, we will be able to use a series of standard transformations without the need of programming knowledge and in a graphic way, but we also have the possibility of creating transformations based on scripts. In a data flow, we will use views or tables...
Read more

SAP Datasphere - Data Builder types and creation of Tables

Image
 There are different artifacts available in the Data Builder as below. Table Graphical View SQL View Entity-Relationship model Analytic model Data Flow Replication Flow Transformation Flow Intelligent Lookup Task Chain Now lets discuss on them in detail. Tables: Column structure of the tables can be defined either manually or by using the existing data as template. These are going to get the information from different source systems like flat file / sap / non-sap and can be filled with data from a CSV file or via a data flow. While creating a table we can define the following: Technical and Business names Data Type Semantic Usage Label Column Primary Keys Default values  can be/not null Visibility of the columns We can also delete current data and upload new data from files and share the current table with other spaces. Hierarchies could be created and the generated CSN annotations could be edited in order to make it synchronize with the expecting changes. Lets discuss th...
Read more