Data Load from DS-- DSO---- Cube

Hello Guys,
I have an issue with the data load.
I use the OFI_GL_14 extractor.
When I did he innit with data transfer I have around 450 K records.
When I loaded to DSO from DS by DTP it loaded the same 450 K .
When I tried to load the data from DSO to Cube it selects only 14.5K records.
It says transfered records 14.5 K and added records 14.5 K records.
Even if it aggregatesat the cube level- it should say transfered 450 K records and 14.5 K records added. is it correct.
I don't have any filters in the DTP.I checked it. I deleted the DTP and again created another new one. The same result.
From DS to DSO is delta-DTP and again from DSO to Cube is delta - DTP.
I am not sure why it filters and select only 14.5 records from 450 K records.
Do you guys encountered this type of situation. Let me know if I am doing something wrong.
Thanks again for your input. It is really appreciated .
Senthil

Are you using infosource in between? If you do, the infosource is aggregating the the data before it gets to the transformation, in that case you will see the transferred record will be less. If you check all the fields as a key field in the infosource, you will get the same record transferred to the transformation and data will be aggregated going to the cube.
thanks.
Wond

Similar Messages

Data Load from a DSO to a Cube

Hello,
I am facing a problem
Case:
There is a DSO with following Char/Key Figure:
Characteristics     ( Value-1 )     ( Value-2 )     ( Value-3 )
A(Key)          ( A1 )     ( A2 )     ( A3 )
B(Key)          ( B1 )     ( B2 )     ( B3 )
C          ( C1 )     ( C1 )     ( C1 )
D          ( D1 )     ( D1 )     ( D1 )
E          ( E1 )     ( E1 )     ( E1 )
F          ( F1 )     ( F1 )     ( F1 )
KF1(Key Figure)     ( 10 )     ( 20 )     ( 30 )
I got below data from the DSO to a Cube(structure is below with data) details are below:
Dimention          ( Values )
C          ( C1 )
D          ( D1 )
E          ( E1 )
F          ( F1 )
KF1(Key Figure)     ( 50 )
My Question is why i am not getting KF1 value as 60.
When i tried with including Key Fields of the DSO, i got all the records in the Cubes.
Where i am mistaking?
Can some one correct me please?
Thanks.
Avinash.

Below are the basic steps which we follow in any BI 2004S system:
1)Create datasource. Here u can set/check the Soucre System fields.
2)Create Transformation for that datasource. (no more update rules/transfer rules)
2.1) While creating transformation for DS it will ask you for data target name, so just assign where u want to update ur data.
DataSource -> Transformation -> Data Target
Now if you want to load data into data target from Source System Datasource:
1) Create infopackage for that data source. If you are creating infopackage for new datasources, it will only allow you update upto PSA, all other options u can see as disabled.
2)Now Create DTP (Data Transfer Process) for that data source.
3) NOw schdule the Infopackage, once the data is loaded to PSA, you can execute your DTP which will load data to data target.
If you are loading data from one one data target to other, no need to use PSA, you can directly execute DTP in that case.
Data Source -> Transformation (IP/DTP) -> Data Target1 -> DTP ->Data Target 2
Use the below link for detailed example:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fc61e12d-0a01-0010-2883-e2fc63ef729b
Infosources are no more mandatory with BI 7.0, below is the link to scenarios where we use infosources:
http://help.sap.com/saphelp_nw04s/helpdata/en/44/0243dd8ae1603ae10000000a1553f6/content.htm
Full or delta depends on your requirement...
chk the below thread to know better
difference between the various loads
hope it helps
Message was edited by:
        sriram viswanathan

Data loading from ODS to CUBE

Hi All,
I have loaded data from ODS to CUBE. now i have requirement to add some fields in the standard cube. so, for testing purpose i have created copy of the original and created transformation . now when i try to load data from ODS it shows me no more data available . while data is already there in ODS.
now what should i do ? i don't want to delete data from original cube. is there any other way to load data through transformation ?
Regards,
Komik Shah

Hi,
Check the DTP of old cube n see whether its Delta. If yes then check whether any one of the foll is check:
1) get delta only once
2) get data by request.
If 1 is checked then delta wont come for the second cube as it says to get delta once and delta is already in one of the cube.
Generally both should be unchecked but can vary as per requirements.
Now for your new DTP, i dont think it will aloow you to change to FULL.
If its allowing you to select FULL, then select it and select from acive table.
try to load and see.
regds,
Shashank

