miércoles, 25 de marzo de 2015

This Content replaces the existing "SAP HANA Cookbook"

First Guidance
 
The First Guidance documents are the beginning of a series of documents that should help to better understand the various concepts of SAP BW powered by SAP HANA.The documents are still “work in progress”, so these guides are not intended to be exhaustive.. The purpose of these documents is to deliver additional information besides SAP Help and blogs to get a better understanding of the concepts of SAP BW on SAP HANA.


 
 
SAP First Guidance - Business Warehouse on SAP HANA Installation (Updated version: reflects now the 7.31/7.40 releases as well, the usage of the SL toolset (SWPM, SUM, etc.) and the current SAP HANA 1.0 SP08 release and there actual revisions.)
After BW on HANA is already available since mid April 2012 this document was enhanched a few times since the first version.
On base of this information this "SAP First Guidance" document is released to support Basis administrators in running and  and configuring a Business Warehouse on a SAP HANA system. SAP First Guidance - Business Warehouse on SAP HANA installation provides answers to major questions and issues as well as workarounds and additional details to complement standard SAP Guides and SAP notes. This SAP First Guidance document has no claim of completeness, but it is the most complete starting point for an successfull implementation.
For more information please contact roland.kramer@sap.com
 
 
 
SAP First Guidance - Migration BW on HANA using the DMO option in SUM
the database migration option (DMO) is an option inside of the software update manager (SUM) for combined update and migration: update an existing SAP system to a higher software release and migrate to SAP HANA database in one technical step. As the technical SUM steps are the same, this “SAP First Guidance” document should make all customer-specific documentation obsolete. It is the complementary documentation to the existing Notes and SUM/DMO Upgrade Guides.
DMO can be used with every BW Release starting from 7.0x and onwards. It makes the two step approach (upgrade/migration) and the usage of the BW post copy automation (BW-PCA) obsolete. It can also be used within a Release, e.g. to go from 7.40 SP06 on anyDB to migrate to 7.40 SP07 on HANA.
For more information please contact roland.kramer@sap.com
 
 


SAP First Guidance - Implementing BW-MT for BW-aDSO
SAP BW 7.4 SP08 powered by SAP HANA is the next milestone for enterprise data warehousing with BW on HANA and provides the next level of simplification for BW .In addition, SAP BW on HANA Virtual Data Warehouse capabilities have been enhanced for even more flexibility. In midterm the advanced DSO shall replace the main BW InfoProviders with persistency (InfoCube, DSO, PSA). The classic InfoProviders are of course still supported and do co-exist with the advanced DSOs.
For more information, please contact roland.kramer@sap.com
 
 


SAP First Guidance - SAP NLS Solution with Sybase IQ
This “SAP First Guidance” document provides all the necessary information to help quickly implement this newly released option:
Store historical BW data on an external IQ server to optimize the  system size  when preparing  to migrate to SAP BW powered by SAP HANA.
The SAP NLS solution with Sybase IQ also helps to keep down the TCO for investing in the SAP In-Memory when historical (“frozen”) data is stored on a less sophisticated device, which acts like a “BW Accelerator on Disk”. SAP Sybase IQ is therefore the perfect smart store for this kind of data.
Please note that the SAP NLS solution can be used with all database versions supported by SAP BW 7.3x. SAP HANA is not necessary. The document is a “work in progress” and is not intended to be exhaustive.  It does however contain all information required for successful implementation of the SAP-NLS solution with Sybase IQ. SAP-NLS can be used with every SAP supported database, where SAP IQ will be the seconday database for data reallocation.
For more information, please contact roland.kramer@sap.com
 
 
SAP First Guidance - SEM/BW Modelling in SolMan 7.1 with MOPZ
Due to constant Questions about the Upgrade to NetWeaver 7.3x and 7.40 including SEM Add-On Components, we created a SAP First Guidance Document which describes the successfull Definition of a SAP BW 7.0/7.01 System with the SEM Add-On Installed on top.  With this Information you will be able to integrate the stack.xml in the SUM (software update manager) process and the DMO (database migration option) DMO process included in SUM as the first input is the location of the stack.xml which defines the download directory for SUM. Furthermore the interaction of the stack.xml in the upgrade process enables you a smooth Integration into the Upgrade Process included in DMO.
For more information please contact roland.kramer@sap.com
 
 
 
 
SAP First Guidance - BW Housekeeping and BW-PCA
The system copy procedure of SAP BW systems and landscapes is complex for a number of reasons. There is a large number of configuration settings (such as connections and delta queue handling for data loading) and system copy scenarios of SAP BW (each with different landscape aspects).  These have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or if you want to perform regular system copies of your SAP BW landscape. BW-PCA can be used from SAP BW 7.0 onwards depending on the SPS level.
Additionally see the usage and implementation of the BW Houskeeping Task List and the Pre/Post Task Lists for Upgrade/Migration. These are Included in the database migration option (DMO) as part of the software update manager (SUM). Additional Details also can be found on the BW ALM Page.
For more information please contact roland.kramer@sap.com
 
------------------------------------------------------------------------------------------------------------
 
 
SAP First Guidance SAP BW 7.40 on HANA - HANA Analysis Processes
Starting with SAP BW 7.4 SP5 on HANA a new feature to analyze data from certain perspectives, for example to calculate ABC classes or to calculate scoring classes, is introduced. This new feature is called SAP HANA Analysis Process and enables the data warehouse modeler to analyze the data using different predefined or own written functions or scripts. HANA provides the integration numerous specialized libraries like PAL, AFL, R to understand the correlation of the data in the existing EDW.
 
