9 Lesson: Creating a Web Intelligence Document for SAP NetWeaver BW 11 Unit 6: SAP Crystal Reports and SAP NetWeaver BW 11 Lesson: Creating a Report with SAP Crystal Reports for Enterprise 11 Lesson: Creating a Report with SAP Crystal Reports 2016 11 Lesson: Creating a Report with SAP Crystal Reports 2016 and SAP BW 13 Unit 7: SAP. 100 Things You Should Know About. This book is one of the first of a new series based on 100 ideas for various SAP software components. It is designed to make reading and understanding SAP ERP more interesting and accessible for your day-to-day work. You can flip through this.
First:You can upgrade in ONE STEP from SAP BW 7.0x to SAP BW 7.40 and higher (e.g. 7.50) including the SEM and other Add-On´s. Hello Beat,Every Customer should start with a BW (on HANA), which answers the Question of the underlying database platform.As our Reference Customers in the german region D-A-CH are midsize customers, I rather think these type of Customers are less afraid what BW on HANA brings for them.Choosing BW on SAP Sybase ASE is a wise decission from the (SAP) Vendor perspective, as ASE is part of the SAP Family.Furthermore the usage od SAP-NLS for BW based on SAP Sybase IQ can be directly enabled on ASE, as they share the same LibDBSL.Best Regards Roland KramerPM BW/In-Memory. Hi,I have a doubt on the delta jobs after migration. When we say BW is migrated to HANA. Does that mean the source system for example ECC will still have the old DB like oracle or DB2. Only the data extracted from the source system ECC will be moved to HANA DB where BW is on the application server, is that a right statement?If we complete our BW migration to HANA DB successfully, then still the delta jobs, update queue, extraction queue are all running on the same old ECC DB ( oracle ).
Then the currently running delta in production will not get effected after the HANA DB migration? Please advise.Thanks for reading.DR.
Checks to be done in ECC system before BW upgrade.Before the upgrade (import of a queue), all extraction queues and open update orders in all clients must be processed. The content of the setup tables must be deleted.
To avoid many problem during the upgrade or to correct it, carry out the following steps:1. Call transaction SMQ1 and check whether all queues in all clients (client = '.'
, queue name 'MCEX.' ) have been processed. To process the queues, start the collective run report for each application in the displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.2. If you use the V3 update that is not serialized (usually for application.): Start collective run report RMBWV3. Where.
denotes application component like 02,03,11, 12, 13. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them, But you need to very careful before taking this decision. There may be inconsistencies between tables VBMOD and VBHDR.
For further information about this, see 2 Notes 652310 and 67014.3. Before the upgrade, delete the contents of the setup tables.
Execute report RMCEXSETUPENTRIESto find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.More detailed information so check the note given below 1083709-Error when you import Support Packages 1081287-Data extraction orders block the upgrade processIf you see RSA7 is empty. Initialise delta for desired datasources too.Also do check the notes below for knowuing more on delta queue: 728687 Delta queued: No data in RSA7To know more about update methods, check this note 505700 LBWE: New update methods as of PI 2002.1If there is a need to reconstrcu the data check the below note 602260 Procedure for reconstructing data for BW.