Simplification List for SAP BW/4HANA (SAP Release 18th June’ 2018)

This document is for the consultant who is working on converting the system from SAP Business Warehouse to SAP BW/4HANA.
Conversion Type: in-place conversion
System: SAP BW 7.5 SP5, powered by SAP HANA or higher
Program: RS_B4HANA_CONVERSION_CONTROL to determine which objects are available in or can be converted to SAP BW/4HANA
BW4 Transfer Tool: Program RS_B4HANA_TRF or STC01/STC02 and select Task List as SAP_BW4_TRANSFER_INPLACE

Below are the list of Objects which are not available or to be converted in SAP BW4/HANA supported objects:
1.      SAP BW Accelerator (BWA) is not available.
2.      The BW/BI Add-on for SAP GUI i.e. front-end tools are not available
Ø  BEx Query Designer
Ø  BEx Web Application Designer
Ø  BEx Analyzer
Ø  BEx Enterprise Report Designer

SAP BW – Data Warehousing:
1.      InfoObject Catalogs are not available. It has been replaced by InfoAreas.
2.      The following types of InfoObjects are not available in SAP BW/4HANA:
Ø  Characteristics that use 0RECORDMODE as an attribute
Ø  Characteristics that are enabled for real-time-data acquisition
Ø  Characteristics that use class CL_RSR_REMOTE_MASTERDATA as their master data read class
Ø  Key figures of data type "Date" or "Time" with aggregation SUM
3.      The SAP BW DataStore Object (classic) is not available in SAP BW/4HANA. It can be converted to a DataStore Object (advanced).
4.      InfoCube is not available in SAP BW/4HANA. It can be converted to a DataStore Object (advanced) (ADSO).
5.      InfoCubes of type VirtualProvider or HybridProvider cannot be converted.
6.      InfoSet is not available in SAP BW/4HANA. It can be converted to a CompositeProvider.
7.      The SAP BW MultiProvider is not available in SAP BW/4HANA. It can be converted to a CompositeProvider.
8.   VirtualProvider &HybridProvider is not available.
9.   Aggregates are not available in SAP BW/4HANA.
10.   Semantically Partitioned Objects (SPO) are not available.
11.   Data Transfer Processes created before SAP BW release 7.5 SP 4 are storing request IDs in as meta data for each data load into DataStore objects (advanced). However, request IDs are not available in SAP BW/4HANA.
12.   The central Composite Provider created with transaction RSLIMO is not available.
13.   The analytical index (AINX), created in the APD (Analysis Process Designer) or directly in transaction RSDD_LTIP, is not available in SAP BW/4HANA.
14.   External SAP HANA views of type Attribute or Analytic View are not available in SAP BW/4HANA.


SAP BW – Data Staging:
1.   Few limitations on Data Transfer Processes (DTP) in SAP BW/4HANA:
Ø  The persistent staging area service (PSA) is no longer available in SAP BW/4HANA. As of that, the following limitations apply:
Ø  DTPs of type "Real-time Data Acquisition" or "Direct Access" are not available.
2.   The persistent staging area service (PSA) and InfoPackages are not available.
3.   InfoPackage Groups are not available in SAP BW/4HANA.
4.   The following object types related to 3.x data flows are not available in SAP BW/4HANA:
Objects should be replaced:
a.      Update Rules
b.      3.x InfoSources
c.      Transfer Rules
d.      3.x DataSources
e.      Transfer and Communication Structures
Objects should be adapted:
a.      InfoPackages
b.      Process Chains
c.      Process Chain Variants
d.      VirtualProviders based on 3.x InfoSource (Cube Type=V, Cube Sub-type=S)
The 3.x data flow migration tool (transaction RSMIGRATE) is therefore also not available.
5.   The Service API for DataSources (S-API) is not available in SAP BW/4HANA. Therefore, the following types of DataSources are not available:
·        Generic DataSources (maintained in transaction RSO2)
·        Export DataSources (8*, generated from transaction RSA1)
·        Technical Content DataSources (0TCT*, activated via transaction RSA1)
6.   The Myself Source System needs to be replaced by an ODP Source System with BW context.
7.   The SAP and BW Source Systems based on Service API (S-API) are not available.
7.   Source systems of type "DB Connect", "UD Connect", SAP Data Services" or "External System (Partner ETL)", "Web Service" are not available in SAP BW/4HANA.
8.   The following Open Hub Destinations are not available:
·        3.x destinations (InfoSpokes)
·        Destination type "Third Party Tool"
9.   InfoSpoke, Real-Time Data Acquisition (RDA) is not available in SAP BW/4HANA.
10.   Nearline Storage (NLS) Partner Solutions are not available.
11.   The classic request and status management (RSSM) based on Request IDs (0REQUID) is not available with SAP BW/4HANA. Therefore, interfaces relying on RSSM are not available either (like APO write interface, open "yellow" requests, BAPI_ISREQUEST_GETSTATUS, etc.). The same applies to functionality associated with it such as archiving request administration data via archiving object BWREQARCH.
12.   The Hierarchy/Attribute Change Run is not required in SAP BW/4HANA.

