Documents in your enterprise are stored on WebDAV servers. You want to use the Knowledge Management (KM) platform to make these documents accessible by employees in the Enterprise Portal. Employees need to read and edit these documents. They also need to create new documents. You also want to make the most of subscription and collaboration services, and to be able to search for documents.
Users of the Portal can also take advantage of WebDAV. WebDAV enables documents to be edited directly on the server. You can use a WebDAV-capable client (for example, Microsoft Office 2000) to open the file directly from the Portal server. You can then make your changes. When you save, the document is updated directly on the Portal server and can be called up in the Portal in its newest version. Locking and version control mechanisms ensure secure work within groups and prevent documents from being accidentally overwritten.
The Knowledge Management platform can be implemented as a WebDAV server and as a WebDAV client. This allows it to be used in different scenarios.

• The KM platform as a WebDAV server You want to access CM repositories of the KM platform with a WebDAV-capable client, for example, MS Webfolder. We recommend this especially if you want to transfer large numbers of files to the KM platform (mass operations).
• The KM platform as a WebDAV client You want to use the KM platform to access documents that are stored on other WebDAVcapable servers (for example, in another Enterprise Portal or on Microsoft Internet Information Servers). You need a WebDAV repository manager to do this.

Download the Complete Manual to know more.

This guide describes how to analyze the Microsoft Exchange integration with SAP Enterprise Portal 6.0

Checklist:

Check MSX-A component setup

• Check MS Outlook setup
  Is the correct version of Microsoft Outlook installed on the IIS server?
  Is Microsoft Outlook configured to access Microsoft Exchange Server?
  Do I have the correct version of Microsoft Exchange Server?

• Check IIS setup
  Can ASP applications run on the IIS?
  Is the MS Exchange server in the same windows logon domain as the IIS server?
  Do users have sufficient rights to execute the MSX-Acomponent?
  Have the MSX-A components been registered?
  Does the setup work with the test application?
  Is Kerberos SSO enabled?
  Do OWA iViews work with SSO?
  Is the MSX-A component configured on the backend server hosting the Kerberos components?

Check portal setup

• Is the user set up correctly?
• Is the IIS configuration mapped correctly?
• Can the IIS server be reached using the host name from the portal?
• Is the integration functioning?

Download the complete manual from Rapidshare or Mediafire.

Collaboration component saves money and time and improces work quality. It provides an open infrastructure to enable communication, create transparency and collect, merge and present information. By allowing to integrate with existing tools and infrastructures and span a wide range of scenarios and situations.

SAP NetWeaver Collaboration supports the people to:

• Create a seamless work flow
• Organize their work
• Create and maintain a network of information
  • by enabling the people to create, modify and publish content and to extend the information network
• To do all this in a self-service mode without having to learn new concepts

Download the Presentation from Rapidshare or Mediafire.

As of BW 3.0A, there is an Export DataSource for the PSA. You can use this DataSource like any other DataSource, for example to read data from the PSA with a RemoteCube. In the example shown here, we will compare data that has been loaded to the InfoCube with data loaded into the PSA. In a query, you can see the data from the InfoCube in one column and the data from the corresponding PSA table in another column. You can compare the results and judge whether they match.

This White Paper (PDF) only gives you an introduction about how you can work with the PSA Export DataSource.

Today, in SAP’s Business Information Warehouse, currency conversion can take place using different parameters defined in a currency translation key (source currency, target currency, exchange rate type and time reference) and in different layers (during update of data to the data targets, at query definition time and at query runtime).

One major requirement, not fully covered by today’s architecture, is the dynamic time currency conversion using variables in Reporting. The dynamic time reference in the above mentioned table only includes dynamic conversion using a “date InfoObject” (no variable input) or the query key date (applicable in only some business cases, see comment below). Therefore, this technical solution shows you how to implement multiple and dynamic time currency conversions in one query. This includes especially variable time conversions allowing the customer to execute different conversions to the same target currency using different dates (example: simulate influence of exchange rates on sales). Please note: the variable selection of the target currency mentioned in this paper can be achieved using standard functionality.

The solution needs to be implemented only once per InfoCube but is very usable for the BW end users. Only the conversion rates (table TCURR) have to be loaded (and maintained on R/3) on a regular basis. Key benefits of this solution are:

• Very easy to use (simple input of time reference by user)
• Independent of data model (solution works with any Infocube and query).
• Correct aggregation of converted quantities (totals and subtotals are calculated).
• Low performance impact: usage of the OLAP BADI (virtual exit) is not leading to bigger data amounts being processed by the OLAP processor.
• No impact on transaction data stored in the BW database.

Know more about it in this manual(PDF).