Skip to Content

For todays evening I had originally planned commenting the brand new TechDemo
Addon I published yesterday.

However I had to work with the SAP Business One database today and that changed
my mind in an instance.

I grant the fact that SAP Business One is a grown solution which originated
in Israel.

Sure, it has been adapted to fit the needs of an international market and there
are a lot of remains of the old base..

I also realize that there are some things a developer just has to live with when
using a product he has not created.

However, somtimes you have the feeling that things are just not going the right
way and your inner self refuses to live with the odd bit sticking out.

The odd bit

Today my colleague came to me with a simple question. “We have a time field in a
report which is unformated, could you please alter the format?”

The field showed “1430” instead of “14:30h”. Thinking “Not a big deal“, I

went to check.

To report this post you need to login first.

2 Comments

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

  1. Scott Barden
    Hi Lutz,

    I can sympathise with this situation, as R/3 stores dates and times as separate numeric character string values – YYYYMMDD and HHMMSS.

    Whilst we at least have the benefit of automatic formatting, this type of date/time persistence is a real pain in the backside, particularly when searching for data falling between date/times.  It also prevents simple date/time arithmetic.

    For example, a user cannot run a report once to select data between 2 different date/time ranges.

    BTW, in the Microsoft world, date/time values are actually stored doubles.  The significant digits represent the date and the decimal value the time (as a proportion of 24hours).

    My other pet peeve is lack of boolean as a fundamental data type…

    Cheers,
    Scott

    (0) 
  2. Lutz Morrien Post author
    … for setting that right.
    Of course a date is a floating point value.
    It is a shame that SAP does not use it for what it is there.

    The boolean trap exists in SBO as well. There is just true or false and not Y/N or J/N. Boolean is valid for all languages, Y/N is not.

    Guess we just have to live with it.

    Lutz Morrien

    (0) 

Leave a Reply