No data loaded from ODS to Cube

Hi,
I am trying to do init with data transfer from 0FIAP_O03 to 0FIAP_C03...
though there is data in the ODS, nothing is loaded to the cube. It just says
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Any suggestions?
Thanks
Shalini

Hi
"Info IDoc received with status 8" implies that there is no data in the source.
But as you say, that data is there in the source(ODS), then there is some inconsistency in the data source and you need to replicate the data source and reactivate that.
IDoc Status 8 signifies that there is no data in the source and its not any error.
For more info on idocs check the below link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0087780d-81b0-2a10-eb82-86e1062f1a2d
Also goto sm58 and clear the idoc there.
Hope this helps
Regards
Shilpa

Data loads from ODS TO CUBE

Hi,
   i have delta loads comming into the ODS. i do full update from ODS to the cube by date range for material moments no. last time when i loaded the data, it loaded few for the date range. rest did not load and sitting at ODS. this is full load and tried to load again. any suggestions...
sp

Hi Srinivas,
        check your update rules between ODS and cube whether they are mapped properly(check your date range for the cube load).
         Do a Init load and then do the delta load.
hope this will help.

Data loads from 2 dsos to 1 infocube

Hi all,
I am trying to update data from DSO1 (Source1: transaction data) to Infocube(TARGET)
In the transformations Start routine, I have to read DSO2(Source2: Master data) for some fields.
DSO1 has CUSTOMER as part of key
DSO2 has CUSTOMER (key) and other fields....FIELD1, FILED2, FIELD3
Infocube to be updated with FIELDS1,2 & 3 WHILE READING DSO2.
WHERE DSO1 CUSTOMER matches with DSO2 CUSTOMER.
Also, data NOT TO BE UPLOADED into Infocube if FIELD1 in DSO2= NULL
Please give me the abap code for the above logic.
Appreciate any help in this regard.
Thanks.
Edited by: Aryaman Krishna on Aug 28, 2011 3:55 PM

Hi,
You will have to read data of another DSO2 in start routine,
1) Create an internal table of type DSO2 and then load data into it.
SELECT CUSTOMER
Field1
Field2 ..... etc
from DSO2
into table it_DSO2
for all entries in source_package
where customer = source_package-customer.
Now you have all the data available in internal table it_DSO2, you can use this internal table in Field routine to skip any record.
In the field routine simply check the required condition and then raise exception CX_RSROUT_SKIP_RECORD to skip particular record.
Regards,
Durgesh.

We have some data loads from ODS to Cube (Deltas)

Dear Experts,
We can see request status green in DSO but in cube it is in yellow and not available for reporting (the request got compressed)
I want to make the status to green and available for reporting but i could'nt do it as i can see some popup message saying the request is already activated and change QM status not possible.
when i run the delta again that also becomes yellow status due to the previous request's was in yello status.
please suggest me how to change the status of compressed request and why it is happening.
Thank you in advance,
Kiran.

Hi,
Chk whether automatic request processing--->Set quality status Ok checked or not?
It might be in manage of cube, in the menu-->goto options somewhere
as I was not before the system ...I couln't guide u exactly...
rgds,
Edited by: Krishna Rao on Mar 30, 2010 3:47 PM

Summing up key figure in Cube - data load from ODS

Hello Gurus,
I am doing a data load from ODS to cube.
The records in ODS are at line-item level, and all needs to be summed up at header level. There is only one key-figure. ODS has header and line-item fields.
I am loading only header field data ( and not the item-field data) from ODS to Cube.
I am expecting only-one record in cube ( for all the item-level records) with all the key-figures summed up. But couldn't see that.
Can anyone please explain how to achieve it.
I promise to reward points.
=====
Example to elaborate my point.
In ODS
Header-field item-field   quantity
123                301          10
123                302           20
123                303           30
Expected record in Cube
Header-field       Quantity
   123                    60
====================
Regards,
Pramod.

Hello Oscar and Paolo.
Thanks for the reply. I am using BW 7.0
Paolo suggested:
>>If you don't add item number to cube and put quantity as adition in update rules >>from ODS to cube it works.
I did that still I get 3 records in cube.
Oscar Suggested:
>>What kind of aggregate do you have for your key figure in update rules (update >>or no change)?
It is "summation". And it cannot be changed. (Or at least I do not know how to change it.)
There are other dimensions in the cube - which corresponds to the field(s) in ODS.
But, I just mentioned these two (i.e. header and item-level) for simplicity.
Can you please help?
Thank you.
Pramod.

