Huge Conversion File - Too many lines

Hi Experts,
Is there any way to split a Conversion File?
I have a Conversión file with too many lines, so when I save it, it takes a lot of time, (11.000 rows, more than half an hour) and sometimes the Excel hand up (froze).
It is becaming a problem, because everytime I save the Conversion file, I can not use the excel for a while.
Any idea?
Thanks in advance.
Iria

Iria and Patrick,
I want to give an information about this.
BPC transformation file can be multiple steps in one file.
For example,
*Options
*Transformation
*Conversion
*Options
*Transformation
*Conversion
*Options
*Transformation
*Conversion
Therefore, If you only has a problem with conversion, you can do it as below
*Options
*Transformation
*Conversion
       conversion part1
*Options
*Transformation
*Conversion
       conversion part2
*Options
*Transformation
*Conversion
       conversion part3
Note 1 : If you don't need multiple transformation, you only need to specifiy it in the first transformation.
Note 2 : Conversion file can have multiple Tabs in one conversion excel workbook but I am not sure about the performance
              when you do that. So please try two things.
                   1. Split it into multiple worksheet
                   2. Split it into multiple workbooks.
              Please update your result for others.
Note3 : You don't need multiple Convert task, it will be executed in a convert task.
I hope it will help you
Thank you.
James Lim
Edited by: James Lim on Mar 4, 2010 4:31 PM

Similar Messages

Too many lines in my log file

Hy every body,
I've made a Tomcat project under Eclipse and I'm using log4j.
I've configured my log4j in "log4j-config.xml" file.
I've made one file per level (DEBUG, INFO, WARN and ERROR), but I'm receiving too many lines in my "debug.log" file.
Example:
17:52:39 - [main] [DEBUG] org.apache.commons.beanutils.BeanUtils : BeanUtils.populate(org.apache.struts.tiles.TilesPlugin@14d556e, {definitions-parser-validate=true, definitions-parser-details=2, definitions-debug=2, moduleAware=true, definitions-config=/WEB-INF/struts/struts-tiles-defs.xml})
17:52:39 - [main] [DEBUG] org.apache.commons.beanutils.BeanUtils : setProperty(org.apache.struts.tiles.TilesPlugin@14d556e, definitions-parser-validate, true)
17:52:39 - [main] [DEBUG] org.apache.commons.beanutils.BeanUtils : setProperty(org.apache.struts.tiles.TilesPlugin@14d556e, definitions-parser-details, 2)
Can some one tell me how to filter my logs.
Here is a part of my "log4j-config.xml" file:
<appender name="DEBUG" class="org.apache.log4j.FileAppender">
<param name="File" value="${log.path}/debug.log" />
<param name="Threshold" value="DEBUG" />
<param name="Append" value="false" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{HH:mm:ss} - [%t] [%-5p] %c : %m%n" />
</layout>
</appender>
Thanks in advance.

Hy every body,
I've made a Tomcat project under Eclipse and I'm
using log4j.
I've configured my log4j in "log4j-config.xml" file.
I've made one file per level (DEBUG, INFO, WARN and
ERROR), but I'm receiving too many lines in my
"debug.log" file.Then don't use that level. The whole point of the various levels is to be able to trade off level of detail for volume of output. Debug is meant to be very verbose.
You can set various classes or packages to log at different levels, overriding the default for that logger. So if you don't want debug output for com.acme.whatever, then in log4j.properties or log4j.xml or whatever, you can configure that package and all "subpackages" for info, warn, or error. See log4j's docs for details.

Too many lines

When opening an excel file I received as an attachment, and I want to open in Numbers, I either get major lag in viewing the workbook and editing it, Or I receive a message that an error occurred because there are "too many lines" and the workbook won't even import to Numbers
I have a "New" IPad 3rd gen.
Apple told me it is because I only have 512ram, but I understood that the new iPad had 1gb?
Is numbers just not strong enough?
Also, when I do get files to import, fonts, formulas and formats are commonly not supported and it negates being able to use the ipad to work on a workbook remotely and send it forward.
Are ther any fixes?

this is the oracle forms forum. your chances increase going to the right forum.
Gerd

Too many lines for CO-PA assessment postings in KSB1

