Overview
This page is used for managing the backdating of many of the Cost Transactions generated in Rootstock, setting the ‘Override Transaction Date’ (aka Accounting Date) set to the 'backdate' on the Inventory Cost Transactions created for those ERP transactions performed. Backdating is often used in normal transactions such as PO Receipts, SO Shipments, and Shop Floor transactions. can not be done during a specific period of time due to things like Physical Inventory, Plant Shutdown, etc.
NOTE Although this date is set to the 'backdate', the Date/Time of these transactions (Transaction Date) is still set to the actual day the transaction was performed, leaving the transaction with two dates, the actual Transaction Date and the Backdate.
Navigation
Cost Accounting Control Record
Processing
Header Section
The design of this section is intended to allow, on a transaction-type-by-transaction-type basis, an Accounting Department to manage what can be backdated, define the date that transactions will be backdated to, Define who can do the backdating, and how long backdating can occur. This record is meant to be updated as often as necessary to handle various occurrences when backdating is required.
EXAMPLE
At the start of a new fiscal month, PO receipts have been physically performed but have yet to be entered into the system. Accounting wants the transactions booked into the fiscal month that just ended.
In this example, the last day of the prior fiscal month is March 31, 2022. Therefore, the ‘Backdate’ field would be set to 3/31/2022.
A user is designated to enter the PO Receipts that need to be backdated. Their User Number is entered in the ‘PO Receipt Backdating User No’ field.
It has been estimated that it will take 10 days, or until April 10, to perform all the backdated PO Receipts. ‘10’ is entered in the ‘PO Receipt No of Transact Days’.
So, from 3/31/2022 for the subsequent 10 days, when the user named in the ‘PO Receipt Backdating User No’ field performs ANY PO Receipts, those receipts will have their ‘Override Transaction Date’ (aka Accounting Date) set to 3/31/2022 on the Inventory Cost Transactions created for the PO Receipts performed.
Fields
Division: The Division associated with this Cost Accounting Control record.
Backdate: The date to which the transactions identified in the upper section of the page will be set to on the ‘Override Transaction Date’ field for affected Inventory Cost Transactions.
IMPORTANT Make sure you have your Division's Shop Calendar defined for this date. For example, if you want to backdate to 2020, you will need to define a Shop Calendar for 2020.
The following is just one set of fields pertaining to a particular transaction; all sets of fields follow the same convention.
PO Receipt Backdating User No: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
PO Receipt No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Sales Order Issue Backdating User ID: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Sales Order Issue No Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Inventory Adjustment Backdating User: ID of the User associated with the transaction to be backdated. Transactions performed by this User will be backdated if the system date is within the specified range.
Inventory Adjustment No of Transact Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Inventory Scrap Backdating User: ID of the User associated with the transaction to be backdated. Transactions performed by this User will be backdated if the system date is within the specified range.
Inventory Scrap No of Transact Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Loc to Loc Move Backdating User Id: ID of the User associated with the transaction to be backdated selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Loc to Loc Move No of Transaction Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Cycle Count Adj Backdating User Id: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Cycle Count Adj No of Transact Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Phy Inv Adj Backdating User Id: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Phy Inv Adj No of Transact Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Labor Booking Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Labor Booking No of Transact Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
RMA Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
RMA Receipt Backdate Number of Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
RMA Shipment Backdate Number of Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
WO Issue Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
WO Issue No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
WO Receipt Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
WO Receipt No of Transact Days: The system uses the number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
WO Scrap Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
WO Scrap No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
WO Close Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
WO Close No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
PO Close Backdating User: ID of the User associated with the transaction to be backdated, selected from the dropdown. Transactions performed by this User will be backdated if the system date is within the specified range.
PO Close No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Standards Change Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Standards Change No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
PO Issue Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
PO Issue No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Inv Loc Add Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Inv Loc Add No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Inv Dol Adj Backdating User: ID of the User associated with the transaction to be backdated, selected from the drop-down. Transactions performed by this User will be backdated if the system date is within the specified range.
Inv Dol Adj No of Transact Days: The system uses this number of days to calculate the end date of the backdate period. (End date = backdate date + Number of Days).
Authorized User to Change Cost Method: This field identifies the user authorized to change the Divisional Cost Method. It is selected from the drop-down.
Tab Section
Transaction Overrides tab
This tab contains overrides for a subset of transactions. When a displayed transaction's checkbox is checked, the Date field in the UI where these transactions are performed allows the Date (which defaults to TODAY) to be backdated to whatever date the user enters. When this is done, those transactions will have their ‘Override Transaction Date’ (aka Accounting Date) set to the user-entered date on the Inventory Cost Transactions records created for those transactions performed.
NOTE Although the ‘Override Transaction Date’ on Inventory Cost Transactions is set to a 'backdate', the Date of these transactions (Transaction Date) is still set to the actual date the transaction was performed.
Fields
Allow Manual SO Date Overrides: When checked, it enables the Transaction Date Override button in SO Fulfillment, where an override date can be entered. The overridden date is used on the SO Issue transaction (Consolidated and P/P/S) and the SO Shipment transaction (when using Pick, Pack, Ship).
Allow Date Override to Inv Adjustments: When checked while doing an Inv Adjust in the given Division, a 'Transaction Date' will be displayed on the 'Inventory Adjust' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to Inv Location Add: When checked while doing an Inventory Add in the given Division, a 'Transaction Date' will be displayed on the 'Inventory Add' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to PO Issue: When checked while doing a PO Issue in the given Division, a 'Transaction Date' will be displayed on the 'PO Issue' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to PO Receipt: When checked while doing a PO Receipt in the given Division, a 'Transaction Date' will be displayed on the 'PO Receipt' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to PO Authorization: When checked, when doing a PO Authorization in the given Division, a 'Transaction Date' will be displayed on the page, defaulted to TODAY. If changed, the 'Accounting Date' on the associated Inventory Cost Transaction record will be set to that date.
Allow Date Override to RMA Transactions: When checked, while doing an RMA Receipt, a 'Transaction Date' field will be displayed on the 'RMA Mass Receipt' and the 'RMA Receipt' pages, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to WO Receipt: When checked while doing a WO Receipt in the given Division, a 'Transaction Date' will be displayed on the 'WO Receipt' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to WO Issue: When checked while doing a WO Issue in the given Division, a 'Transaction Date' will be displayed on the 'WO Issue' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to Inv Loc Xfer: When checked while doing a Loc Transfer in the given Division, a 'Transaction Date' will be displayed on the 'Inv Loc Transfer' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to Inv Proj Xfer: When checked while doing a Proj Transfer in the given Division, a 'Transaction Date' will be displayed on the 'Proj Transfer' page, defaulted to TODAY. If changed, the 'Accounting Date' on the Inventory Cost Transaction record will be set to that date.
Allow Date Override to SYDATA Labor Bkng: When checked, while doing Labor Booking through SYDATA in the given Division, the user can specify a date to the field 'Accounting Date Override' on SYDATA. If specified, the 'Accounting Date' on the Inventory Cost Transaction record and the 'Transaction Date' of the Employee Clock Transaction record will be set to that date.
Disallow Date < Today in Time & Qty Bkng: When checked, users are prevented from entering a Transaction Date earlier than 'TODAY' in the Time and Quantity Booking page.
NOTE The fields Allow Date Override to PO Issue / WO Issue and Allow Date Override to PO Receipt/ WO Receipt are also applied to Purchase Order & Work Order reversal processes (UI only, not applicable yet through SYDATA).
SEE ALSO
Cost Accounting User Control Record
Inventory Cost Transactions
