Lis datasources , INIT loads,

Hi,
i am working on BI7, and v are using some lis datasources like 2lis_02_s013 and
2lis_02_s017 , I want to do init load with data transfer option and after that create delta loads to be used in process chains, i am geeting errors saying that datasources is till updating in sources system for init load
please guide me in this regard,
plz send ur answers to [email protected]
or
[email protected]
correct answers will be awarded points

Hi,
You can use the infopackage to create the init load on the datasource and transfer the data to PSA and from there you can transfer the data into data targets using DTPs either you can go with full update or you can load the deltas from here again.
Creating init loads, and then deltas is all done in the datasource tree where you create the infopackage to extract the data from the source system to BW system.
REgards.

Similar Messages

Is it possible to automate the load of setup tables for LIS datasources?

Hello,
For LIS datasources, eg. 04 (shop floor control), once the production confirmation is done, we have to manually run the transaction OLI4BW to load the setup tables before extracting data to BW. Is there a way to automate the load of setup tables?
Regards,
Suraj

Hi,
Yes we can !
Create variants for small ranges and scheduled all of them at a time. So that, loading will be completed soon.
Thanks,
Saru

INIT load to the 0FIAR_C03

Hi
I am uploading data to the cube 0FIAR_C03, I am using the standard infosource, I have uploaded data using INIT load it replies that INIT update is not possible to the cube 0FIAR_C03 but the full load is possible.
What can I do to make it delta and INIT enabled ?

Hi Sun,
your datasource have to be replaced (from BW PlugIn 2001.1) by the new extractor 0FI_AP_4, that allows delta management !
Look at OSS Note 401646 'New DataSources for Line Items from FI-GL, FI-AP..."
Hope it helps!
Bye,
Roberto

How to see the init load in bi 7.0

hello frnds,
In bi 7.0 when v load data it show the full load and delta load option only,,so my question is, if delta load r there then definately init load also avilable,so where is that init load,,plz guys tell me where is that option,,
2nd question is about compression in bi 3.5,,after loading data into infocube when i do compression it ll not work,,why i dont know ,,plz help me
Thanks
Rosy

Hi Rosy,
Init with data load is Full upload + Delta Enables. Once you run this it will fetch entire records from the Source, delta will be automatically enabled and next time onwards only delta will be coming to BW.
Before you can request a delta update, you must first initialize the delta process.Delta initialization can only be simulated for DataSources from SAP source systems if the DataSource supports this.
I hope the below link will be helpful,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0db2280-8242-2e10-b6a5-86a46d0feb25?QuickLink=index&overridelayout=true
Regarding compression, please check the below link,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
Thanks,
Vinod

LIS datasources generation and activation

Hi experts,
I have to start a new MM implementation on a fresh installed SAP ECC and SAP BI 7.0 systems.
So I have to activate the LIS datasources on the ECC source , activate them and load delta data into BW.
Can you show me a document that tracks the differents steps to follow ?
regards

Hi,
Check in SDN
Logistic information system (LIS)
Business Content and Extractors
Thanks
Reddy

Whats the Actual use of the Setup table apart from the Full/Init loads

Hi guru's
could u explain whats the Actual use of the Setup table apart from the Full/Init loads in Lo Extraction

Hello Guru,
The Setup table is used mainly for storing the Historical data whereas the new and changed records will be maintained in the Update table.
By storing the Historical data in the setup table you don't need to disturb the Application table anymore.
Please go through the following blogs
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/vikash.agrawal/blog/2006/12/18/one-stop-shop-for-all-your-lo-cockpit-needs
https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002719062002E
Hope it helps
Thanks,
Chandran

SRM to BW - init load

Hello Everyone,
i need to do a init load for datasource 0BBP_TD_PO_1. I know the function of init load, but i want to know the process for the initaliasation of the SRM init load. Do i need quiet time, how to perform init load like flushing the queue etc. I dont how the process of initialition of SRM data. Please provide the steps to perform initalisation process.
Thanks in advance,
Lasya.

Hi Lasya,
SRM Init load is no different. Please donot get confused with LO cockpit.
I would definately prefer to do the init load at a quite time... I dont think I need a downtime though.
Steps to do this:
Check in RSA7.. if you have any entries.
Open the info package...(Init Info pak)...and simply cilck on the start button.
I dont think you need to look into LBWQ1 and use the programs to manually run the V3 updates.
Assign points if helpful
Thanks
kalyan

Difference: Full load, Delta Load & INIT load in BW

Hi Experts,
I am new to SAP BW Data warehousing.
What is the difference between Full load, Delta Load & INIT load in BW.
Regards
Praveen

