Init Load and RSA3

I have carried out a transport to Q/A and part of the transport included an Init InfoPackage which was created on Development. I have used this package to schedule an immediate Init load. It is not extracted anything so far but should have, could this be because the package was created on Development? If so how do I resolve.
As a test I went to RSA3 to see if I could carry out a test extract, nothing is being extracted in the sense that the process is still running, could this be because I am extracting on B/W or is there no relationship in that sense? Thanks

Hi,
First of all, count the entries in setup table MC11VA0ITMSETUP, if it has zero records then fill the set up table using tcode OLI7BW.Execute the job in back ground here. And also select the termination date in future.
Do not start the execution of Info package till the job is completed for filling the set up table.
With rgds,
Anil Kumar Sharma .P

Similar Messages

Init load and full load

hi friends
can u plz give me diff between init load and full load

Hi Raj,
You can read about the details here:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
Full load brings all the data (as per selection if any) from the source related to this particular extractor. The init load will also do the same, but will set a delta pointer so that for the next load only the changed or new records need to be extracted.
Hope this helps...

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.

Perform INIT, DELTA, and FULL Load from R3 to BI 7.0

Hi,
Could anyone please give me the information about how to perform the following to load data from the R3 system to the BI 7.0 system:
1. INIT Load
2. Delta Load
3. Full Load
4. RealTime Data Acquisition
Where can I find the settings for all the above in DTP?
For Real Time Data Acquisition; Don't I have to load the data from the data soruce to the PSA........
Does the data goes directly from the data source to the data target throguh Daemon Process? I read the SAP Help doc's but still little confused.......could any one please explain it in your clear way.
Thank, I will assign the points.

the first three are similar to 3.5
check out this blog by KJ for RDA
Real-Time Data Acquisition -BI@2004s

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Full Load" and "Full load with Repair full request"

Hello Experts,
Can any body share with me what is the difference between a "Full Load" and "Full load with Repair full request"?
Regards.

Hi......
What is function of full repair?? what it does?
How to delete init from scheduler?? I dont see any option like that in infopackage
For both of you question there is a oss note 739863-Repairing data in BW ..........Read the following.....
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
Other terms
Restore data, repair data
Reason and Prerequisites
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets.
And also search in forum, will get discussions on this
Full repair loads
Regarding Repair Full Request
Instead of doing of all these all steps.. cant I reload that failed request again??
If some goes wrong with delta loads...it is always better to do re-init...I mean dlete init flag...full repair..all those steps....If it is an infocube you can go for full update also instead of full repair...
Full Upload:
In full upload all the data records are fetched....It is similar to full repair..Incase of infocube to recover missed delta records..we can run full upload.....but in case of ODS does'nt support full upload and delta upload parallely...so inthis case you have to go for full repair...otherwise delta mechanism will get corrupted...
Suppose your ODS activation is failing since there is a Full upload request in the target.......then you can convert full upload to full repair using the program : RSSM_SET_REPAIR _ FULL_FLAG
Hope this helps.......
Thanks==points as per SDN.
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Oct 23, 2008 8:32 PM

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

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

Question on Delta Init Loads

Hi All,
I have a basic question on Delta Inits. I am a beginner in BW and would truly appreciate any input.
At my company, we currently are doing delta loads on the cube 0RT_C35 (Material Movements). They did the Delta Inits prior to that.
Now if we were to add new fields to the cube and need to populate data to the new fields from the beggining, how do I go about doing it..?
Should I delete the Delta Init requests and redo the Delta Inits..? What will happen to the Delta loads that are running daily then..?
Can someone please give me the steps that I need to follow in a sequence.
Like I said, it might be a basic question..but I am not familiar with this process.
Appreciate your help.

Thank You very much Ravi.
I will not be doing it today based on the priority of the tasks..but this is something I will have to do eventually in the next 1-2 weeks. I will definitely let you know how it goes.
So once the mapping and everything is in place and is ready to be loaded, bascially I need to delete data from the datatarget, put the delta job on hold, reinit the delta requests and then I should be able to do the delta jobs again right..?
Thank You so much.
The other issue is that there are probably 25 Delta inits that they did based on the number range for the Material Nbr. But they have only 1 delta. So does the delta job cover the data for all the Delta Init requests..?
I am assigning full points to you for being such a great help. I will let you know when I actually end up doing this.
I will assign the remaining points when I close the request.
Thanks again

FIGL Init Load Failed