Hi Experts,
I created an assessment cycle in KEU1, with one segment, using an PA transfer structure (several cost elements to several value fields), and I´m using one single secondary cost element (category 42) to credit the cost centers.
When I execute the assessment via KEU5, the credits in the cost centers for the cost element category 42 generates too many lines (for example, I had 3 postings to 3 primary cost elements and in KSB1 I have 9 lines of "credits" - operation KSPA.):
Primary Cost Elements:
4110201004 ==> 3.000,00
4110209009 ==> 2.000,00
4110209013 ==> 1.000,00
Secondary cost element (after settlement through KEU5):
6519999999 ==> 134,36-
                            198,92-
                            190,49-
                            291,54-
                            548,27-
                            311,88-
                            2.659,89-
                            1.268,02-
                            396,63-
Do you know how can I summarize this postings to have only 3 (ore one) line for the secondary cost element? I cannot identify what was the criteria used by SAP to generate 9 lines.
Kind Regards
Mayumi

the number of line item crediting the cost centre, shall be the same of the line item required in the COPA posting. So the more receiver you have in COPA , the more line item are created.
Paolo

Too Many Line Items While Creating a PO

Dear All,
Here we have a scenario:
We are creating a PO which is having around 10000(ten thousand) line items, and while saving system is showing error message "Too Many PO Line Items" Message No: FI899. and not able to save it.
Kindly Let me know is there any limit for line item creation in a PO.
Regards,
Ravi B

Limitations are limitations, you need a workaround or pay SAP for an extra developement. Probably worth, if you have such POs everyday.
( I cannot even imagine for what reason a PO should have more than 10000 items. Manual maintenance is impossible, the person would sit for a week and more to finish one PO. the CSR at your vendor is as well not able to put the items from your PO into their Sales order within a reasonable time frame - order entry should be ready before delivery date is arrived.
This sounds like you want buy a company and want create just one purchase order to buy any single material they have on stock. But for that purpose the PO is certainly not designed.
Can you give more background that makes my mind open ? )

8g touch updated 4.2.1, problems synching apps and music. gives multiple errors; device times out, internal device errors, network times out, duplicate file, too many files open. itunes diagnostics ok. what to do?

have an 8g ipod touch which has had problems trying to play games and downloading update 4.2.1. went to the apple store who kindly downloaded the software update but now can't synch and generates multiple error messages; device times out, internal device error, network times out, duplicate file and too many files open etc etc. have latest i tunes download and diagnostic test ok. what can i do?

Does the ext directory have the php_oci8.dll? In the original steps the PHP dir is renamed. In the given php.in the extension_dir looks like it has been updated correctly. Since PHP distributes php_oci8.dll by default I reckon there would be a very good chance that the problem was somewhere else. Since this is an old thread I don't think we'll get much value from speculation.
-- cj

Apps team uploading 114505 kbof text file,too many archives getting

the upload is going on ,too many are getting generated in archivelog location
i have increased 200gb to 900gb
please let me know how to know for 14505 kb of dataupload how many archives gettting generated
can we estimate before dataupload how many archives can generate
can you please explain clearly
thanks

Hi,
There is no specific method to calculate the number of archived log files to be generated for the particular load.
But, we may do some rough calculation by looking at the rate of archived log generation.
Check the following things,
1) How frequently the logs are getting generated and the size of the files.
2) How many data has been loaded so far.
Based on the above input, you may get some idea on number of ARCHIVED LOG files to be generated during the rest of the data load.
Also, you may do the following to avoid keep adding space to archive destination.
1) Wite a UNIX shell script to BACKUP the ARCHIVED LOG FILES and DELETE the files once backuped up; which should run for every 10 minutes.
Thanks.

CO 1SRJ-001: Too many line items selected via report interface

Report group/report 1SRJ/1SRJ-001 (CCentres: Rolling Year): provides an overview for the last 12 periods of actual and plan data.
When you access line item report RKAEP000 (KSB1 or KSBP) from report Cost Centres Rolling Year (1SRJ-001) using the report/report interface, too much data is selected.
For example, you enter fiscal year 2009 and month 8 in selection parameters, the report generates results for the last 12 periods: 2008/9 to 2009/8. But the line item report accessed via report interface selected ALL data for the fiscal years 2008 and 2009.
I searched and found Note 127643 that described a similar but not exactly the same situation. Have anyone have any problems with this report? Any suggestion is appreicated.
Regards,

Issue with report 1SRJ-001 (S_ALR_87013631) has been resolved. The interfaced line item report selects all data records for fiscal years 2008 and 2009, instead of just for the selected last 12 months. The problem is due to missing restrictions for a characteristic, in this case, the from-period and to-period fields.
SAP has corrected the problem by issuing an updated version (1999) and the one we were using was the 1995 version. I imported the updated version of report from client 000 and now it works fine.

