Problem related to class loader and bootstrap loader

how class are loaded and how bootstraping please explain it in detail?

793241 wrote:
how class are loaded and how bootstraping please explain it in detail?Just to put in different words what previous posters are hinting at; this is not a place to come and get answers when you don't want to do research yourself - it is not even a problem you are having as it has a readily available solution; read and enlighten yourself.

Similar Messages

I have a problem with safari. It doesn't load any sites, thing that browers like chrome do, so it isn't a problem related to internet connections. The loading always blocks at 1/10

I have a problem with safari. It doesn't load any sites, thing that browers like chrome do, so it isn't a problem related to internet connection. The loading always blocks at 1/10. I don't know what do to. I CAN'T use it. I have a macbook pro 15 retina late 2013 updated to Yosemite

1. Power off the router. Unplug it from the wall. Wait a while.
    Plug it back to the wall. Power the router on. Wait until all the lights are lit properly. It will take a while.
    Restart the computer.
    Start up in Safe Mode.
    http://support.apple.com/kb/PH14204
2. Delete Caches.db
    Close all windows and quit all applications.
    Hold "option" key down and click "Go" menu in the Finder menu bar.
    Select "Library" from the dropdown.
    Library > Caches > com.apple.Safari > Caches.db
    Right click the Caches.db file and select "Move To Trash.
    Close windows and relaunch Safari.
3. Empty Caches
    Safari > Preference > Advanced
    Checkmark the box for "Show Develop menu in menu bar".
    Develop menu will appear in the Safari menu bar.
    Click Develop and select "Empty Caches" from the dropdown.
4. Delete Cookies
    Safari > Preferences > Privacy > Cookies and other website data:
    Click “Remove All Website Data”.

WARNING: Problem validating implementation class. Failed to load class:

when i am running plsqlAssembler.jar file for wsa.jar with all other atributes , i am getting this warning WARNING: Problem validating implementation class. Failed to load class.
Please if anybody knows about this reply me,
thanks in advance.

