FORM quantity elements limitation

[Former Member]

Is there any limitation about the quantity of elements that a FORM may have?

I am asking it because Iam developing a form with "TOO" much elements and the system doesnt compile the code giving me a message "GEN_BRANCHOFFSET_LIMIT_REACHED" (SHORT DUMP). I am going to put an OSS message, but I just want to know if someone had this problem.

thanks again

Ariel

[rainer_liebisch]

Hi Ariel,

please search in this forum for GEN_BRANCHOFFSET

There is also a reply written by me. It's not a bug.

Thanks and regards,

Rainer

[Former Member]

I only had a limit problem when my App was more than 10000 lines.

How many elements do you have?

[Former Member]

Craig, I have a page with a Tabstrip with 7 Tabstrips items. Then in each tabstrip item I have:

1. 18 fields and 1 tableView

2. 6 fields and 1 tableView

3. 3 fields and 1 tableView

4. 15 fields and 1 tableView<-Up to here everything is OK

5. 8 fields and 1 tableView

6. 10 fields and 1 tableView

7. 4 fields and 1 tableView

Then the tableView"s" has iterators with the same element of fields in each cell... It is a MONSTER page... haha

I have solved the problem deleting the tabstrips and using 7 diferent pages and using links.

A colleague that is working in another project had the same problem and solved it as I .

Well thanks again for helping Craig...

Cheers Ariel

[Former Member]

1. 18 fields and 1 tableView

2. 6 fields and 1 tableView

3. 3 fields and 1 tableView

4. 15 fields and 1 tableView<-Up to here everything is OK

Sounds like it was the line limit?

Remember to mark you message solved to help others in the future searching for help.

[thomas_jung]

I assume that you were including the content of your tabstips items all within the same page. Another alternative would be to use Model-View-Controller. Insde the content of each tabstrip Item, just make a call to one or more controllers. You can then put the logic in to call the correct view for each tab strip item. Each view will be generated into its own ABAP class so you shouldn't hit the generation limit.

Also I usually code my controller so it will only call the view for the Active Tab. That way I am not generating and sending a lot of extra HTML to the client just for tabs that aren't present yet. The following is a little code sample of one of my tab strips:

<phtmlb:containerTabStrip id                    = "TabStrip15"
                          collapsed             = "FALSE"
                          collapsible           = "FALSE"
                          firstVisibleItemIndex = "1"
                          hasContentConnector   = "TRUE"
                          maxVisibleItems       = "5"
                          onCollapse            = "myCollapse"
                          scrollableItems       = "TRUE"
                          selectedIndex         = "<%= application->SELECTED_date2       %>" >
  <phtmlb:containerTabStripItem id    = "D_RTY"
                                title = "<OTR>Yield Dates</OTR>" >
    <phtmlb:containerContentItem>
      <bsp:call url     = "selection.do"
                comp_id = "d1" />
    </phtmlb:containerContentItem>
  </phtmlb:containerTabStripItem>
  <phtmlb:containerTabStripItem id    = "D_PARETO"
                                title = "<OTR>Pareto Dates</OTR>" >
    <phtmlb:containerContentItem>
      <bsp:call url     = "selection.do"
                comp_id = "d2" />
    </phtmlb:containerContentItem>
  </phtmlb:containerTabStripItem>
</phtmlb:containerTabStrip>