Hi Pravin,
Hope the below helps you...
Full update:
A full update requests all the data that corresponds with the selection criteria you have determined in the scheduler.
You can indicate that a request with full update mode is a full repair request using the scheduler menu. This request can be posted to every data target, even if the data target already contains data from an initialization run or delta for this DataSource/source system combination, and has overlapping selection conditions.
If you use the full repair request to reload the data into the DataStore object after you have selectively deleted data from the DataStore object, note that this can lead to inconsistencies in the data target. If the selections for the repair request do not correspond with the selections you made when selectively deleting data from the DataStore object, posting this request can lead to duplicated data records in the data target.
Initialization of the delta process
Initializing the delta process is a precondition for requesting the delta.
More than one initialization selection is possible for different, non-overlapping selection conditions to initialize the delta process when scheduling InfoPackages for data from an SAP system. This gives you the option of loading the data
relevant for the delta process to the Business Information Warehouse in steps.
For example, you could load the data for cost center 1000 to BI in one step and the data for cost center 2000 in another.
The delta requested after several initializations contains the upper amount of all the successful init selections as the selection criterion. After this, the selection condition for the delta can no longer be changed. In the example, data for cost
centers 1000 and 2000 were loaded to BI during a delta.
Delta update
A delta update requests only the data that has appeared since the last delta. Before you can request a delta update you first have to initialize the delta process. A delta update is only possible for loading from SAP source systems. If a delta update fails (status red in the monitor), or the overall status of the delta request was set to red manually, the next data request is carried out in repeat mode. With a repeat request, the data that was loaded incorrectly or incompletely in the failed delta request is extracted along with the data that has accrued from this point on. A repeat can only be requested in the dialog screen. If the data from the failed delta request has already been updated to data targets, delete the data from the data targets in question. If you do not delete the data from the data targets, this could lead to duplicated data records after the repeat request.
Repeat delta update
If the loading process fails, the delta for the DataSource is requested again.
Early delta initialization : This is a advanced concept, but just for your information ...
With early delta initialization you can already write the data to the delta queue or to the delta tables in the application while the initialization is requested in the source system. This enables you to initialize the delta process, in other
words, the init request, without having to stop posting the data in the source system. You can only carry out early delta initialization if this is supported by the extractor for the DataSource that is called in the source system with this data
request. Extractors that support early delta initialization were first supplied with.

BIG Question regarding INIT Loads..I am scratching my head for past 2 days

Hello All,
I have one big question regarding the INIT load. Let me explain you my question with an example:
I have a datasource say 2LIS_02_ITM for which I ran the setup tables on JAN 2008. The setup table is filled with say 10,000 records. After that we are running Delta loads everyday till today (almost 30,000 records). Everything is going fine.
Imagine I lost a delta (delta failed and did'nt I do a repeat delta for 3 days, by then next delta came), Hence I am planning to do a Init load again without deleting / filling the setup tables. Now my question is :
1) Will I get the 10,000 records which got filled initially in the setup tables or will I get 40,000 records (that 10,000 + 30,000 records)
2) If it bring 40,000 how is that possible as I hav'nt filled the setup tables?
3) Is it each time I need to fill the setup tables to start the Init load.
Waiting for your guidance.........

Yes...to answer your question
But...agin I will suggest not to go by that method. Only one delta had failed so why do you want to wipe away the timestamp of the last init just becasue of 1 delta failure? it is possible to correct it
First of all i hope you have stopped the process chain or put a hold to Delta jobs
Now, To answer your doubt, about the status red ..See you mark the status red in each of the the data target before delting the failed request from there (I usually do not just delete the requests frm data targets - I mark them red and then delte it to be safe).
Do not forget to delete subsequent requests afterthe failed delta (agin I always mark them red before doing so)
Regarding the actual reuest itself...you need not mark it red in the monitor..You have got to correct this request and successful - it will automatically turn green.
If after successfully correcting the request, it still does not turn green, you can set qm status green. The next delta will recognize this a successful request and bring in the next delta (this happens in cases where you have the infopackage in a process chian when it shows green because subsequent processes were not completed etc).
Let me know in case you have any questions.

FI_AR_4 Infosource(standard) Init Load

Hi Gurus,
I have an issue regarding INIT load for FI_AR_4 Infosource.It shows yellow status though R/3 has data.I got the records into BW using full upload.
To enable DELTA upload, I Intialised the DELTA "<b>without data transfer</b>".It gives me an error that I cannot Initialise once again after FULL upload.
Could you please help me to solve this.
Regards,
Venkat

