Business Intelligence - An Introduction

Business Intelligence, also known as “BI”, is a term currently used to describe a discipline which captures and assesses various aspects of a company, its customers and competitors. This includes processes and software which assist in gathering, storing, analyzing, and providing access to intelligent information on a companys data in order to identify significant trends or patterns that ultimately facilitate the decision-making process and provide the company with a competitive advantage.

read more...

Business Intelligence

Enterprises no long have to rely on intuition for decision-making. You don’t have to wait for weeks or months for a set of canned reports. An informed knowledge worker of an intelligent enterprise should have standard report, ad-hoc reports, and what-if analysis, forecasting, interactive dashboards on single point click. In addition to this, there are requirement related to legal, and regulatory compliance reporting that are new demands from a business intelligence solutions.

Apnatek’s experts have strong experience in implementing business intelligence solution using both commercially available tools and open source tools in this area. A representative sample of these tools are, for example Oracle BI suite, Microsoft BI suite , Pentaho BI suite, Jaspersoft, Microstrategy, Business Object, and Crystal reports.

Call us today to find out how we can help you architect, design and develop a business intelligence solution based on proven methodologies that meets your specific needs.

Data Management
It helps optimize the potential your organizational data. Key three areas in data management are as follows:



Master data management (MDM) comprises of products, processes, peoples, material, assets, customers, locations, cost centers, planned buildings, and other tangible touch points which centrally and persistently define the non-transactional entities of your company. Master Data Management serves as a source quality information source to your mission-critical operational system i.e. online transaction processing (OLTP) application, and your analytical systems such data warehouse or data marts. A well developed MDM solution will help you improve the quality of day-day business transactions, and strategic decision making.

Meta-data management is data usage context, applications, processes and the relationships among them in your information systems. A good metadata management solution improves quality and the total cost of ownership (TCO) of the data warehousing and business intelligence solutions.

Data quality and Data governance provides mechanism to improve enterprise-wide data integrity. Our experts can help you design and develop an effective meta-data management solution.

read more...

Software Escrow - Definition

Source code escrow means deposit of the source code of the software into an account held by a third party escrow agent. Escrow is typically requested by a party licensing software (the licensee), to ensure maintenance of the software. The software source code is released to the licensee if the licensor files for bankruptcy or otherwise fails to maintain and update the software as promised in the software license agreement.

Source code escrow services may be very limited, such as verifying that media is readable, or very comprehensive, such as doing a complete build of the software based on the source code and verifying that features match the binary version.

Types of escrow
Escrow is best known in the United States in the context of real estate (specifically in mortgages where the mortgage company establishes an escrow account to pay property tax and insurance during the term of the mortgage). Escrow companies are also commonly used in the transfer of high value personal and business property, like websites and businesses, and in the completion of person-to-person remote auctions (such as eBay). In the UK escrow accounts are often used during private property transactions to hold solicitors' client's money, such as the deposit, until such time as the transaction completes. Some solicitors[citation needed] have/had taken to using this money as a loan and got themselves into severe trouble.

Escrow is also known in the judicial context. So-called escrow funds are commonly used to distribute money from a cash settlement in a class action or environmental enforcement action. This way the defendant is not responsible for distribution of judgment monies to the individual plaintiffs or the court-determined use (such as environmental remediation or mitigation). The defendant pays the total amount of the judgment (or settlement) to the court-administered or appointed escrow fund, and the fund distributes the money (often reimbursing its expenses from the judgment funds).

In some jurisdictions, real estate brokers are considered to act as escrow agents when they accept deposits or earnest money for the purchase of real property. In many jurisdictions, the duties of such agents are codified.

Escrow is also used in the field of automated banking and vending equipment. One example is automated teller machines (ATMs), and is the function which allows the machine to hold the money deposited by the customer separately, and in case he or she challenges the counting result, the money is returned. Another example is a vending machine, where the customer's money is held in a separate escrow area pending successful completion of the transaction. If a problem occurs and the customer presses the refund button, the coins are returned from escrow; if no problem occurs, they fall into the coin vault.[1]

read more...

Unique concept of internal table in ABAP

Unique concept of internal table in ABAP :

Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, the programmer is saved the task of dynamic memory management in his or her programs. Internal tables should be used whenever there is a need to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.

Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.

Internal tables as data types



Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type.

Line type