Data load from DSO to cube

Hi gurus
We have a typical problem, we have to combined 2 records into one when they reach to DSO.
One source is flat file and the other is R3. so few fields I am geting from flat file and few from R3 . They are creating one record when they loaded to DSO . Now I am getting one record in active data table but when I load the data to cube from that DSO ( Data is going from change log to cube ) to cube , I am getting 2 seperate records ( one which is loaded from flat file and one which is loaded from R3 ) in cube which I dont want. I want only one record in cube just like i have in my active data table in DSO.
I cant get the data from Active data table because I need delta load.
Would you please advise what can I do to get that one record in Cube?
Pl help

Ravi
I am sending the data thro DTP only but is there any solution to get one record bcos in other scenario I am getting data from 2 different ERP sources and getting one record in DSO and cube as well.
but that is not happening for this second scenario where i am getting data from FLAT file and ERP and traing to create one record.

Data loading from DSO to Cube

Hi,
I have a question,
In book TBW10 i read about the data load from DSO to InfoCube
" We feed the change log data to the InfoCube, 10, -10, and 30 add to the correct 30 value"
My question is cube already have 10 value, if we are sending 10, -10 and 30 Values(delta), the total should be 40 instead of 30.
Please some one explaine me.
Thanks

No, it will not be 40.
It ll be 30 only.
Since cube already has 10, so before image ll nullify it by sending -10 and then the correct value in after immage ll be added as 30.
so it ll be like this 10-10+30 = 30.
Thank-You.
Regards,
Vinod

Full load from a DSO to a cube processes less records than available in DSO

We have a scenario, where every Sunday I have to make a full load from a DSO with OnHand Stock information to a cube, where I register on material and stoer level a counter if there is stock available.
The DTP has no filters at all and has a semantic group on 0MATERIAL and 0PLANT.
The key in the DSO is:
0MATERIAL
0PLANT
0STOCKTYPE
0STOR_LOC
0BOM
of which only 0MATERIAL, 0PLANT and 0STORE_LOC are later used in the transformation.
As we had a growing number of records, we decided to delete in the START routine all records, where the inventory is not GT zero, thus eliminating zero and negative inventory records.
Now comes the funny part of the story:
Prior to these changes I would [in a test system, just copied from PROD] read some 33 million of records and write out the same amount of records. Of course, after the change we expected to write out less. To my total surprise I was reading now however 45 million of records with the same unchanged DTP, and writing out the expected less records.
When checking the number of records in the DSO I found the 45 million, but cannot explain why in the loads before we only retrieved some 33 millions from the same unchanged amount of records.
When checking in PROD - same result: we have some 45 million records in the DSO, but when we do the full load from the DSO to the cube the DTP only processes some 33 millions.
What am I missing - is there a compression going on? Why would the amount of records in a DSO differ from the amount of records processed in the DataPackgages when I am making a FULL load without any filter restrictions and only a semantic grouping in place for parts of the DSO key?
ANY idea, thought is appreciated.

Thanks Gaurav.
I did check if there were more/any loads doen inbetween - there were none in the test system. As I mentioned that it was a new copy from PROD to TEST, I compared the number of entries in the DSO and that seems to be a match between TEST and PROD, ok a some more in PROD but they can be accounted for. In test I loaded the day before the changes were imported to have a comparison, and between that load and the one ofter the changes were imported nothing in the DSO was changed.
Both DTPs in TEST and PW2 load from actived DSO [without archive]. The DTPs were not changed in quite a while - so I ruled that one out. Same with activation of data in the DSO - this DSO get's loaded and activated in PROD daily via process chain and we load daily deltas into the cube in question. Only on Sundays, for the begin of the new week/fiscal period, we need to make a full load to capture all materials per site with inventory. The deltas loaded during the week are less than 1 million, but the difference between the number of records in the DSO and the amount processed in the DataPackages is more than 10 millions per full load even in PROD.
I really appreciated the knowledgable answer, I just wished you would pointed out something that I missed out on.

Data loading from flat file to cube using bw3.5

Hi Experts,
                   Kindly give me the detailed steps with screens about Data loading from flat file to cube using bw3.5
       ...............Please