SAP First Guidance - SAP BW 7.40 on HANA - View Generation
The focus of this document is the exposure of BW data natively in HANA as HANA views that point directly to the data and tables managed by BW. This enables HANA-native consumption of BW data.
 
 
 
SAP First Guidance - SAP BW 7.30 on HANA - Inventory InfoCubes
This SAP first guidance document describes the handling of non-cumulative InfoCubes on SAP HANA. As the handling of Inventory InfoCubes changed within SAP BW 7.30 based on SAP HANA, this document wants to briefly describe the differences. for better understanding it is recommended to read How to Guide based on previous release How to Handle Inventory Management Scenarios in BW.
 
 
SAP First Guidance - SAP BW 7.40 SP05 on HANA - OpenODSView
In SAP BW 7.4 SP05 on HANA the new metadata object Open ODS View is introduced, which provides the data warehouse modeler with a flexible, easy to use tool to integrate external data in the EDW Core Data Warehouse.
 
 
SAP First Guidance - SAP BW 7.40 SP05 powered by SAP HANA - CompositeProvider
A CompositeProvider is an InfoProvider in which you can combine data from BW InfoProviders such as InfoObjects, DataStore Objects, SPOs and InfoCubes, or SAP HANA views such as Analytical or Calculation Views using join or union operations to make the data available for reporting. This paper explains how to create a CompositeProvider in SAP BW 7.4 SP5 using the BW modeling tools in SAP HANA Studio.

SAP Development Tools for Eclipse

ABAP Development Tools for SAP NetWeaver

This site describes how to install and update the front-end components of ABAP Development Tools for SAP NetWeaver (ADT).
It also provides you with detailed information on how to prepare the relevant ABAP back-end system for working with ADT.

Prerequisites

Eclipse PlatformLuna (4.4) or Kepler (4.3)
Operating System
  • Windows 7 32- or 64-Bit, or
  • Apple Mac OS X 10.8, Universal 64-Bit, or
  • Linux distribution
* The compatibility is no more tested by the Eclipse Community since Eclipse Kepler (4.3)
Java RuntimeJRE version 1.6 or higher, 32-Bit or 64-Bit
SAP GUI
  • For Windows OS: SAP GUI for Windows 7.30
  • For Apple Mac or Linux OS: SAP GUI for Java 7.30
Microsoft VC RuntimeFor Windows OS: DLLs VS2010 for communication with the back-end system is required.
NOTE: Install either the x86 or the x64 variant, accordingly to your 32- or 64-Bit Eclipse installation.

Procedure

To install the front-end component of ADT, proceed as follows:
  1. Get an installation of Eclipse Luna (recommended) or Eclipse Kepler.
  2. In Eclipse, choose in the menu bar Help > Install New Software...
  3. For Eclipse Luna (4.4), add the URL https://tools.hana.ondemand.com/luna.
    For Eclipse Kepler (4.3), add the URL https://tools.hana.ondemand.com/kepler.
  4. Press Enter to display the available features.
  5. Select ABAP Development Tools for SAP NetWeaver and choose Next.
  6. On the next wizard page, you get an overview of the features to be installed. Choose Next.
  7. Confirm the license agreements and choose Finish to start the installation.

More Information

To configure the relevant ABAP back-end system, follow the steps in the how-to-guide Configuring the ABAP back-end for ABAP Development Tools
For more information about ABAP Development Tools, see our community.
The downloads are provided under the terms of the SAP DEVELOPER LICENSE AGREEMENT.

lunes, 2 de marzo de 2015

Diferencia entre MB52 y MB5B en Inventario

la MB52 SOLO MUESTRA STOCK FINAL ACTUAL ; En cambio la MB5B te muestra el stock en un momento X, por ejemplo puedes colocar el stock que tenias hasta el 31 de Diciembre del 2013, también te sirve para ver que movimientos hubieron en un intervalo X de tiempo, por ejemplo ver el material BOLIGRAFOS que movimientos se hicieron entre las fechas 1 de Septiembre y 10 de Septiembre.
Esa es la diferencia, claro que la MB5B exige un poco mas de procesamiento de tu servidor, otra transacción similar a la MB5B yo la utilizo mas por ser mas entendible en cuanto a su estructura como reporte es la MB51, que hace casi lo mismo.


 La primero la MB52 solo te muestra el stock del inventario a la fecha por centro o por almacén, en cambio la MB5B te muestra los movimientos en un rango de fechas de los materiales o de determinado material, esta transacciones es mas para el análisis de los movimientos contables y logísticos, es decir en esta se incluyen por ejemplo las actualizaciones de precio que se realizan en la MR21, como también los diferentes ajustes que puede realizar FI a determinado material; por eso esta se vuelve un poco compleja de comprender, pues si no das el rango de fechas adecuado pueda que los saldos iniciales y finales no sean iguales al de la mb53; yo generalmente la utilizo para analizar el comportamiento del precio, cuando el material maneja control de precio V.

How to handle inventory managment in BW

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328?QuickLink=index&overridelayout=true&5003637719724

  SAP BW 4hana DTP ABAP Filter Range using DTP Routine data: lv_date_low TYPE sy-datum, lv_date_high TYPE sy-datum, lv_date TYPE dats, lv_mo...