SAP BW – Analytic Manager:
1.   Certain SAP BW Queries are not available in SAP BW/4HANA:
·        Queries in 3.x Format
·        Queries with Calculations Before Aggregation
·        Queries with Constant Selection with Append
·        Queries that reference technical characteristic Request ID (0REQUID)
2.   The SAP HANA Index for a VirtualProvider and SAP HANA Index for a Query (Snapshot) created via transaction RSDDB are not available.
3.   Personalization in SAP Business Explorer (BEx) is not available in SAP BW/4HANA. The corresponding classic DataStore Objects (0PERS*) are not available.
4.   The SAP BW Data Federator Facade is not available.

SAP BW – Agile Information Access:
1.   SAP BW Workspaces are a fully supported functionality for agile information access.
2.   The following SAP Business Explorer (BEx) objects are not available:
·        BEx Workbooks
·        BEx Web Item (Format SAP BW 7.x)
·        BEx Web Template (Format SAP BW 7.x)
·        BEx Broadcast Settings
·        BEx Precalculation Server
3.   The following front-end objects are not available:
·        SAP Crystal Reports (published to SAP BW)
·        SAP Xcelsius Dashboards (published to SAP BW)
·        BW Enterprise Reports
4.   The Easy Query interface is not available.
5.   Business Planning & Simulation (BW-BPS) applications are not available.
6.   Objects related to Business Planning & Consolidation functionality are not available with core SAP BW/4HANA.



Comments

Post a Comment

Popular posts from this blog

Unforeseen Issue during SAP BW Data Flow Migration

Purpose : To migrate SAP BW Data Flow from 3.x to 7.x version. Tool :  RSMIGRATE (provided by SAP) SAP makes our life easy by providing a great tool to migrate the BW 3.x version to 7.x version automatically. It also provides supportive SAP Notes/KBA for the known errors and issues. However, there were undocumented few issues which we came across during our migration activities. In this post, we will share 'unforeseen issues' and their resolutions which were mostly manual efforts. 1.     Update Rule -  Return Table Logic:  In SAP BW 3.x version we have  Return Table logic  to replicate the source record into multiple record based on key figures as per the requirement. However, in  Transformation  this return table is unsupported and cannot be converted by RSMIGRATE tool automatically.        We need to correct it manually by writing the split logic in end routine.        Here is the key, which we can use- https://www.sdn.sap.com/irj/servlet/prt/portal/p
Read more

Simple Program to Check Active Requests in ODSOs / ADSOs

In this document, we will create a program to check the whether an ODSO/ADSO is having an Active request or not. Scenario : We have BW data flow which loads data from the Source System to DSO and from DSO to further multiple targets, and at the end of the Process Chain the request should get deleted from the source. Here, we have a case if someone did an ad-hoc load from Source System to DSO and subsequently to targets, and forgot to delete the request from the DSO. This leads to duplicate data into Targets in next Process Chain run. Solution : To take care of the above case we can keep a checkpoint in the Process Chain which will monitor the request in DSO.  If an existing request is found in DSO, then a notification can be displayed and we can go ahead and remove it manually.  Case1 : When we have Extraction Layer as ODSO . As we all know SAP has given a Standard Function Module RSSM_ICUBE_REQUESTS_GET which can be used to get the DTP requests which are presen
Read more