If you are using Ex in the implemetation class, make sure that you also include the same in the interface (or SEI).
If the implementation looks something like:
public void doSomething() throws Ex {
System.out.println("Is there something to do, now ?");
then the SEI should be:
public void doSomething() throws Ex, RemoteException;
If your have ommited Ex, then you will have the warning you are seing, and there wont be any artifact generated for Ex in the WSDL.
Because the Ex exception was not mapped to any WSDL artifact, there is no way you will see the Ex exception generated on the client side (or proxy).
I have been able to reproduce your error message, so you should be all good.
WARNING: Problem validating implementation class. Exception declaration mismatch between Implementation: bugyyy.MyServiceImpl and Interface: bugyyy.MyWebService. Impl class Method: doSomething declares exceptions not declared by the interface (bugyyy.Ex)
Hope this helps,
Eric

I fixed the problem with the whole 'waiting' and not loading but now some of my apps won't open, what can I do?

I fixed the problem with the whole 'waiting' and not loading but now some of my apps won't open, what can I do?

- Try a reset. Nothing is lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Purchase/install any new app
- Try the remaining items of:
iOS: Troubleshooting applications purchased from the App Store

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

Difference between delta load and full load

HI,
i am getting confused with full load and delta load.
The scenario is as follows:
I have 4 records which i need to pass to DSO.(Standard DSO)
These are the fields and records.
IO_amount          io_QTY         0UNIT     0CURRENCY     Matnr
1519     195     EA     USD     MM01
2643.85     12     EA     USD     MM02
3580.4     10     EA     USD     MM03
6049.8     12     EA     USD     MM04
Now i need to change the record as
IO_amount          io_QTY         0UNIT     0CURRENCY     Matnr
1500     195     EA     USD     MM01
2643.85     12     EA     USD     MM02
3580.4     10     EA     USD     MM03
6049.8     22     EA     INR     MM04
When i passed it as full and delta load but could not make out any difference..
I can see the data only in active data and change log tables.how can i see that in DSO?
please help out,Points for sure.

Hello Susmitha,
You are right & your view of data is also correct
But only thing here is ODS which you are using mait have Overwright option in its Update Rules /Transformations
Here Q is
Which fields are in KeyFields in DSO Design
If
this Field Values are same in Delta are Full Upload
it will overwrite the records in ODS / DSO
If not
it will add the records to DSO /ODS
Comming to Delta & Full Loads
If you use Full always all data Present will be loaded
if you use Delta always changed & New records will be updated
This happens through Pointers Set ( Snap Shot of Previous Load )
Some tables where you can see RSOLTPSOURCE,RODELTAM etc
Try to wiew this ,Its tough to get
Thanks
Hari

Delta Load and Full load

What is the difference between delta load and full load?when are they used?

Hi,
Delta loads - Brings only the changed or newly added data to the data target...
Full loads - Brings all the data whether it is old, new or changed data to the data target...
Full loads are usually used to load master data since it wont change in course of time and delta loads are used when there are large amount of data to be extracted from the source system. It entirely depends on the requirement...
Regards,
Kishore

Making class available to bootstrap loader? interesting twist.......

We're deploying our jar wrapped in an exe (created by exe4j). It's not an option to unwrap the jar, but I want to make a particular class available to the bootstrap loader. If you're not familiar with exe4j, you can pass arguments to the jvm, so I can pass an -Xbootclasspath argument, but I have no idea how that works when the class is in a package in a jar in an exe. I've tried to pass arguments like -Xbootclasspath/a:com.organization.project.package.MyClass and of course it didn't work. Note that what I'm doing is security policy related, and I'd really prefer not to have this class outside of the wrapped jar.
Is what I want to do actually possible? If so, what am I doing wrong?

Erm, sorry for being unclear :s
I'm doing my best to explain myself, please excuse me for not being a native english speaker ;)
About showing more code, I wouldn't know which part to show : several classes are involved already, each of them weighing a couple hundred lines. That's why I prefer explaining rather than dropping unrevealing code snippets. :-x
If from this description you know what piece of code interests you, I'll post it asap. Until then, here goes a shorter explanation of the situation.
My custom ClassLoader loads .class entries from jar files using the java.util.jar package. I define those classes using defineClass(String name, byte[] b, int off, int len). At the same time entries from the jar file get processed, I list the classes which could or couldn't be loaded. The second list being empty once the jar is processed proved me the classes are well-loaded.
Then I seek through the list of loaded ones for classes implementing AIPlayer, Player or other interfaces. My problem is that the classes implementing AIPlayer (c in my previous example) can't get assigned to AIPlayer though they can get assigned to Player, Player being a super-interface of AIPlayer.
Additionnal information are : Player and AIPlayer are loaded by the bootstrap ClassLoader, the bootstrap ClassLoader being the parent of my custom ClassLoader's instance at some degree (it is either the parent or the parent of the parent).
My question is : why can not a class implementing AIPlayer (and thus, Player) be assigned to AIPlayer, though it can be assigned to Player ?
I hope I was clearer here. Thanks for lending me your time.

Safari and other browsers slow to load and wont load https (secure)

Since the last update of Safari 5, we have noticed that we can't load https pages. So we went to Firefox, that seemed to help for awhile. Now we can't always load https in either. We are also seeing that http pages wont load quickly in either browerser. We have researched all posts within the last month about Safari 5 and hang ups, crashes and slow loading....we have tried everything suggested. Since sites don't load quickly, this has taken a lot of time. Any suggestions would be wonderful. We have contacted our DSL provider 6 times in the last 30 days and they can't find anything wrong with their service or with the modem. We are at a loss. Currently we are trying to download the MocOSXUpdCombo 10.6.4 but we keep timing out. Don't even know if this post will post. Oh yeah, Mail is having problems as well. We ran disk first aid and did the permissions as well. Any suggestions would be wonderful.

Hi again:
I am a long way from an expert on anything - SSL or communications. The fact that both browsers are affected seems to take it out of a Safari-only thing. Also, since everything works on your other computer seems to let your ISP off the hook. I don't think it is your computer, per se.
I did get some random thoughts. Things you might look at/try:
1. Reset Safari (empty the cache, for sure)
2. Take a look at the firewall settings on the computer that is giving you problems.
3. You might try Open DNS (free one) to see if the domain name server process is, somehow, an issue:
http://www.opendns.com/start/
4. You might also download the OS X 10.6.4 combo updater and reapply it. That is probably an overkill and it will take awhile, but it is possible something went wrong with the update.
You can see I am fishing, but nothing seems to be consistent in the behavior.
Barry
P.S. The tundra may be frozen, but you live in a beautiful state.

DAC Load strategy - Increamental Load and Full Load.

Hi all,
Thanks for taking the time to review my post.
Environment
Oracle BI Applications Financial & Project Analytics 7.9.6
OBIEE 10.1.3.4.1
DAC 10.1.3.4.1
Informatica 8.6.0 Hot Fix 4.0
Data Source: Oracle Enterprise Business Suite 11.5.10
Problem
We are working on implementing Supply Chain and Order Management analytics and Financial Analytics in OBIEE Applications 11.5.10.
Another team has already configured Financial – General Ledger and Financial Revenue from Financial Analytics module and we cannot use their Container.
Now we need to configure new Container for remaining modules from Financial Analytics and Chain and Order Management analytics.
As per our Implementation plan we would build and execute the execution plan with those subject areas other than General Ledger and Revenue from Financial Analytics. As we know Out Of Box provides tasks for individual Subject areas and there are common tasks which would load common dimension tables [tables for GL and Revenue area already populated with refresh dates] used across the subject areas.
So when we run our execution plan for remaining subject areas in Financial Analytics/ Supply Chain and Order Management analytics do we need to disable those common task which would load common dimension tables so that other teams work don’t get impacted[common dimension tables will not get impacted] or let allow DAC to decide what to run (Full Load or Incremental Load for those common tasks) based on Refresh dates in those dimension tables.
Thanks!
Radharishna

HI,
You can download the patch from this location https://support.oracle.com/CSP/ui/flash.html and it needs login credentials in order to download the patch.
Thanks,
Navin Kumar Bolla

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...

Init load, delta load and full load

Hi BW,
Please when can I use init delta, delta and full load in a data load process.
Which of them is suppose to be in a process chain and which one is manual.
Regards.

Hi,
When you want to run delta, you have to initialize it first, thats when you run the init delta.Here you have 2 options with data transfer and without data transfer. If the data target is empty and there's no data, you can run the init with data transfer. This'll act as a full pull and also set up the initialization. If there's data already present, then you are better off running the init w/o data transfer. This dosen't pull over any data, but just sets up the initialization.
Then you can start using the delta pulls.That'll just bring over the changes and any new records rather than the whole data and is much more efficient.
You can use full pulls for say generic datasources that are not delta enabled or during a first time data load, or if there is a specific business requirement that needs you to pull over the full data everyday. Or in cases where the std datasource is not delta enabled.
Cheers,
Kedar

App store, Itunes, various apps just say loading and never load

I have only had my ipod 4 for about a week, and Itunes, The App store, and numerous other apps won't load. Its just a grey screen that says loading. I have WiFi and I just updated my Ipod software last night....I reset my Ipod 4 times. PLEASE HELP!!!!!

You said a reset does not solve the problem so download the apps on your computer and sync.

Full Load and delta loads of HR Data using ABAP Program

Hi All,
I need to write an ABAP program that will pull some HR data from some of the infotypes.When i run it for the first time it should pull all the data for all the employees but in the subsequent runs it should run only the delta changes
for example
inital run is on 04/30 it should pull all the data for all the employees
next run 05/02 then it should pull onlly the infotypes for which there is a change between 04/30 and 05/02
Please let me know the solution
Thanks
Bala Duvvuri

Rob,
I understand that I need to AEDTM field but the problem is
during the initial load i will not have any control date stored in the z table so i will fetch all the records using the select queries on various infotypesin the if condition but the problem is i need to repeat the same queries by adding the AEDTM condition in the else condition where control date is not initial(not an initial load) so it will be a duplicacy of all the select queries.
is it a good programming style?please let me know your thoughts on this
if p_ctrl is initial " Initial load
select queries
else " subsequent runs
same select queires with AEDTM condition
endif.
Thanks
Bala Duvvuri

Problem related to class loader and bootstrap loader

Similar Messages

Maybe you are looking for