Explanation of the difference between DET_DATE and DET_PUTIN_DATE fields in the database view [dbo].[AA_NL_ENQUIRY_ADVANCED_VIEW] for reporting purposes.
The view exposes two related date columns. Both are selected directly from the underlying base table SL_PL_NL_DETAIL without transformation.
The difference
DET_DATE: the transaction (accounting/effective) date. Per the base table comment, it is the "Trans date (copy of Header in Sale/Purchase, can be changed in Nominal)". This is the business/posting date the transaction is attributed to and drives the nominal period sort (DET_NOM_PERSORT)
DET_DATE_PUTIN: the "put in" date, i.e. the date the record was physically entered/posted into the system (an audit/data-entry timestamp), which can differ from the effective transaction date. It sits alongside DET_USER_PUTIN (the user who entered the record), reinforcing that this pair captures who entered it and when rather than the accounting date.
DET_DATE= the effective/transaction accounting date (and for Sales/Purchase it's copied from the header; it can be edited in Nominal).DET_DATE_PUTIN= the date the entry was actually put into (entered in) the system.
So for a transaction backdated to a prior period, DET_DATE would reflect the earlier accounting date while DET_DATE_PUTIN would reflect the later date it was keyed in.