Hi BW Gurus,
I tried to load the FIGL line item extractor - FI_GL_14 and it failed after 2 days.
Due to memory and also system resiurces.
I plan to do the following.
1.Create a infopackage for each fiscal period and do a full load.
2.After all the loads do a init without data transfer.
3.Then schedule the delta.
Will this work.
Also please advise whether I can schedule all the full loads for the fiscal periods in parallel.
Also in ECC the users will be posting to figl during the extract. I don't think this will have any impact on the extract. Is it correct.
Please let me know if the above solution will work.
Thanks
Senthil

Hi Senthil,
Please do not do full loads and init w/o data transfer afterwards. You got two options,
1) Perform init w/o data transfer first and then do full loads.Due to this whatever is changed after init w/o data transfer will be captured as delta so that you won't loose any data. If you perform full first,you will loose delta till the time you perform Init.
(Assuming everything is on Overwrite mode on first level DSO which is generally the case for 0FI_GL)
OR
2) Perform Init with fiscal period ranges. You can do any number of Init's with period ranges. Further deltas will automatically take correct fiscal period ranges.
Answer to your one more Q, offcource you can load full for fiscal periods in parallel there is no problem with that.
If you follow one of above two methods you won't even miss a single record.
Let me know if you have any doubts. Please give marks accrodingly.
Regards,
Viren
Edited by: Viren Devi on Mar 15, 2009 12:16 AM

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

Best practices for using .load() and .unload() in regards to memory usage...

