BRF+ condition fetch results in dump SYNTAX_ERROR

[rajukammella]

Hi,

we are using SAP TM 9.0 and during Freight order creation, we use some of the input parameter's and send this data to a BRF+ condition table in our custom Method and fetch the results and use it for further processing.

The condition table had 10 input fields and 3 output fields. It was working fine till now with around 4700 lines in the table. Recently the condition records on the BRF+ table have been increased to a total of 5300 lines.

After this, whenever a condition fetch is triggered in the Method, the system is resulting in a SYNTAX_ERROR dump. I am trying to understand how the below Methods are created to check the number of rows in a condition table are created.

More interesting, while observing the dumps i have found that the Class (Method - UPTO*ROW*) until ROW 5011 is same, But for the last Method i.e. UPTO row 5298, the Class is different. And whenever the system is encountering this Method, it is directly resulting in a dump.

Please help.

Thanks in Advance.

[RaminS]

So if you go to the generated class and do a syntax check does it show a Syntax Error? or is this a runtime dump. Maybe something in the data model changed after the class was generated that is causing the syntax error. If it's a runtime error then definitely report it.

I agree with Mike's point about revisiting the design, We have a decision table that has 10,000 rows (generated dynamically using APIs) and even though it works fine, the question of whether using a decision table in this case has any merit over DB tables, is a legitimate question. BRF+ is supposed to provide better visibility into business context and easy maintenance of business rules. It's hard to argue that a 5K long decision table provides any higher degree of business access.

If you're using expressions like Value Ranges or formulas in the decision table then it makes sense. These can potentially replace multiple rows of a DB table into one single row of decision table and provide tangible benefits for using BRF+.

[pokrakam]

That number of rows makes me wonder whether your design is appropriate. Are you really using the features of BRFplus, or is it just something you could implement in a standard DB table?

To your questions: Decision tables are compiled into code. Once the limit of what can be written into a class is reached, further classes are created. I suspect there is a bug as this is generated code and should be free of syntax errors. Please have a look for notes, and report to SAP if you don't find anything.

Also consider if you can compress your table, this could reduce the size back to where it works. But I'd still suggest reporting this.