Is it compulsory to create ODS in BW?

Hi all,
Is it compulsory to create ODS in BW? Without creating ODS can we load the all types of data sources into BW Cubes?
By creating ODS's unnecessarily wasting the disc space and effort.
Thanks,
Gana

Hi,
It all depends on the scenerio,if the scenario requires the ODS then we use it.In most of the times it is used as Back up data.
Say for example.YThere is some change in the KFs calcluations.
Data is loaded from PSA-->Cube and the data for some historical data for some month needs to be loaded ,so here we cant always load from R3-ECC.Data in PSA is deleted on monthly or 21 days basis.TO have a back up,we go for DSO,when we have a DSO we can delete the data from Cube go for Recalclulation of KFs and Reload data from DSO to Cube.
also in Inventory scenarios it is diffiucult to have DSO as we have Non cumulative KFs so we go for Directly Cubes.
Hope u got it......
Rgds
SVU123
Edited by: svu123 on Jul 26, 2010 8:16 PM

Similar Messages

SAP BW ERROR OCCURS WHILE CREATING ODS OBJECT

HI TO SAP BW GURUS
AFTER CREATING ODS OBJECT,AND ODS OBJECT STRUCTURE,WHILE ACTIVATING THE STRUCTURE I AM GETTING MESSAGE AS
<b>message : STDO:LOG COULDNOT BE WRITTEN ON OUTPUT DEVICE T</b>
COULD ANYONE PLS TELL ME HOW TO RECTIFY THT
VENKAT

