|
| |
| |
| |
|
|
|
| FreeSAP Business Warehouse(BW) Books,Faqs,Material |
| BI InfoObject,Master Data,Modeling,Business Warehouse, Errors,Reporting,Tables,Conversion Routine,Data Uploading,DataStore Objects,Infocube,InfoSets,Interview Questions,Modeling,MultiProvider,TCodes,Upgrade BI,VirtualProviders |
| Language: English |
| RSS Feeds for this Blog |
|
Statistics |
| Unique Visitors: 136 |
| Total Unique Visitors: 5743 |
| Visitors Out: 213 |
| Total Visitors Out: 213 |
|
|
|
| |
|
|
| |
|
| The benefits of SAP BW |
| 2008-08-09 02:17:36 |
SAP Business Warehouse is ships with "Business Content". It comes with ready-made extraction routines, meta-data, InfoCubes, information models, reports and channels that guarantee analysis and reporting capabilities out of the box. It closes the loop as it provide a seamless links to planning and execution applications that allow you to act instantly on the insight you gain to improve the performance of your business processes. It openness ensure that SAP BW is ideal for SAP R/3Æ and other SAP solutions but not limited to them. You can combine it easily with practically any internal or external data source, including existing data marts, with third-party reporting and analysis tools, or planning and execution applications. The flexibility of SAP BW is that it is a ready-to-go solution b...
|
| |
|
| SAP BW Cookbook |
| 2008-08-09 02:17:16 |
Extract from the BW Cookbook Volume 1: "The SAP Business Information Warehouse enables Online Analytical Processing (OLAP) to format the information of large amounts of operative and historical data. OLAP technologyenables multi-dimensional analyses according to various business perspectives. The preconfigured Business Information Warehouse Server for core areas and processes ensures information views within the entire enterprise." Extract from the BW Cookbook Volume 2: Settings In SAP (R/3) Source System STEP 1. Install Plug-In STEP 2. Defining Source System TRANSACTION CODE: SPRO -> SAP Ref. Img -> If R/3 system is 4.0B -> Cross Application components -> Distribution ALE -> Basic Settings -> set up logical system -> Maintain logical systems -> New ent...
|
| |
|
| Responsibilities of BW Data Architect |
| 2008-08-09 02:16:32 |
Responsibilities of an implementation project...For ex, Lets say If its a fresh implementation of BI or for that matter you are implementing SAP... First and foremost will be your requirements gathering from the client. Depending upon the requirements you will creat a business blueprint of the project which is the entire process from the start to the end of an implementation... After the blue print phase sign off we start off with the realization phase where the actual development happens... In our example after installing the necessary softwares, patches for BI we need to discuss with the end users who are going to use the system for inputs like how they want a report to look like and what are the Key Performance Indicators(KPI) for the reports etc., basically its a question and answer se...
|
| |
|
| The Three Layers of SAP BW |
| 2008-08-09 02:15:08 |
SAP BW has three layers: Business Explorer: As the top layer in the SAP BW architecture, the Business Explorer (BEx) serves as the reporting environment (presentation and analysis) for end users. It consists of the BEx Analyzer, BEx Browser, BEx Web, and BEx Map for analysis and reporting activities. Business Information Warehouse Server: The SAP BW server, as the middle layer, has two primary roles:• Data warehouse management and administration: These tasks are handled by the production data extractor (a set of programs for the extraction of data from R/3 OLTP applications such as logistics, and controlling), the staging engine, and the Administrator Workbench.• Data storage and representation: These tasks are handled by the InfoCubes in conjunction with the data manager, Metadata re...
|
| |
|
| SAP Data Warehouse |
| 2008-08-09 02:14:46 |
We have large amounts of historical sales data stored on our legacy system (i.e. multiple files with 1 million+ records). Today the users use custom written programs and the Focus query tool to generate sales'ish type of reports. We are wanting that existing legacy system to go away and need to find a home for the data and the functionality to access and report on that data. What options does SAP afford for data warehousing? How does it affect the response of the SAP database server? We are thinking of moving the data onto a scaleable NT server with large amounts of disk (10gb +) and using PC tools to access the data. In this environment, our production SAP machine would perform weekly data transfers to this historical sales reporting system. Has anybody i...
|
| |
|
| SAP Business Information Warehouse |
| 2008-08-09 02:14:23 |
Ever heard about apples and oranges. SAP/R3 is an OLTP system where as BIWis an OLAP system. LIS reports can not provide the functionality providedby BIW. -----Reply Message-----Subject: Business Information Warehouse Hello, The following information is for you to get more clarity on the subject:SAP R/3 LIS (Logistic Information System) consist of infostructures (whichare representation of reporting requirements). So whenever any event (goodsreciept, invoice reciept etc. ) takes place in SAP R/3 module, if relevantto the infostructure, an corresponding entry is made in the infostructures.Thus infostructures form the database part of the datawarehouse. Forreporting the data (based on OLAP features such drill-down, ab...
|
| |
|
| Use of manual security profiles with SAP BW |
| 2008-08-09 02:04:30 |
Our company is currently on version 3.1H and will be moving to 4.6B latesummer 2000. Currently all of our R/3 security profiles were createdmanually. We are also in the stage of developing and going live with theadd-on system of Business Warehouse (BW). For consistency, we have wishto use manual profiles within the BW system and later convert all of ourmanual security profiles (R/3 and BW) to profile generated ones. Is there anyone else that can shed any light on this situation? (Successor problems with using manual security profiles with BW?) Any feedback would be greatly appreciated. Thank you, -----Reply Message-----Subject: Use of manual security profiles with BW? (Business Informa...
|
| |
|
| What Is SPRO In BW Project? |
| 2008-08-09 02:02:37 |
1) What is spro?2) How to use in bw project?3) What is difference between idoc and psa in transfer methods? 1. SPRO is the transaction code for Implementation Guide, where you can do configuration settings.* Type spro in the transaction box and you will get a screen customizing : Execute Project.* Click on the SAP Reference IMG button. you will come to Display IMG Screen.* The following path will allow you to do the configuration settings : SAP Cutomizing Implementation Guide -> SAP Netweaver ->SAP Business Warehouse Information. 2. SPRO is used to configure the following settings :* General Settings like printer settings, fiscal year settings, ODS Object Settings, Authorisation settings, settings for displaying SAP Documents, etc., etc.,* Links to othe...
|
| |
|
| Main advantages of BW 3.0 over 2.1C |
| 2008-08-09 02:02:15 |
Here's a brief list, without detailed explanations :- - XML support for reading and writing metadata and data.- Web application designer: graphically design and publish web reports and web applications.- Open Hub Service for distributing data to other tables/systems on a schedule. It supports selection, projection, and aggregation. Integrated into the BW monitor.- Process Chains and graphical scheduler for automating complex processes. Supports branching, condition testing, etc. Enables you to schedule all admin functions in a graphical, drag-and-drop fashion, including extracts, index drops and rebuilds, activating data, compressing, rolling up to aggregates, etc.- Transactional ODS objects with read/write API.- Transfer rules for hierarchies.- Subtree insert and subtree update for hierar...
|
| |
|
| Pros and Cons of Web against BEX |
| 2008-08-09 02:01:55 |
Web reporting is faster then Excel, there is less overhead in executing Web reporting as opposed to Excel. (Whitepaper on SAP about this.) There is not anymore work in formatting or creation of templates then in comparison to workbooks. Query creation is the same as in BEX, so there is no new knowledge there. Yes, knowledge of HTML is needed, but if you use the standard CSS templates, you really don't need to know them unless you want to change them. But, if you can write queries or code ABAP, you can definitely learn basic HTML and CSS to customize reporting. Its not that hard. The learning curve for NEW users in Web Reporting vs.. BEX is actually considerably lower. Most people are very familiar with using a web browser, and IMOE I have found they pick up usage of web reporting much q...
|
| |
|
| API Functions Available In BEX |
| 2008-08-09 02:01:31 |
API functions available in BEX 3.x: 1. Function SAPBEXinitConnection(Optional newConnectionObj As Object) As BooleanSet up a connection to BW Server 2. Function SAPBEXgetConnection(Optional what As Integer) As VariantGet the existing connection object if already connected to BW server by help of BEX 3. Sub SAPBEXattachGIS(Optional refreshOnly As Boolean) Attach GIS-MAP (same as clicking the BEX-Toolbar button) 4. Sub SAPBEXpauseOn()In case you like to fire more than one API command (like two individual filter values) without immediate refresh 5. Sub SAPBEXpauseOff()After this command all of the commands called after SAPBEXpauseOn will be executed 6. Function SAPBEXsetVariables(varValues As Range) As IntegerSet variable Values for User to provide Pop-Up Filter selections (Filter dialogs wi...
|
| |
|
| Huge Performance Problems on SAP BW 3.10. |
| 2008-08-09 02:01:05 |
We have huge performance problems on SAP BW 3.10. (Oracle 9.2, AIX). Our users don't get the results of theirs queries, and they often have to log-off from sap when they use the bex analyzer . I have read the differents topics regarding this problem , and read the differents SAP notes. *The database statistics are refreshed every moring , after the data loads. (statistic for the fact table is always current, transaction db20) * Oracle Parameters are set according to SAP notes 632556. * Oracle indices are deleted and recreated every day * Fact table is partitioned * I have tried to change the read mode in RSRT but it didn't work I have checked the BW statistics (st03 and table RSDDSTAT). The database proportion is very high FOR ALL QUERIES (40 to 90%...
|
| |
|
| How to build an extractor? |
| 2008-08-09 02:00:35 |
Using SAP BW 2.1C and soon 3.0A we have to extract data from R/3 FI.Standard extractor can´t be used, since data need to be enhanced and go throug various routines before data contains all information needed in BW. Delta upload mechanism is needed.Where can information on- building a new extractor (including delta mechanism)- enhancing a standard extractor be found? Technically, programming a function module data source would be a modification. There's also a way that allows you to stay close to the standard, especially if you extract data from standard tables: In OLTP:1) Find out which change document object points to the table.2) Use the generic extractor to build a data source for _master data_ over the table.3) Use the "enhance extract structure" f...
|
| |
|
| COPA Extraction Steps |
| 2008-08-09 02:00:13 |
The below are the command steps and explanation. COPA Extraction -steps R/3 System1. KEB02. Select Datasource 1_CO_PA_CCA3. Select Field Name for Partitioning (Eg, Ccode)4. Initialise5. Select characteristics & Value Fields & Key Figures6. Select Development Class/Local Object7. Workbench Request8. Edit your Data Source to Select/Hide Fields9. Extract Checker at RSA3 & Extract BW1. Replicate Data Source2. Assign Info Source3. Transfer all Data Source elements to Info Source4. Activate Info Source5. Create Cube on Infoprovider (Copy str from Infosource)6. Go to Dimensions and create dimensions, Define & Assign7. Check & Activate8. Create Update Rules9. Insert/Modify KF and write routines (const, formula, abap)10. Activate11. Create I...
|
| |
|
| ODS infosource not showing up |
| 2008-08-09 01:59:47 |
To display export infosources under the Infosource hierarchy you need to do the following : 1. Right click the tree at the highest level (Infosources node) and then choose Insert Lost Nodes. 2. Also make sure that under Settings under the menu options you have selected the option to display generated objects for ODS . By default the setting is set to hide objects. And finally refresh your tree. You should be able to the infosources and the infopkgs. They might show up under Unassigned Nodes if you have not transferred the BW app component hierarchy in which case they show up under DM (Data Marts ) node....
|
| |
|
| The query could not be saved due to a problem in transport |
| 2008-08-09 01:59:27 |
After creating a query in BEX, you try and save the query, it gives you the following popup message: "The query could not be saved due to a problem in transport". Steps to correct the problem: 1. Within Adminstrator Workbench click on the Transport Connection tab in the Navigation Window on the left hand side. 2. Select the Request BEx button on the toolbar. 3. Create a transport. 4. Try to change the query again....
|
| |
|
| Query View Workbook |
| 2008-08-09 01:59:08 |
You formatted a query view ( By changing Fonts/column width etc ) and saved as workbook in your favorites in the Browser. When you execute the workbook thru the browser you get the format that has been saved. However, you loose the format when you click the Refresh Button. How to set permanent settings so that formatting remains same as has been designed in the workbook? You can do this :- In Excel using BW, you have what I categorize as 2 different types of cells. You have "Excel" Cells and "BW" Cells. You can determine which you are in by selecting a cell and right mouse clicking. If you get the BW options (Drilldown, Swap, Insert.....) then you are in a BW Cell. If you get the standard (Cut, Copy, Paste) you are in the Excel Cells. If you are formatting an Excel Cell, Format using the ...
|
| |
|
| Stop a scheduled infopacket |
| 2008-08-09 01:58:46 |
I have tried using SM50 to stop a process that has been running forquite sometime. How do I kill a scheduled infopacket. Thanks, -----Reply Message-----Subject: RE: Stop a scheduled infopacket Hello select the Process and press F9. Or can kill the same from the OS levelusing the UNIX command kill -9 . Happy going.. -----Reply Message-----Subject: RE: Stop a scheduled infopacket Kill the job on the R/3 side by using SM37 for ALEREMOTE. Hope this helps... Thanks. -----End of Message-----...
|
| |
|
| BEX Query Authorizations |
| 2008-08-09 01:58:28 |
We are have authorization issues with Querries. We have created a genericRole that has some Standard Query's for our Company attached to this Role.We give access to this role to our user community. The problem we arehaving is that the users can Execute the querries and what they are supposeto do is only Save the Workbook to there favorites. We are running acrossa problem because some of the users are saving the workbook as existingworkbook. So when they do this it wipes out the Query in that Role. Howcan I stop users from overlaying the MASTER Query. There has to be a waythat you can protect a query so that it cannot be changed. Because wehave generic querries that are being used throughout our company, I need tobe able to protect the query so that it can only be saved to u...
|
| |
|
| SAP Console |
| 2008-08-09 01:58:03 |
Subject: SAPConsole Good Morning to all Can I use the standard SAPConsole for Inventory Management relatedtransactions also. Examble: Movement 103 /105 etc. With Best Regards -----Reply Message-----Subject: RE: SAPConsole Can you please explain me, What is a SAP Consule? -----Reply Message-----Subject: RE: SAPConsole Dear: SapConsole is a standard SAP tool which was offered as of 46B (but isbackwards compatible to earlier releases) which translates GUI screens intothe Character based screens that are used with most handheld Radio Frequencydevices used in Warehouses. Beginning in 46B, SAP provided standard transactions which could be used inWarehouse Management, specifically designed to be used with Radio Frequencydevices. As far as I know the only one t...
|
| |
|
| Delete unwanted Objects in QA system |
| 2008-08-09 01:57:30 |
I have deleted unwanted Update rules and InfoSources (that have already been transported to QA system) in my DEV system. How do I get them out of my QA system? I cannot find the deletions in any transports that I have created. Although they could be buried somewhere. Any help would be appreciated. I had the same problem with you. And I have been told there is a way to delete the unwanted objects. You may request the Basis team to open up test box temporarily to remove the obsolete Update rules and InfoSources. Remember to delete the request created in test after you have removed the Update rules and InfoSources.When I tried to delete the master data, get the following message"Lock NOT set for: Deleting master data attributes". What I need to do in order to...
|
| |
|
| LO Cockpit Step By Step |
| 2008-08-09 01:57:06 |
Here is LO Cockpit Step By Step LO EXTRACTION - Go to Transaction LBWE (LO Customizing Cockpit) 1). Select Logistics Application SD Sales BW Extract Structures 2). Select the desired Extract Structure and deactivate it first. 3). Give the Transport Request number and continue 4). Click on `Maintenance' to maintain such Extract Structure Select the fields of your choice and continue Maintain DataSource if needed 5). Activate the extract structure 6). Give the Transport Request number and continue - Next step is to Delete the setup tables 7). Go to T-Code SBIW 8). Select Business Information Warehousei. Setting for Application-Specific Datasourcesii. Logisticsiii. Managing Extract Structuresiv. Initializationv. Delete the content ...
|
| |
|
| Differences Among Query, Workbook and View |
| 2008-08-09 01:56:40 |
Many people are confused by the differences among: Query, Workbook, and View. Here are my thoughts on the subject: A query definition is saved on the server. Never anywhere else. Although people say a workbook contains a query (or several queries); it does not. It contains a reference to a query. The workbook can be saved on the server; or anywhere else that you might save an Excel workbook. What happens if someone changes the query definition on the server? Answer: the next time you refresh the query in the Excel workbook, the new query definition replaces the old query definition in the workbook. Maybe. It depends on what change was made. For example, if someone added a Condition to the query definition, the workbook will be virtually invisible to this. The Condition is available; but...
|
| |
|
| Customer Exit Variable In Bex |
| 2008-08-09 01:56:11 |
The customer exit works at: 1. Extraction side After enhancing datasource in RSA6 we need to populate those enhanced fields in that case we have to create a project in cmod transaction and select the Enhancement assignment RSAP0001 and select the appropriate FM and need to write the select statement in the appropriate include. EXIT_SAPLRSAP_001 - Transaction data EXIT_SAPLRSAP_002 - Master data EXIT_SAPLRSAP_003 - Text EXIT_SAPLRSAP_004 - Hierarchy The above things we need to do in Source System side Ex: R/3 2. Reporting side We need to write the user-exit to populate Reporting related variables in the Enhancement assignment RSR00001 and select the FM EXIT_SAPLRRS0_001 and then in the include ZXRSRU01 we need to write the code. These are helpful especial...
|
| |
|
| Namespaces for SAP BI Objects |
| 2008-08-02 03:55:09 |
Use The following namespaces are generally available for BI objects: SAP-delivery (Business Content) namespace: · Objects beginning with 0 · Generated objects in the DDIC beginning with /BI0/ InfoCube 0SALES, fact table /BI0/FSALES Customer namespace: · Objects beginning with A-Z · Generated objects in the DDIC beginning with /BIC/ InfoCube SALES, fact table /BIC/FSALES Partner-specific namespace and customer-specific namespace: · Object begins with /XYZ/ (example) Special SAP namespaces for generated objects: · The prefixes 1, 2, 3, 4, 6, 7, 8 are required in BW for DataSources and InfoSources in special SAP applications. · The prefix 9A is required for the SAP APO application. When you create your own objects...
|
| |
|
| SAP BI Modeling Data Flow Display |
| 2008-08-02 03:54:38 |
Use In the Modeling functional area of the Data Warehousing Workbench, you can use a graphic to display the dataflow of objects in BI. This illustrates the connections and dependencies between individual objects. You can call this graphic for InfoProviders and InfoSources. Integration From the object tree, you can call this graphic for an object by choosing Display Dataflow in the context menu (right mouse click) of the object. The graphic is displayed in the right-hand screen area of the Data Warehousing Workbench. All related objects and rules are displayed which precede this object in the data flow. For InfoSources with flexible update, all related objects are displayed up to and i...
|
| |
|
| SAP BI Modeling DataSource |
| 2008-08-02 03:52:24 |
Definition Set of fields that provide the data for a business unit for data transfer into BI. From a technical viewpoint, the DataSource is a set of logically-related fields that are provided to transfer data into BI in a flat structure (the extraction structure), or in multiple flat structures (for hierarchies). There are four types of DataSource: ● DataSource for transaction data ● DataSource for master data ○ DataSource for attributes ○ DataSource for texts ○ DataSource for hierarchies Use DataSources supply the metadata description of source data. They are used for extracting data from a source system and for transferring data into BI. The following image illustrates the role of the DataSource in the BI data flow: The data is loaded into BI f...
|
| |
|
| SAP BI Modeling Functions for DataSources |
| 2008-08-02 03:51:47 |
Use You can execute the following DataSource functions in the object tree of the Data Warehousing Workbench. The functions available differ depending on the object type (DataSource – RSDS, DataSource 3.x – ISFS) and source system: ● In the context menu of an application component, you can execute the following functions: ○ For both object types: Replicate metadata for all DataSources that are assigned to this application component. ○ For object type RSDS: Create DataSource. ● In the context menu of a DataSource, you can execute the following functions: ○ For both object types: Display, delete, manage, create transformation, create data transfer process, create InfoPackage. ○ For object type RSDS: Change, copy (however, not with an SAP source s...
|
| |
|
| DataSource Maintenance in SAP BI Modeling |
| 2008-08-02 03:50:23 |
In DataSource maintenance in BI you can display DataSources and 3.x DataSources. You can create or change DataSources for file source systems, UD Connect, DB Connect and Web services on this BI interface. In DataSource maintenance, you can edit DataSources from SAP source systems. In particular, you can specify which fields you want to transfer into BI. In addition, you can determine properties for extracting data from the DataSource and properties for the DataSource fields. You can also change these properties. You call DataSource maintenance from the context menu of a DataSource (Display, Change) or, if you are in the Data Warehousing Workbench, from the context menu of an application component in an object tree (Create DataSource). Alternati...
|
| |
|
| Creating DataSources for File Source Systems SAP BI Modeling |
| 2008-08-02 03:49:58 |
Use Before you can transfer data from a file source system, the metadata (the file and field information) must be available in BI in the form of a DataSource. Prerequisites Note the following with regard to CSV files: ● Fields that are not filled in a CSV file are filled with a blank space if they are character fields and with a zero (0) if they are numerical fields. ● If separators are used inconsistently in a CSV file, the incorrect separator (which is not defined in the DataSource) is read as a character and both fields are merged into one field and may be shortened. Subsequent fields are no longer in the correct order. Note the following with regard to CSV files and ASCII files: ● The conversi...
|
| |
|
| Creating DataSources for UD Connect SAP BI Modeling |
| 2008-08-02 03:49:09 |
Use To transfer data from UD Connect sources into BI, metadata (the information about the source object and source object elements) has to be available in BI in the form of a DataSource. Prerequisites You have connected a UD Connect source system. Note the following background information: Using InfoObjects with UD Connect Data Types and Their Conversion Using SAP Namespace for Generated Objects Procedure You are in the DataSource tree in the Data Warehousing Workbench. ... 1. Select the application components in which the DataSource is to be created and choose Create DataSource. 2. In the next screen, enter a technical name for the DataSource, select the type of the DataSource and choose Copy. The DataSource maint...
|
| |
|
| SAP BI Modeling Creating DataSources for DB Connect |
| 2008-08-02 03:48:35 |
Use Before you can transfer data from a database source system, the metadata (the table, view and field information) must be available in BI in the form of a DataSource. Prerequisites See Requirements for Database Tables or Views You have connected a DB Connect source system. Procedure You are in the Data Warehousing Workbench in the DataSource tree. ... 1. Select the application components in which you want to create the DataSource and choose Create DataSource. 2. On the next screen, enter a technical name for the DataSource, select the type of DataSource and choose Copy. The DataSource maintenance screen appears. 3. Go to the General tab page. a. Enter descriptions for th...
|
| |
|
| Creating DataSources for Web Services SAP BI Modeling |
| 2008-08-02 03:48:02 |
Use In order to transfer data into BI using a Web service, the metadata first has to be available in BI in the form of a DataSource. Procedure You are in the DataSource tree in the Data Warehousing Workbench. ... 1. Select the application components in which the DataSource is to be created and choose Create DataSource. 2. In the next screen, enter a technical name for the DataSource, select the type of the DataSource and choose Copy. The DataSource maintenance screen appears. 3. Go to the General tab page. a. Enter descriptions for the DataSource (short, medium, long). b. If necessary, specify whether the DataSource may potentially deliver duplicate data records within a request...
|
| |
|
| Emulation, Migration and Restoring DataSources SAP BI Modeling |
| 2008-08-02 03:47:31 |
Emulation 3.x DataSources (object type R3TR ISFS) exist in the BI database in the metadata tables that were available in releases prior to SAP NetWeaver 2004s. The emulation permits you to display and use the DataSource 3.x using the interfaces of the new DataSource concept. The DataSource (R3TR RSDS) is instantiated from the metadata tables of the DataSource 3.x. You can display a 3.x DataSource as an emulated DataSource in DataSource maintenance in BI. You can also model the data flow with transformations for an emulated DataSource if there are already active transfer rules and a transfer structure and a PSA for the 3.x DataSource. Once you have defined the objects of the data flow, you can set the processes for data transfer (loading process using InfoPackage and data transfer proces...
|
| |
|
| Using Emulated 3.x DataSources SAP BI Modeling |
| 2008-08-02 03:46:37 |
Use You can display an emulated 3.x DataSource in DataSource maintenance in BI. Changes are not possible in this display. In addition, you can use emulation to create the (new) data flow for a 3.x DataSource with transformations, without having to migrate the existing data flow that is based on the 3.x DataSource. We recommend that you use emulation before migrating the DataSource in order to model and test the functionality of the data flow with transformations, without changing or deleting the objects of the existing data flow. Note that use of the emulated Data Source in a data flow with transformations has an effect on the evaluation of the settings in the InfoPackage. We therefore recommend that you only use the emulation in a development or test system. Constraints An emulated...
|
| |
|
| Migrating 3.x DataSources SAP BI Modeling |
| 2008-08-02 03:46:12 |
Use To take advantage of the new concepts in a data flow using 3.x objects, you must migrate the data flow and the 3.x objects it contains. Procedure ... 1. In the original system (development system), in the Data Warehousing Workbench, choose Migrate in the context menu of the 3.x DataSource. 2. If you want to restore the 3.x DataSource at a later time, choose With Export on the next screen. 3. Specify a transport request. 4. Transport the migrated DataSource to the target system (quality system, productive system). 5. Activate the DataSource in the target system....
|
| |
|
| Migrating 3.x DataSources (UD Connect, Web Service) SAP BI Modeling |
| 2008-08-02 03:45:49 |
Use To take advantage of the new concepts in a data flow using 3.x objects, you must migrate the data flow and the 3.x objects it uses. 3.x XML DataSources and 3.x UD Connect DataSources cannot be migrated in the standard way because the 3.x objects are created in the Myself system and in the new data flow the DataSources need to be created in separate source systems for Service">Web Service and UD Connect. However, you can nevertheless “migrate“ a 3.x DataSource of this type. This involves copying the 3.x DataSource into a source system. Prerequisites The UD Connect source system and the Web service source system are available. The UD Connect source system uses the same RFC destina...
|
| |
|
| Restoring 3.x DataSources SAP BI Modeling |
| 2008-08-02 03:45:04 |
Use In the original system, you can restore 3.x DataSources from DataSources that were migrated in the standard way (SAP source system, file, DB Connect). You use a transport to restore the 3.x DataSource in the target system. Only use this function if unexpected problems occur with the new data flow after migration and these problems can only be solved by restoring the data flow used previously. Prerequisites You exported and archived the relevant 3.x objects when you migrated the 3.x DataSource. Procedure ... 1. In the original system (development system), in the maintenance for the migrated DataSource (transaction RSDS), choose DataSource ® Restore. 2. Specify a transport request. 3. If required, delete the dependent transformation (R...
|
| |
|
| SAP BI Persistent Staging Area |
| 2008-08-02 03:44:43 |
Purpose The Persistent Staging Area (PSA) is the inbound storage area for data from the source systems in the BI system. The requested data is saved, unchanged from the source system. Request data is stored in the transfer structure format in transparent, relational database tables of the BI system in which the request data is stored in the format of the DataSource. The data format remains unchanged, meaning that no summarization or transformations take place, as is the case with InfoCubes. When loading flat files, the data does not remain completely unchanged, since it is adjusted by conversion routines if necessary (for example, the date format 31.21.1999 is converted to 19991231 in order to ensure uniformity of data). The possible coupling of ...
|
| |
|
| DB Storage Parameters BI Persistent Staging Area |
| 2008-08-02 03:44:18 |
Use You can maintain database storage parameters for PSA tables, master data tables, InfoCube fact- and dimension tables, and DataStore object tables. Use this setting to determine how the system handles the table when it creates it in the database: · Use Data Type to set in which physical database area (tablespace) the system is to create the table. Each data type (master data, transaction data, organization- and Customizing data, customer data) has its own physical database area, in which all tables assigned to this data type are stored. If selected correctly, your table is automatically assigned to the correct area when it is created in the database. We recommend you use separate tablespaces for very large tables. You can find informa...
|
| |
|
| |
 |