That is true with the GL if you are using the GL. Once the GL is initialized, AR and AP have to follow that, if GL is not being used, don't worry about it.
Check you ODS status (change -> ODS...). Look at the settings and make sure the "update status automatically" is set, otherwise the system waits for you to turn it green manually.
/smw

How to create generic text datasource to load text data?

met issue in generic master data load
Hi,
please see above link for detail infomation regarding the attribute data load. now the language and description column of the infoobject s_saled is empty. i need to create a generic text datasource to load data from R3 to BW. the table which i use to extract attribute data is VBAK, but i don't find any filed relate to language and description.
met issue in generic master data load
can anyone tell me how to load the text data?
thanks very much.
Eileen

hi eileen,
go to transactio rso2 in your source system ie r/3.
there u have three three fields for transaction data
attributes.
text.
choose text and proceed as u did for trancsaction data load.
thank u,
reward if helpful.

Init Load showing in yellow state.

Hi all,
I am trying to do init for SRM data source to ODS object.
The init load is showing yellow state (0-0 records).
There is no data available in SRM related to this data source.
Can anyone please tell me why it is in yellow state instead of green.
Thanks
S VR.

Hi S VR,
In the monitor screen go to the Status Tab > click on the lights next to Total > Make it Red and save > the system will prompt a couple of messages, say Yes to them. Then you can Manual Update. Once all packages are done (green), then again Status tab > click onthe lights next to Total > Delete Statsu; back to request status > Save. The request should now be green.
else
try repair full request option it can help you..
Hope this helps...
Assign points if helpful...
Regards,
NR
Edited by: N R Pradeep Reddy on Apr 14, 2008 6:14 AM

Enhance LIS Datasource

Hi friends,
Please tell he how to add fields in LIS datasource
I want to add movement type and order type in 0PUR_C01 cube please tell me how to do this.
Thanks,
vish

hi,
Follow the below steps.
1)Go to RSA6 and find the data source you need to enhance.--> Display
2)Double click on the Extract structure.
3)Now click on the append structure button to add the required field on to the existing structure.
4) add your required fields with ZZ appended to your field.
5) Save & Activate the append structure. Then go back and make sure you activate the extract structure also.
6) Now again go back to RSA6 and select your Data Source. But this time go to change Data Source to remove the hide option to the enhanced fields. By default theyll be in hide mode. If you dont remove the hide field then this field will not be seen in BW side.
7) Now go to SE38 to write the logic to populate the data into the enhanced field. Program name to write the logic is ZXRSAU01.
8) Check + Save + Activate.
9) Check in RSA3 if data is populated as per your requirement.
10) Replicate your Data Source.
11) Now go to Data Source/ Trans. Structure screen. Now you can see the enhanced field on the right hand side.
R/3 Side:
Follow the above steps and the enhancement will be RSAP0001:
1.     ZXRSAU01  Transaction Data
2.     ZXRSAU02  Master Data (ATTR).
3.     ZXRSAU03  Master Data (TEXT).
4.     ZXRSAU04  Hierarchies.
Also check the below links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
also please see these threads
Enhancements
Re: enhancements
Regards, Siva

No selection in infopackage possible when Init-load

Hello all,
I have created a loading proccess from an ODS to an Infocube via delta-load. I want to restrict the data and therefore I want to use the selction tab from the infopackage menu. But this is just possible when I choose full-load. When I choose Init-load or delta-load, there is no restriction possible in the selection screen.
Ho can I restict data when i load via delta? the release is 3.5.
Any help would be great.
Best Regards,
Stefan from Munich/Germany

Dear Stefan,
You can not restrict an init/ delta load from an DSO, because the data loaded will correspond to the change log table of the DSO.
What you can do is a "fake" delta. You put a "changed date" in you DSO (filled by the sy-datum in the update rule) and then do a full load from your DSO to your cube with the selection you want and changed data = today. But you will have to be careful in case of reload...
Hope it helps,
Rodolphe

Tab-highlighting duirng the inital Load of the application

Hi All,
Currently I m developing a Flex application where in the
home page,set of seven tabs are there as per the design.
Whenever i click the tab, I have changed the style of the
text to bold..to make it look like highlited.But this works fine
except the inital load of the first page..In the main appliation
tag,i have used the initialize and also the creationComplete events
to make that tab--higlited.Can anyone suggest me a solution to
solve this issue?
I tried using the following code..to highlite..but not
working for the first time..initial display
myTabBar.selectedIndex=4;
myViewStack.selectedIndex=3;

Look at the following thread: [http://www.webmasterworld.com/javascript/3396582.htm] It will involve modifications to your mod pl/sql install..
Thank you,
Tony Miller
Webster, TX

Lis datasources , INIT loads,

Similar Messages

Maybe you are looking for