Load Every Day 2LIS_03_BX (Full Load landscape) BI 7.0

Hi,
We want a simple landscape of material stocks from an SAP R/3 system to SAP BW. We would like to transfer the complete current material stock for a calendar day (u201CSnapshotsu201D), every day. We think that the correct datasource for taht is 2LIS_03_BX, in "How To ..." documents appears that in an Infopackage for this datasource you can set an indicator:
- Full update
- Create Opening Balance
But in BI 7.0 this option doesn't appears ... we can set only "Generate Initial Status" indicator, in infopazkage ...
We try another way, creating two differents DTP, one in "Full" mode and other in "Initial Non-Cumulative for Non-Cumulative Values", but it doesn't works ... The first time we load all data from stock inizialitation (R/3 transaction MCNB), is correct, but the netx day appears the same data ... Any Idea ? Is necessary to execute the inizialitation process in R/3 every day and after that the data load to BW ¿?
We know that we can create a Datasource with R/3 table MARD, but we want to check this landscape ...
Thanks in advanced.
Best Regards,
Carlos.

Hello,
thanks for your answer, it was very useful for us.
But We don't understand your second paragraph, when you say "use the snapshot capability" ...
We thinked that with the solution you described in the first paragraph we can implement "snapshot capability", without
initializing delta or using LO cockpit and delta jobs ? Deleting setup table and after executing setup everyday, don't we obtain a snapshot scenario ? Because we think that with delta queues is not possible to execute setup process, is that true ?
Another thing, I read the document you recommended, and is an old version, because if you see the infopackage to load BX appears the option full, page eleven, and the datasource is 2LIS_40_S278 ... for that we thinked that is not useful for us ... We read about snapshot capability in How To ... handle Inventory Management Scenarios in BW (Version 1.3 - January 2005), but is an old version too. We think for Bi 7.0 there is no documentation.
Best regards,
Carlos.

Similar Messages

Delta load takes longer than Full load

Currently we are doing full load every time it takes 15 minutes to complete the cube load. When I dod delta it takes 40 minutes .
I was adivse to do "Reorganize /BI0/F0FIGL_B10 to apply the values to all the table/index blocks".
If I do this in Quality and Production will it be huge impact in both the boxes.
Please let me know is this a correct solutions. I and expecting BW expert feedback for this .
Thanks

Hi,
first of all you need to identify at which stage the time is consumed. Is it at extraction time or the posting time to PSA, ODS, Cube or maybe in some routines. You can get this info in the monitor of the request by checking the timestamps of the entries.
In your case I think it will be at extraction time and best way to find out what's going on is to schedule a upload and do a sql-trace for the extraction via transaction st05. Check the trace list for select statements with a long response time and check the indexes on the tables. You might need to create some indexes.
regards
Siggi
PS: I guess the reason is that in case of a delta some change documents has to be read by the extractor.
Message was edited by: Siegfried Szameitat

Inventory cube load: can I use full load?

hi,
I have an inventory cube with non-cumolative chars. Can I use full load option or I thave to load with delta for non-cumulative KFs?
Regards,
Andrzej

Hi Aksik,
The load will not matter in the Addregation option.You can load by full or delta.
Now the reports creation has to be done with this in mind that the figures has to come correctly.Specify the aggregation required in the properties of the keyfigure in the query.If required use a ODS in the data flow.
regards
Happy Tony

Delete and full load into ODS versus Full load into ODS

Can someone please advise, that in the context of DSO being populated with overwrite function, would the FULL LOAD in following two options (1 and 2) take the same amount of time to execute or one would take lesser than the other. Please also explain the rationale behind your answer
1. Delete of data target contents of ODS A, Followed by FULL LOAD into ODS A, followed by activation of ODS
2. Plain FULL LOAD into ODS A (i.e. without the preceeding delete data target contents step), Followed by activation of ODS
Repeating the question - whether FULL LOAD in 1 will take the same time as FULL LOAD in 2, if one takes lesser than the other then why so.
Context : Normal 3.5 ODS with seperate change log, new and active record tables.

Hi,
I think the main difference is that you with the process "Delete and full load" you will only get the full loaded data inside the dso. With full load you the system uses the modify logic (overwrite for all datasets already in the dso) and insert for all new datasets which are not inside yet inside the dso
Regards
Juergen

