not able to make new add on layout feature working

[former_member210167]

Hi there. We are using SBO 8.81 PL09 and have make an addon with UDO's. Triying to print the udo objects thorw crystal report and doing everything explained here:

[http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26720%3Fpage%3Dlast%26x-order%3Ddate%26x-showcontent%3Doff]

System gives us an error:

"Input string was not in a correct format". Problem arises when executing:

 Private Sub SBO_Application_LayoutKeyEvent(ByRef eventInfo As SAPbouiCOM.LayoutKeyInfo, ByRef BubbleEvent As Boolean) Handles SBO_Application.LayoutKeyEvent
        Dim oForm As SAPbouiCOM.Form = SBO_Application.Forms.Item(eventInfo.FormUID)
        Dim oEdit As SAPbouiCOM.EditText = oForm.Items.Item("4").Specific
        If eventInfo.BeforeAction = true Then
            eventInfo.LayoutKey = oEdit.Value
        End If

We are stuck with this matter. Anyone have a clue?

Thanks so much!

[Former Member]

Do you know if you have successfully loaded the report through the first 5 steps? Use Try Catch block if you need.

[former_member210167]

Yes, I did. Actually, System asks me to introduce the DocKey@ manually and after that, shows me the layout. I loaded the form by code and by hand, after creating the new report layout type. None of them are working.

Thanks Gordon for your quick reponse

[Former Member]

The new report type may support report only from system table. Check that out.

[former_member210167]

What do you mean? I cannot make a CR report against UDO tables? If do, this new feature is not very useful...

[Former Member]

I mean you can make a CR report against UDO tables but new feature may not support it.

[former_member210167]

As far as I know, new feature does support UDO tables. I have made a test with a simple crystal against OINV table and it is not working either! Maybe it is a bug. I have to check on an earlier path.

[Former Member]

If a simple crystal against OINV table not working, something must be wrong within database. It might be due to bug. However, you need to check demo database first.

[former_member210167]

Finally I got the solution.It is a SAP bug. It is fixed on 8.81 PL11

Check this link:

Thanks everybody