As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Users of the SAP ERP in a merged company are to switch to our ERP without their existing data in SAP being converted.
We still need to access the data in SAP for historical reporting, but the expensive SAP contract needs to be terminated once users have converted to our ERP. Thus the wf SAP adapter is not an option.
Does anyone know which of these options would be better?
"DATA IN SITU OPTION".
We can leave the data in situ and use our oracle or odbc adapters to report against the source. There might be an additional level of complexity because as I understand the WF SAP adapter works directly against the SAP API which produces a much simplified view of the underlying data, but reporting would still be achievable.
"DATA EXTRACT BEFORE SAP SHUTDOWN OPTION".
Before we lose the SAP licence we need to export the data using the SAP import/export facility to an intermediate store (eg SQL server tables, flat files) where we may later report on it with our adapters.
If anyone has experience of similar their answer, as always, would be most appreciated.This message has been edited. Last edited by: hammo1j,
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
As you undoubtedly know, SAP has an abundance of tables. So I think it is hardly doable to produce a download of *all* tables into an sql server instance. Yet I do think it is the best way to go. Of course you can limit the download to those tables that you really need.
Just my 2cts.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
There is very little difference between the two options when going against SAP transparent tables as these are standard SQL tables. The issue arises when you need to access things such as cluster tables, views and logical databases etc. These things often require internal SAP abap routines for access and so cannot be read using a standard relational adapter. For that reason even though it’s going to be a pain doing the analysis of what you actually want to keep go for the "DATA EXTRACT BEFORE SAP SHUTDOWN OPTION".