Read the information message carefully. Then proceed, if you intend to have custom "standard" texts (sort of an oxymoron, but everyplace I've been does this)...
If you are working in a customer system, only create standard texts using the following naming convention:
Initial letter Y or Z in the text name with any text ID
or
Initial letter Y or Z in the text ID with any text name

Is there any simple way to create ods files (OpenOffice Calc)?

Is there any simple way to create ods files (OpenOffice Calc) using ResultSet (from java.sql)?

Mabe, you can create CVS files (plain text) Ej...
====test.cvs=====
1, "aaa"
2, "bbb"
3, "ccc"
===============
Using a "BufferedWriter"

Creating ODS in BI 7.0

Can anyone tell me the procedure to create ODS in BI 7.0 ?
Thanks in advance.
Srini

1.      Select the InfoArea that you want to assign the DataStore object to, or create a new InfoArea. Choose Modeling ® InfoProvider ® Create InfoArea.
       2.      In the context menu of the InfoArea, choose Create DataStore Object.
       3.      Specify a name and a description for the DataStore object, and choose This graphic is explained in the accompanying text Create.
If you want to create a copy of an existing DataStore object, specify the DataStore object that you want to use as a template.
You get to the DataStore object maintenance screen.
       4.      Adding InfoObjects:
On the left-hand side of the screen, there are various templates to choose from. These give you a better overview of a particular task. For performance reasons, the default setting is an empty template. You use the pushbuttons to select different objects as templates.
On the right side of the screen you define the DataStore object. Using the drag and drop function, assign the InfoObjects in the key fields and in the data fields. You can select several InfoObjects at once. The system assigns navigation attributes automatically. These navigation attributes can be switched on to analyze data in the Business Explorer. If the navigation attributes are switched on, they are also displayed in the transformation (only if the DataStore object is the source) and can be updated.
Or:
You are also able to insert InfoObjects without selecting a template in the left half of the screen. This is useful if you know exactly which InfoObjects you want to include in the DataStore object. To do this, choose Insert InfoObjects in the context menu for the node for key fields or data fields. In the dialog box that appears, you can enter and transfer up to ten InfoObjects directly and or you can select them using input help. You can use drag and drop to reassign them.
Note
There has to be at least one key field and one data field.
Additional restrictions:
-         You can create a maximum of 16 key fields (if you have more key fields, you can merge (concatenate) fields into one key field using a routine).
-         You can create a maximum of 749 fields.
-         You can use 1962 bytes (minus 44 bytes for the change log).
-         You cannot include key figures as key fields.
       5.      In the context menu of the Data Fields folder you can Insert New Hierarchy Nodes. In this way you can sort the data fields in a hierarchy. You then get a better overview of large quantities of data fields in query definition.
       6.      Under Settings, you can make various settings and define the properties of the DataStore object.
       7.      Under Indexes, call the context menu to create secondary indexes. This improves the load performance and query performance of the DataStore object. The system automatically creates primary indexes.
If the values in the index fields uniquely identify each record in the table, select Unique Index from the creation dialog box. Errors can occur during activation if the values are not unique.
The system specifies the number of each index. To create a folder for the indexes, choose Continue from the dialog box. Now you can transfer the required key fields into the index folder using drag and drop.
You can create a maximum of 16 secondary indexes. The system also transports these automatically.
       8.      Use This graphic is explained in the accompanying text Check to make sure that the DataStore object is consistent.
       9.      Save the DataStore object and activate it. When you activate the DataStore object, the system generates an export DataSource. You use this to update the DataStore object data to further InfoProviders.

How to create ODS in SAP BW

Hi All,
    <b>can anybody, tell me the steps to create ODS object in SAP BW</b>
Thanks in Advance
Regards
M A Mubeen

Hi Mohammad,
1.      Select the InfoArea to which the new ODS object is to be assigned, or create a new InfoArea. Choose Modeling ® InfoProvider ® Create InfoArea.
       2.      Choose Create ODS Object in the context menu for the InfoArea.
       3.      Specify a name and a description for the ODS object, and choose Create.
If you want to create a copy of an existing ODS object, specify the ODS object that you want to use as a template.
You get to the ODS object maintenance screen.
       4.      Transferring InfoObjects:
On the left side of the screen, there are various templates to choose from, which allow you to get a better overview in relation to a particular task. For performance reasons, the default setting here is an empty template. Using the pushbuttons, select an InfoSource (only the InfoObjects for the communication structure of the InfoSource are displayed), an InfoCube, an ODS object, or an InfoObject catalog.
On the right side of the screen you define the ODS object. Using the Drag&Drop function, assign the InfoObjects in the key fields and in the data fields. It is possible to select several InfoObjects at once. The system assigns navigation attributes automatically. These navigation attributes can be switched on for reporting in BEx.
Or:
You are also able to insert InfoObjects without selecting a template in the left half of the screen. This is useful if you know exactly which InfoObjects you want to include in the ODS object. To do this, choose InfoObjects to Insert in the context menu for the node for key fields or data fields. In the dialog box that appears, you can enter and transfer up to ten InfoObjects directly or you can select them using input help. You can still reassign these by using Drag&Drop.
There has to be at least one key field and one data field.
Additional restrictions:
-         You can create a maximum of 16 key fields (if you have more key fields, you can combine fields using a routine for a key field (concatenate).)
-         You can create a maximum of 749 fields
-         You can use 1962 bytes (minus 44 bytes for the change log)
-         You cannot include key figures as key fields
       5.      Using Settings, you can make various settings and define the properties of the ODS object. See Settings for ODS Objects.
       6.      Under Indexes, you can create secondary indexes by using the context menu in order to improve the load and query performance of the ODS object. Primary indexes are created automatically by the system.
If the values in the index fields uniquely identify each record in the table, select Unique Index from the dialog box. The description of the indexes is specified by the system. To create a folder for the indexes, choose Continue from the dialog box. Now you can transfer the required key fields into the index folder using Drag&Drop.
You can create a maximum of 16 secondary indexes. These are also transported automatically.
For more information, see Indexes
       7.      Use Check to make sure that the ODS object is consistent.
       8.      Save the ODS object, and activate it. Upon activation, an export DataSource is also created that can be used to further update the ODS object data to further data targets.
For the next step of creating update rules refer the below link
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a64c6e07211d2acb80000e829fbfe/content.htm
Assign points if useful..

Is it compulsory to create a factory calendar or not

is it compulsory to create a factory calendar or not

Hi Eswar,
Factory calendar needs to be maintained if you're using some logistics module that require factory calendar.
(Generally for running MRP - Material resource planning, etc. factory calendar maintenance is a must)
Re: Difference between holiday calendar and factory calendar
Regards,
Dilek

How to create ods object with overwrite option

Hi all,
I have two ods objects for Billing and Delivery and one cube for Sales.
Billing and Delivery ODS objects are based on item level data source while sales cube is based on Schedule line level data source.
Now i want to create a new ODS object which will get the data from these there object and update the ods object.Basically i want all the sales order attributes and billing quantity and delivered quantity from the ODS objects.
how to update the new ods object in overwrite mode ??/
Regards,
Viren.

HI,
yes OK but what i mean is that (you might have a perfect reason for this) normally it's nota good idea to have an info cube as a data source (for Performance, look-up reasons etc). If your goal is to load Billing/Delivery/Sales data into one ODS, then make sure that you model this correct.
If you want to use the ODS'es as data sources I would recommend you to use and ODS as data source also for the Sales data.
Kind regards
/martin

Sales office and sales group compulsory when creating a sales order

Hi,
When creating a new sales order, I would like to have the sales office and sales group compulsory.
Does anyone know where is the customizing point?
Thanks for your help,
Ronan

Dear Ronan,
Spro --> Img --> Sales and Distribution --> Basic Functions --> Log of Incomplete items --> Define Incompleeness Procedure (T. Code: OVA2)
Here, Select Group as A - Sales Header
and double-click: Procedures (left hand Dialog Structure).
On to next screen, select Incompleteness Procedure "11" and double click: Fileds (left hand Dialog Structure).
On to next screen, include Table-Filed as:
1. VBAK - VKBUR (for Sales Office) and
2. VBAK - VKGRP (for Sales Group)
for both the entries, select Scr. as "KKAU" and Status as 01 and check Warning.
Note: To make changes in to InCompleteness Procedure, click: (CTRL+F1)
Recommendation: Please save chnaged Incompleteness Procedure as Z - procedure; to avoid changes in to Standard Procedure.
Now,
Spro --> Img --> Sales and Distribution --> Basic Functions --> Log of Incomplete items --> Assign Incompleeness Procedure --> Assign procedures to the sales document types (T. Code: VUA2)
Here, assign your Order type (say, OR) to your Incompleteness Procedure (say, Z - Procedure)
Check Field: IC-Dialog as per requirement (Clck the field and press F1, to read its usage).
Now, Go to, T. Code: VOV8; and select your Sales Doc. Type (say, OR).
Within the Sales Doc., Assign your defined Incompleteness Procedure in to:
Tab: Transacton Flow --> Field: Incompl.proced.
Note: To enable screen, for changes, press (CTRL+F4).
Best Regards,
Amit

How to avoid QM status for a newly created ODS Request be a Warning

Hi Experts,
I AM using 3.5
When I Execute my infopackage lo load a complete load data for an ODS, the QM status of the Request is a warning.
The monitor says no problem or warn for the load.
I can manually turn it into green and activate the data but i can not put it all in a process chain c'ause the activation can not be done without the manual turning into green.
Is there any step in the chain that can turn ir into green or a way to set it created in green? In the IP i have the warnings threatment as judged to be succesful...
Thanks!!!

Hi,
If you want to use an ODS object as a data source for another ODS object or InfoCube, you have to make sure that the data is of good quality, and that it is active in the system.
If you choose the main menu path Environment ® Automatic Request Processing, the system automatically sets the quality status to OK after the data has been loaded into the ODS object. This option must be switched on. There is also the option of activating and updating ODS data automatically. Here, data that has been given the quality status OK is transferred from the activation queue into the active data table, and the change log is updated. The data is then updated into the connected data targets.
http://help.sap.com/saphelp_nw04/helpdata/en/fb/0025391d4f000be10000000a114084/frameset.htm
Please do the above , for more clarity please go through the link give . it is nothing to do other than setting quality status ok
Thanks
BVR

Problem in F4 help while creating ODS queries

When one tries to create a query on ODS then the F4 help option hangs up and never comes back.
Have referred SAP Note 984229 and 955990 already.
System : SAP BI 7.0
SPS: 13
Database : Oracle 10G
Thanks and Regards
Nidhi

At first, I would suggest you try with VL02 Tcode rather doing for enjoy transactions.
Updation of Z table should be sync with your PGI transaction. Here the INSERT/UPDATE should in PERFORM ON COMMIT so the both transaction and Z table will be in sync.
what is the error you are getting for first time execution? Do you need commit work before call transaction?
Regds
Manohar

How to create ODS based on a table (e.g. TCURR)

Hello!
I need to have access to V_TCURR in my BEx reports, cause I want to show relevant rates.
Could you give me some links (if they exists) where I can find information about this?
And I'd be really pleased if someone write a step-by-step instruction, because I tried to do it (I found some instructions in different topics) and failed.
Thanks for responses.

Hi,
why dont you go for generic extraction to extract the data from the table TCURR to ODS.
create the objects according to the fields in the table and design the ODS. map the fields with the objects and extract the data. The you can report on the ODS.
Sunil

Creating ods

hi all,
any one can tell what are prerequisites for the creating the ods.
thanks&regards
praveen

hi,
check sap help
http://help.sap.com/saphelp_bw33/helpdata/en/4a/e71f39488fee0ce10000000a114084/frameset.htm
Prerequisites
Make sure that all the InfoObjects that you want to transfer into the ODS object are active. Create any required InfoObjects that do not exist already and activate them.
As an alternative to creating a new ODS object, it is also possible to transfer an ODS object from SAP delivered Business Content.
Procedure

Why there is need for upgradation

Hi All,
can some one help me out with why we need to go for SAP BW upgradation to SAP BI 7.0?
Thanks,

Hi Bazi,
In BW 7.0 you have more tools to help you designing your data model. I would say also that, even though you have much more tools, the data flows have even become much more simple.
In BW 7.0, to trigger data loads inside the BW system, you have DTPs. In BW 3.x, you had only InfoPackages. That is an advace, because in BW 7.0, you won't necessarily need a staging DSO. That is because you may load first to the DataSource via InfoPackages and then into the InfoProviders you want, via DTP. Check the following thread: [Re: Is it compulsory to create ODS in BW?|Re: Is it compulsory to create ODS in BW?]
RSA1 is more well organized. There are more divisions and the searches are simpler.
Instead of having the dataflow:
DataSource -> Transfer Rule -> InfoSource -> Update Rule -> InfoProvider
You may construct a much simpler flow:
DataSource -> Transformation-> InfoProvider
There is also the new Archiving functionality.
There are many new features in BW 7.0 and it's really worth it.

I am trying to create a new ods ?

hi all,
Can anyone help me out. i am trying to create a new ods.
Where in i have characteristics and keyfigures.
In ods we have - data fields / key fields.
1. can data fields can contain characteristics and keyfigures
2. can key fields can contain key figures as well characteristics?
In which scenario should characteristics should be included in the key fields.
If u have any docs abt ods send it acrros to my email id [email protected]
regds
haritha

Hi Haritha,
     for your first question... YES , You can take charecterstics as Data fields.. and you can create ODS...
     but for your second question , NO, You can't take key figures as key fields..
because.. the example.. Charecterstics means.. on charecterstics based only we are analysis the reports... so, on which based you want report.. suppose for example.. EMPLOY NUMBER based on you want you can take.. that EMP id as KEY FIELDS.. otherwise.. you want to see the report on DEPT ID wise.. you can take.. that Dept Id as key fields.. and then Emp ID you can take as   Data field ...
    so, completely based on your reporting requirement you can put charecterstics as keyfields or datafields...
but .. key figures means.. performance indicators.. these always you need to take as   datafields only..
regards
@jay..

Navigation attributes while creating the ODS

Hi all.
can you pls let me know what is the use of navigation attributes folder while creating ODS.& also about index folder.
Kind Regards,
sami.

Hi,
Navigational Attributes folder: If you have info-object like 0Material in your ODS then attributes of info-object 0MAterial which are marked as navigational comes under this folder and there is an option of check marking these navigational attributes. If you check mark this navigational attribute it will be available in reporting just like another info-object(means you can put filter on this navigational attribute).
Index Folder: Basic reason to have index folder is same as "indexing" this improves the reading from this ODS. Like if you are pulling records from this ODS or you have written select query on this ODS in your routines, indexing on this ODS will improve reading drastically. you can pull info-objects into index folder on the basis of which you are reading data from this DSO, it will improve reading.

Is it compulsory to create ODS in BW?

Similar Messages

Maybe you are looking for