Hi ,
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 the DataSource (short, medium, long).
                            b.      As required, specify whether the DataSource builds an initial non-cumulative and can return duplicate data records within a request.
                            c.      Specify whether you want to generate the PSA for the DataSource in the character format. If the PSA is not typed it is not generated in a typed structure but is generated with character-like fields of type CHAR only.
Use this option if conversion during loading causes problems, for example, because there is no appropriate conversion routine, or if the source cannot guarantee that data is loaded with the correct data type.
In this case, after you have activated the DataSource you can load data into the PSA and correct it there.
       4.      Go to the Extraction tab page.
                            a.      Define the delta process for the DataSource.
                            b.      Specify whether you want the DataSource to support direct access to data.
                            c.      Real-time data acquisition is not supported for data transfer from files.
                            d.      Select the adapter for the data transfer. You can load text files or binary files from your local work station or from the application server.
Text-type files only contain characters that can be displayed and read as text. CSV and ASCII files are examples of text files. For CSV files you have to specify a character that separates the individual field values. In BI, you have to specify this separator character and an escape character which specifies this character as a component of the value if required. After specifying these characters, you have to use them in the file. ASCII files contain data in a specified length. The defined field length in the file must be the same as the assigned field in BI.
Binary files contain data in the form of Bytes. A file of this type can contain any type of Byte value, including Bytes that cannot be displayed or read as text. In this case, the field values in the file have to be the same as the internal format of the assigned field in BI.
Choose Properties if you want to display the general adapter properties.
                            e.      Select the path to the file that you want to load or enter the name of the file directly, for example C:/Daten/US/Kosten97.csv.
You can also create a routine that determines the name of your file. If you do not create a routine to determine the name of the file, the system reads the file name directly from the File Name field.
                              f.      Depending on the adapter and the file to be loaded, make further settings.
■       For binary files:
Specify the character record settings for the data that you want to transfer.
■       Text-type files:
Specify how many rows in your file are header rows and can therefore be ignored when the data is transferred.
Specify the character record settings for the data that you want to transfer.
For ASCII files:
If you are loading data from an ASCII file, the data is requested with a fixed data record length.
For CSV files:
If you are loading data from an Excel CSV file, specify the data separator and the escape character.
Specify the separator that your file uses to divide the fields in the Data Separator field.
If the data separator character is a part of the value, the file indicates this by enclosing the value in particular start and end characters. Enter these start and end characters in the Escape Charactersfield.
You chose the; character as the data separator. However, your file contains the value 12;45 for a field. If you set u201C as the escape character, the value in the file must be u201C12;45u201D so that 12;45 is loaded into BI. The complete value that you want to transfer has to be enclosed by the escape characters.
If the escape characters do not enclose the value but are used within the value, the system interprets the escape characters as a normal part of the value. If you have specified u201C as the escape character, the value 12u201D45 is transferred as 12u201D45 and 12u201D45u201D is transferred as 12u201D45u201D.
In a text editor (for example, Notepad) check the data separator and the escape character currently being used in the file. These depend on the country version of the file you used.
Note that if you do not specify an escape character, the space character is interpreted as the escape character. We recommend that you use a different character as the escape character.
If you select the Hex indicator, you can specify the data separator and the escape character in hexadecimal format. When you enter a character for the data separator and the escape character, these are displayed as hexadecimal code after the entries have been checked. A two character entry for a data separator or an escape sign is always interpreted as a hexadecimal entry.
                            g.      Make the settings for the number format (thousand separator and character used to represent a decimal point), as required.
                            h.      Make the settings for currency conversion, as required.
                              i.      Make any further settings that are dependent on your selection, as required.
       5.      Go to the Proposal tab page.
This tab page is only relevant for CSV files. For files in different formats, define the field list on the Fields tab page.
Here you create a proposal for the field list of the DataSource based on the sample data from your CSV file.
                            a.      Specify the number of data records that you want to load and choose Upload Sample Data.
The data is displayed in the upper area of the tab page in the format of your file.
The system displays the proposal for the field list in the lower area of the tab page.
                            b.      In the table of proposed fields, use Copy to Field List to select the fields you want to copy to the field list of the DataSource. All fields are selected by default.
       6.      Go to the Fields tab page.
