E1 812aga-B 0406
E1 812aga-B 0406
E1 812aga-B 0406
12 Implementation Guide
April 2006
JD Edwards EnterpriseOne General Accounting 8.12 Implementation Guide SKU E1_812AGA-B_0406 Copyright 2006, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer SoftwareRestricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensees responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Open Source Disclosure Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracles PeopleSoft products and the following disclaimers are provided. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Contents
General Preface About This Documentation Preface .............................................................. . . . .xxxiii JD Edwards EnterpriseOne Application Prerequisites..................................................... . . . . .xxxiii Application Fundamentals..................................................................................... . . . . .xxxiii Documentation Updates and Printed Documentation..................................................... . . . . .xxxiv Obtaining Documentation Updates........................................................................ . . . .xxxiv Ordering Printed Documentation......................................................................... . . . . .xxxiv Additional Resources.......................................................................................... ......xxxv Typographical Conventions and Visual Cues............................................................... . . . . .xxxvi Typographical Conventions............................................................................... . . . . .xxxvi Visual Cues.................................................................................................. . . . .xxxvii Country, Region, and Industry Identifiers................................................................ . . . .xxxvii Currency Codes.............................................................................................. . . .xxxviii Comments and Suggestions.................................................................................. . . . .xxxviii Common Fields Used in Implementation Guides.......................................................... . . . .xxxviii
Preface JD Edwards EnterpriseOne General Accounting Preface................................... . . . . . . . .xli JD Edwards EnterpriseOne Products........................................................................ .........xli JD Edwards EnterpriseOne Application Fundamentals................................................... .........xli Common Fields Used in This Implementation Guide...................................................... .........xli Chapter 1 Getting Started with JD Edwards EnterpriseOne General Accounting................... ..........1 JD Edwards EnterpriseOne General Accounting Overview............................................... ..........1 JD Edwards EnterpriseOne General Accounting Business Processes. .. ... .. .. ... .. .. ... .. .. ... .. .. .. ..........1 JD Edwards EnterpriseOne General Accounting Integrations............................................ ..........2 JD Edwards EnterpriseOne General Accounting Implementation....................................... ..........4 Global Implementation Steps.......................................................................................5 JD Edwards EnterpriseOne General Accounting Implementation Steps......................................6
iii
Contents
Chapter 2 Understanding the General Accounting Features............................................. ..........9 General Accounting Features................................................................................. ..........9
Chapter 3 Setting Up the General Accounting System.................................................... . . . . . . . .13 Understanding General Accounting System Setup........................................................ . . . . . . . .13 Prerequisite..................................................................................................... . . . . . . . .14 Setting Up Constants for General Accounting.............................................................. . . . . . . . .14 Understanding General Accounting Constants.......................................................... . . . . . . .14 Prerequisite................................................................................................... . . . . . . .16 Forms Used to Set Up General Accounting Constants................................................. . . . . . . .16 Setting Up General Accounting Constants............................................................... . . . . . . .16 Setting Up User-Defined Codes for General Accounting.................................................. . . . . . . . .18 Setting Up Ledger Types for General Accounting.......................................................... . . . . . . . .20 Setting Up Ledger Type Rules for General Accounting................................................... . . . . . . . .21 Understanding Ledger Type Rules.. ...................................................................... . . . . . . .21 Forms Used to Set Up Ledger Type Rules............................................................... . . . . . . .21 Setting Up a Ledger Type Rule............................................................................ . . . . . . .21 Setting Up AAIs for General Accounting.................................................................... . . . . . . . .24 Understanding General Purpose Accounts.............................................................. . . . . . . .24 Understanding Retained Earnings Accounts............................................................. . . . . . . .26 Understanding Financial Statement Totals............................................................... . . . . . . .27 Understanding Speed Codes.............................................................................. . . . . . . .29 Understanding Account Summarization. ................................................................. . . . . . . .29 Understanding Reconcilable Ranges..................................................................... . . . . . . .29 Understanding Prior Year Account Purges............................................................... . . . . . . .30 Setting Up Business Unit Supplemental Data.............................................................. . . . . . . . .30 Prerequisite................................................................................................... . . . . . . .30 Setting Up Vertex Sales Tax.................................................................................. . . . . . . . .31
Chapter 4 Setting Up Account Reconciliation............................................................... . . . . . . . .33 Understanding Account Reconciliation...................................................................... . . . . . . . .33 Setting Up AAIs for Account Reconciliation................................................................. . . . . . . . .33 Setting Up Reconciliation Codes............................................................................. . . . . . . . .34
iv
Contents
Chapter 5 Setting Up Automatic Bank Statement Processing........................................... . . . . . . . .35 Setting Integration Options for Automatic Bank Statement Processing................................. . . . . . . . .35 Understanding Bank Statement Integration Options.................................................... . . . . . . .35 Setting Integration Options for Conversion Flows....................................................... . . . . . . .35 Setting an Integration Option for the Date Pattern...................................................... . . . . . . .36 Setting Up UDCs for Automatic Bank Statement Processing............................................ . . . . . . . .36 Understanding UDC Setup for Automatic Bank Statement Processing.............................. . . . . . . .36 Setting Up UDCs for Automatic Bank Statements...................................................... . . . . . . .37 Setting Up Cross References................................................................................. . . . . . . . .41 Understanding Cross References......................................................................... . . . . . . .42 Forms Used to Set Up Cross References................................................................ . . . . . . .42 Setting Up Cross References for a Bank Account...................................................... . . . . . . .42 Setting Up a Cross Reference for a Transaction Type................................................. . . . . . . .43 Setting Up Automatic Bank Account Reconciliation....................................................... . . . . . . . .45 Understanding Automatic Bank Account Reconciliation................................................ . . . . . . .45 Forms Used to Set Up Automatic Bank Account Reconciliation. ..... .... ..... .... .... ..... .... ..... . . . . . . . .46 Setting Up Automatic Reconciliation Rules.............................................................. . . . . . . .46 Assigning Automatic Reconciliation Rules to Groups................................................... . . . . . . .49 Assigning Groups to Automatic Bank Statement Accounts............................................ . . . . . . .50
Chapter 6 Setting Up Budget Forecasting and Planning.................................................. . . . . . . . .53 Understanding Budget Forecasting and Planning Setup.................................................. . . . . . . . .53 Setting Up Growth Patterns................................................................................... . . . . . . . .53 Understanding Growth Patterns........................................................................... . . . . . . .53 Forms Used to Set Up Growth Patterns.................................................................. . . . . . . .54 Setting Up a Growth Pattern............................................................................... . . . . . . .54 Assigning a Growth Pattern to Business Units.......................................................... . . . . . . .55
Chapter 7 Setting Up Cash Forecasting....................................................................... . . . . . . . .57 Understanding Cash Forecasting Setup.................................................................... . . . . . . . .57 Understanding Cash Type Codes............................................................................ . . . . . . . .57 Setting Up Cash Type Rules.................................................................................. . . . . . . . .58 Understanding Cash Type Rules.......................................................................... . . . . . . .58 Forms Used to Set Up Cash Type Forecasting.......................................................... . . . . . . .59 Setting Up Cash Type Rules for Accounts Receivable and Accounts Payable. . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Contents
Setting Up Cash Type Rules for General Ledger........................................................ . . . . . . .62 Defining a Cash Forecast Report Structure................................................................. . . . . . . . .63 Understanding Cash Forecast Report Structures....................................................... . . . . . . .63 Prerequisites................................................................................................. . . . . . . .64 Forms Used to Define Cash Forecast Reports.......................................................... . . . . . . .64 Setting Processing Options for the Cash Forecast Report Structures Setup Program (P09523). . . . . . . . .64 Defining a Cash Forecast Report Structure.............................................................. . . . . . . .65
Chapter 8 Setting Up Statements of Cash Flow............................................................. . . . . . . . .69 Understanding Cash Management........................................................................... . . . . . . . .69 Understanding Cash Flow Statements...................................................................... . . . . . . . .69 Setting Up Cash Flow Activity Codes........................................................................ . . . . . . . .70 Setting Up Normal Balance Codes........................................................................... . . . . . . . .71 Setting Up Cash Flow Rules.................................................................................. . . . . . . . .71 Understanding Cash Flow Rules.......................................................................... . . . . . . .71 Forms Used to Set Up Cash Flow Rules................................................................. . . . . . . .72 Setting Up Cash Flow Rules............................................................................... . . . . . . .72
Chapter 9 Setting Up Cash Basis Accounting............................................................... . . . . . . . .75 Understanding Cash Basis Accounting Setup.............................................................. . . . . . . . .75 Setting Up Cash Basis Document Types.................................................................... . . . . . . . .75 Forms Used to Set Up Cash Basis Document Types................................................... . . . . . . .76 Setting Up Document Types for Cash Basis Entries.................................................... . . . . . . .76 Setting Up Document Types to Exclude for Cash Basis Entries..... ..... .... ..... ..... .... ..... .... . . . . . . . .76 Assigning Cash Basis Document Types to the AA Ledger............................................. . . . . . . .77 Setting Up AAIs for Cash Basis Accounting................................................................ . . . . . . . .77 Setting Up AAIs for Unapplied Receipts.................................................................. . . . . . . .77 Setting Up AAIs for Balancing Accounts.................................................................. . . . . . . .78
Chapter 10 Setting Up 52 Period Accounting................................................................. . . . . . . . .79 Setting Up 52 Period Fiscal Date Patterns.................................................................. . . . . . . . .79 Understanding 52 Period Fiscal Date Patterns.......................................................... . . . . . . .79 Forms Used to Set Up 52 Period Fiscal Date Patterns................................................. . . . . . . .80 Defining 52 Period Fiscal Date Patterns.................................................................. . . . . . . .80
vi
Contents
Setting Up 52 Period Reporting Dates....................................................................... . . . . . . . .80 Understanding 52 Period Reporting Dates............................................................... . . . . . . .80 Forms Used to Set Up 52 Period Reporting Dates...................................................... . . . . . . .80 Assigning 52 Period Reporting Dates to a Company................................................... . . . . . . .81 Changing to 52 Period Accounting........................................................................... . . . . . . . .81 Understanding the Repost for 52 Period Program (R0902B).. ........................................ . . . . . . .81 Prerequisite................................................................................................... . . . . . . .81 Running the Repost for 52 Period Program.............................................................. . . . . . . .82 Setting Data Selection for the Repost for 52 Period Program......................................... . . . . . . .82
Chapter 11 Processing Journal Entries......................................................................... . . . . . . . .83 Understanding the Journal Entry Process................................................................... . . . . . . . .83 Understanding Other Methods of Entering Journal Entries............................................... . . . . . . . .84 Working with Journal Entries.................................................................................. . . . . . . . .85 Understanding the Journal Entry Program.... ........................................................... . . . . . . .85 Understanding Types of Journal Entries.................................................................. . . . . . . .85 Understanding Journal Entry Features................................................................... . . . . . . .86 Understanding Temporary Invalid Account Numbers................................................... . . . . . . .87 Forms Used to Work with Journal Entries................................................................ . . . . . . .88 Setting Processing Options for Journal Entry (P0911).................................................. . . . . . . .88 Setting Processing Options for Journal Entry Master Business Function (P0900049). . . . . .. . . . . . . . . . . . . .89 Entering Basic Journal Entries............................................................................. . . . . . . .90 Adding an Attachment to a Journal Entry................................................................ . . . . . . .91 Entering a Journal Entry with an Invalid Account Number............................................ . . . . . . . .92 Entering a Percent Journal Entry.......................................................................... . . . . . . .92 Revising an Unposted Journal Entry...................................................................... . . . . . . .93 Copying a Journal Entry.................................................................................... . . . . . . .94 Deleting an Unposted Journal Entry...................................................................... . . . . . . .94 Working with Reversing Journal Entries..................................................................... . . . . . . . .94 Entering a Reversing Entry................................................................................. . . . . . . .95 Reviewing a Reversing Journal Entry..................................................................... . . . . . . .95 Changing a Posted Journal Entry to a Reversing Entry................................................ . . . . . . .95 Working with Model Journal Entries.......................................................................... . . . . . . . .95 Understanding Model Journal Entries..................................................................... . . . . . . .96 Creating a Model Journal Entry............................................................................ . . . . . . .96 Creating a Model Journal Entry from an Existing Journal Entry....................................... . . . . . . .97 Entering a Journal Entry Based on a Model by Copying the Model. .. .. . .. .. .. .. . .. .. .. .. . .. .. .. . .. . . . . . . . .97 Entering a Journal Entry Based on a Model by Selecting the Model. ..... ..... ..... ...... ..... ..... . . . . . . . .97
vii
Contents
Reviewing Journal Entries..................................................................................... . . . . . . . .98 Forms Used to Review Journal Entries................................................................... . . . . . . .98 Setting Processing Options for General Journal Review (P0011)..................................... . . . . . . .98 Reviewing a Journal Entry.................................................................................. . . . . . . .98 Posting Journal Entries........................................................................................ . . . . . . . .99 Understanding the General Ledger Post Process....................................................... . . . . . . .99 Setting Processing Options for General Ledger Post (R09801).............................................100 Posting Journal Entries...........................................................................................103 Revising and Voiding Posted Journal Entries............................................................... .......103 Understanding Revisions to Posted Journal Entries. .........................................................104 Understanding the Void of a Posted Reversing Journal Entry...............................................104 Forms Used to Revise and Void Posted Journal Entries.....................................................105 Revising a Posted Journal Entry.................................................................................105 Voiding a Posted Journal Entry..................................................................................105 Voiding a Posted Reversing Journal Entry.....................................................................105
Chapter 12 Processing Batch Journal Entries................................................................ .......107 Understanding Journal Entry Batch Processing............................................................ .......107 Uploading Batch Journal Entry............................................................................... .......108 Understanding the Journal Entry Batch Upload Process.....................................................108 Running the Journal Entries Batch Processor. ................................................................109 Setting Processing Options for Journal Entries Batch Processor (R09110Z)..............................109 Working with Batch Journal Entries.......................................................................... .......110 Understanding the Journal Entry Revisions Program.........................................................110 Forms Used to Work with Batch Journal Entries........................................................ . . . . . .111 Setting Processing Options for Journal Entry Revisions (P0911Z1)................................. . . . . . . .111 Posting Processed Batch Journal Entries................................................................... .......112 Purging Processed Batch Journal Entries................................................................... .......112
Chapter 13 Processing Store-and-Forward Journal Entries............................................... .......113 Understanding Store-and-Forward Processing............................................................. .......113 Downloading Master Tables for Store-and-Forward Processing......................................... .......113 Understanding the Download of Master Tables for Processing. .... .... .... ... .... .... ... .... .... ..........113 Prerequisites.......................................................................................................114 Downloading Store-and-Forward Master Tables..............................................................114 Creating Journal Entries for Store-and-Forward Processing............................................. .......115
viii
Contents
Understanding Journal Entry Creation..........................................................................115 Forms Used to Create Store-and-Forward Journal Entries..................................................115 Adding Store-and-Forward Journal Entries....................................................................116 Uploading Store-and-Forward Journal Entries............................................................. .......116 Understanding the Store-and-Forward Upload Process......................................................116 Uploading Store-and-Forward Journal Entries to the Server................................................116 Processing Store-and-Forward Journal Entries............................................................ .......116 Understanding the Store-and-Forward Processor.............................................................116 Running the Store & Forward JE Batch Processor...........................................................117 Setting Processing Options for the Store & Forward JE Batch Processor (R09110ZS)..................117 Updating Transaction Control Records. ..................................................................... .......118 Understanding the Update Transaction Control Record Program...........................................118 Updating Control Records........................................................................................118 Purging Store-and-Forward Journal Entries................................................................ .......118 Purging Processed Store-and-Forward Journal Entries......................................................118
Chapter 14 Processing Allocations.............................................................................. .......119 Understanding Allocations.................................................................................... .......119 Understanding the Process for Creating Allocations...................................................... .......120 Understanding Multitiered Allocations... .................................................................... .......121 Common Elements Used in This Chapter................................................................... .......121 Processing Recurring Journal Entries....................................................................... .......123 Understanding Recurring Journal Entries......................................................................123 Understanding the Recurring JE Compute & Print Program.................................................123 Prerequisite.........................................................................................................124 Forms Used to Process Recurring Journal Entries...........................................................124 Creating Recurring Journal Entries..............................................................................124 Running the Recurring JE Compute & Print Program........................................................126 Setting Data Selection for Recurring JE Compute & Print...................................................126 Setting Processing Options for Recurring JE Compute & Print (R09302). . . . . . . . . . .. . . . . . . .. . . . . . ........126 Processing Indexed Allocations.............................................................................. .......127 Understanding Indexed Allocations.............................................................................127 Understanding the Indexed Computations Compute & Print Program.. ... .. ... .. ... ... .. ... .. ... .........128 Prerequisites.......................................................................................................129 Forms Used to Create Indexed Allocations....................................................................129 Creating Indexed Allocations.....................................................................................129 Running the Indexed Computations Compute & Print Program.. ...........................................132 Setting Data Selection and Sequence for Indexed Computations Compute & Print......................132
ix
Contents
Setting Processing Options for Indexed Computations Compute & Print (R093021). . . . . . . . . . . . . .......132 Processing Variable Numerator Allocations................................................................. .......133 Understanding Variable Numerator Allocations................................................................133 Understanding Variable Numerator Allocation Calculations. .............. .............. ....................135 Prerequisite.........................................................................................................135 Forms Used to Process Variable Numerator Allocations.....................................................135 Creating Variable Numerator Allocations.......................................................................135 Running the Variable Numerator Compute & Print Program.................................................137 Setting Data Selection for Variable Numerator Compute & Print............................................137 Setting Processing Options for Variable Numerator Compute & Print (R093022). . . . . . . . . . . . . . . . ........137
Chapter 15 Reconciling Bank Account Transactions........................................................ .......139 Understanding Bank Account Reconciliation............................................................... .......139 Reconciling Voided Payments and Receipts................................................................ .......139 Understanding the Auto Reconciliation Void Programs......................................................139 Reconciling Voided Payments...................................................................................140 Reconciling Voided Receipts.....................................................................................140 Refreshing Account Reconciliation Information............................................................ .......140 Understanding the Refresh Reconciliation File Program.....................................................140 Prerequisite.........................................................................................................141 Running the Refresh Reconciliation File Program............................................................141 Setting Data Selection for Refresh Reconciliation File.......................................................141 Setting Processing Options for Refresh Reconciliation File (R09130). . . .. . .. . . .. . . .. . . .. . . .. . . .. . ........141 Reconciling Bank Account Transactions Manually......................................................... .......142 Understanding Manual Bank Account Reconciliation.........................................................142 Understanding the Reconciliation Report......................................................................142 Forms Used to Reconcile Bank Account Transactions Manually.. ... ... ... ... ... .. ... ... ... ... ... .........143 Setting Processing Options for Manual Reconciliation (P09131)...... ...... ...... ...... ...... .............143 Reconciling Bank Account Transactions Manually............................................................143 Changing a Reconciled Transaction to Unreconciled...................................................... .......145
Chapter 16 Reconciling Debit and Credit Amounts.......................................................... .......147 Understanding the Debit and Credit Reconciliation Process............................................. .......147 Prerequisites.................................................................................................... .......147 Reconciling Debit and Credit Transactions................................................................. .......147 Forms Used to Reconcile Debit and Credit Transactions....................................................148
Contents
Setting Processing Options for Manual Reconciliation (P09131)..... ...... ...... ...... ...... ..............148 Reconciling Debit and Credit Transactions Manually.. .......................................................149
Chapter 17 Reconciling Bank Tapes............................................................................. .......151 Understanding the Bank Tape Reconciliation Process.................................................... .......151 Reformatting the Bank Tape.................................................................................. .......152 Understanding the Program Used to Reformat Bank Tapes..... ............................................153 Running the Custom Reformat UBE Program.................................................................153 Setting Processing Options for Custom Reformat UBE (R09501)..........................................153 Refreshing Account Reconciliation Information............................................................ .......154 Matching the Bank Tape to the Reconciliation Workfile................................................... .......154 Understanding the Program Used to Reconcile Transactions...............................................154 Running the Match Tape File To Recon File Program........................................................154 Setting Processing Options for Match Tape File To Recon File (R09510).. .. .. .. .. .. .. .. .. .. .. .. .........154 Verifying the Bank Tape Reconciliation...................................................................... .......155
Chapter 18 Processing Bank Statements Manually.......................................................... .......157 Understanding Manual Bank Statement Processing...................................................... .......157 Common Elements Used in This Chapter......................................................................157 Understanding Transaction Codes........................................................................... .......158 Understanding Transit Accounts............................................................................. .......159 Entering Bank Statement Transactions...................................................................... .......160 Understanding Bank Statement Transactions.................................................................160 Forms Used to Enter Bank Statement Transactions..........................................................161 Setting Processing Options for Bank Statement Entry (P09160). ... .. .. ... .. .. ... .. .. ... .. .. ... .. .........161 Entering Bank Statement Transactions.........................................................................165 Refreshing Account Reconciliation Information............................................................ .......166 Understanding the Refresh Reconciliation File Program.....................................................167 Prerequisite.........................................................................................................167 Running the Refresh Reconciliation File Program. ...........................................................167 Setting Data Selection for Refresh Reconciliation File.......................................................167 Setting Processing Options for Refresh Reconciliation File (R09130). . . .. . . .. . . .. . . .. . . .. . .. . . .. . ........167 Running the Bank Journal Statement Process Program.................................................. .......168 Understanding the Bank Journal Statement Process Program..............................................168 Prerequisite.........................................................................................................169 Running the Bank Journal Statement Process Program.....................................................169
xi
Contents
Setting Data Sequence for Bank Journal Statement Process...............................................169 Setting Processing Options for Bank Journal Statement Process (R09170).. . .. . . .. . .. . .. . .. . .. . ........170 Reviewing the Bank Statement Processing Reports..........................................................172 Processing Batch Cash Receipt Transactions.................................................................172
Chapter 19 Processing PeopleSoft Enterprise Bank Statements in JD Edwards EnterpriseOne General Accounting.................................................................................. .......175
Understanding the PeopleSoft Enterprise Treasury and JD Edwards EnterpriseOne General Accounting Integration......................................................................................... .......175 Processing PeopleSoft Enterprise Bank Statements...................................................... .......176 Processing PeopleSoft Enterprise Accounting Transactions............................................. .......176 Converting Accounting Transactions to the F0911Z1 Table.......................................... .......176 Transferring Accounting Transactions to the F0911 Table...................................................177 Posting Accounting Transactions to the F0902 Table.........................................................177
Chapter 20 Processing Bank Statements Automatically................................................... .......179 Understanding the Automatic Bank Statement Process.................................................. .......179 Running the Conversion Flows for Automatic Bank Statement Processing. .......... ......... ........ .......181 Understanding the Conversion Flows for Bank Statements.................................................181 Prerequisites.......................................................................................................181 Running a Bank Statement Conversion Flow..................................................................181 Revising Data in the Staging Tables......................................................................... .......182 Understanding Data Revisions to the Staging Tables........................................................182 Forms Used to Revise Data in Staging Tables................................................................183 Setting Processing Options for Revise Electronic Bank Statement Staging (P09610). . . . .. . . . . . ........183 Revising Staging Data............................................................................................183 Loading Data into the Bank Statement Tables.............................................................. .......185 Understanding the Load Bank Statement Program.... .......................................................185 Running the Load Bank Statement Program...................................................................186 Setting Processing Options for Load Bank Statement (R09612)............................................186 Revising Data in the Bank Statement Tables............................................................... .......186 Understanding Data Revisions to the Bank Statement Tables...... ................. .......................186 Forms Used to Revise Data in the Bank Statement Tables..................................................187 Setting Processing Options for Revise Automatic Bank Statement (P09616). ............................187 Revising Bank Statement Data..................................................................................188 Revising Transactions without a Customer Number..........................................................189
xii
Contents
Processing Automatic Bank Statements.................................................................... .......190 Understanding the Automatic Bank Statement Program........... ..........................................190 Understanding Automatic Bank Statement Reports and Messages........................................192 Running the Process Automatic Bank Statements Program.................................................192 Setting Processing Options for Process Automatic Bank Statements (R09616)..........................193 Reconciling Unreconciled Bank Statement Transactions................................................. .......193 Understanding the Manual Bank Statement Reconciliation Program.......................................194 Form Used to Manually Reconcile Bank Statement Transactions....................... ...................195 Setting Processing Options for Manual Bank Statement Reconciliation (P09631). . . . . . . . . . . . . . . ........195 Reconciling Unreconciled Bank Transactions.................................................................195 Purging Bank Statement Tables.............................................................................. .......199 Understanding the Bank Statement Purge Programs........................................................199 Purging Staging Tables...........................................................................................199 Setting Processing Options for Purge Staging Tables (R09610)............................................199 Purging Automatic Bank Statement Tables Program.........................................................200 Setting Processing Options for Purge Automatic Bank Statement Tables (R09615). . . . . . . . . . . . . ........200
Chapter 21 Creating Budgets..................................................................................... .......201 Understanding Budgets........................................................................................ .......201 Understanding Budget Patterns.............................................................................. .......202 Creating Budget Pattern Codes.............................................................................. .......204 Forms Used to Create Budget Pattern Codes.................................................................204 Creating a Budget Pattern Code.................................................................................204 Changing Budget Pattern Codes for a Group of Accounts................................................ .......205 Understanding Budget Pattern Code Changes................................................................205 Form Used to Change Budget Pattern Codes for a Group of Accounts....................................205 Changing a Budget Pattern Code for a Group of Accounts... ...............................................205 Entering Annual Budgets...................................................................................... .......207 Understanding Annual Budgets..................................................................................207 Understanding Budget Cycles......... ..........................................................................207 Prerequisite.........................................................................................................208 Forms Used to Enter Annual Budget Amounts................................................................209
Setting Processing Options for Requested by Business Unit (P14102) and Requested by Account (P14103).................................................................................................209 Entering Annual Budget Amounts by Business Unit..........................................................210 Entering Annual Budget Amounts by Account.................................................................212 Spreading Annual Budget Amounts to Periods............................................................. .......212 Understanding the Methods for Annual Budget Spreads.....................................................213 Understanding How the System Spreads Annual Budget Amounts........................................213
xiii
Contents
Spreading Annual Budget Amounts to Periods During Budget Entry.......................................214 Running the Spread Annual to Periods Program..............................................................215 Setting Processing Options for Spread Annual to Periods (R14801)... ....................................215 Generating Budget Worksheets.............................................................................. .......215 Understanding Budget Worksheets.. ...........................................................................215 Running the Budget Worksheet.................................................................................216 Setting Data Selection and Sequence for Budget Worksheet...............................................216 Setting Processing Options for Budget Worksheet (R14113)................................................217 Reviewing Budget Comparisons Online..................................................................... .......218 Understanding the Online Budget Comparison Program.....................................................218 Form Used to Review Budget Comparisons Online..........................................................219 Setting Processing Options for Online Budget Comparison (P09210A)....................................219 Reviewing Budget Comparisons Online........................................................................220 Managing Budget Overages.................................................................................. .......221 Understanding the Management of Budget Overages........................................................221 Understanding the Budget Checking Calculation.............................................................222 Running the G/L Budget Checking Report... ..................................................................223 Setting Processing Options for G/L Budget Checking Report (R14115).. .. ... ... .. ... ... .. ... ... .........223 Entering Detailed Budget Amounts.......................................................................... .......224 Understanding the Detailed Budget by Account Program....................................................224 Forms Used to Enter Detailed Budget Amounts...............................................................224 Entering Detailed Budget Amounts by Account...............................................................224 Entering Journalized Budgets................................................................................. .......225 Understanding Journalized Budgets............................................................................225 Prerequisites.......................................................................................................226 Forms Used to Enter Journalized Budgets.....................................................................226 Entering Budget Journal Entries.................................................................................226
Chapter 22 Uploading Budget Data.............................................................................. .......227 Understanding the Budget Upload Process................................................................. .......227 Importing Budget Data from Spreadsheets................................................................. .......227 Understanding the Import Budget Process for Spreadsheets...............................................228 Forms Used to Import Budget Data From a Spreadsheet....................................................228 Setting Processing Options for Upload/Conversion Revisions (P0902Z1).................................228 Importing Budget Data From a Spreadsheet...................................................................229 Importing Budget Data from Text Files...................................................................... .......230 Understanding the Budget Import Process for Text Files.....................................................230 Prerequisites.......................................................................................................230
xiv
Contents
Copying Budget Data into the F0902Z2 Text File.............................................................230 Running the Budget Import Field Mapping Program..........................................................231 Setting Processing Options for Budget Import Field Mapping (R14110M).................................232 Revising Imported Budget Data.. ............................................................................ .......232 Understanding Revisions to Imported Budget Data...........................................................232 Form Used to Revise Imported Budget Data..................................................................233 Revising Imported Budget Data.................................................................................233 Uploading Budget Data to the F0902 Table................................................................. .......233 Understanding the Upload/Conversion Program. .............................................................234 Running the Upload/Conversion Program......................................................................234 Setting Processing Options for Upload/Conversion (R14110).. .............................................235 Purging Processed Records in the F0902Z1 Table.. ...................................................... .......237 Understanding the Processed Upload Purge Program. ......................................................237 Running the Processed Upload Purge Program..............................................................237
Chapter 23 Forecasting and Planning Budgets............................................................... .......239 Understanding Budget Forecasting and Planning......................................................... .......239 Defining Accounts and Retrieving Basis Amounts......................................................... .......240 Understanding Account Definition and Basis Amounts... ....................................................240 Forms Used to Manually Define Accounts and Retrieve Basis Amounts. .. . .. .. .. . .. .. .. . .. .. .. . .........241 Defining Accounts and Retrieving Basis Amounts Manually.................................................241 Generating Accounts and Basis Amounts Automatically.....................................................243 Setting Processing Options for Generate Forecast Basis (R1403)...... ......................... ..........243 Revising Accounts and Basis Amounts...................................................................... .......243 Understanding Account and Basis Amount Revisions........................................................243 Forms Used to Revise Accounts and Basis Amounts........................................................244 Revising Accounts and Basis Amounts.........................................................................244 Generating Budget Forecast Amounts...................................................................... .......245 Understanding Budget Forecast Amount Generation.........................................................245 Prerequisite.........................................................................................................246 Running the Generate Forecast Results Program............................................................246 Setting Data Selection for Generate Forecast Basis..........................................................246 Setting Processing Options for Generate Forecast Results (R1404).......................................246 Revising Budget Forecast Amounts......................................................................... .......247 Understanding Budget Forecast Amount Revisions..........................................................247 Forms Used to Revise Budget Forecast Amounts............................................................248 Revising Budget Forecast Amounts.............................................................................248 Updating Budget Forecast Records.......................................................................... .......249
xv
Contents
Understanding the Budget Forecast Update Program........................................................249 Prerequisite.........................................................................................................250 Running the Apply Forecast to Budget Program..............................................................250 Setting Data Selection for Apply Forecast to Budget.........................................................250 Setting Processing Options for Apply Forecast to Budget (R1407)... ......................................250 Purging Budget Forecast Records........................................................................... .......250 Understanding the Budget Forecast Purge Programs........................................................250 Running the Purge Forecast Basis and Purge Forecast Results Programs...............................251 Setting Data Selection for Purge Forecast Basis and Purge Forecast Results. . . . . . . . . . . . . . . . . . . ........251
Chapter 24 Processing Cash Forecast Data................................................................... .......253 Refreshing Cash Forecast Data.............................................................................. .......253 Understanding the Refresh Cash Forecast Data Program...................................................253 Refreshing Cash Forecast Data.................................................................................255 Setting Processing Options for Refresh Cash Forecast Data (R00522). .. .. . .. . .. .. . .. . .. .. . .. . .. ........255 Analyzing Cash Forecast Information........................................................................ .......256 Understanding Cash Forecast Information.....................................................................256 Understanding Bank Account Opening Balances.............................................................257 Prerequisites.......................................................................................................257 Form Used to Analyze Cash Forecast Information............................................................257 Setting Processing Options for Cash Forecast Analysis (P09522).. ... ... ... ... ... ... ... ... ... ... .........257 Analyzing Cash Forecast Information...........................................................................258 Purging Forecast Data......................................................................................... .......259 Understanding the Cash Forecast Purge.......................................................................259 Purging Cash Forecast Data.....................................................................................260 Setting Processing Options for Purge Cash Forecast Data (R09522B)....................................260
Chapter 25 Creating Cash Basis Entries....................................................................... .......261 Understanding Cash Basis Accounting...................................................................... .......261 Understanding Accrual Entries............................................................................... .......261 Understanding Cash Basis Entries........................................................................... .......262 Running the Cash Basis Program from the Menu.......................................................... .......266 Understanding When to Run the Cash Basis Program from the Menu.....................................266 Understanding Multithreaded Job Queues.....................................................................266 Running the Create Cash Basis Entries Program from the Menu...........................................266 Setting Processing Options for the Create Cash Basis Entries Program (R11C850). . . . . . . . . . . . . .......266
xvi
Contents
Running the Cash Basis Program from the Post........................................................... .......267 Understanding When to Run the Cash Basis Program from the Post......................................267 Running the Cash Basis Entries Program from the General Ledger Post Program (R09801). . . .......267 Setting Processing Options for General Ledger Post (R09801).............................................268 Reviewing Exception Reports................................................................................. .......268 Reviewing Cash Basis Entries................................................................................ .......269 Setting Data Selection for Unposted Cash Basis Report.....................................................269 Printing the Unposted Cash Basis Report......................................................................269 Posting Cash Basis Entries................................................................................... .......269
Chapter 26 Using 52 Period Accounting........................................................................ .......271 Posting 52 Period Accounting Entries.. ..................................................................... .......271 Understanding the 52 Period Accounting Post Program.....................................................271 Running the 52 Period Accounting Post Program.............................................................272 Setting the Processing Options for 52 Period Accounting Post (R098011)................................272 Closing a 52 Period Year...................................................................................... .......272 Understanding the Annual Close for 52 Period Program.....................................................272 Prerequisite.........................................................................................................272 Running the Annual Close for 52 Period Program............................................................273 Setting Data Selection for Annual Close for 52 Period (R09820B)... ... ... ... ... .... ... ... ... ... ..........273 Producing a 52 Period Income Statement.................................................................. .......273 Prerequisites.......................................................................................................273 Setting Data Selection and Sequence for 52 Period Income Statement...................................273 Setting Processing Options for 52 Period Income Statement (R10252).. .. . .. .. . .. .. . .. . .. .. . .. .. ........274 Generating the 52 Period Income Statement..................................................................274
Chapter 27 Understanding Account Consolidations........................................................ .......275 Account Consolidations........................................................................................ .......275 Online Consolidation Method....................................................................................275 High-Volume Consolidation Method.............................................................................276 Multisite Consolidation Method..................................................................................277
Chapter 28 Processing Online Consolidations............................................................... .......279 Understanding Organization Report Structures............................................................ .......279
xvii
Contents
Prerequisites.................................................................................................... .......280 Creating Hierarchical Organization Report Structures..................................................... .......280 Understanding How to Define and Build Organization Report Structures..................................280 Forms Used to Create Hierarchical Organization Report Structures.. .... ..... .... ..... .... .... ...........281 Defining Organization Report Structures.......................................................................281 Building Organization Report Structures.......................................................................281 Setting Processing Options for Business Unit Structure Build (R10450)...................................281 Adding Organization Report Structures Without Using Category Codes.. . .. . .. .. . .. . .. . .. .. . .. . .. .. . . .......282 Understanding Organization Report Structures Without Category Codes. ......... ........ ...............282 Forms Used to Add Organization Report Structures Without Category Codes. . . . . . . . . . . . . . . . . . . ........282 Adding an Organization Report Structure Without Using Category Codes.. .. ... .. .. ... .. .. ... .. .........282 Reviewing and Rearranging Organization Report Structures............................................ .......283 Understanding Organization Report Structure Revisions....................................................283 Form Used to Review and Rearrange Organization Report Structures....................................283 Reviewing and Rearranging Organization Report Structure Components.................................283 Creating Additional Business Units and Copying Report Structures. .... ... ... ... .... ... ... ... .... ... .. .......283 Forms Used to Create Additional Business Units and Copy Report Structures...........................284 Setting Processing Options for Organization Structure Inquiry/Revisions (P0050).......................284 Creating Additional Child Business Units.......................................................................284 Copying Organization Report Structures.......................................................................285 Creating Online Consolidations............................................................................... .......286 Understanding Online Consolidation Creation.................................................................286 Forms Used to Create Online Consolidations.................................................................288 Consolidating Business Units....................................................................................288 Reviewing Online Consolidations............................................................................ .......290 Forms Used to Review Online Consolidations.................................................................290 Setting Processing Options for Online Consolidations (P09218).. .. ... .. .. ... .. .. .. ... .. .. ... .. .. .........290 Reviewing Consolidated Financial Statements Online.......................................................292
Chapter 29 Processing High-Volume Consolidations....................................................... .......293 Understanding High-Volume Consolidation Processing................................................... .......293 Deleting Prior High-Volume Consolidations................................................................. .......293 Understanding the Delete Prior Consolidation Program......................................................294 Deleting Prior Consolidations....................................................................................294 Setting Processing Options for Delete Prior Consolidations (R10861).....................................294 Creating High-Volume Consolidations....................................................................... .......294 Understanding the Refresh Consolidation Program..........................................................295 Understanding the Structure of Fictitious Business Units....................................................295
xviii
Contents
Understanding Records Created by the Refresh Consolidation Program..................................295 Prerequisites.......................................................................................................296 Form Used to Review High-Volume Consolidations..........................................................296 Running the Refresh Consolidation Program.. ................................................................296 Setting Data Selection and Sequence for Refresh Consolidations... ... ... ... ... ... ... .... ... ... ..........296 Setting Processing Options for Refresh Consolidation (R10862)...........................................296 Reviewing High-Volume Consolidations..................................................................... .......297 Understanding High-Volume Consolidation Review..........................................................297 Setting Processing Options for Consolidation Review (P09210A)..........................................297 Reviewing High-Volume Consolidations........................................................................299
Chapter 30 Processing Multisite Consolidations............................................................. .......301 Understanding Source and Target Site Tasks.............................................................. .......301 Understanding Multiple Consolidation Tiers................................................................ .......302 Understanding Multisite Consolidation Structures and Tables...... ...... ....... ...... ...... ...... ...... .......302 Running Control File Reports................................................................................. .......303 Understanding Control File Reports.............................................................................303 Prerequisites.......................................................................................................303 Running the Create UDC Control File Report.................................................................304 Setting Processing Options for Create UDC Control File (R10005). .... ... .... ... .... ... .... ... ...........304 Running the Create Obj/Sub Control File Report..............................................................304 Setting Processing Options for Create Obj/Sub Control File (R10909). .. . .. . .. . .. . .. . . . . . .. . .. . .. ........304 Creating Organizational Structures.......................................................................... .......304 Understanding Organizational Structures......................................................................304 Forms Used to Create Organizational Structures.............................................................305 Defining Organizational Structures..............................................................................305 Creating Account Structures.................................................................................. .......305 Understanding Account Structure Components...............................................................305 Forms Used to Define an Account Structure...................................................................306 Defining an Account Structure...................................................................................306 Building Account Structures......................................................................................307 Setting Data Sequence for Account Structure Build..........................................................307 Setting Processing Options for Account Structure Build (R10430). ... ... ... ... ... ... ... ... ... ... ..........307 Revising and Printing Account Structures................................................................... .......308 Understanding Account Structure Revisions...................................................................308 Forms Used to Revise Account Structures.....................................................................309 Revising Account Structures.....................................................................................309 Printing the Account Structure Report..........................................................................309
xix
Contents
Setting Processing Options for Account Structure Report (R10445).... ..... .... ..... ..... ..... ...........310 Defining Multisite Consolidation Rules...................................................................... .......310 Understanding Components of Multisite Consolidation Rules... ............................................310 Understanding Consolidation Rules.............................................................................310 Understanding Elimination Rules................................................................................311 Forms Used to Define Consolidation and Elimination Rules.................................................311 Defining Consolidation Rules....................................................................................311 Defining Elimination Rules.......................................................................................313 Creating Consolidated Balances............................................................................. .......314 Understanding the Process Consolidations Program.........................................................314 Processing Consolidations.......................................................................................315 Setting Processing Options for Process Consolidations (R10550).. ... ... ... ... ... ... ... ... ... ... .........315 Running the Multisite Consolidations Reports.............................................................. .......317 Understanding Multisite Consolidation Integrity Reports.....................................................318 Understanding the BU/Accounts Monthly Comparison Report..............................................318 Running the Prior Period Balance Integrity Report............................................................319 Setting Processing Options for Prior Period Balance Integrity (R10700).. . . . . . . . . . . . .. . . . . . . . . . . . ........319 Running the UDC Value Control Exceptions Report..........................................................319 Setting Processing Options for UDC Value Control Exceptions (R107011)................................319 Running the Object/Subsidiary Value Control Exceptions Report...........................................320 Setting Processing Options for Object/Subsidiary Value Control Exceptions Report (R107021)........320 Running the BU/Accounts Monthly Comparison Report (R10701)..........................................320 Setting Data Selection and Sequence for BU/Accounts Monthly Comparison Report. . . . . . . . . . . . .......320 Setting Processing Options for BU/Accounts Monthly Comparison Report (R10701)....................320 Running the Consolidated Balance Sheet Report.............................................................320 Setting Processing Options for Consolidated Balance Sheet (R10150). . . . . . . . . . . . . . . . . . . . . . . . . . . ........321 Running the Consolidated Income Statement Report........................................................321 Setting Processing Options for Consolidated Income Statement (R10250). ... ... ... ... ... ... ... .........321 Reviewing Consolidation Statuses........................................................................... .......322 Understanding the Consolidation Console Program..........................................................322 Form Used to Review Consolidation Statuses.................................................................323 Reviewing Consolidation Statuses..............................................................................323 Sending Consolidated Balances by Batch to the Target Company...................................... .......324 Understanding the Process to Send Consolidated Balances to the Target Company....................324 Understanding the MSC Data Transmission Program........................................................324 Prerequisites.......................................................................................................325 Running the MSC Data Transmission Program...............................................................325 Setting Processing Options for MSC Data Transmission (R10610).. .. .. ... .. .. .. .. .. .. .. .. .. .. .. .........325 Sending Consolidated Balances Interactively to the Target Company.................................. .......327 Understanding the Process to Send Consolidated Balances to the Target Company....................327
xx
Contents
Understanding the Consolidation Console Program. .........................................................327 Form Used to Send Consolidated Balances Interactively to the Target Company........................327 Setting Processing Options for Consolidation Console (P10610)...........................................328 Sending Consolidated Balances Interactively to the Target Company.. .. ... .. ... ... .. ... .. ... ... .........328 Processing Consolidated Balances from Non-EnterpriseOne Source Sites............................ .......329 Understanding Inbound Multisite Consolidations..............................................................329 Understanding the Inbound Multisite Consolidations Process...............................................329 Processing Inbound Consolidations Data......................................................................330 Setting Processing Options for Process Inbound Consolidations Data (R1002Z1).......................330 Revising Inbound Consolidations............................................................................ .......330 Understanding Inbound Consolidations Revisions............................................................330 Forms Used to Revise Inbound Consolidations...............................................................331 Revising an Inbound Consolidation.............................................................................331 Purging Inbound Consolidations Data... .................................................................... .......331 Purging Inbound Consolidations.................................................................................331 Generating Multisite Batch Journal Entries................................................................. .......331 Understanding the Journalize Consolidation Balances Program............................................332 Prerequisites.......................................................................................................332 Generating Multisite Batch Journal Entries....................................................................333 Setting Data Selection for Journalize Consol. Balances.....................................................333 Setting Processing Options for Journalize Consol. Balances (R10480).. ... .. ... ... .. ... .. ... ... .........333 Processing and Purging Multisite Batch Journal Entries.................................................. .......334 Understanding Multisite Batch Journal Entry Processing and Purging.....................................334 Processing Batch Journal Entries...............................................................................335 Purging Processed Multisite Journal Entries...................................................................335
Chapter 31 Reviewing Balances and Transactions.......................................................... .......337 Understanding Online Inquiries............................................................................... .......337 Understanding Statutory Inquiries............................................................................ .......338 Understanding Trial Balance Inquiries....................................................................... .......338 Understanding Account Ledger and Balance Inquiries.................................................... .......339 Reviewing Trial Balances, Ledgers, and Subledgers...................................................... .......339 Understanding Trial Balance and Ledger Comparisons......................................................340 Forms Used to Review Balances, Ledgers, and Subledgers................................................340 Setting Processing Options for Trial Balance/Ledger Comparison (P09210A)............................340 Reviewing Trial Balances and Ledger Comparisons..........................................................341 Reviewing Trial Balance Subledger Information...............................................................343 Reviewing Trial Balances...................................................................................... .......343
xxi
Contents
Understanding Trial Balance Review...........................................................................343 Forms Used to Review Trial Balances..........................................................................344 Setting Processing Options for T/B by Object Account (P09214)...........................................344 Setting Processing Options for T/B by Company (P09216)..................................................345 Setting Processing Options for T/B by Subledger (P09215).................................................345 Reviewing Balances by Object Account........................................................................345 Reviewing Balances by Company...............................................................................346 Reviewing Balances by Subledger..............................................................................346 Reviewing Account Ledgers.................................................................................. .......347 Understanding Account Ledger Inquiry.........................................................................348 Understanding Account Ledger by Object Account.... .......................................................348 Understanding Account Ledger by Category Code...........................................................348 Forms Used to Review Account Ledgers.......................................................................349 Setting Processing Options for Account Ledger Inquiry (P09200)..........................................349 Setting Processing Options for Account Inquiry by Object Account (P09201). . . . . . . . . . . . . . . . . . . . ........351 Setting Processing Options for Account Inquiry by Category Code (P09202).............................351 Reviewing Account Ledger Transactions.......................................................................351 Reviewing Ledgers by Object Account.........................................................................352 Reviewing Ledgers by Category Code.........................................................................353 Reviewing Account Balances by Month.. ................................................................... .......353 Understanding Account Balances Review.....................................................................354 Forms Used to Review Account Balances.....................................................................354 Setting Processing Options for Account Balance by Month (P0902P1)....................................354 Reviewing Monthly Account Balances..........................................................................354 Reviewing Balances by Subledger..............................................................................355
xxii
Contents
Prerequisites.......................................................................................................362 Printing a Simple Balance Sheet................................................................................362 Setting Data Selection for Simple Balance Sheet.............................................................362 Setting Processing Options for Simple Balance Sheet (R10111B)..........................................362 Generating a Statement of Cash Flow....................................................................... .......363 Understanding the Statement of Cash Flow...................................................................363 Prerequisites.......................................................................................................366 Printing the Statement of Cash Flow............................................................................366 Setting Data Selection for Statement of Cash Flow Report..................................................366 Setting Processing Options for Statement of Cash Flow Report (R10521)................................366 Generate Consolidated Financial Reports.................................................................. .......367 Understanding Consolidated Financial Reports........... ....................................................367 Prerequisite.........................................................................................................367 Printing a Consolidated Income- 7 Column Statement.......................................................367 Setting Data Selection and Sequence for Consolidated Income-7 Column. . . . . . . . . . . . . . . . . . . . . . . ........368 Setting Processing Options for Consolidated Income-7 Column (R103121A). . . . . . . . . . . . . . . . . . . . ........368 Printing a Consolidated Balance Sheet.........................................................................368 Setting Data Selection and Sequence for Consolidated Balance Sheet... .... .... .... .... ..... ...........369 Setting Processing Options for Consolidated Balance Sheet (R10311A)..................................369 Generating Monthly Spreadsheets........................................................................... .......369 Understanding Monthly Spreadsheets..........................................................................369 Prerequisite.........................................................................................................370 Printing the Monthly Spreadsheet...............................................................................370 Setting Processing Options for Monthly Spreadsheet (R10412A)... ........... .......... .......... ........370 Generating Variance Analysis Reports...................................................................... .......371 Printing the Variance Analysis Report..........................................................................371 Setting Processing Options for Variance Analysis (R10212A)...............................................371 Printing the Variance Analysis w/5 Months Report............................................................371 Setting Processing Options for Variance Analysis w/5 Months (R10411A).... ... .... ... .... ... ...........372
Chapter 33 Verifying Data Integrity for General Accounting............................................... .......373 Understanding General Accounting Integrity Reports..................................................... .......373 Running the Transactions to Batch Headers Report....................................................... .......376 Understanding the Transactions To Batch Headers Report..................................................376 Printing the Transactions to Batch Headers Report...........................................................376 Setting Processing Options for Transactions to Batch Headers (R007021).... ..... ..... ..... ............376 Correcting Discrepancies on the Transactions To Batch Headers Report. ... ... ... .. ... ... ... .. ..........379 Running the Batch to Detail Report.. ........................................................................ .......379
xxiii
Contents
Understanding the Batch to Detail Report......................................................................379 Prerequisite.........................................................................................................380 Printing the Batch to Detail Report..............................................................................380 Setting Processing Options for Batch to Detail (R007031)...................................................380 Running the Unposted Batches Report...................................................................... .......382 Understanding the Unposted Batches Report.................................................................382 Prerequisite.........................................................................................................382 Printing the Unposted Batches Report..........................................................................382 Running the Batches Out of Balance Report............................................................... .......382 Understanding the Batches Out of Balance Report. ..........................................................382 Printing the Batches Out of Balance Report...................................................................383 Setting Data Selection for Batches Out of Balance...........................................................383 Setting Processing Options for Batches Out of Balance (R007032). .......................................383 Correcting Discrepancies on the Batches Out of Balance Report.. .. ... .. ... ... .. ... .. ... ... .. ... .........383 Running the Company by Batch Out of Balance Report.................................................. .......384 Understanding the Company by Batch Out of Balance Report..............................................384 Prerequisite.........................................................................................................384 Printing the Company by Batch Out of Balance Report......................................................385 Setting Processing Options for Company by Batch Out of Balance (R09706). .. . .. .. .. .. .. .. .. .. ........385 Correcting Discrepancies on the Company by Batch Out of Balance Report. . . . . . . . . . . . . . . . . . . . . ........385 Running the Companies in Balance Report................................................................. .......385 Understanding the Companies in Balance Report............................................................385 Printing the Companies in Balance Report.....................................................................386 Locating Out-of-Balance Companies...........................................................................386 Correcting Discrepancies on the Companies in Balance Report............................................387 Running the Intercompany Accounts in Balance Report.................................................. .......388 Understanding the Intercompany Accounts in Balance Report..............................................389 Printing the Intercompany Accounts in Balance Report......................................................389 Setting Processing Options for Intercompany Accounts in Balance (R097011)...........................389 Locating Out-of-Balance Intercompany Accounts.............................................................390 Correcting Discrepancies on the Intercompany Accounts in Balance Report.. . .. . .. .. . .. . .. .. . .. ........390 Running the Account Balance to Transactions Report.................................................... .......390 Understanding the Account Balance to Transactions Report................................................391 Printing the Account Balance to Transactions Report........................................................391 Setting Processing Options for Account Balance to Transactions (R09705). .. .. .. .. . .. .. .. .. .. .. ........391 Correcting Discrepancies on the Account Balance to Transactions Report. . . . . . . . . . . . . . . . . . . . . . . ........393 Running the Accounts without Business Units Report..................................................... .......394 Understanding the Accounts without Business Units Report................................................394 Printing the Accounts without Business Units Report.........................................................394 Setting Processing Options for Accounts w/o Business Units (R097041). . . . . . . . . . .. . . . . . . .. . . . . . ........394
xxiv
Contents
Running the Account Balance without Account Master Report..... ......... .......... ......... ......... .......395 Understanding the Account Balance without Account Master Report......................................395 Prerequisite.........................................................................................................395 Printing the Account Balance without Account Master Report.. ... ... ... ... ... ... ....... ... ... ... ..........395 Setting Processing Options for Account Balance without Account Master (R097031). . . . . . .. . . . ........395 Correcting Discrepancies on the Account Balance without Account Master Report.. ....................396 Running the Transactions without Account Master Report............................................... .......396 Understanding the Transactions without Account Master Report...........................................396 Prerequisite.........................................................................................................396 Printing the Transactions without Account Master Report................................... ................396 Setting Processing Options for Transactions w/o Acct Master (R097021).................................397 Correcting Discrepancies on the Transactions without Account Master Report...........................397
Chapter 34 Maintaining Batch Headers......................................................................... .......399 Understanding Batch Header Revisions..................................................................... .......399 Prerequisite..................................................................................................... .......400 Working with Batch Headers.................................................................................. .......400 Forms Used to Work with Batch Headers......................................................................401 Reviewing Batch Headers........................................................................................401 Adding and Revising Batch Headers............................................................................402 Revising Batches to Post Out of Balance......................................................................403
Chapter 35 Reposting the Account Ledger and Recalculating a Fiscal Year... ....................... .......405 Understanding the Repost Programs........................................................................ .......405 Prerequisites.................................................................................................... .......406 Reposting the Account Ledger............................................................................... .......406 Understanding When to Repost the Account Ledger.........................................................406 Prerequisite.........................................................................................................407 Running the Repost Account Ledger Program................................................................408 Setting Data Selection and Sequence for Repost Account Ledger.........................................408 Setting Processing Options for Repost Account Ledger (R099102)........................................408 Recalculating the Fiscal Year and Period................................................................... .......408 Understanding When to Recalculate the Fiscal Year and Period................. ................. .........409 Running the Calculate Fiscal Year and Period Program.....................................................410 Setting Data Selection and Sequence for Calculate Fiscal Year and Period.. .. .. .. .. .. .. . .. .. .. .........410 Setting Processing Options for Calculate Fiscal Year and Period (R099103)............. ................410
xxv
Contents
Chapter 36 Revising an Organization........................................................................... .......413 Understanding Organization Revisions...................................................................... .......413 Understanding Account Structure Revisions................................................................ .......414 Understanding Tables Affected by Account Structure Revisions......................................... .......414 Prerequisite..................................................................................................... .......415 Changing a Business Unit on Multiple Accounts... ........................................................ .......415 Understanding Changes to a Business Unit...................................................................415 Prerequisite.........................................................................................................415 Form Used to Change a Business Unit on Multiple Accounts...............................................416 Changing a Business Unit on Multiple Accounts..............................................................416 Changing Accounts by Object................................................................................ .......416 Understanding Changes to Accounts by Object...............................................................416 Form Used to Change Accounts by Object....................................................................417 Changing Accounts by Object...................................................................................417 Changing Accounts by Subsidiary........................................................................... .......417 Understanding Changes to Accounts by Subsidiary..........................................................417 Form Used to Change Accounts by Subsidiary................................................................418 Changing Subsidiary Accounts... ...............................................................................418 Updating the F0911 and F0902 Tables. ..................................................................... .......418 Understanding the Process to Update the F0911 and F0902 Tables.......................................418 Prerequisites.......................................................................................................418 Running the Update BU.Obj.Sub to Jrnl Ent Program........................................................419 After Running the Update BU.Obj.Sub to Jrnl Ent Program.................................................419 Changing the Company Number on a Business Unit...................................................... .......419 Understanding Changes to the Company Number on a Business Unit.. .... ... ... ... ... ... ... ... .........419 Moving a Business Unit to a Different Company..............................................................420 Changing Account Information............................................................................... .......421 Understanding Account Information Changes.................................................................421 Running the Change Account Information Program..........................................................422 Setting Data Selection for Change Account Information.....................................................422 Setting Processing Options for Change Account Information (R09813). . .. .. . .. .. . .. . .. .. . .. .. . .. ........422 Updating the Model/Consolidated Field..................................................................... .......423 Understanding Model/Consolidated Field Updates...........................................................423 Running the Update Model/Consolidated Field Program.....................................................424 Updating Category Codes for Business Units.............................................................. .......424 Understanding Category Code Updates........................................................................424 Prerequisite.........................................................................................................424 Running the Update Cat Codes F0101>F0006 Program.....................................................425
xxvi
Contents
Chapter 37 Closing Accounting and Reporting Periods.................................................... .......427 Understanding Period-End Close Tasks..................................................................... .......427 Closing the Accounting Period................................................................................ .......428 Understanding How to Close an Accounting Period..........................................................428 Understanding the Affect of Closing an Accounting Period..................................................428 Forms Used to Close the Accounting and Reporting Period.................................................429 Closing an Accounting Period for a Company.................................................................429 Closing the Accounting Period and Year for a Company.....................................................431 Closing an Accounting Period for Multiple Companies.......................................................431 Changing Financial Reporting Periods...................................................................... .......431 Understanding Financial Reporting Dates......................................................................432 Changing a Financial Reporting Period.........................................................................432
Chapter 38 Closing the Fiscal Year.............................................................................. .......433 Understanding the Fiscal Year Close........................................................................ .......433 Prerequisites.......................................................................................................434 Understanding Setup Requirements and Common Tasks................................................ .......434 Understanding Fiscal Year Setup Requirements... ...........................................................435 Understanding Common Tasks for the Year-End Close......................................................435 Closing a Fiscal Year........................................................................................... .......436 Understanding the Annual Close Program.....................................................................436 Running the Annual Close Program............................................................................436 Setting Data Selection and Sequence for Annual Close.....................................................436 Setting Processing Options for Annual Close (R098201)....................................................437 Closing a Fiscal Year for Budgets............................................................................ .......437 Understanding the Fiscal Year Close for Budget Ledger Types.............................................438
Chapter 39 Summarizing Records and Purging Records................................................... .......439 Understanding Summarizations, Deletions and Purges................................................... .......439 Summarizing Account Ledger Records...................................................................... .......439 Understanding the Summarize Transactions Program.......................................................439 Prerequisites.......................................................................................................440 Summarizing Transactions.......................................................................................441 Setting Processing Options for Summarize Transactions (R09811)........................................441 Purging Prior-Year Records................................................................................... .......441
xxvii
Contents
Understanding the Purge Prior Year JEs Program... .........................................................442 Prerequisites.......................................................................................................443 Purging Prior-Year Records......................................................................................443 Setting Data Selection for Purge Prior Year JEs..............................................................443 Setting Processing Options for Purge Prior Year JEs (R09911).............................................443 Purging Prior-Year Account Balances....................................................................... .......444 Understanding the Purge Prior Year Account Balances Program...........................................444 Prerequisite.........................................................................................................444 Purging Account Balances for Prior Years.....................................................................444 Deleting Account Master Records............................................................................ .......444 Understanding the Delete Account Master Records..........................................................444 Prerequisite.........................................................................................................445 Running the Delete Account Master Records Program......................................................445 Setting Processing Options for Delete Account Master Records (R09814). . . . . . . . . . . . . . . . . . . . . . . ........445 Deleting Business Units and Companies.................................................................... .......445 Understanding the Delete Business Unit/Company Program................................................446 Prerequisites.......................................................................................................446 Running the Delete Business Unit/Company Program.......................................................446 Setting Processing Options for Delete Business Unit/Company (R09925).. ... .. .. ... .. .. ... .. .. .........446
Appendix A General Accounting Tables......................................................................... .......449 Primary Tables.................................................................................................. .......449 Supplemental Tables........................................................................................... .......449
Appendix B Mapping Fields for Journal Entry Batch Processing......................................... .......453 Mapping Fields in the F0911Z1 Table........................................................................ .......453 Mapping Fields in the F0911Z1 Table for Advanced Cost Accounting. .... .... .... ... .... .... .... ... ... .......457 Mapping Fields in the F0911Z1 Table for Externally Reconciled Transactions......................... .......466 Updating Reconciled Transactions in EnterpriseOne.........................................................467
Appendix C Conversion Flow Field Mapping for Automatic Bank Statement Processing........... .......469 Mapping BAI2 Fields to the F09610 and F09611 Tables.................................................. .......469 Record 01...........................................................................................................470 Record 02...........................................................................................................471
xxviii
Contents
Record 03...........................................................................................................472 Record 16...........................................................................................................473 Record 88...........................................................................................................475 Record 49...........................................................................................................476 Record 98...........................................................................................................476 Record 99...........................................................................................................476 Mapping SWIFT Fields to the F09610 and F09611 Tables............................................... .......477 Block 2..............................................................................................................478 Block 4..............................................................................................................478
Appendix D Mapping Fields for Budget Data Import......................................................... .......483 Mapping Fields in the F0902Z1 Table....................................................................... .......483
Appendix E Mapping Fields for Inbound Multisite Consolidations....................................... .......487 Mapping Fields in the F1001Z1 Table....................................................................... .......487 Mapping Fields in the F1002Z1 Table....................................................................... .......490
Appendix F Delivered Workflow for JD Edwards EnterpriseOne General Accounting............... .......495 Delivered Workflow for JD Edwards EnterpriseOne General Accounting............................... .......495 Journal Entry Batch Approval....................................................................................495 Route Expense Report............................................................................................496
Appendix G JD Edwards EnterpriseOne General Accounting Reports................................... .......497 General Accounting Reports.................................................................................. .......497 General Journal Reports..........................................................................................497 Trial Balance Reports. ............................................................................................498 Category Code Reports...........................................................................................498 General Ledger Reports..........................................................................................498 JD Edwards General Accounting Reports: A to Z.......................................................... .......498 JD Edwards EnterpriseOne General Accounting Reports: Selected Reports.......... ................ .......501 R00650 - Data by Business Unit.................................................................................501 Processing Options for Data by Business Unit (R00650)....................................................501
xxix
Contents
R09205P, R09206, R09207- Account Master Reports.......................................................501 Processing Options for the Account Master Reports (R09205P, R09206, R09207)......................502 R09301 - Unposted General Journal, General Journal by Batch, Unposted Cash Basis. . . . . . . . ........502 Processing Options for Unposted General Journal and Unposted Cash Basis Report (R09301)........503 R09311 - General Journal by Account..........................................................................503 Processing Options for General Journal by Account (R09311)..............................................503 R09321 - Transaction Journal....................................................................................503 Processing Options for Transaction Journal (R09321).......................................................503 R09410 - Trial Balance Report...................................................................................504 Processing Options for Trial Balance Report (R09410)......................................................504 R094121 - Trial Balance by Object Report.....................................................................506 Processing Options for Trial Balance By Object Report (R094121)..... ..... ...... ...... ...... ............506 R09421 - G/L by Object Account................................................................................507 Processing Options for G/L by Object Account (R09421)....................................................507 R09422 - G/L with Subledger Totals............................................................................509 Processing Options for G/L with Subledger Totals (R09422)................................................510 R09423 - Transactions by Object................................................................................511 Data Selection for the Transactions by Object.................................................................512 Processing Options for Transactions by Object (R09423) and Transactions by Subsidiary (R09424)............................................................................................................512 R09424 - Transactions by Subsidiary...........................................................................513 Data Selection for the Transactions by Subsidiary............................................................513 Processing Options Transactions by Subsidiary (R09424)..................................................513 R09451 - Account Totals by Supplier/Customer...............................................................513 Processing Options for Account Totals by Supplier/Customer (R09451). . . . . . . . . . . . . .. . . . . . . . . . . . ........513 R09470 - G/L by Category Code................................................................................514 Processing Options for G/L by Category Code (R09470)... .................................................514 R09472 - Debit/Credit T/B by Category Code.................................................................516 Processing Options for Debit/Credit T/B by Category Code (R09472).....................................516 R11C750 - Cash Basis Integrity Test............................................................................517 Data Selection and Sequence for the Cash Basis Integrity Report.........................................517 Processing Options for the Cash Basis Integrity Test (R11C750)... ........................................517 R11C760 - Cash Basis Audit Report............................................................................517 Data Selection and Data Sequencing for the Cash Basis Audit Report....................................518 Processing Options for Cash Basis Audit Report (R11C760)................................................518
xxx
Contents
Index ............................................................................................................529
xxxi
Contents
xxxii
Application Fundamentals
Each application implementation guide provides implementation and processing information for your JD Edwards EnterpriseOne applications. For some applications, additional, essential information describing the setup and design of your system appears in a companion volume of documentation called the application fundamentals implementation guide. Most product lines have a version of the application fundamentals implementation guide. The preface of each implementation guide identifies the application fundamentals implementation guides that are associated with that implementation guide.
xxxiii
General Preface
The application fundamentals implementation guide consists of important topics that apply to many or all JD Edwards EnterpriseOne applications. Whether you are implementing a single application, some combination of applications within the product line, or the entire product line, you should be familiar with the contents of the appropriate application fundamentals implementation guides. They provide the starting points for fundamental implementation tasks.
See Also
Oracles PeopleSoft Customer Connection, http://www.oracle.com/support/support_peoplesoft.html
Web
From the Documentation section of Oracles PeopleSoft Customer Connection website, access the PeopleBooks Press website under the Ordering PeopleBooks topic. Use a credit card, money order, cashiers check, or purchase order to place your order.
Telephone
Contact MMA Partners, the book print vendor, at 877 588 2525.
xxxiv
General Preface
Email
Send email to MMA Partners at peoplebookspress@mmapartner.com.
See Also
Oracles PeopleSoft Customer Connection, http://www.oracle.com/support/support_peoplesoft.html
Additional Resources
The following resources are located on Oracles PeopleSoft Customer Connection website:
Resource Application maintenance information Business process diagrams Interactive Services Repository Hardware and software requirements Updates + Fixes Support, Documentation, Business Process Maps Support, Documentation, Interactive Services Repository Implement, Optimize, and Upgrade; Implementation Guide; Implementation Documentation and Software; Hardware and Software Requirements Implement, Optimize, and Upgrade; Implementation Guide; Implementation Documentation and Software; Installation Guides and Notes Implement, Optimize, and Upgrade; Implementation Guide; Implementation Documentation and Software; Pre-Built Integrations for PeopleSoft Enterprise and JD Edwards EnterpriseOne Applications Implement, Optimize, and Upgrade; Implementation Guide; Supported Platforms Support, Documentation, Documentation Updates Support, Support Policy Support, Documentation, Documentation Updates, Category, Release Notes Support, Roadmaps + Schedules Support, Documentation, Documentation Updates, Category, Release Notes Support, Documentation, Documentation Updates, Category, Release Value Proposition Support, Documentation, Documentation Updates, Category, Statement of Direction Navigation
Installation guides
Integration information
Minimum technical requirements (MTRs) (JD Edwards EnterpriseOne only) Documentation updates Implementation guides support policy Prerelease notes Product release roadmap Release notes Release value proposition Statement of direction
xxxv
General Preface
Typographical Conventions
This table contains the typographical conventions that are used in implementation guides:
Typographical Convention or Visual Cue Bold Description Indicates PeopleCode function names, business function names, event names, system function names, method names, language constructs, and PeopleCode reserved words that must be included literally in the function call. Indicates field values, emphasis, and JD Edwards EnterpriseOne or other book-length publication titles. In PeopleCode syntax, italic items are placeholders for arguments that your program must supply. We also use italics when we refer to words as words or letters as letters, as in the following: Enter the letter O. KEY+KEY Indicates a key combination action. For example, a plus sign (+) between keys means that you must hold down the first key while you press the second key. For ALT+W, hold down the ALT key while you press the W key. Indicates a PeopleCode program or other code example. Indicate chapter titles in cross-references and words that are used differently from their intended meanings.
Italics
xxxvi
General Preface
Description Indicate that the preceding item or series can be repeated any number of times in PeopleCode syntax. Indicate a choice between two options in PeopleCode syntax. Options are separated by a pipe ( | ). Indicate optional items in PeopleCode syntax. When placed before a parameter in PeopleCode syntax, an ampersand indicates that the parameter is an already instantiated object. Ampersands also precede all PeopleCode variables.
{ } (curly braces)
Visual Cues
Implementation guides contain the following visual cues.
Notes
Notes indicate information that you should pay particular attention to as you work with the JD Edwards EnterpriseOne system. Note. Example of a note. If the note is preceded by Important!, the note is crucial and includes information that concerns what you must do for the system to function properly. Important! Example of an important note.
Warnings
Warnings indicate crucial configuration considerations. Pay close attention to warning messages. Warning! Example of a warning.
Cross-References
Implementation guides provide cross-references either under the heading See Also or on a separate line preceded by the word See. Cross-references lead to other documentation that is pertinent to the immediately preceding documentation.
xxxvii
General Preface
Example of a country-specific heading: (FRA) Hiring an Employee Example of a region-specific heading: (Latin America) Setting Up Depreciation
Country Identifiers
Countries are identified with the International Organization for Standardization (ISO) country code.
Region Identifiers
Regions are identified by the region name. The following region identifiers may appear in implementation guides: Asia Pacific Europe Latin America North America
Industry Identifiers
Industries are identified by the industry name or by an abbreviation for that industry. The following industry identifiers may appear in implementation guides: USF (U.S. Federal) E&G (Education and Government)
Currency Codes
Monetary amounts are identified by the ISO currency code.
xxxviii
General Preface
As If Currency Code
Enter the three-character code to specify the currency that you want to use to view transaction amounts. This code enables you to view the transaction amounts as if they were entered in the specified currency rather than the foreign or domestic currency that was used when the transaction was originally entered. Displays a number that identifies a group of transactions to be processed by the system. On entry forms, you can assign the batch number or the system can assign it through the Next Numbers program (P0002). Enter the date in which a batch is created. If you leave this field blank, the system supplies the system date as the batch date. Displays a code from user-defined code (UDC) table 98/IC that indicates the posting status of a batch. Values are: Blank: Batch is unposted and pending approval. A: The batch is approved for posting, has no errors and is in balance, but has not yet been posted. D: The batch posted successfully. E: The batch is in error. You must correct the batch before it can post. P: The system is in the process of posting the batch. The batch is unavailable until the posting process is complete. If errors occur during the post, the batch status changes to E. U: The batch is temporarily unavailable because someone is working with it, or the batch appears to be in use because a power failure occurred while the batch was open.
Batch Number
Branch/Plant
Enter a code that identifies a separate entity as a warehouse location, job, project, work center, branch, or plant in which distribution and manufacturing activities occur. In some systems, this is called a business unit. Enter the alphanumeric code that identifies a separate entity within a business for which you want to track costs. In some systems, this is called a branch/plant. Enter the code that represents a specific category code. Category codes are user-defined codes that you customize to handle the tracking and reporting requirements of your organization. Enter a code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the F0010 table and must identify a reporting entity that has a complete balance sheet. Enter the three-character code that represents the currency of the transaction. JD Edwards EnterpriseOne provides currency codes that are recognized by the International Organization for Standardization (ISO). The system stores currency codes in the F0013 table. Enter the company number associated with the document. This number, used in conjunction with the document number, document type, and general ledger date, uniquely identifies an original document. If you assign next numbers by company and fiscal year, the system uses the document company to retrieve the correct next number for that company.
Business Unit
Category Code
Company
Currency Code
Document Company
xxxix
General Preface
If two or more original documents have the same document number and document type, you can use the document company to display the document that you want. Document Number Displays a number that identifies the original document, which can be a voucher, invoice, journal entry, or time sheet, and so on. On entry forms, you can assign the original document number or the system can assign it through the Next Numbers program. Enter the two-character UDC, from UDC table 00/DT, that identifies the origin and purpose of the transaction, such as a voucher, invoice, journal entry, or time sheet. JD Edwards EnterpriseOne reserves these prefixes for the document types indicated: P: Accounts payable documents. R: Accounts receivable documents. T: Time and pay documents. I: Inventory documents. O: Purchase order documents. S: Sales order documents. Effective Date Enter the date on which an address, item, transaction, or record becomes active. The meaning of this field differs, depending on the program. For example, the effective date can represent any of these dates: The date on which a change of address becomes effective. The date on which a lease becomes effective. The date on which a price becomes effective. The date on which the currency exchange rate becomes effective. The date on which a tax rate becomes effective. Fiscal Period and Fiscal Year G/L Date (general ledger date) Enter a number that identifies the general ledger period and year. For many programs, you can leave these fields blank to use the current fiscal period and year defined in the Company Names & Number program (P0010). Enter the date that identifies the financial period to which a transaction will be posted. The system compares the date that you enter on the transaction to the fiscal date pattern assigned to the company to retrieve the appropriate fiscal period number and year, as well as to perform date validations.
Document Type
xl
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Getting Started with JD Edwards EnterpriseOne Financial Management Application Fundamentals, JD Edwards EnterpriseOne Financial Management Application Fundamentals Implementation
xli
Preface
To display the Ledger Type 2 field on certain forms, you must set a processing option for the program. Net Postings Transaction Code Displays an accumulated amount that shows the net postings for a period or year. Enter a code that identifies the type of transaction that appears on a bank statement. The code must exist in UDC table 09/BJ and is used to identify a journal entry, customer payment, and so on.
xlii
CHAPTER 1
Chapter 1
Input transactions, such as sales orders, purchase orders, receipts, journal entries, and so on
System creates records in: Batch Control (F0011) Account Ledger (F0911)
Source transactions, such as sales orders, purchase orders, receipts, journal entries, and so on
We discuss these business processes in the business process chapters in this implementation guide.
Chapter 1
Workforce Management
Payroll
Financials
Logistics Management Inventory Management Warehouse Management Sales Order Management Procurement and Subcontract Management EDI Processing Transportation Management Advanced Stock Valuation
Accounts Receivable Accounts Payable Job Cost Multi-Currency Processing Service Billing Tax Processing
General Accounting
Localization Asia Pacific Latin America Central America (LACA) Europe, Middle East, and Asia (EMEA)
Multi-mode Manufacturing
Homebuilder Management
Service Management
The JD Edwards EnterpriseOne General Accounting system works with other JD Edwards EnterpriseOne systems to ensure that all information is fully integrated into the general ledger. We discuss integration considerations in the implementation chapters in this implementation guide. Supplemental information about third-party application integrations is located on the Oracle | PeopleSoft Customer Connection website.
Chapter 1
Chapter 1
In the planning phase of your implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About This Documentation with information about where to find the most current version of each. When determining which electronic software updates (ESUs) to install for JD Edwards EnterpriseOne General Accounting, use the EnterpriseOne and World Change Assistant. EnterpriseOne and World Change Assistant, a Java-based tool, reduces the time required to search and download ESUs by 75 percent or more and enables you to install multiple ESUs at one time. See JD Edwards EnterpriseOne Tools 8.96 Software Update Guide For information about the Rapid Start solution for implementation of JD Edwards EnterpriseOne General Accounting, review the documentation available. See JD Edwards EnterpriseOne Rapid Start 8.12 Documentation, JD Edwards EnterpriseOne Rapid Start 8.12 Documentation, Rapid Start Solution.
See Also
About This Documentation, About This Documentation PrefaceAbout This Documentation Preface, page xxxiii
Chapter 1
2. Set up next numbers by system and by company and fiscal year. 3. Set up batch approval and post security for journal entries. Set up approved and secured users. 4. Set up AAIs for account reconciliation and reconciliation codes. 5. Set up UDCs, bank account cross-references, automatic bank statement accounts, and automatic reconciliation rules and groups. 6. Set up growth patterns and assign them to business units. 7. Set up cash type rules for the JD Edwards EnterpriseOne Accounts Receivable, JD Edwards EnterpriseOne Accounts Payable, and JD Edwards EnterpriseOne General Accounting systems and define a cash forecast report structure. 8. Set up cash flow activity codes, normal balance codes, and cash flow rules. 9. Set up document types for cash basis entries, assign the document types to the actual amounts (AA) ledger, and set up AAIs for unapplied receipts and accounts payable and accounts receivable balance accounts. 10. Set up 52-period fiscal date patterns and assign the dates to a company.
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Next Numbers JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Batch Approval and Post Security Chapter 4, Setting Up Account Reconciliation, page 33 Chapter 5, Setting Up Automatic Bank Statement Processing, page 35 Chapter 6, Setting Up Budget Forecasting and Planning, Setting Up Growth Patterns, page 53 Chapter 7, Setting Up Cash Forecasting, page 57
Chapter 8, Setting Up Statements of Cash Flow, page 69 Chapter 9, Setting Up Cash Basis Accounting, page 75
Chapter 1
Step 11. Set up sales tax using Vertex Sales Tax Q Series.
Reference JD Edwards EnterpriseOne Tax Processing 8.12 Implementation Guide, Mapping Fields from Vertex Sales Tax Q Series System to JD Edwards EnterpriseOne Software
Chapter 1
CHAPTER 2
Chapter 2
Description Multiple ledgers provide flexibility without requiring you to enter unnecessary and redundant data. With multiple ledgers, you can: Define any number of unit or monetary ledger types, such as actual or budgeted. Retrieve data about anything from global revenue by product to an individual employees expenses, without creating separate account numbers. Maintain transactions in the appropriate ledger and post to the general ledger by summary or detailed transaction. View two ledgers simultaneously. For example, you can view budget and actual ledgers, with the variance calculated online.
Budgeting
You determine the amount of detail to include in your budgets. For example, you can create budgets at the project or business unit level, or by major account category or specific account. You can also create journal entries for each account and budget amount. This detailed method provides a formal audit trail and is used by construction companies and government agencies that need to record supplemental appropriations for an original budget. You can compare your budget-to-actual figures online using year-to-date, period-to-date, or any other time frame. This comparison enables you to respond to variances in a timely manner. If your budget changes, you can create journal entries that explain the reason for the change to ensure that next years budgets are more accurate. Managers can create their department budgets using a PC spreadsheet and then upload the figures into the JD Edwards EnterpriseOne General Accounting system and produce a final budget.
Allocations
Allocations can be defined for many purposes, such as to distribute expenses and to create annual or period budgets. Using one simple allocation, you can create budgets that reflect an increase or decrease over last years budget or actual amounts. You can allocate from one account to another account based on values in a third account. For example, you can allocate your monthly utilities expense from an overhead account to individual departments based on their percentage of square footage. You can also create allocations based on other allocations and process them together. The three types of allocations in the JD Edwards EnterpriseOne General Accounting system are recurring journal entries, indexed allocations, and variable numerator allocations.
Account Reconciliation After you perform the initial setup requirements, you can reconcile your accounts on a periodic basis. You can reconcile selected expense accounts and bank accounts as well as bank statements. The JD Edwards EnterpriseOne General Accounting system has both manual and automatic bank statement reconciliation programs. Some countries have banking practices that rely heavily on magnetic media processing, electronic fund transfers, and direct bank involvement in the settlement of outstanding debts. For these countries, the bank statement serves as a source document for all banking activity.
10
Chapter 2
Description Intercompany settlements ensure that each companys net balance equals zero (that is, debits equal credits). If your business enters transactions between companies, the companies will be out of balance unless you create and post intercompany balancing entries. You can either create these settlements yourself or choose a method of intercompany settlements to use and have the system create them automatically. Traditionally, when organizations have changed their reporting structure, the process has entailed reworking the chart of accounts, followed by a time-consuming data conversion to get the historical data into the new account coding design. With the JD Edwards EnterpriseOne General Accounting system, when you change an account number, the associated transaction detail and balance histories are transferred automatically by the system, eliminating the need for data conversions. A free-form account number that can be used as a cross-reference to an old account number is available for the initial conversion to the JD Edwards EnterpriseOne General Accounting system.
Reorganization Flexibility
11
Chapter 2
12
CHAPTER 3
13
Chapter 3
Description User-defined codes are codes that you can customize for your business needs. Various programs throughout the JD Edwards EnterpriseOne General Accounting system and other JD Edwards EnterpriseOne systems use these codes. Next numbers establish an automatic numbering system for the documents that you enter in the system. See JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Next Numbers.
Next numbers
Ledger types define the ledgers that you maintain in the general ledger. Ledger types include AA (actual amounts) and BA (budget amounts). After you set up ledger types, you set up the financial rules for each ledger type. Automatic accounting instructions (AAIs) define the rules for the chart of accounts and establish how the system creates automatic entries. If you work in a multilingual environment, you can translate the descriptions of your AAIs.
Prerequisite
Set up your companies, fiscal patterns, business units, and accounts. See JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Organizations.
14
Chapter 3
Description When you create a batch of documents, such as journal entries, you might want to verify the total number of documents and total currency amount for the batch. Doing this enables you to verify the total amount expected against the total amount entered immediately after you enter a batch. The Manager Approval of Input constant enables you to specify whether management approval of batches is required before batches can be posted. Circumstances might occur, especially during implementation, when you need to post batches to prior accounting periods. A constant controls whether the system allows you to do this. If the constant is not set to allow prior period posting, another approach is to change the current period for the company to a prior period and then post to that period. In either case, you need to close the prior period again and process updated period-end financial reports for that period and subsequent periods.
Manager Approval of Input Allow PBCO Postings (allow posted before cut off postings)
You control whether you allow journal entries to be entered with invalid account numbers. Invalid account numbers are account numbers that have not yet been set up in the system for a business unit that already exists in the Business Unit Master table (F0006). By entering an invalid account number, you can complete a batch without exiting and losing your entries. If you allow an invalid account number, the system either: Leaves the batch in an error status and unposted until you correct the invalid account number. Creates a new account dynamically if you have set up the system to do so.
Intercompany Settlements
If your organization has transactions between companies, the companies will be out of balance unless you create and post intercompany balancing entries. You create intercompany settlements to ensure that each companys net balance equals zero (that is, debits equal credits). You can either create these settlements yourself or have the system create them automatically. You can select one of these intercompany settlement methods to use: Hub method Detail method Configured Hub method
Account Symbols
When you enter an account number during data entry, you can use any of these formats: Business unit.object.subsidiary Short ID (8-digit, system-assigned number) Third account number You specify the format that you are using by preceding the account number with a symbol that identifies the format. Normally, you do not specify an account symbol for the most commonly used format to allow for quicker data entry. You can also define the symbol that separates the different components of the business unit.object.subsidiary account format.
15
Chapter 3
Prerequisite
Ensure that only authorized personnel can access and change the general accounting constants.
See Also
JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Setting Up General Accounting for Multicurrency Processing
FormID
Navigation General Accounting System Setup (G0941), General Accounting Constants On the System Setup form, click General Accounting Constants.
Usage Access constants for the General Accounting system, or other systems. Set up constants for the General Accounting system.
W0000B
Specify whether batch control is required. If you select this check box, the system displays an additional form when you enter a batch. You enter the total number of documents and the total amount that you expect the batch to contain. When you finish entering each batch and close the program, the system displays the difference, if any, between the totals that you expected to enter and the totals that you actually entered.
Manager Approval of Input Specify whether the manager is required to approve General Accounting batches before they can be posted.
16
Chapter 3
If you select this check box, the manager must approve batches. The system assigns a Pending status to the batch, and a manager must approve it before it can be posted. If you clear this check box, the system assigns an Approved status to the batch, and it does not require manager approval. Allow PBCO Postings (allow post before cutoff postings) Allow Invalid Accounts Specify whether to allow posting to prior accounting periods. If you allow posting to prior periods, the system generates a warning message to prevent accidental postings to a prior period. Specify whether to allow entry of invalid account numbers for the distribution of vouchers, invoices, and journal entries. If you select this check box, you can enter invalid account numbers if the number is preceded by the invalid account symbol, which is #. If you allow entries with invalid account numbers, you must either change the number to a valid account number or set up a new account number before the batch will post. The system verifies the account number against the Account Master table (F0901). Symbol to Identify Short Number Enter a code, such as * or /, that precedes the short account number (the eight-digit code) during data entry. If the short account number is the one that you typically use, leave this field blank. If it is seldom used, enter a symbol to identify it to the system. Only one of the three fields used for account symbols can be blank. Use blank for the type of account number that you typically use. The other two fields must each be unique. Be sure that no symbol (period, comma, and so on) is used for another purpose in the system. Symbol to Identify BU.Object.Sub (symbol to identify business unit.object.subsidiary) Enter a code, such as * or / that precedes the business unit.object.sub (long) account number during data entry. The business unit.object.sub account number is most commonly used. If it is the one that you typically use, leave this field blank. If it is seldom used, enter a symbol to identify it to the system. Only one of the three fields used for account symbols can be blank. The other two must each be unique. Be sure that no symbol (period, comma, and so on) is used for another purpose in the system. Symbol to Identify 3rd G/L Account # (symbol to identify 3rd general ledger account number) Enter a code, such as * or / that precedes the third, or unstructured, account number during data entry. If the third account number is the one that you typically use, leave this field blank. If it is seldom used, enter a symbol to identify it to the system. Only one of the three fields used for account symbols can be blank. The other two must each be unique. Be sure that no symbol (period, comma, and so on) is used for another purpose in the system. Account Separator Character Enter a character that divides the business unit, object, and subsidiary elements or the flex account code elements of an account number on forms and reports. Enter any special character except #, which is the invalid account symbol or \, which is the work order prefix, as a separator character. Do not use
17
Chapter 3
alphabetic characters or numbers. If you leave this field blank, the system uses the default character, which is a period (.). Intercompany Settlements Specify the method that the system uses to automatically create journal entries between companies within an organization (intercompany settlements). Values are: 1: Hub method. Create intercompany settlements using a hub company. 2: Detail method. Create intercompany settlements without a hub company. This method is valid for multicurrency processing. 3: Configured hub method. Create intercompany settlements using a configured hub. This method is valid for multicurrency processing. N: Do not create intercompany settlements. The system does not post a batch if it contains intercompany settlements. *: Do not create intercompany settlements. The system posts a batch even if it contains intercompany settlements.
See Also
JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Setting Up General Accounting for Multicurrency Processing, Setting Up Multicurrency Constants
18
Chapter 3
Business unit category codes are stored in the Business Unit Master table (F0006).
See Also
JD Edwards EnterpriseOne Tools 8.96 Foundation Guide
19
Chapter 3
20
Chapter 3
Account Balances (F0902) Contains balances by fiscal year and ledger type
FormID
Navigation General Accounting System Setup (G0941), Ledger Type Master Setup On the Work with Ledger Types form, select a ledger and click Select.
21
Chapter 3
Enter a value for Units Ledger Type. The units ledger is relational to the amount ledger. The first character in both ledgers is the same. The second character in the units ledger is a U. The one exception to this rule is the AZ (Cash Basis) amount ledger. If you do not fill in a units ledger for the AZ amount ledger, a default units ledger of ZU will be used by the G/L Post. The units ledger must be a valid ledger type. With the exception of the AZ ledger, you typically set up the unit ledger type with the same first character as the actual amounts ledger type to which it applies. For example, the units ledger for AA is AU. You can set up a units ledger to be used with any of the ledgers that you set up in UDC 09/LT. However, unit ledger types FU, HU, and IU can be used only with the FA, HA, and IA ledgers, respectively. For example, you cannot set up an FX ledger for actual amounts and use it with the FU ledger for units.
Select this option to denote that retained earnings should be calculated for this ledger during the Annual Close. This flag must be selected for the AA and AZ ledgers. This option specifies whether the Annual Close program (R098201) closes accounts in this ledger to a retained earnings account.
Select this check box if entries for this ledger must be in balance (net to zero). Unlike the Create Intercompany Settlements check box, this check box does
22
Chapter 3
not ensure that companies within this ledger are in balance. This check box ensures only that entries for this ledger are in balance. Create Intercompany Settlements Select this check box if you want the system to create balancing entries when a transaction that involves multiple companies is entered for this ledger. This check box works in conjunction with the intercompany settlement method on the General Accounting Constants form. If this check box is selected, the system validates that entries for this ledger are in balance by company when posted. If companies are out of balance, the system uses the intercompany settlement method to bring them into balance. If this check box is selected and the intercompany settlement method is set to N (no intercompany transactions), the system will not post a transaction that involves multiple companies if those companies are out of balance. If this check box is not selected, the system will not validate that companies within this ledger are in balance. Select this check box to prevent users from entering amounts directly in the Account Balances table (F0902) for this ledger. Note. You must select this check box for ledger types AA, CA, and AZ. Otherwise, the system displays an error message. If an amount ledger has a unit ledger associated with it, the check box value for the unit ledger type must be the same as the amount ledger. You must select this check box for the AA ledger type so that users cannot access a budget program, for example, change the ledger type, and change the account balances. However, you might not want to select this check box for the AC ledger because the Compute Restated Balances program (R11414) directly updates this ledger. For example, if you enter amounts for ledger type BA, do not select this check box so that you can enter amounts using the budget programs. Then when finished, select this check box to prevent future updates to the F0902 table. Roll Original Budget to Next Year Override Budget Do Not Spread Code For budget ledger types, select this check box to designate that the original budget can be rolled forward in the Annual Close program. The Job Cost system uses this functionality. For budget ledger types, select this check box for the Spread Annual to Periods program (R14801) to override the DNS (Do Not Spread) code and evenly distribute annual budget amounts among the periods for accounts that are assigned the DNS code. If this check box is not selected, the Spread Annual to Periods program does not distribute annual budget amounts for accounts that are assigned the DNS code. You must distribute the amounts manually. Prevent Creation of Journal Entry Upper Select this check box to specify whether the system should prevent journal entries from being created for this ledger. You will receive an error if you attempt to prevent the creation of journal entries for the AA, CA, or AZ ledgers. Enter the first line of description used in column headings on a report or form. This description should be no larger than the data item size, if possible. If the column heading is only one line, it should be placed in this column. Use the second line of the Column Title when one is not sufficient. Enter the second line of description used in column headings on a report or form. This description should be no larger than the data item size, if possible. If the column heading is only one line, it should be placed in the first column.
Lower
23
Chapter 3
See Also
JD Edwards EnterpriseOne Job Cost 8.12 Implementation Guide, Setting Up the Job Cost System, Setting Up Ledger Types for Job Cost JD Edwards EnterpriseOne Fixed Assets 8.12 Implementation Guide, Setting Up the Fixed Assets System, Setting Up Ledger Type Rules for Fixed Assets JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Setting Up Balance Restatement and As If Restatement, Setting Up the Ledger Type and Rules for Balance Restatement
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Automatic Accounting Instructions, Setting Up AAIs JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Setting Up General Accounting for Multicurrency Processing, Setting Up Multicurrency AAIs for General Accounting
24
Chapter 3
Company 00000
Object Required
Subsidiary Optional
You set up AAI items GLGx for company 00000 only. (The system assumes that your account structure is consistent across all companies.) The exception is AAI item GLG4, which you must set up for each company because it defines the retained earnings account. This table contains the setup considerations for AAI items GLGx:
AAI GLG2 GLG3 Setup Considerations The beginning account range for assets. Enter the object account only. The beginning account range for liabilities and equities. Enter the object account only. You can use this AAI item to reverse the sign on financial reports. GLG4 The account number for retained earnings. Enter the business unit and object account. If the business unit is the same as the company number for all companies, enter only the object account for company 00000. Otherwise, set up GLG4 for each company and specify the business unit and object account. The GLG4 account number must be greater than the account number for GLG1 and less than the account number for GLG4. GLG5 The ending account number for year-to-date income and loss. Enter the object account only. This account number should indicate the last balance sheet account, which must be a nonposting account. The system uses this AAI item in the balance sheet to ensure that assets are equal to liabilities plus equity (a calculated figure). GLG6 The beginning account range for revenue. Enter the object account only. The system uses this AAI item for automatic sign reversal on reports and to calculate the percentage of revenue on some reports and the retained earnings for the general ledger annual close. GLG7 The ending account range for revenue. Enter the object account and, if applicable, the subsidiary. The system uses this AAI item for automatic sign reversal and to calculate the percentage of revenue on some reports. GLG8 GLG9 The beginning account range for cost of goods. Enter the object account only. You can use this AAI item to reverse the sign of expense accounts on some financial reports. The ending account range for cost of goods. Enter the object account and, if applicable, the subsidiary.
25
Chapter 3
AAI GLG11
Setup Considerations The beginning account range for other income. Enter the object account only. You can use this item to reverse the sign of income accounts on some financial reports. Note. Do not leave the beginning range for GLG11 (other income) blank. If you do not want to enter an account, enter the same account number as the beginning range for GLG13 (other expenses). If you do not want to enter an account number for the beginning range, enter the same account number as the beginning range for GLG12 (ending profit and loss accounts).
GLG12
The account for ending profit and loss (income statement), which is used to calculate retained earnings for the general ledger annual close. This is the last account that appears on an income statement. Any accounts that are greater than this account number will not appear on an income statement nor will the accounts be closed to the retained earnings account. Enter the object account and, if applicable, the subsidiary. If you do not enter an object account, the system uses account 999999. Revenues (GLG6) + Expenses (GLG12) = Retained Earnings (GLG4)
GLG13
The beginning account range for other expenses. Enter the object account only. You can use this AAI item to reverse the sign of other expense accounts on some financial reports. Note. If you do not want to enter an account number for the beginning range, enter the same account number as the beginning range for GLG12 (ending profit and loss accounts).
If your business unit and company number is different for balance sheet accounts, you must set up AAI item GLG4 for each company and specify the balance sheet business unit and object account.
26
Chapter 3
In the following example, the system uses GLG4 for each specific company to post the retained earnings amount. The company number is different from the balance sheet business unit for all companies, as shown in this table:
Company 00100 00200 00300 110 210 310 Business Unit Retained Earnings Object Account 4980 4980 4980 Company-Specific GLG4 00100.110.4980 00200.210.4980 00300.310.4980
If you have multiple balance sheet business units for one company, you must set up AAI item GLG4 for the company and specify one balance sheet account. Then, for year-end processing, you must allocate all of the balance sheet business units to the balance sheet business unit specified in GLG4 for the company. If you do not do this, your company will be out of balance because the offset amount for net income would reflect the accounts for one balance sheet business unit (specified in GLG4 for the company) and not all balance sheet business units. In the following example, the system uses GLG4 for each specific company to post the retained earnings amount. The company number is different from the balance sheet business unit for all companies and company 00100 has multiple balance sheet business units, as shown in this table:
Company 00100 110 210 310 00400 00500 410 510 4980 4980 00400.410.4980 00500.510.4980 Business Unit Retained Earnings Object Account 4980 Company-Specific GLG4 00100.110.4980
Note. GLG4 is the only AAI item for general purpose accounts that you can set up by company. All other general purpose items are set up only for company 00000.
27
Chapter 3
Net Income (Loss) You can specify the text that you want to appear for each subtotal in the first description line under the heading Account Use Description on the Set Up Single AAI Item form. This table shows the information needed to set up AAI item FS01:
AAI Item FS01 Description Financial Statement Totals Business Unit Not used Object Required Subsidiary Optional Sequence Number 1.130
Follow these guidelines when setting up AAI item FSxx: Set up AAI item FSxx only for company 00000. Do not enter a business unit. To avoid unpredictable results, do not enter an object account to which the system posts transactions. Do not set up AAI item FSxx for balance sheet accounts. For each financial statement, the JD Edwards EnterpriseOne General Accounting system provides a report version with subtotals based on AAI items FSxx. You must select the report version that contains the subtotals. For example, to print subtotals for AAI items FSxx on the Simple Income Statement report (R10211B), select the report version Income Statement by Branch with AAI Subtotals instead of Income Statement by Branch.
28
Chapter 3
Speed codes can be company specific if you enter the business unit in the AAI item. Thexin the speed code item is a user-defined single character. We recommend that you use only alphabetic characters (letters AZ) if your business units are numeric. Assume that you set up AAI item SPB and define only the object account (1110) as a speed code. During data entry, you type a business unit and, if appropriate, a subsidiary. For example, if you enter 1.B, the system reads it as 1.1110. After you set up speed codes, you must exit and then restart your JD Edwards EnterpriseOne system before you can enter speed codes instead of account numbers. If you use a flexible format for your chart of accounts, you cannot use speed codes.
29
Chapter 3
You must define complete ranges, consisting of a beginning and an ending AAI item. The first range must begin with GLRC01. We recommend that you end the first range with GLRC02, which is the next consecutive number. Define the next range, if needed, to start with GLRC03 and end with GLRC04, and so on. This table shows the information needed to set up AAI item GLRCxx:
AAI Item GLRCxx Description Reconcilable Ranges Business Unit Not used Object Required Subsidiary Optional Sequence Number 1.400
Prerequisite
Set up the business units for which you want to track supplemental data.
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Understanding Supplemental Data
30
Chapter 3
See Also
JD Edwards EnterpriseOne Tax Processing 8.12 Implementation Guide, Setting Up the Interface to Vertex Sales Tax Q Series
31
Chapter 3
32
CHAPTER 4
33
Chapter 4
You must define complete ranges, consisting of a beginning and an ending AAI item. The first range must begin with GLRC01. We recommend that you end the first range with GLRC02, the next consecutive number. Define the next range, if needed, to start with GLRC03 and end with GLRC04, and so on. This example shows how you might set up your GLRCxx AAIs:
Item Number GLRC01 GLRC02 GLRC03 GLRC04 Description Line 1 Reconcilable Range Reconcilable Range Reconcilable Range Reconcilable Range Description Line 2 Begin Range 1 End Range 1 Begin Range 2 End Range 2 Company 00000 00000 00000 00000 Business Unit Object Account 1110 1110 4110 4110 99999999 99999999 Subsidiary
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Automatic Accounting Instructions, Setting Up AAIs
34
CHAPTER 5
See Also
Chapter 20, Processing Bank Statements Automatically, page 179
See Also
JD Edwards EnterpriseOne Tools 8.96 Web Services Gateway: Configuration Editor Guide
35
Chapter 5
If you receive only one bank flat file monthly for one or both bank formats, set the integration options one time only and ensure that you set the option (line 3) to delete the flat file after running the conversion flow. If you receive multiple bank flat files monthly, you must set the integration options before you run each conversion flow to designate the different file names and locations. Value Enter the name of the text file (bank flat file) and its location on lines 1 and 2 (for BAI2) and lines 4 and 5 (for SWIFT). On line 3, specify whether to delete the text file after transferring data to the staging tables. Values are: 0: Do not delete the text file. 1: Delete the text file.
Value
Access the line for E1 Date Pattern and enter the date format in this field.
36
Chapter 5
Warning! Do not add codes to the UDC tables. The program logic for the automatic bank statement programs depends on certain codes and special handling code values to process information correctly. You can change the description and codes for UDCs that are not hard coded; however, you cannot change what the code represents nor can you change the special handling code value, if one exists. For example, the code 2 in UDC table 09/DT is not hard coded but it has a special handling code of 20. You can change the code from 2 to 4 and the description from Todays Date to Current Date, but you cannot change the date that the code represents nor can you change the special handling code (20).
Note. The transaction type code RJE (or other user-specified code with special handling code 02) is used for bank transactions that already exist as journal entries in the JD Edwards EnterpriseOne General Accounting system. For these transactions, the Automatic Bank Statement process does not create a duplicate transaction but, instead, reconciles the existing journal entry against the general ledger. You can use this transaction type code for bank transactions such as bank fees and transfer fees. If your electronic bank statement originates in the PeopleSoft Enterprise Treasury Management system and you reconcile the statement in JD Edwards EnterpriseOne, you must set up this transaction type code. The journal entries for this transaction type are created in the PeopleSoft Treasury Management system, transferred to the JD Edwards EnterpriseOne General Accounting system, and then reconciled against the general ledger.
37
Chapter 5
Code 1 2 3
38
Chapter 5
Code CR VWT
39
Chapter 5
Description No Matching Receipt in G/L Offsetting Entries Not Created Posting Edit Code Invalid Variance Not Within Tolerance 100 140 110 130
All codes in UDC table 09/BA are hard-coded. You can view a complete list of the codes in documents that are provided by BAI. The JD Edwards EnterpriseOne software also contains the BAI2 codes. Ensure that you update the UDC table manually if BAI makes changes to the transaction types. Examples of BAI2 transaction types include:
Code 010 105 224 Description 01 Opening Ledger Credits Not Detailed Commission Status Summary Detail Description 02 None CR CR Special Handling Code
40
Chapter 5
41
Chapter 5
Set up a cross reference for a bank account. Set up a cross reference for a transaction type.
FormID
Navigation Automatic Bank Statement Setup (G09214), Bank Account Cross Reference
Usage Review electronic bank information for your bank accounts, select a bank account to revise, or delete a bank account. Set up cross references for bank accounts.
On the Work With Bank Account Cross Reference form, click Add. On the Revise Bank Account Cross Reference form, you can select G/L Bank Acct from the Form menu to search for an existing bank account or set up a new one.
Work With Transaction Type W09622A Cross Reference Revise Transaction Type Cross Reference
W09622C
Automatic Bank Statement Setup (G09214), Transaction Type Cross Reference On the Work With Transaction Type Cross Reference form, click Add.
Review transaction types that appear on electronic bank statements. Set up cross references for transaction types.
42
Chapter 5
Enter the bank account number as it appears on the electronic bank statement. Enter a format code from UDC table 09/FT. Values are: BAI2 SWIFT PSFT Format codes are hard-coded.
Enter the GL account number of the bank account on the electronic bank statement. Enter the business unit to use to create journal entries for offset accounts. This is the business unit for a bank account or an alternate offset account. (You identify which offset business unit to use as well as the object and subsidiary accounts on the Revise Transaction Type Cross Reference form.) This field enables you to assign a different offset business unit to each transaction type. If you leave this field blank, the system uses the business unit of the bank account as the default value. The Automatic Bank Statement Process program creates offset accounts for JE transactions only.
43
Chapter 5
Enter the format code from UDC table 09/FT for the transaction type. Enter the transaction type code from UDC table 09/ST (SWIFT) or 09/BA (BAI2) for the format that you entered in the Electronic Format Indicator field. These two fields works in conjunction with one another. If you enter a format and an electronic transaction type code for BAI2 or PSFT, the system displays the Debit/Credit Indicator field on the form. The value in the Special Handling Code field of the transaction type determines whether the amount is a debit (D) or credit (C). If you enter a format for SWIFT, the bank flat file for SWIFT already includes the debit or credit indicator so the Debit/Credit Indicator field does not appear on the form.
Enter a value from UDC table 09/TT. If you enter JE in this field, the Offset Business Unit, Object Account, and Subsidiary fields appear on the form. Enter a value from UDC table 09/BU to specify which business unit to use to create journal entries for offset accounts. Values are: 1: Bank Account Business Unit. 2: Alternate Offset Business Unit. If you enter 2, you must specify the alternate offset business unit on the Revise Bank Account Cross Reference form. If you do not, the system uses the business unit of the bank account.
Enter the object account and, optionally, the subsidiary for the offsetting journal entry.
44
Chapter 5
Reconciliation Rules
Reconciliation rules enable you to maximize the number of transactions that the system automatically reconciles and minimize any manual reconciliation. The Process Automatic Bank Statement program uses default rules to reconcile receipts, payments, and drafts in the F0911 table that have cleared your bank account. Each reconciliation rule can have up to five transaction types. Each tab on the Revise Auto Reconciliation Rules corresponds to a transaction type. You assign a reconciliation code from UDC table 09/RC to each transaction type or let the system assign the default value R (Reconciled One for One Match). The reconciliation rules that you define for a transaction type consists of variance accounts, document types, tolerance limits, and so on. The system stores reconciliation rules in the F09626 table.
Reconciliation Groups
After you set up reconciliation rules, you set up reconciliation groups and assign rules to the groups. You can assign only one reconciliation rule to a group; however, you can use the same reconciliation rule for multiple groups. The Process Automatic Bank Statement program accesses the reconciliation rule assigned to the group to retrieve the bank statement account. The system stores reconciliation groups in the F09627 table.
45
Chapter 5
FormID
Navigation Automatic Bank Statement Setup (G09214), Automatic Reconciliation Rules Setup On Work With Auto Reconciliation Rules form, click Add or select an existing rule to revise. Automatic Bank Statement Setup (G09214), Automatic Reconciliation Group
Usage Review reconciliation rules, select an existing rule to revise, or copy or delete an existing rule. Set up a reconciliation rule.
W09626D
W09627A
Review reconciliation groups, select an existing group to revise, or copy or delete an existing group.
W09627B
On Work With Auto Set up a reconciliation Reconciliation Groups form, group. click Addor select an existing group to revise. Automatic Bank Statement Setup (G09214), Automatic Bank Statement Account Setup On the Work With Auto Bank Statement Setup form, click Add or select an existing account to revise. Review automatic bank statement accounts, select an existing account to revise, or copy or delete an existing account. Set up an automatic bank statement account.
W09628A
46
Chapter 5
Reconciliation Rule
Enter the name of the reconciliation rule for which you want to assign transaction type rules.
Payment Clear
Select this tab if the reconciliation rule applies to payments that have cleared the bank. Payment Variance Select this check box for payment variances. If selected, the system displays the Variance Account, Variance Date Mode, Tolerance Limit, and Variance Doc Type fields, which are required. Select this check box for the system to reconcile payments if the cleared date in the F09617 table is before the general ledger date in the F0911 table. Enter a value from UDC table 09/RC. This value is used by the Process Automatic Bank Statement program to indicate that a bank statement has been approved or processed, a payment was voided, and so on. If you leave this field blank, the system uses R (Reconciled One for One Match) as the default value. Enter the general ledger account that the system uses to record any variance amounts for this transaction type and reconciliation rule. This field and the remaining fields on this tab appear only if the Payment Variance check box is selected. Enter a value from UDC table 09/DT to specify the default date for the system to use when it automatically creates journal entries for variances. Values are:
Variance Account
47
Chapter 5
1: Bank statement date 2: Todays date 3: Cleared date Tolerance Limit Variance Doc Type Enter the maximum amount or highest percentage allowed for the system to create an automatic write-off record. Enter a value from UDC table 00/DT for the system to use to create variance journal entries for payments when you run the Process Automatic Bank Statement program. If you leave this field blank, the system uses PN (Manual Check) as the default value.
Receipt Clear
Select this tab if the reconciliation rule applies to receipts that clear the bank. The Reconciliation Code, Variance Date Mode, and Tolerance Limit fields function the same as those on the Payment Clear tab. Receipt Variance Select this check box for receipt variances. If selected, the system displays the Variance Account, Variance Date Mode, Tolerance Limit, and Variance Doc Type fields, which are required.
Receipt Reconciliation Date Select this check box for the system to reconcile receipts if the cleared date in Exception the F09617 table is before the general ledger date in the F0911 table. Create Auto Batch Receipts Select this check box if you want the system to automatically create batch receipts. If selected, the system displays the Auto Batch Receipt Date Mode field, which is required. The system creates automatic batch receipts and applies them to invoices only for transactions with a customer number. If the customer number is blank, the system creates a logged receipt, which is not applied to invoices. The system creates automatic batch receipts only if the receipt and invoice currency is the same. You cannot apply an alternate currency to an automatic batch receipt. Auto Batch Receipt Date Mode Enter a value from UDC table 09/DT to specify the default date for the system to use when it automatically creates batch receipts. Values are the same as those for the Variance Date Mode field. This field is required if you select the Create Auto Batch Receipts check box. Enter the general ledger account that the system uses to record any variance amounts for this transaction type and reconciliation rule. This field and the remaining fields on this tab appear only if the Receipt Variance check box is selected. Enter a value from UDC table 00/DT for the system to use to create variance journal entries for receipts when you run the Process Automatic Bank Statement program. If you leave this field blank, the system uses RC (Receipts) as the default value.
Variance Account
48
Chapter 5
Document Type
Enter a value from UDC table 00/DT for the system to use to create journal entries when you run the Process Automatic Bank Statement program. If you leave this field blank, the system uses JE (Journal Entry) as the default value.
Draft Paid
Select this tab if a reconciliation rule applies to drafts paid by the bank. G/L Date Mode (general ledger date mode) Draft Document Type Enter a value from UDC table 09/DT to specify the default date for the system to use when it automatically creates an entry between the general ledger bank account and the drafts payable account. This field is required. Enter a value from UDC table 00/DT for the system to use to create journal entries when you run the Process Automatic Bank Statement program. If you leave this field blank, the system uses JE (Journal Entry) as the default value.
49
Chapter 5
Reconciliation Group Reconciliation Rule Update Reference 3 field with Bank Statement Number
Enter a name to identify the reconciliation group. Enter the name of the reconciliation rule. Select this check box for the system to populate the GLR3 field in the F0911 table with the bank statement number. The reconciliation group identifies the default value. This check box also appears on the Revise Auto Bank Statement Account Setup form.
50
Chapter 5
G/L Account Number (general ledger account number) Reconciliation Group Reconciliation Rule
Enter the code that identifies the reconciliation group that you want the system to use when it processes automatic bank statements for this bank account. Enter the code that identifies the reconciliation rule for the system to use when it processes automatic bank statements for this bank account. The rule that you enter in this field must be part of the group that you entered in the previous field. The Reconciliation Group and Reconciliation Rule fields work in conjunction with one another. If you leave this field blank, the system uses the reconciliation rule assigned to the group that you entered in the previous field.
Track Taxes
Select this check box for the system to track taxes for this bank account. To update the Tax Explanation Code, Tax Rate Area, and Tax Item Number fields in the F0911 table, you must select this check box as well as enter values in the two remaining tax fields. If you select the Track Taxes check box, this field is required. Enter the code for the tax rate area for this bank account. This code must exist in the F4008 table. The general ledger date of all transactions for this bank account must be greater than or equal to the effective date and less than or equal to the expiration date of the tax rate/area that you enter in this field. If you leave this field blank, the system uses the tax rate area specified for the GL account number in the F0901 table. If there is none, the system issues an error message.
Tax Rate/Area
If you select the Track Taxes check box, this field is required. Enter a value from UDC table 00/EX that begins with the letter V (value added tax). The system uses this code in conjunction with the tax rate area and tax rules to determine how to calculate a tax. This field is always required if the Tax Rate/Area field contains a value
51
Chapter 5
52
CHAPTER 6
See Also
Chapter 23, Forecasting and Planning Budgets, page 239
53
Chapter 6
Multiplies the account balance by 1.01, which is equivalent to multiplying the account balance by one percent and adding that result to the account balance, if you use a growth pattern type of PCT (percentage). You can specify different fixed amounts or percentage amounts for each year for up to 15 years for a growth pattern. The system compounds the growth amounts that you enter for each year. For example, if you enter a percentage growth pattern and specify 1.0 for year 1 and 2.0 for year 2, the system multiplies the account balance by 1.01 the first year and then multiples that amount by 1.02 the following year (for a total of 3.02 percent). After you set up growth pattern codes, you assign them to business units and specify a revision number. Using a revision number enables you to generate multiple budgets for the same business unit. Growth pattern information is stored in the Forecast Growth Patterns table (F1406).
FormID
Navigation Forecasting and Planning (G1411), Forecast Growth Patterns On the Work With Forecast Growth Patterns form, click Add. Forecasting and Planning (G1411), Business Unit Growth Patterns On the Work With Business Unit Growth Patterns form, click Add.
Usage Review existing growth patterns. Add and revise growth patterns. Review growth patterns assigned to business units. Assign growth pattern codes and revision numbers to business units, and revise them.
W1405A
W1405C
54
Chapter 6
Enter a code to specify the amount or percent of increase that you want the system to apply to revenue and expense accounts when it calculates budget amounts. Assign a user-defined code from UDC table 14/GP to specify whether the budget amounts that you forecast are fixed amounts (FIX) or percentages (PCT). Enter the anticipated growth rate for each year in which you want to forecast budget amounts.
55
Chapter 6
Growth Patterns
Select the Growth Patterns tab. Forecast Amount - Year 1 through Forecast Amount Year 15 Displays the amounts that were set up for the budget pattern.
Budget Codes
The Budget Codes tab and corresponding fields are reserved for future use.
56
CHAPTER 7
See Also
JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Understanding Cash Forecasting in Multiple Currencies
57
Chapter 7
Description of Code Cash Forecast Opening Balances Net Operating Incoming Cash Outgoing Cash 10 10 10 10 10
Special Handling
You can set up additional cash type codes for headings. For example, you might set up a heading code for INVOPN (Open Invoices) to appear under the heading Incoming Cash. You must set up cash type codes for the detail row descriptions and the amounts that roll up into the headings. For example, for the heading Open Invoices, you might set up a detail code for INVCK (Open Invoices by Check) or INVEFT (Open Invoices by EFT). Using the previous example, the Cash Forecast Analysis form and the Cash Forecast Report would appear as follows: Incoming Cash Open Invoices Invoices by EFT 1.1110.FIB Invoices by Check 1.1110.BEAR You must set up rules for detail cash type codes, which include information such as bank account numbers, but not for heading cash type codes.
58
Chapter 7
For each detail code, you specify the system in which the cash type rule applies. The requirements for a rule depend on the system. For example, cash type rules for detail codes in the JD Edwards EnterpriseOne General Accounting system require multiple bank accounts, whereas rules for detail codes in the JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable systems require a single bank account. The system uses these rules to select records from the appropriate detail tables when you refresh your cash flow data. For each detail code, you can specify a weight factor so that amounts are adjusted for more realistic expectations. For example, for the detail code for open invoices, you would set a weight factor of 80 percent if you expect about 80 percent of your open invoices to be paid by the due date. You can also designate a cash type code as active or inactive. When you refresh your cash flow data, the system includes only amounts associated with codes that are active. Cash type rules are stored in the F09521 table.
FormID
Navigation Cash Forecasting (G09319), Cash Type Rules Setup Click Add on the Work with Cash Type Rules form
Usage Review a list of cash type rules. Set up cash type rules for the JD Edwards EnterpriseOne Accounts Receivable, JD Edwards EnterpriseOne Accounts Payable, and JD Edwards EnterpriseOne General Accounting systems.
Setting Up Cash Type Rules for Accounts Receivable and Accounts Payable
Access the Revise Cash Type Rule form. Select the A/R or A/P tab.
59
Chapter 7
The fields that appear in the header area of the Revise Cash Type Rule form and on the A/R and A/P tabs are the same.
60
Chapter 7
unexpected events, you can increase the amount by a certain percent. For example, enter 1.10 in this field to increase the amount of open vouchers by 10 percent. The default value is 1 (no weight factor). Node Currency Enter the common currency in which to revalue amounts from multiple detail records. If you leave this field blank, the system uses the currency assigned to company 00000.
Note. For the Base Currency, Payment Instrument, and Originating Module fields, you can enter * to include all values. If you leave any of these three fields blank, the system selects only detail records with blanks to create cash forecast data for the cash type rule. Original Module For accounts receivable, enter a system code of 0, 1, 2, 3, or 4 from UDC table 03B/OS in this field. For accounts payable, enter a software module code of P, R, C, M, or L in this field. The Originating Module fields for AR and AP have different aliases (OMOD and RP3, respectively). Days Past Due - From Enter the beginning number of days prior to the date on which you refresh your cash forecast data. This number is used to select a net due date range so that you can include certain past due amounts for cash forecasting. For example, you can enter 1 in this field and 7 in the Days Past Due - To field to review cash forecast amounts that are up to one week past due. Enter the ending number of days prior to the date on which you refresh your cash forecast data. This number is used to select a net due date range so that you can include certain past due amounts for cash forecasting. For example, you can enter 7 in this field and 1 in the Days Past Due - From field to view cash forecast amounts that are up to one week past due.
61
Chapter 7
Show Past Due Amount in First Date Column or Show Past Due Amount in Past Due Column
Select one of these options only if this is a past due cash type. These options designate the column in which you want past due amounts for this cash type rule to appear on the Cash Forecast Analysis form. If selected, past due amounts appear in the first date period column. If not selected, past due amounts appear in a separate past due column.
Header Fields
G/L (general ledger) Cash Type Select this option under the Data Source heading. If you enter a cash type that is specifically for a heading (a code with the Special Handling field equal to 10 in UDC table 09/CT), the system issues an error message. You do not set up rules for headings.
Beginning Subsidiary
62
Chapter 7
Enter the ending object account in a range of accounts. The ending object account is combined with the ending subsidiary account to specify a bank account. The ending object account must be greater than or equal to the beginning object account. Enter the ending subsidiary account in a range of accounts. The ending subsidiary is combined with the ending object account to specify a bank account. The ending subsidiary account must be greater than or equal to the beginning subsidiary account.
Ending Subsidiary
Note. To enter values in the Beginning Subsidiary and Ending Subsidiary fields: To enter specific subsidiaries, enter a valid subsidiary in both the Beginning Subsidiary and the Ending Subsidiary fields. For example, 1110.BEAR - 1110.FIB include only the subsidiaries BEAR through FIB. To include all subsidiaries as of a specific beginning subsidiary, enter a valid subsidiary in the Beginning Subsidiary field and * in the Ending Subsidiary field. For example, 1110.BEAR - 1110.* include all subsidiaries beginning with BEAR. To include all subsidiaries through a specific subsidiary, enter * in the Beginning Subsidiary field and a valid subsidiary in the Ending Subsidiary field. For example, 1110.*- 1.1110.FIB include all subsidiaries through FIB. To include every subsidiary within an object account, enter * in both the Beginning Subsidiary and Ending Subsidiary fields. For example, 1110.* - 1110.* include all subsidiaries for object account 1110.
63
Chapter 7
Each row in the tree structure corresponds to a heading or detail cash type code in UDC table 09/CT, and each cash type code that is not a heading has a cash type rule associated with it. You can add and move cash type codes within the tree structure to define your reporting structure. You can define multiple reporting structures. Detail cash type codes, which show detail row descriptions such as Checking Accounts, appear under the cash type code in the tree structure. When you expand the tree structure, account data that is selected for the detail cash type code appears under the detail row description. The amounts from detail rows roll up into heading rows. For example, amounts from the detail row Checking Accounts might roll up into the heading Opening Balances. If you add or move a cash type code to a place within the parent/child tree structure that is not allowed, the system issues a detailed error message. If you revise a cash type rule associated with a detail cash type code, the system issues a warning that the revision will affect all reporting structures that use the rule.
Prerequisites
Before you complete the tasks in this section: Set up detail cash type codes and, optionally, heading cash type codes in UDC table 09/CT. Set up cash type rules for detail cash type codes. Set the processing option for the Cash Forecast Report Structures Setup program to include standard report sections.
FormID
Navigation Cash Forecasting (G09319), Cash Forecast Rp Structures Setup On Work with Cash Forecast Reporting Structures, click Add. On Revise Cash Forecast Reporting Structure, click OK.
Usage Review a list of reporting structures. Enter the report structure and its description. Define the structure of the report.
W09523C
W09523A
Setting Processing Options for the Cash Forecast Report Structures Setup Program (P09523)
Use this processing option to specify whether to include reports headings as the default in the cash forecasting reporting structure.
Default Tab
1. Standard Report Sections Specify whether the system includes these report headings from UDC table 09/CT in the cash forecast reporting structure: Cash Forecast (1_TOTCF) Opening Balances (1_BAL) Net Operating Forecast (1_NETOP)
64
Chapter 7
Incoming Cash (1_IN) Outgoing Cash (1_OUT) Values are: Blank or 0: Omit report headings. 1: Add report headings. You can add detail cash type codes to these headings when you define your cash forecast reporting structure.
To define a cash forecast report structure: 1. On Revise Reporting Structure Name, enter a name that uniquely identifies the hierarchical reporting structure. The reporting structure specifies how the system displays data for cash forecasting and must exist in the F09523 table. 2. Expand the tree structure. If you set the processing option to include standard report selections, the system displays the cash type codes for headings (UDC table 09/CT) in hierarchical order. 3. To add a detail cash type code to the existing report structure, select the node where you want the code to exist and click Add Node.
65
Chapter 7
For example, to add the cash type code for Open Invoices by Check to the heading code for Incoming Cash, select Incoming Cash. 4. On Select Cash Type UDC, select one of these options and click Find: Detail Heading 5. In the detail area, scroll down, if necessary, and select the row that corresponds to the code that you want to add. 6. Click OK to update the database. 7. To move (cut and paste) a node, select the node and click Cut (scissors button). 8. Select the node where you want to place the node from the previous step and click Paste. 9. Expand the tree structure to view the node that you moved and its children. 10. Click Save to update the database. 11. On Revise Cash Forecast Reporting Structure, continue to add, delete, or move nodes until your structure is complete. If you add or move a cash type code to a place within the parent/child tree structure that is not allowed, the system issues an error message. 12. To review or revise cash type rules without exiting the form, continue to step 13; otherwise, click Cancel. Important! After you click Cancel to exit the Revise Cash Forecast Reporting Structure form, a window appears with the message Do you wish to automatically be connected to cash type rules to validate the changes made within this reporting structure? Click Yes to validate the cash type rules that you specified in the reporting structure and to ensure that no overlapping account ranges or values exist. You cannot verify that account ranges and values are valid when you add cash type rules. Instead, you must validate the rules when you create or revise a reporting structure. If the ranges and values are not correct, the cash forecast data that displays in the analysis could produce incorrect results. 13. To review or revise a cash type rule, complete these steps: To revise a cash type rule without exiting the program, complete steps 1415. To review multiple cash type rules within a reporting structure, complete steps 1617. To revise multiple cash type rules within a reporting structure, complete steps 1619. 14. On Revise Cash Forecast Reporting Structure, select a detail cash type and then choose Cash Type Rule from the Row menu. 15. On Revise Cash Type Rule, change the fields as necessary and click OK. 16. On Revise Cash Forecast Reporting Structure, select Rules for Rpt Struc from the Form menu. 17. On Revise Reporting Structure Cash Type Rules, select the Data Source option for one of these groups of cash types and click Find: All A/R A/P
66
Chapter 7
G/L Use the Revise Reporting Structure Cash Type Rules form to review multiple cash type rules for a group within a reporting structure and to verify that the rules do not have overlapping general ledger accounts, that the bank account numbers are accurate, and so on. 18. To revise multiple cash type codes for a group within a specific reporting structure, enter a new value in the query-by-example (QBE) row and click OK. 19. On the Message form, click OK to accept the revision. Important! If you change criteria for a cash type rule in this reporting structure, the criteria is changed for all reporting structures that use this cash type rule.
67
Chapter 7
68
CHAPTER 8
69
Chapter 8
An overview of the major sources of cash flow for your business. An assessment of the current liquidity of your business. A way in which to estimate future cash flow, based on historical changes. Information about cash flows generated from trading, as well as other financial activities. You can use cash flow statements to analyze your cash flow and produce reports by fiscal period over one or more bank accounts for a company.
30 40 50 60 70
Cash Generated from Operations Cash Flow from Operating Activities Cash Flow from Investing Activities Cash Flow from Financing Activities Cash and Cash Equivalents
The activity code description does not print on the cash flow report; it is informational only. You can change the description of an activity code, but you cannot change its purpose. For example, you can change the description for activity code 10 from Net Income Before Tax to Net Profit/Loss, but you cannot change how the activity code is used on the cash flow report. You assign accounts to an activity code on the Statement of Cash Flow Activity form. The activity code and description appear in the header area of the form so that you can easily keep track of which activity you are assigning accounts to.
70
Chapter 8
71
Chapter 8
FormID
Navigation Statement of Cash Flow (G1031), Statement of Cash Flow Rules On the Work With Statement of Cash Flow Rules form, click Add. On the Statement of Cash Flows Activity form, click the Select Accounts link in the Account Selection field.
Usage Review a list of cash flow activity codes. Set up cash flow rules.
W10520D
W10520E
This task describes how to set up cash flow rules for activity code 10 and for activity codes 2070. The fields that appear on the Statement of Cash Flows Activity form are different for activity code 10.
Activity Code 10
Enter 10 in the Cash Flow Activity field.
FS AAI Description
Enter the AAI item FSxx for Net Income Before Taxes for the company. Enter a description, if applicable. This description prints on the cash flow statement. The default value is the description from the AAI item entered in the previous step. If you override the
72
Chapter 8
description, the system updates the F10520 table and prints the description on the cash flow statement only.
For activity code 20 and the row for depreciation, enter the accounts for accumulated depreciation, and not the accounts for depreciation expense. Accumulated depreciation is a credit account. Amounts for this account are reversed and are added to the Net Income Before Tax line. You can enter multiple lines, descriptions, and accounts for activity codes 2070. Description Normal Balance Enter the description that you want to print as one line on the cash flow statement. Enter C or D in this field to specify whether the normal balance for the account on this line is a credit or debit. These values are hard-coded in UDC table 10/NB. Click the Select Accounts link to access the Statement of Cash Flows Account Selection form and assign a range of object and subsidiary accounts.
Account Selection
73
Chapter 8
Enter an account in the From Object Account field. To designate all subsidiaries for the object account, enter * in the From Subsidiary Account field. If you leave this field blank, the system uses the first blank subsidiary associated with the "from" object account or the range of accounts. The values in these fields must be equal to or greater than the values in the From Object Account and From Subsidiary Account fields. Accounts that overlap from one line to the next line are not allowed. The system issues the error message Invalid From and Thru values.
74
CHAPTER 9
75
Chapter 9
FormID
Navigation Cash Basis Accounting (G09314), Valid Document Types or Document Types to be Excluded
Usage Verify that the document types that you want to include for cash basis entries appear in UDC table 00/DT. Verify that the document types that you want to exclude from cash basis entries appear in UDC table 00/DX.
W0004A1
Add a document type to include with cash basis entries in UDC table 00/DT and add a document type to exclude from cash basis entries in UDC table 00/DX.
76
Chapter 9
Debit memos (RM) Adjustments (RA) Recurring documents (PR and RR) Finance charges (RF) Accrued property taxes (JT) Depreciation entries (DP) Ensure that any custom document types are analyzed for exclusion of cash basis entries. Do not exclude document types that represent the void for accounts payable payments (PO) or accounts receivable receipts (RO).
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Automatic Accounting Instructions, Setting Up AAIs
77
Chapter 9
If you enter unapplied receipts, you must set up an AAI item for the suspense revenue account. To retrieve the suspense revenue account for unapplied receipts, the system uses one of these AAI items based on the hierarchy indicated: CByyyy. The system first searches for CByyyy (where yyyy is the general ledger offset from the unapplied receipt). You can enter the general ledger offset when you enter the receipt or, by setting a processing option, allow the value to be supplied from the customer master record. CBUC. If CByyyy is not set up or if you do not use a general ledger offset, the system then searches for CBUC. The system supplies UC as the default value for the G/L Offset field when you enter unapplied receipts without an offset. RCyyyy. If the system cannot locate CBUC, the system next searches for RCyyyy (where yyyy is the general ledger offset entered on the receipt). RCUC. If RCyyyy is not set up or if you do not use a general ledger offset, the system finally searches for RCUC. The system supplies UC as the default value for the G/L Offset field in which you enter unapplied receipts without an offset. If the system cannot locate RCUC, it issues an error. Note. If you use the Real Estate Management system, the Unapplied Bill Code field (GLC) is the same as the G/L Offset field that is used in the standard, speed, and draft entry programs. The system searches for CByyyy (where yyyy is the unapplied bill code).
78
CHAPTER 10
79
Chapter 10
FormID
Navigation 52 Period Accounting (G09313), Set 52 Period Dates On Work With 52 Periods: Click Add. Select Print 52 Periods from the Reports menu.
Usage Review a list of 52 period fiscal date patterns. Set up a fiscal date pattern. Print a report of the fiscal date patterns that you have set up
Set Up 52 Periods
W0008BF
FormID
Navigation Organization & Account Setup (G09411), Company Names & Numbers Select a company on the Work With Companies form.
Company Setup
W0010B
80
Chapter 10
52 Period Accounting
Select the 52 Period Accounting tab. 52 Period Normal Number of Periods 52 Period Financial Reporting Period Enter the actual number of accounting periods, not including adjustment periods. Enter a period number to specify a 52-period financial reporting date. This reporting period is used by several EnterpriseOne financial reports. The period number is not the same as the current period that you specify as the accounting period for a company. 52 Period Financial Reporting Year Enter the year in which financial statements are to be prepared. Note. A fiscal year spanning 20062007 would be expressed as 06.
Prerequisite
Post transactions to the F0902 table, Set the processing option in the General Ledger Post program (R09801) to submit the post for 52 periods. The system updates the F0902 and F0902B tables. See JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Posting Financial Transactions, Posting Financial Batches.
81
Chapter 10
82
CHAPTER 11
83
Chapter 11
If you have the general accounting constants set to require management approval, the system creates the batch record in a pending status. You must approve the batch before you can post it. When you approve batches that are in a pending status, the system updates the batch status only on the batch control record. 3. Post journal entries. When you post journal entries, the system updates the status on the batch control record to D (posted), generates records in the F0902 table, and updates the posted status on the journal entries in the F0911 table to P (posted).
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Using Batch Control to Manage the Entry Process
84
Chapter 11
85
Chapter 11
Allocate amounts to different accounts in your general ledger based on the percentage that is entered for each transaction item. Model journal entries. Reduce data entry time by creating a set of templates for frequently used journal entries. You can enter journal entries for the various ledgers that you have set up for budgets, statistical information, units, and so on. The system uses ledger type codes to separate balance amounts and units for each ledger. These are some examples of ledger type codes and their corresponding ledgers: AA: Actual amounts BA: Budget amounts AU: Actual units BU: Budget units You can also enter journal entries to record a taxable entry, such as value-added tax (VAT) or similar taxes, and journal entries with foreign currencies. The system provides a processing option for a debit and credit format, as well as a separate menu selection for that format. The debit and credit format allows you to enter an amount into a debit or a credit field. In this format, you do not need to include the minus sign for credit amounts.
See Also
JD Edwards EnterpriseOne Tax Processing 8.12 Implementation Guide, Entering Tax Information on Orders and Transactions, Entering Journal Entries with VAT
86
Chapter 11
The system replaces each separator character with the missing part of the account number by copying the same part from the preceding account number. To duplicate account number segments, enter a separator character in the account number field for each segment (business unit, object account, and subsidiary account) that you want to duplicate for each subsequent line in your journal entry. For example, if you entered 9.8720 for the account number in the first line of a journal entry and you want to duplicate the business unit for the second line, enter .8730 and the system completes the account number field with 9.8730.
Using Speed Account Entry for Journal Entries for Work Orders
When you enter journal entries for work orders, you can use speed account entry to save time and reduce entry errors. In the Account Number field, you enter \ (backslash), the work order number, a period, and the object account number. The system locates the business unit for the work order and: Replaces the work order number with the business unit. The object account number remains in the Account Number field. Updates the Subledger field with the work order number. Updates the Subledger Type field with W. Updates the Subsidiary field with the cost code from the work order. Updates the Phase field with the phase from the work order. Updates the Asset Number field with the equipment number from the work order.
87
Chapter 11
Note. You cannot enter a header account as an invalid account. Header accounts are typically used for summary purposes during financial reporting and do not allow amounts to be posted to them. If you need to create a header account, use the Copy Accts to Business Units program (P09804) to copy the nonposting header accounts from the model business unit. You can also enter the account manually and assign it a posting code N on the Revise Single Account form.
FormID
Usage Review summarized journal entries by document number. To review all journal entries in a batch, use the General Journal Review program (P0011). Add and revise journal entries.
Journal Entry
W0911A
On Work With Journal Entries, click Add. If you are using batch control, the Batch Control form appears. On the Batch Control form, enter the date and expected totals and continue to the next form.
Defaults
1. Batch Type Specify the system and type of entries for the batch. Examples of batch types include: G: General ledger entries. V: Vouchers. IB: Invoices. If you leave this processing option blank, the system processes all batch types.
Display
1. Debit/Credit Format Specify whether to display journal entries in a debit and credit format.
Versions
1. Journal Entry MBF Version (P0900049) Specify whether to override the journal entry MBF version for journal entry processing. You must specify a valid version for P0900049. If you leave this processing option blank, the system uses version ZJDE0001. This processing option should be changed only by personnel responsible for your system setup.
88
Chapter 11
Edits
1. Fixed Asset ID Specify whether to require an Asset ID if an account is in the AAI account range for assets. Values are: Blank: Do not require an asset ID in the journal entry. 1: Require an Asset ID in the journal entry.
Setting Processing Options for Journal Entry Master Business Function (P0900049)
The master business function (MBF) provides a central location for standard business rules about entering documents such as journal entries, vouchers, and invoices. The master business function is composed of processing options that are shared by certain programs. The processing options for the Journal Entry MBF are used by these journal entry programs: Journal Entries (P0911). Journal Entries with VAT (P09106). Journal Entry Batch Processor (R09110Z). Store and Forward JE Batch Processor (R09110ZS). Recurring Journal Entry Compute & Print (R09302). Indexed Comps Compute And Print Report (R093021). Variable Numerator Compute and Print (R093022). Each program that uses the Journal Entry MBF must specify which version of the MBF is used. If no version is specified, the system uses version ZJDE0001.
Defaults
1. Ledger Type Specify the ledger type from UDC table 09/LT to use as the default value.
Currency
1. Effective Date Specify whether to edit the exchange rate effective date against the general ledger period of the transaction. The effective date is used to calculate currency amounts. Values are: Blank: Do not compare the exchange rate effective date to the general ledger period of the transaction. 1: Compare the exchange rate effective date to the general ledger period of the transaction. 2. Tolerance Specify a tolerance limit that triggers a warning if you enter a currency exchange rate that is over or under the limit. For example, 15.00 indicates over or under 15.00 percent.
89
Chapter 11
Zero Amounts
1. Zero Amounts Specify whether to create journal entry line items with zero amounts and no units. This might be useful when creating journal entries from models. Values are: Blank: Create journal entry line items with zero amounts and no units. 1: Do not create journal entry line items with zero amounts and no units. 2. Audit Information Specify whether to bypass updating the audit information when a change is made to a posted account ledger. Blank: Update audit information. 1: Do not update audit information.
Interop
1. Interoperability Version Specify a version of F0911 Interoperability Processing Options (P0900160). If you specify a version, outbound records will be written. If you leave this processing option blank, ZJDE0001 will be used.
You can enter thousands of transaction lines on the Journal Entry form. To review the transactions, use the Page Up and Page Down keys to load one page of transactions at a time. This has minimal impact on processing time.
Header Area
These fields in the header area are required: Explanation Enter a description for the journal entry.
90
Chapter 11
Enter the general ledger date for the journal entry. If you leave this field blank, the system uses todays date.
Detail Area
These fields in the detail area are required for each general ledger account to which amounts will be distributed: Account Number Enter the general ledger account number. The system validates it against the chart of accounts in the F0901 table and fills in the account description. The system uses the business unit in the account number on the first line of the detail area to fill in other information in the header area, such as document company and base currency code. The first line of the journal entry provides the default base currency code for the entry. Therefore, you cannot delete the first line of the entry. You can, however, change the account number as long as the new account resides in the same company as that of the original account. Amount Enter the number that identifies the amount that the system will add to the account balance of the associated account number. Enter credits with (minus sign) either before or after the amount.
91
Chapter 11
For performance reasons, the paper clip button does not subsequently appear on the Journal entry form unless you click the Attachments button in the far left column of the row heading. The system displays a paper clip button to the left of the journal entry: On the Work With Journal Entries form, when you add text or another attachment to the entire journal entry. On the Journal Entry form, when you add text or another attachment to a specific transaction.
92
Chapter 11
The total debit percentages for balanced journal entries must equal the total credit percentages. The total debit or credit percentages do not have to equal 100 percent. Document Type Percent Leave this field blank for the system to assign JE (journal entry). This code is from UDC table 00/DT. Select the Percent check box to distribute the total amount of a journal entry among accounts based on percentages. The system displays the Distributed Amount field in the header area and the % field in the detail area. Distributed Amount Enter the total amount of the journal entry in this field. For percent journal entries, the system calculates the detailed amounts to distribute based-on percentages entered in the % fields. Enter the percentage of the total amount that the system should distribute to the account number. The system does not assume decimal places in the number that you enter. If you want to specify a percentage that includes a decimal, you must enter the decimal. For example, enter 12 for 12 percent, and enter 42.5 for 42.5 percent.
93
Chapter 11
Delete and re-enter the journal entry. Copy the journal entry and change the fields on the new journal entry before you click OK. Then delete the incorrect journal entry.
94
Chapter 11
This section discusses how to: Enter a reversing entry. Review a reversing journal entry. Change a posted journal entry to a reversing entry.
95
Chapter 11
96
Chapter 11
Document Type
For a model journal entry, leave this field blank for the system to assign JE To enter a percent model journal entry, enter %. The system displays the % field in the detail area of the form. See Chapter 11, Processing Journal Entries, Entering a Percent Journal Entry, page 92.
97
Chapter 11
See Also
Chapter 34, Maintaining Batch Headers, Adding and Revising Batch Headers, page 402
FormID
Navigation Journal Entry, Reports, & Inquiries (G0911), General Journal Review On the Work With Batches form, select the batch that you want to review and click Select.
Usage Review, approve, and post journal entries in a batch. Review a journal entry. You can also delete an unposted journal entry or void a posted journal entry.
W0911BA
98
Chapter 11
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Posting Financial Transactions
99
Chapter 11
No
Yes
Print
1. Account Format 2. Print Error Messages Specify the account format that you want to print on the General Ledger Post report. Specify whether to print error messages on the General Ledger Post report. If you leave this processing option blank and an error is detected, the error message still appears in the work center. Values are: Blank: Do not print error messages. 1: Print error messages.
Versions
1. Detail Currency Restatement Version Specify the version of the Detailed Currency Restatement program (R11411) that you want to run to create entries. If you leave this field blank, the program does not run and detailed currency restatement entries are not created.
100
Chapter 11
Specify the version of the Fixed Asset Post program (R12800) that you want the system to run to create fixed asset entries. If you leave this field blank, the program does not run and fixed asset entries are not created. Specify the version of the 52 Period Accounting Post program (R098011) to use to update the F0902 table and the Account Balances - 52 Period Accounting table (F0902B). If you leave this processing option blank, the program does not run and tables are not updated.
Edits
1. Update Transaction Specify whether to update the account ID, company, fiscal year, period number, century, and fiscal quarter on unposted records in the F0911 table. You might need to update these fields if you have records in the F0911 table that were created by a custom program and do not contain the correct values. The system uses the value in the G/L Account Number field of the unposted record in the F0911 table to update the Account ID and Company fields. The system calculates the correct values for the Fiscal Year, Period Number, and Century fields using the value in the G/L Date field of the unposted record in the F0911 table. The system will update the Fiscal Quarter field on the unposted record in the F0911 table to blank.
Taxes
1. Update Tax File Specify whether and how to update the Taxes table (F0018) when you post transactions with tax information to the general ledger. Values are: Blank: Do not update the F0018 table. 1: Update the F0018 table for these tax explanation codes only: V, VT, V+, U, and UT. 2: Update the F0018 table for all tax amounts. The system does not update the F0018 table for transactions with tax explanation code E (exempt). 3: Update the F0018 table for all tax explanation codes including E (exempt). 2. Update VAT Discounts Specify whether to adjust the tax amount fields, which fields to adjust, and when discounts are taken. The system adjusts the tax amount fields only for transactions with tax explanation code V. To use this processing option, tax rules must be set up for tax on gross including discount and discount on gross including tax. Values are: Blank: Do not adjust tax amounts for discounts taken. 1: Update only the Tax Amount field (STAM). 2: Update the STAM (tax amount), ATXA (taxable amount), and AEXP (extended price) fields. The system uses these algorithms to calculate the adjustment amounts to the tax, taxable, and gross (extended price) amount fields for discounts taken: Adjustment to the gross amount (extended price) = discount taken
101
Chapter 11
Adjustment to the taxable amount = (taxable amount / gross amount) x discount taken Adjustment to the tax amount = (tax amount / gross amount) x discount taken For example: Tax rate = 25 percent Discount taken = 12.50 USD Gross amount (extended price) = 1,250.00 USD Taxable amount = 1,000.00 USD Tax amount = 250.00 USD Based on the example, using the adjustment algorithms, the system calculates these adjustment amounts: Adjustment to the gross amount = 12.50 Adjustment to the taxable amount = 10.00 Adjustment to the tax amount = 2.50 To calculate the adjustments, the system subtracts the adjusted amount from the original amount: Adjusted gross amount: 1,250.0012.50 = 1,237.50 Adjusted Taxable Amount: 1,000.0010.00 = 990.00 Adjusted Tax Amount: 250.002.50 = 247.50 3. Update VAT Receipts and W/O Specify whether to adjust the tax fields, which fields to adjust, and when the receipt has a write-off. The system adjusts the tax amount fields only for transactions with tax explanation code V. Values are: Blank: Do not adjust tax amounts for write-offs. 1: Updates the STAM field only. 2: Updates the STAM, ATXA, and AEXP amount fields. The system uses these algorithms to calculate the adjustment amounts to the tax, taxable, and gross (extended price) amount fields for write-off amounts: Adjustment to the gross amount (extended price) = write-off amount Adjustment to the taxable amount = (taxable amount / gross amount) x write-off amount Adjustment to the tax amount = (tax amount / gross amount) x write-off amount For example: Tax rate = 25 percent Write-off amount = 12.50 USD Gross amount (extended price) = 1,250.00 USD Taxable amount = 1,000.00 USD Tax amount = 250.00 USD Based on the example, using the adjustment algorithms, the system calculates these adjustment amounts:
102
Chapter 11
Adjustment to the gross amount = 12.50 Adjustment to the taxable amount = 10.00 Adjustment to the tax amount = 2.50 To calculate the adjustments, the system subtracts the adjusted amount from the original amount: Adjusted gross amount: 1,250.0012.50 = 1,237.50 Adjusted taxable amount: 1,000.0010.00 = 990.00 Adjusted Tax Amount: 250.002.50 = 247.50
Process
1. Explode parent item time Specify whether the system explodes the time entries for a parent asset down to the children of the parent asset. This processing option applies only to batch type T entries. Values are: Blank: Do not explode the time entries for a parent asset. 1: Explode the time entries for a parent asset. The General Ledger Post program creates time entries for the parent assets children. The system uses the unit of time from the parent asset entries and the rates from the child asset to calculate the appropriate entries.
Cash Basis
1. Units Ledger Type Specify the units ledger type for the system to use for cash basis entries. You must enter a valid ledger type from the UDC table 09/LT. If you leave this processing option blank, the system uses the default ledger type ZU. Specify which version of the Create Cash Basis Entries program (R11C850) to run. The system runs the Create Cash Basis Entries program after the post program finishes. If you leave this processing option, the program does not run and cash basis entries are not created.
103
Chapter 11
104
Chapter 11
FormID
Navigation Journal Entry, Reports, & Inquiries (G0911), Journal Entry On Work With Journal Entries, select the journal entry that you want to revise. On Work With Journal Entries, select the journal entry that you want to void and then select Void from the Row menu. Alternatively, you can void posted journal entries on the General Journal Review form. Voiding on this form is similar to voiding on the Work With Journal Entries form.
Usage Review summarized journal entries by document number. Revise journal entries.
Journal Entry
W0911A
W0911F
105
Chapter 11
106
CHAPTER 12
107
Chapter 12
Errors in Processing
If any errors occur during processing, they appear on the edit report. You can correct the errors and reprocess the batch. If one or more transactions in the batch are in error, the error does not stop the batch from processing. If a transaction in the batch is in error, that transaction is not processed with the rest of the batch. After the batch has been successfully processed, the system updates the value in the VNEDSP field from 0 to 1. These records remain in the F0911Z1 table until they are purged. Alternatively, you can set a processing option to purge this table automatically.
108
Chapter 12
These tips might help you to reduce the number of error messages or identify and resolve them when they occur: Initially process a small number of records in a batch. Most errors that occur on one record also occur on all records. Correct the errors on the smaller number of records and then follow the same sequence of steps when you process a larger number of records in a batch. Remember that only errors prevent a batch from processing. Warning messages alert you to nonstandard entries but do not prevent processing. You control whether you receive warning messages with a processing option. Remember that you might not need to run the batch in proof mode because you have the option to review and delete transactions before you post them. Additionally, any error prevents the batch from processing. Review error messages to help you identify the cause and the resolution of errors. If errors exist that you cannot resolve, enter a transaction manually using the Journal Entry- Revision program (P0911Z1) and process it successfully. Then compare the F0911Z1 transaction that you converted to the F0911Z1 transaction that you entered through the Journal Entry Revisions program (P0911Z1). Comparing the differences assists you in locating discrepancies and resolving the errors.
Version
1. Journal Entry Version Specify a version of Journal Entry MBF Processing Options (P0900049). If you leave this processing option blank, the system runs the standard version (ZJDExxxxx). If the system runs the standard version, it posts all approved G type batches, not just the batches that were created by the Journal Entries Batch Processor program. This is because data selection is set up to select Batch Type G and Batch Status A. You can create a new version of the post program that includes additional data selection (for example, user ID, batch date, and so on), but this may not ensure the results you want. 2. Post Version Specify a version of the General Ledger Post program (R09801) to use to automatically post to the F0902 table. If you leave this processing option blank, the post will not be submitted.
Process
1. Process Mode Specify whether to process the batch in proof or final mode. Values are: Blank: Proof mode. 1: Final mode.
109
Chapter 12
2. Out of Balance
Specify whether to allow general ledger transactions that are out of balance to process. (Amounts do not net to zero.) Values are: Blank: Do not allow out-of-balance transactions to process. 1: Allow out-of-balance transactions to process.
3. Purge
Specify whether to automatically purge processed transactions from the F0911Z1 table. Values are: Blank: Processed transactions are marked as processed, but are not purged. 1: Processed transactions are automatically purged.
Messages
1. Warning Message Specify whether to suppress the creation of warning messages in the work center. Values are: Blank: Create warning messages. 1: Do not create warning messages. 2. Electronic Message Specify a user to receive electronic messages. If you leave this processing option blank, the user who entered the transactions receives the message in the work center.
Edits
1. Batch Approval Specify whether to update the status on all batches created to a status of approved. Values are: Blank: Update the batch status according to the general accounting constants. 1: Update all batches to a status of approved.
110
Chapter 12
You can revise unprocessed records, such as records that ended in error, but it is recommended that you make the revisions in your spreadsheet instead because the Journal Entry Revisions program does not perform the same edits as the Journal Entry program (P0911). Delete unprocessed batch journal entries. After you add journal entries or revise unprocessed journal entries on the Journal Entry Revision program, you must run the Journal Entries Batch Processor program again. Note. You cannot use the Journal Entry Revisions program to revise successfully processed records. You must use the Journal Entry program to revise them because they have been processed in the F0911 table. You cannot use the Journal Entry Revisions program to delete successfully processed batch journal entries. Instead, you must purge them using the Purge Batch Journal Entries program (R0911Z1P).
Journal Entry
W0911A
Entry Type
1. Entry Type Specify whether the system writes control records to the F0041Z1 table for store-and-forward transactions. Values are: Blank: Write transaction control records. 1: Do not write transaction control records.
111
Chapter 12
112
CHAPTER 13
113
Chapter 13
You must download each table separately. You can use data selection or category codes to limit the information that the system downloads from each table. Each version of the Master Table Download program (P00140) represents a table and its associated tables or a group of tables. Each table is associated with one version. Not all versions must be present for all tables. You can create new versions for these tables in the Store & Forward Journal Entry - Revision program (P0911Z1). The business data tables must reside on the local machine that you use for store-and-forward processing of journal entries: F0004 - User-Defined Code Types F0005 - User-Defined Codes F0006 - Business Unit Master F0008 - Date Fiscal Patterns F0009 - General Constants F0010 - Company Constants F0013 - Currency Codes F0014 - Payment Terms F0022 - Tax Rules F0041Z1 - Transaction Control File F0101 - Address Book Master F0111 - Address Book - Whos Who F0116 - Address by Date F0901 - Account Master F0907 - Chart of Accounts Format F0911Z1 - Journal Entry Transactions - Batch File F4008 - Tax Areas F4801 - Work Order Master File In addition to the business data tables, you must also download the technical data tables, such as Next Numbers - Automatic (F0002) and Next Numbers by Company/Fiscal Year - Automatic (F00021). The system creates a download report for each table that you download. Use this report to verify the number of records that the system downloads to your PC. After you download the master tables, you can enter your transactions using the store-and-forward process.
Prerequisites
Before you complete the tasks in this section: Download the necessary master tables. Verify that you are connected to the server and signed on to your normal production environment.
114
Chapter 13
W0911Z1A
115
Chapter 13
116
Chapter 13
The program that you use to process store-and-forward journal entries is different from the program that you use to process batch journal entries, although the results are similar. Verify that you are using the batch processor for store-and-forward journal entries. After you process the journal entries, you must update the transaction control status of the journal entries on the PC to match the status of those on the server.
Setting Processing Options for the Store & Forward JE Batch Processor (R09110ZS)
Processing options enable you to specify the default processing for programs and reports.
Version Tab
1. Journal Entry Version 2. Post Version Specify a version of Journal Entry MBF Processing Options (P0900049). If you leave this processing option blank, the standard version is run. Specify a version of the General Ledger Post program (R09801) to use to automatically post journal entries to the F0902 table. If you specify a version of the General Ledger Post program, the version must exist on the server. If you leave this processing option blank, the post is not submitted.
Process Tab
1. Process Mode Specify whether to process the batch in proof or final mode. Values are: Blank: Proof mode. Tables are not updated. 1: Final mode. Tables are updated. 2. Out of Balance Specify whether to allow general ledger transactions that are out of balance (amounts do not net to zero) to process. Values are: Blank: Do not allow out-of-balance transactions to process. 1: Allow out-of-balance transactions to process. 3. Purge Specify whether to automatically purge processed transactions from the batch file. Values are: Blank: Do not purge processed transactions. 1: Purge processed transactions.
Messages Tab
1. Warning Message Specify whether to suppress the creation of warning messages in the work center. Values are: Blank: Do not suppress warning messages 1: Suppress warning messages. 2. Electronic Message Specify a user to receive electronic messages in the work center. Values are:
117
Chapter 13
Blank: The user who entered the transactions receives the messages. User ID: The user specified receives the messages.
Edits Tab
1. Batch Approval Specify whether to have the status on all batches set to approved. Values are: Blank: The system sets all batch statuses according to the General Accounting constants. 1: The system sets all batch status to approved.
118
CHAPTER 14
Processing Allocations
This chapter provides overviews of allocations, the process for creating allocations, and multitiered allocations and discusses how to: Process recurring journal entries. Process indexed allocations. Process variable numerator allocations.
Understanding Allocations
Allocations can serve many purposes, such as distributing expenses, creating annual or periodic budgets, and calculating currency conversions. Use allocations to redistribute amounts from one or more business units to accounts in other business units, or from one ledger type to another. You can create model journal entries to work as allocations, regardless of whether the amounts change, or create recurring journal entries if the amounts never change. The JD Edwards EnterpriseOne General Accounting system provides three types of allocations: Recurring journal entries Create a recurring journal entry when you have an entry that recurs on a regular basis. Indexed allocations Create an indexed allocation when you want to allocate amounts from one company or business unit to another or create annual or monthly budgets. Variable numerator allocations Create a variable numerator allocation when you want to allocate amounts from one business unit to other business units with a common category code value and to base an allocation on a variable, such as head count. These frequency intervals can be used with all three types of allocations: Weekly Monthly Quarterly Semiannually Annually
119
Processing Allocations
Chapter 14
You can create reversing journal entries for accrual accounting or year-to-date performance calculations for all allocations. Companies often reverse allocations to create estimated distributions that will be reversed on the first day of the next period. When you reverse an allocation and process it in final mode, the system reverses the journal entry that was created initially. When you post the allocation journal entry, the system creates the reversing journal entry on the first day of the next accounting period. For all three types of allocations, the system uses the original document number of an allocation for the journal entries that are created each time that you run the allocation. Even though the journal entries have the same document number, they are not considered duplicates because each journal entry has a different general ledger date. You can use the document number to follow the audit trail back to the original allocation. When you create allocations, these dates affect the allocation types:
Date General ledger date Special period/year Description The date that determines the accounting period to which the journal entry posts. The date that determines the source balances for the allocation. The system selects amounts from the F0902 table based on this date if the based-on period or year is different from the current period or year. The date when the allocation becomes ineligible for processing by the computations programs.
Stop date
120
Chapter 14
Processing Allocations
Specify calculations
Compute
Review allocations
121
Processing Allocations
Chapter 14
For example, if the telephone company sends monthly bills to your corporation for all long distance calls, you could set up tiers to allocate the bill to the departments in your regional offices: Tier 1: Regional offices. This tier could identify the rates or percentages to allocate the bill among regions A, B, and C. Tier 2: Departments in Region A. This tier could identify rates or percentages to allocate the bill for region A among departments X, Y, and Z. Leave this field blank for stand-alone allocations. Rate Factor Enter a number that identifies the index or rate for calculations. The system multiplies the from amounts by this factor to calculate the amounts to distribute. You can specify either positive or negative numbers and no more than 8 decimals. If you specify more than eight decimal positions, the system rounds to eight positions. If you specify a large whole number and a large number of decimal positions, the system might not be able to display the entire number. Even though all decimal positions cannot be displayed, they are stored (up to eight) correctly in the table. If you leave this field blank, the default rate factor is 1.00000000. For annual budgets, you can specify zero to remove all balances and start over. Recur Frequency (recurring frequency) Enter a code to specify the time interval between transactions that the system creates. Values are: Blank: Not recurring. This frequency is valid only for annual budget allocations. MO: Monthly. AN: Annually. WK: Weekly. QT: Quarterly. SA: Semiannually. BW: Biweekly. Note. For annual budgets, only blank or AN are valid. Reverse Select this check box for the system to create reversing entries when you post the original transaction. The system uses the first date of the next period for the general ledger date. Enter a number that identifies the general ledger period to use for based-on amounts. If you leave this field blank, the system uses the current period of the company for the based-on amounts. Enter the fiscal year from which the system extracts based-on amounts. If you leave this field blank, the system uses the current fiscal year of the company. Status Code Select the Approved or On Hold check box. The system creates journal entries and updates accounts for approved transactions only.
122
Chapter 14
Processing Allocations
Stop Date
Enter a date that indicates when the allocation becomes inactive. If the general ledger date is less than this date or if you leave this field blank, the allocation is active. If the general ledger date is greater than or equal to this date, the allocation is inactive.
123
Processing Allocations
Chapter 14
When you run the program in proof mode, the system generates a report but does not create journal entries. This report lists the journal entries that the system will create in the F0911 when you run the program in final mode. The report also lists error messages for recurring journal entries that contain errors. Invalid accounts appear with *** on the report. Review the report to determine whether you need to make any changes to the journal entries before running the program in final mode. In final mode, the system creates journal entries in the F0911 table and advances the general ledger date according to the recurring frequency and stop date. The recurring journal entry is ready for future processing. Batch type D is assigned to recurring journal entries. You should create different versions of the Recurring JE Compute & Print program for recurring frequencies, specific companies, and specific document types. This approach enables you to include specific groups of recurring journal entries. After you run this program in final mode, review and post the journal entries.
Prerequisite
Ensure that the date pattern for next year is set up so that the Recurring JE Compute & Print program advances the dates correctly.
FormID
Navigation Allocations (G0923), Recurring JE Computation On the Work With Recurring Journal Entries form, click Add.
Usage Locate and review existing recurring journal entries. Create recurring journal entries.
124
Chapter 14
Processing Allocations
Enter the text that appears in the first of two description lines for each journal entry that the allocation creates. This field is required. Enter a code that indicates how the system is to calculate the allocation journal entries. The system uses this code in conjunction with the values in the Amount field. Values are: &: Fixed amount method. The system allocates the amount that you specify in the Amount field. You can use this method to create recurring journal entries. %: Percentage method. The system uses the percentage that you specify in the Amount field to perform the allocation. U: Unit method. The system creates a percentage from the units that you specify in the Amount field to perform the allocation. It then allocates the amount in the from and through account range according to the percentages. Examples include square feet and number of employees. Note. If you specify the percentage or unit allocation method, the Computations Based On tab is activated. In this case, the currency for the ledger type or account from which the amount will be distributed must be the same as the currency for the ledger type or business unit company on which the computation is based.
Enter the beginning account and ending account in a range of accounts. Only amounts posted to accounts in this range are allocated.
125
Processing Allocations
Chapter 14
Enter a code that controls whether the allocation is based on month-to-date, year-to-date, or final budget amounts. For the percentage and unit methods, this field is required. Values are: M: Month-to-date. The basis is period activity for the month (net monthly posting for the month). Month-to-date allocations do not include prior month corrections in the allocation base, while year-to-date allocations do. Y: Year-to-date for recurring allocations. The basis is the period-end balance. For profit and loss accounts, this is the sum of all net postings for the year. For balance sheet accounts, this is the cumulative (inception-to-date) balance. For accrual recurring allocations, select the Reverse option. B: Final budget. This is also known as original budget in the JD Edwards EnterpriseOne General Accounting and JD Edwards EnterpriseOne Job Cost systems. No journal entries are created. Use only with budget ledger types.
Period
Enter a number that identifies the general ledger period to use for based-on amounts. If you leave this field blank, the system will use the current period of the company for the based-on amounts. Enter a number that identifies the amount that the system will add to the account balance of the associated account number. Enter credits with a minus sign () either before or after the amount. If you use the percentage allocation method, enter the percentage that you want to allocate to a specific account in this field. The percentages do not have to equal 100, but the debits and credits must balance if the option to require ledgers to balance is selected in the Ledger Type Master Setup program (P0025). If you use the unit allocation method, enter the number of units for the account in this field. The amount will be allocated based on a percentage of the number of units of the account over the total number of units.
Amount
126
Chapter 14
Processing Allocations
Thru Date
1. Thru Date Enter the through date in which to include allocations. If you leave this processing option blank, the current date is used.
Mode
1. Process Mode Enter the processing mode. Values are: 1: Proof mode with report. 2: Final mode to create transactions.
127
Processing Allocations
Chapter 14
To create a budget using indexed allocations, use the balance method and complete the budget fields in the detail area of the Allocations - Index Computations form. This graphic shows how you can use indexed allocations to allocate amounts from the AA ledger to the BA ledger to create a budget:
Amount Company 00001 AA Ledger (Actual Amounts) x 1.25 Amount Company 00001 BA Ledger (Budget Amounts)
Business Unit - 1 3 5
Using indexed allocations
Business Unit - 1 3 5
128
Chapter 14
Processing Allocations
Reads balances or transactions, based on the allocation method, from one or more accounts. Multiplies each balance or transaction by the specified rate index. Creates journal entries with batch type D in the F0911 table. For the balance allocation method, the system creates journal entries based on the balance of an account or a range of accounts. For the transaction allocation method, the system creates journal entries in a one-to-one ratio with the transactions that it reads. Calculates an offset to balance the resulting journal entries, if needed, and distributes the offset to a contra/clearing account. Increases the general ledger date incrementally according to the recurring frequency for the allocation, which ensures that the allocation is ready for future processing. For the update allocation method, updates balances only in the F0902 table for ledger types other than AA. Prints the Indexed Computations Journal report. This report lists detailed allocation information and errors, such as invalid accounts and entries posted before cutoff (PBCO). Invalid accounts appear with *** on the report. You should create different versions of the Indexed Computations Compute & Print program for various recurring frequencies and for specific companies and specific document types. This allows you to include specific groups of allocations. After you run this program in final mode, review and post the journal entries.
Prerequisites
Before you complete the tasks in this section: Ensure that the fiscal date pattern for next month or next year is set so that the program correctly increases the dates incrementally. Before you run the program with multitiered calculations, verify that the posting sequence numbers on the Allocations - Index Computations form are correct so that the allocations run in the required order.
FormID
Navigation Allocations (G0923), Indexed Computations On the Work With Indexed Computations form, click Add.
Usage Locate and review existing indexed allocations. Create indexed allocations.
W09121A
129
Processing Allocations
Chapter 14
Company
Enter the company number. The system uses the current period, fiscal year, and general ledger date of the company for calculations and for identifying errors based on the General Ledger Date field. The number in this field does not affect the journal entries created. Enter text that describes the allocation. The text appears in the first of two description lines for each journal entry that the computation creates. This field is required. Enter the account to use for a balancing or offsetting journal entry. This field is required for all ledger types that are required to balance. You must enter the account in the business unit.object.subsidiary format. Leave this field blank for non-balancing ledger types, such as budgets, and use the annual budget fields in the detail area of the Allocations - Index Computations form.
Explanation
Contra/Clearing Account
Enter a code that controls whether the allocation is based on month-to-date or year-to-date amounts. Values are: M: Month-to-date. The basis is period activity for the month (net monthly postings). These do not include prior month corrections in the allocation base. Y: Year-to-date.
130
Chapter 14
Processing Allocations
The basis is the period-end balance. For profit and loss accounts, this is the sum of all net postings for the year. For balance sheet accounts, this is the cumulative (inception-to-date) balance. These include prior month corrections in the allocation base. If you have recurring annual allocations, set them up as automatically reversing entries by selecting the Reverse check box. Balances, Transaction, and Update Select one of these options to specify how the system creates allocation journal entries or updates: Balance Method. Create journal entries based on the balance of an account or the balance of a range of accounts in the F0902 table. For annual budgets, you must use this method; journal entries will not be created. Transaction Method. Create journal entries on a one-for-one basis for each posted transaction in the F0911 table for the account range specified. Update Method. Update the account balance for non-AA ledger types in the F0902 table and do not create any journal entries. From Bus. Unit (from business unit) Enter a specific business unit or *xxxxx (asterisk and the company number) to specify all business units for the company. If you enter *xxxxx, the system uses all business units for that company and bypasses any business unit security that is set up. For example, if you specify an allocation for *00001, the allocation will be for all business units in company 00001. Even if your access is normally restricted to business unit 3, the allocation will bypass business unit security. You cannot enter *00000 to specify all business units in all companies. To Business Unit From Budget Code Enter a specific business unit or * to post to the business unit entered in the From Business Unit field. Enter a value in this field only for annual budgets. Values are: 1: Requested budget amount. 2: Approved budget amount. 3: Final budget amount. Note. These three codes are valid only when you specify the Balances method and have the recurring frequency set to AN (annual). Blank is not a value. TO OBJ (to object) To SUB (to subsidiary) TO LT Enter a specific account or * to post to the same account indicated in the From Object field. Enter * in this field to carry the subledger in the From OBJ (from object) field to the Thru OBJ (thru object) field. The TO OBJ field must also contain *. Enter the ledger type. If you leave this field blank for annual budgets, the default is BA. If you leave this field blank for other ledger types, the default is AA. Enter text that describes the allocation. The text appears in the second of two description lines for each journal entry that the computation creates.
Explanation -Remark
131
Processing Allocations
Chapter 14
Setting Data Selection and Sequence for Indexed Computations Compute & Print
Specify the allocations that you want to include by document numbers. For multitiered allocations, specify all allocation document numbers that are part of the tiers. For example, if documents JA 1000, JA 1001, and JA 1002 compose the tiers of a multitiered allocation, include documents 1000, 1001, and 1002 in the data selection. Do not change the data sequence provided in the demo version of this program.
Setting Processing Options for Indexed Computations Compute & Print (R093021)
Processing options enable you to specify the default processing for programs and reports.
Mode
1. Process Mode Enter the processing mode. Values are: 1: Proof mode with report. 2: Final mode to create transactions.
Audit Trail
1. Print Audit Trail Specify whether to print an audit trail. Values are: Blank: Print the journal entries only. 1: Print an audit trail of all transactions or accounts that support each journal entry.
Include Alloc
1. Thru Date Enter the through date in which to include allocations. If you leave this processing option blank, the date that the allocation is processed is used.
Multi-tier
1. Multi-Tier Processing Specify whether to include multi-tiered entries. Values are: Blank: Include only posted transactions created before this batch. R: Include the amounts from transactions created in this batch in the totals for multi-tiered entries.
Explanations
1. Journal Entry Explanations Specify how to handle explanations for journal entries. Values are: Blank: Move the specification first description.
132
Chapter 14
Processing Allocations
1: Move the first description on new transactions from the detail transaction that the calculation is based on. This processing option applies to transaction method allocations only.
Errors
1. Error Processing Specify where to distribute error messages. Blank: Send errors to the work center. 1: Print errors on a report.
Log Warnings
1. Warning Processing Specify whether to log errors and warnings. Values are: Blank: Log all errors and warnings. 1: Suppress warnings.
133
Processing Allocations
Chapter 14
The system performs these steps when it calculates variable numerator allocations: 1. Gathers balances from a range of accounts (the Based Upon accounts). 2. Computes the percentage of the total for each account balance. 3. Applies the appropriate percentage to the balance of an account or range of accounts (the Allocate accounts). 4. Creates journal entries to distribute the resulting amounts to a specific account (the Apply To account) within multiple business units 5. Calculates an offset amount, if needed, to balance the resulting journal entries and distributes it to the contra/clearing account that you specify The system assigns batch type D to variable numerator allocations and stores the computation specifications in the Variable Allocation File table (F0912B).
Category Code 1 = 197 (Sales) Account 9901 Head Count AU Ledger Type Inception-To-Date Balances
Variable Numerators
Common Denominator
Amount 500/1000 = (.5x12,000) = 600 300/1000 = (.30x12,000) = 3600 200/1000 = (.2x12,000) = 2400
Allocating an expense account
134
Chapter 14
Processing Allocations
Prerequisite
Before you run a version with multitiered calculations, verify that the posting-sequence numbers on the Specify Variable Numerator Computation form are correct.
FormID
Navigation Allocations (G0923), Variable Numerator On the Work With Variable Numerator form, click Add.
Usage Locate and review existing variable numerator allocations. Create variable numerator allocations.
135
Processing Allocations
Chapter 14
Identification
Select the Identification tab. Explanation Contra/Clearing Account No. Type/Subledger Enter text that describes the allocation. This text appears in the first of two description lines for each journal entry that the allocation creates. Enter the account number associated with a contra/clearing account if the ledger is required to balance. Enter * to specify all subledgers. If you leave this field blank, the system only includes posted transactions with a blank subledger.
Specifications
Select the Specifications tab. From Business Unit OR Code Number AND Value Enter the first business unit in a range of business unit numbers or enter a number from 130 that identifies a business unit category code. Category codes group several business units and allocate the total amount in all of them. For example, 01 could indicate regions. Enter a specific value for the business
136
Chapter 14
Processing Allocations
unit category code. For example, the value WES for category code 01 could indicate only those business units in the western regions. Subsidiary MTD, YTD, ITD Enter a subsidiary account or * to post to the same subsidiary account indicated in the based upon field, even though the object in the apply to field is different. Select one of these options to control whether the allocation is based on month-to-date, year-to-date, or inception-to-date amounts. For month-to-date, the basis is the net posting balance for the month (the fiscal period). These allocations do not include prior month corrections in the allocation base. For year-to-date, the basis is the period-end balance. For profit and loss accounts, this is the sum of all net postings for the year through the end of the month that you specify. For balance sheet accounts, this is the cumulative balance through the end of the month you specify. These allocations do include prior month corrections in the allocation base. For inception-to-date, the basis is the cumulative balance through the end of the month you specify. These allocations include prior month corrections and all postings from prior years. Type/Subledger Enter a number that specifies the subledger account to which amounts are to be posted. The Subsidiary Account, Based Upon Business Unit, Apply To Object Account, Apply To Subledger, Apply To Ledger Type, and Subledger Type fields for the Contra/Clearing Account identify the account that posts the allocation.
Setting Processing Options for Variable Numerator Compute & Print (R093022)
Processing options enable you to specify the default processing for programs and reports.
Effective Date
1. Effective Date Enter the through date in which to include allocations. If you leave this processing option blank, the current date is used.
Mode
1. Process Mode Enter the processing mode. Values are:
137
Processing Allocations
Chapter 14
Multi-Tier
1. Multi-Tier Processing Specify whether to include multi-tiered entries. Values are: Blank: Include only posted transactions created before this batch. 1: Include the amounts from transactions created in this batch in the totals for multi-tiered entries.
Omit Zeros
1. Suppress Zero Amounts Specify whether to print zero amounts. Blank: Print zero amounts. 1: Do not print allocate from and based upon amounts, which are zero.
Errors
1. Print Errors on Report Specify where to distribute error messages. Blank: Send errors to the work center. 1: Print errors on a report.
138
CHAPTER 15
See Also
Chapter 4, Setting Up Account Reconciliation, page 33
139
Chapter 15
These programs automatically reconcile voided payments and receipts (and those with zero amounts) by updating the GLRCND field with the default reconciliation code R on the transactions in the F0911 table. When reconciling payments, the Automatic Reconcile Void Payment program selects payments that were voided manually and those voided during automatic payment processing. You should run these programs before you run the Refresh Reconciliation File program (R09130) so that voided and zero amount payments and receipts are not included in the F0911R workfile. The Automatic Reconcile Void Payments and Automatic Reconcile Void Receipts programs do not have processing options.
140
Chapter 15
The Refresh Reconciliation File program is designed to build only one F0911R workfile. However, you can allow separate workfiles for specific accounts by using the Configured Network Computing function to point to the F0911R workfile locally.
Prerequisite
Before you complete the tasks in this section: Set up the AAI ranges for GLRCxx AAIs to identify account ranges that must be reconciled. Set up a reconciliation code in UDC table 09/RC if you do not want to use the default reconciliation code R.
Select
1. Beginning Date and 2. Ending Date 3. Reconciled Status Specify the dates that you want the system to use as the beginning and ending dates when selecting records from the F0911 table. Values are: Blank: Select only unreconciled records. 1: Select both reconciled and unreconciled records. The F0911R can become unmanageable if you select both reconciled and unreconciled transactions on a regular basis. This can impact processing time. Include reconciled items only when it is necessary to correct a previous reconciliation.
Default
1. Ledger Type Specify the ledger type (UDC table 09/LT) for the system to use when selecting records from the F0911 table. If you leave this processing option blank, the system selects all ledger types.
141
Chapter 15
Display
1. Document Type Filter Specify whether the system includes AE document type transactions when it selects records from the F0911 table. Values are: Blank: Do not include AE transactions. 1: Include AE transactions.
Print
1. Messages Specify which messages to print on the Refresh Reconciliation File report (R09130). Values are: Blank: Print messages only for accounts that are refreshed. 1: Print messages for all accounts.
142
Chapter 15
FormID
Navigation Manual Reconciliation (G09209), Manual Reconciliation Select Bank Account Reconciliation on the Reconciliations form.
Usage Use this form to select the type of reconciliation. Manually reconcile or unreconcile bank account transactions.
W09131A
Defaults
1. Ledger Type 2. Reference 3 Specify a ledger type from the UDC table 09/LT for processing. If you leave this processing option blank, the system uses the default ledger type AA. Specify whether the system updates the Reference 3 field on the record in the F0911 table with a reconciliation number. The system uses the Next Number Revisions program (P0002) to assign the reconciliation number. This reconciliation number can be overridden at the time of reconciliation. If you leave this processing option blank, the system will not update the Reference 3 field.
Debit/Credit Edits
The processing options on this tab are used only by the Debit/Credit Match program. See Chapter 4, Setting Up Account Reconciliation, page 33.
143
Chapter 15
1. Enter the bank account number of the account for which you ran the Refresh Reconciliation File program in the Account Number field. 2. To view both unreconciled and reconciled items, do not select the Unreconciled Only option. You can view reconciled items only if you entered 1 for the Reconciled Status processing option of the Refresh Reconciliation File program. 3. Enter a general ledger date in the From Date field to limit the transactions that you view for the account. You must enter a date that is within the date range that you entered for the Beginning Date and Ending Date processing options of the Refresh Reconciliation File program. To view transactions from a date prior to the date entered for the Beginning Date processing option, you must run the Refresh Reconciliation File program again with different dates. 4. Enter the balance that appears on your bank statement in the Bank Balance field and click Find. 5. To further limit the transactions that you can view for an account, select Options from the Form menu. 6. On Options, enter a value in any of the fields.
144
Chapter 15
For example, if you enter a number in the Document Number field, only documents with that number will appear. This is helpful if you are trying to search for a particular transaction. Reference 1 For receipts, this field contains the batch number of the receipt. For payments, this field contains the payment number. Reference 2 For receipts, this field contains the document number of the receipt. For payments, this field contains the supplier number of the payment. 7. On Bank Account Reconciliation, click Find. The Options option is now selected. This is a reminder that you are viewing only transactions that meet the criteria that you specified on the Options form. 8. To mark a transaction as reconciled, double-click the transaction or select the transaction and then select Reconcile Toggle from the Row menu. 9. To mark more than one transaction (or all transactions) as reconciled, select the transactions and then select Reconcile Toggle from the Row menu. When you mark transactions as reconciled: If the Reference 3 processing option for the Manual Reconciliation program is set to 1, the Reference 3 Selection form appears and displays the next available number from next numbers. If you do not want all transactions to have the same reconciliation number, select Update Single from the form menu on the Reference 3 Selection form. The system displays this form each time you reconcile a transaction so that you can enter a new number for each transaction. The system enters R (or the reconciliation code that you selected) in the R ND field on the Bank Account Reconciliation form. 10. To unreconcile a reconciled transaction, double-click the transaction or select the transaction and then select Reconcile Toggle from the Row menu. 11. To complete the reconciliation process, select Update F0911 from the Form menu for the system to: Update the GLR3 field in the F0911R workfile with the reconciliation number. Update the GLRCND field in the F0911 table with the information in the F0911R workfile for all reconciled transactions. Update the GLR3 field in the F0911 table with the reconciliation number from the F0911R workfile if the Reference 3 processing option for the Manual Reconciliation program is set to 1. 12. To print a report, select Reconciliation Print from the Report menu.
145
Chapter 15
If you ran the Refresh Reconciliation File program since you reconciled the transaction, you must run the program again and set the Reconciled Status processing option to 1 to include reconciled transactions. If you need to change a reconciled transaction to unreconciled for a period that is different from the current period, you must run the Refresh Reconciliation File program again: Set the Reconciled Status processing option to 1 to include reconciled transactions. Change the Beginning Date and Ending Date processing options to include the general ledger date of the transaction that you want to change.
146
CHAPTER 16
Prerequisites
Before you complete the tasks in this section: Run the Auto Reconcile Void Payment program. Run the Auto Reconcile Void Receipt program. Run the Refresh Reconciliation File program.
147
Chapter 16
FormID
W09131A
Select Debit Credit/Match on Manually reconcile and the Reconciliations form. unreconcile debit and credit amounts.
Debit/Credit Edits
The processing options on this tab are used only by the Debit/Credit Match program. 1. Debit/Credit Balance Specify whether debits and credits are required to balance. Values are: Blank: Debits and credits are not required to balance. 1: Debits and credits are required to balance. If you enter 1 for this processing option and you leave the Tolerance Limit processing option blank, the debit and credit transactions must balance exactly; otherwise the system issues an error message. 2. Tolerance Limit Specify the tolerance amount by which debit and credit transactions can be out of balance. This processing option is used only when you enter 1 in the Debit/Credit Balance processing option. If you enter 1 in the Debit/Credit Balance processing option and you leave this processing option blank, debits and credits must balance exactly or the system generates an error. If you enter 1 in the Debit/Credit Balance processing option and you specify an amount for this processing option, the difference between the debit and credit transactions must be less than or equal to the tolerance amount. If the debit and credit transactions are out of balance by the tolerance amount, they are considered reconciled and the system does not generate an error message. For example, if you enter 5.00 in this processing option, debits and credits can be out of balance by 5.00. If debits and credits are greater than the tolerance amount, the system generates an error message. 3. Sort By Specify how the system should sort transactions. Values are: Blank: Sort transactions by general ledger date. 1: Sort transactions by amount. The system sorts the transactions by amount, regardless of whether they are debits or credits. You will be able to see an
148
Chapter 16
amount with the debit and credit together as opposed to searching for the offset of the amount by the general ledger date.
149
Chapter 16
150
CHAPTER 17
See Also
Chapter 15, Reconciling Bank Account Transactions, Reconciling Voided Payments and Receipts, page 139
151
Chapter 17
Yes
No
152
Chapter 17
Positions 6267
Payment date
If data in the F095051 workfile is not in the positions specified, you must create a new custom reformat program. Use the Custom Reformat UBE program as a template for creating your custom program.
Purge
1. Purge F09505 table before processing. Specify whether the system purges the F09505 workfile before it runs the Custom Reformat UBE program. Values are: Blank: Do not purge the F09505 workfile. 1: Purge the F09505 workfile. The system purges this workfile before it updates the F095051 workfile. 2. Purge F095051 table before processing. Specify whether the system purges the F095051 workfile after it runs the Custom Reformat UBE program. Values are: Blank: Do not purge the F095051 workfile. 1: Purge the F095051 workfile.
153
Chapter 17
See Also
Chapter 15, Reconciling Bank Account Transactions, Understanding the Refresh Reconciliation File Program, page 140
Setting Processing Options for Match Tape File To Recon File (R09510)
Use these processing options to specify an account ID and assign a reconciliation number, if applicable.
Select
1. Account ID Specify an account ID to automatically assign to each GL account to maintain an audit trail. The account ID is a unique identification number (account key)
154
Chapter 17
and a self-check digit. This number is also called the account serial number, the short account number, and the ID number. 2. Reference 3 Specify whether to automatically assign a reconciliation number to the Reference 3 field. Values are: Blank: Do not update the Reference 3 field. 1: Update the Reference 3 field with a reconciliation number. 3. Reference 3 Value Specify the reconciliation number to update in the Reference 3 field. If you leave this processing option blank, the system uses the Next Number Revisions program (P0002) to assign the reconciliation number.
155
Chapter 17
Description Summarizes payments that have a cleared date prior to the payment date. Payments appear on this report if: A date was entered in error. The bank cashed a post-dated payment. The payment was released before it was supposed to be released.
Summarizes payments that have cleared the bank, but the cleared amount is not the same as the actual payment amount. Payments appear on this report if: An amount was entered in error. A bank error allowed the payment to be cashed for an amount that was different from the actual amount.
156
CHAPTER 18
See Also
JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange 8.12 Implementation Guide, Processing EDI Documents, Receiving EDI Standard Business Documents
157
Chapter 18
Bank Transit
The number assigned to a particular bank by the Federal Reserve to facilitate the clearing of funds.
Transactions That Cleared Your Bank Account and Have Been Entered in the System
This table shows setup information for transaction types that cleared your bank account and have been entered in the system:
Transaction Code CR Description 01 Cash Receipt Clear Description 02 04 Cash Receipt Clear Description This transaction code is used to record deposits or other receipts that you previously entered in the system. This transaction code is used to record canceled checks or payments that you previously entered in the system.
CK
Payment Clear
08 Payment Clear
Transactions That Cleared Your Bank Account and Have Not Been Entered in the System
This table shows setup information for transactions that cleared your bank account and have not been entered in the system:
Transaction Code JE Description 01 Journal Entry Description 02 01 Journal Entry Description This transaction code is used to record an adjustment that was made by the bank, such as a service charge or a wire transfer fee. These transactions might have an associated value-added tax (VAT).
158
Chapter 18
Description This transaction code is used to record payments that a customer made directly to your bank account, such as a wire transfer, that you have not previously entered in the JD Edwards EnterpriseOne Accounts Receivable system. When you run the Bank Journal Statement Process program (R09170), the system automatically applies the receipt to invoices by running the Update Receipts Header (R03B551) and Apply Receipts to Invoices (R03B50) programs.
CRI
This transaction code is used to record payments that a customer made directly to your bank account, such as a wire transfer, that you have not previously entered in JD Edwards EnterpriseOne Accounts Receivable. When you enter a transaction with this code, the Bank Statement Entry program (P09160) launches the Standard Receipts Entry program (P03B102) so that you can apply the receipt manually to the correct invoices.
DP
07 Draft Paid
This transaction code is used to record drafts that have been submitted by your suppliers to your bank for payment. This transaction code is used to record payments. When you enter transaction with this code, the system launches the Payment With Voucher Match program (P0413M). This transaction code is used to record payments. When you enter a transaction with this code, the system launches the Payment Without Voucher Match program (P0411).
PWM
PWO
BK
Self Reconciling
09 Self Reconciling This transaction code is used to record self-reconciling items. A self-reconciling item does not require reconciliation and does not launch a program.
159
Chapter 18
CR CRE CRI CK When you use transit accounts, you do not need to run the Refresh Reconciliation File program (R09130) to update the F0911R table. However, because you do not update the F0911R table, the Bank Journal Statement Process program cannot compare information between the F0911R and F0917 tables to determine whether an item should be reconciled. The system assumes that the information that you entered in the F0917 table is correct. Therefore, you must reconcile the transit account to ensure the accuracy of the information entered for the bank statement. When the system reconciles the transaction, it marks the bank account as reconciled but does not mark the transit account.
160
Chapter 18
On the Work With Bank Statements form, click Add to enter transactions. Or select the statement to access transactions for an existing statement.
Enter bank statement transactions. You can add transactions to and revise transactions for unprocessed bank statements only.
Clear Receipts
W09160J
On the Enter Statement form, Add detailed information for enter CR in the TR CDe field a cleared cash receipt. and click OK. On the Enter Statement form, Add detailed information for enter JE in the TR CD field a journal entry. and click OK. On the Enter Statement form, Add detailed information for enter CK in the TR CD field a cleared payment. and click OK. On the Enter Statement form, Add detailed information for enter CRE in the TR CD a batch cash receipt. field and click OK. On the Enter Statement form, Add detailed information for enter CRI in the TR CD field an interactive cash receipt. and click OK. On the Enter Statement form, Add detailed information enter DP in the TR CD field for a draft that is paid to a supplier. and click OK. On the Enter Statement form, Add detailed information for enter PWO in the TR CD a manual payment without a field and click OK. matching voucher. On the Enter Statement form, Add detailed information for enter PWM in the TR CD a manual payment with a field and click OK. matching voucher. On the Enter Statement form, select Options from the Form menu. Specify search criteria for the transactions that you want to review or revise.
Journal Entry
W09160E
Clear Payment
W09160G
W09160I
Receipt Entry
W03B102E
W09160H
W0411A
W0413MA
Options
W09160D
161
Chapter 18
Criteria
1. Short account ID for the default bank account Specify whether the system should preload a bank account in the query-by-example (QBE) row. You must enter the short account ID of the bank account. If you leave this processing option blank, the system does not preload a bank account. Specify whether the system should preload a user ID in the QBE row. Values are: Blank: Do not preload a user ID. 1: Preload a user ID. 3. Posted Code Specify whether the system should preload a specific posted code in the QBE row. Values are: A: Preload a posted code of A (approved). D: Preload a posted code of D (processed). 4. Pre-load records Specify whether the system should preload all records. Values are: Blank: Do not preload all records. If the system does not preload all records, you must click Find on the Work With Bank Statements form to load the records. 1: Preload all records.
2. User ID preload
Defaults
1. Default Deposit Transaction Type and 2. Default Withdrawal Transaction Type 3. Default Transit Accounts (Short account ID) Automatic Receipts Entry, Receipts Clear, Manual Receipts Entry, and Payment Clear Specify a default transaction type from UDC table 09/BJ for deposit amounts and withdrawal amounts.
Enter the short account ID for the types of transactions specified in the previous processing options. Enter the short account ID of the default transit account for each processing option.
Journal Entry
1. Default short account ID for Journal Entry transactions Enter the short account ID of the default account for journal entries.
Dates Tab
1. Value Date (GDVLDT) and, 2. G/L Date (GDDGJ) Specify the default date to use for the value date and the GL date. The value date is the date that the payment amount was debited or credited to the bank account. The GL date identifies the financial period to which a transaction is posted. Values are: 0: Use the GL date.
162
Chapter 18
Document Type
1. Default Document Types Enter the default document type from UDC table 00/DT for each processing for Transaction CodesBK option and corresponding transaction code. - Self-Reconciling, CK Payment - Clear, CR - Cash Receipt - Clear, CRE - Cash Receipt - Batch, CRI - Cash Receipt Interactive, DP - Draft Paid to Supplier, JE - Journal Entry, PWM - Manual Payments w/Match, and PWO - Manual Payments w/o Match
Display 1
Gross Amount (GDAG), Remark (GDRMK), Bank Transit (GDTNST), Cleared/Value Date (GDVLDT), Reference (GDR1), and Explanation (GDEXA) Specify whether to restrict access to the field associated with each processing option. Values are: Blank: Do not restrict access. 1: Restrict access.
Display 2
Transit Account (GDANI) and G/L Date (GDDGJ) Specify whether to restrict access to the field associated with the processing options. Values are: Blank: Do not restrict access. 1: Restrict access. 2. Home Business Unit Specify whether to restrict access to the Home Business Unit field or to remove the field from the form. Values are: Blank: Allow regular access. 1: Restrict access. 2: Remove this field from the form. 3. Default Bank Account (specified in the Criteria tab) Specify whether to allow users to change the default bank account. Values are: Blank: Allow. 1: Do not allow.
163
Chapter 18
Versions
1. Override Manual Receipts Entry processing, 2. Override Manual Payments with Voucher Match processing, and 3. Override Manual Payments without Voucher Match processing Specify which version to use of the Standard Receipts Entry (P03B102), Payment With Voucher Match (P0413M), and Payment Without Voucher Match (P0411) programs. If you leave a processing option blank, the system uses version ZJDE0001.
Entry Mode
1. Editing Mode Specify the type of editing that the system performs on the Enter Statements form. Values are: 0: The system does not display the detail form and, therefore, does not perform any editing. 1: The system displays the detail form, but does not perform any editing if you enter incorrect information or leave required fields blank on the form. 2: The system displays the detail form and performs editing if you enter incorrect information or leave required fields blank on the form. 2. Exit Out of Balance Specify whether a user can exit the Enter Statement form out of balance. Values are: Blank: Allow the user to exit out of balance. 1: Set an error that does not allow the user to exit out of balance. 2: Set a warning if the user attempts to exit out of balance, but still allow the user to exit out of balance.
Prev Balance
1. Bank Statement Beginning Balance Specify the mode for populating the beginning balance of the bank statement. Values are: Blank: Allow the user to manually enter the beginning balance. 1: Load the beginning balance using the ending balance from the previous bank statement. This processing option requires that bank statements be entered in sequential order and that the previous statement be completely reconciled before entering the next one. 2: Load the beginning balance using the account balance as of the bank statement date. Include posted transactions only. 3: Load the beginning balance using the account balance as of the bank statement date. Include both posted and unposted transactions. Note. Entering a 1, 2, or 3 in this processing option disables the Beginning Balance field on the Enter Statement form.
164
Chapter 18
Transaction Codes
BK - Self-Reconciling, CK - Payment -Clear, CR Cash Receipt - Clear, CRE - Cash Receipt - Batch, CRI - Cash Receipt Interactive, DP - Draft Paid to Supplier, JE - Journal Entry, PWM - Manual Payments w/Match, and PWO - Manual Payments w/o Match Specify whether to allow the transaction code associated with the processing option. Values are: Blank: Allow the code. 1: Do not allow the code.
165
Chapter 18
PWM or PWO: Leave this field blank. The system uses the number that you enter for the payment. Ty (type) Enter the code from UDC table 00/DT that specifies the kind of document that is used to match the original document. If you entered a default document type for the transaction code in a processing option, the system uses it as the default. A code that designates the processed and reconciled status of a bank statement transaction. This code represents the G/L posted code status of F0917 records as well as the reconciliation status of F0917 and F0911 records. For unprocessed or unreconciled records, the G/L Posted Code field in the F0917 table is A and the Reconciled field is blank. For processed or reconciled records, valid codes are specified in the processing options for the Bank Journal Statement Process program (R09170). These codes are edited against UDC table 09/RC. For reconciled records, the code in the G/L Posted Code field is the same as the code in the Reconciled field for both the F0917 and F0911 tables. After you enter a transaction on the Enter Statement form and click OK or select Detail from the Row menu, the system displays one of the following, based on a processing option setting: If the Editing Mode processing option is 1 or 2, the system displays the detail form that corresponds to the transaction code that you entered. If you entered CR, the system displays the Clear Receipts form. If you entered CK, the system displays the Clear Payment form and so on. If the Editing Mode processing option is 2, the system also performs editing if you enter an invalid value or leave required fields blank on the detail form. Default values for some fields on the detail form are specified in processing options for the Bank Statement Entry program. If the Editing Mode processing option is 0, the system does not display a detail form. Instead, it displays the warning message Incomplete Transactions Exist. Click OK and then Cancel. You must remember to enter the detail at another time.
166
Chapter 18
Prerequisite
Post any unposted batches.
Select
1. Beginning Date and 2. Ending Date 3. Reconciled Status Specify the beginning and ending date to refresh the F0911R table. Select the transactions to include in the F0911R table. Values are: Blank: Reconciled transactions only. 1: Both reconciled and unreconciled transactions. The F0911R table can become unmanageable and impact processing time if you choose to include both reconciled and unreconciled transactions on a regular basis. Include both reconciled and unreconciled records only when you need to correct a previous reconciliation.
167
Chapter 18
Default
1. Ledger Type Specify the ledger type that the system uses to select records from the F0911 table. If you leave this processing option blank, all ledger types are selected.
Display
1. Document Type Filter Specify whether the system includes adjusting entry (AE) transactions when selecting records from the F0911 table. Values are: Blank: Do not include AE transactions. 1: Include AE transactions.
Print
1. Messages Specify whether the system prints messages on the Refresh Reconciliation File report (R09130) for all accounts or only for accounts that are refreshed. Values are: Blank: Print messages only for accounts that are refreshed. 1: Print all messages.
168
Chapter 18
If you used a transit account, the program creates a journal entry to reallocate the amount from the transit account to the bank account. Note. You must post the journal entry batches that the system creates after you run the Bank Journal Statement Process program. Generates reconciliation reports. The program generates these reports, which show the results of the comparison between the F0911R and F0917 tables: - Bank Journal Statement Processing - Bank Reconciliation Report - Cleared Not Issued - Cleared Before Issued - Amounts Not Equal - Unreconciled Items Reconciles transactions. You specify in the processing options whether to run the program in proof or final mode. In proof mode, the system prints reconciliation reports but does not reconcile transactions. In final mode, for each transaction with matching information in the F0911R and F0917 tables, the system updates the GLRCND (Reconciled Code) field in the F0911 table with R..To use a reconciliation code other than R, enter a different code in the processing options for the Bank Journal Statement Process program. If you used a transit account, the system updates the GLRCND field without comparing the two tables. You also specify in the processing options whether you want the system to update the Reference 3 field for the transaction in the F0911 table with the bank statement number. These programs display or print the information in the Reference 3 field: Account Ledger Inquiry (P09200) Account Inquiry by Category Code (P09202) Transaction Journal (R09321)
Prerequisite
Run the Refresh Reconciliation File program to refresh the F0911R table with updated information.
See Also
JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Processing Bank Statements Manually in Multiple Currencies
169
Chapter 18
Proof/Final
1. Process Mode Specify the mode in which to process bank statements. Values are: Blank: Proof mode. Do not update the F0911 table. 1: Final mode. Update the F0911 table.
Document Type
1. Document Type Enter a code from UDC table 00/DT that begins with U. (U1U9 and UAUZ and are reserved for clients.) If you leave this processing option blank, the system uses JE as the default document type. For document type JE, the system uses the next number for journal entries to assign a document number to the transaction. If a document type other than JE, the system uses the next number for bank journals.
Variance
1. Variance Tolerance Limit Enter an amount for the tolerance limit for automatic write-offs. You can also enter an amount with a percent sign to indicate that the number should be used as a percentage. If you leave this processing option blank, tolerance limits are not used. Specify whether to automatically create journal entries to write off variances that are equal to or less than the tolerance limit. Values are: Blank: Do not automatically create journal entries. Variance amounts are listed separately. 1: Automatically create journal entries. 3. Enter the date mode for the Journal Entry. Specify the date to use for the journal entry. Values are: 0: System date. 1: General ledger date. 2: Value (cleared) date. Business Unit Enter the business unit of the GL account for the journal entry. If you leave this processing option blank, the system uses the business unit of the bank account that appears on the bank statement. Enter the object account and the subsidiary of the GL account for the journal entry.
170
Chapter 18
Realized Gain/Loss
1. Realized Gain/Loss Processing Specify whether to create realized gain and loss journal entries. Values are: Blank: Do not create entries. 1: Create entries. 2. Date Mode Specify the date to use for realized gain and loss journal entries. Values are: 0: System date. 1: General ledger date from the F0911R table. 2: Value (cleared) date from the F0917 table.
Date
1. Transaction Mode for Value (Cleared) Date Specify how to manage transactions if the value (cleared) date is earlier than the general ledger date in the F0911 table. Values are: Blank: Do not reconcile the transactions, but print them on the report. 1: Reconcile the transactions and print them on the report. 2: Reconcile the transactions, but do not print them on the report.
Reconciliation
If you leave any of these processing options blank, the system uses the value from the first condition. Enter a code from UDC table 09/RC for each processing option. Exact One for One Match without Consolidation or Use of Tolerance Rule (Default R) Consolidated Items Where the G/L Transactions Balance to Zero and There is No Bank Record. Consolidated Items Where the Bank Transactions Balance to Zero and There is No G/L Amount. The Consolidation Process was Used to Achieve the Match of the Transactions. (There are G/L and Bank Statement Transactions.) The Transactions Were for Different Values But Fell Within the Tolerance Allowed. Enter a code for an exact one-for-one match.
Enter a code for consolidated items with a balance of zero and no bank record.
Enter a code for consolidated items with a balance of zero and no amount.
Enter a code for transactions with different values that are within the tolerance allowed.
171
Chapter 18
This Transaction Only Exists in the Bank Statement File and is a Self Reconciling Item.
Statement
1. Enter the Mode for Populating the GLR3 Reference Field in the F0911 with the F0917 Bank Statement Number. Specify whether to update the GLR3 (Reference 3) field in the F0911 table with the bank statement number in the F0917 table for corresponding records. Values are: Blank: Do not update the GLR3 field. 1: Update the GLR3 field. If you specify final mode for processing, the system overwrites any previous value in the GLR3 field.
Bank Reconciliation
Cleared Not Issued Cleared Before Issued Amounts Not Equal Unreconciled Items
Note. If column C (consolidated) on a report contains an asterisk, that particular line on the report consists of multiple transactions that are consolidated together.
172
Chapter 18
3. Manually reconcile the transactions using the Bank Account Reconciliation form, which you access from the Manual Reconciliation program (P09131).
173
Chapter 18
174
CHAPTER 19
Understanding the PeopleSoft Enterprise Treasury and JD Edwards EnterpriseOne General Accounting Integration
The integration of Oracles PeopleSoft Enterprise Treasury Management and JD Edwards EnterpriseOne General Accounting systems enables you to use the PeopleSoft Treasury Management system to manage your cash and risk for sound fund management and to meet regulatory requirements while maintaining your accounting information in the JD Edwards EnterpriseOne General Accounting system. The PeopleSoft Enterprise Treasury Management system provides business processes for cash management activities such as bank transfers, deal transactions, electronic funds transfers (EFTs), and so on. With the integration, bank statements from PeopleSoft Enterprise Treasury Management are transferred to the JD Edwards EnterpriseOne General Accounting. The JD Edwards EnterpriseOne General Accounting system provides an automatic bank account process that is automated from the bank flat file to bank account reconciliation. For transactions that affect bank accounts, all bank statement data from PeopleSoft Enterprise Treasury Management is mapped from its original bank format to the PSFT bank format. The PSFT bank statements are transferred via the Web Services Gateway to the bank statement staging tables (F09610 and F09611) in the General Accounting system. The Load Bank Statement program uploads the statements to the bank statement tables (F09616 and F09617) and the Process Automatic Bank Statement program processes and reconciles the transactions in the F0911 table. For GL transactions that affect bank accounts, accounting transactions are created in the Treasury Management system and then transferred via the Web Services Gateway to the F0911Z1 table in the JD Edwards EnterpriseOne General Accounting system. The transactions are created with a document type TM (Treasury Management). From the F0911Z1 table, the Journal Entry Batch Processor program (R09110Z) uploads the transactions to the F0911 table and sends a message to PeopleSoft Enterprise Treasury Management indicating whether the program completed successfully. The Process Automatic Bank Statement program processes and reconciles the accounting transactions against RJE transactions in the F0911 table.
175
Chapter 19
After the transactions are written to the F0911 table, they can be posted to the F0902 table using the General Ledger Post program (R09801). When the accounting transactions are successfully posted, a message is sent to PeopleSoft Enterprise Treasury Management.
176
Chapter 19
177
Chapter 19
178
CHAPTER 20
See Also
Chapter 5, Setting Up Automatic Bank Statement Processing, page 35
179
Chapter 20
Next, you run the Load Bank Statement program (R09612) to transfer the data to the bank statement tables (F09616 and F09617) and use the Revise Automatic Bank Statement program (P09616) to revise any data. Then run the Process Automatic Bank Statement program (R09616) to automatically reconcile data from the electronic bank statement against the bank account information in your general ledger. If there are transactions that do not reconcile automatically and a processing option is set accordingly, the program prints an unreconciled report. You can correct unreconciled exceptions through the Manual Bank Statement Reconciliation program (P09631). Note. If you use the PeopleSoft Enterprise Treasury Management system but perform your accounting activities using the JD Edwards EnterpriseOne General Accounting system, you must transfer bank statement data from PeopleSoft Enterprise to the JD Edwards EnterpriseOne bank statement staging tables for automatic bank statement processing. See Chapter 19, Processing PeopleSoft Enterprise Bank Statements in JD Edwards EnterpriseOne General Accounting, page 175. This diagram illustrates the automatic bank statement process:
F09610
F09611
Exit to Manual Exit to Manual Exit to Standard Payment With Payment Without Receipts Entry Voucher Match Voucher Match (P03B102) (P0413M) (P0411)
180
Chapter 20
Prerequisites
To process multiple bank flat files, change the path location in the Value field on the Integration Options form before you run each conversion flow. See Chapter 5, Setting Up Automatic Bank Statement Processing, Setting Integration Options for Conversion Flows, page 35.
Services form that shows conversion flows for automatic bank statement
181
Chapter 20
Note. If you did not set the integration options to delete the text file that was created previously, change the path location in the Value field to the new path on the Integration Options form before you complete these steps. 1. On the Services form, scroll down to PSFT EnterpriseOne Interfaces.Financials.AutoBankStatement. 2. Select one of these: convert_BAI2_To_E1_BankStatementStaging convert_Swift_To_E1_BankStatementStaging 3. Depending on the conversion flow that you selected in the previous step, select one of the these: Test convert BAI2 To E1 BankStatementStaging Test convert Swift To E1 BankStatementStaging 4. On the Assign Input Values form, click Test (without inputs) to run the conversion flow. Note. If you set the integration options to delete the previously created text file after transferring data, the conversion flow creates the new text file using the path specified on the Integration Options form. 5. To access the audit log, return to the Integration Server and under the Logs heading, select Server. 6. If the conversion flow failed, return to the Integration Server and under the Logs heading, select Error.
182
Chapter 20
FormID
Navigation Automatic Bank Statement Processing (G09212), Revise Electronic Bank Statement Staging To purge records, on the Work with Electronic Bank Statement Staging form, select Purge Staging to access the Purge Staging Tables program (R09610).
Usage Review a list of bank statements or limit your search to a specific bank statement.
W09610A
On the Work with Electronic Bank Statement Staging form,, select the bank statement that you want to revise.
Revise data that is in error. You cannot delete or add data on this form. Instead, you must modify the mapping for one of the conversion flows and run it again.
Setting Processing Options for Revise Electronic Bank Statement Staging (P09610)
Use these processing options to restrict users from revising certain fields on the Revise Electronic Bank Statement Staging form.
Update
For each processing option on this tab, values are: Blank: Do not allow the field to be revised. 1: Allow the field to be revised. The processing options for this program correspond to these fields on the Revise Electronic Bank Statement Staging form: Transaction Value Date Transaction Debit/Credit Indicator Transaction Amount Electronic Transaction Type Customer Reference Bank Reference Subfield 9 Misc Information
183
Chapter 20
Header Fields
Closing Balance This field is required for the SWIFT format. The SWIFT bank flat file will always include a closing balance amount, which displays in this field. If the closing balance is not in the bank flat file for the BAI2 or PSFT format, the system calculates the closing balance in this field but it does not update any tables. This enables the staging tables to remain pristine, exactly as the data appeared in the bank flat file. Not Loaded, Loaded, All Select one of these options to identify the transactions that you want to display. If you revise records that have not been loaded from the staging tables to the bank statement tables, run the Load Bank Statement program again so that the bank statement tables reflect the revisions.
Detail Fields
Processing option settings control whether you can revise certain fields in the detail area of this form. Electronic Transaction Type Customer Reference Displays the transaction type code from UDC table 09/BA (BAI2 format) or 09/ST ( SWIFT format). Identifies a reference that appears on the electronic bank statement. The reference in this field links the bank statement transaction to the JD Edwards EnterpriseOne General Accounting system. This could be a deposit number for receipts or a payment number. Displays the date that the payment amount was debited or credited to the bank account. The transaction value date is not the date the bank reconciled the payment.
184
Chapter 20
Indicates if a transaction is a debit or credit. Values are: D: Debit C: Credit RC: Cancellation credit RD: Cancellation debit If you change the Electronic Transaction Type field and the bank format is BAI2 or PSFT, the system supplies the default value for this field. If the bank format is SWIFT, you must enter the indicator.
Transaction Currency Code Bank Reference Reconciliation Code Subfield 9 Misc Information (miscellaneous information)
Displays the transaction currency code of the bank account. In a multicurrency environment, if the bank account currency is foreign, the foreign currency is the transaction currency. Identifies a reference that the bank assigns to electronic bank statements. Displays the code from UDC table 09/RC that identifies whether a transaction has been reconciled. This field is always disabled. Displays information that appears on the electronic bank statement. Displays miscellaneous information that appears on the electronic bank statement.
See Also
Appendix C, Conversion Flow Field Mapping for Automatic Bank Statement Processing, page 469
185
Chapter 20
If a bank statement does not contain transactions, the bank statement is not mapped to the bank statement tables because no detail records exist. The statement is, however, mapped to the staging tables to provide an exact duplicate of the bank flat file.
Process
Purge Staging Tables Specify whether to purge staging records that have been loaded successfully into the bank statement tables. Values are: Blank: Do not purge. 1: Purge. The system runs the Purge Electronic Bank Statement Staging program after it successfully loads the staging records into the bank statement tables.
186
Chapter 20
FormID
Navigation
Usage
Review a list of bank Automatic Bank Statement Processing (G09212), Revise statements or limit your search to a specific Automatic Bank Statement bank statement. If a On the Work With Auto bank statement appears Bank Statement form, select highlighted on this form, Customer/Supplier from the statement contains a the Form menu to revise data error. transactions without a customer number. On the Work With Auto Bank Statement form, select the bank statement that you want to revise. Select Bank Stmt Staging from the Row menu to revise data in the staging tables. Select Purge Bank Statement from the Form menu to access the Purge Automatic Bank Statement Tables program (R09615) and purge the F09616 and F09617 tables. Correct data that is in error. You cannot delete or add records on this form.
W09617A
Automatic Bank Statement Processing (G09212), Automatic Bank Statement Customer/Supplier Entry On the Work With Bank Statement Customer/Supplier Entry form, select a transaction.
Identify automatic batch receipt transactions that are missing a customer number. Enter a missing customer number for an automatic batch receipt transaction. This form contains detailed information associated with the bank statement transaction. All fields except the Customer/Supplier Number field are for reference purposes only and cannot be changed.
W09617B
Revise Fields
For each processing option on this tab, values are:
187
Chapter 20
Blank: Do not allow the field to be revised. 1: Allow the field to be revised. The processing options for this program correspond to these fields on the Revise Auto Bank Statement form: Cleared/Value Date Payment/Receipt Number Bank Statement Transaction Code Remark SWIFT Subfield 9 SWIFT Miscellaneous Information
The system displays transactions by the date they cleared the bank in descending order, with the most recent transaction first. If a data error exists, the system displays a warning message at the top of the Revise Auto Bank Statement form. For BAI2 and PSFT electronic formats, the system performs an integrity check that validates the data that you revise on this form. The integrity check ensures that the opening balance and the total debit and credit amounts equal the closing balance for an electronic bank statement. If there is a discrepancy in the amounts, the program displays a warning message, such as Closing balance is incorrect. If the bank statement does not include a closing balance, the amount calculated in the Closing Balance field becomes the closing balance.
188
Chapter 20
Header Fields
Electronic Bank Account Number Display Transactions w/o Customer/Supplier Number for Auto Batch Receipts Display All, Display Reconciled Transactions, Display Unreconciled Transactions Displays the bank account number from the F09610 staging table. You can revise this field, if necessary. Select this check box to display CR transactions that are missing a customer number. When the system processes automatic bank statements, it requires a customer number to create automatic batch receipts and apply them to invoices. If the customer number is blank, the system creates the automatic batch receipts as logged receipts. These receipts are not applied to invoices. Select one of these options to display only reconciled or unreconciled transactions, or both.
Detail Fields
Processing option settings control whether you can revise certain fields in the detail area of this form. Cleared/Value Date Payment/Receipt Number Displays the date that the payment amount was debited or credited to the bank account. The value date is not the date the bank reconciled the payment. Displays a reference number of up to 16 alphanumeric characters and is typically used for receipts, payments, and bank wire transfers. The Customer Reference (CUSTREF) field in the F09611 staging table maps to this field (CKNU) in the F09617 bank statement table. Electronic Bank Transaction Type Bank Statement Transaction Code Displays a user-defined code from UDC table 09/BA (BAI2 bank format) or 09/ST ( SWIFT bank format) that identifies the transaction type code. Displays a user-defined transaction type, such as CK, CR, DP, JE, or RJE.
189
Chapter 20
This form displays CR transactions only. The customer number is required to create automatic batch receipts and apply them to invoices; it is not required for all CR transactions. If the customer number is blank and the reconciliation rules are set up to create automatic batch receipts, the system creates a logged receipt and does not apply it to invoices. Show Trans w/o Cust/Suppl No for Auto Batch Receipts (show transactions without customer/supplier number for automatic batch receipts) Show All Transactions Select this option to display CR transactions in which the customer number is missing. If a number is missing for a transaction and the transaction is marked as an automatic batch receipt, the Customer/Supplier Flag field on this form is 1. Select this option to display CR transactions with and without customer numbers. If the number exists for a transaction and the transaction is marked as an automatic batch receipt, the Customer/Supplier Flag field on this form is blank.
190
Chapter 20
Uses the offset business unit code (UDC table 09/BU) that is assigned to transaction code JE (on the Revise Transaction Type Cross Reference form) to determine whether to create an offsetting journal entry using the business unit of an alternate offset account or a bank account. Processes the transactions in the F09616 and F09617 tables and reconciles them to the transactions in the F0911 table. Note. The Process Automatic Bank Statement program does not automatically reconcile manual journal entries entered in the JD Edwards EnterpriseOne General Accounting system; you must manually reconcile them. There is no reference number field to connect these transactions from the F09616 and F09617 tables to the F0911 table. Runs the Automatic Batch Receipt program (R03B551) to create batch receipts for CR transactions that are marked for automatic batch receipts. The system creates automatic batch receipts and attempts to apply the receipts to invoices if a customer number is assigned to a transaction. If the customer number is blank, the system creates a logged receipt, which is not applied to invoices. The Process Automatic Bank Statement program populates the GLR3 (Reference 3) field in the F0911 table with the batch number of the bank statement, not the batch number of the receipt or deposit number. If you want the bank statement number to appear on transactions, you must select a check box for the reconciliation rule on the Revise Auto Reconciliation Group form. For multicurrency processing, the program creates batch receipts only if the receipt and invoice currencies are the same. For transactions with customer numbers, runs the Apply Receipts to Invoices program (R03B50) to apply the batch receipts to invoices. If there is no matching invoice, the program creates an invoice with type RU. Updates records in the staging tables as reconciled, unless the records were purged earlier in the process. In a multicurrency environment, the bank account format uses the transaction currency of the bank account. If the bank account currency is foreign (not in the base currency of the company), the foreign currency is the transaction currency. The Process Automatic Bank Statement program cannot calculate gains and losses on foreign currency bank accounts because there are no domestic amounts on the transactions. After you run the Process Automatic Bank Statement program, you can review transactions on the Reconcile Bank Statement Detail to Account Ledger form and manually reconcile any exceptions that did not reconcile and, if applicable, unreconcile reconciled transactions.
191
Chapter 20
192
Chapter 20
Select
Bank Statement Number Specify the bank statement number to reconcile. If you leave this processing option blank, the program processes all bank statements in the F09616 table.
G/L Bank Account Number Specify the general ledger bank account number to reconcile. If you leave (general ledger bank account this processing option blank, the program processes all general ledger bank number) accounts in the F09616 table. Beginning Date Specify the beginning date in which to reconcile records. If you leave this field blank, the program processes all records in the F09616 table through the ending date. If you leave the Ending Date processing option blank, the program processes all records in the table. Specify the ending date in which to reconcile records. If you leave this field blank, the program processes all records in the F09616 as of the beginning date. If you leave the Beginning Date processing option blank, the program processes all records in the table.
Ending Date
Print
For these processing options, values are: Blank: Print 1: Do not print Suppress Printing Unreconciled Report, Suppress Printing Reconciled Report, and Suppress Printing Summary Report Specify whether to print the report. To print all reports, leave these processing options blank.
193
Chapter 20
194
Chapter 20
FormID
Navigation Automatic Bank Statement Processing (G09212), Manual Bank Statement Reconciliation
Usage Reconcile unreconciled transactions for a bank account and, if applicable, unreconcile reconciled transactions.
Defaults
Suppress Reference 3 Update Specify whether to update the Reference 3 (GLR3) field in the F0911 table with a number from next numbers. Values are: Blank: Do not suppress the update of Reference 3. That is, update the Reference 3 field. 1: Suppress the update of Reference 3. That is, do not update the Reference 3 field. Note. You can override this processing option value for transactions on the Reconcile Bank Statement Detail to Account Ledger form. Reconciled Code Specify the reconciliation code from UDC table 09/RC to use as the default value on the Reconcile Bank Statement Detail to Account Ledger form. If you leave this processing option blank, the system uses R (Reconciled One for One Match) as the default value.
Reconcile Bank Statement Detail to Account Ledger form - Search Bank Statement region
Enter the general ledger number for the bank account. Enter the beginning and ending dates in which to view transactions for the bank account. Select Reconciled, Unreconciled, or All from the drop down menu to display the transactions that meet your criteria.
195
Chapter 20
Reconcile Bank Statement Detail to Account Ledger form: Bank Statement Detail
To correct an unreconciled transaction: 1. Select the transaction. 2. Scroll to the top of the Reconcile Bank Statement Detail to Account Ledger form. 3. From the Row menu, select the appropriate program. For example, to correct a transaction in which the payment has not been posted, select the transaction and then select Batch Review from the Row menu. On the Work With Batches form, select the unposted batch and then select Post by Batch from the Row menu. Note. If you use the Row menu to exit to a program and manually create a receipt or payment, the system assigns the bank statement batch number to the batch that you created. For manual journal entries, the system assigns a new batch number instead. Statement D and Statement D... Displays bank statement transactions based on the beginning and ending dates that you entered in the header area of the form. To override the those dates, enter dates in these fields and click Find. The system displays transactions in the F09617 table that correspond to the statement dates that fall within the date or range of dates that you enter. To further limit the transactions that the system displays, enter values in the QBE row.
196
Chapter 20
To display the corresponding F0911 information, which is based on the general ledger date, leave the From Date and Thru Date fields blank in the Account Ledger region, or broaden the date range if necessary, and click Find. No. of Unreconciled Bank Statement Transactions (number of unreconciled bank statement transactions) Recon Code (reconciliation code) Displays the number of unreconciled transactions in the F09617 table that meet the criteria that you specified.
Displays the code from UDC table 09/RC that is used when you manually reconcile a transaction. The default value for this field is set in a processing option for the Manual Bank Statement Reconciliation program. You can override the default value. Displays the value stored in the CUSTREF (Customer Reference) field in the F09611 table which is mapped to the CKNU (Check Number) field in the F09617 table. This field allows up to 16 alphanumeric characters and accommodates reference numbers for receipts, payments, bank wire transfers, and so on. Select this check box to optionally update the Reference 3 field on journal entries that you manually reconcile. When you click Reconcile/Unreconcile to update the journal entries, the Reference 3 form appears with a reference number generated by next numbers. You can override the number with the bank statement number or any other number. Then, you can choose to update each selected F0911 record with the same reference number or with a different reference number. If you choose a different reference number, the system displays the Reference 3 form for each transaction. Select the transactions to reconcile and click the Reconcile/Unreconcile button, which is a toggle. For transactions that you manually reconcile, the system updates either or both of these tables: F09617: Updates the reconciliation code and displays the reconciled transactions. If the transactions remain in the F09611 staging tables, they are updated as reconciled. F0911: Updates the reconciliation code and, if applicable, the Reference 3 field and displays the reconciled transactions in the Account Ledger region of the form. After you reconcile all unreconciled transactions in the F09617 and F0911 tables, the system marks the header record in the F09616 table with D (reconciled). If all transactions in the F09611 table are reconciled, the system updates the header record in the F09610 table with D.
Payment/Receipt Number
Reconcile/Unreconcile
Account Ledger
The system displays general ledger transactions from the F0911 table that correspond to the account number and date range specified in the header area of the form.
197
Chapter 20
Displays general ledger transactions based on the beginning and ending dates that you entered in the header area of the form. To override the dates in the header, enter dates in these fields and click Find. The system displays transactions in the F0911 table that correspond to the general ledger dates that fall within the date or range of dates that you enter. To further limit the transactions that the system displays, enter values in the QBE row.
No. of Unreconciled G/L Transactions (number of unreconciled general ledger transactions) Debit and Credit Book Balance Bank Balance
Displays the number of unreconciled transactions in the F0911 table that meet the criteria that you specified.
Displays the unreconciled debit and credit amounts from the F0911 table for the bank account. Displays the year-to-date balance amount from the F0902 table. Displays the ending balance amount of the latest bank statement for the account from the F09616 table. This ending balance is used as the bank account
198
Chapter 20
opening balance by the Cash Forecast Analysis program when calculating cash forecast amounts for an account, if a processing option is set accordingly. See Chapter 24, Processing Cash Forecast Data, Understanding Bank Account Opening Balances, page 257.
Select
Bank Statement Beginning Date and Bank Statement Ending Date Specify the date range in which to purge records from the F09610 and F09611 staging tables. The system uses these processing options to locate the available records.
199
Chapter 20
If you leave the beginning date blank, all records with a statement date that is on or before the ending date will be purged. If you leave the ending date blank, all records with a statement date that is on or after the beginning date will be purged. If you leave both the beginning and ending dates blank, all records will be purged.
Print
Report Output Specify whether to print the purged records on the Purge Staging tables report (R09610). Values are: Blank: Do not print records. The report prints the bank statement number, general ledger bank account number, statement date, number of detail records, and the total number of records purged. 1: Print records. The report prints detailed information about the records purged.
Setting Processing Options for Purge Automatic Bank Statement Tables (R09615)
Use these processing options to select the date range and the type of information to print on the purge report.
Select
Bank Statement Beginning Date and Bank Statement Ending Date Specify the date range in which to purge records from the F09616 and F09617 bank statement tables. The system uses these processing options to locate the available records. If you leave the beginning date blank, all records with a statement date that is on or before the ending date will be purged. If you leave the ending date blank, all records with a statement date that is on or after the beginning date will be purged. If you leave both the beginning and ending dates blank, all records will be purged.
Report Output
Report Output Specify whether to print the purged records on the Purge Auto Bank Statement Tables report (R09615). Values are: Blank: Do not print records. The report prints the bank statement number, general ledger bank account number, statement date, number of detail records, and the total number of records purged. 1: Print records. The report prints detailed information about the records purged.
200
CHAPTER 21
Creating Budgets
This chapter provides overviews of budgets and budget patterns and discusses how to: Create budget pattern codes. Change budget pattern codes for a group of accounts. Enter annual budgets. Spread annual budget amounts to periods. Generate budget worksheets. Review budget comparisons online. Manage budget overages. Enter detailed budget amounts. Enter journalized budgets.
See Also
Chapter 23, Forecasting and Planning Budgets, page 239
Understanding Budgets
Budgeting provides a projection of future expenses and revenues. Using budget history, you can compare actual amounts to your projections and use the information to improve your budgeting process. You can enter annual budget amounts by business unit or account. Entering amounts by business units creates a budget by department, location, project, and so on. Entering amounts by account creates a budget that crosses business unit boundaries. To review budgets, use an online review or a printed budget worksheet. With an online review, you can compare budget amounts with actual amounts. With the budget worksheet report, you can: Review your requested, approved, and final budgets for the next year. Compare budget amounts against actual amounts and projected amounts for the current year, and against actual amounts from the previous year. Show a projected amount and the percentage that the budget amount varies from the projected amount.
Budget Methods
To create a budget, use one of these methods:
201
Creating Budgets
Chapter 21
Description Enter annual budget amounts. Using the spread program, the system allocates budget amounts to periods, based on budget pattern codes that you assign. This method updates the Account Balances table (F0902) directly. Enter a budget amount for each period for selected accounts, or for selected periods and accounts. This method does not provide a formal audit trail, but it directly updates each period budget in the F0902 table. Enter journal entries to a budget ledger to provide a formal audit trail. This method updates the F0911 table. You must post entries to update the F0902 table. Construction companies that use cost accounting and government agencies that record supplemental appropriations for the original budget typically need a formal audit trail. Journalized budgeting consists of entering, reviewing, and posting the journalized budget entries.
Journalized budgets
Use a spreadsheet program to create budgets and then transfer them to the F0902 table. Then use JD Edwards EnterpriseOne General Accounting programs to process your budget data. For example, you can spread annual budget amounts to your fiscal periods. Create budgets using allocations. See Chapter 15, Reconciling Bank Account Transactions, Reconciling Voided Payments and Receipts, page 139.
Allocations
See Also
Chapter 38, Closing the Fiscal Year, Understanding the Fiscal Year Close for Budget Ledger Types, page 438
202
Chapter 21
Creating Budgets
Description If your revenues and expenses occur in a predictable pattern, you can set up seasonal pattern codes to describe each pattern. For each code, enter the percent of the total annual budget to be spread to each period. If you do not want to spread an annual amount to periods for an account, you can bypass spreading amounts for that account.
No spread
The default budget pattern for the code blank evenly spreads an annual budget equally among periods; however you can change the instructions for the code blank. You should assign the most common budget pattern the code of blank. For example, is your company rarely needs to spread an annual budget equally among the months, you can use the budget pattern code of blank to identify a seasonal pattern code that you frequently use, which speeds data entry of that code. You do not need to define budget pattern codes if your company performs any of these tasks: Creates only annual budgets (no monthly budgets). Manually creates monthly budgets for all accounts. Creates annual budgets for all accounts with the annual amount being spread equally among the periods.
203
Creating Budgets
Chapter 21
FormID
Navigation Budgeting (G1412), Revised Seasonal Patterns On Work with Budget Patterns, click Add.
Usage Review a list of existing budget pattern codes. Create a budget pattern code.
Budget Pattern
Enter a unique three-character code that identifies a seasonal budget pattern. The system uses this code to calculate budget amounts for an accounting period. For example, you could enter SUM or WIN to identify a seasonal pattern code or blank to evenly spread an amount among all periods. For a seasonal pattern code or the DNS budget pattern code, enter a number that identifies the percentage of the total annual budget assigned to the period. You can enter:
Period 01Period 14
204
Chapter 21
Creating Budgets
Whole numbers. For example, 20 for 20 percent. Decimal numbers up to four decimals. For example, .3333 for 33.33 percent. The system rounds more than four decimals to four decimals. Zero (no percentage for the period). For the DNS budget pattern code and each seasonal pattern code, the total of all percentages must equal 100 percent. Note. The default periods for the fiscal year are set up for company 00000 on the Date Pattern Revisions form.
FormID
Usage Change an existing budget pattern code for a group of accounts within a business unit or company.
205
Creating Budgets
Chapter 21
These two fields identify a range of object accounts. If you specify an account in the From Account field, you must also specify an account in the Thru Account field. If you leave the From Account field blank, the default is 0000. If you leave the Thru Account field blank, the default is 9999.
In the Old Code field, enter the three-character code that identifies the seasonal pattern that you want to change. In the New Code field, enter the three-character code that identifies the seasonal pattern that replaces the code in the Old Code field. Three asterisks (***) represent a blank value. To change a blank value to a new value, enter *** in the Old Code field. You can also enter *** in the New Code field to change an existing value to a blank value. Enter * in the Old Code field to change all of the old budget pattern codes to the value that you enter in the New Code field. Enter DNS in the Old Code field to change budget pattern codes from do not spread or in the New Code field to change to do not spread.
206
Chapter 21
Creating Budgets
207
Creating Budgets
Chapter 21
Updates Update requested budget, approved budget, and final budget. Update approved budget and final budget. Update final budget.
The table shows how the system updates amounts in the F0902 during each cycle:
Cycle Cycle 1 Cycle 2 Cycle 3 Requested (BREQ) 7,000 not applicable not applicable Approved (BAPR) 7,000 6,000 not applicable Final (BORG) 7,000 6,000 5,000 Description of Update The system updates the requested, approved, and final amounts. The system updates the approved and final amounts. The system updates the final amount, which represents the annual amount to be spread.
Prerequisite
Decide whether to enter budget amounts by business unit or by account across all business units.
208
Chapter 21
Creating Budgets
FormID
Navigation Budgeting (G1412), Requested by Business Unit, Approved by Business Unit, or Final by Business Unit
W14102B
On the Work with Budgets Enter budgets by business form, select the business unit. unit and assign budget pattern codes to individual accounts. Budgeting (G1412), Requested by Account, Approved by Account, or Final by Account On the Work with Budget Accounts form, select the account. Review a list of accounts by company.
Budget by Account
W14103A
Enter and revise budgets by account and assign budget pattern codes to individual accounts. You can also interactively spread annual budget amounts to periods. See Chapter 21, Creating Budgets, Spreading Annual Budget Amounts to Periods, page 212.
Setting Processing Options for Requested by Business Unit (P14102) and Requested by Account (P14103)
The processing options for the Requested, Approved, and Final by Business Unit and the Requested, Approved, and Final by Account programs are the same, with the exception of the name of the first tab.
Spread Budget
4. Rounding Increment Specify the rounding increment to use for amounts. For example:
209
Creating Budgets
Chapter 21
Blank: Round amounts to the smallest currency unit for the company. 1.00: Round amounts to the nearest 1.00 10.00: Round amounts to the nearest 10.00 The results of rounding will be exactly divisible by the value that you enter for this processing option. 5. Balancing Method Specify the balancing method. Values are: Blank: Do not force the total of the rounded period amounts to be equal to the annual budget amount. 1: Force a balanced spread by rounding the final budget amount. 2: Force a balanced spread by not rounding the last calculated period amount.
210
Chapter 21
Creating Budgets
Enter the three-character budget pattern code. Select this check box to display the period amount fields, which enable you to manually enter budget amounts on a period-by-period basis. To access the Period fields, scroll to the right if necessary. If you do not select this check box, the system automatically spreads the amount among the fields for the accounting periods.
Select this check box to interactively change the processing options for budget spread. Then from the Form menu, select Options. Select one of these options based on whether you want to enter or update a value in the Requested Amount, Approved Amount, or Final Amount field. If you select the Requested option, the system updates the BREQ field and, to expedite entry of the final budget, the BAPR and BORG fields in the F0902 table.
211
Creating Budgets
Chapter 21
If you select the Approved option, the system updates the BAPR field and, to expedite entry of the final budget, the BORG field in the F0902 table. Budg Patt (budget pattern) Enter a code that specifies how to spread budget amounts. If you enter DNS, you must manually enter the amounts for each period. With the Show Periods check box selected, access the Period fields by scrolling to the right. Alternatively, select Detail from the Row menu to access the Detailed Budget by Account form and manually enter the amounts. Requested Amount, Approved Amount, and Final Amount Enter a value in one of these fields. The field that is input capable depends on whether you selected the Requested, Approved, or Final option. If you entered DNS in the previous field, these fields are not input capable.
212
Chapter 21
Creating Budgets
Spread annual budget amounts to periods during budget entry. Run the Spread Annual to Periods program. Set processing options for Spread Annual to Periods (R14801).
213
Creating Budgets
Chapter 21
Description Blank is the default value for annual amounts that are to be evenly spread. The system spreads the annual budget amount for the account equally among the periods. For a 12-month calendar year, the program assigns 1/12 (8.33 percent) to each period. Note. If your company changes the meaning of the blank pattern code, the system divides the annual amount by the percentages that you specify. To spread annual amounts to periods, the system uses information from the Budget Patterns (F1401), Account Master (F0901), and Account Balances (F0902) tables.
Seasonal DNS
The system spreads the annual amount according to the percentages and periods that you specify for a seasonal budget pattern code. If you enter budgets manually, the system does not spread annual amounts to accounts assigned pattern code DNS. You must manually enter an amount for each period on the Budgets by Business Unit or Budgets by Account form. If you run the Spread Annual Periods program, the system spreads annual amounts evenly among the periods only if the Override Budget Do Not Spread Code is selected on the Ledger Type Rules Setup form. If the Override Budget Do Not Spread Code check box is not selected, the program does not spread the annual budget amounts. Instead, you must manually enter them.
214
Chapter 21
Creating Budgets
Budget Spread
1. Rounding Increment Specify the rounding increment to use for amounts. For example: Blank: Round amounts to the smallest currency unit for the company. 1.00: Round amounts to the nearest 1.00 10.00: Round amounts to the nearest 10.00 The results of rounding will be exactly divisible by the value that you enter for this processing option. 2. Balancing Method Specify the balancing method. Values are: Blank: Do not force the total of the rounded period amounts to be equal to the annual budget amount. 1: Force a balanced spread by rounding the annual budget amount prior to spreading the amounts. 2: Force a balanced spread by not rounding the last calculated period amount.
215
Creating Budgets
Chapter 21
Consolidate information if you have a consistent account structure and level of detail across all companies and business units. The Budget Worksheet program uses AAI items FSxx to determine where to print interim total. Some examples for FSxx include: FS04: Gross margin FS05: Operating income FS99: Net income (loss) Depending on how you set the processing options, the Budget Worksheet provides this type of information:
Type of Report Comparisons Description Compares amounts for any level of detail, such as: Ledger type AA (actual amounts) for the prior year. Actual and projected amounts for the current year. Actual and budget year-to-date amounts for the current year and actual year-to-date amounts for prior years. Projections Calculates balances for the year end, such as: Actual amounts plus the remaining budget. Remaining budgets. Actual amounts divided by the percentage complete (Job Cost). Estimates the annual budget for the next year. For example, you can print the actual amounts from the previous year and the projected amounts for the current year, and leave the annual budget amount columns blank to make manual entries. Variances Shows percentages of difference or change between actual amounts and budget amounts. The calculation is based on projected budget amounts.
216
Chapter 21
Creating Budgets
Object account (required) Subsidiary account (required) If you do not specify a company or business unit as the first item in the sequence, the system uses the current fiscal period for company 00000. To print a report for a business unit, or one that consolidates all business units or companies, enter one of these data sequences:
Type of Report Business unit Business unit consolidation Company consolidation Data Sequence Business unit, object account, subsidiary account. Company, object account, subsidiary account. Object account, subsidiary account.
Important! If you change the data sequence, a sequence other than one of the previous sequences can produce undesirable results.
Date
1. Period Number and Fiscal Year Enter the fiscal period and year. If you leave these processing options blank, the financial reporting date for the company is used. For the reporting date to be company-specific, you must use the data sequence to sequence your report by company.
Ledger Types
1. Actual Ledger Type 2. Budget Ledger Type Specify the ledger type from UDC table 09/LT to use for the actual columns. If you leave this processing option blank, the system uses ledger type AA. Specify the ledger type from UDC table 09/LT to use for the budget columns. If you leave this processing option blank, the system uses ledger type BA.
LOD
1. Level of Detail Specify the lowest account level of detail (39) that you want to print. If you leave this processing option blank, the system uses 9.
Signs
1. Reverse Sign Specify how to print amounts. Values are: 0: Print amounts in their original debit and credit format. 1: Reverse the signs on amounts for income statement accounts. Revenues print as positive and expenses print as negative.
217
Creating Budgets
Chapter 21
2: Reverse the sign on amounts for balance sheet accounts. All accounts print as positive. 3: Reverse the sign on amounts for revenue and expenses. Revenues and expenses print as positive. The program uses AAI item GLGx to determine whether liabilities and expense accounts print with a negative sign.
Computations
1. Net Income Computation Specify how to compute net income. Values are: Blank: Do not compute. 1: Compute balance sheet net income. 2: Compute profit/loss net income. 2. Projected Calculation Specify how to calculate projected budget. Values are: Blank: Do not calculate. 1: Actual + Remaining Budget. 2: Actual / Percent Complete. 3: Remaining Budget.
Headings
Print Headings Specify how to print headings on the worksheet. Values are: blank: Print headings on first page only. 1: Print page headings with page number and run date on each page. 2: Print page headings without page number and run date on each page. Date Title Type Enter the date title type to print in the page headings. If you leave this processing option blank, no date title prints.
218
Chapter 21
Creating Budgets
See Also
Chapter 31, Reviewing Balances and Transactions, Reviewing Trial Balances, Ledgers, and Subledgers, page 339
Usage Review budget comparisons online. Review summarized trial balance information for two different ledgers and for a specific account or for all accounts within a business unit.
Default
1. Ledger Type 1 and 2. Ledger Type 2 Specify which two ledger types you want to compare online. If you leave the Ledger Type 1 processing option blank, the system uses BA as the default value. If you leave the Ledger Type 2 processing option blank, the system uses AA. Values are: Blank or 1: Ledger type 1. 2: Ledger type 2.
Display
1. Suppress Zero Balances Specify whether to suppress zero balances. Values are: Blank or N: Do not surprise zero balances. That is, display accounts with zero balances. Y: Suppress zero balances. That is, do not display accounts with zero balances.
219
Creating Budgets
Chapter 21
2. Calculation Method
Specify the method to use to calculate the differences between the two ledgers: Blank or S: Subtraction A: Addition M: Multiplication D: Division
3. Additional Ledger Type 1 and 4. Additional Ledger Type 2 5. Subledger and 6. Subledger Type 7. Account Level Of Detail
Specify additional ledgers for ledger type 1 and ledger type 2. If you leave these processing options blank, the system does not display additional ledger types. Specify a specific subledger and subledger type in which to display balances. If you leave these processing options blank, the system uses the blank subledger and type. Specify the lowest account level of detail (39) that you want to display. If you leave this processing option blank, the system displays level of detail 9.
Currency
1. Currency Code Specify the default currency code to display. If you leave this processing option blank, the system displays all currencies.
Select
1. Date Effective Balances Specify which dates to use for the date effective balances: Values are: Blank or N: Use period end dates. Y: Calculate date effective balances. 2. Default Thru Period Display Specify whether to display a date or a period. Blank or N: Display thru dates. Y: Display thru periods.
220
Chapter 21
Creating Budgets
221
Creating Budgets
Chapter 21
Generates an exception report that lists the unposted transactions in the F0911 table that will cause budget overages. The exception report is for information only and is sequenced by company, account, and detail. The G/L Budget Checking Report does not update any tables.
222
Chapter 21
Creating Budgets
Ledger Type
1. Primary Ledger 2. Secondary Ledger 3. Third Ledger Enter the budget or primary ledger to use for calculations. If you leave this processing option blank, the system uses BA. Enter the second ledger to use for calculations. If you leave this processing option blank, the system uses PA. Enter the third ledger to use for calculations. If you leave this processing option blank, the system uses AA.
Budget Year
1. Fiscal Year Enter the budget year. If you leave this processing option blank, the system uses the current fiscal year.
Calculation Methods
1. Budget Totaling Method Specify the budget totaling method to use. Blank or 1 The total original budget, period amounts for the year, and prior year end posting amounts. 2: The total period amounts for the year. 3: The total original budget and period amounts through the current period. Specify method 1 or 3 only if the original budget has not been spread to periods.
LOD
1. Level of Detail Specify the lowest account level of detail (39). If you leave this processing option blank, the system uses 9. The analysis of accounts occurs at a level no higher than the designated level of detail. For example, if you specify the level of detail 5, the report assumes that all of the budgets are at a level no higher than 5. The exception is level 9. If you specify level 9, the analysis of accounts includes all accounts.
Subledger
1. Subledger and 2. Subledger Type Enter a specific subledger or * for all subledgers. If you enter a specific subledger, enter the subledger type.
223
Creating Budgets
Chapter 21
224
Chapter 21
Creating Budgets
225
Creating Budgets
Chapter 21
Budget entries for a journalized budget are the same as journal entries, but you assign a budget ledger type. You create the budget by entering budget amounts as journal entries, which you then review and post like other journal entries. Batches with budget entries have the same batch type (G) as other journal entries. The system updates journalized budgets in the F0911 table. When you post the batch, the system updates the F0902 table. However, the system does not update the budget amount fields BREQ, BAPR, and BORG in the F0902 table. To change a budget that you entered as a journalized budget, you must use the Journal Entry form. Do not use the annual or detailed budget method to change a journalized budget entry. Budget journal entries typically do not have to be in balance. You specify whether your budget ledgers are required to balance in the Ledger Type Master Setup program (P0025).
Prerequisites
Before you complete the tasks in this section: Specify a budget ledger type, such as BA, in the processing options. Verify that you have set up your fiscal date patterns. (Recommended) Set up a document type, such as BX, for budget journal entries instead of using document type JE.
See Also
Chapter 11, Processing Journal Entries, Entering Basic Journal Entries, page 90
FormID
Navigation Other Budgeting Methods (G1421), Budget Entry On the Work With Journal Entries form, click Add.
Usage Review a list of existing batches of budget journal entries. Add journal entries for budget amounts.
Journal Entry
W0911A
226
CHAPTER 22
227
Chapter 22
Navigation
Usage
Other Budgeting Methods Review a list of existing (G1421), Upload/Conversion batches that have been Revisions uploaded to the F0902Z1 table. On the Work With Batch Account Balances form, select Upload Records from the Form menu. If necessary, you can delete all records regardless of whether they have been processed by selecting Delete All from the Form menu. Import budget data from a spreadsheet. This uploads the budget data to the F0902Z1 table.
Default
1. Ledger Type 2. User ID Field Specify the ledger type from UDC table 09/LT to use for the budget amounts. Specify whether to enable the User ID field. Values are: Blank: Disable the field. 1: Enable the field.
Account Number
1. Account Number Specify the format to use for the account number: Values are:
228
Chapter 22
1: Short account ID. 2: 3rd account number. 3: Long account number. Blank or 4: Business unit, object, and subsidiary.
1. On Upload Records to F0902Z1, select Import Grid Data from the Tools menu. 2. Select an option under the Import Options heading. If you import from Excel, complete the next step. Otherwise, continue to step 4. 3. Click Browse to locate the excel file and enter the worksheet name from which to import data. 4. Specify a range of cells from which to import data (for example, A1:B10) under the Define Cell Range heading:
229
Chapter 22
Prerequisites
Create a folder called Import in the B9/PROD directory, or wherever your EnterpriseOne directory resides.
230
Chapter 22
7,Net Posting 8,Net Posting 9,Net Posting 10,Net Posting 11,Net Posting 12, Net Posting 13,Net Posting 14,Requested,Approved,Final 1.1110.Bear,1,A,1000,100,10,1,0,0,0,0,0,0,0,0,0,0,0,1110,0 1.1110.Fib,1,A,2000,200,20,2,0,0,0,0,0,0,0,0,0,0,0,200,0 1.1110.France,,,3000,300,30,3,0,0,0,0,0,0,0,0,0,0,5000,0,0 1.1105,,,0,52,12313,13213,0,0,0,0,0,0,0,0,0,6589
The budget data appears after the column headings in the text file.
231
Chapter 22
When the program finishes, it sends a message to the work center that indicates whether the batch process completed successfully.
Ledger Type
1. Ledger Type Specify the ledger type for the system to assign to the budget records. Enter a valid ledger type from the Ledger Type Master Setup program (P0025). If you leave this processing option blank, the system uses ledger type BA.
Account Number
1. Account Number Format Specify the account number format that you used in the budget text file. Values are: blank or 3: Long account number. 1: Short account ID. 2: 3rd account number.
232
Chapter 22
Navigation
Usage
Other Budgeting Methods Review a list of existing (G1421), Upload/Conversion batches that have been Revisions uploaded to the F0902Z1 table. On the Work With Batch Account Balances form, select the record to revise. Revise a budget record. These are the budget records that have been imported to the F0902Z1 table.
W0902Z1B
233
Chapter 22
Run the Upload/Conversion program. Set processing options for Upload/Conversion (R14110).
234
Chapter 22
Period
1. Century and 2. Fiscal Year Use these processing options to identify the century and fiscal year that apply to the budget that you are uploading to the F0902 table. For example, if the budget is for fiscal year 2007, enter 20 for the century and 07 for the fiscal year.
Budget Cycle
You can update one, two, or all three of the budget cycles. 1. Requested Budget Specify whether to update the Requested Budget field (BREQ) in the F0902 from the budget that you are uploading. Values are: Blank: Do not update the field. 1: Update the field. If you enter 1 for this processing option and also enter 1 for the Annual/Monthly processing option, the system enters the requested budget amount from the budget that you are uploading in the BREQ field. If you enter 1 for this processing option and leave the Annual/Monthly processing option blank, the system totals the monthly budget amounts in the budget that you are uploading and enters the total in the BREQ field. 2. Approved Budget Specify whether to update the Approved Budget field (BAPR) in the F0902 table from the budget that you are uploading. Values are: Blank: Do not update the field. 1: Update the field. If you enter 1 for this processing option and also enter 1 for the Annual/Monthly processing option, the system enters the approved budget amount from the budget that you are uploading in the BAPR field. If you enter 1 for this processing option and leave the Annual/Monthly processing option blank, the system totals the monthly budget amounts in the budget that you are uploading and enters the total in the BAPR field. 3. Final Budget Specify whether to update the Final Budget field (BORG) in F0902 table from the budget that you are uploading. Values are: Blank: Do not update the field. 1: Update the field. If you enter 1 for this processing option and also enter 1 for the Annual/Monthly processing option, the system enters the final budget amount from the budget that you are uploading into the BORG field. If you enter 1 for this processing option and leave the Annual/Monthly processing option blank, the system totals the monthly budget amounts in the budget that you are uploading and enters the total in the BORG field.
235
Chapter 22
4. Annual/Monthly
Specify whether to upload annual budget amounts (requested, approved, and final) or monthly budget amounts (periods 114) to the F0902 table. Values are: Blank: Upload monthly budget amounts. 1: Upload annual budget amounts. If you enter 1 for this processing option, the system uploads only the annual budget amounts for which you entered 1 in the corresponding Budget Cycle processing options. If you leave processing option blank, the system uploads the monthly budget amounts. The system also totals the monthly budget amounts and enters the total in each annual budget field for which you entered 1 in the corresponding Budget Cycle processing options.
Replace Entries
1. Replace Entries Specify whether to replace the existing entries in the F0902 table with the entries from the budget that you are uploading, or add them. Values are: Blank: Replace existing entries. 1: Add entries.
Reverse Sign
1. Reverse Sign Specify whether to reverse the sign on the amounts in the revenue accounts for the budget that you are uploading. Reversing the sign means that negative numbers become positive numbers, and positive numbers become negative numbers. Values are: Blank: Reverse the sign on the amounts. If the amounts in the revenue accounts in the budget that you are uploading are positive numbers (debits), you must leave this processing option blank. The system will change the positive numbers to negative numbers during the upload. 1: Do not reverse the sign on the amounts; keep it as is. Amounts for revenue accounts in the F0902 table are negative numbers (credits). If the amounts in the revenue accounts in the budget that you are uploading are negative numbers, you must enter 1 in this processing option to keep them as negative numbers.
Job Cost
1. Job Cost Specify whether to update only the monthly budget amounts (periods 114) in the F0902 table from the budget that you are uploading, regardless of how you set the Budget Cycle processing options. Values are: Blank: Update the budget amounts that are specified in the Budget Cycle processing options. 1: Update only the monthly budget amounts. Enter 1 for job cost budgeting.
236
Chapter 22
Mode
1. Mode Specify whether to run the program in proof or final mode: Blank: Proof mode. The system prints a report of the changes that would be made to the amounts in the F0902 table. 1: Final mode. The system updates the F0902 table and prints a report.
Purge
1. Purge Specify whether to automatically purge processed transactions from the F0902Z1 table. Values are: Blank: Do not purge processed transactions. 1: Purge processed transactions.
237
Chapter 22
238
CHAPTER 23
239
Chapter 23
After you complete these tasks, you generate the budget amounts for a revision and then revise the amounts as necessary to achieve the desired results. When you are satisfied with the results, you copy the finalized budget amounts to the F0902 table for each revision. From the F0902 table, the records can be incorporated with budgets from other systems for reporting purposes. You must forecast budgets using the forecasting and planning programs before you can use the standard budget programs. This graphic illustrates the forecasting and planning process and the tables that the system uses during the process:
Set up and assign growth patterns
F1403
F0902
240
Chapter 23
You can do this manually with a search and select program or automatically with a batch program using one of these programs: Revise Forecast Basis (P1403) Generate Forecast Basis (R1403) Regardless of whether you define accounts and retrieve basis amounts manually or generate them automatically, the system copies account information from the F0901 table and net posting amounts from the F0902 table and updates the Forecast Basis table (F1403).
FormID
Navigation Forecasting and Planning (G1411), Revise Forecast Basis On the Work With Forecast Basis form, click Add.
Usage Locate and select existing forecast basis records. Define accounts and retrieve basis amounts.
W1403B
241
Chapter 23
To manually define accounts and retrieve basis amounts: 1. On Retrieve Forecast Basis, complete the header fields. 2. Select the Roll Up Subledger Balances option to roll up subledger balances into the object account total. 3. To retrieve accounts for the same ledger type or a different ledger type and different fiscal year, enter values in these fields: Ledger Type Fiscal Year From Period Thru Period Note. The From Period and Thru Period fields for the two ledger types cannot overlap. For example, assume the first ledger type is AA, the fiscal year is 05, and the from and thru periods are 712. The second ledger type must be for a different range of periods. For example, you could enter 16 for the from and thru periods. This flexibility enables you to retrieve amounts for the last six months of one year and the first six months of the next year, the last three months of one year and the next nine months of the next year, and so on. 4. Click Find. The system retrieves the accounts and displays the balances for each period in the detail area of the form. 5. Select the View Net Postings check box to view the net period postings for each period.
242
Chapter 23
6. Revise any basis amounts in the detail area. 7. To save individual records, select the records and then select Save from the Row menu. 8. To save all records, select Save All from the Form menu. 9. On the Message form, click OK to replace existing unlocked accounts in the F1403 table.
Process
1. Revision Number Specify the revision number in which to generate forecast basis amounts. The system copies account information from the F0901 table and net posting amounts from the F0902 table and updates the F1403 table for the revision number. Specify the ledger type in which the system retrieves net posting amounts in the Ledger Type 1 processing option. This processing option works in conjunction with the Fiscal Year 1, From Period 1, and Thru Period 1 processing options. Optionally specify a second ledger type in which the system retrieves net posting amounts in the Ledger Type 2 processing options. This processing option works in conjunction with the Fiscal Year 2, From Period 2, and Thru Period 2 processing options. Specify whether to roll up subledger balances into the object account. Values are: Blank: Do not roll up subledger balances. 1: Roll up subledger balances. For example, if you specify 1 for this processing option and you use subledgers to track travel expenses by employee, the system will roll up the travel expenses for all employees into the object account.
2. Ledger Type 1, 3. Fiscal Year 1, 4. From Period 1, and 5. Thru Period 1. 6. Ledger Type 2, 7. Fiscal Year 2, 8. From Period 2, and 9. Thru Period 2 10. Roll Up Subledger
243
Chapter 23
Spread an amount over an account using a budget pattern code. If you have budget pattern codes set up, you can assign the code and an override amount and the system will spread the override amount to the amount field for each period, according to the percentages defined for the budget pattern code. Assign override growth pattern codes to individual accounts. Lock records. The Generate Forecast Results program forecasts amounts for locked records only. The Lock Account flag (LOCKFLG) must equal 1 in the F1403 table.
FormID
Navigation Forecasting and Planning (G1411), Revise Forecast Basis On the Work With Forecast Basis form, select the business unit and revision number that you want to revise.
Usage Review existing forecast basis records. Revise accounts and basis amounts.
W1403D
244
Chapter 23
1. On the Forecast Basis Revisions form, select one of these options: Display Periods Annual Total Only 2. To change the period basis amounts for an account, select the Display Periods option and complete the Basis Amount Period fields for the applicable periods. The system updates the amount in the Basis Amount Year Total field accordingly. 3. To spread an amount over an account using a specific budget pattern and amount, complete these fields in the detail area: Budg Patt If you leave this field blank, the system spreads annual budget amounts evenly across all months. Override Amount Enter a value in this field only if you entered a non-blank value in the Budg Patt field. 4. To override the growth pattern for an account, complete the Override Growth Pattern Code field in the detail area. Enter a value in this field for an account only if you do not want the system to use the default growth pattern. The system applies the growth pattern when you run the Generate Forecast Results program. 5. To lock an account record, select the record and then select Lock from the Row menu. The number 1 appears in the Lock Account field to identify the account as locked. To toggle between locking and unlocking an account, select Lock again from the Row menu. 6. To lock all account records, select Lock All from the Form menu. To toggle between locking and unlocking all accounts, select Lock All again from the Form menu. 7. Click OK to accept all revisions. Note. The Generate Forecast Results program generates budget forecast amounts only for locked records in the F1403 table.
245
Chapter 23
You can generate budget forecast amounts up to fifteen years in the future. You specify the fiscal year to begin generating the amounts and the revision number in the processing options. You use data selection to specify the account ranges and business units in which to generate the budget forecast records. The Generate Forecast Results program: Uses the basis amounts that were retrieved and updated in the F1403 table. Applies the growth pattern to the basis amounts for accounts with any posting edit code except N (non-posting). The growth pattern includes the default pattern associated with the business unit and revision number and any override growth patterns associated with individual accounts. Generates forecast amounts only for accounts in the F1403 table that are locked. The Lock Account flag (LOCKFLG) in the F1403 table must equal 1. The data selection for the program is hard coded to select only locked records. This program produces a report that shows the revision number, fiscal year, and number of years to forecast, as well as the number of records that were added and updated in the F1404 and F14041 tables. The report also includes the number of records that failed, if applicable, and sends error messages to the work center. The report does not identify any accounts that are unlocked. Unlocked accounts are not included in the forecast amounts. After you run the Generate Forecast Results program, you can either: Revise the accounts and basis amounts in the F1403 table, if necessary. You must unlock the records using the Revise Forecast Basis program, change the records, and lock the records again. Then, rerun the Generate Forecast Results program to override existing unlocked records in the F1404 and F14041 tables. Review and revise the budget forecast amounts in the F1404 and F14041 tables using the Revise Forecast Results program.
Prerequisite
Ensure that all accounts associated with the business unit and revision number are locked.
246
Chapter 23
Process
1. Revision Number Specify the revision number in which to generate budget forecast amounts. The system applies a growth pattern to the basis amounts and updates the header and detail records in the F1404 and F14041 tables. Specify the first fiscal year in which to generate budget forecast amounts. For example, to generate amounts beginning with the year 2005, enter 05. Specify the number of years in which to generate budget forecast amounts. This processing option is used in conjunction with the Start Fiscal Year processing option. For example, if you enter 05 in the Start Fiscal Year processing option and enter 10 in this processing option, the system generates forecast amounts for 20052015. You can forecast amounts up to 15 years in the future.
247
Chapter 23
W1404B
Revise, lock, and unlock budget forecast amounts for an account for a single year. Revise, lock, and unlock budget forecast amounts for an account for multiple years.
W1404C
You might need to replace or delete a record if you add new records for a range that includes the account number on an existing record.
248
Chapter 23
Change amounts in these fields, as necessary. When you change amounts, the system automatically enters DNS (do not spread) in the Budget Pattern Code field. The amounts in the Forecast Amount Period 112 fields must equal the total amount in the Annual Forecast field. If they are not equal, the system issues the error message Amounts Not Equal. Review the Remaining Amount field and correct the amounts accordingly.
If you are revising a single year, the Lock Account option appears. If you are revising multiple years, the Lock All Fiscal Years option appears. You can select this option to toggle between locking and unlocking an account or fiscal years. Select the option to lock the record. You cannot revise it. Clear the option to unlock the record and revise it.
249
Chapter 23
Prerequisite
Verify that the ledger type to which you want budget forecast records copied is set up in UDC table 09/LT and in the F0025 table.
Budget Ledger
1. Budget Ledger Type Specify the ledger type in which to update budget forecast records. This ledger type must exist in UDC table 09/LT and the F0025 table. The system copies finalized amounts from the F1404 and F14041 tables and updates the F0902 table for the ledger specified in this processing option. Specify a code from UDC table H00/BC. Values are: 1: Update Requested Budget Ledger. 2: Update Approved Budget Ledger. 3: Update Final Budget Ledger.
250
Chapter 23
Running the Purge Forecast Basis and Purge Forecast Results Programs
Select Advanced and Technical (G14111), Purge Forecast Basis or Purge Forecast Results.
Setting Data Selection for Purge Forecast Basis and Purge Forecast Results
If you do not want to purge all records, use data selection to select a specific revision number, business unit, and so on. These purge programs does not have process options. There is no proof or final mode.
251
Chapter 23
252
CHAPTER 24
See Also
Chapter 7, Setting Up Cash Forecasting, page 57 JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Understanding Cash Forecasting in Multiple Currencies
253
Chapter 24
Refresh the F09522 table with new cash forecast records. For each cash type, the Refresh Cash Forecast Data program refreshes the F09522 table with summarized amounts for active cash types by bank account and due date. If more than one bank account or due date meets the selection criteria for a cash type, the program produces multiple summarized amounts. For each unique bank account ID in the F09522 table, the Refresh Cash Forecast Data program creates a bank account record in the F09525 table. The system accesses information in the F09525 table if you use the Search button to locate a bank account number on the Cash Forecast Analysis form. If no bank accounts exist in the F09525 table, the system accesses account master information in the F0901 table instead. You can set a processing option to purge existing cash forecast records for prior based-on dates. The system purges the data in the F09522 table before it refreshes the table with the new cash forecast data. The Cash Forecast Data Refresh program refreshes the F09525 table with bank accounts from all GL cash type rules, and not only for cash type rules in the reporting structure. Note. If you make changes to your data and need to run the Refresh Cash Forecast Data program more than one time in a given day, you must run the Purge Cash Forecast Data program (R09522B) from the menu only before you run the refresh program again. See Chapter 24, Processing Cash Forecast Data, Understanding the Cash Forecast Purge, page 259.
Extract A/R Cash Forecast Data and Extract A/P Cash Forecast Data Programs
The Extract A/R Cash Forecast Data program extracts open invoices with amounts that are not equal to 0, pay status A (approved), and a posted code D (posted) for active AR cash type rules from the F03B11 table. The Extract A/P Cash Forecast Data program extracts open vouchers with amounts that are not equal to 0 and a pay status that is not equal to P (paid) for active AP cash type rules from the F0411 table. To determine which open invoices and vouchers to include in your cash forecast data, you specify a based-on date and a future number of days in the processing options. Invoices and vouchers with due dates that are between the beginning and ending dates are included in your cash forecast data. Depending on whether a cash type has the Past Due option selected, one of these situations applies: If a cash type has the Past Due option selected, the program chooses due dates that are less than the based-on date specified in a processing option: The program adjusts the based-on date by the negative beginning number and the negative ending number of past due days to derive the most recent past due date and the oldest past due date, respectively. The program selects transactions with due dates that are less than or equal to the most recent past due date as well as transactions that are greater than or equal to the oldest past due date and writes new AR and AP cash forecast records to the F09522. If a cash type does not have the Past Due option selected, the program chooses due dates that are greater than or equal to the based-on date specified in a processing option and less than or equal to the ending date and writes new AR and AP cash forecast records to the F09522.
254
Chapter 24
The program repeats this process until it has written records for the bank accounts for all days greater than or equal to the based-on date and all days less than or equal to the ending date. Then, it resets the adjusted date to the based-on date and repeats the process for the next GL cash type. If the program finds an account with a zero balance, it writes the zero balance to the F09522 table for the based-on date. The program always writes the based-on date balance for each bank account to the F09522 table. This balance is used as the beginning book balance for the bank account, even if it is zero. However, for subsequent adjusted dates after the based-on date, the program does not write records to the F09522 table for an adjusted date if the F0911 transactions are not posted. The program writes net F0911 amounts for adjusted dates to the F09522 table only if there are posted F0911 transactions for that specific date. When you access the Cash Forecast Analysis program, any F0911 net amounts on adjusted dates are accumulated and applied to one of these balances: The based-on date book balance in the F09522 The based-on date bank statement balance in the F09616 and F09617 tables. You specify the based-on date to use for the opening balance in a processing option for the Cash Forecast Analysis program.
Process
1. Based On Date Specify the based-on date, or beginning date, for which to create cash forecast data in the F09522 table. If data for the based-on date already exists in the F09522 table, use the Purge Cash Forecast Data program (R09522B) to purge the existing data before you create new cash forecast data. If you leave this processing option blank, the system uses todays date for the based-on date. Specify the future number of days in which to create cash forecast data. For example, if you specify 10, the system creates cash forecast data from (and including) the based-on date through the next 9 calendar days. If you leave this processing option blank or specify 0, the system creates cash forecast data from (and including) the based-on date through the next 6 calendar days.
Version
1. A/R Cash Forecast Data Extraction Version (R03B522), 2. A/P Cash Forecast Data Extraction Version (R04522), and 3. G/L Cash Forecast Data Extraction Version (R09522) Specify the versions to use for the Extract A/R Cash Forecast Data, Extract A/P Cash Forecast Data, and Extract G/L Cash Forecast Data programs. If you leave any of these processing options blank, the system uses version ZJDE0001.
255
Chapter 24
Purge
1. Prior Number of Days Specify the prior number of days in which to begin purging cash forecast records. If you specify 10, all cash forecast records with based-on dates prior to 10 days from the based-on date will be purged. For example, if the based-on date is June 14, all cash forecast records with based-on dates June 4 and before will be purged. If you specify 1, all records with based-on dates prior to today will be purged. If you leave this processing option blank or specify 0, no records will be purged.
256
Chapter 24
Prerequisites
Before you complete the tasks in this section: Run the Refresh Cash Forecast Data program to update the F09522 table. In the processing option for the Cash Forecast Analysis program, specify the name of the reporting structure in which you want to view cash analysis information.
FormID
Navigation Cash Forecasting (G09319), Cash Forecast Analysis To print the Cash Forecast Analysis report, select Print from the Report menu.
Display
1. Reporting Structure Specify the reporting structure that the system uses to display information in the Cash Forecast Analysis program. The reporting structure must exist in the F09523 table. A value for this processing option is required; do not leave it blank. Specify the number of date period columns (up to a maximum of seven, the default) to display on the Cash Forecast Analysis form. If specified in the Setup Cash Type Rules program, the system displays a Past Due column for past due items. Specify the revaluation currency to use to display amounts on the Cash Forecast Analysis form. The currency code must exist in the F0013 table. If you leave this processing option blank, the system uses the currency code for company 00000 from the F0010 table.
2. Number of Columns
3. Revaluation Currency
257
Chapter 24
Specify the company to use to retrieve the fiscal date pattern to calculate cash forecast amounts when the Time Period option in the Cash Forecast Analysis program is set to accounting period. If you leave this processing option blank, the system uses the fiscal date pattern and the fiscal year beginning date of company 00000.
Options
1. Bank Acct Opening Balance Method (bank account opening balance method) Specify the method to use for the opening balance of a bank account: Blank: Book balance. The system uses the book balance from the F0911 and F0902 tables for the opening balance. 1: Bank statement balance. The system uses the bank statement balance from the F09616 table for the opening balance.
Version
1. Cash Forecast Reporting Structures (P09523) and 2. Cash Forecast Report (R095221) Specify the version to use for the Setup Cash Forecast Reporting Structures program and the Cash Forecast Report. If you leave these processing options blank, the system uses ZJDE0001.
258
Chapter 24
The processing time required to display information on this form depends on the amount of data in the F09522 table. Based On Date Enter the date on which cash forecasting data was refreshed.
Bank Acct No (bank account Enter a value that identifies the bank account number (not the account ID) in number) the general ledger. If you use the Search button to locate an account, the system accesses the bank accounts associated with all GL cash type rules in the F09252 table. If no bank accounts exist in the F09525 table, the system accesses the account information in the F0901 table instead. Beginning Date and Ending Date Apply Weight Factors Hide Past Due Column Enter the beginning and ending dates in which to display cash forecast information. If this option is selected, the weight factors defined in the F09521 table are applied to the actual amounts you view on the Cash Forecast Analysis form. If this option is selected, the past due column does not appear on the Cash Forecast Analysis form. If this option is not selected, a separate past due column appears on the form. Specify the segment or interval of time during which to view cash forecast amounts.
Error Message: G/L Cash Type Rule Not Found for [Account]
If a bank account is not assigned to an active GL cash type rule and you refresh the F09522 table, you will receive the warning message on the Cash Forecast Analysis form: G/L Cash Type Rule Not Found for [Account]. The net operating carryover amount for that cash type will not include the bank account, and subsequent opening balances on the Cash Forecast Analysis form will be incorrect. To correct the problem, use the Cash Type Rules Setup program and either add the bank account to the account range for an existing GL cash type rule or set up a new GL cash type rule for the bank account. Then rerun the Refresh Cash Forecast Data program. Access the Cash Forecast Analysis form again. The net operating carryover amount will include the bank account, and subsequent opening balances will be correct.
259
Chapter 24
Use a processing option to specify the prior number of days in which to purge records. The purge program runs before the Refresh Cash Forecast Data program refreshes the data in the table. When you run the purge program from the refresh program, you can purge records up to one day before the based-on date, but not including the based-on date. Note. If you make changes to your data and need to run the Refresh Cash Forecast Data program more than one time in a given day, you must run the Purge Cash Forecast Data program from menu G09319 before you run the refresh program again. If you do not, the program issues this error message: Record already exists in F09522 for based on date. Please purge the records for this date using Purge Cash Forecast Data (R09522B) and then run the refresh. The purge program that you run from the menu enables you to specify an ending based-on date, whereas the purge program that runs from the Refresh Cash Forecast Data program enables you to purge records only up to one day before the based-on date.
Select
1. Beginning Date to Purge Specify the beginning based-on date in which to purge records in the F09522 table. If you leave this processing option blank, the system purges all records with a based-on date prior to the date that you specify in the Ending Date processing option. Specify the ending based-on date in which to purge records in the F09522 table. If you leave both this processing option and the Beginning Date processing option blank, the system purges all records with a based-on date through yesterday.
260
CHAPTER 25
261
Chapter 25
K: automatic payments M: manual payments with match W: manual payments without match RB: receipts The system creates the entry as one sided with a document type of PK, PN, or PT for Accounts Payable and RC or RK for Accounts Receivable. It then creates a balancing entry in the accounts payable and accounts receivable trade accounts with a document type of AE (automatic entry). Because the system creates both documents in the same batch, the batch is in balance and can be posted without error.
262
Chapter 25
263
Chapter 25
Create Cash Basis Entries - A/P If the OBJ and SUB fields are blank, the system searches the F0911 record to locate expense accounts. The system updates the F0911 record in the batch with expense account information from the voucher. The system updates the RNALT6 field to P in the F0414 table.
Create Cash Basis Entries - A/R If the OBJ and SUB fields are blank, the system looks at the F0911 record to locate revenue accounts. The system updates the F0911 record in the batch with revenue account information from the invoice. The system updates the RZALT6 field to P in the F03B14 table.
264
Chapter 25
AA Ledger (F0911)
AZ Ledger (F0911)
JE 1234 G/L Date 6/08/05 Bank Account -300 Bank Fee 300 ALT 6 is updated with P PK 111 G/L Date 6/13/05 Bank Account -400
JZ 1234 G/L Date 6/08/05 Bank Account -300 Bank Fee 300
PV 45666 G/L Date 6/01/05 Expense Account 400 Cash basis entries are not created. Document types PV and RI are excluded.
Cash basis entries for General Accounting, Accounts Payable, and Accounts Receivable systems
This graphic illustrates the cash basis entries created for JD Edwards EnterpriseOne Accounts Payable and JD Edwards EnterpriseOne Accounts Receivable, based on the previous example:
Batch Type G, Batch Number 445 PZ 111 G/L Date 6/13/05 (R11C850) Bank Account -400 (R11C854) Expense Account 400 RZ 32143 G/L Date 6/23/05 (R11C850) Bank Account 600 (R11C853) Expense Account -600
Cash basis entries for Accounts Payable and Accounts Receivable systems
265
Chapter 25
Understanding When to Run the Cash Basis Program from the Menu
When you first use cash basis accounting, you should run the Create Cash Basis Entries program from the menu instead of from the General Ledger Post program. All transactions that were previously entered must be processed for cash basis accounting; therefore, the program requires additional processing time and might run more efficiently during off-peak hours. If you create cash basis entries periodically, such as weekly, monthly, or quarterly, you can control when to create cash basis entries by running the Create Cash Basis Entries program from the menu.
Running the Create Cash Basis Entries Program from the Menu
Select Cash Basis Accounting (G09314), Create Cash Basis Entries.
Setting Processing Options for the Create Cash Basis Entries Program (R11C850)
Use these processing options to create cash basis entries.
Process Tab
This processing option specifies whether to post the cash basis entries. 1. G/L Post (general ledger post) Specify whether to post cash basis entries to the F0911 table.
266
Chapter 25
Defaults Tab
This processing option specifies whether to use journal entry or audit information for the cash basis entries. 1. AZ Journal Entry Explanation Specify whether to use the journal entry explanation from the AA ledger record for the AZ ledger entries. If you leave this processing option blank, the system uses audit information.
Versions Tab
This processing option specifies the post version for the cash basis entries. 1. G/L Post (R09801) Version Specify the version of the General Ledger Post program in which to process cash basis entries. If you leave this processing option blank, the system uses version ZJDE0001.
Understanding When to Run the Cash Basis Program from the Post
After you create cash basis entries, you can ensure that your AZ ledger has the most up-to-date information as cash is received or disbursed by activating a processing option in the General Ledger Post program. To activate the cash basis processing option, you designate the version of the Create Cash Basis Entries program that you want to run. You can activate the cash basis processing option in versions of the General Ledger Post program for these batch types only: G: general ledger K: automatic payments M: manual payments with match W: manual payments without match RB: receipts
Running the Cash Basis Entries Program from the General Ledger Post Program (R09801)
Select Journal Entry, Inquiries, & Reports (G0911), General Ledger Post.
267
Chapter 25
If an accounts payable or accounts receivable error occurs, the system does not update the cash basis posting code and the message No records written appears on the report. Errors continue to appear on subsequent exception reports until you correct them. In most cases, errors that prevent the system from creating cash basis entries for the revenue or expense accounts do not prevent the system from creating the entry for the bank account. When the system creates the entry for the bank account but not the revenue or expense account, the transaction and batch are out of balance. When you correct errors and create cash basis entries again, the next batch for the expense and revenue accounts will be out of balance by the same amount, with the opposite sign. The net effect is that the two batches combined are in balance; however, you must post each of them out of balance.
268
Chapter 25
269
Chapter 25
270
CHAPTER 26
271
Chapter 26
Versions Tab
This processing option specifies the version to run. If a version is specified, the system runs the program after the post program finishes. 52 Period Post Version Specify the version of the 52 Period Accounting Post program to use to update the F0902 and F0902B tables. If you leave this processing option blank, the 52 Period Accounting Post program does not run and does not update the tables.
Prerequisite
Update the F0902 table by running the Annual Close program.
272
Chapter 26
Prerequisites
Before you complete the tasks in this section: Verify that you have set up automatic accounting instruction (AAI) items FSxx. These items establish the optimal interim totals on the income statement. Verify that your 52-period financial reporting dates are set correctly.
273
Chapter 26
Subsidiary The data selection and data sequencing for the 52 Period Income Statement are the same as those for the Simple Income Statement for 12- to 14-period accounting. See Chapter 32, Generating Financial Reports, Setting Data Selection for Simple Income Statement, page 360.
274
CHAPTER 27
Account Consolidations
The account consolidation programs enable you to group, or consolidate, business unit account balances for online review and reports, provided that the balances are in the same currency and all of the companies use the same fiscal date pattern. The JD Edwards EnterpriseOne General Accounting system provides these methods of account consolidation: Online consolidations High-volume consolidations Multisite consolidations The method that you choose depends on the availability of disk space. All methods use AAI items GLG6 (beginning revenue account) and GLG12 (ending income statement account) to distinguish between balance sheet and income statement accounts. When the system calculates cumulative balances, it adds the prior year-end cumulative balance to the year-to-date amount for accounts that are not income statement accounts.
275
Chapter 27
Controls the calculation method for ledger comparison. For example, you can subtract budgeted amounts from actual amounts to calculate budget variances or divide budgeted amounts by actual amounts to show a budget-to-actual ratio. Four calculation options are available. Accesses the ledger for reviewing detail information for business units, down to the account level. Requires less additional disk space than the high-volume method because it creates fewer new records. Instead, it uses the existing account balance records. Enables you to consolidate balances that are based on multiple business unit category codes. Enables you to use the parent/child relationships that you create in organization report structures. The disadvantages of the online consolidation method are: Provides reviewing capability only, although you can export the information to a spreadsheet for analysis. Causes increased processing time, based on the number of business units.
276
Chapter 27
This graphic illustrates a high-volume consolidation that consolidates data by region using business unit category code 02:
Company 00001 Company 00200
BU 3
BU 4
BU 5
BU M40
BU M20
BU M10
121,000 Balance
240,000
115,000
420,000
315,000
20,000
Company Constraints Company 00800 (F0010) Creates: New business units New accounts New accounts balances Category Codes 02 Values C Central N North S South W West BU Master table (F0006) Account Master table (F0901) Account Balance table (F0902)
277
Chapter 27
The information that you consolidate at the central location is accessible to all standard JD Edwards EnterpriseOne programs.
278
CHAPTER 28
See Also
Chapter 27, Understanding Account Consolidations, Online Consolidation Method, page 275
279
Chapter 28
Prerequisites
Before you complete the tasks in this section: Determine the organization report structures to use for your business. Set up the structure codes in UDC table 00/TS. Determine the business unit that is associated with each structure level. For each organization report structure that you want to create, create a pseudo consolidation company and determine the hierarchy to use for the category codes.
280
Chapter 28
FormID
Navigation Advanced Organization Setup (G094111), Organization Structure Definition. On Work With Structure, click Add.
Structure Setup
W0050BA
Sequence
Mode
1. Mode Specify the mode in which to process the consolidations: 0: Proof mode with report. 1: Final mode with update and report 2: Final mode with update and no report
Structure Name
1. Structure Name Enter the name of the business unit structure type.
BU Creation
1. Business Unit Creation Specify whether to dynamically create business units. Values are: Blank: No dynamic business unit creation.
281
Chapter 28
1: Dynamic business unit creation with concatenation of category code values to determine the new business unit. 2: Dynamic business unit creation with next numbering to determine the new business unit. 2. Business Unit Type 3. Pseudo Consolidation Company Enter the business unity type to use to create business units. Enter the pseudo consolidation company to use for business unit creation.
FormID
Navigation Advanced Organization Setup (G094111), Organization Structure Inquiry/Revision On Parent/Child Browse, click Add.
Usage Review and rearrange organization report structures. Add an organization report structure by selecting business units.
Headerless Detail
W0050B
282
Chapter 28
FormID
283
Chapter 28
Forms Used to Create Additional Business Units and Copy Report Structures
Form Name Parent/Child Browse
W0050C
FormID
Navigation Advanced Organization Setup (G094111), Organization Structure Inquiry/Revision From the Parent/Child Browse form, select the business unit to which you want to add a child business unit. From the Parent/Child Browse form, select the business unit that you want to copy and then click Copy.
Usage Review and rearrange organization report structures. Create additional business units.
Headerless Detail
W0050B
W0050F
Copy all or a portion of an existing organization report structure into a new organization report structure.
Structure Type
1. Initial Selection Values Enter values in the processing options to preload the corresponding fields on the Headerless Detail form.
Manager Name
1. Display Managers Name Specify whether to display the managers name in the organizational structure tree. Values are: 0: Do not display the managers name. 1: Display the managers name.
284
Chapter 28
When you add child business units, the system verifies that the parent and the child are not the same, and ensures that the business unit child is not also the parent. Parent Select this check box to see the parent of the business unit to which you are adding children. The parent business unit appears in the detail area. Select the Parent check box again to continue adding children. Enter the business unit of the child. Enter a number that represents the order in which the child business unit appears when listed under their parent. If you leave this field blank when you set up the organization structure, the system assigns the sequence number.
285
Chapter 28
Ensure that the organization report structure to which you are copying exists in UDC table 00/TS but does not exist as a structure in the F0050 table. To Type Structure A code from UDC table 00/TS that identifies the type of organization structure, such as financial or responsibility. Each type of organization structure can have a separate hierarchy. Specify whether to copy an entire organization report structure or only a portion of the structure. Select the Copy Entire Structure option to copy every level of the From Type Structure value to the To Type Structure value, regardless of the level that you selected on the Parent/Child Browse form. Select the Copy Selected Tree Only option to copy only the selected parent business unit and its children from the From Type Structure value to the To Type Structure value.
286
Chapter 28
Consolidated Financial Reporting DIVISION (02) Marketing (240) Consolidated Amount 471,000
Consolidation by category code
287
Chapter 28
Marketing BU 11100
Administration BU 11500
Manufacturing BU 11300
Finance BU 11000
Engineering BU 11400
BU 11120 Eastern
BU 11130 Western
BU 11110 Midwestern
BU 11210 HR
BU 11230 Payroll
Chicago BU11111
Houston BU 11113
BU 11220 IS
Denver BU 11112
FormID
Navigation Consolidations (G1011), Online Consolidations. On the Work With Online Consolidations form, click Add.
288
Chapter 28
Consolidation
Enter the name that corresponds to the consolidated business unit (up to 10 characters). To consolidate business units by organization report structure, enter values in the Type Structure and Parent Business Unit fields.
Company and Category Code Type Structure and Parent Business Unit Category Code Method, Parent Business Unit Method, or Masked Business Unit Method
(optional) Enter a company and a category code (0130) in these fields to consolidate business units by company and category code. Enter the type structure from UDC table 00/TS and the primary business unit in the hierarchy to consolidate business units by organization report structure. Select one of these options: Category Code Method. This method consolidates based on business unit category codes. Parent Business Unit Method. This method consolidates based on organization type structure and a parent business unit. Masked Business Unit Method. This method consolidates based on business units that match character position values.
289
Chapter 28
Menu Selections
After you determine your choices for consolidation, access these menu selections from the Form menu: Store Inquiry Refresh BU (refresh business units) Online Statements Save your criteria. This information is stored in the Online Consolidations Set-up table (F09218). Process account balances. The processing time depends on the number of business units and associated accounts that you are consolidating. This information is stored in the F09218 table. Create consolidated financial statements. See Chapter 28, Processing Online Consolidations, Reviewing Online Consolidations, page 290.
FormID
Navigation Consolidations (G1011), Online Consolidations. On the Work With Online Consolidations form, select the consolidation that you want to review and then select Online Statements from the Row menu.
Usage Locate online consolidations. Review online financial statements for consolidations.
Ledger Type
1. Ledger Types Enter the default ledger types in these processing options. Ledger Type - Column 1. If you leave this processing option blank, ledger type BA is used.
290
Chapter 28
Ledger Type - Column 2. If you leave this processing option blank, ledger type AA is used. 2. Exit With Ledger Type Specify the ledger type to use when exiting to another application: Blank or 1: Ledger Type 1. 2: Ledger Type 2.
Balances
1. Suppress Zero Balances Specify whether to display accounts with zero balances if the Business Unit Detail option is not selected. Values are: Blank or N: Display accounts with zero balances. Y: Do not display accounts with zero balances. 2. Calculation Method Specify the calculation method to use for calculating variances. Values are: A: Addition Blank or S: Subtraction M: Multiplication D: Division.
Additional LT
1. Additional Ledger Types Specify additional ledger types to use for calculating account balances for Ledger Types 1 and 2. If you leave these processing options blank, no additional ledger types are used.
Subledger
Subledger and Subledger Type Enter the subledger and subledger type to use for calculating account balances. If you leave these processing options blank, the system uses a subledger and subledger type of blank.
Account LOD
Account Level of Detail Enter the account level of detail (39) to use. If you leave this processing option blank, 9 is used.
Currency Code
1. Currency Code Enter the currency code to use for calculating account balances. If you leave this processing option blank, all currencies are used. Use this processing option only if you use multicurrency processing.
BU Detail
1. Business Unit Detail Specify whether to display business unit detail. Values are: Blank or N: Do not display business unit detail. Instead, combine business units.
291
Chapter 28
Process Mode
1. Financial Statement Processing Mode Specify the processing mode for the consolidated financial reports. Values are: Blank or T: Trial Balance. B: Balance Sheet. I: Income Statement
Date Effective
1. Date Effective and 2. Date Effectivity For future use.
Job Cost
1. Exclude Blank Object Account Specify whether to exclude blank object accounts: Values are: Blank or 0: Exclude blank object accounts from the consolidation. This value should improve processing time. 1: Include blank object accounts in the consolidation.
292
CHAPTER 29
See Also
Chapter 27, Understanding Account Consolidations, High-Volume Consolidation Method, page 276
293
Chapter 29
Default PO
Pseudo Company Enter the pseudo company number to which to delete records. Enter leading zeros for the pseudo company number. For example, enter 00001 for company 1 This deletes all prior consolidation records for the fictitious pseudo company from the F0901, F0902, and F0911 tables. High Volume Consolidations Account ID Enter the next number to use when refreshing the consolidation accounts. You should enter a number high enough to avoid your normal account numbers. If you leave this processing option blank, the system uses the 90000000.
294
Chapter 29
Run the Refresh Consolidation program. Set data selection and sequence for Refresh Consolidation. Set processing options for Refresh Consolidation (R10862).
295
Chapter 29
Header and nonposting title accounts for reports, such as Assets. Important! You must choose a fictitious company for the consolidation. Refreshing consolidations adds records to the F0006, F0901, and F0902 tables for an entire company. If you choose an actual company for the consolidation, the system creates consolidated records for that company. Separating valid records from those created by the consolidation program is very difficult. After you create a consolidation, you can make adjusting entries directly to the fictitious accounts using the Journal Entry program (P0911). You must also make eliminating entries to handle intercompany settlements. When you delete a prior consolidation, adjusting entries are deleted along with consolidated balances.
Prerequisites
Before you complete the tasks in this section: Restrict access to the Refresh Consolidation program by placing security on the program. Set up a fictitious company for each consolidation that you plan to run. Verify the category codes that you want to use for consolidations. Delete any prior consolidations. Ensure that enough disk space exists on your computer for this process to run.
296
Chapter 29
Default PO
1. Pseudo Company 2. Reporting Code Enter the number of the pseudo company for consolidations. Enter the reporting category code used in the data selection. Use RPxx for business unit and R0xx for account master category codes. For example, category code 02, the region would be RP02.
Performance
1. Fiscal Year and 2. Ledger Type 3. Process Non-Posting Accounts Enter the fiscal year to consolidate. Enter a value for the fiscal year to reduce the number of F0902 records that the system processes. Enter the ledger type to consolidate. Enter 1 to retrieve account balances for non-posting accounts. For better performance, leave this processing option blank so that the program does not attempt to retrieve account balances for accounts that do not have account balances.
Default
1. Ledger Type 1 and 2. Ledger Type 2 Specify the two default ledger types. For example, you can enter ledger types AA and BA, or AA and CA. If you leave the processing option ledger type 1 blank, BA is used. If you leave ledger type 2 blank, AA is used. 3. Exit with Ledger Type Specify the ledger type that the called application should use when exiting to another application. Values are: Blank or 1: Ledger type 1. 2: Ledger type 2.
297
Chapter 29
Display
1. Suppress Zero Balances Specify whether to display posting accounts with zero balances. Values are: Blank or N: Display posting accounts with zero balances. Y: Do not display posting accounts with zero balances. This processing option applies only to posting accounts. Nonposting header accounts will appear on the Trial Balance/ Ledger Comparison form (P09210A) regardless of this processing option. 2. Calculation Method Specify the calculation method to use to calculate variances. Values are: Blank or S: Subtraction. A: Addition. M: Multiplication. D: Division. 3. Additional Ledger Type 1 4. Additional Ledger Type 2 5. Subledger and 6. Subledger Type Specify an additional ledger type to use to calculate account balances for ledger type 1. For example, you can use ledger types AA or C. If you leave this processing option blank, no additional ledger type is used. Specify an additional ledger type to use to calculate account balances for ledger type 2. For example, you can use ledger types AA or CA. If you leave this processing option blank, no additional ledger type is used. Specify the subledger and subledger type that the system uses to calculate account balances. Enter * to select all transactions with subledgers. If you leave the Subledger processing option blank, the system selects transactions with no subledgers. Enter a subledger type such as A or C. If you leave this processing option blank, the system selects a blank subledger type. 7. Account Level Of Detail Specify the account level of detail (39) to use. If you leave this processing option blank, the system uses 9.
Currency
1. Currency Code Specify the currency code to be used for calculating account balances. If you leave this processing option blank, the system uses all currencies.
Select
1. Date Effective Balances Specify whether to use period-end dates or calculate date-effective balances. Values are: Blank or N: Period End Dates. Y: Calculate date effective balances. 2. Default Thru Period Display Specify whether to display through dates or through periods. Values are: Blank or N: Display thru dates. Display
298
Chapter 29
When you refresh consolidations, the system creates balances only, and not transactions. Therefore, the Trial Balance / Ledger Comparison form shows only journal entries that are made directly to the fictitious business unit.
299
Chapter 29
300
CHAPTER 30
See Also
Chapter 27, Understanding Account Consolidations, Multisite Consolidation Method, page 277
301
Chapter 30
302
Chapter 30
Prerequisites
Before you complete the tasks in this section: At both the source and the target, set up a pseudo company in the Company Names & Numbers program (P0010) for the consolidated account balances. Set up the structure codes in UDC table 00/TS. Ensure that your business unit category codes are assigned. Determine the organizational structures to use for your business. For each organizational structure that you want to create, determine the sequence to use for the business unit category codes. At the target, ensure that a model chart of accounts is set up if you want the system to dynamically create business units or accounts.
303
Chapter 30
Version
1. UDC Control File Version Enter a unique name for the UDC Control File version that you are creating. If you leave this processing option blank, the system uses a report name of blank.
Data Selection
1. Object/Subsidiary Control File Version 2. File Data Selection Enter a unique name for the Object/Subsidiary Control File version that you are creating. you would like to create. If you leave this processing option blank, the system uses a report name of blank. Enter 1 to select a unique object and subsidiary. If you leave this processing option blank, only a unique object is selected.
304
Chapter 30
FormID
Navigation Multi-Site Consolidation Setup (G1042), Business Unit Structure Definition On the Work With Structure form, click Add.
Usage Locate and review organization report structures. Define an organization report structure.
Structure Setup
W0050AA
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Organizations, Revising Business Units Within an Organizational Structure
305
Chapter 30
The Account Structure Definition program (P10430A) updates the Account Structure Definition table (F10430A).
Navigation Multi-Site Consolidation Setup (G1042), Account Structure Definition. On the Work With Account Structures form, click Add.
W10430AB
306
Chapter 30
Enter a code from UDC table 00/TS that identifies the type of account structure, such as financial or responsibility. Each type structure can have a different hierarchy. Select this check box to sequence your accounts by object and then subsidiary. The program will ignore category code sequencing.
Process
1. Mode Enter the mode in which to process and update calculations. Values are: 0: Proof mode with report (default).
307
Chapter 30
1: Final mode with report. 2: Final mode without report. 2. Type of Build Enter 1 to add records to an existing structure. If you leave this processing option blank, the system builds a new structure.
Structure Name
1. Structure Name Enter a code from UDC table 00/TS that represents the name of the structure.
Target Object
1. Target Object Enter the fields (Fields 13) to use to load the target object. If you use multiple fields, their values will be concatenated together to form the target object. If you leave this processing option blank, the target object is left blank. Valid fields are OBJA (alternate object ) and R001R023 (category codes 123).
Target Sub
1. Target Subsidiary Enter the fields (Fields 13) to use to load the target subsidiary. If you use multiple fields, their values will be concatenated together to form the target subsidiary. If you leave this processing option blank, the target subsidiary is left blank. Valid fields are SUBA (alternate subsidiary ) and R001R023 (category codes 123).
LOD
Level of Detail Enter the field that contains the account level of detail. If you leave this processing option blank, the level of detail field LDA is used. Valid fields are R001R023 (category codes 123).
308
Chapter 30
When you move components of the structure to other sites in the hierarchy, you can move individual accounts or higher levels of the structure. When you move a component of the structure, the system updates the F10430 table. You might need to revise the account structure detail information before consolidating balances if the target object or subsidiary of an account differs from the source object or subsidiary of an account. Use the Account Structure Inquiry/Revision program (P10440) to rearrange components of the structure and to revise detail information about the account structure. After you create or revise the account structure, you can print the Account Structure report (R10445) to show the complete hierarchy of the structure.
Object Account
309
Chapter 30
LOD
1. Account Level of Detail Enter the account level of detail (3 9) to print. If you leave this processing option blank, the system uses 9.
310
Chapter 30
FormID
Navigation Multi-Site Consolidation (G1021), Consolidation Specifications On the Work With Consolidation Specification Revisions form, click Add. Multi-Site Consolidation (G1021), Elimination Rules. On the Work With Elimination Rules form, click Add.
Usage Locate and review existing multisite consolidation rules. Define consolidation rules and revise existing consolidation rules. Locate and review existing elimination rules. Add elimination rules.
Consolidation Specification W10470D Revisions Work with Elimination Rules Elimination Rules Setup
W10471A W10471B
311
Chapter 30
312
Chapter 30
Live Business Unit Master Snapshot Business Unit Master Effective Date/Version
Select this option to use a live business unit category code structure from the Business Unit Maser table (F0006). Select this option to use a date-effective snapshot of a business unit category code structure from the Date Effective Business Unit Master table (F0006S). Enter the date that was assigned to a date-effective snapshot of a business unit category code structure when the snapshot was created and the number of the version.
Additional Setup
Select the Additional Setup tab. Rounding Factor Enter a code that controls how amounts are to be rounded, that is, whether amounts are rounded to 100s, 1000s, and so on. Codes are: Blank: No rounding 0: Round decimals 1: Round to the nearest 10 2: Round to the nearest 100 3: Round to the nearest 1000 4: Round to the nearest 10000 5: Round to the nearest 100000 6: Round to the nearest 1000000 For example, the number 987,654,321.91 would be appear as follows for each of the rounding factors: Blank: 987,654,321.91 0: 987,654,322.00 1 : 987,654,320.00 2: 987,654,300.00 3: 987,654,000.00 4: 987,650,000.00 5: 987,700,000.00 6: 988,000,000.00 Subledger Detail Balances by Currency Select this check box for subledger detail to be carried forward in the consolidation. Select this check box if you post F0902 records by currency for this company.
313
Chapter 30
Enter a two-character value that you use to group accounts that eliminate one another. The account balances within an elimination group should net to zero. Enter the account to which the system enters the elimination. Leave this field blank to enter the elimination to the account that is being eliminated. Enter the subledger to which the system enters the elimination. If you specify the subledger, you must also specify the subledger type. Leave this field blank to enter the elimination to the subledger that is being eliminated.
Enter the subledger type to which the system enters the elimination. If you specify a subledger type, you must also specify the subledger. Leave this field blank to enter the elimination to the subledger type that is being eliminated.
Enter the account to which the system records variance write-off amounts for the specified elimination group. Specify an elimination percentage for the elimination group.
314
Chapter 30
Omits zero balance accounts. Consolidates year-to-date balances. Matches up fiscal date patterns for account balances. Ignores balances after the as of period. Performs rounding. Maintains the specified subledger and currency detail. Creates account balances at the specified levels of detail. Writes off variances within the specified limits. Eliminates intercompany balances. The Process Consolidations program writes the consolidated balances to these tables: Multi-Site Consolidation Transfer File Header (F1001) Multi-Site Consolidation Transfer (F1002) Multi-Site Consolidation Transfer - Category Codes (F1003)
Processing Consolidations
Select Multi-Site Consolidation (G1021), Process Consolidations.
Process
1. Mode Specify the mode in which to run this program. Values are: 0: Proof mode with report (default). 1: Final mode with report. 2: Final mode without report. 2. Pseudo Company Enter the company number of the pseudo consolidation company.
315
Chapter 30
Enter the period and fiscal year through which the consolidation is to be prepared. If you leave this processing option blank, the financial reporting year and period for the company are used. Enter the target ledger type to be used for consolidation or leave this processing option blank to use ledger type AA. Specify which category codes to save for transmission. Values are: Blank: Do not save category code values. 1: Save business unit category codes. 2: Save account category codes. 3: Save both business unit and account category codes.
Enter 1 to retrieve account balances for non-posting accounts. The designation of non-posting accounts is in the F10430 table, not the F0901 table. Leave this processing option blank for better performance. The program does not attempt to retrieve account balances for accounts that do not have account balances.
BU Creation
1. Dynamic Business Unit Flag Specify how to dynamically create business units. Values are: Blank: Do not use dynamic business unit creation. 1: Use dynamic business unit creation with concatenation of category code values. If you included company in your organizational structure sequence, you must enter 1 for this processing option. 2: Use dynamic business unit creation with next numbering.
Site ID
1. Site ID Enter the site ID associated with the source of the data.
Variance
1. Variance Threshold Enter a variance threshold for creating an automatic write-off amount for consolidations. If a variance exists in the consolidations that were created and the variance is within the tolerance, an automatic write-off is created. Leave this processing option blank if you do not want to use this feature. Note. If the variance entered is a percentage, use the % character. For example, 3 percent would be entered as 3%. 2. Consolidation Variance Threshold Enter the object and subsidiary accounts to use for the automatic write-off amount.
316
Chapter 30
Eliminations
1. Eliminations Ledger Type Enter the target ledger type to be used for elimination entries. If you created rules for the elimination of intercompany transactions, you must enter 1 for this processing option to indicate the ledger type where the system records the eliminated amounts. If you leave this processing option blank, the system does not create eliminating entries. 2. Elimination Variance Threshold Enter a variance threshold for creating an automatic write-off amount for eliminations. If a variance exists in the elimination entries that were created and the variance is within the tolerance, an automatic write-off amount is created. Leave this processing option blank if you do not want to use this feature. Note. If the variance entered is a percentage, use the % character. For example, 3 percent would be entered as 3%.
Currency
Currency Code Multi-Currency Off If the target site uses multiple currencies but your source site uses a single currency, you can set a processing option to designate the currency code for your consolidated account balances. The system does not perform any currency conversion; it simply assigns the currency code to the account balances. The system ignores this processing option if your site uses multicurrency processing.
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Organizations
317
Chapter 30
Run the Consolidated Balance Sheet report. Set processing options for Consolidated Balance Sheet. Run the Consolidated Income Statement report. Set processing options for Consolidated Income Statement.
318
Chapter 30
You must set a processing option to indicate whether you are running the report at a source site or a target site. If the integrity report fails, the system updates one of these fields in the F1001 table. Each of these fields indicates a specific error condition:
Field GPIN07 GPIN08 GPIN05 GPIN06 Description of error Accounts appear in the current consolidation, but not in the previous consolidation. This error applies to the first two versions listed previously. Business units appear in the current consolidation, but not in the previous consolidation. This error applies to the first two versions listed previously. Accounts appear in the previous consolidation, but not in the current consolidation. This error applies to the last two versions listed previously. Business units appear in the previous consolidation, but not in the current consolidation. This error applies to the last two versions listed previously.
Status
1. Integrity Status Enter 1 to force the integrity to fail if the system does not find previous consolidation balances. Do not set the processing option to 1 for the first period in which you create consolidations because the system will not find previous balances for comparison. If you leave this processing option blank, a message prints on the report if a previous balance is not found, but it will not cause an error condition or integrity failure.
Version
1. UDC Control File Version Enter the unique name of the UDC Control File version to validate. If you leave this processing option, the name of blank is used.
319
Chapter 30
Setting Processing Options for Object/Subsidiary Value Control Exceptions Report (R107021)
Processing options enable you to specify the default processing for reports.
Data Selection
1. Object/Subsidiary Control File Version 2. File Data Selection Enter the unique name of the Object/Subsidiary Control File version to validate. If you leave this processing option, the name of blank is used. Enter 1 to select a unique object and subsidiary account. if you leave this processing option blank, only a unique object is selected.
Setting Data Selection and Sequence for BU/Accounts Monthly Comparison Report
Do not change the data selection or data sequence. Each version of the report has the appropriate data selection and data sequence.
Process
1. Integrity Location Enter the site at which the integrity is being run. Values are: 1: Source site. 2: Target site. 2. Integrity Status Enter 1 to force the integrity to fail if the system does not find previous consolidation balances. Do not set the processing option to 1 for the first period in which you create consolidations because the system will not find previous balances for comparison. If you leave this processing option blank, a message prints on the report if a previous balance is not found, but it will not cause an error condition or integrity failure.
320
Chapter 30
Signs
1. Reverse Sign Enter 1 to print the liability accounts as negative amounts. If you leave this processing option blank, the accounts print as positive amounts.
Accounts
Enter the beginning object account for each of these processing options. 1. Beginning Stockholders Equity 2. Automatic Accounting Instructions (Required) Enter the beginning object account that represents stockholders equity. The report does not run if you do not complete this processing option. (Optional) Enter the beginning object account for each of these: Beginning Assets Beginning Liabilities Operating Income If you leave this processing option blank, the system uses accounts for AAI items GLG2, GLG3, and GLG respectively.
Signs
1. Reverse Sign Enter 1 to print expense and liability accounts as negative amounts. If you leave this processing option blank, the accounts print as positive amounts.
Accounts
1. Beginning Object Enter the beginning object account for each of these: Beginning Revenue Beginning Cost of Goods Sold Beginning Other Income Beginning Other Expense If you leave this processing option blank, the system uses accounts for AAI items GLG6, GLG8, GLG11, and GLG13 respectively.
321
Chapter 30
322
Chapter 30
The target is responsible for communicating with the source after the target runs the batch process to create journal entries at the target. The source must manually update the corresponding records from transmission status 1 to transmission status 2. If a previously processed batch of corresponding records has a transmission status 2, the system updates that batch to transmission status 3. The Consolidation Console program also identifies the integrity reports that you are required to run at the source and target sites, based on the processing options that you set. The program indicates whether integrity reports have been run, and whether the integrity reports passed or failed. This information appears in the Integrity Status fields in the detail area. The Integrity Status fields can have these values:
Integrity Status Blank 0 1 2 9 Integrity not run. Integrity not run. Integrity passed. Integrity failed. Override; transmit regardless of integrity status. Description of Status
When you are ready to send the consolidated balances to the target company, the Consolidation Console program enables you to send the information. The system holds the consolidated account balances in the F1001, F1002, and F1003 tables until you delete them. Whether you are at a source or target site, you should delete these records periodically.
FormID
Usage Review consolidation statuses, monitor integrity reports, send consolidated balances to the target company, and delete processed consolidations.
323
Chapter 30
324
Chapter 30
You software includes two versions of this program. Do not change version XJDE0001. You can change version XJDE0002. The system prompts you for the names of the source and target environments. You can use the browse function to locate either environment. If you leave the source environment blank, the system uses your environment as the source environment. If you leave the target environment blank, the system uses your environment as the target environment. You can set a processing option to prevent the transmission of the consolidated balances if one or more integrity reports fail.
Prerequisites
Before you complete the tasks in this section: Verify that the F1001, F1002, and F1003 tables exist on your local drive or that you have access to the tables on the server. Use the Object Configuration Manager program (P986110) to map the MSC Data Transmission program (R10610) to a local drive.
Integrities
If you do not run the specified integrity report for each of the processing options, the transmission is not affected. Prior Period Adjustments Specify whether the Prior Period Balance Integrity report must pass before data can be transmitted. The system considers the integrity report as passing if it does not find any consolidated balances from the prior period that have changed since the previous consolidation. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted. Credits = Debits Specify whether the integrity process that verifies that debits equal credits must pass before data can be transmitted. This integrity process is an internal process that the system runs before writing records to the F1001 and F1002 tables. Values are: Blank: The integrity process that verifies that debits equal credits does not have to pass before data can be transmitted. 1: The integrity process that verifies that debits equal credits must pass before data can be transmitted. Source UDC = Target UDC Specify whether the UDC Value Control integrity report (R107011) must pass before data can be transmitted. The system considers the report as passing
325
Chapter 30
when the consolidation does not contain any instances of user-defined code values that are unrecognized by the target company. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted. Source Obj/Sub = Target Obj/Sub Specify whether the Obj/Sub Value Control integrity report must pass before data can be transmitted. The system considers the integrity report as passing when the consolidation does not contain any instances of object accounts and subsidiaries that are unrecognized by the target company. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted. Accounts Last Month Not This Specify whether the Accounts Last Month Not This Month version of the BU/Accounts Monthly Comparison report must pass before data can be transmitted. The system considers the report as passing when all of the accounts that appeared in last months consolidation appear in this months consolidation. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted. BU Last Month Not This Month Specify whether the Business Units Last Month Not This Month version of the BU/Accounts Monthly Comparison report must pass before data can be transmitted. The system considers the report as passing when all of the business units that appeared in last months consolidation appear in this months consolidation. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted. Accounts This Month Not Last Specify whether the Accounts This Month Not Last Month version of the BU/Accounts Monthly Comparison report must pass before data can be transmitted. The system considers the report as passing when all of the accounts in this months consolidation also appeared in last months consolidation. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted. BU This Month Not Last Month Specify whether the Business Units This Month Not Last Month version of the BU/Accounts Monthly Comparison report must pass before data can be transmitted. The system considers the report as passing when all of the business units in this months consolidation also appeared in last months consolidation. Values are: Blank: This report does not have to pass before data can be transmitted. 1: This report must pass before data can be transmitted.
326
Chapter 30
FormID
Navigation Multi-Site Consolidation (G1021), Consolidation Console. On Consolidation Console, select the consolidation for which you want to send consolidated balances to the target company and then select Transmit from the Row menu.
Usage Review consolidation statuses, monitor integrity reports, send consolidated balances to the target company, and delete processed consolidations.
327
Chapter 30
Integrities
1. Integrities Enter 1 for each integrity report that is required to pass before the consolidation batch may be transmitted. Transmission is not affected by integrity failure or not running the report. The integrity reports for these processing options are: Prior Period Adjustments Credits = Debits Source UDC = Target UDC Source Obj/Sub = Target Obj/Sub Accounts Last Month Not This BU Last Month Not This Month Accounts This Month Not Last BU This Month Not Last
Environment
328
Chapter 30
Enter the number that the transmitter assigned to the batch. During batch processing, the system assigns a new batch number to the transactions for each control (user) batch number it finds.
329
Chapter 30
After you process the inbound consolidations and revise them, if necessary, you can generate journal entries for the summarized account balances, verify that they are accurate, and process them.
Mode
1. Mode Enter the mode in which to run the inbound consolidations process. Values are: 1: Proof mode with report. 2: Final mode. This mode processes F1001Z1 and F1002Z1 records to the F1001 and F1002 respectively.
JE Processing
1. JE Processing Enter the version of the Journalize Consolidation Balances report to run. If you leave this processing option blank, the report does not run.
Purge Data
1. Purge Data Enter 1 to purge all data from the F1001Z1 and F1002Z1 tables after all processing has completed. If you leave this processing option blank, data is not purged from these tables.
330
Chapter 30
Navigation Inbound Multi-Site Consolidations Data (G1023), Revise Inbound Consolidations Data
W1002Z1B
On the Work With Multi-Site Add and revise inbound Consolidation Unedited multisite consolidation Transactions form, select records. the record that you want to revise. To add inbound multisite consolidation records, on the Work With Multi-Site Consolidation Unedited Transactions form, click Add.
331
Chapter 30
When the system creates journal entries in the F0911Z1 table, it does this for each journal entry: Places a concatenation of the source system ID, the batch number, and the transmission date in the Explanation field. Places the consolidation name in the Transaction Number field. Places the last day of the corresponding accounting period in the G/L Date field. Places the source system ID in the User ID field. Note. Regardless of the type of account, the system always updates the Balance Forward field in the F0902 table. Usually, the system does not print balance-forward amounts for income statement accounts. However, to enable inception-to-date reporting for multisite consolidations, the system prints beginning balances for income statement accounts. If the Journalize Consolidation Balances program dynamically creates business units or accounts, it generates reports that show the new information.
Prerequisites
Run these reports at the target company: Prior Period Balance Integrity UDC Value Control Obj/Sub Value Control
332
Chapter 30
Mode
1. Mode Specify the mode in which to run the program: 0: Proof mode with report (default). 1: Final mode with report. 2: Final mode without report.
Company
1. Consolidation Company Enter the number of the consolidation company to update. If you leave this processing option blank, the company defined in the F1001 table is used.
Ledger Type
1. Ledger Type Enter the ledger type from UDC table 09/LT to update. If you leave this processing option blank, the ledger type defined in the F1001 table is used.
Prior Period
1. Prior Period Adjustments Specify create adjusting entries. Values are: Blank: Do not create adjusting entries. The record will not be processed and an error will be written to the report. 1: Create adjusting entries to prior periods for differences between the current and previous consolidation. 2: Create the adjusting entries in the current period. 3: Ignore prior period differences. 2. Directly Update F0902 Enter 1 to directly update F0902 table for Balance Forward differences between the current and previous consolidation. If you leave this processing option blank, the F0902 is not updated.
333
Chapter 30
Business Unit
1. Dynamic Business Units Creation Enter 1 to dynamically create business units that exist in the Consolidation table but do not exist in the F0006 table. If a business unit in the F1002 does not exist in the target, the program creates it. If you leave this processing option blank, business units are not created. 2. Business Unit Type Enter the business unit type to use when creating business units.
Account Number
1. Dynamic Account Creation Specify the dynamic account creation. Values are: Blank: Do not dynamically create accounts. 1: Dynamically create accounts that exist in the consolidation table but do not exist in the F0901 table. 2: Dynamically create accounts that exist in the consolidation table but do not exist in the F0901 table by editing the object only. If the object exists in the account master, the account will be created regardless of the subsidiary. If an account in the F1002 table does not exist in the target, the program creates it.
JE Processing
1. Automatic Batch Journal Entry Processing 2. Version Enter 1 to automatically submit the Process Batch Journal Entry program (R09110Z) after creating batch journal entries. If you leave this processing option blank, the program is not automatically submitted. Enter the version of Process Batch Journal Entry program to run. If you leave this processing option blank, version ZJDE0002 is used.
334
Chapter 30
After you run the Process Batch Journal Entry program, you must post the batch so that F0902 table reflects the amounts from the consolidation. The system holds processed journal entries in the batch table until you globally purge them. You should purge batches after they have been successfully processed.
See Also
Chapter 12, Processing Batch Journal Entries, page 107
See Also
Chapter 12, Processing Batch Journal Entries, Purging Processed Batch Journal Entries, page 112
335
Chapter 30
336
CHAPTER 31
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (CHL and PER) Working With General Ledger Functionality for Chile and Peru
See Also
JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Using Multicurrency Inquiries for General Accounting, Reviewing Accounts in Domestic, Foreign, and As If Currencies
337
Chapter 31
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Creating the Chart of Accounts, Defining an Alternate Chart of Accounts for Statutory Reporting
All four programs have a processing option that enables you to review account balances as of a specific date, instead of viewing balances only as of the ending date for a period. If you do not specify a date for the review, the programs identify the current (open) period for the company in the Company Constants table (F0010) and use the period-ending date for that period as recorded in the Date Fiscal Patterns table (F0008). The cumulative balance for balance sheet accounts includes the cumulative balance forward for the prior year. The cumulative balance for income statement accounts does not include this amount.
338
Chapter 31
339
Chapter 31
Navigation Accounting Reports & Inquiries (G0912), T/B / Ledger ComparisonTo review an account, select the account and then select Subledger Detail from the Row menu. Accounting Reports & Inquiries (G0912), Account Balance by Subledger
Usage Review summarized trial balance information for a specific account or for all accounts within a business unit and for two ledgers.
W092131A
Default
1. Ledger Type 1 2. Ledger Type 2 3. Exit with Ledger Type Specify the default ledger for the first ledger type. If you leave this processing option blank, the system uses ledger type BA. Specify the default ledger for the second ledger type. If you leave this processing option blank, the system uses ledger type AA. Specify the ledger type for the system to use when accessing another program. Values are: Blank or 1: Ledger Type 1. 2: Ledger Type 2.
Display
1. Suppress Zero Balances Specify whether to display posting accounts with zero balances. Values are: Blank or N: Display zero balances.
340
Chapter 31
Y: Do not display zero balances. This processing option applies only to posting accounts. Non-posting header accounts appear on the inquiry form. 2. Calculation Method Specify the calculation method to use when calculating variances. Values are: Blank or S: Subtraction A: Addition. M: Multiplication. D: Division. 3. Additional Ledger Type 1 and 4. Additional Ledger Type 2 5. Subledger Specify an additional ledger type to use when retrieving account balances for ledger type 1 and ledger type 2. If you leave these processing options blank, the system does not use additional ledger types to retrieve balances for these ledger types. Specify the subledger to use for retrieving account balances. Enter * to display all transactions with subledgers. If you leave this processing option blank, the system selects transactions without subledgers. Specify the subledger type from UDC table 00/ST to use for retrieving account balances. If you leave this processing option blank, the system uses blank for the subledger type. Specify the account level of detail to use (39). If you leave this processing option blank, the system uses 9.
6. Subledger Type
Currency
1. Currency Code Use this processing option only if use multicurrency processing. Specify the currency code to use for retrieving account balances. If you leave this processing option blank, the system uses all currency codes.
Select
1. Date Effective Balances Specify whether to use period-end dates or to calculate date-effective balances. Values are: Blank or N: Period-end dates. Y: Date-effective balances. 2. Default Thru Period Display Specify whether to display thru dates or thru periods. Values are: Blank or N: Thru dates. Y: Thru periods.
341
Chapter 31
Skip to Account
Enter an account number to review account balances for a specific account or enter a business unit number to review account balances for all accounts in a business unit. Based on the value that you entered in the Skip to Account field: To review account balances for a specific account, select this check box. To review account balances for all accounts in the business unit, do not select this check box.
Select / Skip To
Ledger Type 1, Ledger Type 2, Type/Subledger, and Level of Detail Period / Date
Change the default information in these fields, if necessary. To display all subledger information posted to accounts, enter * in the Subledger field. If you leave this field blank, the system displays only posted amounts without subledgers. To review account balances through the ending date of a specific period, select this check box. To review account balances through a specific date within a period, clear this check box.
Change the values in these fields, if necessary. If you leave the LT 1 Thru Date and LT 2 Thru Date fields blank, the system uses the current date for the company in which the business unit belongs. To review account balances through a specific date within a period, enter the date in the LT 1 Thru Date and LT 2 Thru Date fields and clear the Period / Date check box. You must set the Date Effective Balances processing option for this program to Y to review account balances through a specific date.
342
Chapter 31
343
Chapter 31
FormID
Navigation Accounting Reports & Inquiries (G0912), T/B by Object Account Accounting Reports & Inquiries (G0912), T/B by Company Accounting Reports & Inquiries (G0912), T/B by Subledger
Usage Review account balance information across all business units. Review account balance information for a specific account across business units for a single company. Review account balances for a specific subledger or for all subledgers.
W09216A
W09215B
Select
1. Date Effective Balances Specify whether to use period-end dates or to calculate date effective balances. Values are: Blank or N: Period-end dates. The system only allows you to use a period-end date in the Thru Date field. The system retrieves totals from the F0902 table. Y: Date effective balances. The system allows you to enter any valid date within a period in the Thru Date field and the totals will be calculated up to that date. The system calculates totals using the F0911 table instead of the F0902 table.
Default
3. Exit Ledger Type Specify the ledger type for the system to use when accessing another program. Values are: Blank or 1: Ledger Type 1. 2: Ledger Type 2. Note. This processing option applies only when accessing programs that have one ledger type, such as Account Balances by Month (P0902P1). For programs with two ledger types, such as Account Ledger Inquiry (P09200), ledger type 1 will always be the same as ledger type 1 of the originating program, and ledger type 2 will be blank.
344
Chapter 31
Display
7. Model Accounts Specify whether to display model accounts. Values are: Blank or N: Exclude model accounts when a company other than 00000 or * is used. Y: Include model accounts when a company other than 00000 or * is used
Display
3. Ledger Type Specify a ledger type from UDC table 09/LT to use when displaying records. If you leave this processing option blank, the system uses ledger type AA.
345
Chapter 31
Select / Skip To
To review balances only for the account number in the Object/Subsidiary field, select this check box. To begin the list of accounts that display with the account number in the Object/Subsidiary field and include all account numbers greater than the account, do not select this check box.
To specify a period, select this check box and enter the period number in the Thru Period field. Enter the period number. This field appears only if you select the Period / Date check box. To specify a through date, enter the date in this field. If you leave this field blank, the system uses the ending date of the current period for the company.
The fields that appear on this form are similar to those on the Trial Balance by Object Account form. See Chapter 31, Reviewing Balances and Transactions, Reviewing Balances by Object Account, page 345.
346
Chapter 31
347
Chapter 31
Review ledgers by object account. Review account ledgers by category code online.
348
Chapter 31
FormID
Usage Review account ledger transaction information for an account. To print the account ledger, select Print Ledger from the Report menu.
Journal Entry
W0911A
On the Work With Account Ledger form, select the transaction for which you want to review the source information and then either click Select or select Original Entry LT1 from the Row menu. To review the source information for a transaction in ledger type 2, select the transaction and then select Original Entry LT 2 from the Row menu.
Review source information for account ledger transactions in ledger type 1 and ledger type 2. Depending on the original transaction, the system accesses various forms. For example, if the original transaction is a journal entry, the system accesses the Journal Entry form or if the original transaction is an accounts receivable invoice, the system accesses the Standard Invoice Entry form. Review detailed information about the document. Review additional details about the document including number and date and the user ID of the person who created the batch. Review account ledger transactions for an object account across business units.
W09200F
On the Work With Account Ledger form, select Details from the Row menu. On the Account Ledger Details form, select Additional Details from the Form menu. Accounting Reports & Inquiries (G0912), Account Inquiry by Object Account To print the account ledger, select Print Ledger from the Report menu.
W09200G
W09201A
W09202A
Accounting Reports & Inquiries (G0912), Account Inquiry by Category Code To print the account ledger for an account, select the account and then select Print Ledger from the Row menu.
349
Chapter 31
Defaults
1. Account Number, 2. For each processing option, specify the default value for the system to display From Date, 3. Through in the corresponding fields on the inquiry form. Date, 4. Ledger Type, 5. Subledger, 6. Subledger Type, and 7. Currency Code
Select
1. From Date Method Specify the date the system should use on the inquiry form if the From Date field is left blank. Values are: 1: Use the beginning date of the current fiscal year as the from date. 2: Use the beginning date of the current period as the from date.
Display
1. Second Ledger Type Specify whether to display a second ledger type, which enables you to view two ledger types at one time. Values are: Blank: Display one ledger type. 1: Display two ledger types. The system uses ledger type 1 as the basis for determining the amount for ledger type 2; therefore, the system displays only records with ledger type 1 amounts on the inquiry form. For example, if you enter AA for ledger type 1 and CA for ledger type 2, the system displays all records with AA ledger type amounts in the F0911 table (F0911) and any matching records with a CA ledger type. The matching records must have the same document number, document type, document company, general ledger date, and journal entry line number. If the system does not find AA ledger type amounts for an account, there is no corresponding CA ledger type amounts. 2. Ledger Type Specify the ledger type to display in the Ledger Type 2 field. The Second Ledger Type processing option must be set to display two ledger types.
Process
1. Exit for PK or PN document type Specify which form to use when accessing to the source document. Values are: Blank: Exit to the Manual Payment Entry form. 1: Exit to the Journal Entry form.
Currency
1. As-If Currency Specify the currency code to use as the default for the as if currency. To display the As If field, you must select As-If Currency from the Form menu on the Work With Account Ledger form. This processing option enables amounts to appear in a currency other than the currency in which they were originally entered.
350
Chapter 31
Only the amounts associated with ledger type 1 are converted to the as if currency. If you leave this processing option blank, amounts appear in the currency of the transaction. 2. Exchange Rate Date Specify the date to use for the exchange rate to display amounts in the as if currency. If you leave this processing option blank, the system uses the date in the Thru Date field on the Work With Account Ledger form.
Defaults
Object/Subsidiary Account Number Specify the default value that the system displays in the Obj/Sub field on the Work With Account Ledger by Object Account form.
Category Code
Category Code (2123) Enter the account category code from UDC table 09/2123. The default value is category 21.
Defaults
Alternate Account Enter the number that identifies the alternate account number in the category code you specified in the Category Code (2123) processing option.
351
Chapter 31
Change the value in this field to review a ledger other than AA (actual amounts) ledger. The program uses AA as the default ledger type. Change the value in this field, if necessary. This field appears only if a processing option is set to display a second ledger type.
352
Chapter 31
Display Company Subtotals Select this option to display company subtotals for the range of companies specified in the From Company and Thru Company fields.
353
Chapter 31
This section provides an overview of account balances review and discusses how to: Set processing options for Account Balance by Month (P0902P1). Set processing options for Account Balance by Subledger (P092131). Review monthly account balances. Review balances by subledger.
Navigation Accounting Reports & Inquiries (G0912), Account Balance by Month Accounting Reports & Inquiries (G0912), Account Balance by Subledger
Usage Review monthly account balances. Review balances by subledger for a specific account.
W092131A
Defaults
Fiscal Year, Ledger Type, Subledger, Subledger Type, and Currency Code For each processing, specify the default value for the system to display in the corresponding fields on the Account Balances form.
354
Chapter 31
Balance Forward
Displays the cumulative prior year-end balance. The system uses this amount as the beginning balance for balance sheet and job cost carry-forward accounts. Note. Do not confuse this amount with the prior year-end net posting amount. The prior year-end net posting amount includes only the postings from the prior year. It does not include the ending balance of the previous year. The prior year-end net postings are typically used for profit and loss statement comparisons.
Displays the prior year-end net postings. The system uses this number for profit and loss statement comparisons.
355
Chapter 31
The system displays subledger detail information on this form only if the posting edit code is not S. The Net Posting Thru Date field shows the net balance posted year-to-date while the Net Posting for Period field shows the net balance for the current period. Period Thru Period Thru Ending Date Select this check box to limit your search to a specific accounting period. To limit your search to a specific ending date, do not select this check box. If the Period check box is selected, enter a fiscal period number in this field. If you leave this field blank, the system uses the ending date of the current period. If the Period check box is not selected, enter a date in this field.
356
CHAPTER 32
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (RUS) Working With General Ledger Reporting, Fixed Assets, and Inventory Management for Russia JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (CHN) Generating Financial Reports for Beijing, Guangzhou, and Shanghai JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (ITA) Working With Functionality for Italy, Verifying Account Balances in Italy
357
Chapter 32
Description You can use any of the standard templates that are provided with the JD Edwards EnterpriseOne General Accounting system. A report template contains a fixed format for your data and predefines the number of columns, their order, and their headings. You can create your own version using any report template. A single report version can contain amounts for individual companies or consolidated totals for several companies. You can design additional, customized financial reports using the Report Design Aid tool.
Custom reports
You can print different levels of summarization on financial reports by specifying a level of detail in which to show accounts. Using AAIs, you assign the account ranges and subtotals that the system uses for the reports.
Setting Up Data Selection and Data Sequence for the Simple Income Statement and Simple Balance Sheet
You must select the object accounts that you want to include on the report. You must also specify a ledger type. If you do not, the system combines all ledger types, which could produce inaccurate results. Financial reports are designed to print in this sequence: Company Object account Subsidiary If you do not use company as your first sequence, the system uses the information for company 00000 to determine the financial reporting date. You must always use a sequence by object account and subsidiary to protect the integrity of your data and to ensure that the level-of-detail subtotals are accurate. To print a report across many business units or companies, use a sequence by object account and subsidiary only. The data sequence item that immediately precedes the object account determines page breaks and totals for all financial reports. For example, if the data sequence is by company, object account, and subsidiary, page breaks and totals occur when the company number changes. If the object account is the first data sequence item, the report has no page breaks and totals appear at the end of the report. You can change the subtotals by changing the sequence and level breaks. For example, you could create subtotals by specifying category codes for level breaks. This table shows the data sequence that is required for specific types of reports:
358
Chapter 32
Data Sequence Setup The data sequence should be: Business Unit Object Account Subsidiary
Prerequisites
Before you complete the tasks in this section: Verify that you have set up AAI items FSxx. Verify that your financial reporting period is set correctly.
359
Chapter 32
See Chapter 37, Closing Accounting and Reporting Periods, Changing Financial Reporting Periods, page 431.
Date
1. Period Number and 2. Fiscal Year Enter the period number and fiscal year that the report should be based on. If you leave these processing options blank, the system uses the financial reporting date of the company.
LOD
1. Level of Detail Enter the lowest level of account detail to print on the report.
Signs
1. Reverse Sign Specify how to print amounts. Values are: 0: Print amounts in their original debit and credit format. 1: Reverse the sign for all account types (revenues will print as positive and expenses as negative). 2: Reverse the sign of revenue accounts only (revenues and expenses will print as positive).
Calculations
1. Calculate Net Income Specify whether to calculate net income. Values are: Blank: Do not calculate net income. 1: Calculate net income.
360
Chapter 32
Headings
1. Print Heading Specify how to print headings. Values are: Blank: Print headings on the first page only. 1: Print headings with page number and run date on each page. 2: Print headings without page number and run date. 2. Date Title Type Enter the date title type to print in the page heading. If you leave this processing option blank, a date title does not print.
361
Chapter 32
Net Income = 374,379.23 This calculation is based on: Assets = 6,966,772.54 Liabilities + Equity: Current Liabilities = 755,755.74 Long-Term Liabilities = 2,027,576.49 Common Stock = 267,500.00 Paid-in-Capital = 1,535,017.77 Retained Earnings = 2,006,543.31 Total Liabilities + Equity = 6,592,393.31
Prerequisites
Before you complete the tasks in this section: Validate the net income amount on your income statement. This amount is the year-to-date income (loss) on the balance sheet. Verify that AAI items GLG2, GLG3, and GLG5 are set up. Verify that your financial reporting period is set correctly. See Chapter 37, Closing Accounting and Reporting Periods, Changing Financial Reporting Periods, page 431. For reports that cross over to a new year, verify that the Annual Close Report (R098201) ran successfully. Balance forward amounts are not created until the close process is complete. See Chapter 38, Closing the Fiscal Year, page 433.
362
Chapter 32
Signs
Reverse Sign Specify how to print amounts. Values are: 0 (zero): Print amounts in their original debit and credit format. 1: Reverse the sign for liability and equity accounts.
Computations
Calculate YTD Net Income Specify whether to calculate and print a year-to-date net income amount. Values are: Blank: Do not print a year-to-date net income amount. 1: Print a year-to-date net income amount.
See Also
Chapter 8, Setting Up Statements of Cash Flow, page 69
363
Chapter 32
If the accounts associated with the description normally have a debit balance (as specified in the F10520 table) and the balances in the F0902 table are positive (zero or greater), the system concatenates the text Increase in before the description. If the balances are negative (less than zero), it concatenates the text Decrease in. If the accounts associated with the description normally have a credit balance (as specified in the F10520 table) and the balances in the F0902 table are positive, the system concatenates the text Decrease in before the description. If the balances are negative, it concatenates the text Increase in. If amounts on the Statement of Cash Flows Report are out of balance, an error message prints at the end of the report. An out-of-balance condition occurs when the difference between beginning and ending cash and cash equivalents is not equal to the net increase or decrease in cash and cash equivalents.
364
Chapter 32
Name of Company Statement of Cash Flows For the Period Ending day/month/year Cash Flows from Operating Activities Net Profit Before Tax Adjustment for: Depreciation and Amortization Profit/Loss on Sale of Fixed Assets Decrease in Interest Expense Decrease in Other Expense Operating Profit Before Working Capital Changes Decrease in Inventory Increase in Receivables Decrease in Payables Cash Generated from Operations Increase in Taxes Paid Increase in Dividends Paid Increase in Other Non-Operating Income Increase in Other Non-Operating Expense Net Cash Flow from Operating Activities
Activity code 10 Activity code 20, line 1 Activity code 20, line 2 Activity code 20, line 3 Activity code 20, line 4 Subtotal activity code 20, lines 1-4 Activity code 30, line 1 Activity code 30, line 2 Activity code 30, line 3 Subtotal activity code 30, lines 1-3 Activity code 40, line 1 Activity code 40, line 2 Activity code 40, line 3 Activity code 40, line 4 Subtotal activity codes 10+20+30+activity code 40, lines 1-4 Activity code 50, line 1 Activity code 50, line 2 Activity code 50, line 3 Subtotal activity code 50, lines 1-3 Activity code 60, line 1 Activity code 60, line 2 Subtotal activity code 60, lines 1-2 50 100 -25 -25
1,000
Increase in Purchase of Fixed Assets Decrease in Proceeds of Sale of Fixed Assets Increase in Purchase of Other Assets Net Cash Flow from Investing Activities Decrease in Non-Current Liabilities Increase in Capital Stock (excluding Retained Earnings) Net Cash Flow from Financing Activities Net Increase/Decrease in Cash and Cash Equivalents Cash and Cash Equivalents (beginning balance) Cash and Cash Equivalents (ending balance)
365
Chapter 32
** This amount equals the difference between the beginning balance and ending balance of cash and cash equivalents.
Prerequisites
Before you complete the tasks in this section: Ensure that all financial statements for the fiscal period have been generated. Ensure that you have access to the programs in the Financial Reports system (system code 10).
Select
1. Fiscal Date Pattern Company 2. Thru Period Number and 3. Fiscal Year Specify which company fiscal date pattern you want to use to print the date on the report. If you leave this processing option blank, the system uses the current period for company 00000 and prints the corresponding date. Specify the through period number and fiscal year n which to run the Statement of Cash Flows Report. If you leave these processing options blank, the system uses the current period number and current fiscal year of the company in the Fiscal Date Pattern Company processing option. If that processing option is blank, the system uses the current period number and fiscal year of company 00000. Specify the ledger type to use for the Statement of Cash Flows Report. If you leave this processing option blank, the system uses ledger type AA. If you work in a multicurrency environment, the currency of the ledger type must be the same as the currency of the company on the report.
4. Ledger Type
Display
1. Scaling Specify the value in which to scale amounts on the report. Values are 1, 10, 100, 1000, 10000, 100000, 1000000, 10000000, 100000000, and 1000000000. The system performs rounding when it scales amounts. If you leave this processing option blank, the system does not scale amounts.
366
Chapter 32
Prerequisite
Define the column headings and data that you want to appear in each column of the consolidated financial report. See JD Edwards EnterpriseOne Tools 8.96: Development Tools: Report Design Aid Guide See JD Edwards EnterpriseOne Tools 8.96: Development Tools: Report Printing Administration Technologies Guide
367
Chapter 32
See JD Edwards EnterpriseOne Tools 8.96: Development Tools: Report Design Aid Guide See JD Edwards EnterpriseOne Tools 8.96: Development Tools: Report Printing Administration Technologies Guide
Amounts
Period/YTD Specify the account balances to appear on the report. Values are: Blank: Print year-to-date account balances. 1: Print account balances for a single period.
Calculations
Calculate Net Income Specify whether to calculate net income. Values are: Blank: Do not calculate net income. If the version uses AAI subtotaling, leave this processing option blank. The system will automatically calculate and print net income. 1: Calculate net income.
368
Chapter 32
Calculations
Compute YTD Income Specify whether to calculate year-to-date income. Values are: Blank: Do not calculate year-to-date income. 1: Calculate year-to-date income.
Signs
Reverse Sign Specify how to print amounts. Values are: 0: Print amounts in their original debit and credit format. 1: Reverse the sign for liability and equity accounts.
369
Chapter 32
Note. You must use version XJDE0006 or create a copy of the version if you want AAI subtotals to appear on your report. XJDE0006 contains additional event rules for AAI subtotaling; therefore, you cannot add a version and achieve the desired results.
Prerequisite
Verify that the financial reporting period is set correctly. See Chapter 37, Closing Accounting and Reporting Periods, Changing Financial Reporting Periods, page 431.
Signs
1. Reverse Sign Specify how to print amounts. Values are: 0: Print amounts in their original debit and credit format. 1: Reverse the sign for income statement accounts (revenues print as positive and expenses print as negative). 2: Reverse the sign for liability and equity accounts. 3: Reverse the sign for revenue accounts only (revenues and expenses print as positive).
Calculations
1. Calculate Net Income Specify the type of net income to calculate. Values are: 1: Calculate balance sheet net income. 2: Calculate profit and loss net income. 3: Do not calculate net income (default)
Columns
1. Column Format Specify the format of the twelve columns that print on the spreadsheet: 1: Last 12 Months Actual (default) 2: Year-to-Date Actual 3: Year-to-Date Actual plus Remaining Budget.
370
Chapter 32
If the Column Format processing option is set to 3, enter the ledger type for the remaining budget. If you leave this processing option blank, the system uses ledger type BA. Enter the ledger type in which to base the spreadsheet. If you leave this processing option blank, the system uses ledger type AA.
3. Ledger Type
Dates
Period Number and Fiscal Year Enter the period number and fiscal year that the report should be based on. If you leave these processing options blank, the system uses the financial reporting date of the company. For the reporting date to be company-specific, you must set the data sequence by company.
371
Chapter 32
372
CHAPTER 33
373
Chapter 33
Out-of-Balance Reports
Use the out-of-balance reports to verify that: Transactions within a company are in balance. Accounts balance on a period-by-period basis. Intercompany settlement accounts are in balance. If a batch has the Exclude Batch from Integrity Report option selected in the Batch Header Revisions program (P0011) and the batch contains an out-of-balance entry, the batch will not appear on the Batches Out of Balance and Company by Batch Out of Balance integrity reports. When you run these two integrity reports, ensure that the data selection for Include Batch on Integrity (IBOI) flag is not equal to N.
374
Chapter 33
Description Provides this transaction level information: Unposted and posted transactions without a batch header record in the F0011 table. Unposted transactions with a batch status of D (posted). In final mode, the system rebuilds missing batch header records in the F0011 table.
Provides batch level information and automatically: Deletes empty batch header records with no AR, AP, or GL detail records. Updates the batch status of a batch header record in the F0011 table to D (posted) if the detail records in the F0911 table are posted, but the header record is unposted. Based on processing option settings, updates the batch status of a batch header record in the F0011 table to D (posted) if the detail records in the F03B11 and F0411 tables are posted, but the header record is unposted.
Unposted Batches (R007011) Batches Out of Balance (R007032) Company by Batch Out of Balance (R09706) Companies in Balance (R097001)
Prints a list of unposted batches based on the batch control records in the F0011 table. Locates batches in which the net amount of debits and credits does not equal zero. Locates out-of-balance amounts within each batch by company. Prints net differences by company and fiscal year and identifies: Adjustments posted to a prior year that are not included in the balance forward amounts for an account. Amounts posted after the period cutoff. Missing intercompany settlements.
Intercompany Accounts in Balance (R097011) Account Balance to Transactions (R09705) Accounts without Business Units (R097041) Account Balance without Account Master (R097031) Transactions without Account Master (R097021)
Locates imbalances between corresponding intercompany accounts. Locates imbalances between the F0902 and F0911 tables on a period-by-period basis. Locates business unit and company discrepancies between the F0006 and F0901 tables. Also locates accounts with missing levels of detail. Locates company and account discrepancies between the F0901 and F0902 tables. Locates company and account discrepancies between the F0911 and F0901 tables.
375
Chapter 33
Post/Unposted
1. Posted/Unposted Transactions Specify the records the system selects for processing. Values are: Blank: Posted and unposted transactions. 1: Unposted transactions only.
Select
Because this is a batch header report, the system uses the batch date, not the general ledger date, to select records.
376
Chapter 33
Specify a beginning and an ending date for a range of dates to limit the records that the system selects for processing. If you leave these processing options blank, the system selects all records unless you enter a value for the Prior Days processing option.
2. Prior Days
Specify the number of days prior to the current date that the system uses to select records for processing. The system selects records with a batch date that is equal to the calculated date through the current date. For example, if you specify 30 for this processing option, the system selects records starting 30 days ago through today. If you leave this processing option blank, the system uses the dates that are specified in the From Date and Thru Date processing options.
3. Batch Type Range From Batch Type and Thru Batch Type 4. Batch Number Range From Batch Number and Thru Batch Number 5. User ID Range From User ID and Thru User ID
Specify the beginning and ending batch types for a range of batch types that the system uses to select records for processing. Enter a value from UDC table 98/IT. If you leave these processing options blank, the system selects all batch types. Specify the beginning and ending batch numbers for a range of batch numbers that the system uses to select records for processing. If you leave these processing options blank, the system selects all batch numbers. Specify the beginning and ending user IDs for a range of user IDs that the system uses for selecting records for processing. If you leave these processing option blanks, the system selects all user IDs.
G/L
If you specify a range of batch types or batch numbers in the Batch processing options and specify 1 for this GL processing option, the system identifies the batches and then compares the corresponding records in the F0911 table to the F0011 table. If you specify a range of batch types or batch numbers in the Batch processing options and leave this GL processing option blank, the system does not perform an integrity check between the F0911 and F0011 tables. 1. G/L Integrity Check Flag Specify whether the system includes records from the F0911 table for comparison with the batch control records in the F0011 table. Values are: Blank: Do not include F0911 records. 1: Include F0911 records. If you do not specify 1 for the AR or AP processing options, the system selects all batch types in the F0911 table for the integrity check
A/R
Values for these processing options are: Blank: Do not include records from the specified table for comparison with batch control records in the F0011. 1: Include records from the specified table for comparison with batch control records in the F0011. If you specify a range of batch types or batch numbers in the Batch processing options and specify 1 for any these processing options, the system identifies the batches and then compares the corresponding records in the AR table to the F0011 table.
377
Chapter 33
If you specify a range of batch types or batch numbers in the processing options and leave any of these AR processing options blank, the system does not perform an integrity check between the specified table and the F0011 table. For example, assume that you specify the batch type range IB through RB in the processing options. Then you specify 1 for the GL and AP processing options and leave the AR processing options blank. The system will perform an integrity check on the batches within the IB through RB range that exist in the F0911 table and compares them to the F0011 table. 1. A/R Ledger File F03B11 Flag 2. A/R Receipts Header File F03B13 Flag 3. Compare Receipts Header and Detail Flag Specify whether the system includes customer ledger records in the F03B11 table. Specify whether the system includes receipt header records in the F03B13 table. Specify whether the system includes receipt header records in the F03B13 and receipts detail records in the F03B14 tables.
A/P
Values for these processing options are: Blank: Do not include records from the specified table for comparison with the batch control records in the F0011 table. 1: Include records from the specified table for comparison with the batch control records in the F0011 table. If you specify a range of batch types or batch numbers in the Batch processing options and specify 1 for any these processing options, the system identifies the batches and then compares the corresponding records in the AP table to the F0011 table. If you specify a range of batch types or batch numbers in the Batch processing options and leave any of these AP processing options blank, the system does not perform an integrity check between the specified table and the F0011 table. 1. A/P Ledger File F0411 Flag 2. A/P Matching Document File F0413 Flag 3. Compare A/P Header and Detail Flag Specify whether the system includes ledger records in the F0411 table. Specify whether the system includes matching document records in the F0413 table. Specify whether the system includes matching document records in F0413 and matching document detail records from the F0414 tables.
Options
1. Rebuild Missing Batch Header F0011 Flag Specify whether the system rebuilds missing batch header records in the F0011 table. Values are: Blank: Do not rebuild missing batch header records. A message will appear on the report that there is no batch header record. 1: Rebuild missing batch header records. A message appears on the report that the missing batch header record was added. 2. Manager Approval Flag Specify whether manager approval is required to rebuild missing batch header records in the F0011 table. Values are:
378
Chapter 33
Blank: Manager approval is not required to rebuild missing batch header records. The batch status will be set to A (approved). 1: Manager approval is required to rebuild missing batch header records. The system sets the batch status to P (pending).
See Also
Chapter 34, Maintaining Batch Headers, Adding and Revising Batch Headers, page 402
379
Chapter 33
F03B11, F03B13, and F03B14 The system does one of the these: Updates the status of the batch header to D in the F0011 table if all corresponding transaction records in the batch are marked as posted. For example, if all F0911 records for batch type G are posted, but the batch header record for the batch in the F0011 table is not posted, the report updates the status of the F0011 record to D (posted). Deletes the batch header and prints a message on the report indicating that the batch was deleted if one of these situations apply: - No records exist for batch type G in the F0911 table. - No records exist in either the F03B11 table or the F03B13 and F03B14 tables and the A/R Integrity Check Flag processing option is set to 1. - No records exist in either the F0411 table or the F0413 and F0414 tables and the A/P Integrity Check Flag processing option is set to 1. Note. If the A/R or A/P Integrity Check Flag processing option is blank, the report ignores the batch regardless of whether unposted records exist in the AR or AP tables. A blank processing option indicates that the batch is not eligible for the integrity check.
Prerequisite
Correct any discrepancies that are identified on the Transactions to Batch Headers report before you run the Batch to Detail report.
Date Range
Because this is a batch level report, the system uses the batch date, not the general ledger transaction date, when selecting records. 1. From Date and 2. Thru Date Specify a beginning and an ending date for a range of dates to limit the records that the system selects for processing. If you leave these processing options blank, the system selects all records unless you enter a value for the Prior Days processing option. Specify the number of days prior to the current date that the system uses to select records for processing. The system selects records with a batch date that is equal to the calculated date through the current date. For example, if you specify 30 for this processing option, the system selects records starting 30 days ago through today. If you leave this processing option blank, the system uses the dates that are specified in the From Date and Thru Date processing options.
3. Prior Days
380
Chapter 33
A/R
1. A/R Integrity Check Flag Specify which tables the integrity check should include. Values are: Blank: Limit the integrity check to include only batch control records in the F0011 table and ledger records in the F0911 table. If you leave this processing option blank and no F0911 records exist, the batch header in the F0011 table is not deleted because the integrity check does not include the AR tables. Therefore, the batch does not appear on the report. 1: Expand the integrity check to include the F03B11, F03B13, F03B14, and F03B11Z1 tables. If you set this processing option to 1 and no records exist in the F0911 and AR tables, the batch header is deleted and a message prints on the report notifying you that it was deleted. If posted detail records exist in the AR tables, but no corresponding F0911 records exist, the batch is ignored and does not appear on the report.
A/P
1. A/P Integrity Check Flag Specify which tables the integrity check should include. Values are: Blank: Limit the integrity check to include only batch control records in the F0011 table and ledger records in the F0911 table. If you leave this processing option blank and no F0911 records exist, the batch header in the F0011 table is not deleted because the integrity check does not include the AP tables. Therefore, the batch does not appear on the report. 1: Expand the integrity check to include the F0411, F0413, and F0414 tables. If you set this processing option to 1 and no records exist in the F0911 and AP tables, the batch header is deleted and a message prints on the report notifying you that it was deleted. If posted detail records exist in the AP tables, but no corresponding records exist in the F0911 table, the batch is ignored and does not appear on the report.
Batch
1. Batch Type 2. Starting Range Of Batch Numbers and 3. Ending Range Of Batch Numbers Specify which batch type the integrity check should include. If you leave this processing option blank, the system includes all batch types. Specify a beginning and ending range of batch numbers for the system to include in the integrity check. If you leave the Starting Range of Batch Numbers processing option blank, the system includes all batch numbers through the batch number that is specified in the Ending Range of Batch Numbers processing option. If you leave the Ending Range of Batch Numbers processing option blank, the system includes all batch numbers from the batch number that is specified in the Starting Range of Batch Numbers processing option. If you leave both processing options blank, the system includes all batch numbers.
381
Chapter 33
Prerequisite
Correct any discrepancies that are identified on the Batch to Detail report before you run the Unposted Batches report.
382
Chapter 33
See Also
Appendix G, JD Edwards EnterpriseOne General Accounting Reports, R09301 - Unposted General Journal, General Journal by Batch, Unposted Cash Basis, page 502
Date Range
Because this is a batch level report, the system uses the batch date, not the general ledger transaction date, when selecting records. 1. From Date and 2. Thru Date Specify a beginning and an ending date for a range of dates to limit the records that the system selects for processing. If you leave these processing options blank, the system selects all records unless you enter a value for the Prior Days processing option. 3. Prior Days Specify the number of days prior to the current date that the system uses to select records for processing. The system selects records with a batch date that is equal to the calculated date through the current date. For example, if you specify 30 for this processing option, the system selects records starting 30 days ago through today. If you leave this processing option blank, the system uses the dates that are specified in the From Date and Thru Date processing options.
Ledger Type
1. Ledger Types Specify an additional ledger type for the system to include in the integrity check. If you leave this processing option blank, the system selects only records for ledger type AA.
383
Chapter 33
Prerequisite
To ensure accuracy, run the Company by Batch Out of Balance report when users are not accessing the system.
384
Chapter 33
Additional Ledger
Ledger Type Specify an additional ledger for the system to include in the integrity check. If you leave this processing option blank, the system selects only records for ledger type AA.
385
Chapter 33
This report identifies adjustments that posted to a prior year that are not included in the balance forward amounts for an account, amounts that were posted after the period cutoff, and missing intercompany settlements. For intercompany settlements, run this report and then run the Intercompany Accounts in Balance report (R097011) immediately to ensure that intercompany accounts are in balance. Note. The Intercompany Settlements field in the general accounting constants controls the automatic generation of intercompany entries. To automatically create intercompany entries for journal entries, you must set this constantto 1 or 2. The Companies in Balance report includes three columns. These columns appear blank if a company is in balance. If a company is out of balance, the summarized (net) amount appears in the columns as described in this table:
Column FY (fiscal year) Description This column shows the fiscal year that is out of balance, using these guidelines: If only one year is out of balance, this column shows all future years that are out of balance by the same amount because the out-of-balance amount carries forward to each year until it is corrected. All the years that follow will display out-of-balance amounts even if a specific year is in balance. If more than one year is out of balance, then the amounts for the fiscal years will be different. The earliest year with an amount is the first out-of-balance condition. Amount This column shows the amount by which the company is out of balance. This field is cumulative. For example, if fiscal year 2006 was out of balance, that amount is added to the amount column for fiscal year 2007. This column shows an amount if an entry is out of balance and was posted to a future period or to a future year.
386
Chapter 33
Run the Repost Account Ledger program (R099102) with the appropriate processing option set to print a report only. If the system identifies discrepancies on the report, run the Repost Account Ledger program in final mode to correct the discrepancies. See Chapter 35, Reposting the Account Ledger and Recalculating a Fiscal Year, Reposting the Account Ledger, page 406.
Two Companies are Out of Balance by the Same Amount in the YTD Column
This error appears on the report if the intercompany settlements were not set up properly, and therefore, were not created for some batches during posting. Ensure that you: Research the automatic accounting instructions (AAIs) that control intercompany settlements and, if necessary, correct them. Restrict the intercompany accounts to automatic journal entries (posting edit code M). Verify that the Intercompany Settlements field in the general accounting constants is set to 1 or 2. To locate the error: Run the Intercompany Accounts in Balance report to locate any imbalances. Run the Trial Balance by Object report or use the Trial Balance by Object inquiry form to determine the period in which the out-of-balance condition occurs. To correct the error, create a balancing intercompany journal entry and post with the Intercompany Settlements field set to * in the general accounting constants. If this field is not set to *, the batch creates intercompany settlements, which causes the transaction for each company to net to zero and does not eliminate the out-of-balance condition. When you are finished, you must change this field back to its original setting.
387
Chapter 33
Missing Company
This error appears on the report if a company was deleted after journal entries for the company were posted. To correct the error: Re-enter the missing company using the Company Names & Numbers program (P0010). Transfer the amounts from the missing company to another company.
388
Chapter 33
Print the Intercompany Accounts in Balance report. Set processing options for Intercompany Accounts in Balance. Locate out-of-balance intercompany accounts. Correct discrepancies on the Intercompany Accounts in Balance Report.
Ledger Type
Ledger type Enter a specific ledger type or leave this processing option blank to process all ledger types.
389
Chapter 33
390
Chapter 33
See Also
Chapter 3, Setting Up the General Accounting System, Setting Up Ledger Type Rules for General Accounting, page 21
Select
1. Company Specify the company number that the system uses to select records from the F0902 table. If you leave this processing option blank, the system selects all companies. Specify the ledger type (UDC table 09/LT) that the system uses to select records from the F0902 table. If you leave this processing option blank, the system selects all amount ledger types in the F0902 table and excludes all unit ledger types in the same table. To process records for unit ledger types, submit the report for each unit ledger type individually. Enter a specific unit ledger type in this processing option and enter the associated amount ledger type in the Amount Ledger Type processing option. For example, if you want to process unit ledger type records from the AU ledger and the associated amount ledger is AA, specify AU for the Ledger Type processing option and AA for the Amount Ledger Type processing option. 3. Fiscal Year Specify the fiscal year that the system uses when selecting records from the F0902 table. Enter the last two digits of the fiscal year. For example, enter 06 for 2006. If you leave this processing option blank, the system selects all fiscal years.
2. Ledger Type
391
Chapter 33
Specify the beginning and ending periods that the system uses to select records from the F0902 table. If you leave the Beginning Period Number processing option blank, the system selects all records with a period number that is prior to the period that is specified in the Ending Period Number processing option. If you leave the Ending Period Number processing option blank, the system selects all records with a period number after the period that is specified in the Beginning Period Number processing option. If you leave both processing options, the system selects all period numbers.
6. Business Unit
Specify the business unit that the system uses to select records from the F0902 table. If you leave this processing option blank, the system selects all business units for the company that is specified in the Company processing option. Specify the beginning and ending object account numbers in a range of object accounts that the system uses to select records from the F0902 table. If you leave the Beginning Object Account processing option blank, the system selects all records with an object account that precedes the object account that is specified in the Ending Object Account processing option. If you leave the Ending Object Account processing option blank, the system selects all records with an object account after the account that is specified in the Beginning Object Account processing option. If you leave both processing options blank, the system selects all object accounts.
Options
1. Clear invalid period balances Specify whether the system deletes period amounts in the F0902 table that have no corresponding records in the F0911 table. Values are: Blank: The system does not delete period amounts for invalid records in the F0902 table and prints the invalid records on the report. 1: Delete period amounts for invalid records in the F0902 table and prints the invalid records on the report. The system deletes period amounts for invalid records only if no records exist in the F0911 table and the corresponding ledger type has the Prevent Direct Balance Update option selected in the Ledger Type Master Setup program (P0025). Example: If an account in the F0902 table for ledger type AA has a balance of 600 in period 6 of fiscal year 2007 and no records for the account exist in the F0911 table for the same period, fiscal year and ledger type, the system deletes the F0902 amount only if the AA ledger type has the Prevent Direct Balance Update check box selected. In this situation, the system deletes the period balance from the F0902 and prints the out-of-balance amount and the message Balance Cleared on the report. Example: If an account in the F0902 table for ledger type AA has a balance of 600 in period 6 of fiscal year 2007 and the same account has a balance of 400 in the same period, fiscal year, and ledger type in the F0911 table, the system does not delete the amount from the F0902 table because the account has a balance in the F0911 table for the same period number, fiscal year and ledger type, regardless of whether the Prevent Direct Balance Update option is selected.
392
Chapter 33
Specify whether the system excludes inactive accounts when comparing period balances in the F0902 table to corresponding records in the F00911 table. Values are: Blank: Include active accounts. 1: Exclude inactive accounts.
Units
1. Amount Ledger Type Use this processing option in conjunction with the Ledger Type processing option to specify the amount ledger type that the system uses to select records from the F0902 table. Specify the amount ledger type (UDC table 09/LT) that is associated with the unit ledger type identified in the Ledger Type processing option. If you leave this processing option blank, the system uses ledger type AA.
Balance Column Has an Amount and Detail Column Does Not Have an Amount
This error appears if entries were made directly to the F0902 table. To correct this error, select the Prevent Direct Balance Update option in the Ledger Type Master Setup program for any ledger type that should not allow data entries directly to the F0902 table. Then run the Account Balance to Transactions report with the Clear Invalid Period Balances processing option set to 1 to delete invalid balances from the F0902 table.
393
Chapter 33
394
Chapter 33
Update
1. Company Number Update Specify whether to update the company number. Values are: 1: Print only the report. 2: Print the report and update the company number.
Prerequisite
Correct any discrepancies identified on the Accounts without Business Units report before you run the Account Balance without Account Master report.
Setting Processing Options for Account Balance without Account Master (R097031)
Processing options enable you to specify the default processing for reports.
Update
1. Company Update Specify whether to update the company number. Values are: 1: Print only the report.
395
Chapter 33
Prerequisite
Correct any discrepancies that are identified on the Account Balance without Account Master report before you run the Transactions without Account Master report.
396
Chapter 33
Update
1. Company Number Update Specify whether to update the company number. Values are: 1: Print only the report. 2: Print the report and update the company number.
397
Chapter 33
398
CHAPTER 34
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Working with Batches
399
Chapter 34
Typically, you should run the Batch to Detail integrity report to delete any empty batch headers. However, you can delete a batch header manually. Before you delete an empty batch header, ensure that no entries exist in the batch.
Prerequisite
Restrict user access to these programs to prevent unauthorized changes.
400
Chapter 34
FormID
Navigation G/L Advanced & Technical Operations (G0931), Batch Header Revisions
Usage Review summarized journal entries by document number. Approve and post journal entry batches. Review the batch processing status stored in the F0011 table for detailed restatement, 52 period, and cash basis batches. Change the status of a batch to approved or pending. Post a batch.
Batch Approval
W0011C
On the Work With Batches form, select Batch Approval from the Form menu. To post a batch, select Post by Batch from the Form menu to access the Work With Batch Versions Available Versions.
To create a batch header, select Create from the Form menu on the Work With Batch Headers form. To revise a batch header, select Revise from the Row menu on the Work With Batch Headers form. To delete the batch, select Delete from the Form menu on the Create/Revise Batch Header form. Confirm the deletion.
Add new batch headers and revise and delete existing batch headers.
Batch Overrides
W0011E
Select Overrides from the Form menu on the Create/Revise Batch Header form.
Specify whether to post a batch out of balance and whether to exclude a batch from appearing on an integrity report.
401
Chapter 34
Difference = 52 If you do not use batch control, or if you did not enter a total expected amount, the system compares the total amount of the transactions you enter to zero and displays the difference as a negative number in this field. Difference Documents If you use the batch control feature, the system displays the number of transactions entered in the batch. If you do not use batch control, the system displays the number as negative.
The Create/Revise Batch Header form is used by many systems. Because of this, the fields listed might not apply to batch types created in some systems. Detailed Restatement Status, 52 Period Status, and Cash Basis Status Change the value in this field to change the processing status of a batch. Values are: Blank. Batch has not been reserved or processed by this particular program. You should only have to change this field to blank if a batch ended abnormally and you would like to process it again. If you add entries to a processed batch, the system automatically resets the processing status to blank. 1: Batch has been reserved or processed by this particular program. This field applies to amounts and documents:
402
Chapter 34
Total Entered
If you use the batch control feature, the total amount entered should equal the total amount expected. This applies to both monetary amounts and the total number of documents.
403
Chapter 34
404
CHAPTER 35
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (CHL and PER) Working With General Ledger Functionality for Chile and Peru, Reposting the Account Ledger Tag File for Chile and Peru JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (POL) Working with Poland-Specific Functionality, Reposting the Account Ledger Tag File
405
Chapter 35
Repost Program Repost Account Ledger (R099102) Use this program to:
Description
Correct damaged account balances in the F0902 table. You must update account balances with the posted amounts from the F0911 table. Post by currency when it becomes an organizational requirement. You must update the F0902 table to reflect the currency information. Calculate Fiscal Year and Period (R099103) Use this program to restate account balances to a new fiscal year or period. This program recalculates the fiscal year and period in the F0911 table using a revised fiscal pattern that is specified in the Date Fiscal Patterns table (F0008). This program also maintains an audit trail of account ledger transactions that transfer account balances to new periods or fiscal years. If you run this program, you must also run the Repost Account Ledger program to update the F0902 table.
Prerequisites
Before you complete the tasks in this section: Place security on the repost program. Post all transactions to avoid creating automatic offsets to the incorrect period. Update fiscal date patterns for the company, if necessary. Back up the F0901, F0902, and F0911 tables.
406
Chapter 35
Prerequisite
Run the Repost Account Ledger program during non-business hours when no users are on the system because it can take a considerable amount of processing time.
407
Chapter 35
Mode
1. Process Mode Specify the processing mode. Values are: 1: Print report. The system prints a report that shows the changes to the F0911 table that will occur if you run the report in update mode. 2: Print report and update. The system prints a report that shows the changes made to the F0911 table and updates the F0902 table to match the F0911 table.
408
Chapter 35
409
Chapter 35
2. Run the Calculate Fiscal Year and Period program and print the report only. 3. Review the report and compare, on a line-by-line basis, the old and new CT, FQ, FY, and PN columns for accuracy. Run the Calculate Fiscal Year and Period program to update the F0911 table to reflect the new fiscal date pattern. Run the Repost Account Ledger program to restate the account balances to reflect the new fiscal date pattern. This updates the F0902 table with amounts that are based on the new period number and fiscal year that were previously assigned to the F0911 records. Use the same data selection that you used when you ran the Calculate Fiscal Year and Period program. Note. None of the financial reports processed under the old fiscal date pattern will match the information on the financial reports for the restated years.
See Also
Chapter 38, Closing the Fiscal Year, page 433 JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Organizations, Setting Up Fiscal Date Patterns
Setting Data Selection and Sequence for Calculate Fiscal Year and Period
For the data selection, enter a company, ledger type, and fiscal year or any combination of the three. If you are changing fiscal periods, do not specify a fiscal year. Do not change the data sequence.
Setting Processing Options for Calculate Fiscal Year and Period (R099103)
Processing options enable you to specify the default processing for programs and reports.
Mode
1. Process Mode Specify the processing model. Values are: 1: Print report. The system prints a report that shows the updates that will occur to the F0911 table if you run the report in update mode. 2: Print report and update.
410
Chapter 35
The system updates the F0911 table and prints a report that shows the updates made to the F0911 to use for an audit trail. You must also run the Report Account ledger program to update the F0902 table. 2. Version Name For R099102 Specify whether to run the Repost Account Ledger program. Values are: Blank: Do not run. XJDE0001: Print. The system prints a report that shows the updates that will occur to the F0902 table if you run the report in update mode. XJDE0002: Print and update. The system updates the F0902 table and prints a report that shows the updates made to the F0902 table to use for an audit trail.
411
Chapter 35
412
CHAPTER 36
Revising an Organization
This chapter provides overviews of organization revisions, account structure revisions, and tables affected by account structure revisions, lists a prerequisite, and discusses how to: Change a business unit on multiple accounts. Change accounts by object. Change accounts by subsidiary. Update the F0911 and F0902 tables. Change the company number on a business unit. Change account information. Update the Model/Consolidated field. Update category codes for business units.
413
Revising an Organization
Chapter 36
414
Chapter 36
Revising an Organization
The Business Unit Master table (F0006) might also be affected. For each account ID, the system posts these items in the F0902 table in sequential order: Account ID Fiscal year Ledger type Subledger Subledger type Currency code (denominated)
Prerequisite
Back up the F0901, F0902, and F0911 tables.
Prerequisite
Create new business units, if applicable. See Chapter 38, Closing the Fiscal Year, page 433.
415
Revising an Organization
Chapter 36
FormID
After you complete this task, complete the additional tasks necessary to update the F0911 and F0902 tables. Old Business Unit and New Business Unit Enter the number of the old business unit that you want to change and the number of the new business unit. The new business unit must exist in the F0006 table.
416
Chapter 36
Revising an Organization
FormID
417
Revising an Organization
Chapter 36
FormID
Prerequisites
Before you complete the task in this section: Verify that your account numbers are correct. Run this program during off-business hours.
418
Chapter 36
Revising an Organization
419
Revising an Organization
Chapter 36
B.U. 4 B.U. 3
420
Chapter 36
Revising an Organization
8. Enter any necessary intercompany transactions. 9. Post the intercompany transactions, if necessary. The Intercompany Settlements field must be set to * in the general accounting constants for the system to post transactions to the intercompany settlement account. 10. If you changed the Intercompany Settlements field in the previous step, change it back to its original value.
See Also
JD Edwards EnterpriseOne Financial Management Solutions Application Fundamentals 8.12 Implementation Guide, Setting Up Organizations, Setting Up Business Units
421
Revising an Organization
Chapter 36
Important! The system updates all of the fields that you select in the processing option. To exclude fields such as Category Codes 2123 that might represent your statutory chart of accounts, verify that the fields are not selected in the processing options. You should restrict access to these processing options so that your statutory chart of accounts is not inadvertently changed. The system does not update the Object.Subsidiary field. To update this field, you can change object accounts or subsidiaries, or you can run the Update BU. Obj. Sub to Jrnl Ent. program.
Global Update
1. From Business Unit Specify the business unit number from which account information will be copied. Enter a valid business unit from the F0006 table. When you run the Change Account Information program, the system copies values from accounts within this business unit to equivalent accounts in other business units. Note. You must enter a value for this processing option. 2. Processing Mode Specify the mode in which to run the Change Account Information program. Values are: Blank or 0: Proof mode. This mode generates a report, but does not update the F0901 table. 1: Final mode. This mode generates a report and updates the F0901 table. 2: Final mode. Updates the F0901 table, but does not generate a report.
Account Info
1. Fields to be included in the Global Update Select the fields to update: Account Description, Posting Edit Code, Level of Detail, Billable, Budget Pattern Code, Unit of Measure, Alternate Object/Subsidiary, Model Account, Account Category Code 123.
422
Chapter 36
Revising an Organization
ACA
1. Advanced Cost Accounting fields to be included in the Global Update: Select the fields to update: Cost Object Edit Code 14 and Item Edit Code.
Alt Desc
1. Update Alternative Descriptions Specify whether the system updates account descriptions in the Account Master - Alternate Description table (F0901D) that have been translated into alternate languages. Values are: Blank: Do not update alternate language account descriptions. 1: Update alternate language account descriptions. The system copies alternate language account descriptions that correspond to language preferences in the F0901D table for accounts within the business unit specified in the From Business Unit processing option to the F0901D table for equivalent accounts in other business units. 2. Specific Alternate Description language code. Specify a language code for the system to use when copying the alternate language account descriptions to the F0901D table. To update a specific language code, enter a code from UDC table 01/LP in this processing option and enter 1 in the Update Alternative Descriptions processing option. To update all language codes, leave this processing option blank and enter 1 in the Update Alternative Description processing option. 3. Include Alternative Descriptions on the report. Specify whether the system prints detail for the alternate language account descriptions that were copied to the F0901D table on the report. Values are: Blank: Do not print detail. 1: Print detail.
423
Revising an Organization
Chapter 36
Likewise, if you change a business unit that is not a model to a model business unit, you must run the Update Model/Consolidated Field program to update the F0901 table. The system changes the Model/Consolidated field to M for all of the accounts within the business unit. Note. If records exist for the business unit in the F0911 or F0902 table or both, you cannot change a business unit that is not a model to a model business unit The Update Model/Consolidated Field program does not update the Model/Consolidated field in the F0901 table for accounts that belong to a consolidation business unit. Instead, those accounts are updated with a value of C in the Model/Consolidated field by the Refresh Consolidation program (R10862).
See Also
Chapter 29, Processing High-Volume Consolidations, Understanding the Refresh Consolidation Program, page 295
Prerequisite
Before you complete the task in this section:
424
Chapter 36
Revising an Organization
Set up numeric-value business units as address book numbers using the Address Book Revisions program (P01012). See JD Edwards EnterpriseOne Address Book 8.12 Implementation Guide, Entering Address Book Records. Back up the F0006 table.
425
Revising an Organization
Chapter 36
426
CHAPTER 37
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, Spain JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, France JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, Italy
427
Chapter 37
428
Chapter 37
Warning or Error WACO (Post Way After Cut Off) PYEB (Period Year-End Balance)
A general accounting constant specifies whether entries can be posted to a closed period (PBCO). Because the F0010 table is cached, you must exit the EnterpriseOne system after you close an accounting period and then restart the websphere server to reset cache. The new period takes effect after you restart and return to the EnterpriseOne system.
FormID
Navigation Periodic and Annual Processes (G0924), Close Accounting Period On the Work With Companies form, select the company for which you want to close the accounting period. On the Work With Companies form, select multiple companies and then select Global Close from the Row menu.
Usage Review company information. Close an accounting period, close the last accounting period and fiscal year, and change a financial reporting period. Close an accounting period, close the last accounting period and fiscal year, and change a financial reporting period for multiple companies. The companies must have the same current period and fiscal year.
Company Setup
W0010B
W0010D
429
Chapter 37
General Accounting
Current Period Increment by 1 the value in this field to close the accounting period for JD Edwards EnterpriseOne General Accounting. The system automatically closes JD Edwards EnterpriseOne Accounts Payable and JD Edwards EnterpriseOne Accounts Receivable if these systems have the same current period as JD Edwards EnterpriseOne General Accounting.
Accounts Payable
Current Period Increment by 1 the value in this field to close the accounting period for JD Edwards EnterpriseOne Accounts Payable without closing the period for JD Edwards EnterpriseOne General Accounting and JD Edwards EnterpriseOne Accounts Receivable. If you close JD Edwards EnterpriseOne Accounts Payable and JD Edwards EnterpriseOne Accounts Receivable separately, you leave JD Edwards EnterpriseOne General Accounting open for final entries for that period.
Accounts Receivable
Current Period Increment by 1 the value in this field to close the accounting period for JD Edwards EnterpriseOne Accounts Receivable without closing the period for JD Edwards EnterpriseOne General Accounting and JD Edwards EnterpriseOne Accounts Payable.
430
Chapter 37
If you close JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable separately, you leave JD Edwards EnterpriseOne General Accounting open for final entries for that period.
The functionality of this form is the same as the Company Setup form except that you can close the accounting period and, if applicable, the fiscal year for multiple companies. To do this, the companies must have the same current period and fiscal year. Current Period Increment by 1 the value in this field for General Ledger, Accounts Payable, and Accounts Receivable.
431
Chapter 37
Financial Reporting
Reporting Period and Reporting Year Increment by 1 the value in the Reporting Period field to specify the new default period for financial reports. To close a fiscal year, increment by 1 the value in the Reporting Year field as well. You can specify a default financial reporting date that is different from the actual accounting period by decreasing the period by 1 or more in the Reporting Period field. This is often referred to as reopening a period and it allows you to generate financial statements for any prior period. Note. Use the Global Period Close form to change the financial reporting period and, if applicable, the fiscal year for multiple companies with the same current period and fiscal year.
432
CHAPTER 38
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (FRA) Working With French Functionality, Closing Accounting Periods and a Fiscal Year in France JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, (ITA) Working With Functionality for Italy, Closing a Fiscal Year in Italy
433
Chapter 38
Prints the Annual Close report (R098201). You can close the same fiscal year as often as needed. Multiple closings are often necessary to handle audit adjustments or unexpected final adjustments. If you close the fiscal year multiple times, the Annual Close program calculates and posts the correct balances without doubling or otherwise inflating balances. For example, if you run the program twice, balances are not doubled. Note. You can provide reports for the first period of the new fiscal year without performing the final year close. Run the Annual Close program to update the balance forward fields for every account in the F0902 table. This carries forward the amounts to the first period of the new fiscal year for reporting purposes.
Retained Earnings
If you need to adjust the amount of the retained earnings account, do not enter an adjusting entry. This can cause undesirable results. Instead, create a new account with the same business unit and object of the retained earnings account and a new subsidiary. You can close more than one company to a single retained earnings account. This is necessary if corporate divisions are set up as companies. You close these divisions to a single retained earnings account to consolidate reporting for the legal corporate entity.
Intercompany Settlements
After you run the Annual Close program, you might need to create journal entries for intercompany settlements to keep the companies in balance. The Annual Close program posts retained earnings to a retained earnings account for a single company but does not create automatic entries for intercompany settlements.
Prerequisites
Before you perform the final fiscal year close: Back up your entire environment for fiscal auditing purposes. You might be asked to provide reproductions of your reports as well as your electronic data files during a tax audit of your information system. Ensure that no users are accessing the F0902 table while the Annual Close program is running. If users are accessing the F0902 table, records might be skipped when the program calculates retained earnings.
434
Chapter 38
435
Chapter 38
Run year-end financial reports, trial balances, and any other reports that are required. Close the fiscal period and year for financial reporting. Run the Annual Close program.
If AAI item GLG12 is not set up, an error message does not appear on the annual close report. The system uses account 999999.99999999 as the default.
436
Chapter 38
If you close multiple companies to the same retained earnings account: - The companies must have the same fiscal date pattern. - You must use a single version that selects all of the companies that are being closed together. For data sequence, the sequence must be by fiscal year, company, and ledger type; do not change it.
Profit/Loss
Profit/Loss Specify whether to create profit/loss account records for next year if the net posting for this year has a zero balance. Values are: Blank: Do not create profit/loss records. 1: Create profit/loss records.
Orig Budget
Original Budget Specify whether to override the original budget regardless of whether record for next year already exists. Values are: Blank: Do not override the original budget. 1: Override the original budget. Note. With job cost accounts, you enter an original budget and then make changes using change orders. For example, assume that you have a job in 2008 that you budgeted for and expect to complete in 2010. You added budgetary information to the original budget in 2008. To override the original budget with new information, enter 1 for this processing option.
Print
Print Specify whether to print detail information for the retained earnings calculation. Values are: Blank: Do not print supporting detail. 1: Print supporting detail. The detailed list for retained earnings can be lengthy and should not be printed unless you need to research the retained earnings calculation.
437
Chapter 38
438
CHAPTER 39
439
Chapter 39
Summarized records are required to support the F0902 table. Unsummarized records for the current year are bypassed when the system purges prior-year journal entries. For prior-year records, summarization is optional. For the prior year. Account balances can be set to zero by the Repost Account Ledger program (R099102) if any purged prior-year records are left unsummarized. You can use the Summarize Transactions program (R09811) to summarize journal entries and replace numerous detailed records with a single record. Specifically, the Summarize Transactions program: Creates a summarized record for each accounting period, ledger type, subledger, or subledger type that contains: - A document type of BF. - A document number that is the system Julian date when you summarize transactions - A general ledger date for the period-ending dates Marks the summarized detail records in the F0911 table with Y (summarized) or blank (not summarized). Three AAI items control the account ranges that are summarized or bypassed: GLRCxx: Defines a range of accounts that must be reconciled before they are summarized. The Reconciled field in the record must have a value from UDC table 09/RC to allow summarization. GLSMxx: Defines the range of accounts not to be summarized. GLPRxx: Defines a range of accounts that are not purged. After the system creates summarized records, you can: Restate prior fiscal years, if necessary. Delete or purge records for that year from the F0911 table. Summarization adds records. You must purge and reorganize to make more disk space available. You do not have to summarize transactions for summarized reporting. You can summarize general ledger reports by setting a processing option to include a specific object account range. The Summarize Transactions program does not include data selection. To specify which transactions the system summarizes, you use processing options in conjunction with AAI items GLSMxx, GLRCxx, and GLPRxx.
Prerequisites
Before you complete the tasks in this section: Back up the F0911 table. Determine the fiscal year, companies, and ledger types that you want to summarize. To ensure adequate processing time, summarize transactions after business hours. For each ledger type that you want to summarize, verify that the Summarize Ledger Types option is selected in the Ledger Type Rules program (P0025). See Chapter 3, Setting Up the General Accounting System, Setting Up Ledger Types for General Accounting, page 20. Reconcile accounts, if necessary.
440
Chapter 39
Summarizing Transactions
Select Summarize & Purge Data (G09317), Summarize Transactions.
Select
1. Number of Periods to Retain Specify the number of periods that you want the system to retain in detail. If you enter 01, the system retains only the current period. The system uses the 14 period net posting amounts from the F0902 table to determine which periods to retain. If you have a 12-period fiscal year and you want to retain information from a prior fiscal year, add two (12+2) and enter 14 in this processing option. If you are in the third period of a fiscal year and you want to retain information from the last two periods of the prior fiscal year, enter 05 as the number of periods to retain and so on. If you want to retain information only for the current fiscal year, do not increase the number of periods by two. For example, if you are in the fourth period of a fiscal year and you want to retain information from periods 2, 3, and 4 of the current fiscal year, enter 03 as the number of periods to retain in the processing option. 2. Company 3. Business Unit 4. Starting Account ID Range 5. Ending Account ID Range 6. Subledger 7. Subledger Type 8. Ledger Type Specify the company number of the records that you want the system to summarize. Enter a valid company number from the F0010 table. Specify the business unit of the records that you want the system to summarize. Enter a valid business unit from the F0006 table. Specify a starting account ID for the range of accounts that you want the system to summarize. Enter a valid account ID from the F0902 table. Specify the ending account ID for the range of accounts that you want the system to summarize. Enter a valid account ID from the F0901 table. Specify the subledger of the records that you want the system to summarize. Specify the subledger type of the records that you want the system to summarize. Enter a valid subledger type from UDC table 00/ST. Specify the ledger type of the records that you want the system to summarize. Enter a valid ledger type from the F0025 table.
441
Chapter 39
Set data selection for Purge Prior Year JEs. Set processing options for Purge Prior Year JEs.
442
Chapter 39
You also might want to defragment the F0911 table and rebuild the table indices. Contact your database administrator for more information about this process. Note. The Purge Prior Year JEs program purges only records from the F0911 table. This program does not purge corresponding records in other systems, such as JD Edwards EnterpriseOne Accounts Payable or JD Edwards EnterpriseOne Accounts Receivable. To avoid integrity issues between JD Edwards EnterpriseOne General Accounting and other systems, contact your system administrator to develop a plan to purge corresponding records.
Prerequisites
Before you complete the tasks in this section: Back up the F0911 table. Set up purge parameters in the AAIs. See Chapter 3, Setting Up the General Accounting System, Setting Up AAIs for General Accounting, page 24. Summarize transactions.
Delete Options
1. Purge and Delete Enter 1 to purge and delete 1099 transactions that are more than three fiscal years old (current and previous two fiscal years). If you partially pay transactions, you might have 1099 transactions that are paid in separate years. These transactions are identified by * in the Payment Number. If you set this processing option to 1, the system purges and deletes these types of transactions only if they are more than three years old. Leave this processing option blank to purge but not delete any questionable 1099 transactions. 2. Delete and Purge Billable Transactions This processing option is for Service Billing clients. Enter 1 to delete and purge billable transactions that have a valid bill code. If you leave this processing option blank, any bill code other than X or Y will be purged but not deleted. However, all X and Y billable transactions will be purged and deleted.
443
Chapter 39
Prerequisite
Back up the F0902 table.
444
Chapter 39
Accounts Payable Ledger (F0411) Employee Transaction History (F0618) Employee Pay Instructions (F06106) Burden Distribution File (F0724) Account Master - Alternate Description (F0901D) Account Balances (F0902) Account Ledger (F0911) Cost Allocations/Flex Budgeting (F0912) Asset Account Balances File (F1202) Purchase Order Detail (F4311) Draw Reporting Master (F51911) You can run the Delete Account Master Records program in proof or final mode.
Prerequisite
Back up the F0901 table.
Mode
Delete Account Specify the processing mode for deleting account master records. Values are: Blank: Proof mode. Prints a report that lists the accounts to be deleted, but does not delete them 1: Final mode. Deletes the accounts and prints a report that lists the accounts that were deleted.
445
Chapter 39
Prerequisites
Before you complete the tasks in this section: Back up the F0006, F0901, F0901D, F0902, and F0911 tables. Verify that there are no transactions for the business unit or company that you are going to delete.
446
Chapter 39
Delete Records
1. Delete Records Enter either the company in which to delete business units or enter a business unit to delete. If you specify a company in this processing option, the system deletes records for all of the business units in the company. If you specify a business unit, the system deletes records for the business unit. If you specify both a business unit and a company, the system deletes records for the business unit only.
447
Chapter 39
448
APPENDIX A
Primary Tables
The General Account system uses these primary tables:
Table Name (Number) Account Master (F0901) Account Balances (F0902) Description Stores account definitions, including account numbers and descriptions. One record exists for each account. Stores account balances including net postings for each period and prior year balances (net and cumulative). One record exists for each account/ledger type/subledger/subledger type/fiscal year and, if you post by currency, transaction currency. Stores detail transactions in the general ledger. One record exists for each transaction. When you use multiple currencies, two records exist for each transaction.
Supplemental Tables
The JD Edwards EnterpriseOne General Accounting system uses these supplemental tables:
Table Name (Number) Next Numbers - Automatic (F0002) Description Stores the next available number for all automatically assigned numbers in the system, such as batch numbers and transaction numbers. Stores user-defined codes and their descriptions. Stores business unit definitions, including name and number, company, and category codes.
449
Appendix A
Table Name (Number) Date Effective Business Unit Master (F0006S) Date Fiscal Patterns (F0008) General Constants (F0009)
Description Stores business unit definitions including name and number, company, and category codes by effective date. Stores each companys fiscal date pattern. Stores the rules that control system-wide functions, such as account coding, batch control, batch approval, date validation, intercompany settlements, and batch balancing. Stores company definitions, including number and name, fiscal date pattern, and current period. Stores identification header records for each batch. Stores the rules that control how the system creates automatic balancing entries, special interim totals for reports, and general information about the chart of accounts. Stores the transaction detail for each item that is subject to tax. Stores tax information by general ledger account. Stores rules for specific ledger types, such as: Attached ledger types for units Financial rules, such as balancing required Column titles for ledger comparisons
Company Constants (F0010) Batch Control Records (F0011) Automatic Accounting Instructions Master (F0012)
Taxes (F0018) Tax Reconciliation Repository (F0018R) Ledger Type Master File (F0025)
Organization Structure Master File (F0050) Structure Definition File (F0050A) Supplemental Database Data Types (F00091) Supplemental Data (F00092) Address Book Master (F0101) WF - Account Ledger Reconciliation (F0911R) Cost Allocations/Flex Budgeting (F0912) Index Computation Entry File (F0912A)
Stores parent/child relationships for business units by structure type. Stores the organization structures that you define for grouping business units by category codes. Stores the definitions of the data types that you use to track additional information about business units. Stores additional information that you enter about business units, categorized by data types. Stores address book information, including companies, suppliers, and customers. Stores unreconciled transaction detail. The system replaces the contents of this table after each reconciliation. Stores information about recurring journal entries (allocations). Stores information about indexed allocations.
450
Appendix A
Table Name (Number) Variable Allocation File (F0912B) Bank Statement Header (F0916) Bank Statement Detail (F0917) Inter/Intra Company Account Relationships (F09190)
Description Stores information about variable numerator allocations. Stores header information about bank statements. Stores detail information about the transactions on bank statements. Stores information about configured hubs for intercompany settlements.
451
Appendix A
452
APPENDIX B
Required Fields
These fields in the F0911Z1 table are required:
Field Name EDI - User ID Alias VNEDUS Type Alpha Length 10 Definition Enter the user ID of the person who is running the process or the person who is to receive messages in the Employee Queue Manager program (P012501). This field, in conjunction with VNEDTN, VNEDBT, and VNEDLN, uniquely identifies a specific journal entry. Enter a value that, in conjunction with VNEDLN, identifies each transaction. Each new transaction number indicates a new journal entry. You can have only one transaction with the same number in a batch unless VNEDLN is different. This field normally contains the document number of the source system so that the transaction can be readily identified. Enter a value that, in conjunction with VNEDTN, identifies each line of the journal entry. Enter a value that indicates whether a record has been processed successfully. Update this field with a value of 0. If the record is processed successfully, the system updates this field to a value of 1. If an error occurs, the system leaves 0 in the field. Do not leave this field blank.
VNEDTN
Alpha
22
VNEDLN VNEDSP
Number Alpha
7 1
453
Appendix B
Field Name EDI Transaction Action EDI Transaction Type EDI - Batch Number
Alias VNEDTC
Type Alpha 1
Length
Definition Enter A for transactions to be processed. No other values are valid. Enter J for journal entries. You cannot leave this field blank. Enter a value that, in conjunction with VNEDTN, VNEDUS, and VNEDLN, uniquely identifies a transaction within a specific batch. This field also acts as a level break and causes the assignment of a new batch number each time that the value changes. You can greatly increase performance by assigning one batch number for each group of transactions that is being processed at one time. Enter a value that indicates the date of the transaction. This field is part of the header section of the journal entry; therefore, you can enter only one value for each document. Enter the general ledger date in the format that your database accepts. Some databases allow you to enter the date in a Gregorian date format (mmddyy), while others might require a Julian date format (cyyddd, where c= century). Enter 0 for transactions in the 20th century and enter 1 for transactions in the 21st century. For example, the date June 1, 2007 corresponds to the Julian date 107152 and the date June 1, 2008 corresponds to the Julian date 108153 (because the year 2008 has a leap day, February 29). Alternatively, you can leave this field blank and complete VNDGM (mm), VNDGD (dd), VNDGY (yy), and VNDG# in the month/day/year/century format. Enter the prefix of the year in VNDG#. For example, enter 20 for 2007.
VNEDTR
Alpha
VNEDBT
Alpha
15
G/L Date
VNDGJ
Date
454
Appendix B
Alias VNANI
Type Alpha
Length 29
Definition A value that represents the account number that you want to update when you process the transaction. Complete either VNANI or VNAID, or VNMCU, VNOBJ, and VNSUB to designate the account number. The first character in the VNANI field must correspond to the Symbol to Identify the Account Number in the F0009 table. For example, if the Symbol to Identify the Short Number is * and you want to enter the Short Number in VNANI, you must precede it with *. Otherwise, leave VNANI blank and enter the Short Number in VNAID. The system populates the fields that you leave blank, based on the account information that you enter. For example, if you complete the Business Unit, Object, and Subsidiary fields, the system updates the Account ID and Account Number fields when the transaction is processed. If you complete the Account Number field, the system updates the Business Unit, Object, Subsidiary, and Account ID fields when the transaction is processed.
Account ID
VNAID
Alpha
Enter a value that represents the identifier of the account that you want to update when you process the transaction. Complete either VNANI or VNAID, or VNMCU, VNOBJ, and VNSUB to designate the account number. Enter a value that helps identify the account number that you want to update when you process the transaction. Complete either VNANI or VNAID, or VNMCU, VNOBJ, and VNSUB to designate the account number. Enter a value that helps identify the account number that you want to update when you process the transaction. Complete either VNANI or VNAID, or VNMCU, VNOBJ, and VNSUB to designate the account number. Enter the tax amount for journal entries with VAT. This amount is passed to the tax calculator for validation and calculation. If the Rate/Rate Area and Tax Explanation Code fields are not passed, this field is ignored. Enter the gross amount for journal entries with VAT. This amount is passed to the tax calculator for validation and calculation. If the Rate/Rate Area and Tax Explanation Code fields are not passed, this field is ignored. Specify whether to update tax information for the account taxed in the F0911. The value 1 updates tax explanation code, tax rate/area and tax item. Enter a value for the GLDLNID field in the F0911 table. The system does not perform any validation or formatting on the value in this field.
Business Unit
VNMCU
Alpha
12
Object Account
VNOBJ
Alpha
Amount - Tax
VNSTAM
Number
15
Number
15
VNTKTX
Character
VNDLNID
Number
455
Appendix B
Alias VNCKNU
Type String
Length 25
Definition Enter a value for the GLCKNU field in the F)911 table. The system does not perform any validation or formatting on the value in this field. A value that helps identify the account number that you want to update when you process the transaction. Complete either VNANI or VNAID, or VNMCU, VNOBJ, and VNSUB to designate the account number. Enter a value that directs the system to read a specific field to locate the account number. Values are: 1: Use the value in the VNAID field. 2: Use the value in the VNANI field. 3: Use the value in the VNANI field, but this value must be the third account number, as defined in the general accounting constants. 4: Use the values assigned in VNMCU, VNOBJ, and VNSUB. 7: Use the value in VNANI, but use the character in the first position of the VNANI field to identify the format in which the account number was entered, as defined in the general accounting constants. For example, if the value in VNANI is #123, the system uses the account number format that is represented by # in the general accounting constants.
VNSUB
Alpha
Account Mode
VNAM
Alpha
Amount
VNAA
Number
15
Enter a value that represents the amount of the transaction. Enter the amount in the format that your database accepts. Some databases accept a decimal identifier, while others do not. If you are entering a foreign currency amount, leave this field blank and enter an amount in VNACR. Enter a description of the transaction. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Explanation
VNEXA
Alpha
30
Company
VNCO
Alpha
Enter the number of the company for which you are processing the transaction. This is required for multicurrency processing.
See JD Edwards EnterpriseOne Multicurrency Processing 8.12 Implementation Guide, Mapping Requirements for Processing Multicurrency Batch Journal Entries, Multicurrency Fields Required in the F0911Z1 Table.
456
Appendix B
Alpha Number
1 8
Optional Fields
You can use optional fields to provide additional information about the journal entries. These fields in the F0911Z1 table are optional:
Field Name EDI - Detail Lines Processed EDI Transaction Type Alias VNEDDL Type Number 5 Length Definition Enter the number of detail lines that are included in a specific transaction. For user verification only. Enter J for journal entry transactions or leave this field blank.
VNEDTR
Alpha
457
Appendix B
Alias VNKCO
Type Alpha 5
Length
Definition Enter a number that identifies the company of the transaction. This field is used only to differentiate transaction numbers by company. If you leave this field blank, the value is determined by the company that is associated with the business unit of the first journal entry line. If you enter a value in this field, the value must exist in the F0010 table. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Document Type
VNDCT
Alpha
Enter a code that identifies the type of transaction. If you leave this field blank, the system uses JE. If you enter a value in this field, the value must exist in user-defined code (UDC) table 00/DT. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Document Number
VNDOC
Number
Enter a number that identifies the transaction in the F0911 table. If you leave this field blank, the system uses next numbers for System 09 to generate a document number. If you enter a value in this field, the value cannot exist in the F0911 table with the same general ledger and document type, or the transaction is considered a duplicate and is not processed. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
VNJELN
Number
Enter a value that you use to track the number of lines in a journal entry. If you leave this field blank, the system updates it when it processes the transactions. The maximum number of journal entry lines in a transaction is 9999. Enter a code that indicates the line extension. If you leave this field blank, the General Ledger Post program (R09801) updates it if multicurrency intercompany settlements exist. Enter a value that indicates whether the transaction has been posted. If you leave this field blank, the General Ledger Post program updates it. If the transaction represents a model journal entry, enter M.
VNEXTL
Alpha
VNPOST
Alpha
458
Appendix B
Field Name
Alias
Type Number 8
Length
Definition Enter a number used to group journal entries that are processed simultaneously. If you leave this field blank, the system uses next numbers for System 00 to generate a batch number. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Batch Type
VNICUT
Alpha
Enter a code that designates the type of transaction being processed (invoice, voucher, and so on). If you enter a value in this field, the value must exist in UDC table 98/IT. If you leave this field blank, the system populates the field with G when it processes the journal entries. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Batch Date
VNDICJ
Date
Enter the date of the batch. If you leave this field blank, the system uses the date on which the batch program is executed. If you complete this field, enter the date in a format that your database accepts. Review the field definition for VNDGJ for more information. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
VNDSYJ
Date
Enter the date on which the batch was entered into the system. If you leave this field blank, the system uses the date on which the batch program is processed. If you complete this field, enter the date in a format that your database accepts. Review the field definition for VNDGJ for more information. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Batch Time
VNTICU
Number
Enter the time when the batch was entered into the system. If you leave this field blank, the system uses the time that the batch program is processed. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Subledger
VNSBL
Alpha
Enter a code that identifies an auxiliary account for the transaction. If you complete this field, you must also enter a value in VNSBLT. Enter a code that identifies a category within a subledger. If you complete this field, the value must exist in UDC table 00/ST.
Subledger Type
VNSBLT
Alpha
459
Appendix B
Alias VNLT
Type Alpha 2
Length
Definition Enter a code that identifies the type of ledger. You can leave this field blank, or enter AA or any other valid ledger type in UDC table 09/LT except CA. Never enter CA in this field. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Period Number
VNPN
Number
A code that indicates the accounting period. We recommend that you leave these fields blank. The system populates them, based on the general ledger date and company. The century in which the transaction takes place. if you leave this field blank, the system populates it based on the general ledger date and company. The year in which the transaction takes place. If you leave this field blank, the system populates it based on the general ledger date and company. A previous exchange rate. Any value that you enter in this field is passed. The system does not validate it. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Century
VNCTRY
Number
Fiscal Year
VNFY
Number
Number
15
Historical Date
VNHDGJ
Date
Any value that you enter in this field is passed. The system does not validate it. If you complete this field, enter the date in a format that your database accepts. Review the field definition for VNDGJ for more information. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Units
VNU
Number
15
Enter the number of units in the transaction. If you complete this field, the system updates the Amount field with the value in the AU ledger when you run the Post General Ledger program (R09801). Enter a value that describes the type of units entered. If you enter a value in this field, the value must exist in UDC table 00/UM. If you leave this field blank and a unit of measure is assigned to the account in the F0901 table, the system updates this field with that unit of measure. Any value that you enter in this field is passed. The system does not validate it.
Unit of Measure
VNUM
Alpha
G/L Offset
VNGLC
Alpha
460
Appendix B
Alias VNRE
Type Alpha 1
Length
Definition Enter a value that indicates whether you want to reverse accrual entries. If you enter R (reverse) in this field, when the entry is posted, the system generates another journal entry with a general ledger date that is the first day of the next period. The transaction amount is reversed from the original entry. Voided transactions are not eligible for this process. You must use the Journal Entry program (P0911) to void journal entries. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
VNEXR VNR1
Alpha Alpha
30 8
Enter a description for a specific journal entry line. Any value that you enter in this field is passed. The system does not validate it. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
Reference 2
VNR2
8 3 8 5
Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it.
Document Pay VNSFX Item Document Original Document Company (Purchase Order) Document Company (Original Order) Document Type Purchase Order Address Number VNODOC VNPKCO
VNOKCO
Alpha
Any value that you enter in this field is passed. The system does not validate it.
VNPDCT
Alpha
Any value that you enter in this field is passed. The system does not validate it.
VNAN8
Number
Enter the address book number of the customer or supplier who is associated with a voucher or invoice transaction. If you enter a value in this field, it must exist in the F0101 table. Enter the payment number for the transaction.
Payment Number
VNCN
Alpha
461
Appendix B
Alias VNDKJ
Type Date 6
Length
Definition Enter the payment date that is associated with the payment number. Use a format that your database accepts. Review the field definition for VNDGJ for more information. Enter the date on which the payment cleared the bank. Use a format that your database accepts. Review the field definition for VNDGJ for more information. The asset ID that is associated with a fixed asset. The system verifies that this field exists in the F1201 table. Any value that you enter in this field is passed. The system does not validate it. Enter a value that indicates whether the record is reconciled. You can enter R in this field to indicate that the record is reconciled. Any value that you enter in this field is passed. The system does not validate it.
Check Cleared VNDKC Date Serial Number Batch Rear End Posted Code Reconciled Code VNASID VNBRE
Date
Alpha Alpha
25 1
VNRCND
Alpha
Summarized Code Purge Code Flag for 1099 G/L Posting Code Alternate 1 G/L Posting Code Alternate 2 G/L Posting Code Alternate 3 G/L Posting Code Alternate 4 G/L Posting Code Alternate 5
1 1 1 1
Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it.
VNALT2
Alpha
VNALT3
Alpha
VNALT4
Alpha
VNALT5
Alpha
462
Appendix B
Field Name G/L Posting Code - Cash Basis Account Commitment Relief Flag Billing Control Currency Update G/L Posting Code Alternate 0 Consumption Tax Cross Reference Delete Not Allowed Client Free Form Alternate 1 Client Free Form Alternate 2 Lease Cost Ledger Posted Code Bill Code Supplier Invoice Number
Alias VNALT6
Type Alpha 1
Length
Definition Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. We recommend that you leave this field blank.
1 1 1 1
VNALTX
Alpha
Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. If you enter a value in this field, the value must exist in UDC table 98/BC. An invoice number for the transaction. Any value that you enter in this field is passed. The system does not validate it. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
VNDLNA VNCFF1
Alpha Alpha
1 1
VNCFF2
Alpha
VNASM
Alpha
VNBC VNVINV
Alpha Alpha
1 25
463
Appendix B
Alias VNIVD
Type Date 6
Length
Definition The invoice date for the transaction. Use a format that your database accepts. Review the field definition for VNDGJ for more information. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
VNWR01 Categories Work Order 01 Purchase Order Purchase Order Suffix Order Type Line Number Fiscal Year Weekly Fiscal Period Weekly Closed Item - As Of Processing Sequence Number Operations Job Type (Craft) Code Job Step Business Unit - Home VNPO VNPSFX VNDCTO VNLNID VNWY VNWN VNFNLP
4 8 3 2 6 2 2 1
Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. If you enter a value in this field, the value must exist in UDC table 00/DT. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. A value that indicates the business unit for the transaction. If you enter a value in this field, the system verifies that it exists in the F0006 table. This field is part of the header section of the journal entry. Therefore, you can enter only one value for each document.
VNOPSQ
Number
6 4 12
DOI Stub
VNDOI
Number
Any value that you enter in this field is passed. The system does not validate it.
464
Appendix B
Field Name
Alias
Length
Definition Any value that you enter in this field is passed. The system does not validate it. Any value that you enter in this field is passed. The system does not validate it. The service or tax date of the transaction. Use a format that your database accepts. If you leave this field blank, the system uses the value from VNDGJ. Review the field definition for VNDGJ for more information.
Ignored Fields
The system does not use values in ignored fields. The fields in this table are ignored by the system.
Field Name Type Record Record Sequence EDI - Document Type EDI - Transaction Set Number EDI - Translation Format EDI - Transmission Date EDI - Send/Receive Indicator Batch File Create G/L Record User Address Number Fiscal Quarter (Obsolete) Reference 3 - Account Reconciliation Document Type Original Document Pay Item Original G/L Posting Code Alternate T VNEDTY VNEDSQ VNEDCT VNEDTS VNEDFT VNEDDT VNEDER VNEDGL VNEDAN VNFQ VNR3 VNODCT VNOSFX VNALTT Alias Alpha Number Alpha Alpha Alpha Date Alpha Alpha Number Number Alpha Alpha Alpha Alpha Type 1 2 2 6 10 6 1 1 8 2 8 2 3 1 Length
465
Appendix B
Field Name G/L Posting Code Alternate U Stock Inventory Commitment G/L Posting Code Alternate W G/L Posting Code Alternate Z Registration Number Payment ID Transaction Originator User ID Program ID Work Station ID Date Updated Time Last Updated VNALTU VNALTV VNALTW VNALTZ VNREG# VNPYID VNTORG VNUSER VNPID VNJOBN VNUPMJ VNUPMT
Alias Alpha Alpha Alpha Alpha Number Number Alpha Alpha Alpha Alpha Date Number
Type 1 1 1 1 8 15 10 10 10 10 6 6
Length
Required Fields
You must populate these fields in the F0911Z1 table for each transaction that you want to update in the JD Edwards EnterpriseOne General Accounting system: VNEDUS (EDI - User ID). VNEDBT (EDI - Batch Number). VNEDTN (EDI - Transaction Number). VNEDLN (EDI - Line Number). VNEDSP (EDI - Processed Flag) - The value in this field must be 2. VNDOC (Document Number).
466
Appendix B
The values in these fields must match the records that you want to update in the F0911 table: VNDCT (Document Type) VNKCO (Document Company) VNDGJ (G/L Date) VNJELN (Journal Entry Line Number) VNEXTL (Line Extension Code) VNRCND (Reconciled Code) VNDKC (Check Cleared Date) After you populate the F0911Z1 table, you run the Update Externally Reconciled Transaction program to update the transactions from the F0911Z1 table to the JD Edwards EnterpriseOne General Accounting system.
467
Appendix B
468
APPENDIX C
See Also
Chapter 20, Processing Bank Statements Automatically, page 179
Records
The information in the BAI2 bank flat file is grouped by record. The tables in this section are organized by record and contain information about whether a field is required (R) or optional (O) according to BAI2 requirements, whether the conversion flow maps the field in a record to an EnterpriseOne field, and so on.
469
Appendix C
BAI2 example
Record 01
Record 01 is the header record that indicates the beginning of the table. It identifies the sender and receiver and describes the table structure. Record 01 ends with the file trailer record (99).
Required or Optional R R R R Field Description Record Code Sender Identification Receiver Identification File Creation Date Field Position 1 2 3 4 EnterpriseOne Table and Field Not applicable F09610.SGBSSID F09610.SGBSRID F09610.SGSTMD F09611.BGSTMD R File Creation Time 5 Not applicable Numeric 4 Field Type and Length Numeric 2 String 9 String 9 Numeric 6
Description The value for this field is always 01. The company or bank that sends the flat file. The company or bank that receives the flat file. The date of the bank statement, in the YYMMDD format. This field does not map to an EnterpriseOne table.
470
Appendix C
Required or Optional R
Field Position 6
Description The bank statement number. Each flat file with the same creation date must have a different bank statement number. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. The value for this field is always 2.
Not applicable
Numeric 5
Not applicable
Numeric 5
Version Number
Not applicable
Numeric 1
Record 02
Record 02 is the group header record. It identifies the group of bank statements with the same as of date and time. Record 02 ends with the group trailer record (98).
Required or Optional R O Field Description Record Code Field Position 1 EnterpriseOne Table and Field Not applicable Not applicable Field Type and Length Numeric 2 String 9
Description The value in this field is always 02. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. The date of the transaction, in YYMMDD format. This field does not map to an EnterpriseOne table.
Not applicable
String 9
Group Status
Not applicable
Numeric 1
As-Of Date
F09611 BGVLDT
Numeric 6
As-Of Time
Not applicable
Numeric 4
471
Appendix C
Required or Optional O
Field Position 7
Description The currency of the amount in record 03. The currency code must exist in the F0013 table. This field does not map to an EnterpriseOne table.
As-Of-Date Modifier
Not applicable
Numeric 1
Record 03
Record 03 is the account identifier and summary status. It identifies the account number and shows account activity and status. Record 03 ends with the account trailer record (49).
Required or Optional R R Field Description Record Code Customer Account Number Field Position 1 2 EnterpriseOne Table and Field Not applicable F09610 SGBAN F09611 BGBAN O Currency Code 3 Not applicable String 3 This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. The opening and closing balances. Summary amounts are positive and do not include a sign. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. Field Type and Length Numeric 2 String 29
Description The value in this field is always 03. The commercial account number. This number should include significant leading zeros.
Type Code
Not applicable
String 3
Amount Summary
F09610 SGOPBAA
Numeric 15, 2
Item Count
Not applicable
Numeric 5
Funds Type
Not applicable
Character 1
472
Appendix C
Required or Optional O
Field Position 8A
Description This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table.
Value Time
9A
Not applicable
Numeric 4
Amount Immediate Availability Amount - 1 Day Availability Amount - 2 or more Day Availability Number of Distributions
8B
Not applicable
Numeric 15, 2
8B
Not applicable
Numeric 15, 2
10B
Not applicable
Numeric 15, 2
8C
Not applicable
Numeric 1
Day Availability 1 9C
Not applicable
Numeric 1
Not applicable
Numeric 15, 2
Not applicable
Numeric 1
Not applicable
Numeric 15, 2
Not applicable
Numeric 1
Not applicable
Numeric 15, 2
Record 16
Record 16 contains transaction detail with accompanying text and reference numbers. All type 16 records correspond to the account number in the Record 03.
473
Appendix C
Required or Optional R R
Field Position 1 2
Description The value in this field is always 16. The type code for the detail transaction. The value for this field must exist in UDC table 09/BA. Unsigned. The type code for the transaction amount indicates whether the amount is a debit or credit. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table.
F09611 BGAA
Numeric 15, 2
Funds Type
Not applicable
Character 1
Value Date
5A
Not applicable
Numeric 6
Value Time
6A
Not applicable
Numeric 4
Amount Immediate Availability Amount - 1 Day Availability Amount - 2 or more Day Availability Number of Distributions
5B
Not applicable
Numeric 15, 2
6B
Not applicable
Numeric 15, 2
7B
Not applicable
Numeric 15, 2
5C
Not applicable
Numeric 1
Day Availability 1 6C
Not applicable
Numeric 1
Amount Available 7C 1
Not applicable
Numeric 15, 2
474
Appendix C
Required or Optional O
Field Description
Field Position
Description This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. A number defined by the bank. This number cannot include a comma or a slash. A number defined by the bank. Typically, this is the deposit or payment number. An informational field used for references purposes only.
Day Availability 2 8C
Not applicable
Numeric 15, 2
Not applicable
Numeric 1
Not applicable
Numeric 15, 2
F09611 BGBANKREF
String 16
F09611 BGCUSTREF
String 16
F09611 BGINFO1
String 360
Record 88
Record 88 is the continuation record for record 16. If the data in record 16 exceeds the maximum physical record length or if dividing the record is necessary for any reason, the continuation record allows the data to continue in the same format.
Required or Optional R Field Description Record Code Field Position 1 EnterpriseOne Table and Field Not applicable Field Type and Length Numeric 2
Description This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table.
Not applicable
Not applicable
475
Appendix C
Record 49
Record 49 is the account trailer record. It provides account level control totals and includes the sum of all amount fields in record type 03 as well as the total number of records associated with an account from records 16 and 88. A record 49 exists for each record 03. Although the fields in record 49 do not map to EnterpriseOne fields, the information in the record is used to identify the end of the transactions and balances for an account.
Required or Optional R R Field Description Record Code Account Control Total Number of Records Field Position 1 2 EnterpriseOne Table and Field Not applicable Not applicable Field Type and Length Numeric 2 Numeric 15, 2
Description The value in this field is always 49. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table.
Not applicable
Numeric 5
Record 98
Record 98 is the group trailer record. It provides group control totals and corresponds to the group header in record type 02. Although the fields in record 98 do not map to EnterpriseOne fields, the information in the record is used to identify the end of the bank statement.
Required or Optional R R R R Field Description Record Group Control Total Number of Accounts Number of Records Field Position 1 2 3 4 EnterpriseOne Table and Field Not applicable Not applicable Not applicable Not applicable Field Type and Length Numeric 2 Numeric 15, 2 Numeric 5 Numeric 5
Description The value in this field is always 98. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table.
Record 99
Record 99 is the file trailer record. It provides file control totals and corresponds to the file header in record type 01. Although the fields in record 99 do not map to EnterpriseOne fields, the information in the record is used to identify the end of the text file. Each text file has one record 99 and one record 01. Record 01 identifies the beginning of the text file.
476
Appendix C
Required or Optional R R R R
Field Position 1
EnterpriseOne Table and Field Not applicable Not applicable Not applicable Not applicable
Description The value in this field is always 99. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table. This field does not map to an EnterpriseOne table.
Blocks
The information in the SWIFT bank flat file is grouped by block. This section contains field information for blocks 2 and 4. It does not contain information for blocks 1 (basic header), 3 (user header), and 5 (trailers) because the fields in those blocks do not map to EnterpriseOne fields. The tables in this section are organized by block and contain information about whether a field is required (R) or optional (O) according to SWIFT requirements, whether the conversion flow maps the field in a record to an EnterpriseOne field, and so on. Because fields can be optional according to SWIFT requirements, the field positions listed in the tables in this section may not reflect the actual field positions in the text file. For example, assume that field positions 16 are required, positions 710 are optional, and positions 1112 are required. If your bank text file does not contain values for positions 710, then positions 1112 will become positions 78. Any subsequent field positions would be adjusted accordingly.
477
Appendix C
SWIFT example
Block 2
Block 2 contains messages and bank statement information.
Field Position 1 EnterpriseOne Table and Field F09610 SGFIO R Message Type 24 F09610 SGMESST R R Time of Message 58 Not applicable F09610 SGSTMD F09611 BGSTMD R Description 1560 F09610 SGDESC04 String 46 A description of bank information. Numeric 4, 0 Date 6 String 4 Field Type and Length Character 1
SWIFT R
Description The value in this field is always 2. Only message type 940 is processed. This field does not map to an EnterpriseOne table. The date of the bank statement.
Block 4
Block 4 contains opening balances, transactions amounts and dates, closing balances, and forecasting amounts. Fields 61 and 86 can be repeated, but they must always occur before field 62.
478
Appendix C
SWIFT R
Field 20
25
135
F09610 SGBAN
String 35
28C
15
Numeric 15
Separator
28C
Not applicable
Character 1
This field is required only if there is a sequence number. This field does not map to an EnterpriseOne table.
Sequence Number
28C
711
Numeric 5
Opening Balance Debit/Credit Indicator Opening Booking Date Opening Balance Currency Code
60m or 60f
F09610 SGOBDBCR
Character 1
The debit (D) or credit (C) indicator for the opening balance. The value date for the opening balance, in YYMMDD format. The 3-character ISO currency code associated with the opening balance amount.
27
F09610 SGOLVDT
Date 6
810
String 3
1125
F09610 SGOPBAA
Numeric 15, 2
The opening balance amount. The date that the transaction clears the bank, in YYMMDD format.
16
F09611 BGVLDT
Date 6
479
Appendix C
SWIFT O
Field 61
Description This field does not map to an EnterpriseOne table. The indicator for debit (D), credit (C), reversal of credit (RC), or reversal of debit (RD). The third character of the ISO currency code. The amount of the transaction. The transaction type identification code. The customer reference, such as payment or receipt. If an external bank reference exists, this field is required. This field does not map to an EnterpriseOne table.
1112
F09611 BGDDBCR
String 2
61
13
F09611 BGCURRT
Character 1
61
1428
F09611 BGAA
Numeric 15, 2
61
2932
F09611 BGTRANT
String 4
61
3348
F09611 BGCUSTREF
String 16
Separator
61
4950
Not applicable
61
5166
F09611 BGBANKREF
String 16
The account servicing institutions reference. If detail (positions 71-102) exists, this field is required. This field does not map to an EnterpriseOne table.
61
6770
Not applicable
Detail
61
71102
F09611 BGSUBF9
String 34
The supplementary details. An informational line that can contain 65 characters. There are six informational lines.
Informational line
86
All
F09611 BGINFO1
String 390
480
Appendix C
SWIFT R
Field Description Closing Balance Debit/Credit Indicator Closing Booking Date Closing Currency Code Closing Balance Amount Closing Available Balance Debit/Credit Indicator Closing Available Value Date Closing Available Currency Code Closing Available Balance Forward Available Balance Debit/Credit Indicator Forward Available Value Date
Field Position
Description The indicator debit (D) or credit (C) for the closing balance amount. The date of the closing balance, in YYMMDD format. The 3-character ISO currency code for the closing balance. The closing balance amount. Field 64 is optional, but if it is used all subfields are required. The value date for the closing available balance, in YYMMDD format. The 3-character ISO currency code for the closing available balance. The closing available balance amount. Field 65 is optional, but if it is used all subfields are required. The value date for the forward available balance, in YYMMDD format.
27
F09610 SGCBDBCR
Date 6
810
F09610 SGCCRCD
String 3
1125
F09610 SGCLBAA
Numeric 15, 2
F09610 SGCADBCR
Character 1
64
27
F09610 SGCAVLDT
Date 6
64
810
F09610 SGCACRCD
String 3
64
1125
F09610 SGCAVAA
Numeric 15, 2
65
F09610 SGFADBCR
Character 1
65
27
F09610 SGFVLDT
Date 6
481
Appendix C
SWIFT R
Field 65
Description The 3-character ISO currency code for the forward available balance. The forward available balance amount.
65
1125
F09610 SGFAVAA
Numeric 15, 2
482
APPENDIX D
Free Form Account Number Enter a value in this field only if you entered 2 for the Account Number processing option (ANS) for the Upload/Conversion Revisions program. This is commonly referred to as the third account number and is typically used to enter the account number from a prior system. No limitations exist for the characters that you can use. Account Number (ANI) Enter the entire account number, including business unit, object account, and subsidiary (if applicable). Enter a value in this field only if you entered 3 for the Account Number processing option for the Upload/Conversion Revisions program. Enter the number of the business unit. Use this field in conjunction with the Object Account and Subsidiary fields) only if you entered 4 for the Account Number processing option for the Upload/Conversion Revisions program.
483
Appendix D
Complete Corresponding Cell in Spreadsheet Enter the object account number. Use this field in conjunction with the Business Unit and Subsidiary fields only if you entered 4 for the Account Number processing option for the Upload/Conversion Revisions program. Enter the subsidiary of the account. Use this field in conjunction with the Business Unit and Object Account fields only if you entered 4 for the Account Number processing option for the Upload/Conversion Revisions program. Enter the value of the subledger for the account. This value is 8 alphanumeric characters. Enter the value of the subledger type for the account. This value is one alphanumeric character. Enter the budget amount for periods 114. Use these fields to import budgets by period. This value is 15 numeric characters. Use this field to import annual budgets. This value is 15 numeric characters. Use this field to enter a prior year posting for this account. This value is 15 numeric characters. Enter a value in this field if you use 52 period accounting. This value is 15 numeric characters. Use this field to import annual budget that are approved. This value is 15 numeric characters. Use this field to import annual budgets that are requested. This value is 15 numeric characters. Use this field to enter a beginning balance for this account. This value is 15 numeric characters.
Subsidiary
Subledger (SBL) Subledger Type (SBLT) Net Posting 01 (AN01) Net Posting 14 (AN14) Original/Beg Budget (BORG) Prior Year Net Postings (APYN) Week to Date Net Postings (AWTD) Approved Budget (BAPR) Requested Budget (BREQ) Beg Balance/PYE Forward (APYC)
484
Appendix D
Company (CO) Date Updated (UPMJ) Budget Memo Change (POU) Commitment Memo Changes (TKER) % Cmp (PC) Note. The system completes the Currency Code Denominated field (CRCX) with the currency of the company to which the accounts belong. The Currency Code From field (CRCD) is typically left blank for budget ledgers.
485
Appendix D
486
APPENDIX E
IAEDBT
Alpha
15
IAEDTN
Alpha
22
Direction Indicator
IADRIN
Alpha
487
Appendix E
Alias IATNAC
Length
Definition Enter A for transactions to be processed. No other values are valid. Leave this field blank because the system populates it. The value N indicates that the transaction was not processed or was processed in error. After the transaction is successfully processed, the system changes the value in this field to Y. Enter the name of the consolidation. This value must exist in UDC table. Enter the general ledger period number of the transaction. Enter the last two digits of the fiscal year. The first two digits of the fiscal year. Enter the ledger type of the transaction. This ledger type must exist in UDC 09/LT. If you leave this field blank, the system uses ledger type AA. Enter the company of the transaction. This company must exist in the F0010 table.
Consolidation Name Period Number General Ledger Fiscal Year Century Ledger Type
3 2 2 2 2
Document Company
IACO
Alpha
488
Appendix E
Field Name EDI Transmission Date EDI - Detail Lines Processed Trading Partner ID
Alias IAEDDT
Type Date 6
Length
IAEDDL IAPNID
5 15 1 15
Not used to process consolidations. Not used to process consolidations. Not used to process consolidations. Not used to process consolidations.
Transmission File IATRFG Status Number of Records Transmitted Date - Sent Number of Records Received Date - Received Prior Period Adjustments Debits = Credits Source UDC = Target UDC IATRSE
IADTSE IATRRC
Date Number
6 15
6 1 1 1 1 1
Not used to process consolidations. Not used to process consolidations. Not used to process consolidations. Not used to process consolidations. Not used to process consolidations. Not used to process consolidations.
Source OBJ/Sub IAIN04 = Target OBJ/Sub Accounts Last Month Not This Month Business Units Last Month Not This Month Accounts This Month Not Last Month Business Units This Month Not Last Month Integrity Control Status 9 IAIN05
IAIN06
Alpha
IAIN07
Alpha
IAIN08
Alpha
IAIN09
Alpha
489
Appendix E
Field Name Integrity Control Status 10 Integrity Control Status 11 Integrity Control Status 12
Length
Definition Not used to process consolidations. Not used to process consolidations. Not used to process consolidations.
490
Appendix E
Field Name EDI - Batch Number EDI Transaction Number File Line Identifier Direction Indicator Transaction Action EDI Successfully Processed
Alias SZEDBT
Type Alpha
Length 15
Definition Enter a number used to group transactions for processing. This field, in conjunction with SZEDUS and SZEDTN, uniquely identifies a specific transaction. Enter a number that identifies a transaction. This field, in conjunction with SZRC5), uniquely identifies each transaction. This field, in conjunction with SZEDUS and SZEDBT, also uniquely identifies a specific transaction. Enter a number that, in conjunction with SZEDTN, identifies each line of the transaction. Enter 1 in for inbound transactions. this indicates that the record was written by an external system. Enter A for transactions to be processed. No other values are valid. Leave this field blank because the system populates it. The number 0 indicates that the transaction was not processed or was processed in error. After the transaction is successfully processed, the system changes the value in the field to 1. Enter the business unit of the transaction. This value must be entered in the format that is defined in the account structure. Enter the object account of the transaction. This value must be entered in the format that is defined in the account structure. Enter the subsidiary account of the transaction. This value must be entered in the format that is defined in the account structure. Enter a description of the account.
SZEDTN
Alpha
22
5 1 1 1
Alpha
12
SZOBJ
Alpha
SZSUB
Alpha
Description
SZDL01
Alpha
30
SZSBLT
Alpha
491
Appendix E
Field Name Currency Code - From Currency Code Denominated In Amount Beginning Balance/PYE Forward
Length
Definition Enter a code that identifies the currency of the transaction. The value in this field must exist in the F0013 table. Enter a code that identifies the currency in which the transaction was denominated. The value in this field must exist in the F0013 table. Enter the cumulative prior year-end balance. The system uses this amount as the beginning balance for balance sheet and job cost accounts. Enter the net amount that is posted during the specified accounting period. These fields represents accounting period 0114. The system uses the accounting periods from the F0010 table. For each period, the net amount posted is the total of all debits and credits from the first day of the period through the last day of the period. Enter the prior year-end net postings. The system uses this number for profit and loss statement comparisons. Not used to process consolidations. Not used to process consolidations.
SZAPYC
Number
15
Number
15
Amount Prior Year Net Postings Amount Week to Date Amount Original/ Beginning Budget Budget Requested Budget Approved
SZAPYN
Number
15
SZAWTD SZBORG
Number Number
15 15
SZBREQ SZBAPR
Number Number
15 15
492
Appendix E
Field Name User Reserved Amount User Reserved Number Transaction Originator SZURAT SZURAB SZTORG
Type 15 8 10
Length
493
Appendix E
494
APPENDIX F
See Also
JD Edwards EnterpriseOne Tools 8.96 Workflow Tools Guide
Description
Workflow Description
The system sends a workflow message to a specified batch approver when a secured user creates a journal entry. The batch remains at a status of P (pending) and cannot be posted until the approver changes the batch status to A (approved). A secured user creates a journal entry batch. The approver for the secured user receives a workflow message to approve the batch. When the approver selects the message in the Work center, the system displays the Work With Batches form. The approver can review the batch and then select Batch Approval from the Row menu to approve the batch.
495
Appendix F
Workflow Objects
System Workflow Object Name Object ID Event Description / Function Name Sequence / Line Number
Description
Workflow Description
The system sends a workflow message to an auditor or manager when a secured user submits an expense report. The auditor or manager is specified as the approver in the routing rules for the expense report. A secured user submits an expense report. The approver for the secured user receives a workflow message to approve the expense report. When the approver selects the message in the work center, the system displays the Expense Report Approval form. The approver can review and approve the expense report on the form.
Workflow Objects
System Workflow Object Name Object ID Event Description / Function Name Sequence / Line Number
496
APPENDIX G
See Also
JD Edwards EnterpriseOne Country-Specific Setup and Processes 8.12 Implementation Guide, JD Edwards EnterpriseOne Country-Specific Reports
497
Appendix G
498
Appendix G
Report ID and Report Name R09206 Account Master Report Cat. Code 2433 R09207 Account Master Report Cat. Code 3443 R09301 Unposted General Journal Unposted Cash Basis Report R09301 General Journal by Batch R09311 General Journal by Account R09321 Transaction Journal
Description Prints the accounts in your chart of accounts that are associated with category codes 2433. Prints the accounts in your chart of accounts that are associated with category codes 3443. Prints unposted transactions.
Navigation Financial Reports (G75C09), Account Master Report Cat. Code 2433
Journal Entry, Reports, & Inquiries (G0911), Unposted General Journal Cash Basis Accounting (G09314), Unposted Cash Basis Report (R09301)
Prints posted and unposted journal entries in batch number sequence. Prints posted and unposted transactions by account. The report provides totals by account number. Prints transactions within a general ledger date range. This report prints the debit and credit amounts that comprise balanced entries for invoices and vouchers.
Journal Entry, Reports, & Inquiries (G0911), General Journal by Batch Journal Entry, Reports, & Inquiries (G0911), General Journal by Account Accounting Reports & Inquiries (G0912), Transaction Journal
Prints account balances by business Accounting Reports & Inquiries unit. Use this report to analyze account (G0912), Trial Balance Report balances by business unit and to obtain business unit totals. This report includes a processing option for level-of-detail summarization. Prints account balances across all business units. Use this report to review similar object accounts, such as all cash accounts, and to obtain account totals for each group of accounts. Prints transactions by object account within a specific business unit. Accounting Reports & Inquiries (G0912), Trial Balance By Object Report.
Prints transactions across all or several Accounting Reports & Inquiries business units. (G0912), G/L by Object Account This report lists transactions by account. Use this report to review specific accounts across all or several business units, and to obtain account totals for each group.
499
Appendix G
Description Prints transaction totals by subledger. This report includes the same information that you can view online with the T/B by Subledger program. Prints the account balances and posted transactions for each object account of a specified company over the period selected.
Navigation Accounting Reports & Inquiries (G0912), G/L with Subledger Totals
Prints the account balances and posted Accounting Reports & Inquiries transactions for every object account (G0912), Transactions by Subsidiary and subsidiary over the period that you select. Prints the balance for each customer and supplier by object account. Prints account balances for accounts assigned to category codes 2143. Prints a trial balance that includes the account balances for accounts assigned to category codes 2143. Use this report to obtain debit and credit totals, and to supplement your chart of accounts reporting for multinational companies and for statutory accounting. Prints the total debit and credit amounts for each account in any given ledger. Current balances for income statement accounts do not include the prior-year balance. To calculate an inception-to-date total for income statement accounts, add the year-end balances for all prior years to the current balance. Accounting Reports & Inquiries (G0912), Account Totals by Supplier/Customer Accounting Reports & Inquiries (G0912), G/L by Category Code Accounting Reports & Inquiries (G0912), Debit/Credit T/B by Category Code
R09451 Account Totals by Supplier/Customer R09470 G/L by Category Code R09472 Debit/Credit T/B by Category Code
500
Appendix G
Description Prints the cash basis entries for a specified time period. This program produces an exception report that shows the accounts that are out of balance. Only cash accounts can be expected to balance between the two ledgers (AA and AZ).
Prints information about the cash basis Cash Basis Accounting (G09314), entries at the transaction level. This Cash Basis Audit Report report is a powerful research tool that allows you to quickly determine which documents are balanced, as well as which documents are posted. Cash basis entries that do not balance are identified by the message Document Not Balanced.
Generic Text
Generic Text Option Specify whether to print generic text on the report. Values are: Blank: Print the text. 1: Do not print the text.
SDB Code
Supplemental Database Code Enter the supplemental database code in which to print records. If you leave this processing option blank, the system prints records for BU (business unit).
501
Appendix G
R09205P - Account Master Report Cat. Code 0123 R09206 - Account Master Report Cat. Code 2433 R09207 - Account Master Report Cat. Code 3443
Processing Options for the Account Master Reports (R09205P, R09206, R09207)
The processing options are the same for Account Master Report Cat. Code 01-23 (R09205P), Account Master Report Cat. Code 24-33 (R09206), and Account Master Report Cat. Code 34-43 (R09207).
Print
These processing options specify how information prints on the report. 1. Unstructured Account Number Specify whether the system prints the 3rd account number (data item ANS) on the report. Values are: Blank: Do not print the 3rd account number (unstructured account number). 1: Print the 3rd account number. 2. Business Unit Description Specify whether the system prints the description of the business unit associated with the accounts when the system changes from printing the accounts for one business unit to printing the accounts for another business unit. Values are: Blank: Do not print the business unit description. 1: Print the business unit description.
R09301 - Unposted General Journal, General Journal by Batch, Unposted Cash Basis
The Unposted General Journal, General Journal by Batch, and Unposted Cash Basis reports print a general journal report to analyze journal entry transactions before you post them to the general ledger. You can print both posted and unposted transactions by batch. The totals printed on this report are by document number and document type within each batch.
Data Selection and Sequence for the Unposted Cash Basis Report
You can enter additional data selection, but you should not change the data sequence. The report calculates totals, and changing the data sequence produces unpredictable totaling results.
502
Appendix G
Processing Options for Unposted General Journal and Unposted Cash Basis Report (R09301)
Processing options enable you to specify the default processing for reports.
Account Mode
Account Specify the format in which to print accounts. Values are: 1: Account number 2: Short account ID 3: Unstructured account 4: Number entered
Units
Units Specify whether to print units. Values are: Blank: Do not print units. 1: Print units.
503
Appendix G
Display
1. Date From and 2. Date Thru Specify a beginning and an ending general ledger date in a range of dates for the system to use when selecting records from the F0911 to print on the report.
Print
1. GLR3 Reference Number Specify whether the system prints the Reference 3 (GLR3) field on the report. The GLR3 field contains either the reconciliation number that is assigned during the manual bank reconciliation process or the bank statement number that is assigned during the bank statement process. Values are: Blank: Do not print the GLR3 field on the report. 1: Print the GLR3 field on the report. 2. Category Code 21-23 Specify which alternate chart of accounts to use to print account numbers. Values are: Blank: Print the BU.Object.Subsidiary account format. 21: Print the alternate chart of accounts using Category Code 21. 22: Print the alternate chart of accounts using Category Code 22. 23: Print the alternate chart of accounts using Category Code 23.
Period
Fiscal Year and Period Number Specify the last two digits of the fiscal year and the period for which the trial balance will be printed. For example, enter 07 for 2007. If you complete one of these processing options, you must also complete the other. If you leave these processing options blank, the program uses the fiscal year and current period defined for the JD Edwards EnterpriseOne General Accounting system on the Company Setup form and recorded in the F0010 table.
Print
1. Account Number Format Specify the format for printed account numbers. Values are: Blank: Standard account number.
504
Appendix G
1: Standard account number. The default is business unit.object.subsidiary. 2: Short account ID. The system assigns this number. 3: Third G/L number. You assign this number during account setup. 2. Accounts with Zero Balances Specify whether the system includes or omits accounts with zero balances for the specified period. Values are: Blank: Include accounts with zero balances. 1: Omit accounts with zero balances. Note. Accounts that are assigned a posting edit code N print even if you set this processing option to 1. Accounts that are assigned a posting edit code N are header accounts, which do not have balances. 3. Page Breaks Enter 1 to skip to a new page when the business unit number changes. Leave this processing option blank if you do not want page breaks.
LOD
For rollup from one level of detail to the next to occur accurately, you cannot skip levels of detail when you set up the chart of accounts. Skipping a level of detail produces unpredictable results. 1. Lowest Level of Detail Specify the lowest level of detail to print on the report. You can enter a value between 3 and 9. For example, if you specify level 7 as the lowest level and the chart of accounts includes levels 8 and 9, level 7 will include the totals for accounts with level 8 and 9 amounts, but the system will not print the detail for levels 8 and 9. If you leave this processing option blank, the system prints all levels of detail on the report.
Ledger
1. Ledger Type Specify the type of ledger that the report uses. The value that you specify must exist in UDC table 09/LT. If you leave this processing option, the system prints amounts for the AA (actual amounts) ledger type. Note. If you specify the CA (foreign currency) ledger type, and the CA ledger type includes amounts for multiple currencies, the totals will be meaningless.
Subledger
1. Subledger Specify whether to print amounts for accounts with subledgers. Values are: Enter a specific subledger number. If you enter a value in this processing option, you must also enter a value in the Subledger Type processing option. Enter * to include all subledgers Leave this processing option blank to include only accounts without subledgers. 2. Subledger Type Specify a code in UDC table 00/ ST that specifies the table containing the subledger numbers. For example, subledger type A for address book subledgers identifies the F0101 table.
505
Appendix G
If you enter a value in this processing option, you must also enter a value for the Subledger processing option.
Currency
This processing option applies only if you post account balances by currency. 1. Currency Code Specify the currency that the system includes in the report to limit the report to amounts for a specific currency code. The code that you enter must exist in the F0013 table. To include amounts for all currencies, enter * . Leave this processing option blank if you do not post balances by currency. Note. If you specify ledger type CA in the Ledger Type processing option, and the CA ledger type includes amounts for multiple currencies, the totals will be meaningless unless you enter a specific currency code for this processing option.
Select
1. Fiscal Year and 2. Period Specify the fiscal year and fiscal period for the system to use when printing the report. If you leave these processing options blank, the system uses the reporting year specified in the Company Names & Numbers program (P0010). Specify the ledger type for the system to use when printing the report. Enter a valid ledger type from the Ledger Type Master Setup program (P0025). If you leave this processing option blank, the system uses ledger type AA. Specify a subledger for the system to use when printing the report. Enter * for all subledgers. Specify a subledger type for the system to use when printing the report. If you entered a subledger in the Subledger processing option, you must enter a value in this processing option. Specify whether the system includes non-posting accounts from the F0902 table on the report. Values are: Blank: Do not include non-posting accounts. 1: Include non-posting accounts. If you changed an account from posting to non-posting and the account still has a balance, the balance is included on the report.
3. Ledger Type
Print
1. Zero Balances Specify whether the system prints accounts with zero balances. Values are:
506
Appendix G
Blank: The system prints accounts with zero balances. 1: The system does not print accounts with zero balances. 2. Account Number Format Specify the format in which the system prints the account number. Values are: 1: Print the account number in business unit.object.subsidiary format. 2: Print the short account ID. 3: Print the third (unstructured) account number.
Currency
1. Currency Code Specify the currency code that the system uses to select records for processing. Enter * to include all currency codes.
Summarize
1. Beginning Range Object Account Summarization and 2. Ending Range Object Account Summarization Enter the beginning object and ending object account in a range of accounts for the system to use when selecting records for this report. In a summarized report, detailed transactions appear as a single, summarized balance for each account in the range that you specify. If you leave these processing options blank, the program prints a detailed report for all accounts in the chart of accounts.
Select
1. From Period Specify the balances that the system includes in the report. Values are: 0: Use the first period of the current fiscal year as the beginning period. This is the default. The report prints all current year transactions for all accounts plus debit and credit totals by period for the current fiscal year. The balance forward totals for balance sheet accounts are from inception through the end of the previous fiscal year. 1: Use the current period as the beginning period. The report prints a balance forward total of the previous activity for the current fiscal year and transactions for the current period only for each account. The report does not print all account activity for the year. The balance forward total reflects the year-to-date amounts through the end of the previous period for profit-and-loss accounts. For balance sheet accounts, the report reflects the inception-to-date amounts through the end of the previous period.
507
Appendix G
2: Use the first period of the first fiscal year (when you first used the JD Edwards EnterpriseOne General Accounting system) as the beginning period. The report prints transaction information from the date when you began processing for General Accounting through the current period. This report can be lengthy, depending on the amount of data that you have. 2. From Date Specify a beginning date in a range of dates for the system to use when selecting records to print on this report. If you leave this processing option blank, the system uses the value specified in the From Period processing option. Specify the ending fiscal year in a range of years that the system uses to select records for this report. Enter the last two digits of the fiscal year. For example, enter 07 for the year 2007. If you enter 0 (for year-to-date balances) for the From Period processing option and you enter a year for this processing option, the year must be the same as the year specified in the Beginning of Fiscal Year field in the Company Names & Numbers program (P0010). Otherwise, the report does not include a line item for balance forward amounts. 4. Period Number 5. Thru Date Specify a period number for the system to use when selecting records for this report. Specify an ending date in a range of dates for the system to use when selecting records to print on this report. If you leave this processing option blank, the system uses the value specified in the From Period processing option. Specify a subledger that the system uses to select records for this report. Enter the subledger or one of these values: Blank: Process records without subledgers. *: Process records for all subledgers, including blank subledgers. 7. Subledger Type Specify a subledger type for the system to use when selecting records for this report. Enter a valid subledger type from UDC table 00/ST. If you specify a value in the Subledger processing option, you must enter a subledger type for this processing option. Specify the ledger type that the system uses to select records for this report. Enter a code from UDC table 09/LT. If you leave this processing option blank, the system uses ledger type AA. Use this processing option in conjunction with the Ledger Type processing option to specify a document type that the system uses to select records for this report. Enter a document type code from UDC table 00/DT. If you leave this processing option blank, the system selects all document types. If you do not specify a ledger type for the Ledger Type processing option, the system ignores the value in this processing option.
6. Subledger
8. Ledger Type
9. Document Type
Print
1. Account Number Format Specify the format in which the system prints the account number. Values are: 1: Print the account number in business unit.object.subsidiary format. 2: Print the short account ID.
508
Appendix G
3: Print the third (unstructured) account number 2. Units Specify whether the system prints amounts only or amounts and units. Values are: Blank: Print amounts only. 1: Print units. 3. Accounts with zero balance Specify whether the system prints accounts with zero balances. Values are: Blank: Print accounts with zero balances. 1: Print accounts with zero balances. 4. Posted Transactions Specify whether the system prints both posted and unposted transactions on the report. Values are: Blank: Print posted transactions only. 1: Print both posted and unposted transactions
Summarize
Beginning and Ending Enter the beginning object and ending object account in a range of accounts for the system to use when selecting records for this report. In a summarized report, detailed transactions appear as a single, summarized balance for each account in the range that you specify. If you leave these processing options blank, the program prints a detailed report for all accounts in the chart of accounts. You cannot enter * to summarize all object accounts. Instead, enter the first and last object accounts from your chart of accounts in these processing options, respectively.
Currency
1. Currency Code 2. Currency Code From Specify the currency code that the system uses to process this report. Enter a specific currency code or * for all currency codes. Specify a currency code for as if reporting. This processing option allows amounts to print in a currency other than the currency in which they are originally entered. Enter a valid currency F0013 table. If you leave this processing option blank, the system prints amounts in the currency in which they were originally entered. Specify the as of date that the system uses when processing the current exchange rate for the as if currency. If you leave this processing option blank, the system uses the value specified in the Thru Date processing option.
3. As-of-date
509
Appendix G
Display
1. Report Content Specify the balances that the system includes in the report. Values are: 0: Use specify the first period of the current fiscal year as the beginning period. This is the default. The report prints current year transactions for all accounts plus debit and credit totals by period for the current fiscal year. The balance forward totals for balance sheet accounts are from inception through the end of the previous fiscal year. 1: Use the current period as the beginning period. The report prints a balance forward total of the previous activity for the current fiscal year and transactions for the current period only for each account. The report does not print all account activity for the year. The balance forward total reflects the year-to-date amounts through the end of the previous period for profit-and-loss accounts. For balance sheet accounts, the report reflects the inception-to-date amounts through the end of the previous period. 2: Use the first period of the first fiscal year (when you began JD Edwards EnterpriseOne General Accounting processing) as the beginning period. The report prints transaction information from the date when you began JD Edwards EnterpriseOne General Accounting processing through the current period. This report can be lengthy, depending on the amount of data that you have. 2. Fiscal Year Enter the fiscal year in which the system processes the report. If you enter 0 for the Report Content processing option (for year-to-date balances) and you enter a year in this processing option, the year that you specify must be the same as the year that is specified in the Beginning of Fiscal Year field in the Company Names & Numbers program (P0010). Otherwise, the report does not include a line item amount for the balance forward. 3. Period 4. Ledger Type Enter the period in which the system processes the report. If you leave this processing option blank, the system uses the financial reporting period. Specify the ledger type that the system uses to select records for this report. Enter a l code from UDC table 09/LT. If you leave this processing option blank, the system uses ledger type AA. Use this processing option in conjunction with the Ledger Type processing option to specify a document type that the system uses to select records for this report. Enter a code from UDC table 00/DT. If you leave this processing option blank, the system selects records for all document types. If you do not enter a value for the Ledger Type processing option, the system ignores the value entered for this processing option. 6. Transaction Status Specify whether the system prints both posted and unposted transactions. Values are: Blank: Print only posted transactions. 1: Print both posted and unposted transactions.
5. Document Type
510
Appendix G
Print
1. Account Number Format Specify the format in which the system prints account numbers. Values are: Blank or 1: Standard account number (business unit.object.subsidiary). 2: Short account ID. 3: Third general ledger number. 2. Print Units Specify whether the system prints amounts only or amounts and units. Values are: Blank: Print amounts only. 1: Print amounts and units. 3. Zero Balances Specify whether the system prints accounts with zero balances. Values are: Blank: Print accounts with zero balances. 1: Omit accounts with zero balances.
Summarization
1. Business Unit Type Specify a business unit type for subledger summarization. Enter a specific business unit type or one of these values: +: Include all types *: Include all non-blank types. 2. Subledger Summarization Beginning Object and 3. Subledger Summarization Ending Object Specify the beginning and ending object accounts in a range of object accounts for subledger summarization.
Currency
1. Currency Code Specify a currency code to use when printing the report. Enter a valid currency code from the F0013 table or * for all currency codes.
511
Appendix G
Column Total: Sum of the Total Transactions plus the Prior Period Transaction Total. Prior Year End Balance: Balance of the object account from the previous year. Prior Period End Balance. Sum of all prior period transactions and the prior year end balance. Ending Balance: Sum of the Prior Year End Balance and the Column Total balance. Note. If you use the CA ledger type, the subtotals and totals might be meaningless because of mixed currencies. If so, the totals will indicate N/A.
Processing Options for Transactions by Object (R09423) and Transactions by Subsidiary (R09424)
Processing options enable you to specify the default processing for reports.
Period
1. Period From and 2. Period To Specify the first and last periods from which the system retrieves transactions for the report. If you leave the Period From processing option blank, the system uses the current period of the company that is specified in the data selection. If you leave the Period To processing option blank, the system uses the period specified in the Period From field. 3. Fiscal Year Enter the last two digits of the fiscal year for which you want the report to print. For example, enter 07 to print the report for the year 2007.
Ledger
1. Ledger Type Specify the ledger type for the report. If you leave this processing option blank, the system uses ledger type AA. Note. If you enter CA for the ledger type, subtotals and totals may be meaningless.
Print
1. Suppress Zero Amounts Specify whether to suppress printing transactions with zero amounts. Values are: Blank: Print transactions with zero amounts. 1: Do not print transactions with zero amounts. 2. Suppress Print Total Specify whether to suppress printing period totals. Values are: Blank: Print period totals. 1: Do not print period totals.
512
Appendix G
Report Detail
1. From Period or From Date 2. Thru Fiscal Year and Period or Thru Date Enter either the period or from date in which to begin the report. Enter the two-digit fiscal year and the period or thru date in which to end the report.
513
Appendix G
Document
1. Document 2. Document Type 3. Unposted Transactions Enter a specific ledger type. If you leave this processing blank, the system uses ledger type AA. Enter a specific document type. If you leave this processing option blank, the system uses all document types. Specify whether to print posted or both posted and unposted transactions. Values are: Blank: Print posted transactions only. 1: Print posted and unposted transactions.
Currency
1. As if Currency 2. As of Date Enter the currency code in which to print as if currency amounts. If you leave this processing option blank, the system uses the company currency. Enter the date in which to retrieve the exchange rate for the as if currency. If you leave this processing option blank, the system uses the date in the Thru Date processing option.
Select
1. From Period Specify the beginning fiscal period for the system to use when selecting account balances for this report. Values are: 0: Year to date. Use the first period of the current fiscal year as the beginning period. The report prints all current year transactions for all accounts plus debit and credit totals by period for the current fiscal year. The balance forward totals for balance sheet accounts are from inception through the end of the previous fiscal year. 1: Current period. Use the current period as the beginning period. The report prints a balance forward total for the current fiscal year and transactions for the current period for each account. It does not print all account activity for the year. The balance forward total reflects the year-to-date amounts through the end of the previous period for profit-and-loss accounts. For balance sheet accounts, the report reflects the inception-to-date amounts through the end of the previous period.
514
Appendix G
2: Inception to date. Use the first period of the first fiscal year in which you began using the JD Edwards EnterpriseOne General Accounting system as the beginning period. The report prints transaction information from the date when you began using the JD Edwards EnterpriseOne General Accounting system through the current period. This report can be lengthy, depending on the amount of data that you have. 2. From Date Specify a beginning date in a range of general ledger dates for the system to use when selecting records to print on this report. If you leave this processing option blank, the system uses the value specified in the From Period processing option. Specify a thru fiscal year for the system to use when selecting records for this report. Enter the last two digits of the fiscal year, for example, 07 for 2007. Specify a period for the system to use when selecting records for this report. Specify an ending date in a range of general ledger dates for the system to use when selecting records for this report. If you leave this processing option blank, the system uses the value specified in the From Period processing option.
Print
1. Ledger Type Specify the ledger type for the system to use when selecting records to print on this report. Enter a valid ledger type from the F0025 table. If you leave this processing option blank, the system uses ledger type AA. Use this processing option in conjunction with the Ledger Type processing option to specify the document type that the system uses to select records for this report. Enter a document type code from UDC table 00/DT. If you leave this processing option blank, the system selects all document types. Note. If you do not enter a value in the Ledger Type processing option, the system ignores the value for this processing option. 3. Transaction Type Specify whether the system prints only posted transactions. Values are: Blank: Print only posted transactions. 1: Print both posted and unposted transactions. 4. Account Category Code (123) Specify the account category code (123) that the system prints on the report. If you leave this processing option blank, the system prints category code 21. The value you enter in this field is used only to print the category codes on the report. It is not used for data selection. 5. Units Specify whether the system prints units as well as amounts. Values are: Blank: Print amounts only. 1: Print both amounts and units. 6. Zero Balances Specify whether the system prints accounts with zero balances. Values are: Blank: Print accounts with zero balances. 1: Do not print accounts with zero balances.
2. Document Type
515
Appendix G
7. Date Order
Specify whether the system prints information in ascending or descending order by date. Values are: Blank: Print information in descending order by date. 1: Print information in ascending order by date.
Currency
1. As-If Currency Code Specify an as if currency code in which to print amounts for this report. This processing option allows you to review amounts in a currency other than the currency in which they are stored. Only amounts associated with the AA ledger type are converted to the as if currency. If you leave this processing option blank, amounts do not print in an as if currency. Specify the date on which to retrieve the exchange rate for the as if currency from the F0015 table. If you enter a value for the As If Currency Code processing option and leave this processing option blank, the system uses the date specified in the Thru Date processing option for the exchange rate.
Select
1. Fiscal Year Specify the fiscal year for the system to use when selecting records to print on this report. If you leave this processing option blank, the system uses the current fiscal year. Specify the period number for the system to use when selecting records to print on this report. If you leave this processing option blank, the system uses the current period number. Specify the ledger type for the system to use when selecting records to print on this report. Enter a valid ledger type from the F0025 table. If you leave this processing option blank, the system uses ledger type AA. Use this processing option to specify the account category code (2123) that the system prints on the report. If you leave this processing option blank, the system prints category code 21. The value you enter for this processing option is used only to print the category codes on the report. It is not used for data selection.
2. Period
3. Ledger Type
516
Appendix G
Data Selection and Sequence for the Cash Basis Integrity Report
Enter the prior fiscal years that you want to view. You must specify ledger type AA. The integrity test and report run more efficiently when you sequence by company.
Select
1. As Of Date Specify the as of date in which to run the integrity test. If you leave this processing option blank, the system uses the current date.
Process
1. Transaction Detail Specify whether to print transaction detail. Values are: Blank: Print summarized information. 1: Print transaction details.
517
Appendix G
Data Selection and Data Sequencing for the Cash Basis Audit Report
Do not change the data selection for Ledger Type equal to AZ (cash basis). You can enter additional data selection to select posted records, a specific batch, or general ledger dates. Do not change the data sequencing. The report calculates totals, and changing the data sequencing produces unpredictable totaling results.
Display
1. Account Number Specify which account number format to print on the report. Values are: Blank: Number specified during data entry 1: Long account number 2: Short account number 3: Unstructured account number
518
519
Glossary
and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability. business function event rule business view See named event rule (NER). A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data. A process that blends a customers modifications to the objects in a current release with objects in a new release. A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machinethe central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server. Tables of information in JD Edwards EnterpriseOne that appear on forms in the software. Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors. A general ledger account in JD Edwards EnterpriseOne Financial Management that is used by the system to offset (balance) journal entries. For example, you can use a contra/clearing account to balance the entries created by allocations in JD Edwards EnterpriseOne Financial Management. An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables. A process that blends a customers modifications to the control tables with the data that accompanies a new release. The process in JD Edwards EnterpriseOne Advanced Cost Accounting of tracing or allocating resources to activities or cost objects. In JD Edwards EnterpriseOne Manufacturing, an element of an items cost (for example, material, labor, or overhead). A logic statement that establishes the relationship between configured item segments. Cross segment edits are used to prevent ordering of configurations that cannot be produced. The process of converting amounts from one currency into another currency, generally for reporting purposes. You can use the currency restatement process, for example, when many currencies must be restated into a single currency for consolidated reporting. A server in a local area network that maintains a database and performs searches for client computers. An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion.
charts connector
contra/clearing account
control tables merge cost assignment cost component cross segment edit
currency restatement
520
Glossary
date pattern denominated-in currency deployment server detail information direct connect
A calendar that represents the beginning date for the fiscal year and the ending date for each period in that year in standard and 52-period accounting. The company currency in which financial reports are based. A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations. Information that relates to individual lines in JD Edwards EnterpriseOne transactions (for example, voucher pay items and sales order detail lines). A transaction method in which a client application communicates interactively and directly with a server application. See also batch-of-one immediate and store-and-forward.
A type of data source that must exist on the iSeries because of BLOB restrictions. The process of providing prices for goods and services in two currencies. A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information. A condition of a form that enables users to change data. A method used for formatting and validating user entries against a predefined rule or set of rules. An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems. An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule. A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages. A server that contains the database and the logic for JD Edwards EnterpriseOne. A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects. A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes dont have to wait if the server is particularly busy. An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion. A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time.
EnterpriseOne process
Environment Workbench
escalation monitor
521
Glossary
event rule
A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field. An entity within a business for which you want to track costs. For example, a facility might be a warehouse location, job, project, work center, or branch/plant. A facility is sometimes referred to as a business unit. A command prompt that enables the user to move quickly among menus and applications by using specific commands. A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files. The report processing mode of a processing mode of a program that updates or creates data records. A server that responds to requests for files via file transfer protocol. Information at the beginning of a table or form. Header information is used to identify or provide control information for the group of records that follows. See Z table. A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems. A process used to supplement a companys internal balancing procedures by locating and reporting balancing problems and data inconsistencies. A method for third-party systems to connect to or access JD Edwards EnterpriseOne. In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form. This internet server service resides on the web server and is used to speed up delivery of the Java class files from the database to the client. An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of the current object. A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence. A database driver that enables heterogeneous servers to access each others data. A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access. An API used by business functions to invoke other business functions. A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers. Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes.
facility
final mode FTP server header information interface table integration server integrity test interoperability model in-your-face-error IServer service jargon Java application server
JDEIPC
522
Glossary
jde.log
The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne. A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms. An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source. A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs. An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment.
JDENET
Location Workbench
logic server
MailMerge Workbench
master business function (MBF) An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases. master table matching document See published table. A document associated with an original document to complete or change a transaction. For example, in JD Edwards EnterpriseOne Financial Management, a receipt is the matching document of an invoice, and a payment is the matching document of a voucher. Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx. A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues. A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions. Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work. In Brazil, a legal document that must accompany all commercial transactions for tax purposes and that must contain information required by tax regulations. In Brazil, a nota fiscal with invoice information. See also nota fiscal.
523
Glossary
In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user. A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-in capabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another. A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release. An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation. An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing. JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server. A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build. Consider the following context: Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions. The process of creating a package build is often referred to, as it is in this example, simply as a package build.
Object Librarian
Object Librarian merge Open Data Access (ODA) Output Stream Access (OSA)
package
package build
package location
The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored. An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion. A means of grouping end items whose similarity of design and manufacture facilitates being planned in aggregate. The ability to define default values for specified fields for a user-defined hierarchy of items, item groups, customers, and customer groups. The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself. A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify.
Package Workbench
pristine environment
524
Glossary
processing option
A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on. A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software. A file server that has been quality assurance tested and commercialized and that is usually provided in conjunction with user support services. A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks. In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench. The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path): 11>21>26>28>38>01 In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.
production environment production-grade file server program temporary fix (PTF) project promotion path
A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service. Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise. The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise. One of the JD Edwards EnterpriseOne methods for replicating data to individual workstations. Such machines are set up as pull subscribers using JD Edwards EnterpriseOne data replication tools. The only time that pull subscribers are notified of changes, updates, and deletions is when they request such information. The request is in the form of a message that is sent, usually at startup, from the pull subscriber to the server machine that stores the F98DRPCN table. An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data. A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and to provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when certain transactions occur. A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level, such as B73.2 or B73.2.1. A server that is responsible for replicating central objects to client machines. In JD Edwards Procurement and Subcontract Management, a request from a supplier for item and price information from which you can create a purchase order.
refresh
525
Glossary
In JD Edwards Sales Order Management, item and price information for a customer who has not yet committed to a sales order. selection Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter. An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number data source. It also updates the Server Plan detail record to reflect completion. An exchange rate entered at the transaction level. This rate overrides the exchange rate that is set up between two currencies. A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release. A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is used to build applications. An application that, during the Installation Workbench process, runs the batch applications that update the specification tables. The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions. Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table. Any type of information that is not maintained in a master file. Supplemental data is usually additional information about employees, applicants, requisitions, and jobs (such as an employees job skills, degrees, or foreign languages spoken). You can track virtually any type of information that your organization needs. For example, in addition to the data in the standard master tables (the Address Book Master, Customer Master, and Supplier Master tables), you can maintain other kinds of data in separate, generic databases. These generic databases enable a standard approach to entering and maintaining supplemental data across JD Edwards EnterpriseOne systems. table access management (TAM) The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions. An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables. An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables. Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level. A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer.
Server Workbench
specification Specification Table Merge Workbench store-and-forward subscriber table supplemental data
table conversion
terminal server
526
Glossary
The task of entering, reviewing and approving, and posting batches of transactions in JD Edwards EnterpriseOne. In JD Edwards Procurement and Subcontract Management, the process of comparing receipt information to suppliers invoices to create vouchers. In a three-way match, you use the receipt records to create vouchers. A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens. An electronic business transaction (electronic data interchange standard document) made up of segments. One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system processes automatically when the event occurs. A specific workflow event that requires special action or has defined consequences or resulting actions. In JD Edwards Procurement and Subcontract Management, the process of comparing purchase order detail lines to the suppliers invoices to create vouchers. You do not record receipt information. Adds new user override records into a customers user override table. In JD Edwards Capital Asset Management, the difference between revenue generated by a piece of equipment and costs incurred by the equipment. In JD Edwards EnterpriseOne Project Costing and JD Edwards EnterpriseOne Manufacturing, the difference between two methods of costing the same item (for example, the difference between the frozen standard cost and the current cost is an engineering variance). Frozen standard costs come from the Cost Components table, and the current costs are calculated using the current bill of material, routing, and overhead rates.
The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data. Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control. An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report. An internal type of a wide character. It is used for writing portable programs for international markets. A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions. A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet. A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows
visual assist vocabulary override wchar_t web application server web server
527
Glossary
terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device. workbench A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditors Workbench (P09E115), and Payroll Cycle Workbench. In JD Edwards EnterpriseOne Manufacturing, a calendar that is used in planning functions that consecutively lists only working days so that component and work order scheduling can be done based on the actual number of work days available. A work day calendar is sometimes referred to as planning calendar, manufacturing calendar, or shop floor calendar. The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules. A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing. A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response. An interoperability capability that enables you to call business functions. An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses. An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks. An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system. An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality. Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format. A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur. A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as interface tables. Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.
workflow
XML Transaction
Z table
Z transaction
528
Index
Numerics/Symbols
52 period accounting annual close 272 assigning reporting dates to a company 81 changing to 81 fiscal date patterns 79 generating income statements 274 multithreaded job queues 271 overview 271 posting entries 271 repost 81 setting up reporting dates 80 52 period Accounting Post (R098011) 271 52 Period Accounting Post (R098011) processing options 272 52 Period Income Statement (R10252) 274 processing options 274 processing options 351 Account Inquiry by Object Account (P09201) processing options 351 Account Ledger Inquiry (P09200) processing options 349 Account Structure (R10445) 309 Account Structure Build (R10430) 306 processing options 307 Account Structure Definition (P10430A) 305 Account Structure Inquiry/Revision (P10440) 309 Account Structure Report (R10445) processing options 310 account structures revisions 414 Account Totals by Supplier/Customer (R09451) 513 processing options 513 accounting period closing 427, 428, 429, 431 accounts balancing 389 changing 421 global updates 422 Accounts w/o Business Units (R097041) processing options 394 Accounts without Business Units (R097041) 394 additional documentation xxxiv allocations indexed allocations 127, 129, 132 indexed allocations example 128 multitiered 121 overview 119 process 120 recurring journal entries 123, 124, 126 types of 119 variable numerator 133, 135, 137 variable numerator example 134 Annual Close (R098201) 436 processing options 437 Annual Close for 52 Period (R09820B) 272
A
AAIs account reconciliation 33 account summarization 29 cash basis accounting 77 financial statement totals 27 general purpose 24 overview 24 prior year account purges 30 reconcilable ranges 29 retained earnings 26 speed codes 29 Account Balance by Month (P0902P1) 354 processing options 354 Account Balance by Subledger (P092131) 354 Account Balance to Transactions (R09705) 393 processing options 391 Account Balance without Account Master (R097031) processing options 395 Account Inquiry by Category Code (P09202) 348
529
Index
application fundamentals xxxiii Apply Forecast to Budget (R1407) 249 processing options 250 attachments adding to journal entries 91 automatic accounting instructions balance sheet 362 automatic bank statement assigning groups to bank statement accounts 50 assigning reconciliation rules 49 automatic bank statements 35 BAI2 conversion flow 181 bank account cross references 42 bank account reconciliation 45 conversion flows 181 loading data into bank statement tables 185 mapping fields for conversion flows 469 overview 179 process 180 processing 190 purging tables 199 reconciliation groups 45 reconciliation rules 45, 46 reconciling unreconciled transactions 194, 195 reports 192 revising data 186, 188 revising staging data 183 revising transactions without customer numbers 189 running a bank statement conversion flow 181 setting an integration option for the date pattern 36 setting integration options for conversion flows 35 setting up cross references 42 staging tables 182 SWIFT conversion flow 181 UDCs 36 unreconciled messages 192
B
balance sheets 361 generating 362 generating consolidated balance sheets 368
net income calculation 361 bank account reconciliation changing reconciled transactions to unreconciled 145 reconciling accounts manually 142 reconciling transactions manually 143 reconciling voided payments 139 reconciling voided receipts 139 refreshing the reconciliation workfile 140, 141 report 142 bank accounts 139 See Also bank account reconciliation setting up cross references 42 Bank Journal Statement Process (R09170) processing options 170 Bank Journal Statement Process Program (R09170) 168 Bank Statement Entry (P09160) processing options 161 bank statements, See automatic bank statements, manual bank statements bank tape reconciliation overview 151 reconciling cleared transactions 154 reformatting bank tapes 153 refreshing account reconciliation information 154 reports 155 verifying 155 Batch Header Revisions (P0011) 399 batch headers adding records 402 missing 379 no posted detail 379 post out of balance 403 reviewing records 401 revising records 399, 402 Batch Out of Balance report (R09706) 384 batch processing errors 108 ignored fields 465 mapping fields for externally reconciled transactions 466 mapping fields for journal entries 453 optional fields 457 posting processed batch journal entries 112 processing batch journal entries 107
530
Index
purging processed records 112 required fields 453 required fields for Advanced Cost Accounting 457 running the batch processor 109 uploading journal entries 108 working with batch journal entries 110 Batch to Detail (R007031) 400 processing options 380 Batches Out of Balance (R007032) 382 processing options 383 BU/Accounts Monthly Comparison Report (R10701) processing options 320 budget forecasting and planning account definition 241 basis amounts 241 defining accounts and retrieving basis amounts manually 241 generating accounts and basis amounts automatically 241, 243 generating forecast amounts 245, 246 process 240 purging forecasts 250 revising accounts and basis amounts 243, 244 revising budget forecasts 247, 248 updating forecast records 249 updating forecasts 250 Budget Import Field Mapping (R14110M) 230, 231 processing options 232 Budget Worksheet (R14113) 215 processing options 217 budgets 239 See Also budget forecasting and planning amounts and encumbrances 222 annual budgets 207 budget checking calculation 222 budget patterns 202 changing budget pattern codes 205 comparing budgets online 220 creating budget pattern codes 204 cycles 207 detailed budgets by account 224 entering annual amounts by account 212 entering annual amounts by business unit 210 entering budget journal entries 226
entering detailed budget amounts by account 224 entering journalized budgets 226 guidelines for spreadsheets 228 importing data from a spreadsheet 228, 229 journalized 202 journalized budgets 225 managing budget overages 221 methods 201 overview 201 purging processed records 237 reviewing budget comparisons online 220 reviewing budgets online 218 revising imported data 232, 233 spreading annual amounts 215 spreading annual budgets 213 uploading imported data 234 uploading imported data to the F0902 table 234 using variable numerator allocations 133 worksheets 215, 216 Business Unit Structure Build (R10450) processing options 281 business units changing company numbers 419 deleting 446 global revisions 418 revisions to multiple accounts 415, 416 supplemental data 30
C
Calculate Fiscal Year and Period (R099103) processing options 410 calendar date pattern changing 409 recalculating 409 cash basis accounting AAIs 77 accrual entries 261 assigning document types to the AA ledger 77 cash basis entries 262 document types 75 entries for AP 263 entries for AR 263 entries for GL 262 entries for units 262
531
Index
errors on exception reports 268 exception reports 268 multithreaded job queues 266 overview 75, 261 posting entries 269 reviewing cash basis entries 269 setting up AAIs for balancing accounts 78 setting up AAIs for unapplied receipts 77 setting up document types 76 cash flow statements cash flow activity codes 70 cash flow rules 71 example 364 generating 366 normal balance codes 71 overview 69, 363 setting up cash flow rules 72 Cash Forecast Analysis (P09522) 253, 256 processing options 257 Cash Forecast Report (R095221) 256 cash forecasting analyzing information 256, 258 cash type codes 57 cash type rules 58 defining a report structure 65 overview 57 process 253 purging data 259, 260 refreshing data 253, 255 report structures 63 setting up cash type rules 59, 62 cash type rules setting up 59, 62 category codes reports 498, 516 Change Account Information (R09813) 421 processing options 422 Change Business Units (P09812) 415 Change Subsidiaries (P09805) 417 chart of accounts revisions 413 close accounting period 427, 428, 429, 431 fiscal year 433 comments, submitting xxxviii common fields xxxviii
Companies in Balance (R097001) 386 Company by Batch Out of Balance (R09706) processing options 385 Consolidated Balance Sheet (R10150) processing options 321 Consolidated Balance Sheet (R10311A) 368 processing options 369 Consolidated Income Statement (R10250) processing options 321 Consolidated Income-7 column (R103121A) processing options 368 Consolidation Console (P10610) 322, 327 processing options 328 Consolidation Review (P09210A) 297 processing options 297 consolidation rules 310 Consolidation Specifications (P10470) 310 consolidations, See high-volume consolidations, multisite consolidations, online consolidations constants overview 14 setting up 16 contact information xxxviii Create Cash Basis Entries (R11C850) 261, 266, 267 Create Cash Basis Entries Program (R11C850) processing options 266 Create Obj/Sub Control File (R10909) 303 processing options 304 Create UDC Control File (R10005) 303 processing options 304 cross-references xxxvii Custom Reformat UBE (R09501) 153 processing options 153 Customer Connection website xxxiv
D
debit and credit reconciliation 148 process 147 reconciling transactions manually Debit/Credit Match (P09131) 147 149
532
Index
Debit/Credit T/B by Category Code (R09472) 516 Delete Account Master Records (R09814) 444, 445 processing options 445 Delete Business Unit/Company (R09925) 446 processing options 446 Delete Prior Consolidation (R10861) 293, 294 Delete Prior Consolidations (R10861) processing options 294 Detailed Budget by Account (P14101) 224 documentation printed xxxiv related xxxiv updates xxxiv
processing options 64 forecasting and planning 243 See Also budget forecasting and planning forms Ledger Type Rules Setup 21
G
G/L Budget Checking Report (R14115) 221 processing options 223 G/L by Category Code (R09470) 514 G/L by Object Account (R09421) 507 G/L with Subledger Totals (R09422) 509 general accounting delivered workflow 495 features 9 integrations 2 system setup 13 tables 449 general journal reports 497 General Journal by Account (R09311) 503 General Journal Review (P0011) processing options 98 general ledger reports 498 General Ledger Post (R09801) processing options 100 Generate Forecast Basis (R1403) 241 processing options 243 Generate Forecast Results (R1404) 245 processing options 246 government reporting 338
E
elimination rules 311 encumbrances 222 Extract A/P Cash Forecast Data (R04522) 254 Extract A/R Cash Forecast Data (R03B522) 254 Extract G/L Cash Forecast Data (R09522) 254
F
fictitious business units 295 financial reports balance sheets 361 changing reporting dates 432 See Also financial reporting dates consolidated reports 367 overview 357 fiscal date pattern changing 409 recalculating 409 fiscal period recalculating 409 fiscal year closing 433, 435, 436 closing for budgets 438 error messages on close reports 436 preparation for closing 435 recalculating 409 Forecast Report Structures Setup (P09523)
H
high-volume consolidations creating 295, 296 deleting prior consolidations 294 example 276 fictitious business units 295 overview 276, 293 reviewing 297, 299
I
implementation general accounting 4 implementation guides ordering xxxiv
533
Index
Importing budgets converting data to F0902Z1 table 230 income statements 359 generating consolidated income statements 367 Indexed Computations Compute & Print (R093021) 128 processing options 132 integration options 35 integrities 318 See Also reports error messages 384, 385, 387, 388, 390, 393, 396 out-of-balance conditions 386, 390 overview 373 reports 374, 376, 379, 382, 384, 386, 394, 395 Intercompany Accounts in Balance (R097011) 389, 390 processing options 389 invalid account numbers 87
revising unposted 93 selecting model 97 speed account entry for work orders 87 types of 85 voiding 104 voiding posted 105 voiding posted reversing 104, 105 Journal entries generating 84 Journal Entries Batch Processor (R09110Z) 108 processing options 109 Journal Entry Master Business Function (P0900049) 89 Journal Entry Revisions (P0911Z1) processing options 111 Journalize Consol. Balances (R10480) processing options 333 Journalize Consolidation Balances (R10480) 332
J
journal entries 108, 113 See Also batch processing; store-and-forward processing accepting invalid account numbers adding an attachment 91 basic 85 batch processing 107 changing posted to reversing 95 copying 94 copying models 97 creating models 96, 97 deleting unposted 94 duplicating account number segments 86 entering basic 90 entering percent 92 entering reversing 95 error messages 91 model 86, 96 overview 83 percent 85 post process 99 posting 99, 103 reversing 85, 95, 104 reviewing 98 reviewing reversing 95 revising posted 104, 105
L
ledger types setting up 20 setting up rules for 21 Load Bank Statement (R09612) processing options 186
185
87
M
Manual Bank Statement Reconciliation (P09631) 194 processing options 195 manual bank statements entering bank statement transactions 160 entering transactions 165 overview 157 processing bank statements 168 processing batch cash receipts 172 reconciliation reports 172 refreshing the reconciliation workfile 167 transaction codes 158 transit accounts 159 Manual Reconciliation (P09131) processing options 143 master business function 89 Match Tape File To Recon File (R09510) 154
534
Index
processing options 154 Monthly Spreadsheet (R10412A) 369 processing options 370 MSC Data Transmission (R10610) 324 processing options 325 multisite consolidations account structures 305 building account structures 306, 307 consolidation rules 310 consolidation statuses 322 control file reports 303 creating consolidated balances 314 defining account structures 305, 306 defining consolidation rules 311 defining elimination rules 313 defining structures 302 elimination rules 311 errors on reports 319 generating batch journal entries 333 generating multisite batch journal entries 332 ignored fields for F1001Z1 table 490 ignored fields for F1002Z1 table 492 mapping fields for inbound consolidations 487 mapping fields in the F1002Z1 table 490 mapping optional fields for F1001Z1 table 488 mapping optional fields for F1002Z1 table 491 multiple tiers 302 organization structures 304 overview 277 printing account structures 308 process 301 processing 315, 334 processing batch journal entries 335 processing inbound consolidations 330 purging 334, 335 purging inbound consolidations 331 reports 317, 318 required fields for F1001Z1 table 487 required fields for the F1002Z1 table 490 reviewing statuses 323 revising account structures 308, 309 revising inbound consolidations 330, 331
sending consolidated balances 324, 327, 328 source site 301, 302 target site 301, 302 transmission program 324, 325 uploading consolidations 329 multithreaded job queues 52 period accounting 271 cash basis accounting 266
N
notes xxxvii
O
object accounts global revisions 416, 418 Object/Subsidiary Value Control Exceptions Report (R107021) processing options 320 Online Budget Comparison (P09210A) 218 processing options 219 online consolidations adding report structures 282 building organization report structures 280 building report structures 281 consolidating business units 288 consolidating business units by category code 287 consolidating business units by report structure 287 copying report structures 283, 285 creating 286 creating additional business units 283, 284 defining report structures 280, 281 organization report structures 279 overview 275 rearranging report structures 283 reviewing 290 reviewing financial statements online 292 reviewing report structures 283 Online Consolidations (P09218) processing options 290 online inquiries Account Balance by Month (P0902P1) 339, 354
535
Index
Account Balance by Subledger (P092131) 354 Account Balances by Subledger (P092131) 339, 355 Account Inquiry by Category Code (P09202) 339, 348, 353 Account Inquiry by Object Account (P09201) 339, 348, 352 Account Ledger Inquiry (P09200) 339, 348, 351 overview 337 Statutory Account Inquiry (P09218A) 339 T/B / Ledger Comparison (P09210A) 339, 340 T/B by Company (P09216) 338, 343, 346 T/B by Object Account (P09214) 338, 345 T/B by Subledger (P09215) 338, 346 T/B Ledger Comparison (P09210A) 341 T/B/ Ledger Comparison (P09210A) 338 Trial Balance by Object Account (P09214) 343 trial balances 338 Organization Structure Definition (P0050B) 280 Organization Structure Inquiry/Revision (P0050) 283 Organization Structure Inquiry/Revisions (P0050) processing options 284
P
PC budget upload field mapping 231 mapping fields in F0902Z1 table 483 purging records 237 PeopleCode, typographical conventions xxxvi period end, See accounting period post general ledger 99 prerequisites xxxiii Print Reconciliation Report (R09132P) 142 printed documentation xxxiv Prior Period Balance Integrity (R10700)
processing options 319 Process Automatic Bank Statement (R09616) 190 Process Automatic Bank Statements (R09616) processing options 193 Process Batch Journal Entry (R09110Z) 334 Process Consolidations (R10550) 314 processing options 315 Process Inbound Consolidations Data (R1002Z1) 329 processing options 330 processing options 148, 274 52 Period Accounting Post (R098011) 272 Account Balance by Month (P0902P1) 354 Account Balance to Transactions (R09705) 391 Account Balance without Account Master (R097031) 395 Account Inquiry by Object Account (P09201) 351 Account Ledger Inquiry (P09200) 349 Account Structure Build (R10430) 307 Account Structure Report (R10445) 310 Account Totals by Supplier/Customer (R09451) 513 Accounts w/o Business Units (R097041) 394 Annual Close (R098201) 437 Apply Forecast to Budget (R1407) 250 Bank Journal Statement Process (R09170) 170 Bank Statement Entry (P09160) 161 Batch to Detail (R007031) 380 Batches Out of Balance (R007032) 383 BU/Accounts Monthly Comparison Report (R10701) 320 Budget Import Field Mapping (R14110M) 232 Budget Worksheet (R14113) 217 Business Unit Structure Build (R10450) 281 Calculate Fiscal Year and Period (R099103) 410 Cash Forecast Analysis (P09522) 257
536
Index
Cash Forecast Report Structures Setup (P09523) 64 Change Account Information (R09813) 422 Company by Batch Out of Balance (R09706) 385 Consolidated Balance Sheet (R10150) 321 Consolidated Balance Sheet (R10311A) 369 Consolidated Income Statement (R10250) 321 Consolidated Income-7 column (R103121A) 368 Consolidation Console (P10610) 328 Consolidation Review (P09210A) 297 Create Cash Basis Entries Program (R11C850) 266 Create Obj/Sub Control File (R10909) 304 Create UDC Control File (R10005) 304 Custom Reformat UBE (R09501) 153 Delete Account Master Records (R09814) 445 Delete Business Unit/Company (R09925) 446 Delete Prior Consolidations (R10861) 294 G/L Budget Checking Report (R14115) 223 General Journal Review (P0011) 98 General Ledger Post (R09801) 100 Generate Forecast Basis (R1403) 243 Generate Forecast Results (R1404) 246 Indexed Computations Compute & Print (R093021) 132 Intercompany Accounts in Balance (R097011) 389 Journal Entries Batch Processor (R09110Z) 109 Journal Entry Revisions (P0911Z1) 111 Journalize Consol. Balances (R10480) 333 Load Bank Statement (R09612) 186 Manual Bank Statement Reconciliation (P09631) 195 Manual Reconciliation (P09131) 143 Match Tape File To Recon File (R09510) 154 Monthly Spreadsheet (R10412A) 370
MSC Data Transmission (R10610) 325 Object/Subsidiary Value Control Exceptions Report (R107021) 320 Online Budget Comparison (P09210A) 219 Online Consolidations (P09218) 290 Organization Structure Inquiry/Revisions (P0050) 284 Prior Period Balance Integrity (R10700) 319 Process Automatic Bank Statements (R09616) 193 Process Consolidations (R10550) 315 Process Inbound Consolidations Data (R1002Z1) 330 Purge Automatic Bank Statement Tables (R09615) 200 Purge Cash Forecast Data (R09522B) 260 Purge Prior Year JEs (R09911) 443 Purge Staging Tables (R09610) 199 Recurring JE Compute & Print (R09302) 126 Refresh Cash Forecast Data (R00522) 255 Refresh Consolidation (R10862) 296 Refresh Reconciliation File (R09130) 141 Repost Account Ledger (R099102) 408 Requested by Account (P14103) 209 Requested by Business Unit (P14102) 209 Revise Automatic Bank Statement (P09616) 187 Simple Balance Sheet (R10111B) 362 Simple Income Statement (R10211B) 360 Spread Annual to Periods (R14801) 215 Statement of Cash Flows Report (R10521) 366 Store & Forward JE Batch Processor (R09110ZS) 117 Summarize Transactions (R09811) 441 T/B by Company (P09216) 345 T/B by Object Account (R09214) 344 T/B by Subledger (P09215) 345 Transactions by Subsidiary (R09424) 513
537
Index
Transactions to Batch Headers (R007021) 376 Transactions without Account Master (R097021) 397 Trial Balance/Ledger Comparison (P09210A) 340 UDC Value Control Exceptions (R107011) 319 Upload/Conversion (R14110) 235 Upload/Conversion Revisions (P0902Z1) 228 Variable Numerator Compute & Print (R093022) 137 Variance Analysis (R10212A) 371 Variance Analysis w/5 Months (R10411A) 372 purge prior-year account balances 444 prior-year records 442 Purge Automatic Bank Statement Tables (R09615) processing options 200 Purge Cash Forecast Data (R09522B) 259 processing options 260 Purge Prior Year Account Balances (R09912) 444 Purge Prior Year JEs (R09911) 442, 443 Purge Prior Year JEs (R09911) processing options 443 Purge Staging Tables (R09610) processing options 199
R
reconciliation, See bank account reconciliation, bank tape reconciliation, see debit and credit reconciliation reconciliation groups assigning groups to bank statement accounts 50 automatic bank statements 45 reconciliation rules assigning rules to groups 49 automatic bank statements 45 setting up 46 Recurring JE Compute & Print (R09302) 123 processing options 126 Refresh Cash Forecast Data (R00522) 253 processing options 255 Refresh Consolidation (R10862) 293, 295
processing options 296 Refresh Reconciliation File (R09130) 140, 154, 167 processing options 141 related documentation xxxiv reports Account Balance to Transactions (R09705) 375, 393 Account Balance w/o Account Master (R097031) 375 Account Balance without Account Master (R097031) 395 Account Structure (R10445) 309 Account Totals by Supplier/Customer (R09451) 513 Accounts without Business Units (R097041) 375, 394 Auto Bank Statement Processing (R09616) 192 Batch Out of Balance (R09706) 384 Batch to Detail (R007031) 375, 379 Batches Out of Balance (R007032) 375, 382 BU/Accounts Monthly Comparison (R10701) 318 Business Units/Accounts Monthly Comparison (R10701) 320 Cash Forecast Report (R095221) 256 category codes 498 Companies in Balance (R097001) 375, 386 Company by Batch Out of Balance (R09706) 375 Consolidated Balance Sheet (R10150) 318, 320 Consolidated Income Statement (R10250) 318, 321 Create Obj/Sub Control File (R10909) 303 Create UDC Control File (R10005) 303, 304 Debit/Credit T/B by Category Code (R09472) 516 G/L Budget Checking Report (R14115) 221 G/L by Category Code (R09470) 514 G/L by Object Account (R09421) 507 G/L with Subledger Totals (R09422) 509 general journal 497
538
Index
General Journal by Account (R09311) 503 general ledger 498 Intercompany Account Balance Integrity Report (R097011) 375 Intercompany Accounts in Balance (R097011) 389 Monthly Spreadsheet (R10412A) 369 Object/Subsidiary Value Control (R107021) 318, 320 Print Reconciliation Report (R09132P) 142 Prior Period Balance Integrity (R10700) 319 Simple Income Statement (R10211B) 359 Statement of Cash Flows Report (R10521) 363 Transaction Journal (R09321) 503 Transaction w/o Account Master (R097021) 375 Transactions by Object (R09423) 511 Transactions by Subsidiary (R09424) 513 Transactions to Batch Headers (R007021) 375 Transactions To Batch Headers (R007021) 376 Transactions without Account Master (R097021) 396 trial balance 498 Trial Balance by Object Account (R094121) 506 UDC Value Control (R107011) 319 UDC Value Control Exceptions (R107011) 318 Unposted Batches (R007011) 375, 382 Unposted Cash Basis Report (R09301) 269 Variance Analysis (R10212A) 371 Variance Analysis w/5 Months Actual (R10411A) 371 repost program 406, 408 when to repost 406 Repost Account Ledger (R099102) 406 processing options 408 Requested by Account (P14103) processing options 209 Requested by Business Unit (P14102)
processing options 209 Revise Automatic Bank Statement (P09616) processing options 187 Revise Electronic Bank Statement Staging (P09610) 182 Revise Forecast Basis (P1403) 241 Revise Inbound Consolidations Data (P1002Z1) 330
S
Simple Balance Sheet (R10111B) processing options 362 Simple Income Statement (R10211B) processing options 360 speed codes AAIs 29 example of 29 Spread Annual to Periods (R14801) processing options 215 Spreading annual amounts to periods during budget entry 213 spreadsheets overview of monthly 369 printing monthly spreadsheets 370 Statement of Cash Flows Report (R10521) 363 processing options 366 statements of cash flow, See cash flow statements statutory programs 338 Store & Forward JE Batch Processor (R09110ZS) processing options 117 store-and-forward processing adding journal entries 116 batch processor 116 creating journal entries 115 downloading master tables 113, 114 overview 113 purging processed journal entries 118 running the batch processor 117 updating transaction control records 118 uploading journal entries 116 subsidiaries global revisions 417, 418 suggestions, submitting xxxviii Summarize Transactions (R09811) 439, 441 processing options 441
539
Index
30
T
T/B / Ledger Comparison (P09210A) 340 T/B by Company (P09216) 343 processing options 345 T/B by Object Account (R09214) processing options 344 T/B by Subledger (P09215) 343 processing options 345 Transaction Journal (R09321) 503 Transactions by Object (R09423) 511 Transactions by Subsidiary (R09424) 513 processing options 513 Transactions to Batch Headers (R007021) 399 processing options 376 Transactions without Account Master (R097021) 396 processing options 397 transit accounts 159 trial balance inquiries 338 reports 498 Trial Balance by Object Account (P09214) 343 Trial Balance by Object Account (R094121) 506 Trial Balance/Ledger Comparison (P09210A) processing options 340 trial balances online inquiries 338 reviewing balances by company 343, 346 reviewing balances by object account 343, 345 reviewing balances by subledger 346 reviewing ledger comparisons 340, 341 typographical conventions xxxvi
automatic bank statements 36 business unit category codes 18 cash flow activity codes 70 cash flow rules 71 cash type codes 57 document types 19 ledger types 20 normal balance codes 71 overview 18 reconciliation codes 19, 34 subledger types 19 transaction codes 19 unposted batches 382 Unposted Batches (R007011) 382 Unposted Cash Basis Report (R09301) 269 Update BU.Obj.Sub to Jrnl Ent (R09806) 418, 419 Update Category Codes F0101>F0006 (R098021) 424, 425 Update Model/Consolidated Field (R0006QD) 423 Upload/Conversion (R0902Z1) 228 Upload/Conversion (R14110) 234 processing options 235 Upload/Conversion Revisions (P0902Z1) 234 processing options 228
V
Variable Numerator Compute & Print (R093022) processing options 137 Variance Analysis (R10212A) 371 processing options 371 Variance Analysis w/5 Months (R10411A) processing options 372 Variance Analysis w/5 Months Actual (R10411A) 371 Vertex sales tax 31 visual cues xxxvii
U
UDC Value Control Exceptions (R107011) processing options 319 UDCs account category codes 19
W
warnings xxxvii work orders speed account entry 87
540