Difference between Normal Date and Closing date

zeninoleg

Maybe a silly question but....
What is the difference between Normal date and Closing date?

Savatage

What do you mean Normal Date?

zeninoleg

NORMALDATE (Date)
Use this function to return the normal date (as opposed to the closing date) for the argument Date.

I was going through the functions and found that one. I just want to know the logic begind the Closing date.

Alex_Chow

the NORMALDATE function is used to check if the value is a... umm..... a normal date. For example, it can't be a blank.

The closing date is dates used to close your income statement during year end. This way, you can see your income statement for year end without the closing entries.

zeninoleg

OK, let me just rephrase the question. What can be an example when one should use Closing date?

value is a... umm..... a normal date. For example, it can't be a blank.

Can a Closing date be Blank?

Alex_Chow

No, closing dates can't be blank.

You would use closing dates if you want to get the balance sheet for a particular year.

zeninoleg

Ok, thanks for your help

Alex_Chow

can you mark the topic as [SOLVED]?

zeninoleg

mmmmm........yep, I can.......I quess I am capable to........ :whistle:

David_Singleton

I wanted to stay away from technical stuff, but, IMO the information given here is not correct.

Navision internally stores DATE fields with one extra bit at the end. This bit is used to differentiate between NORMAL dates and CLOSING dates. In simple terms, a CLOSING Date is a period of zero time between two dates, i.e. a date between 23:59:59.9999 and 00:00:00.0000. For example, when sorting:

18102006D
C18102006D
19102006D

The prime purpose of Closing dates is to be able to post (most commonly) GL transactions in what some people call Period 13. This makes it possible to post closing entries that do not apear on either years accounts, but are visible in totalling.

Theoretically you can use 365 Closing dates in a year, and do normal transactions with them, but commonly they are only used to close a financial year.

The function NORMALDATE will return the normal date of a closing date, (Basically it just removes the C ). And CLOSINGDATE date does the opposite.

petevans

Ok so the only usage is to place a transaction outside of periods?

For example if I do Date1 := CLOSINGDATE(31.12.2006);

Then by comparison Date1 will be bigger than 31.12.2006 but smaller than 01.01.2007 so that it will "fall between" any code using comparison operators.

I'm a (novice) developer so I don't really see the business or financial benefits of this, but have I got the functional part right?

Thanks in advance.

David_Singleton

petevans wrote:

Ok so the only usage is to place a transaction outside of periods?

For example if I do Date1 := CLOSINGDATE(31.12.2006);

Then by comparison Date1 will be bigger than 31.12.2006 but smaller than 01.01.2007 so that it will "fall between" any code using comparison operators.

I'm a (novice) developer so I don't really see the business or financial benefits of this, but have I got the functional part right?

Thanks in advance.

Yes !

petevans

So in order for this functionality to have any meaning, it needs working code to use comparison operators ('>', '<', etc.) on dates?

David_Singleton

petevans wrote:

So in order for this functionality to have any meaning, it needs working code to use comparison operators ('>', '<', etc.) on dates?

Well not really, the whole point of closing dates was to work with FLow fields.

The filter 01/01/06..31/12-06 will give you all the numbers for this year, but will exclude any entries made on 31/12/06C, so you wont see the closing journal. Things like this.

petevans

Oh alright. I guess there is a comparison in the code for the filter somewhere then. Somewhere the system needs to determine whether or not 31/12/06C is within the filter, and that must mean a comparison of some sort, if I am not way off.

Anyway, thanks for your help! \:D/