Subject: | |
From: | |
Reply To: | |
Date: | Wed, 20 Nov 1996 18:04:32 -0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
M Gopalakrishnan wrote:
>
> Hi
>
> We are currently in the process of adding new CENTURY variable for
> MPE/iX.
>
> Proposed HPCENTURY CI variable would return the century component
> (first two digit of the current year) corresponding to the HPYEAR
> CI variable. For example,
>
> In 1997, HPYEAR = 97 and HPCENTURY = 19
> 2000, HPYEAR = 00 and HPCENTURY = 20
> 2001, HPYEAR = 01 and HPCENTURY = 20 and so on.
>
> Hence, we would be having HPCENTURY and HPYEAR variables to get the Year.
>
> Question : Do you need (how important it is) to have a new CI variable for
> four-digit year, having 1997 for Year 1997, 2000 for Year 2000,
> and so on?. If you need, what would be the better name for the
> variable? (one suggestion is : HPYEAR4).
Hi,
I don't see any reason to create something like HPYEAR4. What I think
that would be a good thing to have is a variable for the complete date
in the format YYYYMMDD (e.g. 19961120).
Something else that I was looking for recently also might be interesting
to have, and that is a variable for the calendar week. I have put this
in this newsgroup a few weeks ago and I received different answers on
how to calculate this number. Having it at system level would be nice.
Don't you think so ?
Best regards,
Marnix Van Achter
Supply Chain Software
Belgium
|
|
|