SAP Issue - SAP 9.1 can result in B1UP new Tab feature can cause SAP B1 Client crashes

In SAP 9.1 there is unfortunately a new bug/limitation that can potentially in combination with B1UP's new tab feature cause the SAP Business One client to crash after updating BP Master data (and potentially other SAP windows) :-(

What is the symptoms (how does it fail)?

We are still early in the full investigation but what we are seeing is that after an update of BP Master Data and press of the OK button, the B1 Client become unresponsive and crashes

Who is affected?

People that are running SAP 9.1 and have created one or more tabs with the Tab wizard are potentially affected.

If the 2 above statements is true and you have issues then try to run the following SQL statement against the SAP database. If it return records you are most likely affected.

MSSQL:

SELECT DISTINCT Code+': UF - Content creator need to be to a new panelevel' AS Description FROM [@BOY_41_FUNC_L02] WHERE U_BOY_FPN > 999 OR U_BOY_TPN > 999
UNION ALL
SELECT Code+': UF - Macro pane-switcher need to be to a new panelevel' FROM [@BOY_41_FUNCTIONS] WHERE CAST(U_BOY_MCRO AS NVARCHAR(4000)) IN ('Panelevel(1000);','Panelevel(1001);','Panelevel(1002);','Panelevel(1003);','Panelevel(1004);','Panelevel(1005);','Panelevel(1006);','Panelevel(1007);','Panelevel(1008);', 'Panelevel(1009);', 'Panelevel(1010);')
UNION ALL
SELECT DISTINCT Code+': IPT - System lines that need new panelevel' FROM [@BOY_IPT_SYS] WHERE U_BOY_PANE > 999 OR U_BOY_PAN2 > 999
UNION ALL
SELECT DISTINCT Code+': IPT - UDF lines that need new panelevel' FROM [@BOY_IPT_UDF] WHERE U_BOY_PANE > 999 OR U_BOY_PAN2 > 999

HANA:

(((SELECT DISTINCT "Code" || ': UF - Content creator need to be to a new panelevel' AS "Description" FROM "@BOY_41_FUNC_L02" WHERE "U_BOY_FPN" > 999 OR "U_BOY_TPN" > 999 UNION ALL SELECT "Code" || ': UF - Macro pane-switcher need to be to a new panelevel' FROM "@BOY_41_FUNCTIONS" WHERE CAST("U_BOY_MCRO" AS NVARCHAR(4000)) IN ('Panelevel(1000);','Panelevel(1001);','Panelevel(1002);','Panelevel(1003);','Panelevel(1004);','Panelevel(1005);','Panelevel(1006);','Panelevel(1007);','Panelevel(1008);','Panelevel(1009);','Panelevel(1010);') )  UNION ALL SELECT DISTINCT "Code" || ': IPT - System lines that need new panelevel' FROM "@BOY_IPT_SYS" WHERE "U_BOY_PANE" > 999 OR "U_BOY_PAN2" > 999)  UNION ALL SELECT DISTINCT "Code" || ': IPT - UDF lines that need new panelevel' FROM "@BOY_IPT_UDF" WHERE "U_BOY_PANE" > 999 OR "U_BOY_PAN2" > 999)

I'm affected. What to do?

The issue is that the items placed on tab each have a panelevel (FromPane and ToPane). In the past this number had no limitations but in SAP 9.1 it can max be 3 digits so if a panelevel is defined as 1000, 1001, etc. it cause the issue. 

The fix is to choose a lower panelevel. An easy rule for that is that panelevel 1000 should be converted to 100 and 1001 should be converted to 101 ect. The SQL you ran previous tell you what Universal Functions need to be changed because the panelevel is too high.

Sample fix

Here I will show you a sample of the bug and how we fix it.

On BP Master Data we have a simple tab:

Running the SQL it give me 3 task (you might get more or less)

This mean that in order to fix this I need to go to the 2 Universal Functions and the one Item Placement tool. Lets do that.

First UF-001. Here the columns "From Pane" and "To Pane" have value 1000. We need to change that to 100 instead.

Next is UF-002. Again need to change 1000 to 100

Finally we need to look at the Item Placement Tool. Again "from" and "to pane" columns need to be changed from 1000 to 100

Going forward (What will Boyum do?)

• Change how new tabs are created so it will not suggest a tab with pane higher that 999
• Investigate if we can implement some kind of auto-fixer for the issue (that automatically does what is shown above)
• Log a general SAP support ticket to highlight the issue