PL/SQL problem with too many lines - can not apply changes

I have a complex PL/SQL that requires checking 90 check boxes and the query works to a certain point then it just stops being able to be saved (apply changes) after a high no. of lines has been typed in. (The PL/SQL query is to check against a file, that the file has all the check boxes as yes. If there is only 1 or 2 boxes checked, then the sql created only checks those 2 fields for yes.) Is there a way to increase the coding space (or number of lines) that APEX can save/use.

This is the whole PL/SQL coding. At this point, we cannot add any more lines or it will come up with "web page cannot be found" message.
declare
q varchar2(32767); -- query
new varchar2(1):='Y'; -- first one
begin
q := 'select a."CONTR_ID", a."NAME", b."PHONE_NO", b."EMAIL_ADDR" FROM contractor a, contacts b where a.contr_id = b.contr_id and a.contr_id not in (Select unique a."CONTR_ID" from contractor a, contractor_competency b where a."CONTR_ID" = b."CONTR_ID" ';
-------------------Start ENV
if :P33_AIR_QUALITY_TESTING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Air Quality Testing'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_ASBESTOS_REMOVAL_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Asbestos Removal De-Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_ASBESTOS_REMOVAL_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Asbestos Removal Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_BUILDING_ASBESTOS_REMOVAL = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Building Asbestos Removal'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_ENVIRONMENTAL_CONSULTING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Environmental Consulting'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_MANHOLE_ASBESTOS_REM_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Manhole Asbestos Removal De-Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_MANHOLE_ASBESTOS_REM_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Manhole Asbestos Removal Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_OIL_FILTERING = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Oil Filtering'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_OIL_SAMPLING = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Oil Sampling'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_OIL_SPILL_CLEANUP = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Oil Spill Cleanup'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_PUMPING_OUT_MANHOLES = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Pumping Out Manholes'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_SIGNED_ENVIRO_DOCS = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Signed Enviro Docs PRO-MS-008'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_TRANSPORTATION_OF_D_GOODS = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Transportation of Dangerous Goods'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_TRANSPORTATION_OF_PCB = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Transportation of PCB'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_WASTE_PICK_UP = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Waste Pick-Up'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
-------------------- start OCM
if :P33_GREENFIELD_POLELINE_CONST = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Greenfield Poleline Construction'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_HV_OVERHEAD_MAINTENANCE = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''HV Overhead Maintenance'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_INSULATOR_WARNING = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Insulator Warning'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_LV_OVERHEAD_MAINTENANCE = 'YES' then
if new = 'Y' then q := q || ' and (';
new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''LV Overhead Maintenance'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_OVERHEAD_INFRARED_SCAN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Overhead Infrared Scanning'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_POLEHOLES_AND_ANCHORS = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || ' (instr(upper(b."JOB"),upper(''Poleholes and Anchors'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_POLELINE_INSPECTION = 'YES' then
if new = 'Y' then q := q || ' and( '; new := 'N';
else
q := q || ' or '; end if;
q := q || ' (instr(upper(b."JOB"),upper(''Poleline Inspection'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_POLELINE_WORK_TO_35KV = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || ' (instr(upper(b."JOB"),upper(''Poleline Work to 35KV'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_POLELINE_TO_44KV = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || ' (instr(upper(b."JOB"),upper(''Poleline to 44KV'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_ROCK_DRILLING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Rock Drilling'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_TENSION_STRINGING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || ' (instr(upper(b."JOB"),upper(''Tension Stringing'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_TREE_TRIMMING_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Tree Trimming (De-Energized)'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_TREE_TRIMMING_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Tree Trimming (Energized)'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_WOOD_POLE_TESTING_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Wood Pole Testing De-Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_WOOD_POLE_TESTING_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Wood Pole Testing Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
------------------ start UCM
if :P33_CO2_CLEANING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''CO2 Cleaning'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_CABLE_PULLING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Cable Pulling'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_CABLE_TESTING_DEENERGIZED = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Cable Testing De-Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_CABLE_TESTING_ENERGIZED = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Cable Testing Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_CONC_DUCT_MAN_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Conc. Duct & Manhole (De-Energized)'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_CONC_DUCT_MAN_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Conc. Duct & Manhole (Energized)'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_DIR_BURIED_DUCT_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Direct Buried (De-Energized)'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_DIR_BURIED_DUCT_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Direct Buried (Energized)'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_DIRECTIONAL_BORING_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Directional Boring De-Energized'')) > 0) and
((instr(upper(b."SET_YES_NO"),''NO'') > 0) or
(instr(upper(b."CRAFTMAN_YES_NO"),''NO'') > 0) and
(instr(upper(b."PROBATION_YES_NO"),''NO'') > 0)) ';
end if;
if :P33_DIRECTIONAL_BORING_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Directional Boring Energized'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_GENERAL_EXCAVATION = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''General Excavation Around Plant'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_HV_UG_MAINTENANCE = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''HV Underground Maintenance'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_LV_UG_MAINTENANCE = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''LV Underground Maintenance'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_MANHOLE_CLEANING_DEEN = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Manhole Cleaning De-Energized'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_MANHOLE_CLEANING_ENER = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Manhole Cleaning Energized'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_MANHOLE_INSPECTION = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Manhole Inspection'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_UG_EQUIPMENT_INSPECTIONS = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''UG Equipment Inspections'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_UG_INFRA_RED_SCANNING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''UG Infra Red Scanning'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_UG_CABLE_LOCATES = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Underground Cable Locates'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
------------------------ start SCM
if :P33_FENCING_AROUND_SUBSTATION = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Fencing Around Substation'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_FENCING_GREENFIELD = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Fencing Greenfield'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_INSPECTION_AND_TESTING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Inspection And Testing'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_STATION_CIVIL_WORK = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Station Civil Work'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_STATION_CONST_DEENERGIZED = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Station Construction (De'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_STATION_CONST_ENERGIZED = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Station Construction (E'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_STATION_INFRARED_SCANNING = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Station Infrared Scanning'')) > 0) and
(instr(upper(b.”SET_YES_NO”),''NO'') > 0) ';
end if;
if :P33_STATIONS_ASBESTOS_REMOVAL = 'YES' then
if new = 'Y' then q := q || ' and ('; new := 'N';
else
q := q || ' or '; end if;
q := q || '(instr(upper(b."JOB"),upper(''Stations Asbestos Removal'')) > 0) and
(instr(upper(b."SET_YES_NO"),''NO'') > 0) ';
end if;
if new = 'N' then q := q || ' ) ';
end if;
q := q || ' ) ';
return q;
end;

