Business objects what is a context

Creating and Viewing SAP BusinessObjects Contexts Problem: The Customer has multiple fact tables and wants to reuse the dimension tables without aliasing all the dimension tables or creating loops Solution: Create contexts for each fact table Open up the Information Design tool IDT and within the IDT open up the data foundation layer From within the DFX layer if IDT select Aliases and Context Add a new context and name the new context Select the newly added context and you can now edit the context joins in two ways graphically or by viewing the individual joins.

We will start by viewing the joins graphically and selecting edit Select the newly added context and you can now edit the context joins in two ways graphically or by viewing the individual joins. We will start by viewing the joins graphically and selecting edit Tip : Webi can be complicated. In Webi it is a calculation. Context is a collection of joins in universe, which is generates a Query in Business Objects.

Please Turn OFF your ad blocker. Learn More. Home Interview Questions Business Objects. What is context in Business Objects and their usages? Interview Candidate Jul 17th, 10 Business Objects. First Prev Next Last. Showing Answers 1 - 10 of 10 Answers. Context can be used to resolve loops in the universe A context is a rule by which designer can decide which of two paths to choose when more than one path is possible from one table to another.

Hi Rajesh;. Context is the sets of join path for one table to another table. Context is a method by which designer can decide which path to choose when more than two path possible from one table to another table.

You use contexts to direct join paths in a schema which contains multiple fact tables. Alias are not appropriate in such schema. These can occur when two many-to-one join paths converge on a single table. Multiple rows can be returned for a single dimension causing inflated results. Contexts can split out the query so that the correct number of rows are returned for the dimension. You can use contexts to exclude objects that are not compatible with an object using the AggregateAware function in its definition, from being used in a query with the aggregate aware object.

If you have multiple contexts in universe, try creating a report which includes objects common to both the context. This situation does not give enough information on which context to use while generating the query and inturn it prompts all available contexts to user to choose from. Once user selects the context, query is generated accordingly. Make sure Allow selection of multiple context option is selected from SQL tab of universe parameters as user might select multiple context in case of ambiguous query.

Incompatible Objects query. If you have used object in a report which belong to multiple context and objects which are unique to each contexts. The tool creates multiple SELECT statements for each context and then result is merged in to present in single table form this is called as Incompatible Objects query. Inferred query. Inferred query is query which gives enough information to tool to choose the right context without prompting to user.

When you have context in universe make sure you test the contexts by creating all three types of query and observe the behavior of tool in each query type. Resolving Loops using Shortcut Join. Apart from alias and context, shortcut join can also be used to resolve the loops in universe. When do I use Contexts in a Universe? If your universe has multiple fact transaction tables, you will need one context for each fact.

And just to be clear, for this purpose, I am defining a fact table as the lowest level of transactional data. There may be multiple tables that belong to one fact, such as Invoice Header and Invoice Detail. In this case, the Invoice Detail table would be considered the lowest level of transactional data. But if you have multiple facts, you will need contexts.

OK, So what is a Context? A context is a list of joins that define a logical path through a universe. Contexts are used to resolve loops that are caused by multiple fact tables accessing common dimension tables. The joins that belong to a context are the joins from the fact table, leading to any and all dimension tables that might be needed for that fact.

The joins highlighted in blue, are all members of the Sales Context. Joins that are not members of a context are called isolated joins.

Isolated joins will not be recognized by the reporting tools. Note: This rule will go away in BI 4. As you can imagine, joins that do not connect directly to a fact table, can be in multiple contexts. When properly implemented, contexts will prevent Fan Traps and Chasm Traps from returning incorrect results. If a user runs a query which includes objects from two different contexts, Web Intelligence will generate two separate SQL statement, and join the results on the common dimensions after results have been retrieved.

How do I create a Context? There are several methods for creating contexts. They can be created manually, or automatically. The most accurate method is to create them manually.