Data Insights in BODS– INFORMATION STEWARD

Data Insight is used to do the DHA (Data Health Assessment) on the data i.e. to see if the data is good to use. You use the tool data Insight to do a test / profiling on the data before we use the data for the ETL process. You can also say that Insight is used to do data investigation. It automates the analysis and monitors the data.

Using Data Insight we can perform the following tasks-

  • Data Profiling
  • Column query
  • Integrity test and Custom query
  • Scheduling
  • Creating a trend reports
  • Sampling reports

Getting Started

Creating Connection

Navigation to data Insight

Note:- First you need to start the Data insight Engine before you use the Data Insight tool.

To start the Data Insight Engine, follow the below navigation-

Start – Program Files – SAP Information Steward – Information Steward

This opens a web based tool.

b8.png

Continue reading “Data Insights in BODS– INFORMATION STEWARD”

SAP BW Back-End Usage Standards and Guidelines

Write ­Optimized DataStore Objects

Consider the following important facts in mind before you choose to use a Write Optimized DataStore Object:

  1. The primary unique key to a WODS Object consists of Request ID, Data Packet ID, and Record Number. The system does not use the semantic key as the primary, unique key to the data. This means that each time you load a particular semantic key into a WODS Object, you get a new, unique record.
  2. Write ­Optimized DataStore Objects do not aggregate data. If you extract and load two records with the same logical key (or extract and load the same record twice,) both records appear in the WODS Object.
  3. No delta detection or extraction function exists for WODS Objects. When forwarding data to subsequent data targets, the system will forward the requests (loads) that have not yet moved to those targets. Note, however, that this can result in duplicate rows going to the subsequent target.

Continue reading “SAP BW Back-End Usage Standards and Guidelines”

BW Development Standards Part 9: Process chain Standards and Guidelines

This post describes standards for building process chains in SAP BW at any generic development project. 

Process Chain Names & Attributes Standards:

Process chain technical names should begin with Z or as per your client naming conventions. 

Guidelines

Descriptions for meta chains (parent process chains that execute sub-­chains) should include “Meta” or “Parent.”

 Display Groupings:

 Standards

  1. Never leave a process chain under the default, “Not Assigned,” Display Grouping. Use the Display Components toolbar button ( ) to assign new process chains to the appropriate display grouping.
  2. Refer your client’s SAP BW Naming Convention document for Display Grouping technical names

 

Guidelines:

  1. If you have a large application composed of multiple logical subsystems, you may create multiple display groupings for your application. Doing so can help you organize your process chains by subsystem. Just make sure the name and description conform to the client standards.
  2. To ensure that you do not leave process chains abandoned under the “Not Assigned” display grouping, consider getting into the habit of assigning the display grouping immediately after you create the Start process for new process chains.

 

Process Chain Scheduling: Continue reading “BW Development Standards Part 9: Process chain Standards and Guidelines”