General Ledger Control Report | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 44: Display General Ledger Exceptions (DGLE) |
Chapter 43: Resetting the General Ledger Interface File (RGLI)
Purpose: Use Resetting the General Ledger Interface File to clear the General Ledger Interface file and recreate postings based on updated or corrected information.
Note: You cannot run the reset for any period in which you have generated a general ledger download file. The Date posted field indicates that a General Ledger Interface record has been downloaded. See Generating the General Ledger Download File (GGLD).
When to run the reset: Normally, you use this menu option only if the general ledger is out of balance. You can use the General Ledger Control Report to determine if any journal sources are out of balance.
You can also use the reset if you change the setting of a system control value that affects how G/L transactions post.
You should not attempt to run the reset for the current date if there is any ongoing activity that could affect the general ledger, or if the asynchronous jobs are still active.
In this chapter:
• Reset General Ledger Interface Screen
Reset General Ledger Interface Screen
How to display this screen: Enter RGLI in the Fast path field at the top of any menu or select Reset General Ledger Interface File from a menu.
GLR0026 ENTER Reset General Ledger Interface 2/22/99 15:41:35 EZK Mail Order
Recreate records within the following date range:
Start date . . . .
End date . . . . .
Bank # . . . . . . . (for A/P Cash G/L#)
Division . . . . . . . (for A/P Division)
Submit to batch . . . . Y (Y/N)
Warning: All existing records within specified date range will be deleted!
F3=Exit F12=Cancel |
Field |
Description |
Start date |
The first date to include in the reset. Numeric, 6 positions (MMDDYY format); required. |
End date |
The last date to include in the reset. You should not attempt to run the reset for the current date if the asynchronous jobs are still active. Numeric, 6 positions (MMDDYY format); required. |
Bank |
The bank code to use for deriving the G/L account number for the credit posting for A/P disbursements. The system uses the A/P cash general ledger number. Bank codes are defined in and validated against the Bank file. See Chapter 6: Working with Banks (WBNK). Alphanumeric, 3 positions; required. |
Division |
The division to use for A/P postings. The system uses this division and its associated entity when recreating the general ledger postings for accounts payable purchases and disbursements; however, if there was a Division specified for the warehouse when you received the purchase order related to the A/P activity, the system uses this division instead. See the description of the Division field under Creating and Maintaining Warehouses (WWHS) for more information. Division codes are defined in and validated against the Division file. See Chapter 3: Working with Divisions (WDIV). Alphanumeric, 2 positions; required. |
Submit to batch |
This field controls whether you submit a batch job or run the reset interactively. Valid values are: Y (default) = Submit a batch job N = Run the reset interactively. You will need to wait at the screen until the reset is complete. Alphanumeric, 1 position; required. |
In general, the system clears the general ledger records for the specified period and rebuilds the records from the transaction records.
Update |
Source of Information |
Clears the General Ledger Interface file and General Ledger Detail file for the specified date range |
N/A |
Resets sales transactions |
Invoice Ship To file Invoice Header file Invoice Detail file Order Header file Invoice Detail Charge file Order Additional Charge file |
Resets Delivery Confirmation |
Order Line History file (records for Activity V (Delivered)) |
Tax rates |
Effective dates for the SCF or postal code |
Order transaction amounts |
Invoice Payment Method file |
Credit card deposits |
Invoice Payment Method file (total of freight, additional freight, tax, handling, and merchandise, based on the division associated with the source code on the order header) For G/L account numbers: Bank file (debit transactions) or Pay Type file (credit transactions) |
A/P payments |
For transaction amount: A/P Invoice Detail History (calculated by multiplying the cost * units) For G/L account number: A/P Invoice Header Division and entity: entry at the Reset General Ledger Interface prompt screen (only if the division was originally supplied at a prompt screen, as in A/P entry or A/P check generation) |
Void transactions for A/P checks |
A/P Check file G/L account number: A/P Invoice Header file |
A/R transactions |
A/R Header and Detail files |
G/L adjustments |
G/L Adjustments file |
Changes to G/L account numbers |
New number from appropriate file. The exception is inventory transactions, which use the G/L number that is stored in the Item Transaction History file |
General Ledger Control Report | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 44: Display General Ledger Exceptions (DGLE) |
AP_APPD CWDirect 18.0 August 2015 OTN