The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.

Line Type can also refer to an ABAP Object’s reference pointer value. If two ABAP Objects are not related, they do not have the same line type. The line type is stored in the value of the reference pointer and can be viewed in the debugger. If one object attempts to access another unrelated object’s components, you will receive an error specifying that the line types do not match.

Key

The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key is UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries with the same key. The uniqueness depends on the table access method.

If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves internal tables. If a table has an elementary line type, the default key is the entire line. An internal table which has a line type that is itself an internal table, has an empty key.

The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.

Later versions of ABAP permit the definition of secondary keys.

Table type

The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:

Standard tables have an internal linear index. (Think of index as “record number”. It is not to be confused with a database index, for example). From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.

Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be unique or not. Standard tables and sorted tables are known generically as index tables.

Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.

Generic internal tables

Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols and the interface parameters of procedures. You cannot use them to declare data objects.

Internal tables as dynamic data objects

Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.

Choosing a table type

The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.

Standard tables

This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.

Sorted tables

This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.

Hashed tables:

This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.

read more...

SAP Netweaver

In the present era, where companies are struggling to unite various heterogeneous environments in their organizations and maintain a lower Total Cost of Ownership (TCO) NetWeaver comes as a solution to all their problems. SAP NetWeaver is the latest advancement in the mySAP Technology, which was developed as an Artificial Intelligence (AI) shell that accepts standard comments, literally as they are spoken, by domain experts.

Another unique feature of NetWeaver™ that makes it stand out amongst other software technologies is its modularity. The knowledge engineer can more easily create "digestible chunks" of modules or sub-dependency networks, which help to keep the overarching dependency network from becoming potentially incomprehensible because of apparent complexity. This text is aimed at explaining SAP NetWeaver architecture and its interoperability with Microsoft.NET and IBM WebSphere. In addition it aims at bringing out all the advantages that are associated with SAP NetWeaver.

Net Weaver in simple words is an application and Integration platform in which Web Services play a major role and which is open for Non-SAP applications and platform. It is used by organizations to improve productivity and enhance efficiency by making all the resources that are available in an enterprise to work collectively. The SAP customers to bring heterogeneous environments at one platform use SAP NetWeaver. In addition, it enables customers to use the already existing systems without putting in much investment. Further in the near future, the various corporate sectors and Organizations have to take a decision for some common platform; could be Microsoft .NET, IBM Websphere or SAP NetWeaver. Irrespective of the choice that they make, SAP NetWeaver is the one that integrates with all the three technologies.
Read This Nugget: As it’s name suggests, Enterprise Core will contain the inward, enterprise processes that make the enterprise work. The outward, collaborative processes will not be included in Enterprise Core. They will be included in what is called Enterprise Extensions.

SAP NetWeaver attains the process of integration by integrating all the available heterogeneous resources of the existing system and unifying them into a homogeneous form. This integrated information forms the basis of total, comprehendible, focused solution as desired in an enterprise.
2.0 NetWeaver Object Model and Enterprises Architecture
This section focuses on overview of the object model of NetWeaver. This basic knowledge facilitates the organizations in constructing an apprehensible knowledge base. The various components that are present in NetWeaver Object Model are Data Links, Dependency Networks, Nodes and in some cases, evaluation groups. Each of these components and their function in the NetWeaver Object Model is described below:

* Data Links: These objects of the NetWeaver function to request data about the real-world objects. They can also be defined as the objects that have one-to-one relation with the real-life objects and can be logically and mathematically manipulated. Thus, making the knowledge representation in NetWeaver simple as well as insightful. Moreover, these objects are reusable and can be referred as and when required.

* Dependency Networks: The dependency networks in NetWeaver play the central role in formulating the representation of the problem. These dependency networks are used to interconnect different objects in the object model. Therefore, they are considered to be the most important factor in the object model of NetWeaver. Using the "New Network" that is present in the network window can create a new dependency network. Also, new dependency networks can be added in the object model in the later stages without creating any interference with the already existing knowledge base.

* Nodes: Nodes function to form the relation between data links and dependency networks. Nodes are classified into logical nodes and functional nodes. The logical nodes define the dependencies of the network on its antecedents and the functional nodes are used to construct the mathematical relation in the data links.