I messed up files too many

I think i added my old jam packs, lucky me i already had them all.Here is the problem, i shifted all loops to external disk and logic recognizes them but i have triplicates of most files.It looks like i have 2 remixes and 2 rhythm I have caf and aif for both and i am not sure what to keep. With all picked i have 64k of loops. i compared my view window, to others i have seen, and i have an extra rhythm and i had all files in remix duplicated in both formats. i have seperated those but not sure which ones to keep Thanks. Jon

Hey Jon,
I don't think you messed up any files. They are probably just double (or triple) indexed. What you need to do is trash the Apple Loop Index files and re-index only the loops you want to use (you can trash any extra loops to save hard drive space too). Find /Mac HD/Library/Audio/Apple Loop Index and /Mac HD/User/Library/Audio/Apple Loop Index. Trash these files (make backups if you're worried) and then drag the loops from the external drive into Logic's Loop Browser. They will re-index and should only show 1 set thereafter.
As for which files to keep that depends on your needs. .aif files are larger but more universal (other apps, older GarageBand) with little? or no metadata and .caf are 1/2 size, Apple oriented and lots of metadata storage. Personally I trashed the .aif and am sticking with .caf.
Hope That Helps,
Dave

Compound trigger returns too many lines

Hi all.
I have created a compound trigger which executes a procedure. Although the trigger now runs (I was getting a mutating table error before), it returns multiple lines where I am expecting only one line. When I run the procedure by itself, without the trigger, it runs as expected. Truth is, I created the trigger based on an example I found online, and I am not sure how to modify it to my needs. I don't need the data I am generating in the AFTER EACH ROW section. It exists because the trigger doesn't seem to run otherwise. Any help would be highly appreciated.
create or replace trigger test.requisitions_trigger
FOR INSERT OR UPDATE ON test.supply_items
COMPOUND TRIGGER
TYPE t_change_tab IS TABLE OF test.tab1_audit%ROWTYPE; g_change_tab t_change_tab := t_change_tab();
AFTER EACH ROW IS
BEGIN
g_change_tab.extend;
IF INSERTING THEN
g_change_tab(g_change_tab.last).action := 'INSERT';
ELSE
g_change_tab(g_change_tab.last).action := 'UPDATE';
END IF;
g_change_tab(g_change_tab.last).created_time := SYSTIMESTAMP;
END AFTER EACH ROW;
AFTER STATEMENT IS
BEGIN
test.Requisitions;
END AFTER STATEMENT;
END requisitions_trigger;

