Skip to Content

Introduction:

This blog focuses on a work around solution to read the negative precision value in BO-WEBI 4.1 version.

Issue:

In 4.1 version it has been observed that the smaller precision negative values are not picked in WEBI when BEX is used as a source of the data.

Bex Output:

Bex.JPG

WEBI Output for the relative Line:

WEBI-Before.JPG

Number Format of the Line:

Old.JPG

Work around solution:

Change the number format to below: Where negative is placed in apostrophe.

New.JPG

Please use the required decimals.

WEBI Output:

WEBI - After.JPG

Cause of the Issue:

This issue is coming in BO 4.1 when BEX is used as a source of the data and when the lines are using NODIM to suppress the units. NODIM values are not passing to WEBI when the values are too less.

This issue is identified in when the BW7.3 as backend and BO 4.1, the smaller negative precision values are not been pulled in WEBI for which the above work around works fine as a solution.

When BW7.4 as backend (Support Pack is less than 5), even the Smaller precision values both for Positive and Negative values also not been recognized by WEBI or by Crystal when the lines are using NODIM function. Quick work around is to remove the NODIM and then pull the values in reporting.

From SP5 of BW7.4, this side effect of NODIM is not occurring and the normal number formatting can be applied.

Hope this works for you. 🙂

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. venkat v

    Dear Murali,

    can you explain what are the Bex  variable worked or not   worked at WEBI side .when we created webi reports on bex what type of errors we face  and what are the bex options not reflected at webi side

    (0) 

Leave a Reply