MCTFSPRIUM 12-120303 - AUDIT REQUIREMENTS FOR THE UNIT ELECTRONIC DIARY FEEDBACK REPORT (DFR)

Paragraph 120303, Chapter 12 of the MCTFSPRIUM. Reproduced from the 2026-06-01 manual snapshot (source file 20303_AUDIT_REQUIREMENTS_FOR_THE_UNIT_ELECTRONIC_DIARY_FEEDBACK_REPORT_DFR.md). Verify against the live manual before reporting a transaction: Open the PRIUM on MOL (MOL access required).

Source text

Section 1

General Information.  The DFR will be viewed on the date the cycle becomes available, except for cycles becoming available over a weekend or during a holiday.  In these cases, the DFR will be viewed on the first working day after the weekend or holiday.  Each MCTFS cycle will be accounted for.  All DFRs, to include DFRs comprised of inconsistent conditions, will be certified by the commanding officer or the individual designated by the commanding officer serving in the capacity as the certifying officer, within 10 calendar days.  In order to accurately audit the DFR, it must be addressed by parts.  The following audit requirements are provided as applicable to those parts:

a.  Part I will contain all unit diaries that processed in the requested cycle.  If the DFR is requested without a cycle number, Part I will contain all unit diary information on the Diary Statistic Report (DSR) for that reporting unit.  The transactions total for each unit diary will be compared to the total number of action statements on the Transaction Counter Page of the unit diary

b.  Part II contains error messages generated from unit diaries submitted by the reporting unit.  Therefore if no unit diaries are processed for the cycle requested, or if there are no rejected transactions listed on Part I, there will be no action required.  If there are rejected transactions on Part II of the DFR, the following actions are required:

(1) Each transaction listed on the report will be audited to determine why the transaction failed to process correctly.  The error message printed below the transaction gives a brief reason for the failure and should be used as a starting point for research.  Once the reason for the error is known, the appropriate correction procedures can be taken.

(2) Each error will be annotated with the corrective action taken, to include unit diary number and date of the unit diary that reported the corrective action

(3) Request assistance from your regional Manpower Information Systems Support Office (MISSO) when efforts to take corrective action at the reporting unit fail or when the unit has questions concerning error messages. c. Part III contains advisory messages generated from several different modes of input and are not connected to a particular unit diary submitted by the unit.  Therefore, a unit may not have submitted a unit diary for several days and still have advisory messages posting to Part III of the DFR for cycles processed during the period that no unit diaries were submitted.  If there are advisory messages on this part, the following actions are required:

(1) Each advisory message will be annotated with the corrective or appropriate action taken.  Those messages requiring unit diary action will also be annotated with the unit diary number and date of the unit diary reporting the corrective action.  Only those advisory messages not requiring any type of action will be annotated with No Action Required "NAR" or words to that effect.  In those cases where unit diary action is not required, annotate corrective action; for example, letter sent to the Commandant of the Marine Corps, Disbursing Officer, etc.

(2) Caution must be taken to ensure that each advisory message is analyzed on its own merit.  Information regarding composite score data elements, composite scores, PUREX routines and messages from Headquarters, U.S. Marine Corps or from the Department of the Navy Central Adjudication Facility (security clearance action) is often times looked upon as routine in nature.  The action does not stop at the unit diary section; further action may not be complete until the advisory message is passed to another work section, the S2, S3 Training Section or the Marine's individual company commanding officer, or even a personal interview with the Marine.

(3) Request assistance from your servicing Manpower Information Systems Support Office (MISSO) when all unit efforts to resolve advisory messages fail or when the unit has questions concerning advisory messages.

Section 2

The 'Diary Feedback Report Summary' view provides the status of all EDFR Cycles downloaded to UD/MIPS.  This window is defaulted to display all cycles downloaded, in cycle order, ascending.  The Diary Feedback Report Summary can be filtered by Cycle Status by selecting a status from the dropdown list. a.  A Certifier can change the EDFR cycle status in this window by selecting the appropriate status in the 'Cycle Status' dropdown list.

Section 3

The 'Diary Feedback Cycle' view contains the traditional three-part DFR.  The Diary Feedback Cycle will contain three Tabs labeled, Part I, Part II and Part III.  The column headers, on each tab page, are sort filters that are activated by clicking the header.  Only one column header can be used for each sort; nested sorts are not possible.  The following functionality is available within each part of the DFR:

a.  Part II, Part III transactions can also be filtered.  The 'Filter By' dropdown list box allows the user to select user-defined filters from either a Section or Status.

b.  'Flag Codes' denote the status of EDFR transactions.  The below Flag Codes apply to Parts II and III: FLAG CODES CODE | DESCRIPTION O | Open.  The transaction has not been worked and has no notes against it. N | Open, with Notes.  The transaction may be partially worked. W | Worked.  A user has put notes against it (with/without a corrective action) and there is no other action needed. V | Reviewed.  A reviewer has viewed and verified the correct action has been taken prior to certification. R | Rejected.  A user has annotated notes to the transaction and put it in a Worked status, but the Certifier rejected it.  Only a Certifier has the ability to put a transaction in Rejected status. C | Certified.  A user has annotated notes to the transaction and put it in a Worked status, and the Certifier has put the transaction in Certified status.  At this time, no other notes can be made against the transaction.  EDFR transactions can only be changed to a certified status by a Certifying Officer, whom is authorized to certify an EDFR transaction.

Section 4

The 'Transaction Detail' view may be accessed by selecting and double clicking a DFR transaction from Part II, or Part III.  This view will display a single EDFR transaction and provide options to view EDFR cycle notes, apply an EDFR transaction status, and apply an EDFR transaction note.  Also, the “Add to Diary/Pool” button will be available to Preparer ELSIGs.  When selected, this button will open the unit diary module where a unit diary entry may be created and applied to the selected DFR transaction.  The unit diary English statement is automatically displayed in the Transaction Notes. The EDFR information (that is, Cycle Number) is automatically applied to the unit diary entry's historical statement.  All notes added to the transaction are displayed in the DFR Notes.

Section 5

The EDFR transaction status will automatically change to a 'Worked' status if a note is applied or a unit diary entry is reported on a Part II or Part III transaction.  Preparers can change the transaction status from 'Worked' to 'Open'.  The Preparer must select the 'Save' button to save all changes and maintain the 'Worked' status.  Certifying Officers can change an EDFR transaction status from 'Open' to 'Worked' if a note is applied to the transaction.  Also, they may change and save a transaction status from 'Rejected' to 'Certified', again if a note is applied to the transaction. 6. Administration Reporting Unit Codes may produce an EDFR for subordinate Reporting Unit Codes.  A dropdown box containing the available subordinate Reporting Unit Codes is located on the EDFR Toolbar.  By selecting a subordinate RUC from the list, the user will gain access to the EDFR for the selected RUC.  If the RUC has no subordinate Reporting Unit Codes, they will not see the dropdown list.

Section 7

Filing Requirements

a.  'Archive DFR' archives a Certified DFR when it is complete.  When the DFR is archived, it is stored electronically to the UDMIPS server. The archive cycle(s) can be viewed by selecting ‘Archived DFR’. b. The Commanding Officer/Officer-In-Charge or certifying officer will verify the completion of the DFR. c. The DFR will be archived and retained for the current year plus two.

d.  No requirement exists to print, audit, or otherwise maintain DFR's.