* Evaluation Group: An evaluation group is a user-defined collection of networks. An evaluation group specifies a collection of networks that are conceptually relevant to one another and that the knowledge base designer wants to see evaluated as a set.
3.0 Interoperability of SAP NetWeaver with Microsoft .NET
SAP along with Microsoft is creating a development kit, which enables to create Iviews inside Microsoft Visual Studio.

The Iviews help in integrating information and functions from a wide range of sources in an enterprise portal. It helps in developing portal content on your preferred platform. It also helps in accessing and gathering Information consistently. This is achieved by integration of SAP Knowledge Management and data management tools such as Microsoft Content Management Server. This integration centralizes the Knowledge base and helps in coordination of processes, which cover various Technologies e.g., SAP NetWeaver supports an environment in which SAP Exchange Infrastructure and Microsoft BizTalk Server can exchange information.

Additionally, SAP Web Application Server, which is a component of SAP NetWeaver, supports platform independent Web services and the same Web services as standards as Microsoft, including Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL), and Universal Description, Discovery, and Integration (UDDI). For Microsoft .NET, SAP’s .NET connector provides a highly scalable and reliable communication infrastructure, as well as a Microsoft Visual Studio .NET Add-In to simplify development.

4.0 Interoperability of SAP NetWeaver with IBM WebSphere

Interoperability of SAP NetWeaver with IBM WebSphere takes at People, Information and process level. This interoperability helps in developing portal content on your preferred platform thus saving investments. SAP NetWeaver supports groupware and collaboration products such as Lotus. It helps in accessing and gathering Information consistently. This is done by integration of SAP Knowledge Management and data management tools such as IBM Content Manager. It also centralizes the Knowledge base and helps in coordination of processes, which cover various Technologies e.g., SAP NetWeaver supports an environment in which SAP Exchange Infrastructure and IBM WebSphere Business Integration can exchange information. As mentioned earlier, SAP Web Application Server, a component of SAP NetWeaver, supports platform-independent Web services and other primary technology standards including J2EE Connector Architecture (JCA) and Java Message Service (JMS). SAP Java Connector is a toolkit that allows a Java application to communicate with any SAP system. It combines an easy-to-use API with extraordinary flexibility and performance. The package supports both, Java-to-SAP, as well as SAP-to-Java calls. Customers using IBM WebSphere can easily access existing business objects and integrate their applications with any SAP application.

5.0 Creating an ASP .NET Web Application Using the SAP .NET Connector

SAP.NET Connector along with Microsoft.NET can be used to create Web Applications. The following example illustrates creating .NET project using Microsoft Visual Studio. NET. Here, a client application reads and displays customer data from an SAP System using a search value and then displays it in a data grid.

The example uses the function module RFC_CUSTOMER_GET, which requires that customer data exist in the target SAP System, for example, in IDES. Although it is possible to rename all development objects and generated proxy classes, default names are used in this example. This example is provided as part of the connector sample code (DNCWebApp).

Procedure of Creating an ASP .NET Web Application Using the SAP .NET Connector:
1. Open Microsoft Visual Studio .NET.

2. Create a new C# Web form project:
Choose New. New Project. Visual C# Projects. ASP .NET Web Application.

You can also create a project in any other common programming language for .NET, for example, in Visual Basic .NET. In this case, you must add the SAP .NET proxy classes as a separate project in the Microsoft Visual Studio .NET solution.

3. Rename the form Webform1.aspx to Default.aspx.

4. Add Web controls to your Web form.

5. Add proxy classes to connect the Web applications to your SAP server.

#

a. In the Solution Explorer, right-click on your project.
#

b. Choose Add. Add new item.
#

c. Select Web Project Items.
#

SAP Connector Class and choose Open.
#

The SAP .NET Connector Wizard opens.
#

d. Decide from where you want to generate the proxy classes.

Proxies can be created from

* - Web Services Description Language (WSDL) files that originate in an SAP interface repository (IFR)
* - An SAP server
* - Standard WSDL files

#

e. Select the client proxy object type and select beautify names option.
#

f. Select the Remote Function Modules (RFM) you want to use in your proxy object.

You can use search filters to look for the Remote Function Modules. In the example, enter the search argument RFC_CUST* in Name-Filter and select RFC_CUSTOMER_GET.

#

g. Add the modules to your proxy object and choose NEXT.

The proxy classes for the referenced table and structure types are automatically created and added to the project.

