SentDtTm field: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →See also: m |
mNo edit summary |
||
Line 8: | Line 8: | ||
| data_element_sort_index = 6 | | data_element_sort_index = 6 | ||
}} | }} | ||
It is automatically populated during [[sending]]. | It is automatically populated during [[sending]]. | ||
== Data Use == | == Data Use == | ||
Line 27: | Line 20: | ||
== Potential Change == | == Potential Change == | ||
{{potential Change}} These should be moved to the same spot in | {{potential Change}} These should be moved to the same spot in CFE as CCMDB. | ||
[[Category:Sending]] | [[Category:Sending]] | ||
[[Category:AutoTimeStamps]] | [[Category:AutoTimeStamps]] |
Revision as of 10:26, 2017 March 17
Data Element (edit) | |
Field Name: | SentDtTm |
CCMDB Label: | not stated |
CCMDB tab: | not stated |
Table: | L_Log |
Data type: | date |
Length: | not stated |
Program: | Med and CC |
Created/Raw: | Raw |
Start Date: | 1988-07-11 |
End Date: | 2300-01-01 |
Sort Index: | 6 |
Time the record was last sent.
It is automatically populated during sending.
Data Use
Instructions for requesting a batch of data from DSM uses this.
See also
- LastOpened_DtTm field - cfe and ccmdb
- Start_Date field/Start_Time field - cfe
- LastChanged_DtTm field - apparently only in ccmdb_data.mdb, after recordstatus which is in different spot in ccmdb(later) than in cfe(earlier)
Potential Change
Template:Potential Change These should be moved to the same spot in CFE as CCMDB.