Hi,
I'm struggling to understand this, so I'm hoping someone can explain how to further enhance the functionality of my simple unload function, or maybe just point out some best practices in unloading external content.
The scenario is that I'm loading and unloading external swfs into my movie(many, many times over) In order to load my external content, I am doing the following:
Declare global loader:
var assetLdr:Loader = new Loader();
Load the content using this function:
function loadAsset(evt:String):void{
var assetName:String = evt;
if (assetName != null){
assetLdr = new Loader();
var assetURL:String = assetName;
var assetURLReq:URLRequest = new URLRequest(assetURL);
assetLdr.load(assetURLReq);
assetLdr.contentLoaderInfo.addEventListener( Event.INIT , loaded)
assetLdr.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, displayAssetLoaderProgress);
function loaded(event:Event):void {
   var targetLoader:Loader = Loader(event.target.loader);
   assetWindow.addChild(targetLoader);
Unload the content using this function:
function unloadAsset(evt:Loader) {
trace("UNLOADED!");
evt.unload();
Do the unload by calling the function via:
unloadAsset(assetLdr)
This all seems to work pretty well, but at the same time I am suspicious that the content is not truly unloaded, and some reminents of my previously loaded content is still consuming memory. Per my load and unload function, can anyone suggest any tips, tricks or pointers on what to add to my unload function to reallocate the consumed memory better than how I'm doing it right now, or how to make this function more efficient at clearing the memory?
Thanks,
~Chipleh

Since you use a single variable for loader, from GC standpoint the only thing you can add is unloadAndStop().
Besides that, your code has several inefficiencies.
First, you add listeners AFTER you call load() method. Given asynchronous character of loading process, especially on the web, you should always call load() AFTER all the listeners are added, otherwise you subject yourself to unpredictable results and bud that are difficult to find.
Second, nested function are evil. Try to NEVER use nested functions. Nested functions may be easily the cause for memory management problems.
Third, your should strive to name variables in a manner that your code is readable. For whatever reason you name functions parameters evt although a better way to would be to name them to have something that is descriptive of a parameter.
And, please, when you post the code, indent it so that other people have easier time to go through it.
With that said, your code should look something like that:
function loadAsset(assetName:String):void{
     if (assetName) {
          assetLdr = new Loader();
          assetLdr.contentLoaderInfo.addEventListener(Event.INIT , loaded);
          assetLdr.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, displayAssetLoaderProgress);
          // load() method MUST BE CALLED AFTER listeners are added
          assetLdr.load(new URLRequest(assetURL));
// function should be outside of other function.
function loaded(e:Event):void {
     var targetLoader:Loader = Loader(event.target.loader);
     assetWindow.addChild(targetLoader);
function unloadAsset(loader:Loader) {
     trace("UNLOADED!");
     loader.unload();
     loader.unloadAndStop();

Loading library.swf (unpacked from swc) using loader() and using it's assets

I try to load libary.swf from an swc file in order to use it's library items.
i load the library.swf using urlrequest and loader() and then use getDefinition() to fetch the class definition
of the UIMovieclip element.
i simply created the swc file by adding library assets to an swf file, converting them to a flex component and extending each compoent with the UIMovieClip class.
when i load the swf file from a url (http) i get the following error:
VerifyError: Error #1053: Illegal override of UIMovieClip in mx.flash.UIMovieClip.
when i load the file locally, i get no error. any ideas why?
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600" creationComplete="init()">
    <fx:Script>
        <![CDATA[
            import mx.core.UIComponent;
            import mx.flash.UIMovieClip;
            private var _context: LoaderContext;
            private var _request: URLRequest;
            private var _loader:Loader;
            private var _library:Object;
            private var _executeFunction:Function = null;
            public function _setExecuteFunction(f:Function):void {
                this._executeFunction=f;
            public function handleLibInitialized(e:Event):void {
                this._library=e.target.applicationDomain;
                var a:Class = this._library.getDefinition("lobby_page_component");
                var b:MovieClip = new a() as MovieClip;
                var c:UIComponent = new UIComponent();
                c.addChild(b);
                this.addElement(c);
            public function init():void {
                Security.allowDomain("*");
                var url2:String="http://url/for/library.swf"; <- http provides an error
                 var url2:String="/path/to/library.swf"; <- local path works
                             this._context = new LoaderContext(false,ApplicationDomain.currentDomain);
                this._request = new URLRequest(url2);
                this._loader = new Loader();
                this._loader.contentLoaderInfo.addEventListener(Event.INIT,this.handleLibInitialized);
                this._loader.load(this._request,this._context);
        ]]>
    </fx:Script>
</s:Application>

hello,
thanks for trying to help.
if this is the case, why it happens only when i load the library.swf file from an http location instead of a local location ?
how can i make sure that my adobe flash has the same UIMovieClip version?
kfir

Custom class loader and local class accessing local variable

I have written my own class loader to solve a specific problem. It
seemed to work very well, but then I started noticing strange errors in
the log output. Here is an example. Some of the names are in Norwegian,
but they are not important to this discussion. JavaNotis.Oppstart is the
name of my class loader class.
java.lang.ClassFormatError: JavaNotis/SendMeldingDialog$1 (Illegal
variable name " val$indeks")
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.lang.ClassLoader.defineClass(ClassLoader.java:431)
at JavaNotis.Oppstart.findClass(Oppstart.java:193)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at JavaNotis.SendMeldingDialog.init(SendMeldingDialog.java:78)
at JavaNotis.SendMeldingDialog.<init>(SendMeldingDialog.java:54)
at JavaNotis.Notistavle.sendMelding(Notistavle.java:542)
at JavaNotis.Notistavle.access$900(Notistavle.java:59)
at JavaNotis.Notistavle$27.actionPerformed(Notistavle.java:427)
JavaNotis/SendMeldingDialog$1 is a local class in the method
JavaNotis.SendMeldingDialog.init, and it's accessing a final local
variable named indeks. The compiler automatically turns this into a
variable in the inner class called val$indeks. But look at the error
message, there is an extra space in front of the variable name.
This error doesn't occur when I don't use my custom class loader and
instead load the classes through the default class loader in the JVM.
Here is my class loading code. Is there something wrong with it?
Again some Norwegian words, but it should still be understandable I hope.
     protected Class findClass(String name) throws ClassNotFoundException
         byte[] b = loadClassData(name);
         return defineClass(name, b, 0, b.length);
     private byte[] loadClassData(String name) throws ClassNotFoundException
         ByteArrayOutputStream ut = null;
         InputStream inn = null;
         try
             JarEntry klasse = arkiv.getJarEntry(name.replace('.', '/')
+ ".class");
             if (klasse == null)
                throw new ClassNotFoundException("Finner ikke klassen "
+ NOTISKLASSE);
             inn = arkiv.getInputStream(klasse);
             ut = new ByteArrayOutputStream(inn.available());
             byte[] kode = new byte[4096];
             int antall = inn.read(kode);
             while (antall > 0)
                 ut.write(kode, 0, antall);
                 antall = inn.read(kode);
             return ut.toByteArray();
         catch (IOException ioe)
             throw new RuntimeException(ioe.getMessage());
         finally
             try
                if (inn != null)
                   inn.close();
                if (ut != null)
                   ut.close();
             catch (IOException ioe)
     }I hope somebody can help. :-)
Regards,
Knut St�re

I'm not quite sure how Java handles local classes defined within a method, but from this example it seems as if the local class isn't loaded until it is actually needed, that is when the method is called, which seems like a good thing to me.
The parent class is already loaded as you can see. It is the loading of the inner class that fails.
But maybe there is something I've forgotten in my loading code? I know in the "early days" you had to do a lot more to load a class, but I think all that is taken care of by the superclass of my classloader now. All I have to do is provide the raw data of the class. Isn't it so?

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

Init Load and RSA3

Similar Messages

Maybe you are looking for