Limit for rows in a shuttle?

Question

Hello All,
Application Express 3.1.2.00.02
IE 7
I select 5000 rows (line ids) in my shuttle then press a button which passes the ids to a PL/SQL package to update a table using these line ids, this is something I've done in many applications. The problem in this case is only 4000 rows get updated. I receive no error when moving from the left to the right side of the shuttle or at any other time in the process. Everything seems to be just fine, until I look at the results and only 4000 rows were updated.
Does anyone know what limit am I running into here? Is there a work around?
Here is my code which includes the call to the PL/SQL package.
Thanks!
Declare
l_selected APEX_APPLICATION_GLOBAL.VC_ARR2;
lqtelntbl  FORX_QOT_PRICING.gQteLnTbl;
x PLS_INTEGER := 1;
BEGIN
-- Convert the colon separated string of values into
-- a PL/SQL array
If :P2_APPLY_TO_LINES = 'NA' Then
  RAISE_APPLICATION_ERROR( -20110, 'At least one line is required.' );
End If;
l_selected := APEX_UTIL.STRING_TO_TABLE(:P2_APPLY_TO_LINES);
-- Loop over array
FOR i IN 1.. NVL(l_selected.count,0)
LOOP
  If l_selected(i) != 'NA' Then
    lqtelnTbl(x) := l_selected(i);
    x := x+1;
  End If;
END LOOP;
FORX_QOT_PRICING.CostUpdate( pQteHdrId   => :P1_SEARCH,
                      pQteLnTbl   => lQteLnTbl,
                      pFieldName  => :P2_FIELD_NAME_SELECT,
                      pFieldValue => :P2_FIELD_VALUES,
                      pSupplierId => :P2_DEFAULT_SUPPLIER,
                      pSubInventory => :P2_SUBINVENTORY,
                      pClass      => :P2_CLASS,
                      pWhse       => :P2_WHSE,
                       -- begin JVM changes
                      pMaintLinkQuote  => :P2_MAINT_LINK_QUOTE,
                      pIncumbent       => :P2_INCUMBENT,
                      pEndOfLife       => :P2_END_OF_SERVICE_LIFE,
                      pMaintType       => :P2_MAINTAINENCE_TYPE2,
                      pContractStart   => :P2_CONTRACT_START_DATE,
                      pServiceDuration => :P2_SERVICE_DURATION,
                      pContractEnd     => :P2_CONTRACT_END_DATE,
                      pContractCoTerm  => :P2_CONTRACT_COTERM_DATE,
                      pMultiTermEndDate => :P2_MULTI_TERM_END_DATE,
                      --pPricingAnalyst  => :P2_PRICING_ANALYST,
                      --pMaintSpecialist => :P2_MAINTENANCE_SPECIALIST,
                      --pMaintTypeHead   => :P2_MAINTENANCE_TYPE1,
                      -- end JVM changes
                      pUserId     => :P1_USERID,
                      pRespId     => :P1_RESPID,
                      pRespApplId => :P1_RESPAPPLID );
END;

Answer 1

Thanks for the reply. Here's what I know for sure...
The shuttle (:P2_APPLY_TO_LINES) has 5000 rows (line ids) on the left side that are moved to the right. The page submits and calls my process, which calls a database package, no problems occur in the form of an error, but not all the rows that were in the right side shuttle get updated.
In order to find out what's going on I figured I would determine the length of the delimited string in :P_APPLY_TO_LINES. I created a custom table with one column, datatype CLOB and inserted :P2_APPLY_TO_LINES into it as the first step in my process (before calling my database package). The length of this value is 32000. I then changed the shuttle LOV and used a different value (line number as opposed to line id) as the return value in the LOV definition. The shuttle item length still maxed out at 32000 when inserted into the CLOB column BUT more rows were processed by my procedure because more line numbers "fit" into :P2_APPLY_TO_LINES. This is because the max length of the line number is 4 digits in this case (lines 1-5000) while every line id is 7 digits.
So I'm guessing there is a limit to the length of a shuttle item, and this limit is 32000. I'd just feel better if someone can confirm this, and I'm more confused by the fact that I don't get an error. You'd think if I tried to cram 40000 into a field that can only hold 32000 that I'd get an error. As it stands, if my users aren't paying attention they'll think they're updating all the rows when in reality they're only getting as many as :P2_APPLY_TO_LINES can hold.
Does anyone have an opinion if my analysis is correct?
Edited by: blue72TA on Mar 2, 2012 9:49 AM
Edited by: blue72TA on Mar 2, 2012 9:50 AM