In your Re: Mutating Table error - Compound Trigger, the REQUISITIONS procedure was taking an argument that was taken from the row being inserted or updated. In this version, there is no argument. If the REQUISITIONS procedure takes no arguments (and just to harp on it, I'll reiterate that having a table and a procedure with the same name is more than a bit confusing), then you just need a statement level trigger. A statement level trigger is free to query the table being modified all it likes without raising any mutating table concerns (because the current statements changes are either guaranteed to have not been applied or to have been completely applied, there is no risk of seeing data in an inconsistent state).
Justin

Too Many Lines of Code in Record Selection Formula....

I'm trying to run a crystal rpt. w/ over 2000 lines of code/conditions in Record Selection Formula, but the report bombs out after typing a little over 1065 lines of code.
I get the following error message:
Failed to open rowset.
Details: ADO Error Code: 0x80040e14
Source: OraOLEDB
Description: ROW-00001: Cannot allocate memoryD
Native Error: 1
Does anyone have any suggestions or possible solutions??

this is the oracle forms forum. your chances increase going to the right forum.
Gerd

Until how many lines can we write java file

in java file, how many lines can I write?
Manybe It will depend on file system such as window, unix file system.
but, I don't know the exact size.
please let me know how many lines I can wirte in java file of window and unix file system.
thank you in advance.

A class and method implementation in source lines of code (sans comments and white space) should be as large as necessary, but no larger. Good design principals tend to drive towards smaller peices, but there is no one right size size limit.
Personally, I suspect any method that has over 50 lines of code as being too large and probably refactorable. I also suspect any single class (or for that matter .java file) with more than 50 methods or more than 2000 lines of code as being too large and probably refactorable. But sometimes we might really need a 500 line method or an 8000 line, 200 method class. Maybe its a performance thing. Maybe it is just that complicated and too hard to break up. I doubt it occurs frequently, but I won't be shocked when I see it.
Sometimes GUI classes (Swing and AWT) get really huge. Sometimes this is due to code generation, sometimes its just being sloppy. It pays to know the difference.
But the Java langauge sets reasonable (if not overly generous) limits on bytecode and constant pool sizes If the Java compiler begins to complain that something you have built is is too large, face it, it probably is. It's like running into scope nesting or nested name (class in a class in a class...) size limits - usually not a good sign for the structure of your code.
Chuck

Increase number of rows in a Conversion File

Hi Experts,
I´m setting up a huge conversion file (around 25000 rows), and when I`m going to validate it, Only the first 3568 rows are safe.
Does anybody know how to modify the conversion file, in order to allow more rows?
Thank`s in advance.

Hi,
Isnt it very tedious to maintain such a huge conversion file? Can you consider to use some java scripts or some wild characters to reduce the number of rows in your file.
Hope this helps.

Custom Office 2007 Doc Service Errors: Too many, ignored; Filtering Failed

Hi...
We are running SES 10.1.8.4 with the MS Office 2007 workaround outlined at: http://blogs.oracle.com/searchtech/
While indexing production files, a number of the following errors were logged (cleansed to hide actual paths, files names, servers, etc.):
ERROR crawler_5 1114 files inside zip file, Too many, ignored: /.../46629_bin
ERROR crawler_5 EQG-30123: Filtering failed for "http://someserver/somefile.docx&lang=en"; trace information:
1114 files inside zip file, Too many, ignored: /.../46629_bin
It appears like all these errors are for docx files. This could just be a coincidence. We have very limited access to the files themselves due to confidentiality.
In reading the README file for the MS Office 2007 document service, ZIP is one of the required document types for this workaround. Specifically,
the OfficeX files are XML packaged in zip format, so you must tell SES to index zip files
Is the custom MS Office 2007 document service not able to index certain docx files?
Are these files too large and/or complex for indexing?
Any guidance is appreciated.
Thanks!

More information. All the documents that throw this error are between 9.5 - 13.5 MB in size.

Huge Conversion File - Too many lines

Similar Messages

Maybe you are looking for