6. Build the solution with Build. Build Solution.

7. Create an SAP Login page to support user name and password authentication

#

a. In the Solution Explorer, right-click on your project.
#

b. Choose Add. Add new item.
#

c. Select Web Project Items. SAP Login Form

Leave the name as SAPLogin1.aspx.

8. Set the system connection information in the destination object of the SAPLogin1.aspx page:

#

a. In the Solution Explorer window find the item SAPLogin1.aspx and double-click on it to bring it up in the designer.
#

b. Look for the component destination1 on the bottom of the form.
#

c. Click on the destination component and set the properties for connecting to your SAP system (for example AppServerHost and System Number). The other properties like client, Password and username will be set from the login page.

9. Data bind the data grid to BRFCKNA1Table:

BRFCKNA1Table is the parameter of RFC_CUSTOMER_GET that contains the list of customers.

#

a. Select SAP Table Wizard from the SAP proxy toolbox and Drag Drop it to your working area. In the dialog box, select BRFCKNA1Table.
#

b. Select the data grid, and under Properties change Data Source to BRFCKNA1Table using the drop down list.
#

c. Customize the list of columns displayed on the data grid by modifying the Columns collection property.

10. On the default.aspx page, double-click the Button control you added earlier to create an event handler for the control.

11. Add the connect code to your project:
Select Connect code from the SAP proxy toolbox.

Drag Drop it in the source code of your event handler. A fragment of sample code is then inserted. It connects to the SAP server using the authorization settings from the Proxy Wizard. Normally, you must change these settings.

The syntax for the application will be

private void btnSearch_Click(object sender, System.EventArgs e)

{

// Declare parameters here

SAPProxy1 proxy = new SAPProxy1();

try

{

proxy.Connection =

SAP.Connector.SAPLoginProvider.GetSAPConnection(this);

// Call methods here

proxy.Rfc_Customer_Get("", txtCust.Text, ref brfcknA1Table1);

// Now update Data Bindings. On WinForms this will be automatic, on

// WebForms call the following line

this.DataBind();

}

catch(Exception ex)

{

// If SAPLoginProvider.GetSAPConnection(this) cannot get a connection,

// we might get an error.

// Normally this can be ignored as it will automatically will force a

// relogon.

}

}

12. Build and run the application.

The browser window opens and you are redirected to your SAPLogin1.aspx login page.

13. Enter connection data (for example user, password and client).

If you select SAVE this login information will be stored as an encrypted cookie on your computer and will provide an alternative single sign-on capability the next time you wish to access the site. If you do not select SAVE, the login information will still be saved in the ASP .NET session state but will be lost once the browser is closed.

14. Enter a search argument, for example A* in the Textbox field and choose Search. Thus we create an ASP.NET Application using Visual Studio .NET using Proxy classes to connect to the server and Binding the DATA GRID. Your application connects to the SAP System and displays the requested data in the Data Grid.



6.0 Using the SAP Java Connector
SAP’s new Java middleware, the SAP Java Connector (JCO) allows customers and partners to easily build SAP-enabled components in Java. JCO supports both inbound (Java calls ABAP) and outbound (ABAP calls Java) calls in desktop and server applications.

In this Sample Program we connect to SAP and call two BAPIs.
Import statements: Any program using JCO should contain the following import statement:

import com.sap.mw.jco.*;

Otherwise, you have to fully qualify each class and interface which is very inconvenient.

Connecting to SAP
JCO.Client mConnection;

A connection (or session) with SAP is handled by class JCO.Client

try {
mConnection =
JCO.createClient("400", // SAP client
"c3026902", // userid
"********", // password
"EN", // language
"iwdf5020", // host name
"00"); // system number
mConnection.connect();
}
catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
}

"A Client object is created via a call to createClient(). You can use a specific application server (as in the above code) or a server group (load balancing)." REFER the JCO Javadoc for the overloaded createClient() method for the latter possibility.

"The Client class's connect () method tries to log on to SAP. If that fails for any reason, an exception is thrown. If the call succeeds, we can now stay connected for as long as we like. When we are done, we can call disconnect () to explicitly log off."



6.0 Advantages of SAP NetWeaver

a. Enhanced Adaptability: Enhanced adaptability actually refers towards the adaptability of SAP NetWeaver towards the existing Business System in any organization. It provides a heterogeneous environment, integrating the various applications; databases and making available open technologies like web services readily available to the user. It saves money on unnecessary customization of the existing business System.