Loading 0employee master data (full load)

0employee master data has been loaded several times in BW...it looks like sometimes the load runs and creates a new record eventhough the data hasn't changed. guessing this is because of the time parameter entered on the (infopackage) update screen?? How do we remove the duplicate records?
Thanks for your help!
Chuck

because its time dependent master data....check table PA0000....
hope it helps...when you are creating your queries you have to give them a key data...an employee might have worked in a particular department during a certain time and another department during another time...
begin date and end date are very important here...
Hope it helps

ODS vs Full Load

Hi All,
I need help regarding the data modeling related to cube 0PCA_C01.
Currently the data source 0EC_PCA_1 is used to extract data from R3 and populate the cube. We are having a full load every day and delete the data from previous load.
I am planning to load only deltas to cube. I found that data source 0EC_PCA_1 is not set up to pull deltas from R3.
So I am left with option of pseudo deltas with the ODS between R3 and the cube.
Can anyone help me out in deciding the key fields for the new ODS. So that the data doesn't get lost when we load it to cube
Regards,
NPR

Hi,
I think 0EC_PCA_1 datasoruce supports delta.
Goto RSA6 double click on 0EC_PCA_1 datasource and u will c the delta option is enabled.
regards,
md zubair sha

Question on Deltas after Init and Full load

Hi
We have an ODS X pushing data to two cubes A & B. ODS X data is initialized to Cube A long back and deltas are loading every day. Now We have recently created Cube B and made a fulll load from ODS X and loading the Deltas from ODS X with same info package we are using to load the deltas in to cube A. Do we get any data inconsistencies if we load like this ? Do I need to make a new init for Cube B to get proper deltas ? I'm hoping that Deltas will automatically take care of reversal in Cube B too...Please advice.
Thanks
Sam

This looks fine, since u have already done full load from X to B, and currently loading delta to both A n B , it is fine, no need for new init.
Regards,
Rathy

Can I use full load for daily loads in LO Cockpit extraction.

I am using LO cockpit extraction for 2LIS_11_VAITM and i am using delta load for daily load and I have following doubt.
Can i use full load for daily loads instead of delta in LO Cockpit extraction.
Because, my understanding is that full load always takes data from setup tables in ECC and set up tables will not have delta data.
pls reply. Thanks.

You are right abt the understanding that full load (atleast for the extractor at hand) brings data from setup tables. You are also right that delta records are not loaded into setup tables.
So if you plan to do full loads every day, you have to load the setup tables everyday. It is at this juncture that I have to remind you that, filling of setup tables requires a downtime of the system to ensure that no changes / creates happen during the process.
Hence performing a full load is not a very good approach to go by...especially when SAP made the job easy by doing all the dirty work of identifying changes and writing them to extraction queue.
Hope this helps!

BI7 : Change full load to delta load - things to do?

http://wiki.sdn.sap.com/wiki/display/profile/2007/04/30/Differencebetweenfull,intialanddeltaupdatemodes
Difference: Full load, Delta Load & INIT load in BW
Hi.
Since am not familiar with BW request clarity as to how to achieve the following :
We are on BI 7.
On our BW server, One of the Existing process chain loads data as full load daily Till date.
This schedule runs for about 4 to 6 hours during the nights. And the data seems to be growing.
And doing full load, now seems, not that meaningful for data analysis.
So we now feel we need not do a full load every day. But do only the incremental load.
How to make this effective in our existing process chains.
I went thro the 2 links above, but a few things am not clear.
What exactly needs to be done to change a full load into a delta load.
Also do not wish to have any data loss happening.
We run the schedules on a particular process chain for BW around 1 am.
Say from tomorrow I want to have the data loading as delta.
What exactly are the steps to be followed.
Precautions to be taken
So that we have the correct data load and no data is lost - while doing this.
Things to do am not clear :
do initialization with data transfer / or without data tranfer ?
The make it delta?
So that from tomorrow all data loading becomes delta ?
Or
since in our scenario,
daily basis it is full load.
Just make it delta load,
so that whatever changes will run in the next days schedule.
What all things are to be done stepwise.
if anyone could advise.
That would be very helpful.
Also any documentation which explains all these if someone could share the link please ?
Many thanks
indu
Edited by: Indumathy Narayanan on Aug 26, 2011 5:50 PM

