This Excel spreadsheet can be found under PS_HOME\excel\ExcelToCI.xls.

ExcelToCI is fairly simple to use, and you may find a component interface already exists for the component you want to load data to. If not, it is relatively simple to create one.

This article by ERP Associates provides an excellent overview of how to use it.

Good luck with it.

Perhaps the key benefit of using file layouts is that it abstracts the parsing of the input file from the processing. So if the structure of your input file changes, you theoretically just have to change the file layout and not the PeopleCode processing to cater for the change. However, in practice changes aren't always this simple! With SQR you will have to write the code that parses your file, but this is fairly trivial. Also if you keep the procedure for parsing your file separate from the procedure that loads your file, you have essentially achieved this abstraction anyway. How will users be selecting the input file? For example, will they be using the file attachment functionality?

Another consideration is whether you (and your fellow developers) are more comfortable with SQR or PeopleCode/Application Engine programs. If everyone in your organisation has excellent SQR skills, then that's a good reason to use SQR. Of course, if you want to learn something new then you might want to try using file layouts, PeopleCode and application engine. Remember, introducing new technology doesn't always make the problem easier to solve.

A lot of people will argue that you should be moving away from SQR and towards using PeopleCode and Application Engine programs because SQR is being phased out. But I guess you could make a similar argument about PeopleCode and Application Engine programs with Oracle's move towards SOA and fusion applications.

In terms of efficiency, there isn't really a difference. You can write an inefficient SQR as easily as you can write an inefficient application engine program. Efficiency typically comes down to your SQL skills and understanding of database performance. Granted some developers tend to struggle with efficiency on application engines programs but I wouldn't put that down to the technology.

In end, the choice might all come down to your time frames. Do you have the luxury of an extra week to fiddle around with a newer technology like file layouts with PeopleCode and application engine programs or do you need to stick to something you are more familiar with like SQR to get the work done on time?

Sorry, I don't have a definite answer for you, but perhaps some of these considerations will help with your decision. Please post if there are any other technical considerations that you think may be important.

Thank you