b. Lower TCO: SAP NetWeaver instead of replacing the existing system interweaves the various resources like databases, legacy systems; Internet based Information and provides a heterogeneous Environment for the user to get the maximum from the new unified system. It also prevents unnecessary customization of the entire system. Moreover, it reduces complexity and makes the system more comprehendible and flexible to the rapidly changing business processes. All of these lead to reduced the total cost of ownership.

c. Better ROI: SAP NetWeaver increases the return on investment. As mentioned earlier, by using this technology IT strategies can be synchronized with SAP solutions. This synchronization makes the system more reliable leading to better assessment services, which in turn lead to financial benefits.

7.0 Conclusion

NetWeaver uses a very transparent process to provide the ability to trace the logic structure right from the raw data to information, which can be used for analysis. It helps in developing portal content on your preferred platform. Interoperability of SAP NetWeaver both with Microsoft .NET and IBM Hemisphere takes at People, Information and process level. For Microsoft .NET, Sap’s .NET connector provides a highly scalable and reliable communication infrastructure, as well as a Microsoft Visual Studio .NET Add-In to simplify development. Further, Sap’s new Java middleware, the SAP Java Connector (JCO) allows customers and partners to easily build SAP-enabled components in Java. Thus, helping decision makers interpret and manipulate the output of the decision model that provides mathematically robust knowledge about complex problems. Hence, making SAP NetWeaver a Complete Solution for the Integration with various applications and platforms that are used in various organizations.

IF you find this ARTICLE interesting, Leave your comments.

read more...

AUTO INSURANCE QUOTE

Use
SAP Policy Management (FS-PM) is an integrated policy management system that is suitable for insurance companies operating on a global basis and for the regional market. This is guaranteed by integration in the SAP landscape.

Integration - auto insurance quote
SAP Policy Management is a central component of the insurance solution portfolio (SAP for Insurance), based on SAP NetWeaver 2004s (SAP NetWeaver Application Server ABAP 7.0).

This integration ensures that the communication with other SAP components, such as FS-BP (Business Partner), FS-CD (Collections/Disbursements), FS-CM (Claims Management), FS-ICM (Incentives & Commission Management), FS-RI (Reinsurance), and additional components is possible using defined interfaces. You can also connect systems from other providers.

Features
The following graphics show an overview of SAP for Insurance and the system architecture of SAP Policy Management:



Overview of architecture of SAP Policy Management. Auto insurance and statutory health insurance are potential LoB modules.

SAP Policy Management is divided into a basic part and into lines of business parts with industry-specific product models and business processes/transactions.

The Product Engine (msg.PM) linked to SAP Policy Management delivers the definition of the product structure used as the basis for policies, and for rating and plausibility check rules, and it also executes the calculations for each insurance product.

For more information, see:

● Collections/Disbursements

● In-Force Business Management

● Product Engine (msg.PM)

● Lines of Business

● Object Management

● Journal Management

● Fund Management

● Correspondence

● Accounting Component

read more...

BW - Integration

Analysis of BW support navigation facilities integrated to BW 3.0

OLAP BAPI: SAP BW 3.0 comes with the OLAP BAPI Interface (OBI) which provides functions that can be used by third party reporting tools to access BW Info cubes. It provides an open interface to access any information that is available through OLAP engine.

Integrating with XML: OLAP BAPI serves as the basis for the SAP implementation of XML for analysis. It is an XML API based on Simple Object Access Protocol (SOAP) designed for standardized access to an analytical data provider over the web. The XML interface introduced with SAP BW 3.0 release accepts XML data streams compliant with the SOAP. Unlike all other SAP BW interfaces in XML interface the actual data transfer is initiated by the source system.

Open Hub Services: The Open Hub Service allows controlled distribution of consistent data from any SAP BW InfoProvider to flat files, database tables and other applications with full support for delta management, selections, projections and aggregation. Open Hub Services have InfoSpokes as their core metadata objects. With the SAP 3.0 release InfoSpokes have become generally available.

Content Management Framework: The SAP Web Content Management Server stores unstructured information that users can go through and use efficiently. Integration with the SAP BW content management framework provides an integrated view on structured and unstructured information to the end user.

read more...