Hi,
Kindly look at following links as well
http://help.sap.com/saphelp_nw04s/helpdata/en/44/9821620553053de10000000a1553f6/content.htm
Generic Delta
If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system. Only the data that has newly arrived is transferred.
To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                            b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
Thanks and regards

How to make LIS Extractor nightly full load

Hello All,
We need an LIS Extractor to be a full load. It appears Full Load only reads setup tables. How can we do a full load for a LIS Extractor?
Thanks!

Hi All,
Here is our scenerio:
I am referring to the LO Cockpit.
We have deltas coming over to a DSO that has a key of order number, material and batch. Now, when the order is created, for example, it will have batch NULL because we have not determined what batch to use yet. It could remain like this for days. In the meantime this record comes over to BW...just fine and updates. Now, we have decided for this order that exists in BW with a batch of NULL that we allocate a batch to it now. Now this record comes over to BW and it creates a new record. So we have 2 records in BW, one with batch NULL and one with batch updated. We really only want to see the record with batch updated.
We also thought about, what happens if we assign a batch (after the record came over to BW as batch NULL), then this creates 2 records as mentioned above and then now we change this batch to yet another batch. Now when this record comes over to BW this order will have 3 records by batch, yet only the latest is valid.
So we thought a full load would work, which it would. How do you handle such a scenerio for deltas? We load to DSO as mentioned and then push to a Cube.
Thanks

Error in Transaction Data - Full Load

Hello All,
This is the current scenario that I am working on:
There is a process chain which has two transaction data load (FULL LOADS) processes to the same cube.In the process monitor everything seems okay (data loads seem fine) but overall status for both loads failed due to 'Error in source system/extractor' and it says 'error in data selection'.
Processing is set to data targets only.
On doing a manage on the cube, I found 3 old requests that were red and NOT set to QM status red. So I set them to QM status red and Deleted them and the difference I saw was that the subsequent requests became available for Reporting.
Now this data load which is a full load takes for ever - I dont even know why I do not see a initialize delta update option there - can Anyone tell me why I dont see that.
And, coming to the main question, how do I get the process chain completed - will I have to repeat the data loads or what options do I have to have a succesfully running process chain or at least these 2 full loads of transaction data.
Thank you - points will be assigned for helpful answers
- DB
Edited by: Darshana on Jun 6, 2008 12:01 AM
Edited by: Darshana on Jun 6, 2008 12:05 AM

One interesting discovery I just found in R/3, was this job log with respect to the above process chain:
it says that the job was cancelled in R/3 because the material ledger currencies were changed.
the process chain is for inventory management and the data load process that get cancelled are for the job gets cancelled in the source system:
1. Material Valuation: period ending inventories
2. Material Valuation: prices
The performance assistant says this but I am not sure how far can I work on the R/3 side to rectify this:
Material ledger currencies were changed
Diagnosis
The currencies currently set for the material ledger and the currency types set for valuation area 6205 differ from those set at conversion of the data (production startup).
System Response
The system does not allow you to post transactions after changing the currency settings to ensure consistency.
Procedure
Replace the current settings with the those entered at production
start-up.
If you wish to change the currency settings, you must use programs to convert data from the old to the new currencies.
Inform your system administrator
Anyone knowledgable in this area please give your inputs.
- DB

0BBP_BPART_BUYID_ATTR Datasource taking too much time for full load

Hello Gurus,
This Data source is fetching 95000 records for five hours in full load. There is no Delta capability. When I run trace and try to see code, It has Oracle and MS SQL inxes but not DB2, and we are on DB2 database. Also all the fields are hidden except Business partner and Buyer ID. I didnot find any notes on this datasource.
Did any one faced this issue, Help me how can I make this loading Faster in Daily Full loads.

Hi,
Divide the load using selections in different infopackages
Thanks
HP

Initial Load/ Full Load

Is there a Diffference Between Initial Load and a Full Load?

Hello Xcaliber,
There is a difference if you put it in the context of delta loads.
The initial load will do a "full load" on some selection and after that, delta loads can take place.
A full load will do a full load but you can not perform delta load (except if you are doing a pseudo-delta) after that.
Hope this helps.

Delta and Full Load question for cube and ODS