Here you edit the fields that you transferred to the field list of the DataSource from the Proposal tab page. If you did not transfer the field list from a proposal, you can define the fields of the DataSource here.
                            a.      To define a field, choose Insert Row and specify a field name.
                            b.      Under Transfer, specify the decision-relevant DataSource fields that you want to be available for extraction and transferred to BI.
                            c.      Instead of generating a proposal for the field list, you can enter InfoObjects to define the fields of the DataSource. Under Template InfoObject, specify InfoObjects for the fields in BI. This allows you to transfer the technical properties of the InfoObjects into the DataSource field.
Entering InfoObjects here does not equate to assigning them to DataSource fields. Assignments are made in the transformation. When you define the transformation, the system proposes the InfoObjects you entered here as InfoObjects that you might want to assign to a field.
                            d.      Change the data type of the field if required.
                            e.      Specify the key fields of the DataSource.
These fields are generated as a secondary index in the PSA. This is important in ensuring good performance for data transfer process selections, in particular with semantic grouping.
                              f.      Specify whether lowercase is supported.
                            g.      Specify whether the source provides the data in the internal or external format.
                            h.      If you choose the external format, ensure that the output length of the field (external length) is correct. Change the entries, as required.
                              i.      If required, specify a conversion routine that converts data from an external format into an internal format.
                              j.      Select the fields that you want to be able to set selection criteria for when scheduling a data request using an InfoPackage. Data for this type of field is transferred in accordance with the selection criteria specified in the InfoPackage.
                            k.      Choose the selection options (such as EQ, BT) that you want to be available for selection in the InfoPackage.
                              l.      Under Field Type, specify whether the data to be selected is language-dependent or time-dependent, as required.
       7.      Check, save and activate the DataSource.
       8.      Go to the Preview tab page.
If you select Read Preview Data, the number of data records you specified in your field selection is displayed in a preview.
This function allows you to check whether the data formats and data are correct.
For More Info: http://help.sap.com/saphelp_nw70/helpdata/EN/43/01ed2fe3811a77e10000000a422035/content.htm

Automated data load from APO to SEM transactional cube

Hi ,
We have BW-SEM system integrated with APO system.
I could see automated data loads from APO to SEM transactional cube ..
Infopackage name as "Request loaded using the APO interface without monitor log" ..
I don't see any infopackage by this name in both the systems ( APO & SEM )..
I am not sure how it configured ..
Appreciate any inputs on how its happens .....
Thanks in advance

Hi,
As I mentioned the starting point will be the tcode BPS0. There will be 2 planning areas created (if I am correct) one for SEM cube and the other for APO cube. The better way to find it will be goto tcode se16 and enter UPC_BW_AREA and key in the cube names in the cube field. this will give you the planning area names now look for a multiplanning area which has the 2 areas included in them (this is available in table UPC_AREAM).
then goto BPS0 and you will have to find which function is being used to post the data.
thanks

Error when loading from ODS to Cube

Hello Friends,
I am having trouble loading data from ODS to Infocube in my 2004S system.When loading data i get this message
07/03/2007     13:10:25     Data target 'ODSXYZ ' removed from list of loadable targets; not loadable.
07/03/2007     13:28:42     Data target 'ODSXYZ ' is not active or is incorrect; no loading allowed
I checked for ODSXYZ in my data target but there is nothing by that name.Even the infopackage doesnt have it.What needs to be done.Please help.
Thanks.

Its a expected behavior. When you migrate ur DS, the infopacks associated with it, will grey out all the data targets that they were feeding before, that applies to any infopack you create even after the migration. You womt be able to delete it.
Having said this, this shouldnt impact ur loads from ODS to Cube. As this shoudl be taken care of by ur DTP's rather than ur infopacks.
A few questions:
How are you loading ur cube?
Did the data get thru fine to PSA with the infopack in question?
How did you load ur DSO(assuming the load was successful)?
Message was edited by:
        voodi

Loading from ODS to Cube in process chain

Hi Experts,
How can I do a full load from ODS to cube when using further processing in process chain? Your help is much appreciated.
Thanks,
Bill

Hi,
You can use a DTP for this.
Create transformation between DSO and cube.
Create DTP and run it.
Loading data from one cube to another cube.
Cube to cube data loading
how to upload data from cube to cube
Can we pull data from one cube to another cube
Data Load Steps:
Reading data from another cube
Hope this helps.
Thanks,
JituK

Data Load from DS-- DSO---- Cube

Similar Messages

Maybe you are looking for