Hi all,
I need to push full load from Delta ODS.
I have process chain.... in which the steps are like below,
1. R/3 extractor for ODS1 (delta)
2. ODS1 to ODS2 (delta)
3. ODS2 to Cube ---> needs to be full load
Now when i run process chain by further processing automatically ODS2 does init/delta for Cube.
How can i make it possible for full load ??
can any one guide anything in this ?
Thanks,
KS

Hi,
1. R/3 extractor for ODS1 (delta) : This is OK, normally you can put the Delta InfoPack in Process Chian
2. ODS1 to ODS2 (delta): It automatically flow from ODS1 to ODS2 (you need to select Update Data automaticall in the Targets at the time of ODS creation)
3. ODS2 to Cube ---> needs to be full load :
This you create a Update rules from ODS1 to Cube then Create InfoPackage in between ODS2 and Cube then do full loads. You can delete the data in the CUbe before the load ann dthen do Full load to Cube.
Note: In ODS2 don't select Upadate Data autmaticlly to Data Targets
Thanks
Reddy
Edited by: Surendra Reddy on Nov 21, 2008 1:57 PM

Apple mail quits unexpectedly every day for years

My Apple Mail quits unexpectedly (crashed) every day when I load it.   This has been happening for 3 years and I'm getting a little tired of it. Crashes most every time i first load it . If i reopen it, then it I can use it.    Even after switching to newer OSX and from macbook to mini, still is happening. It always says quit unxpectedly.   Most often there is a message in there about it trying to check my work email (Exchange) even though only the @me cloud account is setup.    On my iphone there is the cloud and exchange acounts.    I tried loading with SHIFT ,and you can load that way, but it won't fix it permanently, just don't want to have to push SHIFT every time. I tried t rebuild on mailbox, but its still happening.
Its as if its trying to access my work/exchange email even that's not setup here, just the cloud account (@me).   Sometimes I'll see part of a date or subject from a work email (Exchange) in the error message, which is really weird.
Any help would be great.

Here's today's error message. Can anyone help me resolve this??
Process:
Mail [39731]
Path:
/Applications/Mail.app/Contents/MacOS/Mail
Identifier:
com.apple.mail
Version:
6.5 (1508)
Build Info:
Mail-1508000000000000~3
Code Type:
X86-64 (Native)
Parent Process: launchd [157]
User ID:
501
Date/Time:
2013-07-26 11:00:42.747 -0600
OS Version:
Mac OS X 10.8.4 (12E55)
Report Version: 10
Sleep/Wake UUID: 10C0813D-BD3D-4A05-AEBC-1B28363C915A
Interval Since Last Report:
80754 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 842 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
27597F76-EA9A-6396-2280-C488124DA98F
Crashed Thread: 24 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[ABRecord setValue: '<work email address removed here>' forKey: 'Email'] invalid value'
abort() called
terminate called throwing an exception
Application Specific Backtrace 1:
0   CoreFoundation
0x00007fff97200b06 __exceptionPreprocess + 198
1   libobjc.A.dylib
0x00007fff8b29a3f0 objc_exception_throw + 43
2   CoreFoundation
0x00007fff972008dc +[NSException raise:format:] + 204
3   AddressBook
0x00007fff9129ff36 -[ABRecord setValue:forKey:] + 116
4   Message
0x00007fff8df600b7 __42-[MFRecentsManager _updateRecentsForKeys:]_block_invoke_0 + 719
5   Foundation
0x00007fff8cde99cf -[NSBlockOperation main] + 124
6   Foundation
0x00007fff8cdbf926 -[__NSOperationInternal start] + 684
7   Foundation
0x00007fff8cdc70f1 __block_global_6 + 129
8   libdispatch.dylib
0x00007fff8f1fcf01 _dispatch_call_block_and_release + 15
9   libdispatch.dylib
0x00007fff8f1f90b6 _dispatch_client_callout + 8
10 libdispatch.dylib
0x00007fff8f1fa1fa _dispatch_worker_thread2 + 304
11 libsystem_c.dylib
0x00007fff96c07d0b _pthread_wqthread + 404
12 libsystem_c.dylib
0x00007fff96bf21d1 start_wqthread + 13

Load Every Day 2LIS_03_BX (Full Load landscape) BI 7.0

Similar Messages

Maybe you are looking for